Index: /trunk/gsdl-documentation/manuals/clean-all.sh
===================================================================
--- /trunk/gsdl-documentation/manuals/clean-all.sh	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/clean-all.sh	(revision 13632)
@@ -0,0 +1,26 @@
+#!/bin/sh
+
+echo "clean english version"
+cd en
+rm -r html
+rm -r pdf
+cd ..
+
+echo "clean french version"
+cd fr
+rm -r html
+rm -r pdf
+cd ..
+
+echo "clean spanish version"
+cd es
+rm -r html
+rm -r pdf
+cd ..
+
+
+echo "clean russian version"
+cd ru
+rm -r html
+rm -r pdf
+cd ..
Index: /trunk/gsdl-documentation/manuals/generate-html.sh
===================================================================
--- /trunk/gsdl-documentation/manuals/generate-html.sh	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/generate-html.sh	(revision 13632)
@@ -0,0 +1,139 @@
+#!/bin/sh
+
+gsdlhome=$GSDLHOME
+
+if [ "$gsdlhome" == "" ]; then
+    # assume tutorials in a subdir of gsdl
+      pushd .. > /dev/null
+      gsdlhome=`pwd`
+      popd > /dev/null
+fi
+
+echo "procesing english version"
+cd en
+mkdir html
+
+echo "User's manual (english)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl User_en.xml > html/User_en_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl User_en.xml > html/User_en_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl User_en.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "Installer's manual (english)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Install_en.xml > html/Install_en_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Install_en.xml > html/Install_en_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Install_en.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "Developer's manual (english)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Develop_en.xml > html/Develop_en_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Develop_en.xml > html/Develop_en_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Develop_en.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "From paper to collection (english)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Paper_en.xml > html/Paper_en_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Paper_en.xml > html/Paper_en_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Paper_en.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+cd ..
+
+
+echo "procesing french version"
+cd fr
+mkdir html
+cp -r images/ html/images
+cp ../style.css html/
+
+echo "User's manual (french)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl User_fr.xml > html/User_fr_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl User_fr.xml > html/User_fr_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl User_fr.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "Installer's manual (french)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Install_fr.xml > html/Install_fr_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Install_fr.xml > html/Install_fr_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Install_fr.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "Developer's manual (french)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Develop_fr.xml > html/Develop_fr_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Develop_fr.xml > html/Develop_fr_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Develop_fr.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "From paper to collection (french)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Paper_fr.xml > html/Paper_fr_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Paper_fr.xml > html/Paper_fr_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Paper_fr.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+cd ..
+
+
+echo "procesing spanish version"
+cd es
+mkdir html
+cp -r images/ html/images
+cp ../style.css html/
+
+echo "User's manual (spanish)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl User_es.xml > html/User_es_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl User_es.xml > html/User_es_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl User_es.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "Installer's manual (spanish)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Install_es.xml > html/Install_es_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Install_es.xml > html/Install_es_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Install_es.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "Developer's manual (spanish)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Develop_es.xml > html/Develop_es_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Develop_es.xml > html/Develop_es_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Develop_es.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "From paper to collection (spanish)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Paper_es.xml > html/Paper_es_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Paper_es.xml > html/Paper_es_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Paper_es.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+cd ..
+
+
+echo "procesing russian version"
+cd ru
+mkdir html
+cp -r images/ html/images
+cp ../style.css html/
+
+echo "User's manual (russian)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl User_ru.xml > html/User_ru_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl User_ru.xml > html/User_ru_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl User_ru.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "Installer's manual (russian)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Install_ru.xml > html/Install_ru_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Install_ru.xml > html/Install_ru_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Install_ru.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "Developer's manual (russian)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Develop_ru.xml > html/Develop_ru_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Develop_ru.xml > html/Develop_ru_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Develop_ru.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+echo "From paper to collection (russian)"
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-index.xsl Paper_ru.xml > html/Paper_ru_index.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-one-html.xsl Paper_ru.xml > html/Paper_ru_all.html
+java -cp $gsdlhome/gli:../ ApplyXSLT ../xml-to-many-html.xsl Paper_ru.xml | perl -S $gsdlhome/gli/help/splithelpdocument.pl
+mv *.htm html/
+
+cd ..
Index: /trunk/gsdl-documentation/manuals/generate-pdf.sh
===================================================================
--- /trunk/gsdl-documentation/manuals/generate-pdf.sh	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/generate-pdf.sh	(revision 13632)
@@ -0,0 +1,78 @@
+#!/bin/sh
+
+gsdlhome=$GSDLHOME
+export CLASSPATH=$CLASSPATH:../packages/fop-0.20.5/build/fop.jar:../packages/fop-0.20.5/lib:../
+
+
+if [ "$gsdlhome" == "" ]; then
+    # assume tutorials in a subdir of gsdl
+      pushd .. > /dev/null
+      gsdlhome=`pwd`
+      popd > /dev/null
+fi
+
+echo "procesing english manuals"
+cd en
+mkdir pdf
+
+#echo "User's manual (english)"
+#./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml User_en.xml -pdf pdf/User_en.pdf
+echo "Developer's manual (english)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Develop_en.xml -pdf pdf/Develop_en.pdf
+echo "User's manual (english)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Install_en.xml -pdf pdf/Install_en.pdf
+echo "From Paper to Collection (english)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Paper_en.xml -pdf pdf/Paper_en.pdf
+
+cd ..
+
+
+echo ""
+echo "procesing french manuals"
+cd fr
+mkdir pdf
+
+#echo "User's manual (french)"
+#./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml User_fr.xml -pdf pdf/User_fr.pdf
+echo "Developer's manual (french)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Develop_fr.xml -pdf pdf/Develop_fr.pdf
+echo "User's manual (french)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Install_fr.xml -pdf pdf/Install_fr.pdf
+echo "From Paper to Collection (french)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Paper_fr.xml -pdf pdf/Paper_fr.pdf
+
+cd ..
+
+
+echo ""
+echo "procesing spanish manuals"
+cd es
+mkdir pdf
+
+#echo "User's manual (spanish)"
+#./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml User_es.xml -pdf pdf/User_es.pdf
+echo "Developer's manual (spanish)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Develop_es.xml -pdf pdf/Develop_es.pdf
+echo "User's manual (spanish)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Install_es.xml -pdf pdf/Install_es.pdf
+echo "From Paper to Collection (spanish)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Paper_es.xml -pdf pdf/Paper_es.pdf
+
+cd ..
+
+
+echo ""
+echo "procesing russian manuals"
+cd ru
+mkdir pdf
+
+echo "User's manual (russian)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml User_ru.xml -pdf pdf/User_ru.pdf
+echo "Developer's manual (russian)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Develop_ru.xml -pdf pdf/Develop_ru.pdf
+echo "User's manual (russian)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Install_ru.xml -pdf pdf/Install_ru.pdf
+echo "From Paper to Collection (russian)"
+./../packages/fop-0.20.5/fop.sh -xsl ../xml-to-pdf.xsl -xml Paper_ru.xml -pdf pdf/Paper_ru.pdf
+
+cd ..
Index: /trunk/gsdl-documentation/manuals/processing/common.xsl
===================================================================
--- /trunk/gsdl-documentation/manuals/processing/common.xsl	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/processing/common.xsl	(revision 13632)
@@ -0,0 +1,191 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0"
+  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+  xmlns:java="http://xml.apache.org/xalan/java"
+  xmlns:util="ExternalRef" extension-element-prefixes="util">
+  
+  <xsl:template match="Title"><p><b><i><xsl:apply-templates/></i></b></p></xsl:template>
+  
+  <xsl:template match="Title" mode="Figure">
+  	<xsl:param name="no"/>
+  	<div style="margin-right:1.7pt;" align="center"><b>Figure&#160;<xsl:value-of select="$no"/>
+  			<xsl:if test="SubTitle"><xsl:value-of select="SubTitle"/></xsl:if>&#160;
+		  	<xsl:apply-templates select="Text"/></b>
+		</div>
+  </xsl:template>
+  
+  <xsl:template match="Title" mode="Table">  	  
+    <div style="margin-right:1.7pt;" align="center">
+    <b>Table&#160;<xsl:number count="Table[not(@class='hidden')]" level="any"/>&#160;<xsl:apply-templates/></b></div>
+  </xsl:template>
+
+	<xsl:template match="NumberedList"><ol><xsl:apply-templates/></ol></xsl:template>
+  <xsl:template match="NumberedItem"><li><xsl:apply-templates/></li></xsl:template>
+
+  <xsl:template match="BulletList">
+	<xsl:if test="not(parent::Bullet)">
+    <ul style="list-style-type: disc;">
+      <xsl:for-each select="Bullet">
+		<li><xsl:apply-templates/></li>
+		<xsl:if test="BulletList">
+		<xsl:for-each select="BulletList">
+  		  <ul style="list-style-type: disc;"><xsl:for-each select="Bullet"><li><xsl:apply-templates/></li></xsl:for-each></ul>
+		</xsl:for-each>
+		</xsl:if>
+	  </xsl:for-each>
+    </ul>
+    <p/>
+    </xsl:if>
+  </xsl:template>
+
+  <xsl:template match="Text">
+	<xsl:choose>
+		<xsl:when test="parent::Indented">
+		  <p style="font-size=12px; color=black; text-align=justify; margin-left=15pt;"><xsl:apply-templates/></p>
+		</xsl:when>
+		<xsl:when test="parent::Title|parent::Footnote"><xsl:apply-templates/></xsl:when>
+		<xsl:when test="not(parent::Version) and not(parent::Date) and not(parent::NumberedItem) and not(parent::Bullet)">
+			<p><xsl:apply-templates/></p>
+		</xsl:when>
+		<xsl:otherwise><xsl:apply-templates/></xsl:otherwise>
+	</xsl:choose>    
+  </xsl:template>
+
+  <xsl:template match="CodeLine">  
+  <xsl:choose>
+	<xsl:when test="parent::Figure or parent::th">
+	  <div style="margin-top:0pt; margin-right:0in; margin-bottom:0in; margin-left:2pt; margin-bottom:0pt; 
+	font-family: Courier; font-size: 11px"><xsl:apply-templates/></div>
+	</xsl:when>		
+	<xsl:when test="name(preceding-sibling::*[position()=1])='CodeLine' or name(following-sibling::*[position()=1])='CodeLine'">
+	  
+	    <div style="margin-top:0pt; margin-right:0pt; margin-bottom:0pt; margin-left:2em; font-size:10px; font-family:Courier;"><xsl:apply-templates/></div>
+	  
+	</xsl:when>      
+	<!-- a single line of code between two text paragraphs -->
+	<xsl:otherwise>
+	  <p><div style="font-size:10px; margin-right:0pt; margin-left:2em; margin-bottom:2px; margin-top:2px; font-family:Courier;">
+	<xsl:apply-templates/></div></p>	  
+  </xsl:otherwise>
+  </xsl:choose>  
+  </xsl:template>
+
+  <xsl:template match="Figure">
+    <a id="Figure_{@id}"/>
+  	<!-- number of current figure = total_number_of_previous_figure - total_number_of_previous_sub_figures-->
+    <xsl:variable name="temp_total_figs"><xsl:number count="Figure" level="any"/></xsl:variable>       
+    <xsl:variable name="temp_num_of_sub_figs">
+			<xsl:number count="Figure[Title/SubTitle and substring(translate(@id, '_0123456789', '99999999999'), string-length(@id)-1, string-length(@id))='99']" level="any"/>
+   	</xsl:variable>  	  	
+  	<xsl:variable name="no"><xsl:value-of select="$temp_total_figs - $temp_num_of_sub_figs"/></xsl:variable>   
+    <p/>        
+    <xsl:apply-templates select="Title" mode="Figure"><xsl:with-param name="no" select="$no"/></xsl:apply-templates>
+    <xsl:choose>    
+    <xsl:when test="CodeLine">
+      <table class="figure_code" align="center">
+      <xsl:for-each select="*[not(name()='Title')]">
+        <tr>
+        <xsl:if test="parent::Figure[@class='withLineNumber']">
+        <td><div style="linenumber"><xsl:number value="position()" format="1"/>&#160;&#160;</div></td></xsl:if>
+        <td><xsl:apply-templates select="."/></td></tr>
+      </xsl:for-each>
+      </table>
+    </xsl:when>
+    <xsl:when test="File"><div align="center"><xsl:apply-templates select="File"/></div><br/>
+		</xsl:when>    
+    </xsl:choose>
+    <br/>
+  </xsl:template> 
+
+  <xsl:template match="Table">
+    <p/>
+    <a id="Table_{@id}"/>
+    <xsl:if test="not(@class='hidden') and not(normalize-space(Title/Text)='')"><xsl:apply-templates select="Title" mode="Table"/></xsl:if>
+    <table cellpadding="2pt" cellspacing="2pt">
+        <xsl:if test="not(@class='hidden')">
+	  <xsl:if test="not(../../@class='hidden')"><xsl:attribute name="style">border-collapse:collapse;border:1px solid black;</xsl:attribute></xsl:if>
+	  <xsl:attribute name="rules">rows</xsl:attribute><xsl:attribute name="align">center</xsl:attribute>		
+	</xsl:if>
+	<xsl:if test="@class='hidden'"><xsl:attribute name="width">90%</xsl:attribute><xsl:attribute name="align">center</xsl:attribute></xsl:if>
+        <xsl:for-each select="TableContent/tr">
+          <tr>
+	  <xsl:if test="not(../../@class='hidden')"><xsl:attribute name="style">border-collapse:collapse;border:1px solid black;</xsl:attribute></xsl:if>
+          <xsl:for-each select="th"><td valign="top"><xsl:if test="File"><xsl:attribute name="align">right</xsl:attribute></xsl:if>
+          <xsl:apply-templates select="node()"/></td></xsl:for-each>
+	  </tr>
+	</xsl:for-each>
+    </table>
+    <br/>
+  </xsl:template>
+    
+  <xsl:template match="Section">     
+    <a name="Section_{@id}"/>
+    <h3><xsl:if test="not(starts-with(../../@id, 'appendix'))">
+    <xsl:number level="multiple" format="1.1" count="//Chapter|//Chapter//Section"/>&#160;</xsl:if>
+    <xsl:apply-templates select="Title/Text"/></h3>
+    <xsl:apply-templates select="Content/*"/>
+  </xsl:template>
+
+  <xsl:template match="Section" mode="preface">    
+    <h3><xsl:apply-templates select="Title/Text"/></h3>
+    <xsl:apply-templates select="Content/*"/>
+  </xsl:template>
+
+  <xsl:template match="Subsection">
+    <a name="Subsection_{@id}"/>
+    <h4><xsl:apply-templates select="Title/Text"/></h4>
+    <xsl:apply-templates select="Content/*"/>
+  </xsl:template>
+  
+  <xsl:template match="Part"><a id="Part_{@id}"/><xsl:apply-templates/></xsl:template>    
+
+  <xsl:template match="Comment"><xsl:apply-templates/></xsl:template>  
+  <xsl:template match="Indented"><p><div style="margin-left: 1em;"><xsl:apply-templates/></div></p></xsl:template>
+  <xsl:template match="img|table|br|td|tr|th">
+  	<xsl:copy><xsl:for-each select="@*"><xsl:copy/></xsl:for-each><xsl:apply-templates/></xsl:copy>
+  </xsl:template> 
+  <xsl:template match="i|b|u"><xsl:element name="{name()}"><xsl:apply-templates/></xsl:element></xsl:template>  
+  <xsl:template match="File"><a href="{@url}" target="_blank"><img src="../{@url}" width="{@width}" height="{@height}" border="0"/></a></xsl:template>
+  
+  
+  
+  <xsl:template match="text()"><xsl:value-of select="."/></xsl:template>
+  
+  <xsl:template match="Author"><b><xsl:apply-templates/></b></xsl:template>
+  <xsl:template match="Affiliation"><i><xsl:apply-templates/></i></xsl:template>
+  <xsl:template name="version_and_date"><p><b><xsl:apply-templates select="Version/Text"/></b>&#160;&#160;<xsl:apply-templates select="Date/Text"/></p></xsl:template>
+  
+  <xsl:template match="Chapter|Appendix|Bibliography" mode="index">
+  <dt><a href="#Chapter_{@id}"><xsl:apply-templates select="Title/Text"/></a></dt>
+  <xsl:for-each select="Content/Section"><dd><a href="#Section_{@id}"><xsl:apply-templates select="Title/Text"/></a></dd></xsl:for-each>
+</xsl:template>
+
+  <xsl:template match="Section" mode="index">
+  <dt><a href="#Section_{@id}"><xsl:apply-templates select="Title/Text"/></a></dt>  
+  </xsl:template>
+
+<xsl:template match="Chapter">
+  <a id="Chapter_{@id}"/>    
+  <h2><xsl:if test="not(starts-with(@id, 'appendix')) and not(starts-with(@id, 'biblio'))">
+  <xsl:value-of select="position()"/></xsl:if>&#160;<xsl:apply-templates select="Title/Text"/></h2>
+  <xsl:apply-templates select="Content/*"/>
+</xsl:template>
+
+  
+
+<xsl:template match="Figure" mode="ref">
+  	<xsl:variable name="temp_total_figs"><xsl:number count="Figure" level="any"/></xsl:variable>       
+	<xsl:variable name="temp_num_of_sub_figs">
+	<xsl:number count="Figure[Title/SubTitle and substring(translate(@id, '_0123456789', '99999999999'), string-length(@id)-1, string-length(@id))='99']" level="any"/>
+   	</xsl:variable>	  	
+  	<xsl:variable name="no"><xsl:value-of select="$temp_total_figs - $temp_num_of_sub_figs"/></xsl:variable>
+  	<xsl:variable name="subtitle">
+  	<xsl:if test="Title/SubTitle"><xsl:value-of select="substring-before(substring-after(Title/SubTitle, '('), ')')"/></xsl:if>
+  	</xsl:variable>
+  	<xsl:value-of select="concat($no, $subtitle)"/>
+  </xsl:template>  
+  <xsl:template match="Table" mode="ref"><xsl:number level="any"/></xsl:template>
+  <xsl:template match="Chapter" mode="ref"><xsl:number level="any"/></xsl:template>
+  <xsl:template match="Section" mode="ref"><xsl:number count="//Chapter|//Chapter//Section" format="1.1" level="multiple"/></xsl:template>
+  <xsl:template match="Subsection" mode="ref"><xsl:number level="multiple" format="1.1.1" count="//Chapter|//Chapter//Section|//Chapter//Section//Subsection"/></xsl:template>
+</xsl:stylesheet>
Index: /trunk/gsdl-documentation/manuals/processing/crossref-inter.xsl
===================================================================
--- /trunk/gsdl-documentation/manuals/processing/crossref-inter.xsl	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/processing/crossref-inter.xsl	(revision 13632)
@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0"
+  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+  xmlns:java="http://xml.apache.org/xalan/java"
+  xmlns:util="ExternalRef" extension-element-prefixes="util">
+
+<xsl:template match="CrossRef">
+    <xsl:variable name="ref" select="@ref"/>
+    <xsl:if test="@external">	    	
+	    <xsl:variable name="external" select="@external"/>	    
+	    <!--<a><xsl:attribute name="href"><xsl:value-of select="java:getRef($util, '@external', '@lang', '@target', '$ref')"/></xsl:attribute></a>-->
+	    <a><xsl:attribute name="href"><xsl:value-of select="concat(@external, '_', @lang, '_all.html#', @target, '_', @ref)"/></xsl:attribute><xsl:value-of select="util:getRef($external, @lang, @target, $ref)"/></a>    
+	  </xsl:if>
+	
+	<xsl:variable name="current_chapter" select="ancestor-or-self::Chapter[position()=1]/@id"/>
+
+	<xsl:variable name="target_chapter">
+		<xsl:choose>
+  		<xsl:when test="@target='Figure'"><xsl:value-of select="//Figure[@id=$ref]/ancestor-or-self::Chapter[position()=1]/@id"/></xsl:when>
+  		<xsl:when test="@target='Table'"><xsl:value-of select="//Table[@id=$ref]/ancestor-or-self::Chapter[position()=1]/@id"/></xsl:when>
+  		<xsl:when test="@target='Chapter'"><xsl:value-of select="//Chapter[@id=$ref]/ancestor-or-self::Chapter[position()=1]/@id"/></xsl:when>
+  		<xsl:when test="@target='Section'"><xsl:value-of select="//Section[@id=$ref]/ancestor-or-self::Chapter[position()=1]/@id"/></xsl:when> 		
+  		<xsl:when test="@target='Subsection'"><xsl:value-of select="//Subsection[@id=$ref]/ancestor-or-self::Chapter[position()=1]/@id"/></xsl:when>
+  		</xsl:choose>
+	</xsl:variable>
+  	
+	<a>
+	<xsl:attribute name="href">
+	<xsl:if test="not($current_chapter=$target_chapter)"><xsl:value-of select="concat('Chapter_', $target_chapter, '.htm#', @target, '_', @ref)"/></xsl:if>
+	<xsl:if test="$current_chapter=$target_chapter"><xsl:value-of select="concat('#', @target, '_', @ref)"/></xsl:if>
+	</xsl:attribute>
+  		<xsl:choose>
+  		<xsl:when test="@target='Figure'"><xsl:apply-templates select="//Figure[@id=$ref]" mode="ref"/></xsl:when>
+  		<xsl:when test="@target='Table'"><xsl:apply-templates select="//Table[@id=$ref]" mode="ref"/></xsl:when>
+  		<xsl:when test="@target='Chapter'"><xsl:apply-templates select="//Chapter[@id=$ref]" mode="ref"/></xsl:when>
+  		<xsl:when test="@target='Section'"><xsl:apply-templates select="//Section[@id=$ref]" mode="ref"/></xsl:when> 		
+  		<xsl:when test="@target='Subsection'"><xsl:apply-templates select="//Subsection[@id=$ref]" mode="ref"/></xsl:when>
+  		</xsl:choose>
+  	</a>
+  </xsl:template>
+  
+  <!--
+  <xsl:template match="FootnoteList">  
+  <xsl:for-each select="Footnote">
+  	<xsl:variable name="number">
+  		<xsl:apply-templates select="//FootnoteRef[@id=@id]" mode="getid"/>
+  	</xsl:variable>
+  	
+    <a name="fn{@id}"/><a href="#fnref{@id}">[<xsl:value-of select="$number"/>]</a>
+    <xsl:apply-templates/>
+    <br/>
+  </xsl:for-each>
+  </xsl:template>-->
+  
+  <xsl:template match="FootnoteRef">  	
+  	<a name="fnref{@id}"/><a href="#fn{@id}">[<xsl:number count="FootnoteRef" level="any" from="Chapter"/>]</a>
+  </xsl:template>     
+ 
+  <xsl:template match="FootnoteRef" mode="getid">
+  	<xsl:number count="FootnoteRef" level="any" from="Chapter"/>
+  </xsl:template>
+
+  </xsl:stylesheet>
Index: /trunk/gsdl-documentation/manuals/processing/crossref-pdf.xsl
===================================================================
--- /trunk/gsdl-documentation/manuals/processing/crossref-pdf.xsl	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/processing/crossref-pdf.xsl	(revision 13632)
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0"
+  xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format"
+  xmlns:java="http://xml.apache.org/xalan/java" xmlns:util="ExternalRef" extension-element-prefixes="util">
+
+  <xsl:template match="CrossRef">
+    <xsl:variable name="ref" select="@ref"/>
+    <xsl:if test="@external">	    	
+	    <xsl:variable name="external" select="@external"/>
+	    <xsl:value-of select="util:getRef($external, @lang, @target, $ref)"/>
+	  </xsl:if>
+    
+  	<fo:basic-link color="blue" internal-destination="{@target}_{@ref}">
+  		<xsl:choose>
+  		<xsl:when test="@target='Figure'"><xsl:apply-templates select="//Figure[@id=$ref]" mode="ref"/></xsl:when>
+  		<xsl:when test="@target='Table'"><xsl:apply-templates select="//Table[@id=$ref]" mode="ref"/></xsl:when>
+  		<xsl:when test="@target='Chapter'"><xsl:apply-templates select="//Chapter[@id=$ref]" mode="ref"/></xsl:when>
+  		<xsl:when test="@target='Section'"><xsl:apply-templates select="//Section[@id=$ref]" mode="ref"/></xsl:when> 		
+  		<xsl:when test="@target='Subsection'"><xsl:apply-templates select="//Subsection[@id=$ref]" mode="ref"/></xsl:when>
+  		</xsl:choose>
+  	</fo:basic-link>
+  </xsl:template>
+  
+  <xsl:template match="FootnoteList">  
+  <xsl:for-each select="Footnote">
+    <a name="fn{@id}"/><a href="#fnref{@id}">[<xsl:value-of select="@id"/>]</a>
+    <xsl:apply-templates/>
+    <br/>
+  </xsl:for-each>
+  </xsl:template>
+  <xsl:template match="FootnoteRef"><a name="fnref{@id}"/><a href="#fn{@id}">[<xsl:value-of select="@id"/>]</a></xsl:template>
+  
+  <xsl:template match="Figure" mode="ref">
+  	<xsl:variable name="temp_total_figs"><xsl:number count="Figure" level="any"/></xsl:variable>       
+	<xsl:variable name="temp_num_of_sub_figs">
+	<xsl:number count="Figure[Title/SubTitle and substring(translate(@id, '_0123456789', '99999999999'), string-length(@id)-1, string-length(@id))='99']" level="any"/>
+   	</xsl:variable>	  	
+  	<xsl:variable name="no"><xsl:value-of select="$temp_total_figs - $temp_num_of_sub_figs"/></xsl:variable>
+  	<xsl:variable name="subtitle">
+  	<xsl:if test="Title/SubTitle"><xsl:value-of select="substring-before(substring-after(Title/SubTitle, '('), ')')"/></xsl:if>
+  	</xsl:variable>
+  	<xsl:value-of select="concat($no, $subtitle)"/>
+  </xsl:template>  
+  
+  <xsl:template match="Table" mode="ref"><xsl:number level="any"/></xsl:template>
+  
+  <xsl:template match="Chapter" mode="ref"><xsl:number level="any"/></xsl:template>
+  
+  <xsl:template match="Section" mode="ref"><xsl:number count="//Chapter|//Chapter//Section" format="1.1" level="multiple"/></xsl:template>  
+  
+  <xsl:template match="Subsection" mode="ref"><xsl:number level="multiple" format="1.1.1" count="//Chapter|//Chapter//Section|//Chapter//Section//Subsection"/></xsl:template>
+  </xsl:stylesheet>
Index: /trunk/gsdl-documentation/manuals/processing/crossref.xsl
===================================================================
--- /trunk/gsdl-documentation/manuals/processing/crossref.xsl	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/processing/crossref.xsl	(revision 13632)
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0"
+  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+  xmlns:java="http://xml.apache.org/xalan/java"
+  xmlns:util="ExternalRef" extension-element-prefixes="util">
+
+  <xsl:template match="CrossRef">
+    <xsl:variable name="ref" select="@ref"/>
+    <xsl:if test="@external">	    	
+	    <xsl:variable name="external" select="@external"/>	    
+	    <!--<a><xsl:attribute name="href"><xsl:value-of select="java:getRef($util, '@external', '@lang', '@target', '$ref')"/></xsl:attribute></a>-->
+	    <a><xsl:attribute name="href"><xsl:value-of select="concat(@external, '_', @lang, '_all.html#', @target, '_', @ref)"/></xsl:attribute><xsl:value-of select="util:getRef($external, @lang, @target, $ref)"/></a>    
+	  </xsl:if>
+    
+  	<a href="#{@target}_{@ref}">
+  		<xsl:choose>
+  		<xsl:when test="@target='Figure'"><xsl:apply-templates select="//Figure[@id=$ref]" mode="ref"/></xsl:when>
+  		<xsl:when test="@target='Table'"><xsl:apply-templates select="//Table[@id=$ref]" mode="ref"/></xsl:when>
+  		<xsl:when test="@target='Chapter'"><xsl:apply-templates select="//Chapter[@id=$ref]" mode="ref"/></xsl:when>
+  		<xsl:when test="@target='Section'"><xsl:apply-templates select="//Section[@id=$ref]" mode="ref"/></xsl:when> 		
+  		<xsl:when test="@target='Subsection'"><xsl:apply-templates select="//Subsection[@id=$ref]" mode="ref"/></xsl:when>
+  		</xsl:choose>
+  	</a>
+  </xsl:template>
+  
+  <xsl:template match="FootnoteList">  
+  <xsl:for-each select="Footnote">
+    <a name="fn{@id}"/><a href="#fnref{@id}">[<xsl:value-of select="@id"/>]</a>
+    <xsl:apply-templates/>
+    <br/>
+  </xsl:for-each>
+  </xsl:template>
+  <xsl:template match="FootnoteRef"><a name="fnref{@id}"/><a href="#fn{@id}">[<xsl:value-of select="@id"/>]</a></xsl:template>
+  </xsl:stylesheet>
Index: /trunk/gsdl-documentation/manuals/processing/fo-common.xsl
===================================================================
--- /trunk/gsdl-documentation/manuals/processing/fo-common.xsl	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/processing/fo-common.xsl	(revision 13632)
@@ -0,0 +1,444 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
+
+<xsl:variable name="font" select="Cyrillic"/>
+
+<!-- display title in different formats -->
+<xsl:template match="Title">
+<xsl:choose>
+<!-- manual title -->
+<xsl:when test="parent::Manual">
+  <fo:block font-size="24.0pt" line-height="24pt" space-after.optimum="25pt" text-align="right" padding-top="3pt"><xsl:apply-templates/></fo:block>
+</xsl:when>
+
+<!-- chapter title -->
+<xsl:when test="parent::Chapter">
+<fo:block font-size="24.0pt" line-height="24pt" text-align="right" padding-top="3pt" id="Chapter_{../@id}">
+<xsl:if test="not(starts-with(@id, 'appendix')) and not(starts-with(@id, 'biblio'))"><xsl:number count="Chapter" format="1"/></xsl:if>
+</fo:block>
+<fo:block font-size="24.0pt" line-height="24pt" space-before.optimum="25pt" text-align="right" padding-top="3pt" text-indent="3cm"><xsl:apply-templates/></fo:block>
+</xsl:when>
+
+<!-- sections' title, with section number -->
+<xsl:when test="parent::Section and not(../Manual)">
+<fo:block font-size="12.0pt" text-align="left" padding-top="3pt" space-before.optimum="25pt" id="Section_{../@id}">
+<xsl:if test="not(starts-with(../../../@id, 'appendix'))"><xsl:number level="multiple" count="Chapter|Chapter/Content/Section" format="1.1"/>&#160;&#160;</xsl:if>
+<xsl:apply-templates select="Text"/>
+</fo:block>
+</xsl:when>
+
+<!-- tables(not hidden) title, in grey background and with unique number -->
+<xsl:when test="parent::Table">
+<fo:block id="Table_{../@id}" font-size="10.0pt" font-weight="bold" line-height="15pt" background-color="grey" margin-left="25pt" space-before="10pt" space-after="3pt">
+Table&#160;<xsl:number level="any" count="Table[not(@class='hidden')]"/>&#160;&#160;<xsl:apply-templates select="Text"/><xsl:value-of select="SubTitle"/>
+</fo:block>
+</xsl:when>
+
+<!-- title of subsections -->
+<xsl:when test="parent::Subsection">
+<fo:block font-size="10pt" font-weight="bold" text-align="left" id="{../@id}" space-before.optimum="25pt">
+<xsl:apply-templates select="Text"/>
+</fo:block>
+</xsl:when>
+
+<!-- title of parts -->
+<xsl:when test="parent::Part">
+<fo:block font-size="10pt" font-weight="bold" text-align="left" id="{../@id}" space-before.optimum="15pt">
+<xsl:apply-templates select="Text"/>
+</fo:block>
+</xsl:when>	
+</xsl:choose>
+</xsl:template>
+
+
+
+<xsl:template match="Title" mode="Figure">
+<xsl:param name="no"/>
+<fo:block id="Figure_{../@id}" font-size="10.0pt" font-weight="bold" line-height="15pt" background-color="grey" margin-left="25pt" space-before="10pt" space-after="3pt">
+Figure&#160;<xsl:value-of select="$no"/><xsl:if test="SubTitle"><xsl:value-of select="SubTitle"/></xsl:if>&#160;<xsl:apply-templates select="Text"/>
+</fo:block>
+</xsl:template>
+
+
+
+<!-- deal with various text paragraph formats -->
+<xsl:template match="Text">
+<xsl:choose>
+<!-- these text display directly -->
+<xsl:when test="parent::Title|parent::Author|parent::Affiliation|parent::Version|parent::Date|parent::Bullet|parent::Footnote"><xsl:apply-templates/></xsl:when>
+
+<!-- text in table cells display with 11pt font size -->
+<xsl:when test="parent::th">
+<fo:block font-size="11.0pt"><xsl:apply-templates select="node()"/></fo:block>
+</xsl:when>
+
+<!-- indented text -->
+<xsl:when test="parent::Indented">
+<fo:block font-size="11.0pt" color="black" text-align="justify" space-before.optimum="15pt" margin-left="35pt">
+<xsl:apply-templates/>
+</fo:block>
+</xsl:when>
+
+<!-- normal text paragraphs -->
+<xsl:otherwise>
+<fo:block font-size="11.0pt" color="black" text-align="justify" space-before.optimum="15pt" margin-left="25pt">
+<xsl:apply-templates/>
+</fo:block>
+</xsl:otherwise>
+</xsl:choose>
+</xsl:template>
+
+
+
+<xsl:template match="Section|Content"><xsl:apply-templates/></xsl:template>
+
+
+<xsl:template match="Version">
+<fo:block font-size="12.0pt" font-weight="bold" color="gray" space-before.optimum="15pt" padding-top="3pt" margin-left="25pt" text-align-last="justify">
+<xsl:apply-templates/><fo:leader leader-pattern="space"/><xsl:value-of select="following-sibling::Date"/>
+</fo:block>
+</xsl:template>
+
+
+<xsl:template match="BulletList">
+<xsl:if test="not(parent::Bullet)">
+<fo:list-block start-indent="2cm" provisional-distance-between-starts="12pt" font-family="{$font}" space-before.optimum="15pt">
+<xsl:for-each select="Bullet">
+<fo:list-item><fo:list-item-label end-indent="label-end()">
+<fo:block><fo:inline font-family="Symbol">&#x2022;</fo:inline></fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">				
+<fo:block><xsl:apply-templates/></fo:block>
+
+<!-- if contains a child BulletList node -->
+<xsl:if test="BulletList">					
+<xsl:for-each select="BulletList">
+<fo:list-block start-indent="3cm" provisional-distance-between-starts="12pt" font-family="{$font}" space-before.optimum="5pt">
+<xsl:for-each select="Bullet">
+<fo:list-item><fo:list-item-label end-indent="label-end()">
+<fo:block><fo:inline font-family="Symbol">&#x2022;</fo:inline></fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block><xsl:apply-templates/></fo:block>
+</fo:list-item-body>
+</fo:list-item>
+</xsl:for-each>
+</fo:list-block>	
+</xsl:for-each>
+</xsl:if>
+
+</fo:list-item-body>
+</fo:list-item>
+</xsl:for-each>
+</fo:list-block>
+</xsl:if>
+</xsl:template>
+
+
+
+<xsl:template match="NumberedList">
+<fo:list-block start-indent="2cm" provisional-distance-between-starts="12pt" font-family="{$font}" space-before.optimum="15pt">
+<xsl:for-each select="NumberedItem">
+<fo:list-item><fo:list-item-label end-indent="label-end()">
+<fo:block><fo:inline font-family="Symbol"><xsl:number/>.</fo:inline></fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<xsl:choose>
+<!-- does not contain child (indented) Text or CodeLines -->
+<xsl:when test="(count(Text)+count(CodeLine))=1">
+<fo:block><xsl:apply-templates select="Text/node()"/></fo:block>
+</xsl:when>
+
+<!-- contains child (indented) Text or CodeLines -->
+<xsl:otherwise>
+<fo:block><xsl:apply-templates select="Text[1]/node()"/></fo:block>
+<fo:list-block start-indent="3cm" provisional-distance-between-starts="12pt" font-family="{$font}" space-before.optimum="15pt" space-after.optimum="15pt">
+<xsl:for-each select="child::*[position()>1]">
+<fo:list-item><fo:list-item-label end-indent="label-end()"><fo:block/></fo:list-item-label>
+<fo:list-item-body><fo:block><xsl:apply-templates/></fo:block></fo:list-item-body>
+</fo:list-item>
+</xsl:for-each>
+</fo:list-block>
+</xsl:otherwise>
+</xsl:choose>
+</fo:list-item-body>
+</fo:list-item>
+</xsl:for-each>
+</fo:list-block>
+</xsl:template>
+
+
+
+<xsl:template match="b"><fo:inline font-weight="bold"><xsl:apply-templates/></fo:inline></xsl:template>
+
+<xsl:template match="i"><fo:inline font-style="italic"><xsl:apply-templates/></fo:inline></xsl:template>
+
+<xsl:template match="u"><fo:inline text-decoration="underline" color="blue"><xsl:apply-templates/></fo:inline></xsl:template>
+
+<xsl:template match="CodeLine">
+<fo:block font-size="8.0pt" font-family="Courier" color="black" text-align="left">
+<xsl:choose>
+<xsl:when test="parent::NumberedItem or parent::Bullet"/>
+<!-- normal code lines -->
+<xsl:when test="not(parent::Figure) and not(parent::th)">
+<xsl:attribute name="margin-left">50pt</xsl:attribute>
+<xsl:if test="not(name(preceding-sibling::*[position()=1])='CodeLine')">
+<xsl:attribute name="space-before.optimum">8pt</xsl:attribute>
+</xsl:if>
+</xsl:when>
+
+<!-- codeline in a hidden table -->
+<xsl:when test="parent::th and ../../../../@class='hidden'">
+<xsl:attribute name="margin-left">10pt</xsl:attribute>
+<xsl:attribute name="space-before.optimum">8pt</xsl:attribute>
+<xsl:attribute name="space-after.optimum">8pt</xsl:attribute>
+</xsl:when>
+<!-- normal table -->
+<xsl:otherwise>
+<xsl:if test="not(parent::th)">
+<xsl:attribute name="space-before.optimum">3pt</xsl:attribute>
+</xsl:if>
+</xsl:otherwise>
+</xsl:choose>
+
+<xsl:apply-templates/>
+</fo:block>
+
+<!--
+<xsl:param name="withLineNumber">n</xsl:param>
+<xsl:choose>
+<xsl:when test="not(parent::Figure) and not(parent::th)">
+<fo:block font-size="8.0pt" font-family="Courier" color="black" text-align="left" margin-left="50pt">
+<xsl:if test="not(name(preceding-sibling::*[position()=1])='CodeLine')">
+<xsl:attribute name="space-before.optimum">8pt</xsl:attribute>
+</xsl:if>
+<xsl:apply-templates/>
+</fo:block>
+</xsl:when>
+
+<xsl:when test="parent::th and ../../../../@class='hidden'">
+<fo:block font-size="8.0pt" font-family="Courier" color="black" 
+text-align="left" margin-left="10pt" space-before.optimum="8pt" space-after.optimum="8pt">
+<xsl:apply-templates/>
+</fo:block>
+</xsl:when>
+
+<xsl:otherwise>
+<fo:block font-size="8.0pt" font-family="Courier" color="black" text-align="left">
+<xsl:if test="not(parent::th)">
+<xsl:attribute name="space-before.optimum">3pt</xsl:attribute>
+</xsl:if>
+<xsl:if test="$withLineNumber='y'"><xsl:number/></xsl:if>
+<xsl:apply-templates/>
+</fo:block>
+</xsl:otherwise>
+</xsl:choose>
+-->
+</xsl:template>
+
+
+
+
+
+<!-- table -->
+<xsl:template match="Table">
+<fo:table table-layout="fixed" width="100%">
+<fo:table-column column-width="proportional-column-width(1)"/>
+<fo:table-body>
+
+<!-- table title -->
+
+<fo:table-row>
+<!-- always keep the table title with the table -->
+<xsl:if test="not(normalize-space(Title/Text)='')"><xsl:attribute name="keep-with-next">always</xsl:attribute></xsl:if>				
+<fo:table-cell>
+<fo:block>
+<xsl:if test="not(normalize-space(Title/Text)='')"><xsl:apply-templates select="Title"/></xsl:if>
+</fo:block>
+</fo:table-cell>
+</fo:table-row>
+
+<!-- table content -->
+
+<fo:table-row>
+<fo:table-cell>
+<fo:block>
+<!-- use nested table to center-align the table -->
+<fo:table table-layout="fixed" width="100%">
+<fo:table-column column-width="25pt"/>
+<fo:table-column column-width="60pt"/>				
+<fo:table-body>
+<fo:table-row>
+<fo:table-cell column-number="1"/>
+<fo:table-cell column-number="2">
+<fo:table table-layout="fixed">
+<xsl:for-each select="TableContent/tr[1]/th">
+<fo:table-column>
+
+<!-- calculate the column width based on the width in the original html file -->
+
+<xsl:attribute name="column-width">
+<xsl:value-of select="concat(number(@width) * 0.8, 'px')"/>
+</xsl:attribute>
+</fo:table-column>
+</xsl:for-each>
+<fo:table-body>
+<xsl:for-each select="TableContent/tr">
+
+<!-- this is to ensure no breaks in the table -->
+
+<fo:table-row keep-with-next="always">
+<xsl:for-each select="th">
+<xsl:choose>
+
+<!-- when the cell contains only text -->
+
+<xsl:when test="not(../../../@class='hidden') and not(File)">
+<fo:table-cell column-number="{position()}" vertical-align="top" padding="2pt" border="0.5pt" border-color="black" border-style="solid">
+<xsl:if test="position()=1 and normalize-space(../../tr[1]/th[1])=''"><xsl:attribute name="text-align">right</xsl:attribute></xsl:if>
+<xsl:if test="position()>1 and not(last())"><xsl:attribute name="text-align">left</xsl:attribute></xsl:if>
+<xsl:if test="last()"><xsl:attribute name="text-align">justify</xsl:attribute></xsl:if>
+<xsl:apply-templates/>
+</fo:table-cell>
+</xsl:when>
+
+<!-- when the cell is an image --> 
+
+<xsl:when test="not(../../../@class='hidden') and File">
+<fo:table-cell column-number="{position()}" vertical-align="top" text-align="right" padding="2pt" border="0.5pt" border-color="black" border-style="solid">
+<xsl:apply-templates/>
+</fo:table-cell>
+</xsl:when>
+
+<!-- deal with hidden table -->
+
+<xsl:when test="../../../@class='hidden'">
+<fo:table-cell column-number="{position()}" vertical-align="top" padding="2pt">
+<xsl:if test="position()=1"><xsl:attribute name="text-align">left</xsl:attribute></xsl:if>
+<xsl:if test="position()>1"><xsl:attribute name="text-align">justify</xsl:attribute></xsl:if>
+<xsl:apply-templates/>
+</fo:table-cell></xsl:when></xsl:choose></xsl:for-each></fo:table-row></xsl:for-each></fo:table-body></fo:table></fo:table-cell>
+</fo:table-row></fo:table-body></fo:table></fo:block></fo:table-cell></fo:table-row></fo:table-body></fo:table>
+</xsl:template>
+
+
+
+<!-- Figure -->
+<xsl:template match="Figure">
+<fo:table table-layout="fixed" width="100%">
+<fo:table-column column-width="proportional-column-width(1)"/>
+<fo:table-body>
+
+<!-- figure title -->
+<!-- number of current figure = total_number_of_previous_figure - total_number_of_previous_sub_figures-->
+<xsl:variable name="temp_total_figs"><xsl:number count="Figure" level="any"/></xsl:variable>       
+<xsl:variable name="temp_num_of_sub_figs">
+  <xsl:number count="Figure[Title/SubTitle and substring(translate(@id, '_0123456789', '99999999999'), string-length(@id)-1, string-length(@id))='99']" level="any"/>
+</xsl:variable>  	  	
+<xsl:variable name="no"><xsl:value-of select="$temp_total_figs - $temp_num_of_sub_figs"/></xsl:variable>
+
+<fo:table-row keep-with-next="always"><fo:table-cell><fo:block>
+<xsl:apply-templates select="Title" mode="Figure"><xsl:with-param name="no" select="$no"/></xsl:apply-templates>
+</fo:block></fo:table-cell></fo:table-row>
+
+
+<fo:table-row><fo:table-cell>
+<xsl:if test="File"><xsl:apply-templates select="File"/></xsl:if>
+<xsl:if test="CodeLine">
+<fo:block text-align="left">
+<fo:table start-indent="3pt" table-layout="fixed" width="100%" border-spacing="3pt">
+<fo:table-column column-width="proportional-column-width(1)"/>
+<fo:table-column column-width="100mm"/>
+<fo:table-column column-width="proportional-column-width(1)"/>
+<fo:table-body>
+<fo:table-row>
+<fo:table-cell column-number="2">
+
+<xsl:if test="not(@calss='withLineNumber')">
+<xsl:attribute name="border-width">0.1pt</xsl:attribute><xsl:attribute name="border-style">solid</xsl:attribute>
+<xsl:attribute name="border-color">black</xsl:attribute><xsl:attribute name="border-collapse">separate</xsl:attribute>
+</xsl:if>
+
+<xsl:choose>
+<!-- display the codeline number besides each codeline using nested table -->
+<xsl:when test="@class='withLineNumber'">
+<fo:table start-indent="3pt" table-layout="fixed" width="100%" border-spacing="3pt">
+<fo:table-column column-width="28pt"/>											  
+<fo:table-column column-width="proportional-column-width(1)" border-width="0.1pt" border-style="solid" border-color="black" border-collapse="separate"/>
+<fo:table-body>
+<xsl:for-each select="CodeLine">
+<fo:table-row>
+<fo:table-cell column-number="1">
+<fo:block font-size="8pt" font-family="Courier" space-before.optimum="3pt" text-align="right"><xsl:number/></fo:block>
+</fo:table-cell>
+<fo:table-cell column-number="2"><xsl:apply-templates select="."/></fo:table-cell>
+</fo:table-row>
+</xsl:for-each>
+</fo:table-body>
+</fo:table>										
+</xsl:when>
+
+<xsl:otherwise><xsl:apply-templates select="CodeLine"/></xsl:otherwise>
+</xsl:choose></fo:table-cell></fo:table-row></fo:table-body></fo:table></fo:block></xsl:if>
+</fo:table-cell></fo:table-row></fo:table-body></fo:table>
+</xsl:template>
+
+
+
+
+<xsl:template match="File">
+<xsl:variable name="height"><xsl:value-of select="@height"/>em</xsl:variable>
+<xsl:variable name="width"><xsl:value-of select="@width"/>em</xsl:variable>
+<fo:block display-align="center" text-align="center" space-after.optimum="15pt" space-before.optimum="3pt">
+<fo:external-graphic display-align="center" src="{@url}" content-height="{$height}" content-width="{$width}"/>
+</fo:block>
+</xsl:template>
+
+
+
+<!-- reference in the text to a footnote -->
+<xsl:template match="FootnoteRef">
+<xsl:variable name="no"><xsl:value-of select="@id"/></xsl:variable>
+<fo:footnote>
+<fo:inline baseline-shift="super" font-size="smaller">(<xsl:value-of select="$no"/>)</fo:inline>
+<fo:footnote-body>
+<fo:list-block provisional-label-separation="0pt" provisional-distance-between-starts="18pt" space-after.optimum="6pt">
+<fo:list-item>
+<fo:list-item-label end-indent="label-end()">
+<fo:block>(<xsl:number count="//FootnoteRef" level="any"/>)</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block><xsl:apply-templates select="//Footnote[@id=$no]"/></fo:block>
+</fo:list-item-body>
+</fo:list-item>
+</fo:list-block>
+</fo:footnote-body>
+</fo:footnote>
+</xsl:template>
+
+
+<xsl:template match="Footnote"><xsl:apply-templates/></xsl:template>
+
+
+<xsl:template match="BibItem">
+<fo:block font-size="11.0pt" color="black" text-align="justify" space-before.optimum="15pt" margin-left="25pt"><xsl:apply-templates/></fo:block>
+</xsl:template>
+
+
+<xsl:template match="Author">
+<fo:block font-size="15pt" color="black" text-align="right" space-before.optimum="25pt"><xsl:apply-templates/></fo:block>
+</xsl:template>
+
+
+<xsl:template match="Affiliation">
+<fo:block font-size="10.0pt" color="black" text-align="right" space-after.optimum="125pt" space-before.optimum="25pt"><xsl:apply-templates/></fo:block>
+</xsl:template>
+
+
+<xsl:template match="Text" mode="heading"><fo:block font-size="18.0pt" color="gray" text-align="right"><xsl:apply-templates/></fo:block></xsl:template>
+
+
+<xsl:template match="text()"><xsl:value-of select="."/></xsl:template>
+
+<xsl:template match="br"><fo:block/></xsl:template>
+</xsl:stylesheet>
Index: /trunk/gsdl-documentation/manuals/processing/style.css
===================================================================
--- /trunk/gsdl-documentation/manuals/processing/style.css	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/processing/style.css	(revision 13632)
@@ -0,0 +1,27 @@
+/* CSS Document */
+
+h1{ font-family:arial,sans-serif; font-weight:normal; font-size:25px; margin:0; }
+h2{ font-family:arial,sans-serif; font-weight:normal; font-size:22px; margin:0; }
+h3{ font-family:arial,sans-serif; font-weight:normal; font-size:18px; }
+h4{ font-family:arial,sans-serif; font-size:14px; }
+
+p{ FONT-SIZE: 13px; FONT-FAMILY: Arial, Helvetica, sans-serif; COLOR: #000000}
+
+table.figure_code{
+	padding-bottom:2pt; padding-left:2pt; padding-right:2pt; padding-top:2pt;	
+	border-collapse: collapse; border: solid; color:black; border-width: 1pt;
+}
+
+div.linenumber{
+	margin-top:0pt; margin-right:0in; margin-bottom:0in; margin-left:0pt; margin-bottom:0pt; font-family:Courier; FONT-SIZE: 8pt
+}
+
+li {FONT-SIZE: 12px; FONT-FAMILY: Arial, Helvetica, sans-serif; COLOR: #000000}
+
+ul {list-style-type: decimal}
+
+dd {margin-top: 2pt; margin-bottom: 0pt; font-size: 12px}
+dt {margin-top: 1pt; margin-bottom: 0pt; font-size: 12px}
+a {font-size: 12px}
+
+img{border: 0px}
Index: /trunk/gsdl-documentation/manuals/processing/xml-to-index.xsl
===================================================================
--- /trunk/gsdl-documentation/manuals/processing/xml-to-index.xsl	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/processing/xml-to-index.xsl	(revision 13632)
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0"
+  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+  xmlns:java="http://xml.apache.org/xslt/java"
+  extension-element-prefixes="java"
+  exclude-result-prefixes="java">
+  
+  <xsl:variable name="mode">cd</xsl:variable>
+  <xsl:output method="html"/>
+  <xsl:include href="common.xsl"/>
+  
+  <xsl:template match="Manual">
+    <html>
+      <head><title><xsl:value-of select="Title/Text"/></title></head>
+      <link rel="stylesheet" href="../../style.css" type="text/css"/>
+      <body>
+	<h2><xsl:apply-templates select="Heading/Text"/></h2>
+	<h1><xsl:apply-templates select="Title/Text"/></h1>
+	
+	<xsl:apply-templates select="Author"/>
+	<xsl:apply-templates select="Affiliation"/>
+  <xsl:apply-templates select="Text"/>
+	<xsl:apply-templates select="Comment"/>
+	<xsl:call-template name="version_and_date"/>		<br/>
+
+	<xsl:apply-templates select="Section" mode="preface"/>
+		
+	<dl>
+	  <xsl:apply-templates select="Chapter"/>
+	</dl>
+  </body>
+</html>
+</xsl:template>
+
+  <xsl:template match="Chapter">
+    <dt><a href="Chapter_{@id}.htm"><xsl:apply-templates select="Title/Text"/></a></dt>
+    <dd><xsl:for-each select="Title">
+			<xsl:apply-templates/><br/>
+			</xsl:for-each>
+    </dd>
+  </xsl:template>
+</xsl:stylesheet>
Index: /trunk/gsdl-documentation/manuals/processing/xml-to-many-html.xsl
===================================================================
--- /trunk/gsdl-documentation/manuals/processing/xml-to-many-html.xsl	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/processing/xml-to-many-html.xsl	(revision 13632)
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+  xmlns:java="http://xml.apache.org/xslt/java"
+  xmlns:util="xalan://org.greenstone.gsdl3.util.XSLTUtil"
+  extension-element-prefixes="java util"
+  exclude-result-prefixes="java util">
+
+  <xsl:include href="common.xsl"/>
+  <xsl:include href="crossref-inter.xsl"/>
+
+  <xsl:output method="html"/> 
+  
+  <xsl:template match="Chapter|FootnoteList">    
+    <html>
+      <head>
+	<title><xsl:apply-templates select="Title/Text"/></title>
+	<link rel="stylesheet" href="../../style.css" type="text/css"/>
+      </head>
+      <body>
+        <table width="90%" border="0" align="center"><tr><td>
+	<h2><xsl:value-of select="/Manual/Heading/Text"/>&#160;<xsl:value-of select="/Manual/Title/Text"/></h2>
+	<a name="Chapter_{@id}"/><h1>
+	  <xsl:if test="not(starts-with(@id, 'appendix') or starts-with(@id, 'biblio'))">
+	  Chapter <xsl:number/>&#160;</xsl:if><xsl:apply-templates select="Title/Text"/></h1>
+	
+	<xsl:if test="Content/Section">
+	<h3>Contents</h3>	
+	<xsl:apply-templates select="Content/Section" mode="index"/>
+	</xsl:if>
+
+	<xsl:apply-templates select="Content/*"/>	
+	
+	<xsl:if test="descendant::FootnoteRef and not(name()='FootnoteList')">
+  	<hr/>
+	  <xsl:for-each select="descendant::FootnoteRef">
+	  <xsl:variable name="fnrefname"><xsl:value-of select="@id"/></xsl:variable>
+	  <xsl:variable name="number"><xsl:number count="FootnoteRef" level="any" from="Chapter"/></xsl:variable>  		  
+	  <xsl:for-each select="/Manual/FootnoteList/Footnote[@id=$fnrefname]">
+		<!--<a name="fn{@id}"/><a href="#fnref{@id}">[<xsl:number/>]</a>&#160;-->		
+    <a name="fn{@id}"/><a href="#fnref{@id}">[<xsl:value-of select="$number"/>]</a>
+		<xsl:apply-templates/>
+		<br/>		
+     </xsl:for-each>     
+	  </xsl:for-each>
+	</xsl:if>
+	</td></tr></table>
+      </body>
+    </html>    
+  </xsl:template>  
+</xsl:stylesheet> 
Index: /trunk/gsdl-documentation/manuals/processing/xml-to-one-html.xsl
===================================================================
--- /trunk/gsdl-documentation/manuals/processing/xml-to-one-html.xsl	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/processing/xml-to-one-html.xsl	(revision 13632)
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0"
+  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+  xmlns:java="http://xml.apache.org/xslt/java"
+  xmlns:util="xalan://org.greenstone.gsdl3.util.XSLTUtil"
+  extension-element-prefixes="java util"
+  exclude-result-prefixes="java util">
+
+  <xsl:include href="common.xsl"/>
+  <xsl:include href="crossref.xsl"/>
+  <xsl:output method="html"/>
+  
+  <xsl:template match="Manual">
+    <html>
+      <head>
+      <title><xsl:value-of select="Title/Text"/></title>
+      <link rel="stylesheet" href="../../style.css" type="text/css"/>
+      </head>
+    <body>
+    <table width="90%" border="0" align="center">
+      <tr><td>
+    	<h2><xsl:apply-templates select="Heading/Text"/></h2>
+			<h1><xsl:apply-templates select="Title/Text"/></h1>
+			<xsl:apply-templates select="Author"/>
+			<xsl:apply-templates select="Affiliation"/>
+			<xsl:apply-templates select="Text"/>
+			<xsl:apply-templates select="Comment"/>
+			<xsl:call-template name="version_and_date"/>		
+			<br/>			
+			<xsl:apply-templates select="Section" mode="preface"/>
+			<h3>Contents</h3>
+			<a name="index"/>
+			<dl>
+	  		<xsl:apply-templates select="Chapter[not(@hidden)]|Appendix|Bibliography" mode="index"/>
+			</dl>
+			<xsl:apply-templates select="Chapter"/>
+			<xsl:apply-templates select="Appendix"/>
+			<xsl:apply-templates select="Bibliography"/>	
+			<xsl:if test="FootnoteList"><hr/><xsl:apply-templates select="FootnoteList"/></xsl:if>	
+			</td></tr></table>
+    </body>
+  </html>
+</xsl:template>  
+</xsl:stylesheet>
Index: /trunk/gsdl-documentation/manuals/processing/xml-to-pdf.xsl
===================================================================
--- /trunk/gsdl-documentation/manuals/processing/xml-to-pdf.xsl	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/processing/xml-to-pdf.xsl	(revision 13632)
@@ -0,0 +1,214 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
+
+<xsl:include href="fo-common.xsl"/>
+<xsl:include href="crossref-pdf.xsl"/>
+
+<xsl:variable name="font" select="sans-serif"/>
+
+<xsl:template match="Manual">
+
+<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
+<fo:layout-master-set>
+<!-- template set for different types of pages -->
+<!-- the first page template -->
+<fo:simple-page-master master-name="first" page-height="29.7cm" page-width="21cm" margin-top="1cm" margin-bottom="2cm" margin-left="2.5cm" margin-right="2.5cm">
+<fo:region-start extent="1cm"/>
+<fo:region-body margin-top="3cm" margin-left="2cm"/>
+<fo:region-before precedence="true" extent="3cm"/>
+<fo:region-after extent="1.5cm"/>
+</fo:simple-page-master>
+
+<!-- the preface page template -->
+<fo:simple-page-master master-name="preface" page-height="29.7cm" page-width="21cm" margin-top="1cm" margin-bottom="2cm" margin-left="2.5cm" margin-right="2.5cm">
+<fo:region-body margin-top="3cm"/>
+<fo:region-before extent="3cm"/>
+<fo:region-after extent="1.5cm"/>
+</fo:simple-page-master>
+
+<!-- the acknowledgements page template -->
+<fo:simple-page-master master-name="acknowledgements" page-height="29.7cm" page-width="21cm"
+margin-top="1cm" margin-bottom="2cm" margin-left="2.5cm" margin-right="2.5cm">
+<fo:region-body margin-top="3cm"/>
+<fo:region-before extent="3cm"/>
+<fo:region-after extent="1.5cm"/>
+</fo:simple-page-master>
+
+<!-- the table of content page template -->
+<fo:simple-page-master master-name="ToC" page-height="29.7cm" page-width="21cm" margin-top="1cm" margin-bottom="2cm" margin-left="2.5cm" margin-right="2.5cm">
+<fo:region-body margin-top="3cm"/>
+<fo:region-before extent="3cm"/>
+<fo:region-after extent="1.5cm"/>
+</fo:simple-page-master>
+
+<!-- the document page template -->
+<fo:simple-page-master master-name="document" page-height="29.7cm" page-width="21cm" margin-top="1cm" margin-bottom="2cm" margin-left="2.5cm" margin-right="2.5cm">
+<fo:region-body margin-top="3cm"/>
+<fo:region-before extent="3cm" precedence="true" display-align="after"/>
+<fo:region-after extent="1.5cm"/>
+</fo:simple-page-master>
+</fo:layout-master-set>
+
+
+
+<!-- Cover Page-->
+
+<fo:page-sequence master-reference="first">
+<fo:static-content flow-name="xsl-region-start">
+<!-- left banner image -->
+<fo:block-container height="29cm" width="2cm" left="0cm" top="0cm">
+<fo:block><fo:external-graphic src="url('Install_files/image001.jpg')" height="29cm"/></fo:block>
+</fo:block-container>
+</fo:static-content>
+<fo:flow flow-name="xsl-region-body">
+<xsl:apply-templates select="Heading/Text" mode="heading"/>
+<xsl:apply-templates select="Title"/>
+<xsl:apply-templates select="Author"/>
+<xsl:apply-templates select="Affiliation"/>
+<xsl:apply-templates select="Text"/>
+<xsl:apply-templates select="Comment"/>
+<xsl:apply-templates select="Version"/>
+</fo:flow>
+</fo:page-sequence>
+
+
+
+<!-- Preface -->
+
+<fo:page-sequence master-reference="preface">
+<fo:flow flow-name="xsl-region-body">
+<xsl:for-each select="Section[not(@id='acknowledgements')]"><xsl:apply-templates/></xsl:for-each>
+</fo:flow>
+</fo:page-sequence>
+
+<fo:page-sequence master-reference="acknowledgements">
+<fo:flow flow-name="xsl-region-body"><xsl:apply-templates select="Section[@id='acknowledgements']"/></fo:flow>
+</fo:page-sequence>
+
+
+
+<!-- ToC Page -->
+
+<fo:page-sequence master-reference="ToC">
+<fo:flow flow-name="xsl-region-body">
+<fo:block text-align="right" font-size="24.0pt" line-height="24pt" space-after.optimum="25pt" padding-top="3pt">Contents</fo:block>
+<xsl:for-each select="Chapter">
+  <xsl:variable name="show_number">
+    <xsl:if test="starts-with(@id, 'appendix') or starts-with(@id, 'biblio')">n</xsl:if>
+    <xsl:if test="not(starts-with(@id, 'appendix')) and not(starts-with(@id, 'biblio'))">y</xsl:if>
+  </xsl:variable>
+  <fo:block text-align="start" font-size="15.0pt" line-height="15pt" text-align-last="justify" space-before.optimum="15pt" padding-top="3pt">
+  <fo:basic-link color="black" internal-destination="Chapter_{@id}">
+  <xsl:if test="$show_number='y'"><xsl:number/>&#160;&#160;</xsl:if>
+  <xsl:apply-templates select="Title/Text"/>
+  <fo:leader leader-pattern="space"/>
+  <fo:page-number-citation ref-id="Chapter_{@id}"/>
+  </fo:basic-link>
+  </fo:block>
+
+  <xsl:for-each select="Content/Section">
+    <fo:block text-align="start" font-size="10.0pt" font-weight="bold" text-align-last="justify" padding-top="3pt" space-before.optimum="15pt" margin-left="12pt">
+    <fo:basic-link color="black" internal-destination="Section_{@id}">
+    <xsl:if test="$show_number='y'"><xsl:number level="multiple" count="Chapter|Chapter/Content/Section" format="1.1"/>&#160;&#160;</xsl:if>
+    <xsl:apply-templates select="Title/Text"/>
+    <fo:leader leader-pattern="space"/>
+    <fo:page-number-citation ref-id="Section_{@id}"/>
+    </fo:basic-link>
+    <xsl:for-each select="Content/Subsection"><xsl:call-template name="SubsectionLink"/></xsl:for-each>
+    </fo:block>
+  </xsl:for-each>
+</xsl:for-each>
+
+
+
+<!-- figure and table lists -->
+<!--
+<xsl:if test="not(count(//Figure[not(normalize-space(Title/Text)='')])=0)">
+<fo:block break-before="page" space-before.optimum="50pt" space-after.optimum="15pt" font-size="15pt" font-weight="bold">Figures</fo:block>
+<xsl:for-each select="//Figure">
+<fo:block text-align="start" font-size="10.0pt" font-weight="bold" text-align-last="justify">
+<fo:basic-link color="black" internal-destination="Figure_{@id}">
+<xsl:apply-templates select="Title/Text"/>
+<fo:leader leader-pattern="space"/>
+<fo:page-number-citation ref-id="Figure_{@id}"/>
+</fo:basic-link>
+</fo:block>
+</xsl:for-each>
+</xsl:if>
+
+<xsl:if test="not(count(//Table[not(normalize-space(Title/Text)='')])=0)">
+<fo:block break-before="page" space-before.optimum="50pt" space-after.optimum="15pt" font-size="15pt" font-weight="bold">Tables</fo:block>
+<xsl:for-each select="//Table[not(@class='hidden')]">
+<fo:block text-align="start" font-size="10.0pt" font-weight="bold" text-align-last="justify">
+<fo:basic-link color="black" internal-destination="Table_{@id}">
+<xsl:apply-templates select="Title/Text"/>
+<fo:leader leader-pattern="space"/>
+<fo:page-number-citation ref-id="Table_{@id}"/>
+</fo:basic-link>
+</fo:block>
+</xsl:for-each>
+</xsl:if>
+-->
+
+</fo:flow>
+</fo:page-sequence>
+
+
+
+<!-- Document -->
+
+<fo:page-sequence master-reference="document" initial-page-number="1">
+<!-- defines header of a page -->
+<fo:static-content flow-name="xsl-region-before">
+<xsl:variable name="pageno"><fo:page-number/></xsl:variable>
+<xsl:choose>
+<xsl:when test="$pageno='1'">
+<fo:block-container height="1cm" width="18cm" left="0cm" top="0cm" display-align="after">
+<fo:block text-align="start" font-size="10pt" font-family="{$font}" line-height="14pt">greenstone.org<fo:external-graphic src="url('_files/header.gif')"/>
+</fo:block>
+</fo:block-container>
+</xsl:when>
+<xsl:otherwise>
+<fo:block-container height="1cm" width="18cm" left="0cm" top="0cm" display-align="after">
+<fo:block text-align="start" font-size="10pt" font-family="{$font}" line-height="14pt">
+<fo:page-number/>&#160;&#160;
+<fo:retrieve-marker retrieve-class-name="head" retrieve-position="first-including-carryover" retrieve-boundary="page-sequence"/>
+</fo:block>
+</fo:block-container>
+</xsl:otherwise>
+</xsl:choose>
+</fo:static-content>
+
+<!-- footer of a page -->
+<fo:static-content flow-name="xsl-footnote-separator">
+<fo:block><fo:leader leader-pattern="rule" leader-length="100%" rule-style="solid" rule-thickness="0.5pt"/></fo:block>
+</fo:static-content>
+
+<fo:flow flow-name="xsl-region-body">
+<xsl:for-each select="Chapter">
+<!-- header -->
+<fo:block><fo:marker marker-class-name="head"><xsl:value-of select="Title"/></fo:marker></fo:block>
+<xsl:apply-templates/>
+<xsl:if test="not(count(following-sibling::*[not(name()='FootnoteList')])=0)">
+<fo:block break-after="page"/>
+</xsl:if>
+</xsl:for-each>
+
+</fo:flow>
+</fo:page-sequence>
+</fo:root>
+</xsl:template>
+
+
+
+<xsl:template name="SubsectionLink">
+<fo:block text-align="start" font-size="10.0pt" text-align-last="justify" margin-left="25pt" padding-top="3pt">
+<fo:basic-link color="black">
+<xsl:attribute name="internal-destination">Subsection_<xsl:value-of select="@id"/></xsl:attribute>
+<xsl:apply-templates select="Title/Text"/>
+<fo:leader leader-pattern="space"/>
+<fo:page-number-citation ref-id="Subsection_{@id}"/>
+</fo:basic-link>
+</fo:block>
+</xsl:template>
+</xsl:stylesheet>
Index: /trunk/gsdl-documentation/manuals/xml-source/en/Develop_en.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/en/Develop_en.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/en/Develop_en.xml	(revision 13632)
@@ -0,0 +1,5208 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">GREENSTONE DIGITAL LIBRARY</Text>
+</Heading>
+<Title>
+<Text id="2">DEVELOPER'S GUIDE</Text>
+</Title>
+<Author>
+<Text id="3">David Bainbridge, Dana McKay and Ian H. Witten</Text>
+</Author>
+<Affiliation>
+<Text id="4">Department of Computer Science<br/>University of Waikato, New Zealand</Text>
+</Affiliation>
+<Text id="5">Greenstone is a suite of software for building and distributing digital library collections. It provides a new way of organizing information and publishing it on the Internet or on CD-ROM. Greenstone is produced by the New Zealand Digital Library Project at the University of Waikato, and developed and distributed in cooperation with UNESCO and the Human Info NGO. It is open-source software, available from <i>http://greenstone.org</i> under the terms of the Gnu General Public License.</Text>
+<Comment>
+<Text id="6">We want to ensure that this software works well for you. Please report any problems to <i>greenstone@cs.waikato.ac.nz</i></Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">March 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">About this manual</Text>
+</Title>
+<Content>
+<Text id="10">This manual explains how Greenstone works. It is aimed at those who wish to customise collections and to develop and maintain the software.</Text>
+<Text id="11">Section <CrossRef target="Chapter" ref="understanding_the_collection-building_process"/> gives an insider's account of the collection-building process, including the directory structure, the internal document format, and the configuration file that governs the structure of each collection. Section <CrossRef target="Chapter" ref="getting_the_most_out_of_your_documents"/> describes the parts of Greenstone that process source documents (and metadata) and dictate how the information is accessed through the user interface. It also describes âexternalâ software components that are distributed with Greenstone. Section <CrossRef target="Chapter" ref="the_greenstone_runtime_system"/> explains the structure of the Greenstone runtime system, and also gives details of the software that help to understand how it works and how to modify the system to suit different needs. Section <CrossRef target="Chapter" ref="configuring_your_greenstone_site"/> describes the Greenstone configuration files, and an Appendix introduces the C++ Standard Template Library.</Text>
+<Text id="12">When working with the Greenstone software, you may encounter references to features that are not described in this manual, for Greenstone is under constant development. To learn about current work, join the Greenstone mailing list (instructions at greenstone.org).</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="13">Companion documents</Text>
+</Title>
+<Content>
+<Text id="14">The complete set of Greenstone documents includes five volumes:</Text>
+<BulletList>
+<Bullet>
+<Text id="15">Greenstone Digital Library Installer's Guide</Text>
+</Bullet>
+<Bullet>
+<Text id="16">Greenstone Digital Library User's Guide</Text>
+</Bullet>
+<Bullet>
+<Text id="17">Greenstone Digital Library Developer's Guide <i>(this document)</i></Text>
+</Bullet>
+<Bullet>
+<Text id="18">Greenstone Digital Library: From Paper to Collection</Text>
+</Bullet>
+<Bullet>
+<Text id="19">Greenstone Digital Library: Using the Organizer</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="20">Acknowledgements</Text>
+</Title>
+<Content>
+<Text id="21">The Greenstone software is a collaborative effort between manypeople. Rodger McNab and Stefan Boddie are the principal architects andimplementors. Contributions have been made by David Bainbridge, GeorgeBuchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, JohnMcPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, ToddReed, Bill Rogers, John Thompson, and Stuart Yeates. Other members of the New ZealandDigital Library project provided advice and inspiration in the design ofthe system: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te TakaKeegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols and Lloyd Smith. We would also like toacknowledge all those who have contributed to the GNU-licensed packagesincluded in this distribution: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE and XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="understanding_the_collection-building_process">
+<Title>
+<Text id="22">Understanding the collection-building process</Text>
+</Title>
+<Content>
+<Text id="23">End users of Greenstone can build collections using the Collector, described in the <i>Greenstone Digital Library User's Guide</i>(Section 3). This makes it very easy to build collections modelled after existing ones but with new content. However, it is not really feasible to use the Collector to create collections with completely new structures. It does invite you to edit the collection configuration file, which governs the collection's structure, but you need to know quite a lot about Greenstone to make radical yet effective changes. This section tells you what you need to know to do this. It also describes the Greenstone directory structure and the format in which documents are stored internally.</Text>
+<Text id="24">We assume throughout this manual that you have installed Greenstone on your computer, be it Windows or Unix. If you have not yet done this you should consult the <i>Greenstone Digital Library Installer's Guide</i>. The name <i>GSDLHOME</i> is used throughout to refer to the Greenstone home directory, which is called <i>%GSDLHOME%</i> on Windows systems and <i>$GSDLHOME</i> on Unix ones. You set this directory during the installation procedure.</Text>
+<Section id="building_collections_from_the_command_line">
+<Title>
+<Text id="25">Building collections from the command line</Text>
+</Title>
+<Content>
+<Text id="26">Let us begin by walking through the operations involved in building a collection from the command line, to help understand the process better. Of course, for more user-friendly collection building, you should use the Collector instead. The collection we take as an example is one that comes on the Greenstone software distribution CD-ROM, and contains the WWW home pages of many of the people who have worked on the New Zealand Digital Library Project and the Greenstone software.</Text>
+<Text id="27">Separate subsections follow for building under Windows and Unix. In fact, the two subsections are very nearly identicalâyou need only go through the one that pertains to your system. When following the walkthrough, you may find some operations mysterious and arcane, but follow them closelyâtheir meaning will be explained later on. After the walkthroughs is a brief summary of the differences between building a collection under the two systems.</Text>
+<Subsection id="collection_building_under_windows">
+<Title>
+<Text id="28">Collection building under Windows</Text>
+</Title>
+<Content>
+<Text id="29">The first challenge when building a Greenstone collection from the command line under Windows is to get at the âcommand prompt,â the place where you type commands. Try looking in the <i>Start</i> menu, or under the <i>Programs</i> submenu, for an entry like <i>MS-DOS Prompt</i>, <i>DOS Prompt</i>, or <i>Command Prompt</i>. If you can't find it, invoke the <i>Run</i> entry and try typing <i>command</i> (or <i>cmd</i>) in the dialog box. If all else fails, seek help from one who knows, such as your system administrator.</Text>
+<Text id="30">Change into the directory where Greenstone has been installed. Assuming Greenstone was installed in its default location, you can move there by typing</Text>
+<CodeLine>cd "C:\Program Files\gsdl "</CodeLine>
+<Text id="31">(You need the quotation marks because of the space in <i>Program Files</i>.) Next, at the prompt type</Text>
+<CodeLine>setup.bat</CodeLine>
+<Text id="32">This batch file (which you can read if you like) tells the system where to look for Greenstone programs.<FootnoteRef id="1"/>If, later on in your interactive session at the DOS prompt, you wish to return to the top level Greenstone directory you can accomplish this by typing <i>cd "%GSDLHOME%"</i> (again, the quotation marks are here because of spaces in the filename). If you close your DOS window and start another one, you will need to invoke <i>setup.bat</i> again.</Text>
+<Text id="33">Now you are in a position to make, build and rebuild collections. The first program we will look at is the Perl program <i>mkcol.pl</i>, whose name stands for âmake a collection.â First run the program by typing <i>perl âS mkcol.pl</i> to cause a description of usage and a list of arguments to appear on the screen âif your Windows environment is set up to associate the Perl application with files ending in <i>.pl</i>, this can be more concisely expressed by entering <i>mkcol.pl</i>. As you can see from the usage statement, the only required argument is <i>creator</i>, which is used to specify who built the collection.</Text>
+<Text id="34">Let us now use the command to create the initial files and subdirectories necessary for our home page collection of Greenstone Digital Library project members. To assign the collection the name <i>dlpeople</i>, I typed</Text>
+<CodeLine>perl âS mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<Text id="35">(or <i>mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</i> if Perl is associated with the <i>.pl</i> file extension). Please substitute your email address for mine!</Text>
+<Text id="36">To view the newly created files, move to the newly created collection directory by typing</Text>
+<CodeLine>cd "%GSDLHOME%\collect\dlpeople"</CodeLine>
+<Figure id="collection_configuration_file_created_by_mkcol">
+<Title>
+<Text id="37">Collection configuration file created by <i>mkcol.pl</i></Text>
+</Title>
+<CodeLine>creatorÂ Â Â Â Â Â Â Â Â Â Â Â Â me@cs.waikato.ac.nz</CodeLine>
+<CodeLine>maintainerÂ Â Â Â Â Â Â Â Â Â me@cs.waikato.ac.nz</CodeLine>
+<CodeLine>publicÂ Â Â Â Â Â Â Â Â Â Â Â Â Â true</CodeLine>
+<CodeLine>betaÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â true</CodeLine>
+<CodeLine>indexesÂ Â Â Â Â Â Â Â Â Â Â Â Â document:text</CodeLine>
+<CodeLine>defaultindexÂ Â Â Â Â Â Â Â document:text</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â ZIPPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â GAPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â TEXTPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â HTMLPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â EMAILPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â ArcPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â RecPlug</CodeLine>
+<CodeLine>classifyÂ Â Â Â Â Â Â Â Â Â Â Â AZList -metadata "Title"</CodeLine>
+<CodeLine>collectionmetaÂ collectionnameÂ Â Â Â "dlpeople"</CodeLine>
+<CodeLine>collectionmetaÂ iconcollectionÂ Â Â Â ""</CodeLine>
+<CodeLine>collectionmetaÂ collectionextraÂ Â Â ""</CodeLine>
+<CodeLine>collectionmetaÂ .document:textÂ Â Â Â "documents "</CodeLine>
+</Figure>
+<Text id="38">You can list the contents of this directory by typing <i>dir</i>. There should be seven subdirectories: <i>archives</i>, <i>building</i>, <i>etc</i>, <i>images</i>, <i>import</i>, <i>index</i> and <i>perllib</i>.</Text>
+<Text id="39">Now we must populate the collection with sample documents. Source material for the <i>dlpeople</i> collection can be found on the Greenstone distribution CD-ROM under the directory <i>collect\dlpeople</i>. First, insert the CD-ROM into the drive (e.g. into <i>D:\</i>). Next, copy the contents of the <i>D:\collect\dlpeople</i> directory into the <i>dlpeople</i> collection's <i>import</i> directory. You can do this as follows:</Text>
+<Indented>
+<Text id="40">select the contents of the <i>dlpeople</i> directory <br/>and drag them into the <i>dlpeople</i> collection's <i>import</i> directory.</Text>
+</Indented>
+<Text id="41">Alternatively, you can type the command</Text>
+<CodeLine>xcopy /s d:\collect\dlpeople\* import</CodeLine>
+<Text id="42">In the collection's <i>etc</i> directory there is a file called <i>collect.cfg</i>. Open it using your favourite text editor âa basic but commonly available one is called <i>edit</i>. It should look something like Figure <CrossRef target="Figure" ref="collection_configuration_file_created_by_mkcol"/>, which shows the collection configuration file that was created by using the command <i>perl âS mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</i>.</Text>
+<Text id="43">Now you are ready to âimportâ the collection. This is the process of bringing the documents into the Greenstone system, standardising the document format, the way that metadata is specified, and the file structure in which the documents are stored. Type <i>perl âS import.pl</i> at the prompt to get a list of all the options for the import program. The -<i>remove old</i> option is used to ensure that any previously imported documents are removed first.</Text>
+<CodeLine>perl âS import.pl -removeold dlpeople</CodeLine>
+<Text id="44">Don't worry about all the text that scrolls pastâit's just reporting the progress of the import. Be aware that importing this collection takes about five minutes on a 1 GHz computer, and correspondingly longer on slower machines. Note that you do not have to be in either the <i>collect</i> or <i>dlpeople</i> directories when this command is entered; because GSDLHOME is already set, the Greenstone software can work out where the necessary files are.</Text>
+<Text id="45">Now let's make some changes to the collection configuration file to customize its appearance. First, give the collection a name. This will be treated by web browsers as the page title for the front page of the collection, and used as the collection icon in the absence of a picture. Change the line that reads <i>collectionmeta collectionname "dlpeople"</i> to something like <i>collectionmeta collectionname "The People of the NZDL project"</i>.</Text>
+<Text id="46">Add a description of your collection between the quotes of the line that reads <i>collectionmeta collectionextra ""</i>. This is used as the <i>About this collection</i> text on the collection's home page. I added âThis collection is made up of the home pages of some of the people who have worked on the NZDL project.â It is important to enter this as a single line in the editor âdon't be tempted to press enter if the cursor reaches the right-hand side of the editor window even though there is more text to add, just keep on typing âotherwise the configuration file cannot be parsed correctly. If you want your collection to be usable with different language interfaces, there is a way to make this text come out differently depending on the interface language chosen. This is described in Section <CrossRef target="Section" ref="configuration_file"/> below.</Text>
+<Text id="47">You can use any picture you can view in a web browser for a collection iconâthe image I created is shown in Figure <CrossRef target="Figure" ref="collection_icon"/>. Put the location of the image between the quotes of the line <i>collectionmeta iconcollection ""</i> in the configuration file. As shorthand, and to aid portability <i>_httpprefix_</i> can be used as the start of a URL that points to an image within the Greenstone file area. For example you could enter: <i>_httpprefix_/collect/dlpeople/images/icon.gif</i> if you have put a suitable image in the collection's <i>images</i> directory (<i>collect\dlpeople\images</i> in our example).</Text>
+<Text id="48">Save the collection configuration file, and close itâyou won't need to look at it again during this tutorial.</Text>
+<Text id="49">The next phase is to âbuildâ the collection, which creates all the indexes and files that make the collection work. Type <i>perl âS buildcol.pl</i> at the command prompt for a list of collection-building options. These options are explained more fully in Section <CrossRef target="Section" ref="import_and_build_processes"/>. For now, stick to the defaults by typing</Text>
+<CodeLine>perl âS buildcol.pl dlpeople</CodeLine>
+<Text id="50">Again, don't worry about the âprogress reportâ text that scrolls past.</Text>
+<Text id="51">Make the collection âliveâ as follows:</Text>
+<Text id="52">select the contents of the <i>dlpeople</i> collection's <i>building</i> directory and drag them into the <i>index</i> directory.</Text>
+<Text id="53">Alternatively, you can remove the <i>index</i> directory (and all its contents) by typing the command</Text>
+<CodeLine>rd /s index                 # on Windows NT/2000</CodeLine>
+<CodeLine>deltree /Y index       # on Windows 95/98</CodeLine>
+<Text id="54">and then change the name of the <i>building</i> directory to <i>index</i> with</Text>
+<CodeLine>ren building index</CodeLine>
+<Text id="55">Finally, type</Text>
+<CodeLine>mkdir building</CodeLine>
+<Text id="56">in preparation for any future rebuilds. It is important that these commands are issued from the correct directory (unlike the Greenstone commands <i>mkcol.pl</i>, <i>import.pl</i> and <i>buildcol.pl</i>). If the current working directory is not <i>dlpeople</i>, type <i>cd "%GSDLHOME%\collect\dlpeople"</i> before going through the <i>rd</i>, <i>ren</i> and <i>mkdir</i> sequence above.</Text>
+<Text id="57">You should be able to access the newly built collection from your Greenstone homepage. You will have to reload the page if you already had it open in your browser, or perhaps even close the browser and restart it (to prevent caching problems). Alternatively, if you are using the âlocal libraryâ version of Greenstone you will have to restart the library program. To view the new collection, click on the image. The result should look something like Figure <CrossRef target="Figure" ref="about_page_for_the_new_collection"/>.</Text>
+<Figure id="collection_icon">
+<Title>
+<Text id="58">Collection icon</Text>
+</Title>
+<File width="156" height="120" url="images/Dev_Fig_2.gif"/>
+</Figure>
+<Text id="59">In summary then, the commands typed to produce the <i>dlpeople</i> collection are:</Text>
+<CodeLine>cd "C:\Program Files\gsdl " # assuming default location</CodeLine>
+<CodeLine>setup.bat</CodeLine>
+<CodeLine>perl âS mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<CodeLine>cd "%GSDLHOME%\collect\dlpeople "</CodeLine>
+<CodeLine>xcopy   /s   d:\collect\dlpeople\*   import # assuming D drive</CodeLine>
+<CodeLine>perl âS import.pl dlpeople</CodeLine>
+<CodeLine>perl âS buildcol.pl dlpeople</CodeLine>
+<CodeLine>rd /s index           # on Windows NT/2000</CodeLine>
+<CodeLine>deltree /Y index # on Windows 95/98</CodeLine>
+<CodeLine>ren building index</CodeLine>
+<CodeLine>mkdir building</CodeLine>
+</Content>
+</Subsection>
+<Subsection id="collection_building_under_unix">
+<Title>
+<Text id="60">Collection building under Unix</Text>
+</Title>
+<Content>
+<Text id="61">First change into the directory where Greenstone has been installed. For example, if Greenstone is installed under its default name at the top level of your home account you can move there by typing</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<Text id="62">Next at the prompt, type</Text>
+<CodeLine>source setup.bash     # if you're running the BASH shell</CodeLine>
+<CodeLine>source setup.csh       # if you're running the C shell</CodeLine>
+<Text id="63">These batch files (which you can read if you like) tell the system where to look for Greenstone programs. If, later on in your command-line session with Greenstone, you wish to return to the top level Greenstone directory you can accomplish this by typing <i>cd $GSDLHOME</i>.</Text>
+<Text id="64">If you are unsure of the shell type you are using, enter <i>echo $0</i> at your command-line prompt âit will print out the sought information. If you are using a different shell contact your system administrator for advice.</Text>
+<Text id="65">With the appropriate setup file sourced, we are now in a position to make, build and rebuild collections. The first program we will look at is the Perl program <i>mkcol.pl</i>, whose name stands for âmake a collection.â First run the program by typing <i>mkcol.pl</i> on its own to cause a description of usage and a list of arguments to appear on the screen. As you can see from the usage statement, the only required argument is <i>creator</i>, which is used to specify who built the collection.</Text>
+<Figure id="about_page_for_the_new_collection">
+<Title>
+<Text id="66">âAboutâ page for the new collection</Text>
+</Title>
+<File width="389" height="409" url="images/Dev_Fig_3.png"/>
+</Figure>
+<Text id="67">Let us now use the command to create the initial files and directories necessary for our home page collection of Greenstone Digital Library project members. To assign the collection the name <i>dlpeople</i>, I typed</Text>
+<CodeLine>mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<Text id="68">Please substitute your email address for mine!</Text>
+<Text id="69">To view the newly created files, move to the newly created collection directory by typing</Text>
+<CodeLine>cd $GSDLHOME/collect/dlpeople</CodeLine>
+<Text id="70">You can list the contents of this directory by typing <i>ls</i>. There should be seven subdirectories: <i>archives</i>, <i>building</i>, <i>etc</i>, <i>images</i>, <i>import</i>, <i>index</i> and <i>perllib</i>.</Text>
+<Text id="71">Now we must populate the collection with sample documents. Source material for the <i>dlpeople</i> collection can be found on the Greenstone distribution CD-ROM under the directory <i>collect/dlpeople</i>. To get information from a CD-ROM under Linux, insert the disk into the drive and type</Text>
+<CodeLine>mount /cdrom</CodeLine>
+<Text id="72">at the prompt (this command may differ from one system to another). Once mounted, the CD-ROM can be used like any other directory, so type <i>ls /cdrom/collect</i>. This should reveal a directory called <i>dlpeople</i> on the CD-ROM.</Text>
+<Text id="73">Next, copy the contents of the <i>/cdrom/collect/dlpeople</i> directory into the <i>GSDLHOME/collect/dlpeople/import</i> directory. To do this, type the command</Text>
+<CodeLine>cp âr /cdrom/collect/dlpeople/*   import/</CodeLine>
+<Text id="74">Then type</Text>
+<CodeLine>umount /cdrom</CodeLine>
+<Text id="75">to close the CD-ROM drive.</Text>
+<Text id="76">In the collection's <i>etc</i> directory there is a file called <i>collect.cfg</i>. Open this using your favourite text editor âemacs is a popular editor on Linux. It should look something like Figure <CrossRef target="Figure" ref="collection_configuration_file_created_by_mkcol"/>, which shows the collection configuration file that was created by using the command <i>mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</i>.</Text>
+<Text id="77">Now you are ready to âimportâ the collection. This is the process of bringing the documents into the Greenstone system, standardising the document format, the way that metadata is specified, and the file structure in which the documents are stored. Type <i>import.pl</i> at the prompt to get a list of all the options for the import program. The -<i>remove old</i> option is used to ensure that any previously imported documents are removed first</Text>
+<CodeLine>import.pl âremoveold dlpeople</CodeLine>
+<Text id="78">Don't worry about all the text that scrolls pastâit's just reporting the progress of the import. Be aware that importing this collection takes about five minutes on a 1 GHz computer, and correspondingly longer on slower machines. Note, you do not have to be in either the <i>collect</i> or <i>dlpeople</i> directories when this command is entered; because GSDLHOME is already set, the Greenstone software can work out where the necessary files are.</Text>
+<Text id="79">Now let's make some changes to the collection configuration file to customize its appearance. First, give the collection a name. This will be treated by web browsers as the page title for the front page of the collection, and used as the collection icon in the absence of a picture. Change the line that reads <i>collectionmeta collectionname "dlpeople"</i> to something like <i>collectionmeta collectionname "The People of the NZDL project"</i>.</Text>
+<Text id="80">Add a description of your collection between the quotes of the line that reads <i>collectionmeta collectionextra ""</i>. This is used as the <i>About this collection</i> text on the collection's home page. I added âThis collection is made up of the home pages of some of the people who have worked on the NZDL project.â It is important to enter this as a single line in the editorâdon't be tempted to press enter if the cursor reaches the right-hand side of the editor window even though there is more text to add, just keep on typing âotherwise the configuration file cannot be parsed correctly. If you want your collection to be usable with different language interfaces, there is a way to make this text come out differently depending on the interface language chosen. This is described in Section <CrossRef target="Section" ref="configuration_file"/> below.</Text>
+<Text id="81">You can use any picture you can view in a web browser for a collection iconâthe image I created is shown in Figure <CrossRef target="Figure" ref="collection_icon"/>. Put the location of the image between the quotes of the line <i>collectionmeta iconcollection ""</i> in the configuration file. As shorthand, and to aid portability <i>_httpprefix_</i> can be used as the start of a URL that points to an image within the Greenstone file area. For example you could enter: <i>_httpprefix_/collect/dlpeople/images/icon.gif</i> if you have put a suitable image in the collection's <i>images</i> directory (<i>collect/dlpeople/images</i> in our example).</Text>
+<Text id="82">Save the collection configuration file, and close itâyou won't need to look at it again during this tutorial.</Text>
+<Text id="83">The next phase is to âbuildâ the collection, which creates all the indexes and files that make the collection work. Type <i>buildcol.pl</i> at the command prompt for a list of collection-building options. These options are explained more fully in Section <CrossRef target="Section" ref="import_and_build_processes"/>. For now, stick to the defaults by typing</Text>
+<CodeLine>buildcol.pl dlpeople</CodeLine>
+<Text id="84">at the prompt. Again, don't worry about the âprogress reportâ text that scrolls past.</Text>
+<Text id="85">Make the collection âliveâ by putting all the material that has just been put in the collection's <i>building</i> directory into the <i>index</i> directory. If you have built this collection before, first remove the old index using</Text>
+<CodeLine>rm âr index/*</CodeLine>
+<Text id="86">(assuming you are in the <i>dlpeople</i> directory) at the prompt. Then type</Text>
+<CodeLine>mv building/* index/</CodeLine>
+<Table id="collection-building_differences_between_windows_and_linux">
+<Title>
+<Text id="87">Collection-building differences between Windows and Linux</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="265">
+<Text id="88"><b>Windows</b></Text>
+</th>
+<th width="265">
+<Text id="89"><b>Linux</b></Text>
+</th>
+</tr>
+<tr>
+<th width="265">
+<Text id="90">Run <i>setup.bat</i> to make Greenstone programs available</Text>
+</th>
+<th width="265">
+<Text id="91">Source <i>setup.bash</i> or <i>setup.csh</i> to make programs available</Text>
+</th>
+</tr>
+<tr>
+<th width="265">
+<Text id="92">Copy files from CD-ROM using the visual manager or Windows commands</Text>
+</th>
+<th width="265">
+<Text id="93">Copy files from CD-ROM using <i>mount</i> and Unix commands</Text>
+</th>
+</tr>
+<tr>
+<th width="265">
+<Text id="94">Old collection index replaced by typing <i>rd /s index</i> then <i>ren building index</i> followed by <i>mkdir building</i>, or by using visual file manager.</Text>
+</th>
+<th width="265">
+<Text id="95">Old collection index replaced by typing <i>rm âr index/*</i> then <i>mv building/* index</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="96">You should be able to access the collection from your Greenstone homepage. You will have to reload the page if you already had it open in your browser, or perhaps even close the browser and restart it (to prevent caching problems). To view the new collection, click on the image. The result should look something like Figure <CrossRef target="Figure" ref="about_page_for_the_new_collection"/>.</Text>
+<Text id="97">In summary then, the commands typed to produced the <i>dlpeople</i> collection are:</Text>
+<CodeLine>cd ~/gsdl # assuming default Greenstone in home directory</CodeLine>
+<CodeLine>source setup.bash     # if you're running the BASH shell</CodeLine>
+<CodeLine>source setup.csh       # if you're running the C shell</CodeLine>
+<CodeLine>mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<CodeLine>cd $GSDLHOME/collect/dlpeople</CodeLine>
+<CodeLine>mount /cdrom # assuming this is where CD-ROM is mapped to</CodeLine>
+<CodeLine>cp âr /cdrom/collect/dlpeople/* import/</CodeLine>
+<CodeLine>umount /cdrom</CodeLine>
+<CodeLine>import.pl dlpeople</CodeLine>
+<CodeLine>buildcol.pl dlpeople</CodeLine>
+<CodeLine>rm -r index/*</CodeLine>
+<CodeLine>mv building/* index</CodeLine>
+</Content>
+</Subsection>
+<Subsection id="differences_between_windows_and_unix">
+<Title>
+<Text id="98">Differences between Windows and Unix</Text>
+</Title>
+<Content>
+<Text id="99">The collection building process under Unix is very similar to that under Windows, but there are some small differences which are summarised in Table <CrossRef target="Table" ref="collection-building_differences_between_windows_and_linux"/>.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="greenstone_directories">
+<Title>
+<Text id="100">Greenstone directories</Text>
+</Title>
+<Content>
+<Text id="101">Figure <CrossRef target="Figure" ref="structure_of_the_gsdlhome_directory"/> shows the structure of the <i>GSDLHOME</i> directory. Table <CrossRef target="Table" ref="where_to_find_information_about_directories"/> gives a brief description of the contents of each of the directories shown in the diagram. Some directories are more fully described in a later section of the manualâuse the section guide in Table <CrossRef target="Table" ref="where_to_find_information_about_directories"/> to see where to find more information.</Text>
+<Figure id="structure_of_the_gsdlhome_directory">
+<Title>
+<Text id="102">Structure of the <i>GSDLHOME</i> directory</Text>
+</Title>
+<File width="415" height="143" url="images/Dev_Fig_4.gif"/>
+</Figure>
+<Table id="where_to_find_information_about_directories">
+<Title>
+<Text id="103">Where to find information about directories</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="331">
+<Text id="104"><b>Contents</b></Text>
+</th>
+<th width="66">
+<Text id="105">Section</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="106"><i>bin</i></Text>
+</th>
+<th width="331">
+<Text id="107">Executable code, including binaries in the directory with your O/S name.</Text>
+</th>
+<th width="66">
+<Text id="108">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="109"><i>bin/script</i></Text>
+</th>
+<th width="331">
+<Text id="110">Perl scripts used for creating and building collections (for example <i>import.pl</i> and <i>buildcol.pl</i>). To get a description of any of these programs, type their name at the command prompt.</Text>
+</th>
+<th width="66">
+<Text id="111">1.3</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="112"><i>perllib</i></Text>
+</th>
+<th width="331">
+<Text id="113">Perl modules used at import and build time (plugins, for example).</Text>
+</th>
+<th width="66">
+<Text id="114">2.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="115"><i>perllib/plugins</i></Text>
+</th>
+<th width="331">
+<Text id="116">Perl code for document processing plugins.</Text>
+</th>
+<th width="66">
+<Text id="117">2.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="118"><i>perllib/classify</i></Text>
+</th>
+<th width="331">
+<Text id="119">Perl code for classifiers (for example the AZList code that makes a document list based on the alphabetical order of some attribute).</Text>
+</th>
+<th width="66">
+<Text id="120">2.2</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="121"><i>cgi-bin</i></Text>
+</th>
+<th width="331">
+<Text id="122">All Greenstone CGI scripts, which are moved to the system cgi-bin directory.</Text>
+</th>
+<th width="66">
+<Text id="123">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="124"><i>tmp</i></Text>
+</th>
+<th width="331">
+<Text id="125">Directory used by Greenstone for storing temporary files.</Text>
+</th>
+<th width="66">
+<Text id="126">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="127"><i>etc</i></Text>
+</th>
+<th width="331">
+<Text id="128">Configuration files, initialisation and error logs, user authorisation databases.</Text>
+</th>
+<th width="66">
+<Text id="129">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="130"><i>src</i></Text>
+</th>
+<th width="331">
+<Text id="131">C++ code used for serving collections via a web server.</Text>
+</th>
+<th width="66">
+<Text id="132">3</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="133"><i>src/colservr</i></Text>
+</th>
+<th width="331">
+<Text id="134">C++ code for serving collectionsâanswering queries and the like.</Text>
+</th>
+<th width="66">
+<Text id="135"><CrossRef target="Section" ref="protocol"/></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="136"><i>src/recpt</i></Text>
+</th>
+<th width="331">
+<Text id="137">C++ code for getting queries from the user interface and formatting query responses for the interface.</Text>
+</th>
+<th width="66">
+<Text id="138">3.9</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="139"><i>packages</i></Text>
+</th>
+<th width="331">
+<Text id="140">Source code for non-Greenstone software packages that are used by Greenstone.</Text>
+</th>
+<th width="66">
+<Text id="141">2.5</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="142"><i>packages/mg</i></Text>
+</th>
+<th width="331">
+<Text id="143">The source code for mg , the compression and indexing software used by Greenstone.</Text>
+</th>
+<th width="66">
+<Text id="144">2.5</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="145"><i>mappings</i></Text>
+</th>
+<th width="331">
+<Text id="146">Unicode translation tables (for example for the GB Chinese character set).</Text>
+</th>
+<th width="66">
+<Text id="147">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="148"><i>macros</i></Text>
+</th>
+<th width="331">
+<Text id="149">The macro files used for the user interface.</Text>
+</th>
+<th width="66">
+<Text id="150">2.4</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="151"><i>collect</i></Text>
+</th>
+<th width="331">
+<Text id="152">Collections being served from this copy of Greenstone</Text>
+</th>
+<th width="66">
+<Text id="153">1.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="154"><i>lib</i></Text>
+</th>
+<th width="331">
+<Text id="155">C++ source code used by both the collection server and the receptionist.</Text>
+</th>
+<th width="66">
+<Text id="156">3.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="157"><i>images</i></Text>
+</th>
+<th width="331">
+<Text id="158">Images used in the user interface.</Text>
+</th>
+<th width="66">
+<Text id="159">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="160"><i>docs</i></Text>
+</th>
+<th width="331">
+<Text id="161">Documentation.</Text>
+</th>
+<th width="66">
+<Text id="162">â</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Section>
+<Section id="import_and_build_processes">
+<Title>
+<Text id="163">Import and build processes</Text>
+</Title>
+<Content>
+<Text id="164">In the command-line collection-building process of Section <CrossRef target="Section" ref="building_collections_from_the_command_line"/>, one command, <i>import.pl</i>, is used for importing documents and another, <i>buildcol.pl</i>, for building the collection. Here we learn more about what these programs do and the options that they support. We use the variable <i>col_name</i> to refer to the collection being built or imported.</Text>
+<Text id="165">The import and build processes have many similarities, and as a result take many of the same options, described in Table <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/>. (Remember that to see the options for any Greenstone script you just type its name with no options at the command prompt).</Text>
+<Table id="options_for_the_import_and_build_processes">
+<Title>
+<Text id="166">Options for the <i>import</i> and <i>build</i> processes</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="104">
+<Text id="167"><b>Argument</b></Text>
+</th>
+<th width="293">
+<Text id="168"><b>Function</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="169"><i>-verbosity</i></Text>
+</th>
+<th width="104">
+<Text id="170">Number 0-3</Text>
+</th>
+<th width="293">
+<Text id="171">Control how much information about the process is printed to standard error; 0 gives a little, 3 gives lots.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="172"><i>-archivedir</i></Text>
+</th>
+<th width="104">
+<Text id="173">Directory name</Text>
+</th>
+<th width="293">
+<Text id="174">Specify where the Greenstone archive files are storedâthat is, where <i>import.pl</i> puts them and where <i>buildcol.pl</i> finds them. Defaults to <i>GSDLHOME/collect/col_name/archives</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="175"><i>-maxdocs</i></Text>
+</th>
+<th width="104">
+<Text id="176">Number &gt;0</Text>
+</th>
+<th width="293">
+<Text id="177">Indicates the maximum number of documents to be imported or built. Useful when testing a new collection configuration file, or new plugins.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="178"><i>-collectdir</i></Text>
+</th>
+<th width="104">
+<Text id="179">Directory name</Text>
+</th>
+<th width="293">
+<Text id="180">Specify where the collection can be found. Defaults to <i>GSDLHOME/collect</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="181"><i>-out</i></Text>
+</th>
+<th width="104">
+<Text id="182">Filename</Text>
+</th>
+<th width="293">
+<Text id="183">Specify a file to which to write all output messages, which defaults to standard error (the screen). Useful when working with debugging statements.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="184"><i>-keepold</i></Text>
+</th>
+<th width="104">
+<Text id="185">None</Text>
+</th>
+<th width="293">
+<Text id="186">Do not remove the result of the previous import or build operation. In the case of import, do not remove the contents of the <i>archives</i> directory; when building, do not remove the content of the <i>building</i> directory.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="187"><i>âdebug</i></Text>
+</th>
+<th width="104">
+<Text id="188">None</Text>
+</th>
+<th width="293">
+<Text id="189">Print plugin output to standard output.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Subsection id="the_import_process">
+<Title>
+<Text id="190">The import process</Text>
+</Title>
+<Content>
+<Text id="191">The import process's primary responsibility is to convert documents from their native format into the Greenstone Archive Format used within Greenstone, and write a summary file (called <i>archives.inf</i>) which will be used when the collection is built. <i>Import.pl</i> needs to know what plugins should be used, and where to find the original document files. Table <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/> shows the options common to both import and build processes; Table <CrossRef target="Table" ref="additional_options_for_the_import_process"/> shows additional options applicable to the import process only. The <i>OIDtype</i> option deserves some explanation. Each document has an associated Object Identifier or OID. This is best computed by hashing the contents of the document (<i>hash</i>). However, this is slow, so a simpler alternative (<i>incremental</i>) is provided which simply numbers the documents sequentially in the order in which they are imported. You can use <i>incremental</i> for speed, but use <i>hash</i> if you intend adding documents to your collection at a later date (without re-importing).</Text>
+<Table id="additional_options_for_the_import_process">
+<Title>
+<Text id="192">Additional options for the <i>import</i> process</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="104">
+<Text id="193"><b>Argument</b></Text>
+</th>
+<th width="293">
+<Text id="194"><b>Function</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="195"><i>-importdir</i></Text>
+</th>
+<th width="104">
+<Text id="196">Directory name</Text>
+</th>
+<th width="293">
+<Text id="197">Where material to be imported is found. Defaults to <i>GSDLHOME/collect/col_name/import</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="198"><i>-removeold</i></Text>
+</th>
+<th width="104">
+<Text id="199">None</Text>
+</th>
+<th width="293">
+<Text id="200">Remove the contents of the <i>archives</i> directory before importing.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="201"><i>-gzip</i></Text>
+</th>
+<th width="104">
+<Text id="202">None</Text>
+</th>
+<th width="293">
+<Text id="203">Zip up the Greenstone archive documents produced by <i>import</i> (ZIPPlug must be included in the plugin list, and <i>gzip</i> must be installed on your machine).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="204"><i>-groupsize</i></Text>
+</th>
+<th width="104">
+<Text id="205">Number &gt;0</Text>
+</th>
+<th width="293">
+<Text id="206">Number of documents to group together into one Greenstone archive file, defaults 1 (that is, one document per file).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="207"><i>âsortmeta</i></Text>
+</th>
+<th width="104">
+<Text id="208">Metadata tag name</Text>
+</th>
+<th width="293">
+<Text id="209">Sort the documents alphabetically by the named metadata tag. However, if the collection has more than one group in the collection (i.e. <i>groupsize</i> &gt;1), this functionality is disabled.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="210"><i>-OIDtype</i></Text>
+</th>
+<th width="104">
+<Text id="211"><i>hash</i> or <br/><i>incremental</i></Text>
+</th>
+<th width="293">
+<Text id="212">Method of creating OIDs for documents: <i>hash</i> hashes the content but is slow; <i>incremental</i> simply assigns document numbers sequentially, and is faster.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Figure id="steps_in_the_import_process">
+<Title>
+<Text id="213">Steps in the <i>import</i> process</Text>
+</Title>
+<File width="402" height="379" url="images/Dev_Fig_5.gif"/>
+</Figure>
+<Text id="214">Figure <CrossRef target="Figure" ref="steps_in_the_import_process"/> represents the import process implemented by the <i>import.pl</i> program. Each oval represents a module used to perform tasks that relate to a specific part of the Greenstone system. All these modules can be found in the <i>GSDLHOME/perllib</i> directory.</Text>
+<Text id="215">For step 3, note that import variables like <i>importdir</i> and <i>archivedir</i> can be set from the collection configuration file or from the command line. If set in the command line, any configuration file setting is ignored.</Text>
+<Text id="216">In step 6, the archives information file (<i>archives.inf</i>) is created.</Text>
+<Text id="217">Step 7 creates an object that knows where documents are to be saved, and obeys any special saving instructions (such as <i>sortmeta</i>, which sorts the documents according to a specified metadata tag).</Text>
+<Text id="218">Most of the work done in the import process is actually accomplished by plugins, which are called by the <i>plugin</i> module. This module creates a pipeline of the plugins specified in the collection configuration file. It also handles the writing of Greenstone archive documents (using a <i>document</i> object).</Text>
+</Content>
+</Subsection>
+<Subsection id="the_build_process">
+<Title>
+<Text id="219">The build process</Text>
+</Title>
+<Content>
+<Text id="220">During the building process the text is compressed, and the full-text indexes that are specified in the collection configuration file are created. Furthermore, information about how the collection is to appear on the web is precalculated and incorporated into the collectionâfor example information about icons and titles, and information produced by classifiers. <i>Buildcol.pl</i> has many options that it shares with <i>import.pl</i>, shown in Table <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/>, and some that are specific to its purpose, in Table <CrossRef target="Table" ref="additional_options_for_the_build_process"/>.</Text>
+<Table id="additional_options_for_the_build_process">
+<Title>
+<Text id="221">Additional options for the <i>build</i> process</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="104">
+<Text id="222"><b>Argument</b></Text>
+</th>
+<th width="293">
+<Text id="223"><b>Function</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="224"><i>-builddir</i></Text>
+</th>
+<th width="104">
+<Text id="225">Directory name</Text>
+</th>
+<th width="293">
+<Text id="226">Specify where the result of building is to be stored (defaults to <i>GSDLHOME/collect/col_name/building</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="227"><i>-index</i></Text>
+</th>
+<th width="104">
+<Text id="228">Index name (e.g.<br/><i>section:Title</i>)</Text>
+</th>
+<th width="293">
+<Text id="229">Specify which indexes to build. This defaults to all the indexes indicated in the collection configuration file.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="230"><i>-allclassifications</i></Text>
+</th>
+<th width="104">
+<Text id="231">None</Text>
+</th>
+<th width="293">
+<Text id="232">Prevent the build process from removing classifications that include no documents (for example, the âXâ classification in titles if there are no documents whose titles start with the letter <i>X</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="233"><i>-create_images</i></Text>
+</th>
+<th width="104">
+<Text id="234">None</Text>
+</th>
+<th width="293">
+<Text id="235">Create collection icons automatically (to use this, GIMP, and the Gimp Perl module, must be installed).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="236"><i>-mode</i></Text>
+</th>
+<th width="104">
+<Text id="237"><i>all</i>, <br/><i>compress_text</i>, <br/><i>infodb</i>, or <br/><i>build_index</i></Text>
+</th>
+<th width="293">
+<Text id="238">Determine what the build process is to do (defaults to <i>all</i>). <i>All</i> does a full build, <i>compress_text</i> only compresses the document text, <i>infodb</i> creates a database of information pertaining to the collectionâname, files, associated files, classification information and the likeâand <i>build_index</i> builds the indexes specified in the collection configuration file or on the command line.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="239"><i>âno_text</i></Text>
+</th>
+<th width="104"/>
+<th width="293">
+<Text id="240">Don't store compressed text. This option is useful for minimizing the size of the built indexes if you intend always to display the original documents at run-time.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Figure id="steps_in_the_build_process">
+<Title>
+<Text id="241">Steps in the <i>build</i> process</Text>
+</Title>
+<File width="308" height="234" url="images/Dev_Fig_6.gif"/>
+</Figure>
+<Text id="242">The diagram in Figure <CrossRef target="Figure" ref="steps_in_the_build_process"/> represents the execution of <i>buildcol.pl</i>. Many of the steps are common to the import process. The first one that is not is step 4 (to the left). This is performed only if the <i>create_images</i> option has been set. Then, the images are created and registered in the collection configuration file by a function in the <i>buildcol.pl</i> script. For this to work properly, GIMP (Gnu Image Manipulation Program), and the Gimp Perl module, must be installed and properly configured. Also, there must be write (as well as read) access to the collection configuration file.</Text>
+<Text id="243">Step 5 first checks to see whether there is a collection-specific build procedure. A few collections require special build-time processing, in which case a collection-specific builder must be written and placed in the collection's <i>perllib</i> directory, named by the collection name with âbuilderâ suffixed. Collection-specific builders are derived from <i>mgbuilder</i>. In step 5 the builder (be it the default or a collection-specific one) is initialised with information such as how many documents are to be included, whether or not the old version of the collection is to be retained, and where the <i>building</i> and <i>archive</i> directories are located.</Text>
+<Text id="244">Step 6 is the building step, in which the document text is compressed and indexed, collection titles and icons are stored in a collection information database, and data structures are built to support the classifiers that are called for in the collection's plugins. All these steps are handled by <i>mgbuilder</i> (or the collection-specific builder), which in turn uses the mg (âManaging Gigabytes,â see Witten <i>et al</i>., 1999) software for compressing and indexing.</Text>
+<Text id="245">The parts of the collection that are built can be specified by the <i>mode</i> option, but the default is to build everythingâcompressed text, indexes, and collection information database.</Text>
+<Text id="246">To make a collection available over the web once it is built, you must move it from the collection's <i>building</i> directory to the <i>index</i> directory. Collections are not built directly into <i>index</i> because large collections may take hours or days to build. It is important that the building process does not affect an existing copy of the collection until the build is complete.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="greenstone_archive_documents">
+<Title>
+<Text id="247">Greenstone archive documents</Text>
+</Title>
+<Content>
+<Text id="248">All source documents are brought into the Greenstone system by converting them to a format known as the Greenstone Archive Format. This is an XML style that marks documents into sections, and can hold metadata at the document or section level. You should not have to create Greenstone archive files manuallyâthat is the job of the document processing plugins described in the next chapter. However, it may be helpful to understand the format of Greenstone files, and so we describe it here.</Text>
+<Text id="249">In XML, tags are enclosed in angle brackets for markup. The Greenstone archive format encodes documents that are already in html, and any embedded &lt;, &gt;, or " characters within the original text ar7e escaped using the standard convention <i>&amp;lt;</i>, <i>&amp;gt;</i> and <i>&amp;quot;</i>.</Text>
+<Figure id="greenstone_archive_format">
+<Title>
+<Text id="250">Greenstone archive format: (a) Document Type Definition (DTD); (b) Example document</Text>
+<SubTitle>
+<Text id="251">(a)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;!DOCTYPE GreenstoneArchive [</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Section (Description,Content,Section*)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Description (Metadata*)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Content (#PCDATA)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Metadata (#PCDATA)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;ATTLIST Metadata name CDATA #REQUIRED&gt;</CodeLine>
+<CodeLine>]&gt;</CodeLine>
+</Figure>
+<Figure id="greenstone_archive_format_1">
+<Title>
+<Text id="252"/>
+<SubTitle>
+<Text id="253">(b)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;?xml version="1.0"?&gt;</CodeLine>
+<CodeLine>&lt;!DOCTYPE GreenstoneArchive SYSTEM</CodeLine>
+<CodeLine>"http://greenstone.org/dtd/GreenstoneArchive/1.0/GreenstoneArchive.dtd" &gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "gsdlsourcefilename"&gt;ec158e.txt&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Freshwater Resources in Arid Lands&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "Identifier"&gt;HASH0158f56086efffe592636058&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "gsdlassocfile"&gt;cover.jpg:image/jpeg:&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "gsdlassocfile"&gt;p07a.png:image/png:&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Preface&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>This is the text of the preface</i>
+</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;First and only chapter&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Part 1&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>This is the first part of the first and only chapter</i>
+</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Part 2&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>This is the second part of the first and only chapter</i>
+</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+</Figure>
+<Text id="254">Figure <CrossRef target="Figure" ref="greenstone_archive_format"/> gives the XML Document Type Definition (DTD) for the Greenstone archive format. Basically, a document is split up into <i>Sections</i>, which can be nested. Each <i>Section</i> has a <i>Description</i> that comprises zero or more <i>Metadata</i> items, and a <i>Content</i> part (which may be null)âthis is where the actual document's contents go. With each <i>Metadata</i> element is associated a name attribute (the name can be anything), and some textual data. In XML, <i>PCDATA</i> stands for âparsed character dataâ: basically text.</Text>
+<Text id="255">Figure <CrossRef target="Figure" ref="greenstone_archive_format_1"/> shows a simple document in this format, comprising a short book with two associated images. The book has two sections called <i>Preface</i> and <i>First and only chapter</i> respectively, the second of which has two subsections. Note that there is no notion of a âchapterâ as such: it is represented simply as a top-level section</Text>
+<Table id="greenstone_archive_format_values">
+<Title>
+<Text id="256">Greenstone archive format: Values for the <i>name</i> attribute of the <i>Metadata</i> tag</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="130">
+<Text id="257"><i>gsdlsourcefilename</i></Text>
+</th>
+<th width="400">
+<Text id="258">Original file from which the Greenstone archive file was generated</Text>
+</th>
+</tr>
+<tr>
+<th width="130">
+<Text id="259"><i>gsdlassocfile</i></Text>
+</th>
+<th width="400">
+<Text id="260">File associated with the document (e.g. an image file)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="261">The <i>&lt;Section&gt;</i> tag denotes the start of each document section, and the corresponding <i>&lt;/Section&gt;</i> closing tag marks the end of that section. Following each <i>&lt;Section&gt;</i> tag is a <i>&lt;Description&gt;</i> section. Within this come any number of <i>&lt;Metadata&gt;</i> elements. Thus different metadata can be associated with individual sections of a document. Most of these are for particular metadata types such as <i>&lt;Title&gt;</i>. The two values of the <i>name</i> attribute shown in Table <CrossRef target="Table" ref="greenstone_archive_format_values"/> are treated specially by Greenstone; all others are considered to be metadata that is attached to that section.</Text>
+<Text id="262">In some collections documents are split into individual pages. These are treated as sections. For example, a book might have first-level sections that correspond to chapters, within each of which are defined a number of âsectionsâ that actually correspond to the individual pages of the chapter.</Text>
+<Subsection id="document_metadata">
+<Title>
+<Text id="263">Document metadata</Text>
+</Title>
+<Content>
+<Text id="264">Metadata is descriptive information such as author, title, date, keywords, and so on, that is associated with a document. It has already been mentioned that metadata is stored with documents. Looking at Figure <CrossRef target="Figure" ref="greenstone_archive_format"/>, you can see that <i>&lt;Metadata&gt;</i> tags specify the name of the metadata type, and give a value for that metadata. One example is the line <i>&lt;Metadata name="Title"&gt;First and only chapter&lt;/Metadata&gt;</i> in Figure <CrossRef target="Figure" ref="greenstone_archive_format_1"/>âthe title of a document is a piece of metadata associated with it. The Dublin Core metadata standard is used for defining metadata types (Dublin Core, 2001; Weibel, 1999; Thiele, 1997).</Text>
+<Text id="265">Table <CrossRef target="Table" ref="dublin_core_metadata_standard"/> shows what types are available in the standardâstarred entries are used in collections available from the New Zealand Digital Library web site today. If there is no type that aptly describes a particular kind of metadata, metadata types that are not in the Dublin Core may be used too. For example, the Demo collection contains <i>how to</i> and <i>Magazine</i> metadata.</Text>
+<Table id="dublin_core_metadata_standard">
+<Title>
+<Text id="266">Dublin Core metadata standard</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="133">
+<Text id="267"><b>Name</b></Text>
+</th>
+<th width="94">
+<Text id="268"><b>Metadata <br/>subtag</b></Text>
+</th>
+<th width="305">
+<Text id="269"><b>Definition</b></Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="270">*Title</Text>
+</th>
+<th width="94">
+<Text id="271">Title</Text>
+</th>
+<th width="305">
+<Text id="272">A name given to the resource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="273">*Creator</Text>
+</th>
+<th width="94">
+<Text id="274"><i>Creator</i></Text>
+</th>
+<th width="305">
+<Text id="275">An entity primarily responsible for making the content of the resource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="276">*Subject and keywords</Text>
+</th>
+<th width="94">
+<Text id="277"><i>Subject</i></Text>
+</th>
+<th width="305">
+<Text id="278">The topic of the content of the resource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="279">*Description</Text>
+</th>
+<th width="94">
+<Text id="280"><i>Description</i></Text>
+</th>
+<th width="305">
+<Text id="281">An account of the content of the resource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="282">*Publisher</Text>
+</th>
+<th width="94">
+<Text id="283"><i>Publisher</i></Text>
+</th>
+<th width="305">
+<Text id="284">An entity responsible for making the resource available</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="285">Contributor</Text>
+</th>
+<th width="94">
+<Text id="286"><i>Contributor</i></Text>
+</th>
+<th width="305">
+<Text id="287">An entity responsible for making contributions to the content of the resource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="288">*Date</Text>
+</th>
+<th width="94">
+<Text id="289"><i>Date</i></Text>
+</th>
+<th width="305">
+<Text id="290">The date that the resource was published or some other important date associated with the resource.</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="291">Resource type</Text>
+</th>
+<th width="94">
+<Text id="292"><i>Type</i></Text>
+</th>
+<th width="305">
+<Text id="293">The nature or genre of the content of the resource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="294">Format</Text>
+</th>
+<th width="94">
+<Text id="295"><i>Format</i></Text>
+</th>
+<th width="305">
+<Text id="296">The physical or digital manifestation of the resource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="297">*Resource identifier</Text>
+</th>
+<th width="94">
+<Text id="298"><i>Identifier</i></Text>
+</th>
+<th width="305">
+<Text id="299">An unambiguous reference to the resource within a given context: this is the object identifier or OID</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="300">*Source</Text>
+</th>
+<th width="94">
+<Text id="301"><i>Source</i></Text>
+</th>
+<th width="305">
+<Text id="302">A reference to a resource from which the present resource is derived</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="303">*Language</Text>
+</th>
+<th width="94">
+<Text id="304"><i>Language</i></Text>
+</th>
+<th width="305">
+<Text id="305">A language of the intellectual content of the resource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="306">Relation</Text>
+</th>
+<th width="94">
+<Text id="307"><i>Relation</i></Text>
+</th>
+<th width="305">
+<Text id="308">A reference to a related resource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="309">*Coverage</Text>
+</th>
+<th width="94">
+<Text id="310"><i>Coverage</i></Text>
+</th>
+<th width="305">
+<Text id="311">The extent or scope of the content of the resource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="312">Rights management</Text>
+</th>
+<th width="94">
+<Text id="313"><i>Rights</i></Text>
+</th>
+<th width="305">
+<Text id="314">Information about rights held in and over the resource</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="inside_greenstone_archive_documents">
+<Title>
+<Text id="315">Inside Greenstone archive documents</Text>
+</Title>
+<Content>
+<Text id="316">Within a single document, the Greenstone archive format imposes a limited amount of structure. Documents are divided into paragraphs. They can be split hierarchically into sections and subsections; these may be nested to any depth. Each document has an associated Object Identifier or OIDâthese are extended to identify sections and subsections by appending section and subsection numbers, separated by periods, to the document's OID. For example, subsection 3 of section 2 of document HASHa7 is referred to as HASHa7.2.3.</Text>
+<Text id="317">When you read a book in a Greenstone collection, the section hierarchy is manifested in the table of contents of the book. For example, books in the Demo collection have a hierarchical table of contents showing chapters, sections, and subsections, as illustrated in Figure <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection"/>. Documents in the Computer Science Technical Reports collection do not have a hierarchical subsection structure, but each document is split into pages and you can browse around the pages of a retrieved document. Chapters, sections, subsections, and pages are all implemented simply as âsectionsâ within the document.</Text>
+<Figure id="hierarchical_structure_in_the_demo_collection">
+<Title>
+<Text id="318">Hierarchical structure in the Demo collection</Text>
+<SubTitle>
+<Text id="318a">(a)</Text>
+</SubTitle>
+</Title>
+<File width="373" height="251" url="images/Dev_Fig_8a.gif"/>
+</Figure>
+<Figure id="hierarchical_structure_in_the_demo_collection_1">
+<Title>
+<Text id="318b">Hierarchical structure in the Demo collection</Text>
+<SubTitle>
+<Text id="318c">(b)</Text>
+</SubTitle>
+</Title>
+<File width="373" height="251" url="images/Dev_Fig_8b.gif"/>
+</Figure>
+<Text id="319">The document structure is also used for searchable indexes. There are three possible levels of index: <i>document</i>, <i>section</i>, and <i>paragraph</i>, though most collections do not use all three levels. A <i>document</i> index contains the full documentâyou use it to find all documents that contain a particular set of words (the words may be scattered far and wide throughout the document). When a <i>section</i> index is created, each portion of text that is indexed stretches from a <i>&lt;Section&gt;</i> tag to the next-occurring <i>&lt;Section&gt;</i> tagâthus a chapter that immediately begins with a new section will produce an empty document in the index. Sections and subsections are treated alike: the hierarchical document structure is flattened for the purposes of creating searchable indexes. Paragraph-level indexes consider each paragraph as a separate document, and are useful for doing more focused searches.</Text>
+<Text id="320">The pulldown menu in Figure <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection_1"/> shows the searchable indexes for the Demo collection. âChaptersâ and âsection titlesâ are section-level indexes, while âentire booksâ is a document-level index. As well as indexes of text, indexes of any kind of metadata can also be created. For example, some collections offer searchable indexes of section titles, and Figure <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection_1"/> illustrates this.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="configuration_file">
+<Title>
+<Text id="321">configuration file</Text>
+</Title>
+<Content>
+<Text id="322">The collection configuration file governs the structure of a collection as seen by the user, allowing you to customise the âlook and feelâ of your collection and the way in which its documents are processed and presented. A simple collection configuration file is created when you run <i>mkcol.pl</i>, which records your E-mail address as the creator and maintainer. Remember from the earlier walkthrough that the <i>creator</i> argument is mandatoryâunless specified separately, the same information is recorded as the maintainer.</Text>
+<Table id="items_in_the_collection_configuration_file">
+<Title>
+<Text id="323">Items in the collection configuration file</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<CodeLine>creator</CodeLine>
+</th>
+<th width="397">
+<Text id="324">E-mail address of the collection's creator</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>maintainer</i></CodeLine>
+</th>
+<th width="397">
+<Text id="325">E-mail address of the collection's maintainer</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>public</i></CodeLine>
+</th>
+<th width="397">
+<Text id="326">Whether collection is to be made public or not</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>beta</i></CodeLine>
+</th>
+<th width="397">
+<Text id="327">Whether collection is beta version or not</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>indexes</i></CodeLine>
+</th>
+<th width="397">
+<Text id="328">List of indexes to build</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>defaultindex</i></CodeLine>
+</th>
+<th width="397">
+<Text id="329">The default index</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>subcollection</i></CodeLine>
+</th>
+<th width="397">
+<Text id="330">Define a subcollection based on metadata</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>indexsubcollections</i></CodeLine>
+</th>
+<th width="397">
+<Text id="331">Specify which subcollections to index</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>defaultsubcollection</i></CodeLine>
+</th>
+<th width="397">
+<Text id="332">The default indexsubcollection</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>languages</i></CodeLine>
+</th>
+<th width="397">
+<Text id="333">List of languages to build indexes in</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>defaultlanguage</i></CodeLine>
+</th>
+<th width="397">
+<Text id="334">Default index language</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>collectionmeta</i></CodeLine>
+</th>
+<th width="397">
+<Text id="335">Defines collection-level metadata</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>plugin</i></CodeLine>
+</th>
+<th width="397">
+<Text id="336">Specify a plugin to use at build time</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>format</i></CodeLine>
+</th>
+<th width="397">
+<Text id="337">A format string (explained below)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>classify</i></CodeLine>
+</th>
+<th width="397">
+<Text id="338">Specify a classifier to use at build time</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="339">Each line of the collection configuration file is essentially an âattribute, valueâ pair. Each attribute gives a piece of information about the collection that affects how it is supposed to look or how documents are to be processed. Table <CrossRef target="Table" ref="items_in_the_collection_configuration_file"/> shows the items that can be included in a collection configuration file, and what each is used for. As well as these, all the command-line options for <i>import.pl</i> and <i>buildcol.pl</i> may be specified in a collection configuration fileâe.g. a line reading <i>no_text true</i> will set <i>buildcol.pl</i>'s <i>no_text</i> option.</Text>
+<Text id="340">The collection configuration file created by the <i>mkcol.pl</i> script, shown in Table <CrossRef target="Table" ref="collection_configuration_file_created_by_mkcd"/>, is a very simple one and contains a bare minimum of information. Lines 1 and 2 stem from the <i>creator</i> value supplied to the <i>mkcol.pl</i> program, and contain the E-mail addresses of the person who created the collection and the person responsible for maintaining it (not necessarily the same person).</Text>
+<Table id="collection_configuration_file_created_by_mkcd">
+<Title>
+<Text id="341">Collection configuration file created by <i>mkcd.pl</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="342"><b>Attribute</b></Text>
+</th>
+<th width="265">
+<Text id="343"><b>Value</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>1</CodeLine>
+</th>
+<th width="132">
+<CodeLine>creator</CodeLine>
+</th>
+<th width="265">
+<Text id="344">username@email.com</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>2</CodeLine>
+</th>
+<th width="132">
+<CodeLine>maintainer</CodeLine>
+</th>
+<th width="265">
+<Text id="345">username@email.com</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>3</CodeLine>
+</th>
+<th width="132">
+<CodeLine>public</CodeLine>
+</th>
+<th width="265">
+<Text id="346">True</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>4</CodeLine>
+</th>
+<th width="132">
+<CodeLine>beta</CodeLine>
+</th>
+<th width="265">
+<Text id="347">True</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>5</CodeLine>
+</th>
+<th width="132">
+<CodeLine>indexes</CodeLine>
+</th>
+<th width="265">
+<Text id="348">document:text</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>6</CodeLine>
+</th>
+<th width="132">
+<CodeLine>defaultindex</CodeLine>
+</th>
+<th width="265">
+<Text id="349">document:text</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>7</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="350">ZIPPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>8</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="351">GAPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>9</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="352">TextPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>10</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="353">HTMLPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>11</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="354">EMAILPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>12</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="355">ArcPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>13</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="356">RecPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>14</CodeLine>
+</th>
+<th width="132">
+<CodeLine>classify</CodeLine>
+</th>
+<th width="265">
+<Text id="357">AZList metadata Title</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>15</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="358">collectionname       "sample collection"</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>16</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="359">iconcollection       ""</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>17</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="360">collectionextra     ""</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>18</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="361">.document:text     "documents"</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="362">Line 3 indicates whether the collection will be available to the public when it is built, and is either <i>true</i> (the default, meaning that the collection is publicly available), or <i>false</i> (meaning that it is not). This is useful when building collections to test software, or building collections of material for personal use. Line 4 indicates whether the collection is beta or not (this also defaults to <i>true</i>, meaning that the collection is a beta release).</Text>
+<Text id="363">Line 5 determines what collection indexes are created at build time: in this example only the document text is to be indexed. Indexes can be constructed at the <i>document</i>, <i>section</i>, and <i>paragraph</i> levels. They can contain the material in <i>text</i>, or in any metadataâmost commonly <i>Title</i>. The form used to specify an index is <i>level:data</i>. For example, to include an index of section titles as well, you should change line 5 to <i>indexes document:text section:Title</i>. More than one type of data can be included in the same index by separating the data types with commas. For example, to create a section-level index of titles, text and dates, the line should read <i>indexes section:text,Title,Date.</i> The default index defined in line 6 is the default to be used on the collection's search page.</Text>
+<Text id="364">Lines 7â13 specify which plugins to use when converting documents to the Greenstone archive format and when building collections from archive files. Section <CrossRef target="Section" ref="plugins"/> gives information about what plugins are available. The order in which plugins are listed is the order in which they are tried on each document, and once a plugin that is able to process a document is found, no more are tried.</Text>
+<Text id="365">Line 14 specifies that an alphabetic list of titles is to be created for browsing purposes. Browsing structures are constructed by âclassifiersâ. Section <CrossRef target="Section" ref="classifiers"/> gives information about classifiers and what they can do.</Text>
+<Text id="366">Lines 15â18 are used to specify collection-level metadata. Specified through <i>collectionname</i>, the long form of the name is used as the collection's âtitleâ for the web browser. The <i>collectionicon</i> entry gives the URL of the collection's icon. If an index is specified (as in line 18), the string following is displayed as the name of that index on the collection's search page. A particularly important piece of collection-level metadata is <i>collectionextra</i>, which gives a stretch of text, surrounded by double quotes, describing the collection. This will be shown as the âAbout this collectionâ text. You can put in different versions of <i>collectionextra</i> for different interface languages by adding a language specification in square brackets. For example,</Text>
+<Indented>
+<Text id="367">collectionmeta collectionextra "collection description"</Text>
+</Indented>
+<Indented>
+<Text id="368">collectionmeta collectionextra [l=fr] "description in French"</Text>
+</Indented>
+<Indented>
+<Text id="369">collectionmeta collectionextra [l=mi] "description in Maori"</Text>
+</Indented>
+<Text id="370">If the interface language is set to âfrâ or âmiâ, the appropriate version of the description will be displayed. For other languages the default version will appear.</Text>
+<Text id="371">This simple collection configuration file does not include any examples of format strings, nor of the subcollection and language facilities provided by the configuration file. Format strings are covered more thoroughly in Section <CrossRef target="Section" ref="formatting_greenstone_output"/>, but we will look at subcollections and languages here.</Text>
+<Subsection id="subcollections">
+<Title>
+<Text id="372">Subcollections</Text>
+</Title>
+<Content>
+<Text id="373">Greenstone allows you to define subcollections and build separate indexes for each one. For example, in one collection there is a large subset of documents called <i>Food and Nutrition Bulletin</i>. We use this collection as an example.</Text>
+<Text id="374">This collection has three indexes, all at the section level: one for the whole collection, one for the <i>Food and Nutrition Bulletin</i>, and the third for the remaining documents. The relevant lines from the collection configuration file can be seen below.</Text>
+<CodeLine>indexes                           section:text</CodeLine>
+<CodeLine>subcollection               fn "Title/^Food and Nutrition Bulletin/i "</CodeLine>
+<CodeLine>subcollection               other "!Title/^Food and Nutrition Bulletin/i "</CodeLine>
+<CodeLine>indexsubcollections fn   other   fn,other</CodeLine>
+<Text id="375">The second and third lines define subcollections called <i>fn</i>, which contains the <i>Food and Nutrition Bulletin</i> documents, and <i>other</i>, which contains the remaining documents. The third field of these definitions is a Perl regular expression that identifies these subsets using the <i>Title</i> metadata: we seek titles that begin with <i>Food and Nutrition Bulletin</i> in the first case and ones that do not in the second case (note the â!â). The final <i>i</i> makes the pattern-matching case-insensitive. The metadata field, in this case <i>Title</i>, can be any valid field, or <i>Filename</i> to match against the document's original filename. The fourth line, <i>indexsubcollections</i>, specifies three indexes: one for the <i>fn</i> subcollection, one for the <i>other</i> subcollection, and the third for both subcollections (i.e. all the documents). Note that if two entries had been specified on the <i>indexes</i> line, the total number of indexes generated would have been six rather than three.</Text>
+<Text id="376">If a collection contains documents in different languages, separate indexes can be built for each language. Language is a metadata statement; values are specified using the ISO 639 standard two-letter codes for representing the names of languagesâfor example, <i>en</i> is English, <i>zh</i> is Chinese, and <i>mi</i> is Maori. Since metadata values can be specified at the section level, parts of a document can be in different languages.</Text>
+<Text id="377">For example, if the configuration file contained</Text>
+<CodeLine>indexes section:text section:Title document:text paragraph:text</CodeLine>
+<CodeLine>languages en zh mi</CodeLine>
+<Text id="378">section text, section title, document text, and paragraph text indexes would be created for English, Chinese, and Maoriâtwelve indexes altogether. Adding a couple of subcollections multiplies the number of indexes again. Care is necessary to guard against index bloat.</Text>
+<Text id="379">(This index specification could be defined using the <i>subcollection</i> facility rather than the <i>languages</i> facility. However, since the syntax precludes creating subcollections of subcollections, it would then be impossible to index each language in the subcollections separately.)</Text>
+</Content>
+</Subsection>
+<Subsection id="cross-collection_searching">
+<Title>
+<Text id="380">Cross-collection searching</Text>
+</Title>
+<Content>
+<Text id="381">Greenstone has a facility for âcross-collection searching,â which allows several collections to be searched at once, with the results combined behind the scenes as though you were searching a single unified collection. Any subset of the collections can be searched: the Preferences page allows you to choose which collections are included in the searches.</Text>
+<Text id="382">Cross-collection searching is enabled by a line</Text>
+<CodeLine>supercollection col _1 col _2 âŠ.</CodeLine>
+<Text id="383">where the collections involved are called <i>col_1</i>, <i>col_2</i>, âŠ The same line should appear in the configuration file of every collection that is involved.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="getting_the_most_out_of_your_documents">
+<Title>
+<Text id="384">Getting the most out of your documents</Text>
+</Title>
+<Content>
+<Text id="385">Collections can be individualised to make the information they contain accessible in different ways. This chapter describes how Greenstone extracts information from documents and presents it to the user: the document processing (Section <CrossRef target="Section" ref="plugins"/>) and classification structures (Section <CrossRef target="Section" ref="classifiers"/>), and user interface tools (Sections <CrossRef target="Section" ref="formatting_greenstone_output"/> and <CrossRef target="Section" ref="controlling_the_greenstone_user_interface"/>).</Text>
+<Section id="plugins">
+<Title>
+<Text id="386">Plugins</Text>
+</Title>
+<Content>
+<Text id="387">Plugins parse the imported documents and extract metadata from them. For example, the html plugin converts html pages to the Greenstone archive format and extracts metadata which is explicit in the document formatâsuch as titles, enclosed by <i>&lt;title&gt;&lt;/title&gt;</i> tags.</Text>
+<Text id="388">Plugins are written in the Perl language. They all derive from a basic plugin called <i>BasPlug</i>, which performs universally-required operations like creating a new Greenstone archive document to work with, assigning an object identifier (OID), and handling the sections in a document. Plugins are kept in the <i>perllib/plugins</i> directory.</Text>
+<Text id="389">To find more about any plugin, just type <i>pluginfo.pl plugin-name</i> at the command prompt. (You need to invoke the appropriate <i>setup</i> script first, if you haven't already, and on Windows you need to type <i>perl âS pluginfo.pl plugin-name</i> if your environment is not set up to associate files ending in <i>.pl</i> as Perl executables). This displays information about the plugin on the screenâwhat plugin-specific options it takes, and what general options are allowed.</Text>
+<Text id="390">You can easily write new plugins that process document formats not handled by existing plugins, format documents in some special way, or extract a new kind of metadata.</Text>
+<Subsection id="general_options">
+<Title>
+<Text id="391">General Options</Text>
+</Title>
+<Content>
+<Text id="392">Table <CrossRef target="Table" ref="options_applicable_to_all_plugins"/> shows options that are accepted by any plugin derived from BasPlug.</Text>
+<Table id="options_applicable_to_all_plugins">
+<Title>
+<Text id="393">Options applicable to all plugins</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<CodeLine><i>input_encoding</i></CodeLine>
+</th>
+<th width="397">
+<Text id="394">Character encoding of the source documents. The default is to automatically work out the character encoding of each individual document. It is sometimes useful to set this value though, for example, if you know that all your documents are plain ASCII, setting the input encoding to <i>ascii</i> greatly increases the speed at which your collection is imported and built. There are many possible values. Use <i>pluginfo.pl BasPlug</i> to get a complete list.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>default_encoding</i></CodeLine>
+</th>
+<th width="397">
+<Text id="395">The encoding that is used if <i>input_encoding</i> is <i>auto</i> and automatic encoding detection fails.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>process_exp</i></CodeLine>
+</th>
+<th width="397">
+<Text id="396">A Perl regular expression to match against filenames (for example, to locate a certain kind of file extension). This dictates which files a plugin processes. Each plugin has a default (<i>HTMLPlug</i>'s default is <i>(?i).html?</i>âthat is, anything with the extension <i>.htm</i> or <i>.html</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>block_exp</i></CodeLine>
+</th>
+<th width="397">
+<Text id="397">A regular expression to match against filenames that are not to be passed on to subsequent plugins. This can prevent annoying error messages about files you aren't interested in. Some plugins have default blocking expressionsâfor example, <i>HTMLPlug</i> blocks files with <i>.gif</i>, <i>.jpg</i>, <i>.jpeg</i>, <i>.png</i>, <i>.rtf</i> and <i>.css</i> extensions.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>cover_image</i></CodeLine>
+</th>
+<th width="397">
+<Text id="398">Look for a <i>.jpg</i> file (with the same name as the file being processed) and associate it with the document as a cover image.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_acronyms</i></CodeLine>
+</th>
+<th width="397">
+<Text id="399">Extract acronyms from documents and add them as metadata to the corresponding Greenstone archive documents.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>markup_acronyms</i></CodeLine>
+</th>
+<th width="397">
+<Text id="400">Add acronym information into document text.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_language</i></CodeLine>
+</th>
+<th width="397">
+<Text id="401">Identify each document's language and associate it as metadata. Note that this is done automatically if <i>input_encoding</i> is <i>auto</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>default_language</i></CodeLine>
+</th>
+<th width="397">
+<Text id="402">If automatic language extraction fails, language metadata is set to this value.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>first</i></CodeLine>
+</th>
+<th width="397">
+<Text id="403">Extract a comma-separated list of the first stretch of text and add it as <i>FirstNNN</i> metadata (often used as a substitute for <i>Title</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_email</i></CodeLine>
+</th>
+<th width="397">
+<Text id="404">Extract E-mail addresses and add them as document metadata.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_date</i></CodeLine>
+</th>
+<th width="397">
+<Text id="405">Extract dates relating to the content of historical documents and add them as <i>Coverage</i> metadata.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="document_processing_plugins">
+<Title>
+<Text id="406">Document processing plugins</Text>
+</Title>
+<Content>
+<Table id="greenstone_plugins">
+<Title>
+<Text id="407">Greenstone plugins</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="60"/>
+<th width="72"/>
+<th width="236">
+<Text id="408"><b>Purpose</b></Text>
+</th>
+<th width="85">
+<Text id="409"><b>File types</b></Text>
+</th>
+<th width="76">
+<Text id="410"><b>Ignores files</b></Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="411"><b>General</b></Text>
+</th>
+<th width="72">
+<Text id="412"><i>ArcPlug</i></Text>
+</th>
+<th width="236">
+<Text id="413">Processes files named in the file <i>archives.inf</i>, which is used to communicate between the import and build processes. Must be included (unless <i>import.pl</i> will not be used).</Text>
+</th>
+<th width="85">
+<Text id="414"><i>â</i></Text>
+</th>
+<th width="76">
+<Text id="415"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="416"><i>RecPlug</i></Text>
+</th>
+<th width="236">
+<Text id="417">Recurses through a directory structure by checking to see whether a filename is a directory and if so, inserting all files in the directory into the plugin pipeline. Assigns metadata if <i>âuse_metadata_files</i> option is set and <i>metadata.xml</i> files are present.</Text>
+</th>
+<th width="85">
+<Text id="418"><i>â</i></Text>
+</th>
+<th width="76">
+<Text id="419"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="420"><i>GAPlug</i></Text>
+</th>
+<th width="236">
+<Text id="421">Processes Greenstone archive files generated by <i>import.pl.</i> Must be included (unless <i>import.pl</i> will not be used).</Text>
+</th>
+<th width="85">
+<Text id="422"><i>.xml</i></Text>
+</th>
+<th width="76">
+<Text id="423"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="424">TEXTPlug</Text>
+</th>
+<th width="236">
+<Text id="425">Processes plain text by placing it between <i>&lt;pre&gt; &lt;/pre&gt;</i> tags (treating it as preformatted).</Text>
+</th>
+<th width="85">
+<Text id="426"><i>.txt, .text</i></Text>
+</th>
+<th width="76">
+<Text id="427"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="428"><i>HTMLPlug</i></Text>
+</th>
+<th width="236">
+<Text id="429">Processes html, replacing hyperlinks appropriately. If the linked document is not in the collection, an intermediate page is inserted warning the user they are leaving the collection. Extracts readily available metadata such as <i>Title</i>.</Text>
+</th>
+<th width="85">
+<Text id="430"><i>.htm, .html, .cgi, .php, .asp, .shm, .shtml</i></Text>
+</th>
+<th width="76">
+<Text id="431"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="432"><i>WordPlug</i></Text>
+</th>
+<th width="236">
+<Text id="433">Processes Microsoft Word documents, extracting author and title where available, and keeping diagrams and pictures in their proper places. The conversion utilities used by this plugin sometimes produce html that is poorly formatted, and we recommend that you provide the original documents for viewing when building collections of WORD files. However, the text that is extracted from the documents is adequate for searching and indexing purposes.</Text>
+</th>
+<th width="85">
+<Text id="434"><i>.doc</i></Text>
+</th>
+<th width="76">
+<Text id="435"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="436"><i>PDFPlug</i></Text>
+</th>
+<th width="236">
+<Text id="437">Processes PDF documents, extracting the first line of text as a title. The <i>pdftohtml</i> program fails on some PDF files. What happens is that the conversion process takes an exceptionally long time, and often an error message relating to the conversion process appears on the screen. If this occurs, the only solution that we can offer is to remove the offending document from the collection and re-import.</Text>
+</th>
+<th width="85">
+<Text id="438"><i>.pdf</i></Text>
+</th>
+<th width="76">
+<Text id="439"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="440"><i>PSPlug</i></Text>
+</th>
+<th width="236">
+<Text id="441">Processes PostScript documents, optionally extracting date, title and page number metadata.</Text>
+</th>
+<th width="85">
+<Text id="442"><i>.ps</i></Text>
+</th>
+<th width="76">
+<Text id="443"><i>.eps</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="444"><i>EMAILPlug</i></Text>
+</th>
+<th width="236">
+<Text id="445">Processes E-mail messages, recognising author, subject, date, etc. This plugin does not yet handle MIME-encoded E-mails propoerlyâalthough legible, they often look rather strange.</Text>
+</th>
+<th width="85">
+<Text id="446">Must end in digits or digits followed by <i>.Email</i></Text>
+</th>
+<th width="76">
+<Text id="447"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="448"><i>BibTexPlug</i></Text>
+</th>
+<th width="236">
+<Text id="449">Processes bibliography files in <i>BibTex</i> format</Text>
+</th>
+<th width="85">
+<Text id="450"><i>.bib</i></Text>
+</th>
+<th width="76">
+<Text id="451"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="452"><i>ReferPlug</i></Text>
+</th>
+<th width="236">
+<Text id="453">Processes bibliography files in <i>refer</i> format</Text>
+</th>
+<th width="85">
+<Text id="454"><i>.bib</i></Text>
+</th>
+<th width="76">
+<Text id="455"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="456"><i>SRCPlug</i></Text>
+</th>
+<th width="236">
+<Text id="457">Processes source code files</Text>
+</th>
+<th width="85">
+<Text id="458"><i>Makefile, Readme, .c, .cc, .cpp, .h, .hpp, .pl, .pm, .sh</i></Text>
+</th>
+<th width="76">
+<Text id="459"><i>.o, .obj, .a, .so, .dll</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="460"><i>ImagePlug</i></Text>
+</th>
+<th width="236">
+<Text id="461">Processes image files for creating a library of images. Only works on UNIX.</Text>
+</th>
+<th width="85">
+<Text id="462"><i>.jpeg, .jpg, .gif, .png, .bmp, .xbm, .tif, .tiff</i></Text>
+</th>
+<th width="76">
+<Text id="463"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="464"><i>SplitPlug</i></Text>
+</th>
+<th width="236">
+<Text id="465">Like BasPlug and ConvertToPlug, this plugin should not be called directly, but may be inherited byplugins that need to process files containing several documents</Text>
+</th>
+<th width="85">
+<Text id="466"><i>â</i></Text>
+</th>
+<th width="76">
+<Text id="467"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="468"><i>FOXPlug</i></Text>
+</th>
+<th width="236">
+<Text id="469">Processes FoxBASE dbt files</Text>
+</th>
+<th width="85">
+<Text id="470"><i>.dbt, .dbf</i></Text>
+</th>
+<th width="76">
+<Text id="471"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="472"><i>ZIPPlug</i></Text>
+</th>
+<th width="236">
+<Text id="473">Uncompresses <i>gzip</i>, <i>bzip</i>, <i>zip</i>, and <i>tar</i> files, provided the appropriate Gnu tools are available.</Text>
+</th>
+<th width="85">
+<Text id="474"><i>.gzip, .bzip, .zip, .tar, .gz, .bz, .tgz, .taz</i></Text>
+</th>
+<th width="76">
+<Text id="475"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="476"><b>Collection <br/>Specific</b></Text>
+</th>
+<th width="72">
+<Text id="477"><i>PrePlug</i></Text>
+</th>
+<th width="236">
+<Text id="478">Processes html output using PRESCRIPT, splitting documents into pages for the Computer Science Technical Reports collection.</Text>
+</th>
+<th width="85">
+<Text id="479"><i>.html, .html.gz</i></Text>
+</th>
+<th width="76">
+<Text id="480"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="481"><i>GBPlug</i></Text>
+</th>
+<th width="236">
+<Text id="482">Processes Project Gutenberg etextâwhich includes manually-entered title information.</Text>
+</th>
+<th width="85">
+<Text id="483"><i>.txt.gz, .html, .htm</i></Text>
+</th>
+<th width="76">
+<Text id="484"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="485"><i>TCCPlug</i></Text>
+</th>
+<th width="236">
+<Text id="486">Processes E-mail documents from Computists' Weekly</Text>
+</th>
+<th width="85">
+<Text id="487">Must begin with <i>tcc or cw</i></Text>
+</th>
+<th width="76">
+<Text id="488"><i>â</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="489">Document processing plugins are used by the collection-building software to parse each source document in a way that depends on its format. A collection's configuration file lists all plugins that are used when building it. During the import operation, each file or directory is passed to each plugin in turn until one is found that can process itâthus earlier plugins take priority over later ones. If no plugin can process the file, a warning is printed (to standard error) and processing passes to the next file. (This is where the <i>block_exp</i> option can be usefulâto prevent these error messages for files that might be present but don't need processing.) During building, the same procedure is used, but the <i>archives</i> directory is processed instead of the <i>import</i> directory.</Text>
+<Text id="490">The standard Greenstone plugins are listed in Table <CrossRef target="Table" ref="greenstone_plugins"/>. Recursion is necessary to traverse directory hierarchies. Although the import and build programs do not perform explicit recursion, some plugins cause indirect recursion by passing files or directory names into the plugin pipeline. For example, the standard way of recursing through a directory hierarchy is to specify <i>RecPlug</i>, which does exactly this. If present, it should be the last element in the pipeline. Only the first two plugins in Table <CrossRef target="Table" ref="greenstone_plugins"/> cause indirect recursion.</Text>
+<Text id="491">Some plugins are written for specific collections that have a document format not found elsewhere, like the E-text used in the Gutenberg collection. These collection-specific plugins are found in the collection's <i>perllib/plugins</i> directory. Collection-specific plugins can be used to override general plugins with the same name.</Text>
+<Text id="492">Some document-processing plugins use external programs that parse specific proprietary formatsâfor example, Microsoft Wordâinto either plain text or html. A general plugin called <i>ConvertToPlug</i> invokes the appropriate conversion program and passes the result to either <i>TEXTPlug</i> or <i>HTMLPlug</i>. We describe this in more detail shortly.</Text>
+<Text id="493">Some plugins have individual options, which control what they do in finer detail than the general options allow. Table <CrossRef target="Table" ref="plugin-specific_options"/> describes them.</Text>
+<Table id="plugin-specific_options">
+<Title>
+<Text id="494">Plugin-specific options</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="495"><b>Option</b></Text>
+</th>
+<th width="265">
+<Text id="496"><b>Purpose</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="497"><i>HTMLPlug</i></Text>
+</th>
+<th width="132">
+<Text id="498"><i>nolinks</i></Text>
+</th>
+<th width="265">
+<Text id="499">Do not trap links within the collection. This speeds up the import/build process, but any links in the collection will be broken.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="500"><i>description_tags</i></Text>
+</th>
+<th width="265">
+<Text id="501">Interpret tagged document files as described in the subsection below.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="502"><i>keep_head</i></Text>
+</th>
+<th width="265">
+<Text id="503">Do not strip out html headers.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="504"><i>no_metadata</i></Text>
+</th>
+<th width="265">
+<Text id="505">Do not seek any metadata (this may speed up the import/build process).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="506"><i>metadata_fields</i></Text>
+</th>
+<th width="265">
+<Text id="507">Takes a comma-separated list of metadata types (defaults to <i>Title</i>) to extract. To rename the metadata in the Greenstone archive file, use <i>tag&lt;newname&gt;</i> where <i>tag</i> is the html tag sought and <i>newname</i> its new name.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="508"><i>hunt_creator_metadata</i></Text>
+</th>
+<th width="265">
+<Text id="509">Find as much metadata as possible about authorship and put it in the Greenstone archive document as <i>Creator</i> metadata. You also need to include <i>Creator</i> using the <i>metadata_fields</i> option.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="510"><i>file_is_url</i></Text>
+</th>
+<th width="265">
+<Text id="511">Use this option if a web mirroring program has been used to create the structure of the documents to be imported.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="512"><i>assoc_files</i></Text>
+</th>
+<th width="265">
+<Text id="513">Gives a Perl regular expression that describes file types to be treated as associated files. The default types are <i>.jpg</i>, <i>.jpeg</i>, <i>.gif</i>, <i>.png</i>, <i>.css</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="514"><i>rename_assoc_files</i></Text>
+</th>
+<th width="265">
+<Text id="515">Rename files associated with documents. During this process the directory structure of any associated files will become much shallower (useful if a collection must be stored in limited space).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="516"><i>HTMLPlug</i> and <br/><i>TEXTPlug</i></Text>
+</th>
+<th width="132">
+<Text id="517"><i>title_sub</i></Text>
+</th>
+<th width="265">
+<Text id="518">Perl substitution expression to modify titles.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="519"><i>PSPlug</i></Text>
+</th>
+<th width="132">
+<Text id="520"><i>extract_date</i></Text>
+</th>
+<th width="265">
+<Text id="521">Extract the creation date from the PostScript header and store it as metadata.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="522"><i>extract_title</i></Text>
+</th>
+<th width="265">
+<Text id="523">Extract the document title from the PostScript header and store it as title metadata.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="524"><i>extract_pages</i></Text>
+</th>
+<th width="265">
+<Text id="525">Extract the page numbers from the PostScript document and add them to the appropriate sections as metadata with the tag <i>Pages.</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="526"><i>RecPlug</i></Text>
+</th>
+<th width="132">
+<Text id="527"><i>use_metadata_files</i></Text>
+</th>
+<th width="265">
+<Text id="528">Assign metadata from a file as described in the subsection below.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="529"><i>ImagePlug</i></Text>
+</th>
+<th width="132">
+<Text id="530">Various options</Text>
+</th>
+<th width="265">
+<Text id="531">See <i>ImagePlug.pm.</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="532"><i>SRCPlug</i></Text>
+</th>
+<th width="132">
+<Text id="533"><i>remove_prefix</i></Text>
+</th>
+<th width="265">
+<Text id="534">Gives a Perl regular expression of a leading pattern which is to be removed from the filename. Default behaviour is to remove the whole path.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="plugins_to_import_proprietary_formats">
+<Title>
+<Text id="535">Plugins to import proprietary formats</Text>
+</Title>
+<Content>
+<Text id="536">Proprietary formats pose difficult problems for any digital library system. Although documentation may be available about how they work, they are subject to change without notice, and it is difficult to keep up with changes. Greenstone has adopted the policy of using GPL (Gnu Public License) conversion utilities written by people dedicated to the task. Utilities to convert Word and PDF formats are included in the <i>packages</i> directory. These all convert documents to either text or html. Then <i>HTMLPlug</i> and <i>TEXTPlug</i> are used to further convert them to the Greenstone archive format. <i>ConvertToPlug</i> is used to include the conversion utilities. Like <i>BasPlug</i> it is never called directly. Rather, plugins written for individual formats are derived from it as illustrated in Figure <CrossRef target="Figure" ref="plugin_inheritance_hierarchy"/>. <i>ConvertToPlug</i> uses Perl's dynamic inheritance scheme to inherit from either <i>TEXTPlug</i> or <i>HTMLPlug</i>, depending on the format to which a source document has been converted.</Text>
+<Figure id="plugin_inheritance_hierarchy">
+<Title>
+<Text id="537">Plugin inheritance hierarchy</Text>
+</Title>
+<File width="229" height="193" url="images/Dev_Fig_9.gif"/>
+</Figure>
+<Text id="538">When <i>ConvertToPlug</i> receives a document, it calls <i>gsConvert.pl</i> (found in <i>GSDLHOME/bin/script</i>) to invoke the appropriate conversion utility. Once the document has been converted, it is returned to <i>ConvertToPlug</i>, which invokes the text or html plugin as appropriate. Any plugin derived from <i>ConvertToPlug</i> has an option <i>convert_to</i>, whose argument is either <i>text</i> or <i>html</i>, to specify which intermediate format is preferred. Text is faster, but html generally looks better, and includes pictures.</Text>
+<Text id="539">Sometimes there are several conversion utilities for a particular format, and <i>gsConvert</i> may try different ones on a given document. For example, the preferred Word conversion utility <i>wvWare</i> does not cope with anything less than Word 6, and a program called <i>AnyToHTML</i>, which essentially just extracts whatever text strings can be found, is called to convert Word 5 documents.</Text>
+<Text id="540">The steps involved in adding a new external document conversion utility are:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="541">Install the new conversion utility so that it is accessible by Greenstone (put it in the <i>packages</i> directory).</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="542">Alter <i>gsConvert.pl</i> to use the new conversion utility. This involves adding a new clause to the <i>if</i> statement in the <i>main</i> function, and adding a function that calls the conversion utility.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="543">Write a top-level plugin that inherits from <i>ConvertToPlug</i> to catch the format and pass it on.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Subsection>
+<Subsection id="assigning_metadata_from_a_file">
+<Title>
+<Text id="544">Assigning metadata from a file</Text>
+</Title>
+<Content>
+<Text id="545">The standard plugin <i>RecPlug</i> also incorporates a way of assigning metadata to documents from manually (or automatically) created XML files. We describe this in some detail, so that you can create metadata files in the appropriate format. If the <i>use_metadata_files</i> option is specified, <i>RecPlug</i> uses an auxiliary metadata file called <i>metadata.xml</i>. Figure <CrossRef target="Figure" ref="xml_format"/> shows the XML Document Type Definition (DTD) for the metadata file format, while Figure <CrossRef target="Figure" ref="xml_format_1"/> shows an example <i>metadata.xml</i> file.</Text>
+<Figure id="xml_format">
+<Title>
+<Text id="546">XML format: (a) Document Type Definition (DTD); (b) Example metadata file</Text>
+<SubTitle>
+<Text id="547">(a)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;!DOCTYPE GreenstoneDirectoryMetadata [</CodeLine>
+<CodeLine>   &lt;!ELEMENT DirectoryMetadata (FileSet*)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT FileSet (FileName+,Description)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT FileName (#PCDATA)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT Description (Metadata*)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT Metadata (#PCDATA)&gt;</CodeLine>
+<CodeLine>   &lt;ATTLIST Metadata name CDATA #REQUIRED&gt;</CodeLine>
+<CodeLine>   &lt;ATTLIST Metadata mode (accumulate|override) "override"&gt;</CodeLine>
+<CodeLine>]&gt;</CodeLine>
+</Figure>
+<Figure id="xml_format_1">
+<Title>
+<Text id="548"/>
+<SubTitle>
+<Text id="549">(b)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;?xml version="1.0" ?&gt;</CodeLine>
+<CodeLine>&lt;!DOCTYPE GreenstoneDirectoryMetadata SYSTEM</CodeLine>
+<CodeLine>"http://greenstone.org/dtd/GreenstoneDirectoryMetadata/<br/>1.0/GreenstoneDirectoryMetadata.dtd"&gt;</CodeLine>
+<CodeLine>&lt;DirectoryMetadata&gt;</CodeLine>
+<CodeLine>   &lt;FileSet&gt;</CodeLine>
+<CodeLine>       &lt;FileName&gt;nugget.*&lt;/FileName&gt;</CodeLine>
+<CodeLine>       &lt;Description&gt;</CodeLine>
+<CodeLine>       &lt;Metadata name="Title"&gt;Nugget Point Lighthouse&lt;/Metadata&gt;</CodeLine>
+<CodeLine>           &lt;Metadata name="Place" mode="accumulate"&gt;Nugget Point&lt;/Metadata&gt;</CodeLine>
+<CodeLine>       &lt;/Description&gt;</CodeLine>
+<CodeLine>   &lt;/FileSet&gt;</CodeLine>
+<CodeLine>   &lt;FileSet&gt;</CodeLine>
+<CodeLine>       &lt;FileName&gt;nugget-point-1.jpg&lt;/FileName&gt;</CodeLine>
+<CodeLine>       &lt;Description&gt;</CodeLine>
+<CodeLine>           &lt;Metadata name="Title"&gt;Nugget Point Lighthouse , The Catlins &lt;/Metadata&gt;</CodeLine>
+<CodeLine>           &lt;Metadata name="Subject"&gt;Lighthouse&lt;/Metadata&gt;</CodeLine>
+<CodeLine>       &lt;/Description&gt;</CodeLine>
+<CodeLine>   &lt;/FileSet&gt;</CodeLine>
+<CodeLine>&lt;/DirectoryMetadata&gt;</CodeLine>
+</Figure>
+<Text id="550">The example file contains two metadata structures. In each one, the <i>filename</i> element describes files to which the metadata applies, in the form of a regular expression. Thus <i>&lt;FileName&gt;nugget.*&lt;/FileName&gt;</i> indicates that the first metadata record applies to every file whose name starts with ânuggetâ.<FootnoteRef id="2"/>For these files, <i>Title</i> metadata is set to âNugget Point Lighthouse.â</Text>
+<Text id="551">Metadata elements are processed in the order in which they appear. The second structure above sets <i>Title</i> metadata for the file named <i>nugget-point-1.jpg</i> to âNugget Point Lighthouse, The Catlins,â overriding the previous specification. It also adds a <i>Subject</i> metadata field.</Text>
+<Text id="552">Sometimes metadata is multi-valued and new values should accumulate, rather than overriding previous ones. The <i>mode=accumulate</i> attribute does this. It is applied to <i>Place</i> metadata in the first specification above, which will therefore be multi-valued. To revert to a single metadata element, write <i>&lt;Metadata name=âPlaceâ mode=âoverrideâ&gt;New Zealand&lt;/Metadata&gt;</i>. In fact, you could omit this mode specification because every element overrides unless otherwise specified. To accumulate metadata for some field, <i>mode=accumulate</i> must be specified in every occurrence.</Text>
+<Text id="553">When its <i>use_metadata_files</i> option is set, <i>RecPlug</i> checks each input directory for an XML file called <i>metadata.xml</i> and applies its contents to all the directory's files and subdirectories.</Text>
+<Text id="554">The <i>metadata.xml</i> mechanism that is embodied in RecPlug is just one way of specifying metadata for documents. It is easy to write different plugins that accept metadata specifications in completely different formats.</Text>
+</Content>
+</Subsection>
+<Subsection id="tagging_document_files">
+<Title>
+<Text id="555">Tagging document files</Text>
+</Title>
+<Content>
+<Text id="556">Source documents often need to be structured into sections and subsections, and this information needs to be communicated to Greenstone so that it can preserve the hierarchical structure. Also, metadataâtypically the titleâmight be associated with each section and subsection.</Text>
+<Text id="557">The simplest way of doing this is often simply to edit the source files. The HTML plugin has a <i>description_tags</i> option that processes tags in the text like this:</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>   &lt;Description&gt;</CodeLine>
+<CodeLine>       &lt;Metadata name="Title"&gt; Realizing human rights for poor people: Strategies for achieving the international development targets&lt;/Metadata&gt;</CodeLine>
+<CodeLine>   &lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="558"><i>(text of section goes here)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="559">The &lt;!-- âŠ --&gt; markers are used because they indicate comments in HTML; thus these section tags will not affect document formatting. In the <i>Description</i> part other kinds of metadata can be specified, but this is not done for the style of collection we are describing here. Also, the tags can be nested, so the line marked <i>text of section goes here</i> above can itself include further subsections, such as</Text>
+<Text id="560"><i>(text of first part of section goes here)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>   &lt;Description&gt;</CodeLine>
+<CodeLine>       &lt;Metadata name="Title"&gt; The international development targets&lt;/Metadata&gt;</CodeLine>
+<CodeLine>   &lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="561"><i>(text of subsection goes here)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="562"><i>(text of last part of section goes here)</i></Text>
+<Text id="563">This functionality is inherited by any plugins that use HTMLPlug. In particular, the Word plugin converts its input to HTML form, and so exactly the same way of specifying metadata can be used in Word (and RTF) files. (This involves a bit of work behind the scenes, because when Word documents are converted to HTML care is normally taken to neutralize HTML's special interpretation of stray â&lt;â and â&gt;â signs; we have arranged to override this in the case of the above specifications.) Note that exactly the same format as above is used, even in Word files, including the surrounding â&lt;!--â and â--&gt;â. Font and spacing is ignored.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="classifiers">
+<Title>
+<Text id="564">Classifiers</Text>
+</Title>
+<Content>
+<Text id="565">Classifiers are used to create a collection's browsing indexes. Examples are the <i>dlpeople</i> collection's <i>Titles A-Z</i> index, and the <i>Subject</i>, <i>How to</i>, <i>Organisation</i> and <i>Titles A-Z</i> indexes in the Humanity Development Libraryâof which the Demo collection is a subset. The navigation bar near the top of the screenshots in Figures 3 and 8a include the <i>search</i> function, which is always provided, followed by buttons for any classifiers that have been defined. The information used to support browsing is stored in the collection information database, and is placed there by classifiers that are called during the final phase of <i>buildcol.pl</i>.</Text>
+<Figure id="azlist_classifier">
+<Title>
+<Text id="566"><i>AZList</i> classifier</Text>
+</Title>
+<File width="390" height="182" url="images/Dev_Fig_11.png"/>
+</Figure>
+<Text id="567">Classifiers, like plugins, are specified in a collection's configuration file. For each one there is a line starting with the keyword <i>classify</i> and followed by the name of the classifier and any options it takes. The basic collection configuration file discussed in Section <CrossRef target="Section" ref="configuration_file"/> includes the line <i>classify AZListâmetadata Title</i>, which makes an alphabetic list of titles by taking all those with a <i>Title</i> metadata field, sorting them and splitting them into alphabetic ranges. An example is shown in Figure <CrossRef target="Figure" ref="azlist_classifier"/>.</Text>
+<Figure id="list_classifier">
+<Title>
+<Text id="568"><i>List</i> classifier</Text>
+</Title>
+<File width="394" height="143" url="images/Dev_Fig_12.png"/>
+</Figure>
+<Text id="569">A simpler classifier, called <i>List</i>, illustrated in Figure <CrossRef target="Figure" ref="list_classifier"/>, creates a sorted list of a given metadata element and displays it without any alphabetic subsections. An example is the <i>how to</i> metadata in the Demo collection, which is produced by a line <i>classify List âmetadata Howto</i> in the collection configuration file.<FootnoteRef id="3"/> Another general-purpose list classifier is <i>DateList</i>, illustrated in Figure <CrossRef target="Figure" ref="datelist_classifier"/>, which generates a selection list of date ranges. (The <i>DateList</i> classifier is also used in the Greenstone Archives collection.)</Text>
+<Figure id="datelist_classifier">
+<Title>
+<Text id="570"><i>DateList</i> classifier</Text>
+</Title>
+<File width="390" height="159" url="images/Dev_Fig_13.png"/>
+</Figure>
+<Text id="571">Other classifiers generate browsing structures that are explicitly hierarchical. Hierarchical classifications are useful for subject classifications and subclassifications, and organisational hierarchies. The Demo collection's configuration file contains the line<br/><i>classify Hierarchy âhfile sub.txt âmetadata Subject âsort Title</i>, and Figure <CrossRef target="Figure" ref="hierarchy_classifier"/> shows the subject hierarchy browser that it produces. The bookshelf with a bold title is the one currently being perused; above it you can see the subject classification to which it belongs. In this example the hierarchy for classification is stored in a simple text format in <i>sub.txt</i>.</Text>
+<Figure id="hierarchy_classifier">
+<Title>
+<Text id="572"><i>Hierarchy</i> classifier</Text>
+</Title>
+<File width="394" height="198" url="images/Dev_Fig_14.png"/>
+</Figure>
+<Text id="573">All classifiers generate a hierarchical structure that is used to display a browsing index. The lowest levels (i.e. leaves) of the hierarchy are usually documents, but in some classifiers they are sections. The internal nodes of the hierarchy are either <i>Vlist</i>, <i>Hlist</i>, or <i>Datelist</i>. A <i>Vlist</i> is a list of items displayed vertically down the page, like the âhow toâ index in the Demo collection (see Figure <CrossRef target="Figure" ref="list_classifier"/>). An <i>Hlist</i> is displayed horizontally. For example, the <i>AZList</i> display in Figure <CrossRef target="Figure" ref="azlist_classifier"/> is a two-level hierarchy of internal nodes consisting of an <i>Hlist</i>(giving the A-Z selector) whose children are <i>Vlists</i> âand their children, in turn, are documents. A <i>Datelist</i> (Figure <CrossRef target="Figure" ref="datelist_classifier"/>) is a special kind of <i>Vlist</i> that allows selection by year and month.</Text>
+<Text id="574">The lines used to specify classifiers in collection configuration files contain a <i>metadata</i> argument that identifies the metadata by which the documents are classified and sorted. Any document in the collection that does not have this metadata defined will be omitted from the classifier (but it is still indexed, and consequently searchable). If no <i>metadata</i> argument is specified, all documents are included in the classifier, in the order in which they are encountered during the building process. This is useful if you want a list of all documents in your collection.</Text>
+<Table id="greenstone_classifiers">
+<Title>
+<Text id="575">Greenstone classifiers</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="576"><b>Argument</b></Text>
+</th>
+<th width="305">
+<Text id="577"><b>Purpose</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="578"><i>Hierarchy</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="579">Hierarchical classification</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="580"><i>hfile</i></Text>
+</th>
+<th width="305">
+<Text id="581">Classification file</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="582"><i>metadata</i></Text>
+</th>
+<th width="305">
+<Text id="583">Metadata element to test against <i>hfile</i> identifier</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="584"><i>sort</i></Text>
+</th>
+<th width="305">
+<Text id="585">Metadata element used to sort documents within leaves (defaults to <i>Title</i>)</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="586"><i>buttonname</i></Text>
+</th>
+<th width="305">
+<Text id="587">Name of the button used to access this classifier (defaults to value of metadata argument)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="588"><i>List</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="589">Alphabetic list of documents</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="590"><i>metadata</i></Text>
+</th>
+<th width="305">
+<Text id="591">Include documents containing this metadata element</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="592"><i>buttonname</i></Text>
+</th>
+<th width="305">
+<Text id="593">Name of button used to access this classifier (defaults to value of metadata argument)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="594"><i>SectionList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="595">List of sections in documents</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="596"><i>AZList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="597">List of documents split into alphabetical ranges</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="598"><i>metadata</i></Text>
+</th>
+<th width="305">
+<Text id="599">Include all documents containing this metadata element</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="600"><i>buttonname</i></Text>
+</th>
+<th width="305">
+<Text id="601">Name of button used to access this classifier (defaults to value of metadata argument)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="602"><i>AZSectionList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="603">Like <i>AZList</i> but includes every section of the document</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="604"><i>DateList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="605">Similar to <i>AZList</i> but sorted by date</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="606">The current set of classifiers is listed in Table <CrossRef target="Table" ref="greenstone_classifiers"/>. Just as you can use the <i>pluginfo.pl</i> program to find out about any plugin, there is a <i>classinfo.pl</i> program that gives you information about any classifier, and the options it provides.</Text>
+<Text id="607">All classifiers accept the argument <i>buttonname</i>, which defines what is written on the Greenstone navigation button that invokes the classifier (it defaults to the name of the metadata argument). Buttons are provided for each Dublin Core metadata type, and for some other types of metadata.</Text>
+<Text id="608">Each classifier receives an implicit name from its position in the configuration file. For example, the third classifier specified in the file is called CL3. This is used to name the collection information database fields that define the classifier hierarchy.</Text>
+<Text id="609">Collection-specific classifiers can be written, and are stored in the collection's <i>perllib/classify</i> directory. The Development Library has a collection-specific classifier called <i>HDLList</i>, which is a minor variant of <i>AZList</i>.</Text>
+<Subsection id="list_classifiers">
+<Title>
+<Text id="610">List classifiers</Text>
+</Title>
+<Content>
+<Text id="611">The various flavours of list classifier are shown below.</Text>
+<BulletList>
+<Bullet>
+<Text id="612"><i>SectionList</i>âlike <i>List</i> but the leaves are sections rather than documents. All document sections are included except the top level. This is used to create lists of sections (articles, chapters or whatever) such as in the Computists' Weekly collection (available through <i>nzdl.org</i>), where each issue is a single document and comprises several independent news items, each in its own section.</Text>
+</Bullet>
+<Bullet>
+<Text id="613"><i>AZList</i>âgenerates a two-level hierarchy comprising an <i>HList</i> whose children are <i>VLists</i>, whose children are documents. The <i>HList</i> is an A-Z selector that divides the documents into alphabetic ranges. Documents are sorted alphabetically by metadata, and the resulting list is split into ranges.</Text>
+</Bullet>
+<Bullet>
+<Text id="614"><i>AZSectionList</i>âlike <i>AZList</i> but the leaves are sections rather than documents.</Text>
+</Bullet>
+<Bullet>
+<Text id="615"><i>DateList</i>âlike <i>AZList</i> except that the top-level <i>HList</i> allows selection by year and its children are <i>DateLists</i> rather than <i>VLists</i>. The metadata argument defaults to <i>Date</i>.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="the_hierarchy_classifier">
+<Title>
+<Text id="616">The hierarchy classifier</Text>
+</Title>
+<Content>
+<Text id="617">All classifiers are hierarchical. However, the list classifiers described above have a fixed number of levels, whereas the âhierarchyâ classifiers described in this section have an arbitrary number of levels. Hierarchy classifiers are more complex to specify than list classifiers.</Text>
+<Figure id="part_of_the_file_sub">
+<Title>
+<Text id="618">Part of the file <i>sub.txt</i></Text>
+</Title>
+<CodeLine>1           1       "General reference"</CodeLine>
+<CodeLine>1.2       1.2       "Dictionaries, glossaries, language courses, terminology</CodeLine>
+<CodeLine>2           2       "Sustainable Development, International cooperation, Pro</CodeLine>
+<CodeLine>2.1       2.1       "Development policy and theory, international cooperatio</CodeLine>
+<CodeLine>2.2       2.2       "Development, national planning, national plans"</CodeLine>
+<CodeLine>2.3       2.3       "Project planning and evaluation (incl. project managem</CodeLine>
+<CodeLine>2.4       2.4       "Regional development and planning incl. regional profil</CodeLine>
+<CodeLine>2.5       2.5       "Nongovernmental organisations (NGOs) in general, self-</CodeLine>
+<CodeLine>2.6       2.6       "Organisations, institutions, United Nations (general, d</CodeLine>
+<CodeLine>2.6.1   2.6.1       "United Nations"</CodeLine>
+<CodeLine>2.6.2   2.6.2       "International organisations"</CodeLine>
+<CodeLine>2.6.3   2.6.3       "Regional organisations"</CodeLine>
+<CodeLine>2.6.5   2.6.5       "European Community - European Union"</CodeLine>
+<CodeLine>2.7       2.7       "Sustainable Development, Development models and example</CodeLine>
+<CodeLine>2.8       2.8       "Basic Human Needs"</CodeLine>
+<CodeLine>2.9       2.9       "Hunger and Poverty Alleviation"</CodeLine>
+</Figure>
+<Text id="619">The <i>hfile</i> argument gives the name of a file, like that in Figure <CrossRef target="Figure" ref="part_of_the_file_sub"/>, which defines the metadata hierarchy. Each line describes one classification, and the descriptions have three parts:</Text>
+<BulletList>
+<Bullet>
+<Text id="620">Identifier, which matches the value of the metadata (given by the <i>metadata</i> argument) to the classification.</Text>
+</Bullet>
+<Bullet>
+<Text id="621">Position-in-hierarchy marker, in multi-part numeric form, e.g. 2, 2.12, 2.12.6.</Text>
+</Bullet>
+<Bullet>
+<Text id="622">The name of the classification. (If this contains spaces, it should be placed in quotation marks.)</Text>
+</Bullet>
+</BulletList>
+<Text id="623">Figure <CrossRef target="Figure" ref="part_of_the_file_sub"/> is part of the <i>sub.txt</i> file used to create the subject hierarchy in the Development Library (and the Demo collection). This example is a slightly confusing one because the number representing the hierarchy appears twice on each line. The metadata type <i>Hierarchy</i> is represented in documents with values in hierarchical numeric form, which accounts for the first occurrence. It is the second occurrence that is used to determine the hierarchy that the hierarchy browser implements.</Text>
+<Text id="624">The <i>hierarchy</i> classifier has an optional argument, <i>sort</i>, which determines how the documents at the leaves are ordered. Any metadata can be specified as the sort key. The default is to produce the list in the order in which the building process encounters the documents. Ordering at internal nodes is determined by the order in which things are specified in the <i>hfile</i> argument.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_classifiers_work">
+<Title>
+<Text id="625">How classifiers work</Text>
+</Title>
+<Content>
+<Text id="626">Classifiers are Perl objects, derived from <i>BasClas.pm</i>, and are stored in the <i>perllib/classify</i> directory. They are used when the collection is built. When they are executed, the following four steps occur.</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="627">The <i>new</i> method creates the classifier object.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="628">The <i>init</i> method initialises the object with parameters such as metadata type, button name and sort criterion.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="629">The <i>classify</i> method is invoked once for each document, and stores information about the classification made within the classifier object.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="630">The <i>get_classify_info</i> method returns the locally stored classification information to the build process, which it then writes to the collection information database for use when the collection is displayed at runtime.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="631">The <i>classify</i> method retrieves each document's OID, the metadata value on which the document is to be classified, and, where necessary, the metadata value on which the documents are to be sorted. The <i>get_classify_info</i> method performs all sorting and classifier-specific processing. For example, in the case of the <i>AZList</i> classifier, it splits the list into ranges.</Text>
+<Text id="632">The build process initialises the classifiers as soon as the <i>builder</i> object is created. Classifications are created during the build phase, when the information database is created, by <i>classify.pm</i>, which resides in Greenstone's <i>perllib</i> directory.</Text>
+<Table id="items_appearing_in_format_strings">
+<Title>
+<Text id="633">Items appearing in format strings</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="634"><i>[Text]</i></Text>
+</th>
+<th width="397">
+<Text id="635">The document's text</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="636"><i>[link] âŠ [/link]</i></Text>
+</th>
+<th width="397">
+<Text id="637">The html to link to the document itself</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="638"><i>[icon]</i></Text>
+</th>
+<th width="397">
+<Text id="639">An appropriate icon (e.g. the little text icon in a <i>Search Results</i> string)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="640"><i>[num]</i></Text>
+</th>
+<th width="397">
+<Text id="641">The document number (useful for debugging).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="642"><i>[metadata-name]</i></Text>
+</th>
+<th width="397">
+<Text id="643">The value of this metadata element for the document, e.g. <i>[Title]</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="formatting_greenstone_output">
+<Title>
+<Text id="644">Formatting Greenstone output</Text>
+</Title>
+<Content>
+<Text id="645">The web pages you see when using Greenstone are not pre-stored but are generated âon the flyâ as they are needed. The appearance of many aspects of the pages is controlled using âformat strings.â Format strings belong in the collection configuration file, introduced by the keyword <i>format</i> followed by the name of the element to which the format applies. There are two different kinds of page element that are controlled by format strings. The first comprises the items on the page that show documents or parts of documents. The second comprises the lists produced by classifiers and searches. All format strings are interpreted at the time that pages are displayed. Since they take effect as soon as any changes in <i>collect.cfg</i> are saved, experimenting with format strings is quick and easy.</Text>
+<Text id="646">Table <CrossRef target="Table" ref="items_appearing_in_format_strings"/> shows the format statements that affect the way documents look. The <i>DocumentButtons</i> option controls what buttons are displayed on a document page. Here, <i>string</i> is a list of buttons (separated by |), possible values being <i>Detach</i>, <i>Highlight</i>, <i>Expand Text</i>, and <i>Expand Contents</i>. Reordering the list reorders the buttons.</Text>
+<Table id="the_format_options">
+<Title>
+<Text id="647">The <i>format</i> options</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="246">
+<Text id="648"><i>format DocumentImages true/false</i></Text>
+</th>
+<th width="283">
+<Text id="649">If <i>true</i>, display a cover image at the top left of the document page (default <i>false</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="650"><i>format DocumentHeading formatstring</i></Text>
+</th>
+<th width="283">
+<Text id="651">If <i>DocumentImages</i> is <i>false</i>, the format string controls how the document header shown at the top left of the document page looks (default <i>[Title]</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="652"><i>format DocumentContents true/false</i></Text>
+</th>
+<th width="283">
+<Text id="653">Display table of contents (if document is hierarchical), or next/previous section arrows and âpage k of nâ text (if not).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="654"><i>format DocumentButtons string</i></Text>
+</th>
+<th width="283">
+<Text id="655">Controls the buttons that are displayed on a document page (default <i>Detach|Highlight</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="656"><i>format DocumentText formatstring</i></Text>
+</th>
+<th width="283">
+<Text id="657">Format of the text to be displayed on a document page: default</Text>
+<CodeLine>Â Â Â Â <i>&lt;center&gt;&lt;table width=537&gt;</i></CodeLine>
+<CodeLine><i>Â Â Â Â Â Â &lt;tr&gt;&lt;td&gt;[Text]&lt;/td&gt;&lt;/tr&gt;</i></CodeLine>
+<CodeLine><i>Â Â Â Â Â Â &lt;/table&gt;&lt;/center&gt;</i></CodeLine>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="658"><i>format DocumentArrowsBottom true/false</i></Text>
+</th>
+<th width="283">
+<Text id="659">Display next/previous section arrows at bottom of document page (default <i>true</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="660"><i>format DocumentUseHTML true/false</i></Text>
+</th>
+<th width="283">
+<Text id="661">If <i>true</i>, each document is displayed inside a separate frame. The Preferences page will also change slightly, adding options applicable to a collection of html documents, including the ability to go directly to the original source document (anywhere on the Web) rather than to the Greenstone copy.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Subsection id="formatting_greenstone_lists">
+<Title>
+<Text id="662">Formatting Greenstone lists</Text>
+</Title>
+<Content>
+<Text id="663">Format strings that control how lists look can apply at different levels of the display structure. They can alter all lists of a certain type within a collection (for example <i>DateList</i>), or all parts of a list (for example all the entries in the <i>Search</i> list), or specific parts of a certain list (for example, the vertical list part of an <i>AZList</i> classifier on title).</Text>
+<Text id="664">Following the keyword <i>format</i> is a two-part keyword, only one part of which is mandatory. The first part identifies the list to which the format applies. The list generated by a search is called <i>Search</i>, while the lists generated by classifiers are called <i>CL1, CL2, CL3,âŠ</i> for the first, second, third,âŠ classifier specified in <i>collect.cfg</i>. The second part of the keyword is the part of the list to which the formatting is to applyâeither <i>HList</i> (for horizontal list, like the A-Z selector in an <i>AZList</i>), <i>VList</i> (for vertical list, like the list of titles under an <i>AZList</i>), or <i>DateList</i>. For example:</Text>
+<Indented>
+<Text id="665"><i>format CL4VList ...</i>                                  applies to all <i>VLists</i> in CL4</Text>
+</Indented>
+<Indented>
+<Text id="666"><i>format CL2HList ...</i>                                applies to all <i>HLists</i> in CL2</Text>
+</Indented>
+<Indented>
+<Text id="667"><i>format CL1DateList ...</i>                      applies to all <i>DateLists</i> in CL1</Text>
+</Indented>
+<Indented>
+<Text id="668"><i>format SearchVList ...</i>                        applies to the Search Results list</Text>
+</Indented>
+<Indented>
+<Text id="669"><i>format CL3 ...</i>                                                    applies to all nodes in CL3, unless otherwise specified</Text>
+</Indented>
+<Indented>
+<Text id="670"><i>format VList ...</i>                                                applies to all <i>VLists</i> in all classifiers, unless otherwise specified</Text>
+</Indented>
+<Text id="671">The â...â in these examples stand for html format specifications that control the information, and its layout, that appear on web pages displaying the classifier. As well as html specifications, any metadata may appear within square brackets: its value is interpolated in the indicated place. Also, any of the items in Table <CrossRef target="Table" ref="the_format_options"/> may appear in format strings. The syntax for the strings also includes a conditional statement, which is illustrated in an example below.</Text>
+<Text id="672">Recall that all classifiers produce hierarchies. Each level of the hierarchy is displayed in one of four possible ways. We have already encountered <i>HList</i>, <i>VList</i>, and <i>DateList</i>. There is also <i>Invisible</i>, which is how the very top levels of hierarchies are displayedâbecause the name of the classifier is already shown separately on the Greenstone navigation bar.</Text>
+</Content>
+</Subsection>
+<Subsection id="examples_of_classifiers_and_format_strings">
+<Title>
+<Text id="673">Examples of classifiers and format strings</Text>
+</Title>
+<Content>
+<Figure id="excerpt_from_the_demo_collection_collect" class="withLineNumber">
+<Title>
+<Text id="674">Excerpt from the Demo collection's <i>collect.cfg</i></Text>
+</Title>
+<CodeLine>classify Hierarchy -hfile sub.txt -metadata Subject -sort Title</CodeLine>
+<CodeLine>classify AZList       -metadata Title</CodeLine>
+<CodeLine>classify Hierarchy -hfile org.txt -metadata Organisation -sort Title</CodeLine>
+<CodeLine>classify List           -metadata Howto</CodeLine>
+<CodeLine>format SearchVList " &lt;td valign=top [link][icon][/link]&lt;/td&gt;&lt;td&gt;{If}</CodeLine>
+<CodeLine>                                       {[parent(All':'):Title],[parent(All':'):Title]:}</CodeLine>
+<CodeLine>                                       [link][Title][/link]&lt;/td&gt; "</CodeLine>
+<CodeLine>format CL4Vlist                 "&lt;br&gt;[link][Howto][/link] "</CodeLine>
+<CodeLine>format DocumentImages   true</CodeLine>
+<CodeLine>format DocumentText       "&lt;h3&gt;[Title]&lt;/h3&gt;\\n\\n&lt;p&gt;[Text]"</CodeLine>
+<CodeLine>format DocumentButtons " Expand Text|Expand contents|Detach|Highlight"</CodeLine>
+</Figure>
+<Text id="675">Figure <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/> shows part of the collection configuration file for the Demo collection. We use this as an example because it has several classifiers that are richly formatted. Note that statements in collection configuration files must not contain newline charactersâin the Table, longer lines are broken up for readability.</Text>
+<Text id="676">Line 4 specifies the Demo collection's <i>How To</i> classifier. This is the fourth in the collection configuration file, and is therefore referred to as CL4. The corresponding format statement is line 7 of Figure <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>. The âhow toâ information is generated from the <i>List</i> classifier, and its structure is the plain list of titles shown in Figure <CrossRef target="Figure" ref="list_classifier"/>. The titles are linked to the documents themselves: clicking a title brings up the relevant document. The children of the hierarchy's top level are displayed as a <i>VList</i>(vertical list), which lists the sections vertically. As the associated <i>format</i> statement indicates, each element of the list is on a newline (â <i>&lt;br&gt;</i> â) and contains the <i>Howto</i> text, hyperlinked to the document itself.</Text>
+<Text id="677">Line 1 specifies the Demo collection's <i>Subject</i> classification, referred to as CL1 (the first in the configuration file), and Line 3 the <i>Organisation</i> classification CL3. Both are generated by the <i>Hierarchy</i> classifier and therefore comprise a hierarchical structure of <i>VLists</i>.</Text>
+<Text id="678">Line 2 specifies the remaining classification for the Demo collection, <i>Titles A-Z</i> (CL2). Note that there are no corresponding format strings for the classifiers CL1 -CL3. Greenstone has built-in defaults for each format string type and so it's not necessary to set a format string unless you want to override the default.</Text>
+<Figure id="formatting_the_document">
+<Title>
+<Text id="679">Formatting the document</Text>
+</Title>
+<File width="394" height="277" url="images/Dev_Fig_17.gif"/>
+</Figure>
+<Text id="680">This accounts for the four <i>classify</i> lines in Figure <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>. Coincidentally, there are also four <i>format</i> lines. We have already discussed one, the <i>CL4Vlist</i> one. The remaining three are the first type of format string, documented in Table <CrossRef target="Table" ref="items_appearing_in_format_strings"/>. For example, line 8 places the cover image at the top left of each document page. Line 9 formats the actual document text, with the title of the relevant chapter or section preceding the text itself. These are illustrated in Figure <CrossRef target="Figure" ref="formatting_the_document"/>.</Text>
+<Figure id="formatting_the_search_results">
+<Title>
+<Text id="681">Formatting the search results</Text>
+</Title>
+<File width="396" height="243" url="images/Dev_Fig_18.gif"/>
+</Figure>
+<Text id="682">Line 5 of Figure <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/> is a rather complicated specification that formats the query result list returned by a search, whose parts are illustrated in Figure <CrossRef target="Figure" ref="formatting_the_search_results"/>. A simplified version of the format string is</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;</CodeLine>
+<CodeLine>&lt;td&gt;[link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="683">This is designed to appear as a table row, which is how the query results list is formatted. It gives a small icon linked to the text, as usual, and the document title, hyperlinked to the document itself.</Text>
+<Text id="684">In this collection, documents are hierarchical. In fact, the above hyperlink anchor evaluates to the title of the section returned by the query. However, it would be better to augment it with the title of the enclosing section, the enclosing chapter, and the book in which it occurs. There is a special metadata item, <i>parent</i>, which is not stored in documents but is implicit in any hierarchical document, that produces such a list. It either returns the parent document, or, if used with the qualifier <i>All</i>, the list of hierarchically enclosing parents, separated by a character string that can be given after the <i>All</i> qualifier. Thus</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt; <br/>&lt;td&gt;{[parent(All': '):Title]: }[link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="685">has the effect of producing a list containing the book title, chapter title, etc. that enclose the target section, separated by colons, with a further colon followed by a hyperlink to the target section's title.</Text>
+<Text id="686">Unfortunately, if the target is itself a book, there is no parent and so an empty string will appear followed by a colon. To circumvent such problems you can use <i>if</i> and <i>or âŠ else</i> statements in a format string:</Text>
+<CodeLine>{If}{[metadata], action-if-non-null, action-if-null}</CodeLine>
+<CodeLine>{Or}{action, else another-action, else another-action, etc}</CodeLine>
+<Text id="687">In either case curly brackets are used to signal that the statements should be interpreted and not just printed out as text. The <i>If</i> tests whether the metadata is empty and takes the first clause if not, otherwise the second one (if it exists). Any metadata item can be used, including the special metadata <i>parent</i>. The <i>Or</i> statement evaluates each action in turn until one is found that is non-null. That one is sent to the output and the remaining actions are skipped.</Text>
+<Text id="688">Returning to line 5 of Figure <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>, the full format string is</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;</CodeLine>
+<CodeLine>&lt;td&gt;{If}{[parent(All': '):Title],</CodeLine>
+<CodeLine>           [parent(All': '):Title]:}</CodeLine>    
+<CodeLine>      [link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="689">This precedes the <i>parent</i> specification with a conditional that checks whether the result is empty and only outputs the parent string when it is present. Incidentally, <i>parent</i> can be qualified by <i>Top</i> instead of <i>All</i>, which gives the top-level document name that encloses a sectionâin this case, the book name. No separating string is necessary with <i>Top</i>.</Text>
+<Text id="690">Some final examples illustrate other features. The <i>DateList</i> in Figure <CrossRef target="Figure" ref="datelist_classifier"/> is used in the <i>Dates</i> classification of the Computists' Weekly collection (which happens to be the second classifier, CL2). The classifier and format specifications are shown below. The <i>DateList</i> classifier differs from <i>AZList</i> in that it always sorts by <i>Date</i> metadata, and the bottom branches of the browsing hierarchy use <i>DateList</i> instead of <i>VList</i>, which causes the year and month to be added at the left of the document listings.</Text>
+<CodeLine>classify AZSectionList metadata=Creator</CodeLine>
+<CodeLine>format CL2Vlist "&lt;td&gt;[link][icon][/link]&lt;/td&gt; <br/>&lt;td&gt;[Creator]&lt;/td&gt; <br/>&lt;td&gt;&amp;nbsp;&amp;nbsp;[Title]&lt;/td&gt; <br/>&lt;td&gt;[parent(Top):Date]&lt;/td&gt; "</CodeLine>
+<Text id="691">The format specification shows these <i>VLists</i> in the appropriate way.</Text>
+<Text id="692">The format-string mechanism is flexible but tricky to learn. The best way is by studying existing collection configuration files.</Text>
+</Content>
+</Subsection>
+<Subsection id="linking_to_different_document_versions">
+<Title>
+<Text id="693">Linking to different document versions</Text>
+</Title>
+<Content>
+<Text id="694">Using the <i>[link] âŠ [/link]</i> mechanism in a format string inserts a hyperlink to the text of a document, and when the link is clicked the html version of the document is displayed. In some collections, it is useful to be able to display other versions of the document. For example, in a collection of Microsoft Word documents, it is nice to be able to display the Word version of each document rather than the html that is extracted from it; similarly for PDF documents.</Text>
+<Text id="695">The key to being able to show different versions of a document is to embed the necessary information about where the other versions reside into the Greenstone archive form of the document. The information is represented in the form of metadata. Recall that putting</Text>
+<CodeLine>[link][Title][/link]</CodeLine>
+<Text id="696">into a format string creates a link to the html form of the document, whose anchor text is the document's title. The Word and PDF plugins both generate <i>srclink</i> metadata so that if you put</Text>
+<CodeLine>[srclink][Title][/srclink]</CodeLine>
+<Text id="697">into a format string, a link is created to the Word or PDF form of the document; again the anchor in this example is the document's title. In order that the appropriate icon can be displayed for Word and PDF documents, these plugins also generate <i>srcicon</i> metadata so that</Text>
+<CodeLine>[srclink][srcicon][/srclink]</CodeLine>
+<Text id="698">creates a link which is labeled by the standard Word or PDF icon (whichever is appropriate), rather than the document's title.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="controlling_the_greenstone_user_interface">
+<Title>
+<Text id="699">Controlling the Greenstone user interface</Text>
+</Title>
+<Content>
+<Text id="700">The entire Greenstone user interface is controlled by macros which reside in the <i>GSDLHOME/macros</i> directory. They are written in a language designed especially for Greenstone, and are used run time to generate web pages. Translating the macro language into html is the last step in displaying a page. Thus changes to a macro file affect the display immediately, making experimentation quick and easy. All macro files used by Greenstone are listed in <i>GSDLHOME/etc/main.cfg</i> and are loaded every time it starts. One exception to this is when using the Windows Local LIbrary; in this case it is necessary to restart the process.</Text>
+<Text id="701">Web pages are generated on the fly for a number of reasons, and the macro system is how Greenstone implements the necessary flexibility. Pages can be presented in many languages, and a different macro file is used to store all the interface text in each language. When Greenstone displays a page the macro interpreter checks a language variable and loads the page in the appropriate language (this does not, unfortunately, extend to translating document content). Also, the values of certain display variables, like the number of documents found by a search, are not known ahead of time; these are interpolated into the page text in the form of macros.</Text>
+<Subsection id="the_macro_file_format">
+<Title>
+<Text id="702">The macro file format</Text>
+</Title>
+<Content>
+<Text id="703">Macro files have a <i>.dm</i> extension. Each file defines one or more <i>packages</i>, each containing a series of macros used for a single purpose. Like classifiers and plugins, there is a basis from which to build macros, called <i>base.dm</i> ; this file defines the basic content of a page.</Text>
+<Text id="704">Macros have names that begin and end with an underscore, and their content is defined using curly brackets. Content can be plain text, html (including links to Java applets and JavaScript), macro names, or any combination of these. This macro from <i>base.dm</i> defines the content of a page in the absence of any overriding macro:</Text>
+<CodeLine>_content_ {&lt;p&gt;&lt;h2&gt;Oops&lt;/h2&gt;_textdefaultcontent_}</CodeLine>
+<Text id="705">The page will read âOopsâ at the top, and <i>_textdefaultcontent_</i>, which is defined, in English, to be <i>The requested page could not be found. Please use your browsers 'back' button or the above home button to return to the Greenstone Digital Library,</i> and in other languages to be a suitable translation of this sentence.</Text>
+<Text id="706"><i>_textdefaultcontent_</i> and <i>_content_</i> both reside in the <i>global</i> package because they are required by all parts of the user interface. Macros can use macros from other packages as content, but they must prefix their names with their package name. For example,</Text>
+<CodeLine>_collectionextra_ {This collection contains _about:numdocs_ documents. It was last built _about:builddate_ days ago.)</CodeLine>
+<Text id="707">comes from <i>english.dm</i>, and is used as the default description of a collection. It is part of the <i>global</i> package, but <i>_numdocs_</i> and <i>_builddate_</i> are both in the <i>about</i> packageâhence the <i>about:</i> preceding their names.</Text>
+<Text id="708">Macros often contain conditional statements. They resemble the format string conditional described above, though their appearance is slightly different. The basic format is <i>_If_(x,y,z)</i>, where <i>x</i> is a condition, <i>y</i> is the macro content to use if that condition is true, and <i>z</i> the content if it is false. Comparison operators are the same as the simple ones used in Perl (less than, greater than, equals, not equals). This example from <i>base.dm</i> is used to determine how to display the top of a collection's <i>about</i> page:</Text>
+<CodeLine>_imagecollection_ {</CodeLine>
+<CodeLine>       _If_( "_iconcollection_ " ne "",</CodeLine>
+<CodeLine>                 &lt;a href = "_httppageabout_ "&gt; </CodeLine>
+<CodeLine>                         &lt;img src = "_iconcollection_ " border = 0&gt;</CodeLine>
+<CodeLine>                         &lt;/a&gt;,</CodeLine>
+<CodeLine>                 _imagecollectionv_)</CodeLine>
+<CodeLine>}</CodeLine>
+<Text id="709">This looks rather obscure. <i>_iconcollection_</i> resolves to the empty string if the collection doesn't have an icon, or the filename of an image. To paraphrase the above code: If there is a collection image, display the <i>About this Collection</i> page header (referred to by <i>_httppageabout_</i>) and then the image; otherwise use the alternative display <i>_imagecollectionv_</i>.</Text>
+<Text id="710">Macros can take arguments. Here is a second definition for the <i>_imagecollection_</i> macro which immediately follows the definition given above in the <i>base.dm</i> file:</Text>
+<CodeLine>_imagecollection_[v=1]{_imagecollectionv_}</CodeLine>
+<Text id="711">The argument <i>[v=1]</i> specifies that the second definition is used when Greenstone is running in text-only mode. The language macros work similarlyâapart from <i>english.dm</i>, because it is the default, all language macros specify their language as an argument. For example,</Text>
+<CodeLine>_textimagehome_ {Home Page}</CodeLine>
+<Text id="712">appears in the English language macro file, whereas the German version is</Text>
+<CodeLine>_textimagehome_ [l=de] {Hauptaseite}</CodeLine>
+<Text id="713">The English and German versions are in the same package, though they are in separate files (package definitions may span more than one file). Greenstone uses its <i>l</i> argument at run time to determine which language to display.</Text>
+<Figure id="part_of_the_aboutdm_macro_file">
+<Title>
+<Text id="714">Part of the <i>about.dm</i> macro file</Text>
+</Title>
+<CodeLine>package about</CodeLine>
+<CodeLine>##############################################</CodeLine>
+<CodeLine># about page content</CodeLine>
+<CodeLine>###############################################</CodeLine>
+<CodeLine>_pagetitle_ {_collectionname_}</CodeLine>
+<CodeLine>_content_ {</CodeLine>
+<CodeLine>&lt;center&gt;</CodeLine>
+<CodeLine>_navigationbar_</CodeLine>
+<CodeLine>&lt;/center&gt;</CodeLine>
+<CodeLine>_query:queryform_</CodeLine>
+<CodeLine>&lt;p&gt;_iconblankbar_</CodeLine>
+<CodeLine>&lt;p&gt;_textabout_</CodeLine>
+<CodeLine>_textsubcollections_</CodeLine>
+<CodeLine>&lt;h3&gt;_help:textsimplehelpheading_&lt;/h3&gt;</CodeLine>
+<CodeLine>_help:simplehelp_</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine>_textabout_ {</CodeLine>
+<CodeLine>&lt;h3&gt;_textabcol_&lt;/h3&gt;</CodeLine>
+<CodeLine>_Global:collectionextra_</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="715">As a final example, Figure <CrossRef target="Figure" ref="part_of_the_aboutdm_macro_file"/> shows an exerpt from the macro file <i>about.dm</i> that is used to generate the âAbout this collectionâ page for each collection. It shows three macros being defined, <i>_pagetitle_</i>, <i>_content_</i> and <i>_textabout_</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="using_macros">
+<Title>
+<Text id="716">Using macros</Text>
+</Title>
+<Content>
+<Text id="717">Macros are powerful, and can be a little obscure. However, with a good knowledge of html and a bit of practice, they become a quick and easy way to customise your Greenstone site.</Text>
+<Text id="718">For example, suppose you wanted to create a static page that looked like your current Greenstone site. You could create a new package, called <i>static</i>, for example, in a new file, and override the <i>_content_</i> macro. Add the new filename to the list of macros in <i>GSDLHOME/etc/main.cfg</i> which Greenstone loads every time it is invoked. Finally, access the new page by using your regular Greenstone URL and appending the arguments <i>?a=p&amp;p=static</i> (e.g. <i>http://servername/cgi-bin/library?a=p&amp;p=static</i>).</Text>
+<Text id="719">To change the âlook and feelâ of Greenstone you can edit the <i>base</i> and <i>style</i> packages. To change the Greenstone home page, edit the <i>home</i> package (this is described in the <i>Greenstone Digital Library Installer's Guide</i>). To change the query page, edit <i>query.dm</i>.</Text>
+<Text id="720">Experiment freely with macros. Changes appear instantly, because macros are interpreted as pages are displayed. The macro language is a useful tool that can be used to make your Greenstone site your own.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="the_packages_directory">
+<Title>
+<Text id="721">The packages directory</Text>
+</Title>
+<Content>
+<Table id="the_packages_directory_1">
+<Title>
+<Text id="722">The <i>packages</i> directory</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="217">
+<Text id="723"><b>Package</b></Text>
+</th>
+<th width="180">
+<Text id="724"><b>URL</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="725"><i>mg</i></Text>
+</th>
+<th width="217">
+<Text id="726">mg, short for âManaging Gigabytes.â Compression, indexing and search software used to manage textual information in Greenstone collections.</Text>
+</th>
+<th width="180">
+<Text id="727"><i>www.citri.edu.au/mg</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="728"><i>wget</i></Text>
+</th>
+<th width="217">
+<Text id="729">Web mirroring software for use with Greenstone. Written in C++</Text>
+</th>
+<th width="180">
+<Text id="730"><i>www.tuwien.ac.at/~prikryl/ wget.html</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="731"><i>w3mir</i></Text>
+</th>
+<th width="217">
+<Text id="732">A web mirroring program written in Perl. This is not Greenstone's preferred mirroring program because it relies on a specific outdated version of a certain Perl module (which is distributed in the <i>w3mir</i> directory).</Text>
+</th>
+<th width="180">
+<Text id="733"><i>www.math.uio.no/~janl/w3mir</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="734"><i>windows</i></Text>
+</th>
+<th width="217">
+<Text id="735">Packages used when running under Windows.</Text>
+</th>
+<th width="180">
+<Text id="736"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="737"><i>windows/gdbm</i></Text>
+</th>
+<th width="217">
+<Text id="738">Version of the Gnu Database Manager created for Windows. Gdbm comes as a standard part of Linux.</Text>
+</th>
+<th width="180">
+<Text id="739"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="740"><i>windows/crypt</i></Text>
+</th>
+<th width="217">
+<Text id="741">Encryption program used for passwords for Greenstone's administrative functions.</Text>
+</th>
+<th width="180">
+<Text id="742"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="743"><i>windows/stlport</i></Text>
+</th>
+<th width="217">
+<Text id="744">Standard Template Library, for use when compiling Greenstone with certain Windows compilers.</Text>
+</th>
+<th width="180">
+<Text id="745"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="746"><i>wv</i></Text>
+</th>
+<th width="217">
+<Text id="747">Microsoft Word converter (for building collections from Word documents) slimmed down for Greenstone.</Text>
+</th>
+<th width="180">
+<Text id="748"><i>sourceforge.net/projects/ wvware</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="749"><i>pdftohtml</i></Text>
+</th>
+<th width="217">
+<Text id="750">PDF converter used when building collections from PDF documents.</Text>
+</th>
+<th width="180">
+<Text id="751"><i>www.ra.informatik.uni-stutt gart.de/ <br/>~gosho/pdftohtml</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="752"><i>yaz</i></Text>
+</th>
+<th width="217">
+<Text id="753">Z39.50 client program being used for research in making Greenstone Z39.50 compliant. Progress is reported in the <i>README.gsdl</i> file.</Text>
+</th>
+<th width="180">
+<Text id="754"><i>www.indexdata.dk</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="755">The <i>packages</i> directory, whose contents are shown in Table <CrossRef target="Table" ref="the_packages_directory_1"/>, is where all the code used by Greenstone but written by other research teams resides. All software distributed with Greenstone has been released under the Gnu Public license. The executables produced by these packages are placed in the Greenstone <i>bin</i> directory. Each package is stored in a directory of its own. Their functions vary widely, from indexing and compression to converting Microsoft Word documents to html. Each package has a README file which gives more information about it.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="the_greenstone_runtime_system">
+<Title>
+<Text id="756">The Greenstone runtime system</Text>
+</Title>
+<Content>
+<Text id="757">This chapter describes the Greenstone runtime system so that you can understand, augment and extend its capabilities. The software is written in C++ and makes extensive use of virtual inheritance. If you are unfamiliar with this language you should learn about it before proceeding. Deitel and Deitel (1994) provide a comprehensive tutorial, while Stroustroup (1997) is the definitive reference.</Text>
+<Text id="758">We begin by explaining the design philosophy behind the runtime system since this has a strong bearing on implementation. Then we provide the implementation details, which forms the main part of this chapter. The version of Greenstone described here is the CGI version (Web Library if for Windows users). The Windows Local Library uses the same source code but has a built-in webserver front end. Also, the Local Library is a persistent process.</Text>
+<Section id="process_structure">
+<Title>
+<Text id="759">Process structure</Text>
+</Title>
+<Content>
+<Figure id="overview_of_a_general_greenstone_system">
+<Title>
+<Text id="760">Overview of a general Greenstone system</Text>
+</Title>
+<File width="382" height="335" url="images/Dev_Fig_20.png"/>
+</Figure>
+<Text id="761">Figure <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/> shows several users, represented by computer terminals at the top of the diagram, accessing three Greenstone collections. Before going online, these collections undergo the importing and building processes described in earlier chapters. First, documents, shown at the bottom of the figure, are imported into the XML-compliant Greenstone Archive Format. Then the archive files are built into various searchable indexes and a collection information database that includes the hierarchical structures that support browsing. This done, the collection is ready to go online and respond to requests for information.</Text>
+<Text id="762">Two components are central to the design of the runtime system: âreceptionistsâ and âcollection servers.â From a user's point of view, a receptionist is the point of contact with the digital library. It accepts user input, typically in the form of keyboard entry and mouse clicks; analyzes it; and then dispatches a request to the appropriate collection server (or servers). This locates the requested piece of information and returns it to the receptionist for presentation to the user. Collection servers act as an abstract mechanism that handle the content of the collection, while receptionists are responsible for the user interface.</Text>
+<Figure id="greenstone_system_using_the_null_protocol">
+<Title>
+<Text id="763">Greenstone system using the ânull protocolâ</Text>
+</Title>
+<File width="329" height="424" url="images/Dev_Fig_21.png"/>
+</Figure>
+<Text id="764">As Figure <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/> shows, receptionists communicate with collection servers using a defined protocol. The implementation of this protocol depends on the computer configuration on which the digital library system is running. The most common case, and the simplest, is when there is one receptionist and one collection server, and both run on the same computer. This is what you get when you install the default Greenstone. In this case the two processes are combined to form a single executable (called <i>library</i>), and consequently using the protocol reduces to making function calls. We call this the <i>null protocol</i>. It forms the basis for the standard out-of-the-box Greenstone digital library system. This simplified configuration is illustrated in Figure <CrossRef target="Figure" ref="greenstone_system_using_the_null_protocol"/>, with the receptionist, protocol and collection server bound together as one entity, the <i>library</i> program. The aim of this chapter is to show how it works.</Text>
+<Text id="765">Usually, a âserverâ is a persistent process that, once started, runs indefinitely, responding to any requests that come in. Despite its name, however, the collection server in the null protocol configuration is not a server in this sense. In fact, every time any Greenstone web page is requested, the <i>library</i> program is started up (by the CGI mechanism), responds to the request, and then exits. We call it a âserverâ because it is also designed to work in the more general configuration of Figure <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/>.</Text>
+<Text id="766">Surprisingly, this start-up, process and exit cycle is not as slow as one might expect, and results in a perfectly usable service. However, it is clearly inefficient. There is a mechanism called Fast-CGI (<i>www.fastcgi.com</i>) which provides a middle ground. Using it, the <i>library</i> program can remain in memory at the end of the first execution, and have subsequent sets of CGI arguments fed to it, thus avoiding repeated initialisation overheads and accomplishing much the same behaviour as a server. Using Fast-CGI is an option in Greenstone, and is enabled by recompiling the source code with appropriate libraries.</Text>
+<Text id="767">As an alternative to the null protocol, the Greenstone protocol has also been implemented using the well-known CORBA scheme (Slama <i>et al.</i>, 1999). This uses a unified object oriented paradigm to enable different processes, running on different computer platforms and implemented in different programming languages, to access the same set of distributed objects over the Internet (or any other network). Then, scenarios like Figure <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/> can be fully implemented, with all the receptionists and collection servers running on different computers.</Text>
+<Figure id="graphical_query_interface_to_greenstone">
+<Title>
+<Text id="768">Graphical query interface to Greenstone</Text>
+</Title>
+<File width="397" height="348" url="images/Dev_Fig_22.png"/>
+</Figure>
+<Text id="769">This allows far more sophisticated interfaces to be set up to exactly the same digital library collections. As just one example, Figure <CrossRef target="Figure" ref="graphical_query_interface_to_greenstone"/> shows a graphical query interface, based on Venn diagrams, that lets users manipulate Boolean queries directly. Written in Java, the interface runs locally on the user's own computer. Using CORBA, it accesses a remote Greenstone collection server, written in C++.</Text>
+<Text id="770">The distributed protocol is still being refined and readied for use, and so this manual does not discuss it further (see Bainbridge <i>et al</i>., 2001, for more information).</Text>
+</Content>
+</Section>
+<Section id="conceptual_framework">
+<Title>
+<Text id="771">Conceptual framework</Text>
+</Title>
+<Content>
+<Figure id="generating_the_about_this_collection_page">
+<Title>
+<Text id="772">Generating the âabout this collectionâ page</Text>
+</Title>
+<File width="398" height="354" url="images/Dev_Fig_23.png"/>
+</Figure>
+<Text id="773">Figure <CrossRef target="Figure" ref="generating_the_about_this_collection_page"/> shows the âabout this collectionâ page of a particular Greenstone collection (the Project Gutenberg collection). Look at the URL at the top. The page is generated as a result of running the CGI program <i>library</i>, which is the above-mentioned executable comprising both receptionist and collection server connected by the null protocol. The arguments to <i>library</i> are <i>c=gberg</i>, <i>a=p</i>, and <i>p=about</i>. They can be interpreted as follows:</Text>
+<Indented>
+<Text id="774"><i>For the Project Gutenberg collection (c=gberg), the action is to generate a page (a=p), and the page to generate is called âaboutâ (p=about).</i></Text>
+</Indented>
+<Figure id="greenstone_runtime_system">
+<Title>
+<Text id="775">Greenstone runtime system</Text>
+</Title>
+<File width="534" height="345" url="images/Dev_Fig_24.gif"/>
+</Figure>
+<Text id="776">Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/> illustrates the main parts of the Greenstone runtime system. At the top, the receptionist first initialises its components, then parses the CGI arguments to decide which action to call. In performing the action (which includes further processing of the CGI arguments), the software uses the protocol to access the content of the collection. The response is used to generate a web page, with assistance from the format component and the macro language.</Text>
+<Text id="777">The macro language, which we met in Section <CrossRef target="Section" ref="controlling_the_greenstone_user_interface"/>, is used to provide a Greenstone digital library system with a consistent style, and to create interfaces in different languages. Interacting with the library generates the bare bones of web pages; the macros in <i>GSDLHOME/macros</i> wrap them in flesh.</Text>
+<Text id="778">The Macro Language object in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/> is responsible for reading these files and storing the parsed result in memory. Any action can use this object to expand a macro. It can even create new macro definitions and override existing ones, adding a dynamic dimension to macro use.</Text>
+<Text id="779">The layout of the âabout this collectionâ page (Figure <CrossRef target="Figure" ref="generating_the_about_this_collection_page"/>) is known before runtime, and encoded in the macro file <i>about.dm</i>. Headers, footers, and the background image are not even mentioned because they are located in the <i>Global</i> macro package. However, the specific âaboutâ text for a particular collection is not known in advance, but is stored in the collection information database during the building process. This information is retrieved using the protocol, and stored as <i>_collectionextra_</i> in the <i>Global</i> macro package. Note this macro name is essentially the same name used to express this information in the collection configuration file described in Section <CrossRef target="Section" ref="configuration_file"/>. To generate the content of the page, the <i>_content_</i> macro in the <i>about</i> package (shown in Figure <CrossRef target="Figure" ref="part_of_the_aboutdm_macro_file"/>) is expanded. This in turn expands <i>_textabout_</i>, which itself accesses <i>_collectionextra_</i>, which had just been dynamically placed there.</Text>
+<Text id="780">One further important ingredient is the Format object. Format statements in the collection configuration file affect the presentation of particular pieces of information, as described in Section <CrossRef target="Section" ref="formatting_greenstone_output"/>. They are handled by the Format object in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/>. This object's main task is to parse and evaluate statements such as the format strings in Figure <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>. As we learned in Section <CrossRef target="Section" ref="formatting_greenstone_output"/>, these can include references to metadata in square brackets (e.g. <i>[Title]</i>), which need to be retrieved from the collection server. Interaction occurs between the Format object and the Macro Language object, because format statements can include macros that, when expanded, include metadata, which when expanded include macros, and so on.</Text>
+<Text id="781">At the bottom of Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/>, the collection server also goes through an initialisation process, setting up Filter and Source objects to respond to incoming protocol requests, and a Search object to assist in this task. Ultimately these access the indexes and the collection information database, both formed during collection building.</Text>
+<Text id="782">Ignoring blank lines, the receptionist contains 15,000 lines of code. The collection server contains only 5,000 lines (75% of which are taken up by header files). The collection server is more compact because content retrieval is accomplished through two pre-compiled programs. mg, a full-text retrieval system, is used for searching, and gdbm, a database management system, is used to hold the collection information database.</Text>
+<Text id="783">To encourage extensibility and flexibility, Greenstone uses inheritance widelyâin particular, within Action, Filter, Source, and Search. For a simple digital library dedicated to text-based collections, this means that you need to learn slightly more to program the system. However, it also means that mg and gdbm could easily be replaced should the need arise. Furthermore, the software architecture is rich enough to support full multimedia capabilities, such as controlling the interface through speech input, or submitting queries as graphically drawn pictures.</Text>
+</Content>
+</Section>
+<Section id="how_the_conceptual_framework_fits_together">
+<Title>
+<Text id="784">How the conceptual framework fits together</Text>
+</Title>
+<Content>
+<Text id="785">Sections <CrossRef target="Section" ref="collection_server"/> and <CrossRef target="Section" ref="receptionist"/> explain the operation of the collection server and receptionist in more detail, expanding on each module in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/> and describing how it is implemented. It is helpful to first work through examples of a user interacting with Greenstone, and describe what goes on behind the scenes. For the moment, we assume that all objects are correctly initialised. Initialisation is a rather intricate procedure that we revisit in Section <CrossRef target="Section" ref="initialisation"/>.</Text>
+<Subsection id="performing_a_search">
+<Title>
+<Text id="786">Performing a search</Text>
+</Title>
+<Content>
+<Figure id="searching_gutenberg_for_darcy">
+<Title>
+<Text id="787">Searching Gutenberg for <i>Darcy</i></Text>
+</Title>
+<File width="396" height="353" url="images/Dev_Fig_25.png"/>
+</Figure>
+<Text id="788">When a user enters a query by pressing <i>Begin search</i> on the search page, a new Greenstone action is invoked, which ends up by generating a new html page using the macro language. Figure <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/> shows the result of searching the Project Gutenberg collection for the name <i>Darcy</i>. Hidden within the html of the original search page is the statement <i>a=q</i>. When the search button is pressed this statement is activated, and sets the new action to be <i>queryaction</i>. Executing <i>queryaction</i> sets up a call to the designated collection's Filter object (<i>c=gberg</i>) through the protocol.</Text>
+<Text id="789">Filters are an important basic function of collection servers. Tailored for both searching and browsing activities, they provide a way of selecting a subset of information from a collection. In this case, the <i>queryaction</i> sets up a filter request by:</Text>
+<BulletList>
+<Bullet>
+<Text id="790">setting the filter request type to be <i>QueryFilter</i>(Section <CrossRef target="Section" ref="collection_server"/> describes the different filter types);</Text>
+</Bullet>
+<Bullet>
+<Text id="791">storing the user's search preferencesâcase-folding, stemming and so onâin the filter request;</Text>
+</Bullet>
+<Bullet>
+<Text id="792">calling the <i>filter()</i> function using the null protocol.</Text>
+</Bullet>
+</BulletList>
+<Text id="793">Calls to the protocol are synchronous. The receptionist is effectively blocked until the filter request has been processed by the collection server and any data generated has been returned.</Text>
+<Text id="794">When a protocol call of type <i>QueryFilter</i> is made, the Filter object (in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/>) decodes the options and makes a call to the Search object, which uses mg to do the actual search. The role of the Search object is to provide an abstract program interface that supports searching, regardless of the underlying search tool being used. The format used for returning results also enforces abstraction, requiring the Search object to translate the data generated by the search tool into a standard form.</Text>
+<Text id="795">Once the search results have been returned to the receptionist, the action proceeds by formatting the results for display, using the Format object and the Macro Language. As Figure <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/> shows, this involves generating: the standard Greenstone header, footer, navigation bar and background; repeating the main part of the query page just beneath the navigation bar; and displaying a book icon, title and author for each matching entry. The format of this last part is governed by the <i>format SearchVList</i> statement in the collection configuration file. Before title and author metadata can be displayed, they must be retrieved from the collection server. This requires further calls to the protocol, this time using <i>BrowseFilter</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="retrieving_a_document">
+<Title>
+<Text id="796">Retrieving a document</Text>
+</Title>
+<Content>
+<Text id="797">Following the above query for <i>Darcy</i>, consider what happens when a document is displayed. Figure <CrossRef target="Figure" ref="the_golf_course_mystery"/> shows the result of clicking on the icon beside <i>The Golf Course Mystery</i> in Figure <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/>.</Text>
+<Figure id="the_golf_course_mystery">
+<Title>
+<Text id="798"><i>The Golf Course Mystery</i></Text>
+</Title>
+<File width="393" height="349" url="images/Dev_Fig_26.png"/>
+</Figure>
+<Text id="799">The source text for the Gutenberg collection comprises one long file per book. At build time, these files are split into separate pages every 200 lines or so, and relevant information for each page is stored in the indexes and collection information database. The top of Figure <CrossRef target="Figure" ref="the_golf_course_mystery"/> shows that this book contains 104 computer-generated pages, and below it is the beginning of page one: who entered it, the title, the author, and the beginnings of a table of contents (this table forms part of the Gutenberg source text, and was not generated by Greenstone). At the top left are buttons that control the document's appearance: just one page or the whole document; whether query term highlighting is on or off; and whether or not the book should be displayed in its own window, detached from the main searching and browsing activity. At the top right is a navigation aid that supports direct access to any page in the book: simply type in the page number and press the âgo to pageâ button. Alternatively, the next and previous pages are retrieved by clicking on the arrow icons either side of the page selection widget.</Text>
+<Text id="800">The action for retrieving documents, <i>documentaction</i>, is specified by setting <i>a=d</i> and takes several additional arguments. Most important is the document to retrieve: this is specified through the <i>d</i> variable. In Figure <CrossRef target="Figure" ref="the_golf_course_mystery"/> it is set to <i>d=HASH51e598821ed6cbbdf0942b.1</i> to retrieve the first page of the document with the identifier <i>HASH51e598821ed6cbbdf0942b</i>, known in more friendly terms as <i>The Golf Course Mystery</i>. There are further variables: whether query term highlighting is on or off (<i>hl</i>) and which page within a book is displayed (<i>gt</i>). These variables are used to support the activities offered by the buttons on the page in Figure <CrossRef target="Figure" ref="the_golf_course_mystery"/>, described above. Defaults are used if any of these variables are omitted.</Text>
+<Text id="801">The action follows a similar procedure to <i>queryaction</i>: appraise the CGI arguments, access the collection server using the protocol, and use the result to generate a web page. Options relating to the document are decoded from the CGI arguments and stored in the object for further work. To retrieve the document from the collection server, only the document identifier is needed to set up the protocol call to <i>get_document()</i>. Once the text is returned, considerable formatting must be done. To achieve this, the code for <i>documentaction</i> accesses the stored arguments and makes use of the Format object and the Macro Language.</Text>
+</Content>
+</Subsection>
+<Subsection id="browsing_a_hierarchical_classifier">
+<Title>
+<Text id="802">Browsing a hierarchical classifier</Text>
+</Title>
+<Content>
+<Text id="803">Figure <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/> shows an example of browsing, where the user has chosen <i>Titles A-Z</i> and accessed the hyperlink for the letter <i>K</i>. The action that supports this is also <i>documentaction</i>, given by the CGI argument <i>a=d</i> as before. However, whereas before a <i>d</i> variable was included, this time there is none. Instead, the node within the browsable classification hierarchy to display is specified in the variable <i>cl</i>. In our case this represents titles grouped under the letter <i>K</i>. This list was formed at build time and stored in the collection information database.</Text>
+<Figure id="browsing_titles_in_the_gutenberg_collection">
+<Title>
+<Text id="804">Browsing titles in the Gutenberg collection</Text>
+</Title>
+<File width="394" height="351" url="images/Dev_Fig_27.png"/>
+</Figure>
+<Text id="805">Records that represent classifier nodes in the database use the prefix <i>CL</i>, followed by numbers separated by periods (.) to designate where they lie within the nested structure. Ignoring the search button (leftmost in the navigation bar), classifiers are numbered sequentially in increasing order, left to right, starting at 1. Thus the top level classifier node for titles in our example is <i>CL1</i> and the page sought is generated by setting <i>cl=CL1.11</i>. This can be seen in the URL at the top of Figure <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/>.</Text>
+<Text id="806">To process a <i>cl</i> document request, the Filter object is used to retrieve the node over the protocol. Depending on the data returned, further protocol calls are made to retrieve document metadata. In this case, the titles of the books are retrieved. However, if the node were an interior one whose children are themselves nodes, the titles of the child nodes would be retrieved. From a coding point of view this amounts to the same thing, and is handled by the same mechanism.</Text>
+<Text id="807">Finally, all the retrieved information is bound together, using the macro language, to produce the web page shown in Figure <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/>.</Text>
+</Content>
+</Subsection>
+<Subsection id="generating_the_home_page">
+<Title>
+<Text id="808">Generating the home page</Text>
+</Title>
+<Content>
+<Figure id="greenstone_home_page">
+<Title>
+<Text id="809">Greenstone home page</Text>
+</Title>
+<File width="397" height="393" url="images/Dev_Fig_28.png"/>
+</Figure>
+<Text id="810">As a final example, we look at generating the Greenstone home page. Figure <CrossRef target="Figure" ref="greenstone_home_page"/> showsâfor the default Greenstone installation âits home page after some test collections have been installed. Its URL, which you can see at the top of the screen, includes the arguments <i>a=p</i> and <i>p=home</i>. Thus, like the âabout this collectionâ page, it is generated by a <i>pageaction</i> (<i>a=p</i>), but this time the page to produce is <i>home</i>(<i>p=home</i>). The macro language, therefore, accesses the content of <i>home.dm</i>. There is no need to specify a collection (with the <i>c</i> variable) in this case.</Text>
+<Text id="811">The purpose of the home page is to show what collections are available. Clicking on an icon takes the user to the âabout this collectionâ page for that collection. The menu of collections is dynamically generated every time the page is loaded, based on the collections that are in the file system at that time. When a new one comes online, it automatically appears on the home page when that page is reloaded (provided the collection is stipulated to be âpublicâ).</Text>
+<Text id="812">To do this the receptionist uses the protocol (of course). As part of appraising the CGI arguments, <i>pageaction</i> is programmed to detect the special case when <i>p=home</i>. Then, the action uses the protocol call <i>get_collection_list()</i> to establish the current set of online collections. For each of these it calls <i>get_collectinfo()</i> to obtain information about it. This information includes whether the collection is publicly available, what the URL is for the collection's icon (if any), and the collection's full name. This information is used to generate an appropriate entry for the collection on the home page.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="source_code">
+<Title>
+<Text id="813">Source code</Text>
+</Title>
+<Content>
+<Table id="standalone_programs_included_in_greenstone">
+<Title>
+<Text id="814">Standalone programs included in Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="815"><i>setpasswd/</i></Text>
+</th>
+<th width="397">
+<Text id="816">Password support for Windows.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="817"><i>getpw/</i></Text>
+</th>
+<th width="397">
+<Text id="818">Password support for Unix.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="819"><i>txt2db/</i></Text>
+</th>
+<th width="397">
+<Text id="820">Convert an XML-like ASCII text format to Gnu's database format.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="821"><i>db2txt/</i></Text>
+</th>
+<th width="397">
+<Text id="822">Convert the Gnu database format to an XML-like ASCII text format.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="823"><i>phind/</i></Text>
+</th>
+<th width="397">
+<Text id="824">Hierarchical phrase browsing tool.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="825"><i>hashfile/</i></Text>
+</th>
+<th width="397">
+<Text id="826">Compute unique document ID based on content of file.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="827"><i>mgpp/</i></Text>
+</th>
+<th width="397">
+<Text id="828">Rewritten and updated version of Managing Gigabytes package in C++.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="829"><i>w32server/</i></Text>
+</th>
+<th width="397">
+<Text id="830">Local library server for Windows.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="831"><i>checkis/</i></Text>
+</th>
+<th width="397">
+<Text id="832">Specific support for installing Greenstone under Windows.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="833">The source code for the runtime system resides in <i>GSDLHOME/src</i>. It occupies two subdirectories, <i>recpt</i> for the receptionist's code and <i>colservr</i> for the collection server's. Greenstone runs on Windows systems right down to Windows 3.1, and unfortunately this imposes an eight-character limit on file and directory names. This explains why cryptic abbreviations like <i>recpt</i> and <i>colservr</i> are used. The remaining subdirectories include standalone utilities, mostly in support of the building process. They are listed in Table <CrossRef target="Table" ref="standalone_programs_included_in_greenstone"/>.</Text>
+<Text id="834">Another directory, <i>GSDLHOME/lib</i>, includes low-level objects that are used by both receptionist and collection server. This code is described in Section <CrossRef target="Section" ref="common_greenstone_types"/>.</Text>
+<Text id="835">Greenstone makes extensive use of the Standard Template Library (STL), a widely-used C++ library from Silicon Graphics (<i>www.sgi.com</i>) that is the result of many years of design and development. Like all programming libraries it takes some time to learn. Appendix A gives a brief overview of key parts that are used throughout the Greenstone code. For a fuller description, consult the official STL reference manual, available online at <i>www.sgi.com</i>, or one of the many STL textbooks, for example Josuttis (1999).</Text>
+</Content>
+</Section>
+<Section id="common_greenstone_types">
+<Title>
+<Text id="836">Common Greenstone types</Text>
+</Title>
+<Content>
+<Text id="837">The objects defined in <i>GSDLHOME/lib</i> are low-level Greenstone objects, built on top of STL, which pervade the entire source code. First we describe <i>text_t</i>, an object used to represent Unicode text, in some detail. Then we summarize the purpose of each library file.</Text>
+<Subsection id="the_text_t_object">
+<Title>
+<Text id="838">The text_t object</Text>
+</Title>
+<Content>
+<Text id="839">Greenstone works with multiple languages, both for the content of a collection and its user interface. To support this, Unicode is used throughout the source code. The underlying object that realises a Unicode string is <i>text_t</i>.</Text>
+<Figure id="the_text_t_api" class="withLineNumber">
+<Title>
+<Text id="840">The <i>text_t</i> API (abridged)</Text>
+</Title>
+<CodeLine>typedef vector&lt;unsigned short&gt; usvector;</CodeLine>
+<CodeLine/>
+<CodeLine>class text_t {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>usvector text;</CodeLine>
+<CodeLine>unsigned short encoding; // 0 = unicode, 1 = other</CodeLine>
+<CodeLine/>
+<CodeLine>public:</CodeLine>
+<CodeLine>   // constructors</CodeLine>
+<CodeLine>   text_t ();</CodeLine>
+<CodeLine>   text_t (int i);</CodeLine>
+<CodeLine>   text_t (char *s); // assumed to be a normal c string</CodeLine>
+<CodeLine/>
+<CodeLine>   void setencoding (unsigned short theencoding);</CodeLine>
+<CodeLine>   unsigned short getencoding ();</CodeLine>
+<CodeLine/>
+<CodeLine>   // STL container support</CodeLine>
+<CodeLine>   iterator begin ();</CodeLine>
+<CodeLine>   iterator end ();</CodeLine>
+<CodeLine/>
+<CodeLine>   void erase(iterator pos);</CodeLine>
+<CodeLine>   void push_back(unsigned short c);</CodeLine>
+<CodeLine>   void pop_back();</CodeLine>
+<CodeLine/>
+<CodeLine>   void reserve (size_type n);</CodeLine>
+<CodeLine/>
+<CodeLine>   bool empty () const {return text.empty();}</CodeLine>
+<CodeLine>   size_type size() const {return text.size();}</CodeLine>
+<CodeLine/>
+<CodeLine>   // added functionality</CodeLine>
+<CodeLine>   void clear ();</CodeLine>
+<CodeLine>   void append (const text_t &amp;t);</CodeLine>
+<CodeLine/>
+<CodeLine>   // support for integers</CodeLine>
+<CodeLine>   void appendint (int i);</CodeLine>
+<CodeLine>   void setint (int i);</CodeLine>
+<CodeLine>   int getint () const;</CodeLine>
+<CodeLine/>
+<CodeLine>   // support for arrays of chars</CodeLine>
+<CodeLine>   void appendcarr (char *s, size_type len);</CodeLine>
+<CodeLine>   void setcarr (char *s, size_type len);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="841">Unicode uses two bytes to store each character. Figure <CrossRef target="Figure" ref="the_text_t_api"/> shows the main features of the <i>text_t</i> Application Program Interface (API). It fulfils the two-byte requirement using the C++ built-in type <i>short</i>, which is defined to be a two byte integer. The data type central to the <i>text_t</i> object is a dynamic array of unsigned shorts built using the STL declaration <i>vector&lt;unsigned short&gt;</i> and given the abbreviated name <i>usvector</i>.</Text>
+<Text id="842">The constructor functions (lines 10â12) explicitly support three forms of initialisation: construction with no parameters, which generates an empty Unicode string; construction with an integer parameter, which generates a Unicode text version of the numeric value provided; and construction with a <i>char*</i> parameter, which treats the argument as a null-terminated C++ string and generates a Unicode version of it.</Text>
+<Text id="843">Following this, most of the detail (lines 17â28) is taken up maintaining an STL vector-style container: <i>begin()</i>, <i>end()</i>, <i>push_back()</i>, <i>empty()</i> and so forth. There is also support for clearing and appending strings, as well as for converting an integer value into a Unicode text string, and returning the corresponding integer value of text that represents a number.</Text>
+<Figure id="overloaded_operators_to_text_t" class="withLineNumber">
+<Title>
+<Text id="844">Overloaded operators to <i>text_t</i></Text>
+</Title>
+<CodeLine>class text_t {</CodeLine>
+<CodeLine>   // ...</CodeLine>
+<CodeLine>   public:</CodeLine>
+<CodeLine>   text_t &amp;operator=(const text_t &amp;x);</CodeLine>
+<CodeLine>   text_t &amp;operator+= (const text_t &amp;t);</CodeLine>
+<CodeLine>   reference operator[](size_type n);</CodeLine>
+<CodeLine/>
+<CodeLine>   text_t &amp;operator=(int i);</CodeLine>
+<CodeLine>   text_t &amp;operator+= (int i);^ \\</CodeLine>
+<CodeLine>   text_t &amp;operator= (char *s);</CodeLine>
+<CodeLine>   text_t &amp;operator+= (char *s);</CodeLine>
+<CodeLine/>
+<CodeLine>   friend inline bool operator!=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator==(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&lt; (const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&gt; (const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&gt;=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&lt;=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   // ...</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="845">There are many overloaded operators that do not appear in Figure <CrossRef target="Figure" ref="the_text_t_api"/>. To give a flavour of the operations supported, these are shown in Figure <CrossRef target="Figure" ref="overloaded_operators_to_text_t"/>. Line 4 supports assignment of one <i>text_t</i> object to another, and line 5 overloads the <i>+=</i> operator to provide a more natural way to append one <i>text_t</i> object to the end of another. It is also possible, through line 6, to access a particular Unicode character (represented as a <i>short</i>) using array subscripting [ ]. Assign and append operators are also provided for integers and C++ strings. Lines 12â18 provide Boolean operators for comparing two <i>text_t</i> objects: equals, does not equal, precedes alphabetically, and so on.</Text>
+<Text id="846">Member functions that take <i>const</i> arguments instead of non- <i>const</i> ones are also provided (but not shown here). Such repetition is routine in C++ objects, making the API fatter but no bigger conceptually. In reality, many of these functions are implemented as single in-line statements. For more detail, refer to the source file <i>GSDLHOME/lib/text_t.h</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_greenstone_library_code">
+<Title>
+<Text id="847">The Greenstone library code</Text>
+</Title>
+<Content>
+<Text id="848">The header files in <i>GSDLHOME/lib</i> include a mixture of functions and objects that provide useful support for the Greenstone runtime system. Where efficiency is of concern, functions and member functions are declared <i>inline</i>. For the most part, implementation details are contained within a header file's <i>.cpp</i> counterpart.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="100">
+<Text id="849"><b>cfgread.h</b></Text>
+</th>
+<th width="450">
+<Text id="850">Functions to read and write configuration files. For example, <i>read_cfg_line()</i> takes as arguments the input stream to use and the <i>text_tarray</i> (shorthand for <i>vector&lt;text_t&gt;</i>) to fill out with the data that is read.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="851"><b>display.h</b></Text>
+</th>
+<th width="450">
+<Text id="852">A sophisticated object used by the receptionist for setting, storing and expanding macros, plus supporting types. Section <CrossRef target="Section" ref="receptionist"/> gives further details.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="853"><b>fileutil.h</b></Text>
+</th>
+<th width="450">
+<Text id="854">Function support for several file utilities in an operating system independent way. For example, <i>filename_cat()</i> takes up to six <i>text_t</i> arguments and returns a <i>text_t</i> that is the result of concatenating the items together using the appropriate directory separator for the current operating system.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="855"><b>gsdlconf.h</b></Text>
+</th>
+<th width="450">
+<Text id="856">System-specific functions that answer questions such as: does the operating system being used for compilation need to access <i>strings.h</i> as well as <i>string.h</i>? Are all the appropriate values for file locking correctly defined?</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="857"><b>gsdltimes.h</b></Text>
+</th>
+<th width="450">
+<Text id="858">Function support for date and times. For example, <i>time2text()</i> takes computer time, expressed as the number of seconds that have elapsed since 1 January 1970, and converts it into the form YYYY/MM/DD hh:mm:ss, which it returns as type <i>text_t</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="859"><b>gsdltools.h</b></Text>
+</th>
+<th width="450">
+<Text id="860">Miscellaneous support for the Greenstone runtime system: clarify if littleEndian or bigEndian; check whether Perl is available; execute a system command (with a few bells and whistles); and escape special macro characters in a <i>text_t</i> string.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="861"><b>gsdlunicode.h</b></Text>
+</th>
+<th width="450">
+<Text id="862">A series of inherited objects that support processing Unicode <i>text_t</i> strings through IO streams, such as Unicode to UTF-8 and <i>vice versa</i>; and the removal of zero-width spaces. Support for map files is also provided through the <i>mapconvert</i> object, with mappings loaded from <i>GSDLHOME/mappings</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="863"><b>text_t.h</b></Text>
+</th>
+<th width="450">
+<Text id="864">Primarily the Unicode text object described above. It also provides two classes for converting streams: <i>inconvertclass</i> and <i>outconvertclass</i>. These are the base classes used in <i>gsdlunicode.h</i>.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="collection_server">
+<Title>
+<Text id="865">Collection server</Text>
+</Title>
+<Content>
+<Text id="866">Now we systematically explain all the objects in the conceptual framework of Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/>. We start at the bottom of the diagramâwhich is also the foundations of the systemâwith Search, Source and Filter, and work our way up through the protocol layer and on to the central components in the receptionist: Actions, Format and Macro Language. Then we focus on object initialisation, since this is easier to understand once the role of the various objects is known.</Text>
+<Text id="867">Most of the classes central to the conceptual framework are expressed using virtual inheritance to aid extensibility. With virtual inheritance, inherited objects can be passed around as their base class, but when a member function is called it is the version defined in the inherited object that is invoked. By ensuring that the Greenstone source code uses the base class throughout, except at the point of object construction, this means that different implementationsâusing, perhaps, radically different underlying technologiesâcan be slotted into place easily.</Text>
+<Text id="868">For example, suppose a base class called <i>BaseCalc</i> provides basic arithmetic: add, subtract, multiply and divide. If all its functions are declared virtual, and arguments and return types are all declared as strings, we can easily implement inherited versions of the object. One, called <i>FixedPrecisionCalc</i>, might use C library functions to convert between strings and integers and back again, implementing the calculations using the standard arithmetic operators: <i>+</i>, â, <i>*</i>, and <i>/</i>. Another, called <i>InfinitePrecisionCalc</i>, might access the string arguments a character at a time, implementing arithmetic operations that are in principal infinite in their precision. By writing a main program that uses <i>BaseCalc</i> throughout, the implementation can be switched between fixed precision and infinite precision by editing just one line: the point where the calculator object is constructed.</Text>
+<Subsection id="the_search_object">
+<Title>
+<Text id="869">The Search object</Text>
+</Title>
+<Content>
+<Figure id="search_base_class_api">
+<Title>
+<Text id="870">Search base class API</Text>
+</Title>
+<CodeLine>class searchclass {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   searchclass ();</CodeLine>
+<CodeLine>   virtual ~searchclass ();</CodeLine>
+<CodeLine>   // the index directory must be set before any searching</CodeLine>
+<CodeLine>   // is done</CodeLine>
+<CodeLine>   virtual void setcollectdir (const text_t &amp;thecollectdir);</CodeLine>
+<CodeLine>   // the search results are returned in queryresults</CodeLine>
+<CodeLine>   // search returns 'true' if it was able to do a search</CodeLine>
+<CodeLine>   virtual bool search(const queryparamclass &amp;queryparams,</CodeLine>
+<CodeLine>                         queryresultsclass &amp;queryresults)=0;</CodeLine>
+<CodeLine>   // the document text for 'docnum' is placed in 'output'</CodeLine>
+<CodeLine>   // docTargetDocument returns 'true' if it was able to</CodeLine>
+<CodeLine>   // try to get a document</CodeLine>
+<CodeLine>   // collection is needed to see if an index from the</CodeLine>
+<CodeLine>   // collection is loaded. If no index has been loaded</CodeLine>
+<CodeLine>   // defaultindex is needed to load one</CodeLine>
+<CodeLine>   virtual bool docTargetDocument(const text_t &amp;defaultindex,</CodeLine>
+<CodeLine>                                               const text_t &amp;defaultsubcollection,</CodeLine>
+<CodeLine>                                               const text_t &amp;defaultlanguage,</CodeLine>
+<CodeLine>                                               const text_t &amp;collection,</CodeLine>
+<CodeLine>                                               int docnum,</CodeLine>
+<CodeLine>                                               text_t &amp;output)=0;</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   querycache *cache;</CodeLine>
+<CodeLine>   text_t collectdir; // the collection directory</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="871">Figure <CrossRef target="Figure" ref="search_base_class_api"/> shows the base class API for the Search object in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/>. It defines two virtual member functions: <i>search()</i> and <i>docTargetDocument()</i>. As signified by the <i>=0</i> that follows the argument declaration, these are <i>pure</i> functionsâmeaning that a class that inherits from this object must implement both (otherwise the compiler will complain).</Text>
+<Text id="872">The class also includes two protected data fields: <i>collectdir</i> and <i>cache</i>. A Search object is instantiated for a particular collection, and the <i>collectdir</i> field is used to store where on the file system that collection (and more importantly its index files) resides. The <i>cache</i> field retains the result of a query. This is used to speed up subsequent queries that duplicate the query (and its settings). While identical queries may seem unlikely, in fact they occur on a regular basis. The Greenstone protocol is stateless. To generate a results page like Figure <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/> but for matches 11â20 of the same query, the search is transmitted again, this time specifying that documents 11â20 are returned. Caching makes this efficient, because the fact that the search has already been performed is detected and the results are lifted straight from the cache.</Text>
+<Text id="873">Both data fields are applicable to every inherited object that implements a searching mechanism. This is why they appear in the base class, and are declared within a protected section of the class so that inherited classes can access them directly.</Text>
+</Content>
+</Subsection>
+<Subsection id="search_and_retrieval_with_mg">
+<Title>
+<Text id="874">Search and retrieval with MG</Text>
+</Title>
+<Content>
+<Text id="875">Greenstone uses MG (short for Managing Gigabytes, see Witten <i>et al</i>., 1999) to index and retrieve documents, and the source code is included in the <i>GSDLHOME/packages</i> directory. MG uses compression techniques to maximise disk space utilisation without compromising execution speed. For a collection of English documents, the compressed text and full text indexes together typically occupy one third the space of the original uncompressed text alone. Search and retrieval is often quicker than the equivalent operation on the uncompressed version, because there are fewer disk operations.</Text>
+<Figure id="api_for_direct_access_to_mg">
+<Title>
+<Text id="876">API for direct access to MG (abridged)</Text>
+</Title>
+<CodeLine>enum result_kinds {</CodeLine>
+<CodeLine>   result_docs,           // Return the documents found in last search</CodeLine>
+<CodeLine>   result_docnums,     // Return document id numbers and weights</CodeLine>
+<CodeLine>   result_termfreqs, // Return terms and frequencies</CodeLine>
+<CodeLine>   result_terms           // Return matching query terms</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>int mgq_ask(char *line);</CodeLine>
+<CodeLine>int mgq_results(enum result_kinds kind, int skip, int howmany,</CodeLine>
+<CodeLine>                               int (*sender)(char *, int, int, float, void *),</CodeLine>
+<CodeLine>                               void *ptr);</CodeLine>
+<CodeLine>int mgq_numdocs(void);</CodeLine>
+<CodeLine>int mgq_numterms(void);</CodeLine>
+<CodeLine>int mgq_equivterms(unsigned char *wordstem,</CodeLine>
+<CodeLine>                           int (*sender)(char *, int, int, float, void *),</CodeLine>
+<CodeLine>                           void *ptr);</CodeLine>
+<CodeLine>int mgq_docsretrieved (int *total_retrieved, int *is_approx);</CodeLine>
+<CodeLine>int mgq_getmaxstemlen ();</CodeLine>
+<CodeLine>void mgq_stemword (unsigned char *word);</CodeLine>
+</Figure>
+<Text id="877">MG is normally used interactively by typing commands from the command line, and one way to implement <i>mgsearchclass</i> would be to use the C library <i>system()</i> call within the object to issue the appropriate mg commands. A more efficient approach, however, is to tap directly into the mg code using function calls. While this requires a deeper understanding of the mg code, much of the complexity can be hidden behind a new API that becomes the point of contact for the object <i>mgsearchclass</i>. This is the role of <i>colserver/mgq.c</i>, whose API is shown in Figure <CrossRef target="Figure" ref="api_for_direct_access_to_mg"/>.</Text>
+<Text id="878">The way to supply parameters to mg is via <i>mgq_ask()</i>, which takes text options in a format identical to that used at the command line, such as:</Text>
+<CodeLine>mgq_ask( ".set casefold off ");</CodeLine>
+<Text id="879">It is also used to invoke a query. Results are accessed through <i>mgq_results</i>, which takes a pointer to a function as its fourth parameter. This provides a flexible way of converting the information returned in mg data structures into those needed by <i>mgsearchclass</i>. Calls such as <i>mgq_numdocs()</i>, <i>mgq_numterms()</i>, and <i>mgq_docsretrieved()</i> also return information, but this time more tightly prescribed. The last two give support for stemming.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_source_object">
+<Title>
+<Text id="880">The Source object</Text>
+</Title>
+<Content>
+<Figure id="source_base_class_api">
+<Title>
+<Text id="881">Source base class API</Text>
+</Title>
+<CodeLine>class sourceclass {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   sourceclass ();</CodeLine>
+<CodeLine>   virtual ~sourceclass ();</CodeLine>
+<CodeLine>   // configure should be called once for each configuration line</CodeLine>
+<CodeLine>   virtual void configure (const text_t &amp;key, const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   // init should be called after all the configuration is done but</CodeLine>
+<CodeLine>   // before any other methods are called</CodeLine>
+<CodeLine>   virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   // translate_OID translates OIDs using " .pr " , . " fc " etc.</CodeLine>
+<CodeLine>   virtual bool translate_OID (const text_t &amp;OIDin, text_t &amp;OIDout, comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   // get_metadata fills out the metadata if possible, if it is not</CodeLine>
+<CodeLine>   // responsible for the given OID then it return s false.</CodeLine>
+<CodeLine>   virtual bool get_metadata (const text_t &amp;requestParams, const text_t &amp;refParams,</CodeLine>
+<CodeLine>                           bool getParents, const text_tset &amp;fields, const text_t &amp;OID,</CodeLine>
+<CodeLine>                           MetadataInfo_tmap &amp;metadata, comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool get_document (const text_t &amp;OID, text_t &amp;doc, </CodeLine>
+<CodeLine>                           comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="882">The role of Source in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/> is to access document metadata and document text, and its base class API is shown in Figure <CrossRef target="Figure" ref="source_base_class_api"/>. A member function maps to each task: <i>get_metadata()</i> and <i>get_document()</i> respectively. Both are declared <i>virtual</i>, so the version provided by a particular implementation of the base class is called at runtime. One inherited version of this object uses gdbm to implement <i>get_metadata()</i> and mg to implement <i>get_document()</i>: we detail this version below.</Text>
+<Text id="883">Other member functions seen in Figure <CrossRef target="Figure" ref="source_base_class_api"/> are <i>configure()</i>, <i>init()</i>, and <i>translate_OID()</i>. The first two relate to the initialisation process described in Section <CrossRef target="Section" ref="initialisation"/>.</Text>
+<Text id="884">The remaining one, <i>translate_OID()</i>, handles the syntax for expressing document identifiers. In Figure <CrossRef target="Figure" ref="the_golf_course_mystery"/> we saw how a page number could be appended to a document identifier to retrieve just that page. This was possible because pages were stored as âsectionsâ when the collection was built. Appending â.1â to an OID retrieves the first section of the corresponding document. Sections can be nested, and are accessed by concatenating section numbers separated by periods.</Text>
+<Text id="885">As well as hierarchical section numbers, the document identifier syntax supports a form of relative access. For the current section of a document it is possible to access the <i>first child</i> by appending <i>.fc</i>, the <i>last child</i> by appending <i>.lc</i>, the <i>parent</i> by appending <i>.pr</i>, the <i>next sibling</i> by appending <i>.ns</i>, and the <i>previous sibling</i> by appending <i>.ps</i>.</Text>
+<Text id="886">The <i>translate_OID()</i> function uses parameters <i>OIDin</i> and <i>OIDout</i> to hold the source and result of the conversion. It takes two further parameters, <i>err</i> and <i>logout</i>. These communicate any error status that may arise during the translation operation, and determine where to send logging information. The parameters are closely aligned with the protocol, as we shall see in Section <CrossRef target="Section" ref="protocol"/>.</Text>
+<Part id="database_retrieval_with_gdbm">
+<Title>
+<Text id="887">Database retrieval with gdbm</Text>
+</Title>
+<Content>
+<Text id="888">GDBM is the Gnu database manager program (<i>www.gnu.org</i>). It implements a flat record structure of key/data pairs, and is backwards compatible with dbm and ndbm. Operations include storage, retrieval and deletion of records by key, and an unordered traversal of all keys.</Text>
+<Figure id="gdbm_database_for_the_gutenberg_collection">
+<Title>
+<Text id="889">Gdbm database for the Gutenberg collection (excerpt)</Text>
+</Title>
+<CodeLine>[HASH01d7b30d4827b51282919e9b]</CodeLine>
+<CodeLine>&lt;doctype&gt;         doc</CodeLine>
+<CodeLine>&lt;hastxt&gt;           0</CodeLine>
+<CodeLine>&lt;Title&gt;             The Winter's Tale</CodeLine>
+<CodeLine>&lt;Creator&gt;         William Shakespeare</CodeLine>
+<CodeLine>&lt;archivedir&gt;   HASH01d7/b30d4827.dir</CodeLine>
+<CodeLine>&lt;thistype&gt;       Invisible</CodeLine>
+<CodeLine>&lt;childtype&gt;     Paged</CodeLine>
+<CodeLine>&lt;contains&gt;        " .1; " .2; " .3; " .4; " .5; " .6; " .7; " .8; " .9; " .10; " .11; " .12;            \ <br/>                           " .13; " .14; " .15; " .16; " .17; " .18; " .19; " .20; " .21; " .22;            \ <br/>                           " .23; " .24; " .25; " .26; " .27; " .28; " .29; " .30; " .31; " .32;            \ <br/>                           " .33; " .34; " .35</CodeLine>
+<CodeLine>&lt;docnum&gt;           168483</CodeLine>
+<CodeLine>âââââââââââââââââââââââ-</CodeLine>
+<CodeLine>[CL1]</CodeLine>
+<CodeLine>&lt;doctype&gt;         classify</CodeLine>
+<CodeLine>&lt;hastxt&gt;           0</CodeLine>
+<CodeLine>&lt;childtype&gt;     HList</CodeLine>
+<CodeLine>&lt;Title&gt;             Title</CodeLine>
+<CodeLine>&lt;numleafdocs&gt; 1818</CodeLine>
+<CodeLine>&lt;thistype&gt;       Invisible</CodeLine>
+<CodeLine>&lt;contains&gt;       " .1; " .2; " .3; " .4; " .5; " .6; " .7; " .8; " .9; " .10; " .11; " .12;          \ <br/>                           " .13; " .14; " .15; " .16; " .17; " .18; " .19; " .20; " .21; " .22;          \ <br/>                            " .23; " .24</CodeLine>
+<CodeLine>âââââââââââââââââââââââ-</CodeLine>
+<CodeLine>[CL1.1]</CodeLine>
+<CodeLine>&lt;doctype&gt;         classify</CodeLine>
+<CodeLine>&lt;hastxt&gt;           0</CodeLine>
+<CodeLine>&lt;childtype&gt;     VList</CodeLine>
+<CodeLine>&lt;Title&gt;             A</CodeLine>
+<CodeLine>&lt;numleafdocs&gt; 118</CodeLine>
+<CodeLine>&lt;contains&gt;      HASH0130bc5f9f90089b3723431f;HASH9cba43bacdab5263c98545;\</CodeLine>
+<CodeLine>                          HASH12c88a01da6e8379df86a7;HASH9c86579a83e1a2e4cf9736;   \</CodeLine>
+<CodeLine>                           HASHdc2951a7ada1f36a6c3aca;HASHea4dda6bbc7cdeb4abfdee;   \</CodeLine>
+<CodeLine>                          HASHce55006513c47235ac38ba;HASH012a33acaa077c0e612b9351;\</CodeLine>
+<CodeLine>                          HASH010dd1e923a123826ae30e4b;HASHaf674616785679fed4b7ee;\</CodeLine>
+<CodeLine>                         HASH0147eef4b9d1cb135e096619;HASHe69b9dbaa83ffb045d963b;\</CodeLine>
+<CodeLine>                         HASH01abc61c646c8e7a8ce88b10;HASH5f9cd13678e21820e32f3a;\</CodeLine>
+<CodeLine>                         HASHe8cbba1594c72c98f9aa1b;HASH01292a2b7b6b60dec96298bc;\</CodeLine>
+<CodeLine>                         ...</CodeLine>
+</Figure>
+<Text id="890">Figure <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> shows an excerpt from the collection information database that is created when building the Gutenberg collection. The excerpt was produced using the Greenstone utility <i>db2txt</i>, which converts the gdbm binary database format into textual form. Figure <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> contains three records, separated by horizontal rules. The first is a document entry, the other two are part of the hierarchy created by the <i>AZList</i> classifier for titles in the collection. The first line of each record is its key.</Text>
+<Text id="891">The document record stores the book's title, author, and any other metadata provided (or extracted) when the collection was built. It also records values for internal use: where files associated with this document reside (<i>&lt;archivedir&gt;</i>) and the document number used internally by mg (<i>&lt;docnum&gt;</i>).</Text>
+<Text id="892">The <i>&lt;contains&gt;</i> field stores a list of elements, separated by semicolons, that point to related records in the database. For a document record, <i>&lt;contains&gt;</i> is used to point to the nested sections. Subsequent record keys are formed by concatenating the current key with one of the child elements (separated by a period).</Text>
+<Text id="893">The second record in Figure <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> is the top node for the classification hierarchy of <i>Titles AâZ</i>. Its children, accessed through the <i>&lt;contains&gt;</i> field, include <i>CL1.1</i>, <i>CL1.2</i>, <i>CL1.3</i> and so on, and correspond to the individual pages for the letters <i>A</i>, <i>B</i>, <i>C</i> etc. There are only 24 children: the <i>AZList</i> classifier merged the <i>QâR</i> and <i>YâZ</i> entries because they covered only a few titles.</Text>
+<Text id="894">The children in the <i>&lt;contains&gt;</i> field of the third record, <i>CL1.1</i>, are the documents themselves. More complicated structures are possibleâthe <i>&lt;contains&gt;</i> field can include a mixture of documents and further <i>CL</i> nodes. Keys expressed relative to the current one are distinguished from absolute keys because they begin with a quotation mark (").</Text>
+</Content>
+</Part>
+<Part id="using_mg_and_gdbm_to_implement_a_source_object">
+<Title>
+<Text id="895">Using MG and GDBM to implement a Source object</Text>
+</Title>
+<Content>
+<Figure id="api_for_mg_and_gdbm_based_version_of_sourceclass">
+<Title>
+<Text id="896">API for mg and gdbm based version of <i>sourceclass</i> (abridged)</Text>
+</Title>
+<CodeLine>class mggdbmsourceclass : public sourceclass {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   // Omitted, data fields that store:</CodeLine>
+<CodeLine>   //     collection specific file information</CodeLine>
+<CodeLine>   //     index substructure</CodeLine>
+<CodeLine>   //     information about parent</CodeLine>
+<CodeLine>   //     pointers to gdbm and mgsearch objects</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   mggdbmsourceclass ();</CodeLine>
+<CodeLine>   virtual ~mggdbmsourceclass ();</CodeLine>
+<CodeLine>   void set_gdbmptr (gdbmclass *thegdbmptr);</CodeLine>
+<CodeLine>   void set_mgsearchptr (searchclass *themgsearchptr);</CodeLine>
+<CodeLine>   void configure (const text_t &amp;key, const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   bool translate_OID (const text_t &amp;OIDin, text_t &amp;OIDout,</CodeLine>
+<CodeLine>                                           comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   bool get_metadata (const text_t &amp;requestParams,</CodeLine>
+<CodeLine>                                           const text_t &amp;refParams,</CodeLine>
+<CodeLine>                                         bool getParents, const text_tset &amp;fields,</CodeLine>
+<CodeLine>                                         const text_t &amp;OID, MetadataInfo_tmap &amp;metadata,</CodeLine>
+<CodeLine>                                         comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   bool get_document (const text_t &amp;OID, text_t &amp;doc,</CodeLine>
+<CodeLine>                                         comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="897">The object that puts mg and gdbm together to realise an implementation of <i>sourceclass</i> is <i>mggdbmsourceclass</i>. Figure <CrossRef target="Figure" ref="api_for_mg_and_gdbm_based_version_of_sourceclass"/> shows its API. The two new member functions <i>set_gdbmptr()</i> and <i>set_mgsearchptr()</i> store pointers to their respective objects, so that the implementations of <i>get_metadata()</i> and <i>get_document()</i> can access the appropriate tools to complete the job.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="the_filter_object">
+<Title>
+<Text id="898">The Filter object</Text>
+</Title>
+<Content>
+<Figure id="api_for_the_filter_base_class">
+<Title>
+<Text id="899">API for the Filter base class</Text>
+</Title>
+<CodeLine>class filterclass {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   text_t gsdlhome;</CodeLine>
+<CodeLine>   text_t collection;</CodeLine>
+<CodeLine>   text_t collectdir;</CodeLine>
+<CodeLine>   FilterOption_tmap filterOptions;</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   filterclass ();</CodeLine>
+<CodeLine>   virtual ~filterclass ();</CodeLine>
+<CodeLine>   virtual void configure (const text_t &amp;key,Â const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   // returns the name of this filter</CodeLine>
+<CodeLine>   virtual text_t get_filter_name ();</CodeLine>
+<CodeLine>   // returns the current filter options</CodeLine>
+<CodeLine>   virtual void get_filteroptions (InfoFilterOptionsResponse_t &amp;response,</CodeLine>
+<CodeLine>                                 comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void filter (const FilterRequest_t &amp;request,</CodeLine>
+<CodeLine>                         FilterResponse_t &amp;response,</CodeLine>
+<CodeLine>                         comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="900">The base class API for the Filter object in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/> is shown in Figure <CrossRef target="Figure" ref="api_for_the_filter_base_class"/>. It begins with the protected data fields <i>gsdlhome</i>, <i>collection</i>, and <i>collectdir</i>. These commonly occur in classes that need to access collection-specific files.</Text>
+<BulletList>
+<Bullet>
+<Text id="901"><i>gsdlhome</i> is the same as <i>GSDLHOME</i>, so that the object can locate the Greenstone files.</Text>
+</Bullet>
+<Bullet>
+<Text id="902"><i>collection</i> is the name of the directory corresponding to the collection.</Text>
+</Bullet>
+<Bullet>
+<Text id="903"><i>collectdir</i> is the full pathname of the collection directory (this is needed because a collection does not have to reside within the <i>GSDLHOME</i> area).</Text>
+</Bullet>
+</BulletList>
+<Text id="904"><i>mggdbsourceclass</i> is another class that includes these three data fields.</Text>
+<Text id="905">The member functions <i>configure()</i> and <i>init()</i> (first seen in <i>sourceclass</i>) are used by the initialisation process. The object itself is closely aligned with the corresponding filter part of the protocol; in particular <i>get_filteroptions()</i> and <i>filter()</i> match one for one.</Text>
+<Figure id="how_a_filter_option_is_stored">
+<Title>
+<Text id="906">How a filter option is stored</Text>
+</Title>
+<CodeLine>struct FilterOption_t {</CodeLine>
+<CodeLine>   void clear (); \   void check_defaultValue ();</CodeLine>
+<CodeLine>   FilterOption_t () {clear();}</CodeLine>
+<CodeLine>   text_t name;</CodeLine>
+<CodeLine>   enum type_t {booleant=0, integert=1, enumeratedt=2, stringt=3};</CodeLine>
+<CodeLine>   type_t type;</CodeLine>
+<CodeLine>   enum repeatable_t {onePerQuery=0, onePerTerm=1, nPerTerm=2};</CodeLine>
+<CodeLine>   repeatable_t repeatable;</CodeLine>
+<CodeLine>   text_t defaultValue;</CodeLine>
+<CodeLine>   text_tarray validValues;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>struct OptionValue_t {</CodeLine>
+<CodeLine>   void clear ();</CodeLine>
+<CodeLine>   text_t name;</CodeLine>
+<CodeLine>   text_t value;</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="907">Central to the filter options are the two classes shown in Figure <CrossRef target="Figure" ref="how_a_filter_option_is_stored"/>. Stored inside <i>FilterOption_t</i> is the <i>name</i> of the option, its <i>type</i>, and whether or not it is <i>repeatable</i>. The interpretation of <i>validValues</i> depends on the option type. For a Boolean type the first value is <i>false</i> and the second is <i>true</i>. For an integer type the first value is the minimum number, the second the maximum. For an enumerated type all values are listed. For a string type the value is ignored. For simpler situations, <i>OptionValue_t</i> is used, which records as a <i>text_t</i> the <i>name</i> of the option and its <i>value</i>.</Text>
+<Text id="908">The request and response objects passed as parameters to <i>filterclass</i> are constructed from these two classes, using associative arrays to store a set of options such as those required for <i>InfoFilterOptionsResponse_t</i>. More detail can be found in <i>GSDLHOME/src/recpt/comtypes.h</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="inherited_filter_objects">
+<Title>
+<Text id="909">Inherited Filter objects</Text>
+</Title>
+<Content>
+<Figure id="inheritance_hierarchy_for_filter">
+<Title>
+<Text id="910">Inheritance hierarchy for Filter</Text>
+</Title>
+<File width="337" height="245" url="images/Dev_Fig_38.gif"/>
+</Figure>
+<Text id="911">Two levels of inheritance are used for filters, as illustrated in Figure <CrossRef target="Figure" ref="inheritance_hierarchy_for_filter"/>. First a distinction is made between Query and Browse filters, and then for the former there is a specific implementation based on mg. To operate correctly, <i>mgqueryfilterclass</i> needs access to mg through <i>mgsearchclass</i> and to gdbm through <i>gdbmclass</i>. <i>browsefilterclass</i> only needs access to gdbm. Pointers to these objects are stored as protected data fields within the respective classes.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_collection_server_code">
+<Title>
+<Text id="912">The collection server code</Text>
+</Title>
+<Content>
+<Text id="913">Here are the header files in <i>GSDLHOME/src/colservr</i>, with a description of each. The filename generally repeats the object name defined within it.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="120">
+<Text id="914"><b>browsefilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="915">Inherited from <i>filterclass</i>, this object provides access to gdbm. (Described above.)</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="916"><b>collectserver.h</b></Text>
+</th>
+<th width="420">
+<Text id="917">This object binds Filters and Sources for one collection together, to form the Collection object depicted in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="918"><b>colservrconfig.h</b></Text>
+</th>
+<th width="420">
+<Text id="919">Function support for reading the collection-specific files <i>etc/collect.cfg</i> and <i>index/build.cfg</i>. The former is the collection's configuration file. The latter is a file generated by the building process that records the time of the last successful build, an index map list, how many documents were indexed, and how large they are in bytes (uncompressed).</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="920"><b>filter.h</b></Text>
+</th>
+<th width="420">
+<Text id="921">The base class Filter object <i>filterclass</i> described above.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="922"><b>maptools.h</b></Text>
+</th>
+<th width="420">
+<Text id="923">Defines a class called <i>stringmap</i> that provides a mapping that remembers the original order of a <i>text_t</i> map, but is fast to look up. Used in <i>mggdbmsourceclass</i> and <i>queryfilterclass</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="924"><b>mggdbmsource.h</b></Text>
+</th>
+<th width="420">
+<Text id="925">Inherited from <i>sourceclass</i>, this object provides access to mg and gdbm. (Described above.)</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="926"><b>mgppqueryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="927">Inherited from <i>queryfilterclass</i>, this object provides an implementation of <i>QueryFilter</i> based upon mg++, an improved version of mg written in C++. Note that Greenstone is set up to use mg by default, since mg++ is still under development.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="928"><b>mgppsearch.h</b></Text>
+</th>
+<th width="420">
+<Text id="929">Inherited from <i>searchclass</i>, this object provides an implementation of Search using mg++. Like <i>mgppqueryfilterclass</i>, this is not used by default.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="930"><b>mgq.h</b></Text>
+</th>
+<th width="420">
+<Text id="931">Function-level interface to the mg package. Principal functions are <i>mg_ask()</i> and <i>mg_results()</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="932"><b>mgqueryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="933">Inherited from <i>queryfilterclass</i>, this object provides an implementation of <i>QueryFilter</i> based upon mg.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="934"><b>mgsearch.h</b></Text>
+</th>
+<th width="420">
+<Text id="935">Inherited from <i>searchclass</i>, this object provides an implementation of Search using mg. (Described above.)</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="936"><b>phrasequeryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="937">Inherited from <i>mgqueryclass</i>, this object provides a phrase-based query class. It is not used in the default installation. Instead <i>mgqueryfilterclass</i> provides this capability through functional support from <i>phrasesearch.h</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="938"><b>phrasesearch.h</b></Text>
+</th>
+<th width="420">
+<Text id="939">Functional support to implement phrase searching as a post-processing operation.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="940"><b>querycache.h</b></Text>
+</th>
+<th width="420">
+<Text id="941">Used by <i>searchclass</i> and its inherited classes to cache the results of a query, in order to make the generation of further search results pages more efficient. (Described above.)</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="942"><b>queryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="943">Inherited from the Filter base class <i>filterclass</i>, this object establishes a base class for Query filter objects. (Described above.)</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="944"><b>queryinfo.h</b></Text>
+</th>
+<th width="420">
+<Text id="945">Support for searching: data structures and objects to hold query parameters, document results and term frequencies.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="946"><b>search.h</b></Text>
+</th>
+<th width="420">
+<Text id="947">The base class Search object <i>searchclass</i>. (Described above.)</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="948"><b>source.h</b></Text>
+</th>
+<th width="420">
+<Text id="949">The base class Source object <i>sourceclass</i>. (Described above.)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="protocol">
+<Title>
+<Text id="950">Protocol</Text>
+</Title>
+<Content>
+<Table id="list_of_protocol_calls">
+<Title>
+<Text id="951">List of protocol calls</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="952"><i>get_protocol_name()</i></Text>
+</th>
+<th width="397">
+<Text id="953">Returns the name of this protocol. Choices include <i>nullproto</i>, <i>corbaproto</i>, and <i>z3950proto</i>. Used by protocol-sensitive parts of the runtime system to decide which code to execute.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="954"><i>get_collection_list()</i></Text>
+</th>
+<th width="397">
+<Text id="955">Returns the list of collections that this protocol knows about.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="956"><i>has_collection()</i></Text>
+</th>
+<th width="397">
+<Text id="957">Returns <i>true</i> if the protocol can communicate with the named collection, i.e. it is within its collection list.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="958"><i>ping()</i></Text>
+</th>
+<th width="397">
+<Text id="959">Returns <i>true</i> if a successful connection was made to the named collection. In the null protocol the implementation is identical to <i>has_collection().</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="960"><i>get_collectinfo()</i></Text>
+</th>
+<th width="397">
+<Text id="961">Obtains general information about the named collection: when it was last built, how many documents it contains, and so on. Also includes metadata from the collection configuration file: âabout this collectionâ text; the collection icon to use, and so on.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="962"><i>get_filterinfo()</i></Text>
+</th>
+<th width="397">
+<Text id="963">Gets a list of all Filters for the named collection.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="964"><i>get_filteroptions()</i></Text>
+</th>
+<th width="397">
+<Text id="965">Gets all options for a particular Filter within the named collection.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="966"><i>filter()</i></Text>
+</th>
+<th width="397">
+<Text id="967">Supports searching and browsing. For a given filter type and option settings, it accesses the content of the named collections to produce a result set that is filtered in accordance with the option settings. The data fields returned also depend on the option settings: examples include query term frequency and document metadata.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="968"><i>get_document()</i></Text>
+</th>
+<th width="397">
+<Text id="969">Gets a document or section of a document.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="970"><CrossRef target="Table" ref="list_of_protocol_calls"/> lists the function calls to the protocol, with a summary for each entry. The examples in Section <CrossRef target="Section" ref="how_the_conceptual_framework_fits_together"/> covered most of these. Functions not previously mentioned are <i>has_collection()</i>, <i>ping()</i>, <i>get_protocol_name()</i> and <i>get_filteroptions()</i>. The first two provide yes/no answers to the questions âdoes the collection exists on this server?â and âis it running?â respectively. The purpose of the other two is to support multiple protocols within an architecture that is distributed over different computers, not just the null-protocol based single executable described here. One of these distinguishes which protocol is being used. The other lets a receptionist interrogate a collection server to find what options are supported, and so dynamically configure itself to take full advantage of the services offered by a particular server.</Text>
+<Figure id="null_protocol_api">
+<Title>
+<Text id="971">Null protocol API (abridged)</Text>
+</Title>
+<CodeLine>class nullproto : public recptproto {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   virtual text_t get_protocol_name ();</CodeLine>
+<CodeLine>   virtual void get_collection_list (text_tarray &amp;collist,</CodeLine>
+<CodeLine>                comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void has_collection (const text_t &amp;collection,</CodeLine>
+<CodeLine>                bool &amp;hascollection,</CodeLine>
+<CodeLine>                comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void ping (const text_t &amp;collection,</CodeLine>
+<CodeLine>                  bool &amp;wassuccess,</CodeLine>
+<CodeLine>                  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_collectinfo (const text_t &amp;collection,</CodeLine>
+<CodeLine>                  ColInfoResponse_t &amp;collectinfo,</CodeLine>
+<CodeLine>                  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_filterinfo (const text_t &amp;collection,</CodeLine>
+<CodeLine>                   InfoFiltersResponse_t &amp;response,</CodeLine>
+<CodeLine>                   comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_filteroptions (const text_t &amp;collection,</CodeLine>
+<CodeLine>                   const InfoFilterOptionsRequest_t &amp;request,</CodeLine>
+<CodeLine>                   InfoFilterOptionsResponse_t &amp;response,</CodeLine>
+<CodeLine>                   comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void filter (const text_t &amp;collection,</CodeLine>
+<CodeLine>                   FilterRequest_t &amp;request,</CodeLine>
+<CodeLine>                   FilterResponse_t &amp;response,</CodeLine>
+<CodeLine>                   comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_document (const text_t &amp;collection,</CodeLine>
+<CodeLine>                  const DocumentRequest_t &amp;request,</CodeLine>
+<CodeLine>                  DocumentResponse_t &amp;response,</CodeLine>
+<CodeLine>                  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="972">Figure <CrossRef target="Figure" ref="null_protocol_api"/> shows the API for the null protocol. Comments, and certain low level details, have been omitted (see the source file <i>recpt/nullproto.h</i> for full details).</Text>
+<Text id="973">This protocol inherits from the base class <i>recptproto</i>. Virtual inheritance is used so that more than one type of protocolâincluding protocols not even conceived yetâcan be easily supported in the rest of the source code. This is possible because the base class object <i>recptproto</i> is used throughout the source code, with the exception of the point of construction. Here we specify the actual variety of protocol we wish to useâin this case, the null protocol.</Text>
+<Text id="974">With the exception of <i>get_protocol_name()</i>, which takes no parameters and returns the protocol name as a Unicode-compliant text string, all protocol functions include an error parameter and an output stream as the last two arguments. The error parameter records any errors that occur during the execution of the protocol call, and the output stream is for logging purposes. The functions have type <i>void</i>âthey do not explicitly return information as their final statement, but instead return data through designated parameters such as the already-introduced error parameter. In some programming languages, such routines would be defined as procedures rather than functions, but C++ makes no syntactic distinction.</Text>
+<Text id="975">Most functions take the collection name as an argument. Three of the member functions, <i>get_filteroptions()</i>, <i>filter()</i>, and <i>get_document()</i>, follow the pattern of providing a Request parameter and receiving the results in a Response parameter.</Text>
+</Content>
+</Section>
+<Section id="receptionist">
+<Title>
+<Text id="976">Receptionist</Text>
+</Title>
+<Content>
+<Text id="977">The final layer of the conceptual model is the receptionist. Once the CGI arguments are parsed, the main activity is the execution of an Action, supported by the Format and Macro Language objects. These are described below. Although they are represented as objects in the conceptual framework, Format and Macro Language objects are not strictly objects in the C++ sense. In reality, Format is a collection of data structures with a set of functions that operate on them, and the Macro Language object is built around <i>displayclass</i>, defined in <i>lib/display.h</i>, with stream conversion support from <i>lib/gsdlunicode.h</i>.</Text>
+<Subsection id="actions">
+<Title>
+<Text id="978">Actions</Text>
+</Title>
+<Content>
+<Table id="actions_in_greenstone">
+<Title>
+<Text id="979">Actions in Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="980"><i>action</i></Text>
+</th>
+<th width="397">
+<Text id="981">Base class for virtual inheritance.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="982"><i>authenaction</i></Text>
+</th>
+<th width="397">
+<Text id="983">Supports user authentication: prompts the user for a password if one has not been entered; checks whether it is valid; and forces the user to log in again if sufficient time lapses between accesses.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="984"><i>collectoraction</i></Text>
+</th>
+<th width="397">
+<Text id="985">Generates the pages for the Collector.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="986"><i>documentaction</i></Text>
+</th>
+<th width="397">
+<Text id="987">Retrieves documents, document sections, parts of the classification hierarchy, or formatting information.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="988"><i>extlinkaction</i></Text>
+</th>
+<th width="397">
+<Text id="989">Takes a user directly to a URL that is external to a collection, possibly generating an alert page first (dictated by the Preferences).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="990"><i>pageaction</i></Text>
+</th>
+<th width="397">
+<Text id="991">Generates a page in conjunction with the macro language.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="992"><i>pingaction</i></Text>
+</th>
+<th width="397">
+<Text id="993">Checks to see whether a collection is online.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="994"><i>queryaction</i></Text>
+</th>
+<th width="397">
+<Text id="995">Performs a search.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="996"><i>statusaction</i></Text>
+</th>
+<th width="397">
+<Text id="997">Generates the administration pages.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="998"><i>tipaction</i></Text>
+</th>
+<th width="397">
+<Text id="999">Brings up a random tip for the user.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1000"><i>usersaction</i></Text>
+</th>
+<th width="397">
+<Text id="1001">Supports adding, deleting, and managing user access.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="1002">Greenstone supports the eleven actions summarised in Table <CrossRef target="Table" ref="actions_in_greenstone"/>.</Text>
+<Figure id="using_the_cgiargsinfoclass_from_pageactioncpp" class="withLineNumber">
+<Title>
+<Text id="1003">Using the <i>cgiargsinfoclass</i> from <i>pageaction.cpp</i></Text>
+</Title>
+<CodeLine>cgiarginfo arg_ainfo;</CodeLine>
+<CodeLine>arg_ainfo.shortname = " a " ;</CodeLine>
+<CodeLine>arg_ainfo.longname = " action" ;</CodeLine>
+<CodeLine>arg_ainfo.multiplechar = true;</CodeLine>
+<CodeLine>arg_ainfo.argdefault = " p" ;</CodeLine>
+<CodeLine>arg_ainfo.defaultstatus = cgiarginfo::weak;</CodeLine>
+<CodeLine>arg_ainfo.savedarginfo = cgiarginfo::must;</CodeLine>
+<CodeLine>argsinfo.addarginfo (NULL, arg_ainfo);</CodeLine>
+<CodeLine/>
+<CodeLine>arg_ainfo.shortname = " p" ;</CodeLine>
+<CodeLine>arg_ainfo.longname = " page" ;</CodeLine>
+<CodeLine>arg_ainfo.multiplechar = true;</CodeLine>
+<CodeLine>arg_ainfo.argdefault = " home" ;</CodeLine>
+<CodeLine>arg_ainfo.defaultstatus = cgiarginfo::weak;</CodeLine>
+<CodeLine>arg_ainfo.savedarginfo = cgiarginfo::must;</CodeLine>
+<CodeLine>argsinfo.addarginfo (NULL, arg_ainfo);</CodeLine>
+</Figure>
+<Text id="1004">The CGI arguments needed by an action are formally declared in its constructor function using <i>cgiarginfo</i>(defined in <i>recpt/cgiargs.h</i>). Figure <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/> shows an excerpt from the <i>pageaction</i> constructor function, which defines the size and properties of the CGI arguments <i>a</i> and <i>p</i>.</Text>
+<Text id="1005">For each CGI argument, the constructor must specify its short name (lines 2 and 10), which is the name of the CGI variable itself; a long name (lines 3 and 11) that is used to provide a more meaningful description of the action; whether it represents a single or multiple character value (lines 4 and 12); a possible default value (lines 5 and 13); what happens when more than one default value is supplied (lines 6 and 14) (since defaults can also be set in configuration files); and whether or not the value is preserved at the end of this action (lines 7 and 15) .</Text>
+<Text id="1006">Since it is built into the code, web pages that detail this information can be generated automatically. The <i>statusaction</i> produces this information. It can be viewed by entering the URL for the Greenstone administration page.</Text>
+<Text id="1007">The twelve inherited actions are constructed in <i>main()</i>, the top-level function for the <i>library</i> executable, whose definition is given in <i>recpt/librarymain.cpp</i>. This is also where the <i>receptionist</i> object (defined in <i>recpt/receptionist.cpp</i>) is constructed. Responsibility for all the actions is passed to the <i>receptionist</i>, which processes them by maintaining, as a data field, an associative array of the Action base class, indexed by action name.</Text>
+<Figure id="action_base_class_api">
+<Title>
+<Text id="1008">Action base class API</Text>
+</Title>
+<CodeLine>class action {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   cgiargsinfoclass argsinfo;</CodeLine>
+<CodeLine>   text_t gsdlhome;</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   action ();</CodeLine>
+<CodeLine>   virtual ~action ();</CodeLine>
+<CodeLine>   virtual void configure (const text_t &amp;key, const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual text_t get_action_name ();</CodeLine>
+<CodeLine>   cgiargsinfoclass getargsinfo ();</CodeLine>
+<CodeLine>   virtual bool check_cgiargs (cgiargsinfoclass &amp;argsinfo,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool check_external_cgiargs (cgiargsinfoclass &amp;argsinfo,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              outconvertclass &amp;outconvert,</CodeLine>
+<CodeLine>              const text_t &amp;saveconf,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_cgihead_info (cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              response_t &amp;response,</CodeLine>
+<CodeLine>              text_t &amp;response_data,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool uses_display (cgiargsclass &amp;args);</CodeLine>
+<CodeLine>   virtual void define_internal_macros (displayclass &amp;disp,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void define_external_macros (displayclass &amp;disp,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool do_action (cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              browsermapclass *browsers,</CodeLine>
+<CodeLine>              displayclass &amp;disp,</CodeLine>
+<CodeLine>              outconvertclass &amp;outconvert,</CodeLine>
+<CodeLine>              ostream &amp;textout,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1009">Figure <CrossRef target="Figure" ref="action_base_class_api"/> shows the API for the Action base class. When executing an action, <i>receptionist</i> calls several functions, starting with <i>check_cgiargs()</i>. Most help to check, set up, and define values and macros; while <i>do_action()</i> actually generates the output page. If a particular inherited object has no definition for a particular member function, it passes through to the base class definition which implements appropriate default behaviour.</Text>
+<Text id="1010">Explanations of the member functions are as follows.</Text>
+<BulletList>
+<Bullet>
+<Text id="1011"><i>get_action_name()</i> returns the CGI <i>a</i> argument value that specifies this action. The name should be short but may be more than one character long.</Text>
+</Bullet>
+<Bullet>
+<Text id="1012"><i>check_cgiargs()</i> is called before <i>get_cgihead_info()</i>, <i>define_external_macros()</i>, and <i>do_action()</i>. If an error is found a message is written to <i>logout</i>; if it is serious the function returns <i>false</i> and no page content is produced.</Text>
+</Bullet>
+<Bullet>
+<Text id="1013"><i>check_external_cgiargs()</i> is called after <i>check_cgiargs()</i> for all actions. It is intended for use only to override some other normal behaviour, for example producing a login page when the requested page needs authentication.</Text>
+</Bullet>
+<Bullet>
+<Text id="1014"><i>get_cgihead_info()</i> sets the CGI header information. If <i>response</i> is set to <i>location</i>, then <i>response_data</i> contains the redirect address. If <i>response</i> is set to <i>content</i>, then <i>response_data</i> contains the content type.</Text>
+</Bullet>
+<Bullet>
+<Text id="1015"><i>uses_display()</i> returns <i>true</i> if the <i>displayclass</i> is needed to output the page content (the default).</Text>
+</Bullet>
+<Bullet>
+<Text id="1016"><i>define_internal_macros()</i> defines all macros that are related to pages generated by this action.</Text>
+</Bullet>
+<Bullet>
+<Text id="1017"><i>define_external_macros()</i> defines all macros that might be used by other actions to produce pages.</Text>
+</Bullet>
+<Bullet>
+<Text id="1018"><i>do_action()</i> generates the output page, normally streamed through the macro language object <i>display</i> and the output conversion object <i>textout</i>. Returns <i>false</i> if there was an error that prevented the action from outputting anything.</Text>
+</Bullet>
+</BulletList>
+<Text id="1019">At the beginning of the class definition, <i>argsinfo</i> is the protected data field (used in the code excerpt shown in Figure <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/>) that stores the CGI argument information specified in an inherited Action constructor function. The other data field, <i>gsdlhome</i>, records <i>GSDLHOME</i> for convenient access.<FootnoteRef id="4"/>The object also includes <i>configure()</i> and <i>init()</i> for initialisation purposes.</Text>
+</Content>
+</Subsection>
+<Subsection id="formatting">
+<Title>
+<Text id="1020">Formatting</Text>
+</Title>
+<Content>
+<Figure id="core_data_structures_in_format">
+<Title>
+<Text id="1021">Core data structures in Format</Text>
+</Title>
+<CodeLine>enum command_t {comIf, comOr, comMeta, comText, comLink, comEndLink,</CodeLine>
+<CodeLine>         comNum, comIcon, comDoc,</CodeLine>
+<CodeLine>         comHighlight, comEndHighlight};</CodeLine>
+<CodeLine>enum pcommand_t {pNone, pImmediate, pTop, pAll};</CodeLine>
+<CodeLine>enum dcommand_t {dMeta, dText};</CodeLine>
+<CodeLine>enum mcommand_t {mNone, mCgiSafe};</CodeLine>
+<CodeLine>struct metadata_t {</CodeLine>
+<CodeLine>   void clear();</CodeLine>
+<CodeLine>   metadata_t () {clear();}</CodeLine>
+<CodeLine>   text_t metaname;</CodeLine>
+<CodeLine>   mcommand_t metacommand;</CodeLine>
+<CodeLine>   pcommand_t parentcommand;</CodeLine>
+<CodeLine>   text_t parentoptions;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>// The decision component of an {If}{decision,true-text,false-text}</CodeLine>
+<CodeLine>// formatstring. The decision can be based on metadata or on text;</CodeLine>
+<CodeLine>// normally that text would be a macro like</CodeLine>
+<CodeLine>// _cgiargmode_.</CodeLine>
+<CodeLine>struct decision_t {</CodeLine>
+<CodeLine>   void clear();</CodeLine>
+<CodeLine>   decision_t () {clear();}</CodeLine>
+<CodeLine>   dcommand_t command;</CodeLine>
+<CodeLine>   metadata_t meta;</CodeLine>
+<CodeLine>   text_t text;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>struct format_t {</CodeLine>
+<CodeLine>   void clear();</CodeLine>
+<CodeLine>   format_t () {clear();}</CodeLine>
+<CodeLine>   command_t command;</CodeLine>
+<CodeLine>   decision_t decision;</CodeLine>
+<CodeLine>   text_t text;</CodeLine>
+<CodeLine>   metadata_t meta;</CodeLine>
+<CodeLine>   format_t *nextptr;</CodeLine>
+<CodeLine>   format_t *ifptr;</CodeLine>
+<CodeLine>   format_t *elseptr;</CodeLine>
+<CodeLine>   format_t *orptr;</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1022">Although formatting is represented as a single entity in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/>, in reality it constitutes a collection of data structures and functions. They are gathered together under the header file <i>recpt/formattools.h</i>. The core data structures are shown in Figure <CrossRef target="Figure" ref="core_data_structures_in_format"/>.</Text>
+<Figure id="data_structures_built_for_sample_format_statement">
+<Title>
+<Text id="1023">Data structures built for sample <i>format</i> statement</Text>
+</Title>
+<File width="395" height="152" url="images/Dev_Fig_43.png"/>
+</Figure>
+<Text id="1024">The implementation is best explained using an example. When the format statement</Text>
+<CodeLine>format CL1Vlist</CodeLine>
+<Text id="1025" type="code">"[link][Title]{If}{[Creator], by [Creator]}[/link]} "</Text>
+<Text id="1026">is read from a collection configuration file, it is parsed by functions in <i>formattools.cpp</i> and the interconnected data structure shown in Figure <CrossRef target="Figure" ref="data_structures_built_for_sample_format_statement"/> is built. When the format statement needs to be evaluated by an action, the data structure is traversed. The route taken at <i>comIf</i> and <i>comOr</i> nodes depends on the metadata that is returned from a call to the protocol.</Text>
+<Text id="1027">One complication is that when metadata is retrieved, it might include further macros and format syntax. This is handled by switching back and forth between parsing and evaluating, as needed.</Text>
+</Content>
+</Subsection>
+<Subsection id="macro_language">
+<Title>
+<Text id="1028">Macro language</Text>
+</Title>
+<Content>
+<Text id="1029">The Macro Language entity in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/>, like Format, does not map to a single C++ class. In this case there is a core class, but the implementation of the macro language also calls upon supporting functions and classes.</Text>
+<Text id="1030">Again, the implementation is best explained using an example. First we give some sample macro definitions that illustrate macro precedence, thenâwith the aid of a diagramâwe describe the core data structures built to support this activity. Finally we present and describe the public member functions to <i>displayclass</i>, the top-level macro object.</Text>
+<Figure id="illustration_of_macro_precedence">
+<Title>
+<Text id="1031">Illustration of macro precedence</Text>
+</Title>
+<CodeLine>package query</CodeLine>
+<CodeLine>_header_ []         {_querytitle_}</CodeLine>
+<CodeLine>_header_ [l=en]     {Search page}</CodeLine>
+<CodeLine>_header_ [c=demo]   {&lt;table bgcolor=green&gt;&lt;tr&gt;&lt;td&gt;_querytitle_&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;}</CodeLine>
+<CodeLine>_header_ [v=1]      {_textquery_}</CodeLine>
+<CodeLine>_header_ [l=fr,v=1,c=hdl] {HDL Page de recherche}</CodeLine>
+</Figure>
+<Text id="1032">In a typical Greenstone installation, macro precedence is normally: <i>c</i>(for the collection) takes precedence over <i>v</i>(for graphical or text-only interface), which takes precedence over <i>l</i>(for the language). This is accomplished by the line</Text>
+<CodeLine>macroprecedence c,v,l</CodeLine>
+<Text id="1033">in the main configuration file <i>main.cfg</i>. The macro statements in Figure <CrossRef target="Figure" ref="illustration_of_macro_precedence"/> define sample macros for <i>_header_</i> in the <i>query</i> package for various settings of <i>c</i>, <i>v</i>, and <i>l</i>. If the CGI arguments given when an action is invoked included <i>c=dls</i>, <i>v=1</i>, and <i>l=en</i>, the macro <i>_header_[v=1]</i> would be selected for display. It would be selected ahead <i>of _content_[l=en]</i> because <i>v</i> has a higher precedence than <i>l</i>. The <i>_content_[l=fr,v=1,c=dls]</i> macro would not be selected because the page parameter for <i>l</i> is different.</Text>
+<Figure id="data_structures_representing_the_default_macros">
+<Title>
+<Text id="1034">Data structures representing the default macros</Text>
+</Title>
+<File width="382" height="194" url="images/Dev_Fig_45.png"/>
+</Figure>
+<Text id="1035">Figure <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/> shows the core data structure built when reading the macro files specified in <i>etc/main.cfg</i>. Essentially, it is an associative array of associative arrays of associative arrays. The top layer (shown on the left) indexes which package the macro is from, and the second layer indexes the macro name. The final layer indexes any parameters that were specified, storing each one as the type <i>mvalue</i> which records, along with the macro value, the file it came from. For example, the text defined for <i>_header_[l=en]</i> in Figure <CrossRef target="Figure" ref="illustration_of_macro_precedence"/> can be seen stored in the lower of the two <i>mvalue</i> records in Figure <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/>.</Text>
+<Figure id="displayclass_api">
+<Title>
+<Text id="1036"><i>Displayclass</i> API (abridged)</Text>
+</Title>
+<CodeLine>class displayclass</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   displayclass ();</CodeLine>
+<CodeLine>   ~displayclass ();</CodeLine>
+<CodeLine>   int isdefaultmacro (text_t package, const text_t &amp;macroname);</CodeLine>
+<CodeLine>   int setdefaultmacro (text_t package, const text_t &amp;macroname,  </CodeLine>
+<CodeLine>         text_t params, const text_t &amp;macrovalue);</CodeLine>
+<CodeLine>   int loaddefaultmacros (text_t thisfilename);</CodeLine>
+<CodeLine>   void openpage (const text_t &amp;thispageparams,</CodeLine>
+<CodeLine>         const text_t &amp;thisprecedence);</CodeLine>
+<CodeLine>   void setpageparams (text_t thispageparams,</CodeLine>
+<CodeLine>         text_t thisprecedence);</CodeLine>
+<CodeLine>   int setmacro (const text_t &amp;macroname,</CodeLine>
+<CodeLine>         text_t package,</CodeLine>
+<CodeLine>         const text_t &amp;macrovalue);</CodeLine>
+<CodeLine>   void expandstring (const text_t &amp;inputtext, text_t &amp;outputtext);</CodeLine>
+<CodeLine>   void expandstring (text_t package, const text_t &amp;inputtext,</CodeLine>
+<CodeLine>         text_t &amp;outputtext, int recursiondepth = 0);</CodeLine>
+<CodeLine>   void setconvertclass (outconvertclass *theoutc) {outc = theoutc;}</CodeLine>
+<CodeLine>   outconvertclass *getconvertclass () {return outc;}</CodeLine>
+<CodeLine>   ostream *setlogout (ostream *thelogout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1037">The central object that supports the macro language is <i>displayclass</i>, defined in <i>lib/display.h</i>. Its public member functions are shown in Figure <CrossRef target="Figure" ref="displayclass_api"/>. The class reads the specified macro files using <i>loaddefaultmacros()</i>, storing in a protected section of the class (not shown) the type of data structure shown in Figure <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/>. It is also permissible for macros to be set by the runtime system using <i>setmacro()</i> (in the last example of Section <CrossRef target="Section" ref="how_the_conceptual_framework_fits_together"/>, <i>pageaction</i> sets <i>_homeextra_</i> to be the dynamically generated table of available collections using this function.) This is supported by a set of associative arrays similar to those used to represent macro files (it is not identical, because the former does not require the âparameterâ layer). In <i>displayclass</i>, macros read from the file are referred to as <i>default macros</i>. Local macros specified through <i>setmacro()</i> are referred to as <i>current macros</i>, and are cleared from memory once the page has been generated.</Text>
+<Text id="1038">When a page is to be produced, <i>openpage()</i> is first called to communicate the current settings of the page parameters (<i>l=en</i> and so on). Following that, text and macros are streamed through the classâtypically from within an <i>actionclass</i> âusing code along the lines of:</Text>
+<CodeLine>cout &lt;&lt; text_t2ascii &lt;&lt; display &lt;&lt; "_amacro_ "</CodeLine>
+<CodeLine>         &lt;&lt; "_anothermacro_ ";</CodeLine>
+<Text id="1039">The result is that macros are expanded according to the page parameter settings. If required, these settings can be changed partway through an action by using <i>setpageparams()</i>. The remaining public member functions provide lower level support.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_receptionist_code">
+<Title>
+<Text id="1040">The receptionist code</Text>
+</Title>
+<Content>
+<Text id="1041">The principal objects in the receptionist have now been described. Below we detail the supporting classes, which reside in <i>GSDLHOME/src/recpt</i>. Except where efficiency is paramountâin which case definitions are in-lineâimplementation details are contained within a header file's <i>.cpp</i> counterpart. Supporting files often include the word <i>tool</i> as part of the file name, as in <i>OIDtools.h</i> and <i>formattools.h</i>.</Text>
+<Text id="1042">A second set of lexically scoped files include the prefix <i>z3950</i>. The files provide remote access to online databases and catalogs that make their content publicly available using the Z39.50 protocol.</Text>
+<Text id="1043">Another large group of supporting files include the term <i>browserclass</i>. These files are related through a virtual inheritance hierarchy. As a group they support an abstract notion of browsing: serial page generation of compartmentalised document content or metadata. Browsing activities include perusing documents ordered alphabetically by title or chronologically by date; progressing through the titles returned by a query ten entries at a time; and accessing individual pages of a book using the âgo to pageâ mechanism. Each browsing activity inherits from <i>browserclass</i>, the base class:</Text>
+<BulletList>
+<Bullet>
+<Text id="1044"><i>datelistbrowserclass</i> provides support for chronological lists;</Text>
+</Bullet>
+<Bullet>
+<Text id="1045"><i>hlistbrowserclass</i> provides support for horizontal lists;</Text>
+</Bullet>
+<Bullet>
+<Text id="1046"><i>htmlbrowserclass</i> provides support for pages of html;</Text>
+</Bullet>
+<Bullet>
+<Text id="1047"><i>invbrowserclass</i> provides support for invisible lists;</Text>
+</Bullet>
+<Bullet>
+<Text id="1048"><i>pagedbrowserclass</i> provides go to page support;</Text>
+</Bullet>
+<Bullet>
+<Text id="1049"><i>vlistbrowserclass</i> provides support for vertical lists.</Text>
+</Bullet>
+</BulletList>
+<Text id="1050">Actions access <i>browserclass</i> objects through <i>browsetools.h</i>.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="140">
+<Text id="1051"><b>OIDtools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1052">Function support for evaluating document identifiers over the protocol.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1053"><b>action.h</b></Text>
+</th>
+<th width="390">
+<Text id="1054">Base class for the Actions entity depicted in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1055"><b>authenaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1056">Inherited action for handling authentication of a user.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1057"><b>browserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1058">Base class for abstract browsing activities.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1059"><b>browsetools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1060">Function support that accesses the <i>browserclass</i> hierarchy. Functionality includes expanding and contracting contents, outputing a table of contents, and generating control such as the âgo to pageâ mechanism.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1061"><b>cgiargs.h</b></Text>
+</th>
+<th width="390">
+<Text id="1062">Defines <i>cgiarginfo</i> used in Figure <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/>, and other data structure support for CGI arguments.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1063"><b>cgiutils.h</b></Text>
+</th>
+<th width="390">
+<Text id="1064">Function support for CGI arguments using the data structures defined in <i>cgiargs.h</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1065"><b>cgiwrapper.h</b></Text>
+</th>
+<th width="390">
+<Text id="1066">Function support that does everything necessary to output a page using the CGI protocol. Access is through the function</Text>
+<CodeLine>void cgiwrapper (receptionist &amp;recpt, text_t collection);</CodeLine>
+<Text id="1067">which is the only function declared in the header file. Everything else in the <i>.cpp</i> counterpart is lexically scoped to be local to the file (using the C++ keyword <i>static</i>). If the function is being run for a particular collection then <i>collection</i> should be set, otherwise it should be the empty string "". The code includes support for Fast-CGI.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1068"><b>collectoraction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1069">Inherited action that facilitates end-user collection-building through the Collector. The page generated comes from <i>collect.dm</i> and is controlled by the CGI argument <i>p=page</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1070"><b>comtypes.h</b></Text>
+</th>
+<th width="390">
+<Text id="1071">Core types for the protocol.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1072"><b>converter.h</b></Text>
+</th>
+<th width="390">
+<Text id="1073">Object support for stream converters.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1074"><b>datelistbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1075">Inherited from <i>browserclass</i>, this object provides browsing support for chronological lists such as that seen in the Greenstone Archives collection under âdatesâ in the navigation bar.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1076"><b>documentaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1077">Inherited action used to retrieve a document or part of a classification hierarchy.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1078"><b>extlinkaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1079">Inherited action that controls whether or not a user goes straight to an external link or passes through a warning page alerting the user to the fact that they are about to move outside the digital library system.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1080"><b>formattools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1081">Function support for parsing and evaluating collection configuration <i>format</i> statements. Described in more detail in Section <CrossRef target="Subsection" ref="formatting"/> above.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1082"><b>historydb.h</b></Text>
+</th>
+<th width="390">
+<Text id="1083">Data structures and function support for managing a database of previous queries so a user can start a new query that includes previous query terms.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1084"><b>hlistbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1085">Inherited from <i>browserclass</i>, this object provides browsing support for horizontal lists.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1086"><b>htmlbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1087">Inherited from <i>browserclass</i>, this object provides browsing support for html pages.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1088"><b>htmlgen.h</b></Text>
+</th>
+<th width="390">
+<Text id="1089">Function support to highlight query terms in a <i>text_t</i> string.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1090"><b>htmlutils.h</b></Text>
+</th>
+<th width="390">
+<Text id="1091">Function support that converts a <i>text_t</i> string into the equivalent html. The symbols ", <i>&amp;</i>, <i>&lt;</i>, and <i>&gt;</i> are converted into <i>&amp;quot;</i>, <i>&amp;amp;</i>, <i>&amp;lt;</i> and <i>&amp;gt;</i> respectively.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1092"><b>infodbclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1093">Defines two classes: <i>gdbmclass</i> and <i>infodbclass</i>. The former provides the Greenstone API to gdbm; the latter is the object class used to store a record entry read in from a gdbm database, and is essentially an associative array of integer-indexed arrays of <i>text_t</i> strings.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1094"><b>invbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1095">Inherited from <i>browserclass</i>, this object provides browsing support for lists that are not intended for display (invisible).</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1096"><b>nullproto.h</b></Text>
+</th>
+<th width="390">
+<Text id="1097">Inherited from <i>recptproto</i>, this class realises the null protocol, implemented through function calls from the receptionist to the collection server.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1098"><b>pageaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1099">Inherited action that, in conjunction with the macro file named in <i>p=page</i>, generates a web page.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1100"><b>pagedbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1101">Inherited from <i>browserclass</i>, this object provides browsing support for the âgo to pageâ mechanism seen (for example) in the Gutenberg collection.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1102"><b>pingaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1103">Inherited action that checks to see whether a particular collection is responding.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1104"><b>queryaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1105">Inherited action that takes the stipulated query, settings and preferences and performs a search, generating as a result the subset of <i>o=num</i> matching documents starting at position <i>r=num</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1106"><b>querytools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1107">Function support for querying.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1108"><b>receptionist.h</b></Text>
+</th>
+<th width="390">
+<Text id="1109">Top-level object for the receptionist. Maintains a record of CGI argument information, instantiations of each inherited action, instantiations of each inherited browser, the core macro language object <i>displayclass</i>, and all possible converters.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1110"><b>recptconfig.h</b></Text>
+</th>
+<th width="390">
+<Text id="1111">Function support for reading the site and main configuration files.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1112"><b>recptproto.h</b></Text>
+</th>
+<th width="390">
+<Text id="1113">Base class for the protocol.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1114"><b>statusaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1115">Inherited action that generates, in conjunction with <i>status.dm</i>, the various administration pages.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1116"><b>tipaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1117">Inherited action that produces, in conjunction with <i>tip.dm</i>, a web page containing a tip taken at random from a list of tips stored in <i>tip.dm</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1118"><b>userdb.h</b></Text>
+</th>
+<th width="390">
+<Text id="1119">Data structure and function support for maintaining a gdbm database of users: their password, groups, and so on.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1120"><b>usersaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1121">An administrator action inherited from the base class that supports adding and deleting users, as well as modifying the groups they are in.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1122"><b>vlistbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1123">Inherited from <i>browserclass</i>, this object provides browsing support for vertical lists, the mainstay of classifiers. For example, the children of the node for titles beginning with the letter <i>N</i> are stipulated to be a <i>VList</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1124"><b>z3950cfg.h</b></Text>
+</th>
+<th width="390">
+<Text id="1125">Data structure support for the Z39.50 protocol. Used by <i>z3950proto.cpp</i>, which defines the main protocol class(inherited from the base class <i>recptproto</i>), and configuration file parser <i>zparse.y</i> (written using Yacc).</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1126"><b>z3950proto.h</b></Text>
+</th>
+<th width="390">
+<Text id="1127">Inherited from <i>recptproto</i>, this class realises the Z39.50 protocol so that a Greenstone receptionist can access remote library sites running Z39.50 servers.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1128"><b>z3950server.h</b></Text>
+</th>
+<th width="390">
+<Text id="1129">Further support for the Z39.50 protocol.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="initialisation">
+<Title>
+<Text id="1130">Initialisation</Text>
+</Title>
+<Content>
+<Text id="1131">Initialisation in Greenstone is an intricate operation that processes configuration files and assigns default values to data fields. In addition to inheritance and constructor functions, core objects define <i>init()</i> and <i>configure()</i> functions to help standardise the task. Even so, the order of execution can be difficult to follow. This section describes what happens.</Text>
+<Text id="1132">Greenstone uses several configuration files for different purposes, but all follow the same syntax. Unless a line starts with the hash symbol (#) or consists entirely of white space, the first word defines a keyword, and the remaining words represent a particular setting for that keyword.</Text>
+<Text id="1133">The lines from configuration files are passed, one at a time, to <i>configure()</i> as two arguments: the keyword and an array of the remaining words. Based on the keyword, a particular version of <i>configure()</i> decides whether the information is of interest, and if so stores it. For example, <i>collectserver</i>(which maps to the Collection object in Figure <CrossRef target="Figure" ref="greenstone_runtime_system"/>) processes the format statements in a collection's configuration file. When the keyword <i>format</i> is passed to <i>configure()</i>, an <i>if</i> statement is triggered that stores in the object a copy of the function's second argument.</Text>
+<Text id="1134">After processing the keyword and before the function terminates, some versions of <i>configure()</i> pass the data to <i>configure()</i> functions in other objects. The Receptionist object calls <i>configure()</i> for Actions, Protocols, and Browsers. The NullProtocol object calls <i>configure()</i> for each Collection object; Collection calls Filters and Sources.</Text>
+<Text id="1135">In C++, data fields are normally initialized by the object's constructor function. However, in Greenstone some initialisation depends on values read from configuration files, so a second round of initialisation is needed. This is the purpose of the <i>init()</i> member functions, and in some cases it leads to further calls to <i>configure()</i>.</Text>
+<Figure id="initialising_greenstone_using_the_null_protocol">
+<Title>
+<Text id="1136">Initialising Greenstone using the null protocol</Text>
+</Title>
+<CodeLine>============</CodeLine>
+<CodeLine>Main program</CodeLine>
+<CodeLine>============</CodeLine>
+<CodeLine>Statically construct Receptionist</CodeLine>
+<CodeLine>Statically construct NullProtocol</CodeLine>
+<CodeLine>Establish the value for 'gsdlhome' by reading gsdlsite.cfg</CodeLine>
+<CodeLine>Foreach directory in GSDLHOME/collect that isn't "modelcol":</CodeLine>
+<CodeLine>   Add directory name (now treated as collection name) to NullProtocol:</CodeLine>
+<CodeLine>       Dynamically construct Collection</CodeLine>
+<CodeLine>       Dynamically construct Gdbm class</CodeLine>
+<CodeLine>       Dynamically construct the Null Filter</CodeLine>
+<CodeLine>       Dynamically construct the Browse Filter</CodeLine>
+<CodeLine>       Dynamically construct MgSearch</CodeLine>
+<CodeLine>       Dynamically construct the QueryFilter</CodeLine>
+<CodeLine>       Dynamically construct the MgGdbmSource</CodeLine>
+<CodeLine>       Configure Collection with 'collection'</CodeLine>
+<CodeLine>           Passing 'collection' value on to Filters and Sources:</CodeLine>
+<CodeLine>       Configure Receptionist with 'collectinfo':</CodeLine>
+<CodeLine>           Passing 'collectinfo' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>Add NullProtocol to Receptionist</CodeLine>
+<CodeLine>Add in UTF-8 converter</CodeLine>
+<CodeLine>Add in GB converter</CodeLine>
+<CodeLine>Add in Arabic converter</CodeLine>
+<CodeLine>Foreach Action:</CodeLine>
+<CodeLine>   Statically construct Action</CodeLine>
+<CodeLine>   Add Action to Receptionist</CodeLine>
+<CodeLine>Foreach Browsers:</CodeLine>
+<CodeLine>   Statically construct Browser</CodeLine>
+<CodeLine>   Add Browser to Receptionist</CodeLine>
+<CodeLine>Call function cgiwrapper:</CodeLine>
+<CodeLine>   =================</CodeLine>
+<CodeLine>   Configure objects</CodeLine>
+<CodeLine>   =================</CodeLine>
+<CodeLine>   Configure Receptionist with 'collection'</CodeLine>
+<CodeLine>       Passing 'collection' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>       NullProtocol not interested in 'collection'</CodeLine>
+<CodeLine>   Configure Receptionist with 'httpimg'</CodeLine>
+<CodeLine>       Passing 'httpimg' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>       NullProtocol passing 'httpimg' on to Collection</CodeLine>
+<CodeLine>       Passing 'httpimg' value on to Filters and Sources:</CodeLine>
+<CodeLine>   Configure Receptionist with 'gwcgi'</CodeLine>
+<CodeLine>       Passing 'gwcgi' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>       NullProtocol passing 'gwcgi' on to Collection</CodeLine>
+<CodeLine>           Passing 'gwcgi' value on to Filters and Sources:</CodeLine>
+<CodeLine>   Reading in site configuration file gsdlsite.cfg</CodeLine>
+<CodeLine>       Configure Recptionist with 'gsdlhome'</CodeLine>
+<CodeLine>           Passing 'gsdlhome' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>           NullProtocol passing 'gsdlhome' on to Collection</CodeLine>
+<CodeLine>               Passing 'gsdlhome' value on to Filters and Sources:</CodeLine>
+<CodeLine>       Configure Recptionist with ...</CodeLine>
+<CodeLine>       ... and so on for all entries in gsdlsite.cfg</CodeLine>
+<CodeLine>   Reading in main configuration file main.cfg</CodeLine>
+<CodeLine>       Confiugre Recptionist with ...</CodeLine>
+<CodeLine>       ... and so on for all entries in main.cfg</CodeLine>
+<CodeLine>   ====================</CodeLine>
+<CodeLine>   Initialising objects</CodeLine>
+<CodeLine>   ====================</CodeLine>
+<CodeLine>   Initialise the Receptionist</CodeLine>
+<CodeLine>       Configure Receptionist with 'collectdir'</CodeLine>
+<CodeLine>           Passing 'collectdir' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>           NullProtocol not interested in 'collectdir'</CodeLine>
+<CodeLine>       Read in Macro files</CodeLine>
+<CodeLine>       Foreach Actions</CodeLine>
+<CodeLine>           Initialise Action</CodeLine>
+<CodeLine>       Foreach Protocol</CodeLine>
+<CodeLine>           Initialise Protocol</CodeLine>
+<CodeLine>           When Protocol==NullProtocol:</CodeLine>
+<CodeLine>               Foreach Collection</CodeLine>
+<CodeLine>                   Reading Collection's build.cfg</CodeLine>
+<CodeLine>                   Reading Collection's collect.cfg</CodeLine>
+<CodeLine>                       Configure Collection with 'creator'</CodeLine>
+<CodeLine>                           Passing 'creator' value on to Filters and Sources:</CodeLine>
+<CodeLine>                       Configure Collection with 'maintainer'</CodeLine>
+<CodeLine>                           Passing 'maintainer' value on to Filters and Sources:</CodeLine>
+<CodeLine>                       ... and so on for all entries in collect.cfg</CodeLine>
+<CodeLine>       Foreach Browsers</CodeLine>
+<CodeLine>           Initialise Browser</CodeLine>
+<CodeLine>   =============</CodeLine>
+<CodeLine>   Generate page</CodeLine>
+<CodeLine>   =============</CodeLine>
+<CodeLine>   Parse CGI arguments</CodeLine>
+<CodeLine>   Execute designated Action to produce page</CodeLine>
+<CodeLine>End.</CodeLine>
+</Figure>
+<Text id="1137">Figure <CrossRef target="Figure" ref="initialising_greenstone_using_the_null_protocol"/> shows diagnostic statements generated from a version of Greenstone augmented to highlight the initialisation process. The program starts in the <i>main()</i> function in <i>recpt/librarymain.cpp</i>. It constructs a Receptionist object and a NullProtocol object, then scans <i>gsdlsite.cfg</i>(located in the same directory as the <i>library</i> executable) for <i>gsdlhome</i> and stores its value in a variable. For each online collectionâas established by reading in the directories present in <i>GSDLHOME/collect</i> âit constructs a Collection object, through the NullProtocol object, that includes within it Filters, Search and Source, plus a few hardwired calls to <i>configure()</i>.</Text>
+<Text id="1138">Next <i>main()</i> adds the NullProtocol object to the Receptionist, which keeps a base class array of protocols in a protected data field, and then sets up several converters. <i>main()</i> constructs all Actions and Browsers used in the executable and adds them to the Receptionist. The function concludes by calling <i>cgiwrapper()</i> in <i>cgiwrapper.cpp</i>, which itself includes substantial object initialisation.</Text>
+<Text id="1139">There are three sections to <i>cgiwrapper()</i>: configuration, initialisation and page generation. First some hardwired calls to <i>configure()</i> are made. Then <i>gsdlsite.cfg</i> is read and <i>configure()</i> is called for each line. The same is done for <i>etc/main.cfg</i>.</Text>
+<Text id="1140">The second phase of <i>cgiwrapper()</i> makes calls to <i>init()</i>. The Receptionist makes only one call to its <i>init()</i> function, but the act of invoking this calls <i>init()</i> functions in the various objects stored within it. First a hardwired call to <i>configure()</i> is made to set <i>collectdir</i>, then the macro files are read. For each action, its <i>init()</i> function is called. The same occurs for each protocol stored in the receptionistâbut in the system being described only one protocol is stored, the NullProtocol. Calling <i>init()</i> for this object causes further configuration: for each collection in the NullProtocol, its collection-specific <i>build.cfg</i> and <i>collect.cfg</i> are read and processed, with a call to <i>configure()</i> for each line.</Text>
+<Text id="1141">The final phase of <i>cgiwrapper()</i> is to parse the CGI arguments, and then call the appropriate action. Both these calls are made with the support of the Receptionist object.</Text>
+<Text id="1142">The reason for the separation of the configuration, initialisation, and page generation code is that Greenstone is optimised to be run as a server (using Fast-cgi, or the Corba protocol, or the Windows Local Library). In this mode of operation, the configuration and initialisation code is executed once, then the program remains in memory and generates many web pages in response to requests from clients, without requiring re-initalisation.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="configuring_your_greenstone_site">
+<Title>
+<Text id="1143">Configuring your Greenstone site</Text>
+</Title>
+<Content>
+<Text id="1144">There are two configuration files in Greenstone that are used for configuring various aspects of your Greenstone site. These files are the âmainâ configuration file <i>main.cfg</i>, found in <i>GSDLHOME/etc</i>, and the âsiteâ configuration file <i>gsdlsite.cfg</i>, found in <i>GSDLHOME/cgi-bin</i>. These files each control specific aspects of site-wide configuration. Both can be viewed from the Greenstone administration page.</Text>
+<Section id="main_configuration_file">
+<Title>
+<Text id="1145">Main configuration file</Text>
+</Title>
+<Content>
+<Text id="1146">The main configuration file <i>main.cfg</i> is used to configure the receptionistâthat part of Greenstone that fields queries and displays pages. You can control everything from the languages that the interface can use to what logs are kept.</Text>
+<Subsection id="site_maintenance_and_logging">
+<Title>
+<Text id="1147">Site maintenance and logging</Text>
+</Title>
+<Content>
+<Text id="1148">Lines in the configuration file dictate how your Greenstone site is maintained, what facilities it offers, which events are logged, and what notification is given to the maintainer. Table <CrossRef target="Table" ref="configuration_options_for_site_maintenance_and_logging"/> details some of the options that are available; the remaining ones are described in the following sections.</Text>
+<Table id="configuration_options_for_site_maintenance_and_logging">
+<Title>
+<Text id="1149">Configuration options for site maintenance and logging</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="1150"><b>Value</b></Text>
+</th>
+<th width="246">
+<Text id="1151"><b>Purpose</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1152"><i>maintainer</i></Text>
+</th>
+<th width="151">
+<Text id="1153">NULL or an E-mail address</Text>
+</th>
+<th width="246">
+<Text id="1154">E-mail address of the site maintainer to be used for certain notification purposes. If NULL, E-mail events are disabled</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1155"><i>MailServer</i></Text>
+</th>
+<th width="151">
+<Text id="1156">NULL or a server name</Text>
+</th>
+<th width="246">
+<Text id="1157">Outgoing mail server for this site. If NULL, <i>mail.maintainer's-domain</i> is used (e.g. if the maintainer is <i>help@example.com</i> the default is <i>mail.example.com</i>.) If this doesn't resolve to a valid smtp server, E-mail events will not work</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1158"><i>status</i></Text>
+</th>
+<th width="151">
+<Text id="1159"><i>enabled</i> or <i>disabled</i></Text>
+</th>
+<th width="246">
+<Text id="1160">Determines whether the âMaintenance and administrationâ page is to be made available</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1161"><i>collector</i></Text>
+</th>
+<th width="151">
+<Text id="1162"><i>enabled</i> or <i>disabled</i></Text>
+</th>
+<th width="246">
+<Text id="1163">Determines whether the end-user collection building âcollectorâ facility is available</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1164"><i>logcgiargs</i></Text>
+</th>
+<th width="151">
+<Text id="1165"><i>true</i> or <i>false</i></Text>
+</th>
+<th width="246">
+<Text id="1166">If <i>true</i>, a usage log is kept in <i>usage.txt</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1167"><i>usecookies</i></Text>
+</th>
+<th width="151">
+<Text id="1168"><i>true</i> or <i>false</i></Text>
+</th>
+<th width="246">
+<Text id="1169">If <i>true</i>, information about the site users is collected (using cookies) and written to <i>usage.txt</i>(this only works if <i>logcgiargs</i> is <i>true</i>)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1170"><i>LogDateFormat</i></Text>
+</th>
+<th width="151">
+<Text id="1171"><i>LocalTime</i> or <br/><i>UTCTime</i> or <br/><i>Absolute</i></Text>
+</th>
+<th width="246">
+<Text id="1172">Format in which time information is written to the log. <i>LocalTime</i> produces the format âThu Dec 07 12:34 NZDT 2000â, <i>UTCTime</i> is the same format but in GMT, and <i>absolute</i> is an integer representing the number of seconds since 00:00:00 01/01/1970 GMT</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1173"><i>LogEvents</i></Text>
+</th>
+<th width="151">
+<Text id="1174"><i>AllEvents</i> or <br/><i>CollectorEvents</i><br/>or <i>disabled</i></Text>
+</th>
+<th width="246">
+<Text id="1175">Logs certain events to <i>events.txt</i>. <i>AllEvents</i> logs all Greenstone events, <i>CollectorEvents</i> logs only events related to the Collector, and <i>disabled</i> log no events</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1176"><i>EmailEvents</i></Text>
+</th>
+<th width="151">
+<Text id="1177"><i>enabled</i> or <i>disabled</i></Text>
+</th>
+<th width="246">
+<Text id="1178">E-mail the maintainer (if there is oneâsee the maintainer option) every time an event occurs</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1179"><i>EmailUserEvents</i></Text>
+</th>
+<th width="151">
+<Text id="1180"><i>enabled</i> or <i>disabled</i></Text>
+</th>
+<th width="246">
+<Text id="1181">E-mail the user on certain eventsâsuch as the collector finishing a collection build</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1182"><i>macrofiles</i></Text>
+</th>
+<th width="151">
+<Text id="1183">list of macro filenames</Text>
+</th>
+<th width="246">
+<Text id="1184">Determine what macros are available for Greenstone's user interface software</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="language_support">
+<Title>
+<Text id="1185">Language support</Text>
+</Title>
+<Content>
+<Text id="1186">Two kinds of entry in the <i>main.cfg</i> configuration file affect the way that different languages are handled. They determine which languages and encodings are available from the Preferences page. <i>Encoding</i> lines specify the different types of character encoding that can be selected. <i>Language</i> lines specify what user interface languages can be selected (of course, there must be a language macro for each possible language).</Text>
+<Text id="1187">The <i>Encoding</i> line can contain four possible values: <i>shortname</i>, <i>longname</i>, <i>map</i> and <i>multibyte</i>. The <i>shortname</i> is the standard charset label, and must be specified for all encodings. The <i>longname</i> gives the encoding name that is displayed on the Preferences page. If it is absent it defaults to the <i>shortname</i>. The <i>map</i> value is mandatory for all encodings except utf8, which is handled internally (and should always be enabled). The <i>multibyte</i> value should be set for all character sets that require more than one byte per character. The file <i>main.cfg</i> specifies many encodings, most of which are commented out. To enable an encoding, remove the comment character â#â.</Text>
+<Text id="1188">Each <i>Language</i> line can contain three possible values, <i>shortname</i>, <i>longname</i>, and <i>default_encoding</i>. The <i>shortname</i> is the ISO 639 two-letter language symbol, and is required. The <i>longname</i> is the name that is used for the language on the Preferences page. If absent, it defaults to the <i>shortname</i>. The <i>default_encoding</i> option is used to specify the preferred encoding for this language.</Text>
+</Content>
+</Subsection>
+<Subsection id="page_parameters_and_cgi_arguments">
+<Title>
+<Text id="1189">Page parameters and CGI arguments</Text>
+</Title>
+<Content>
+<Text id="1190">Page parameters and CGI arguments may be defined from within the <i>main.cfg</i> configuration file. Recall from Figure <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/> that most CGI arguments are defined within the library C++ code itself. However, it is occasionally useful to define new arguments or edit existing ones at configuration time, thus avoiding the need to recompile the library.</Text>
+<Text id="1191">To do this you use the <i>cgiarg</i> configuration option. <i>Cgiarg</i> may take up to six arguments; <i>shortname</i>, <i>longname</i>, <i>multiplechar</i>, <i>argdefault</i>, <i>defaultstatus</i> and <i>savedarginfo</i>. These arguments correspond to the CGI argument options described in Section <CrossRef target="Section" ref="receptionist"/>. For example, in the default <i>main.cfg</i> file the <i>cgiarg</i> configuration option is used to set the default values of the existing <i>a</i> and <i>p</i> CGI arguments to <i>p</i> and <i>home</i> respectively.</Text>
+<Text id="1192">Page parameters are special cases of CGI arguments which correspond to parameters in Greenstone's macro files. For example, the <i>l</i> CGI argument directly corresponds to the <i>l=</i> parameter in the macro files. To define a CGI argument to also be a page parameter you use the <i>pageparam</i> configuration option.</Text>
+<Text id="1193">The best way to learn about the various configuration options possible in the <i>main-cfg</i> configuration file is to experiment with the file itself. Note that if you are using the Windows local library version of Greenstone you must restart the server before any configuration files changes take effect.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="site_configuration_file">
+<Title>
+<Text id="1194">Site configuration file</Text>
+</Title>
+<Content>
+<Table id="lines_in_gsdlsitecfg">
+<Title>
+<Text id="1195">Lines in <i>gsdlsite.cfg</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="1196"><b>Line</b></Text>
+</th>
+<th width="397">
+<Text id="1197"><b>Function</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1198"><i>gsdlhome</i></Text>
+</th>
+<th width="397">
+<Text id="1199">A path to the <i>GSDLHOME</i> directory.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1200"><i>httpprefix</i></Text>
+</th>
+<th width="397">
+<Text id="1201">The web address of <i>GSDLHOME</i>. If the document root on your web server is set to <i>GSDLHOME</i> you do not need this line.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1202"><i>httpimage</i></Text>
+</th>
+<th width="397">
+<Text id="1203">The web address of the directory containing the images for the user interface. If your web-server's document root is set to <i>GSDLHOME</i> this will be <i>images</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1204"><i>gwcgi</i></Text>
+</th>
+<th width="397">
+<Text id="1205">The web address of this cgi script (usually ends in <i>library</i>). This is not needed if your web server sets the environment variable <i>SCRIPT_NAME</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1206"><i>maxrequests</i></Text>
+</th>
+<th width="397">
+<Text id="1207">(Only applies if <i>fast-cgi</i> is in use.) The number of requests fast-cgi should process before it exits. When debugging the library this should be set to a small number, otherwise it should be a large number.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="1208">The site configuration file <i>gsdlsite.cfg</i> sets variables that are used by the library software and web-server at run-time, and resides in the same directory as the <i>library</i> program. Table <CrossRef target="Table" ref="lines_in_gsdlsitecfg"/> describe the lines in this file; they are explained in Section 5 of the <i>Greenstone Digital Library Installer's Guide.</i></Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_a_stl">
+<Title>
+<Text id="1209">Appendix A: The C++ Standard Template Library</Text>
+</Title>
+<Content>
+<Text id="1210">The Standard Template Library (STL) is a widely-used C++ library from Silicon Graphics (<i>www.sgi.com</i>). This Appendix gives a brief overview of key parts that are used throughout the Greenstone code. For a fuller description, consult the official STL reference manual, available online at <i>www.sgi.com</i>, or one of the many STL textbooks, for example Josuttis (1999).</Text>
+<Text id="1211">As the word âtemplateâ suggests, STL is not just a plug-and-use object library. Coupled with the template mechanism in C++, it provides a forum for programmers to concisely develop their own objects that tap into the algorithmic capabilities embedded within STL. This adds an extra layer of complexity, but it's worth it.</Text>
+<Text id="1212">To help understand the Greenstone code excerpts given in this manual, we give a few tutorial level examples that use STL.</Text>
+<Section id="lists">
+<Title>
+<Text id="1213">Lists</Text>
+</Title>
+<Content>
+<Figure id="programming_a_list_of_integers" class="withLineNumber">
+<Title>
+<Text id="1214">Programming a list of integers</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>#define nil 0</CodeLine>
+<CodeLine/>
+<CodeLine>struct intlist {</CodeLine>
+<CodeLine>   int val;</CodeLine>
+<CodeLine>   struct intlist* next;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_list(intlist* head)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   int total = 0;</CodeLine>
+<CodeLine>   intlist* curr = head;</CodeLine>
+<CodeLine>   while (curr!=nil)</CodeLine>
+<CodeLine>   {</CodeLine>
+<CodeLine>       total += curr-&gt;val;</CodeLine>
+<CodeLine>       curr = curr-&gt;next;</CodeLine>
+<CodeLine>   }</CodeLine>
+<CodeLine/>
+<CodeLine>   return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>void main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   intlist node1 = { 5, nil };</CodeLine>
+<CodeLine>   intlist node2 = { 4, nil };</CodeLine>
+<CodeLine>   node2.next = &amp;node1;</CodeLine>
+<CodeLine/>
+<CodeLine>   int total = total_int_list(&amp;node2);</CodeLine>
+<CodeLine>  cout &lt;&lt; " List items total to: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="1215">First we study two programs that implement an integer list. One uses basic C++ types (the âold fashionedâ way), the other uses STL. Figure <CrossRef target="Figure" ref="programming_a_list_of_integers"/> shows the source code implementation that does <i>not</i> use STL. Lines 5â8 define the basic data structure we are going to use: the field <i>val</i> stores the integer value, and <i>next</i> points to the next element in the listâa classic implementation of a linked list.</Text>
+<Text id="1216">To demonstrate use of the data structure, the main program (lines 23â32) sets up an integer list with elements [5, 4]. It then calls the function <i>total_int_list</i> (defined over lines 10â21) which takes as its only parameter a pointer to the head of a list and sums the values in it. The returned answer (9 in our example) is printed to the screen.</Text>
+<Text id="1217">The main work is accomplished by lines 12â18. First some initialisation: the local variable <i>total</i> is set to zero, and <i>curr</i> to point to the start of the list. Then a while loop adds the current integer element in the list to the running total (<i>total += curr-&gt;val;</i>) before moving on to the next element (<i>curr = curr-&gt;next;</i>). The while loop terminates when <i>curr</i> becomes equal to <i>nil</i>, signifying that there are no more elements left to process.</Text>
+<Figure id="programming_a_list_of_integers_using_stl">
+<Title>
+<Text id="1218">Programming a list of integers using STL</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine>#include &lt;list&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_list(list&lt;int&gt;* head)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   int total = 0;</CodeLine>
+<CodeLine>   list&lt;int&gt;::iterator curr = head-&gt;begin();</CodeLine>
+<CodeLine>   while (curr!=head-&gt;end())</CodeLine>
+<CodeLine>   {</CodeLine>
+<CodeLine>       total += *curr;</CodeLine>
+<CodeLine>       curr++;</CodeLine>
+<CodeLine>   }</CodeLine>
+<CodeLine/>
+<CodeLine>   return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>void main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   list&lt;int&gt; vals;</CodeLine>
+<CodeLine>   vals.push_back(5);</CodeLine>
+<CodeLine>   vals.push_back(4);</CodeLine>
+<CodeLine/>
+<CodeLine>   int total = total_int_list(&amp;vals);</CodeLine>
+<CodeLine>   cout &lt;&lt; " List items total to: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="1219">Figure <CrossRef target="Figure" ref="programming_a_list_of_integers_using_stl"/> shows an equivalent program using STL. It is no longer necessary to define a suitable data structure in the code; all that is necessary is the <i>#include &lt;list&gt;</i> directive on line 2 that includes the template version for a list defined in STL. The object is called a âcontainer classâ because when we declare a variable of this type we also specify the type we want it to store. On line 19 an integer list is realised with the statement <i>list&lt;int&gt; vals;</i>. Elements can be added to the object using the member function <i>push_back()</i>, as is done on lines 20â21.</Text>
+<Text id="1220">The main work is done by lines 6â12. There are still two initialisations and a while loop, but other than that the new syntax has little in common with the old. Central to this new way of processing is a variable of type <i>iterator</i>(line 7). In STL many classes include <i>iterator</i> types to provide a uniform way of working through a sequence of container objects. The first element is returned with <i>begin()</i> and the element just past the last one with <i>end()</i>. Moving to the next element is accomplished by the increment operation ++, which is overloaded by the iterator class to implement this task, and the value stored there is accessed through dereferencing (<i>*curr</i> on line 10), which is also overloaded.</Text>
+<Text id="1221">The STL implementation of this program is slightly smaller (25 lines verses 31) than the conventional code. The gains are more noticeable in larger projects, because the STL <i>list</i> object is more powerful than the example here illustrates. It is, for instance, a doubly linked list that supports several forms of insertion and deletionâsomething that would require additional programming effort to add to the basic integer list version.</Text>
+<Text id="1222">Note that the parameter to <i>total_int_list</i> in Figure <CrossRef target="Figure" ref="programming_a_list_of_integers_using_stl"/> was implemented as a pointer, to correspond with the pointer used in <i>total_int_list</i> in Figure <CrossRef target="Figure" ref="programming_a_list_of_integers"/>. In STL it is often more natural (and more desirable) to use references rather than pointers. Then the parameter becomes <i>list&lt;int&gt;&amp; head</i>, and its member functions are called with the syntax <i>head.begin();</i> and so on.</Text>
+</Content>
+</Section>
+<Section id="maps">
+<Title>
+<Text id="1223">Maps</Text>
+</Title>
+<Content>
+<Text id="1224">When implementing a digital library system, it is useful to be able to store elements in an array indexed by text strings rather than by numeric indexes. In Greenstone, for example, this greatly simplifies storing the macro files once they have been read; and the various configuration files. A data type that supports such access is called an <i>associative array</i>, and is often built in to modern high-level languages. It is also known by the name <i>hash array</i> (most notably in Perl), since hashing is the normal technique used to implement the text index.</Text>
+<Figure id="using_associative_arrays_in_stl" class="withLineNumber">
+<Title>
+<Text id="1225">Using associative arrays in STL</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine>#include &lt;map&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_table(map&lt;char*, int&gt;&amp; table)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   int total = 0;</CodeLine>
+<CodeLine>   map&lt;char*, int&gt;::iterator curr = table.begin();</CodeLine>
+<CodeLine>   while (curr!=table.end())</CodeLine>
+<CodeLine>   {</CodeLine>
+<CodeLine>       total += (curr-&gt;second);</CodeLine>
+<CodeLine>       curr++;</CodeLine>
+<CodeLine>   }</CodeLine>
+<CodeLine/>
+<CodeLine>   return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>int main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   map&lt;char*, int&gt; table;</CodeLine>
+<CodeLine>   table["Alice"] = 31;</CodeLine>
+<CodeLine>   table["Peter"] = 24;</CodeLine>
+<CodeLine>   table["Mary"]   = 47;</CodeLine>
+<CodeLine/>
+<CodeLine>   int total = total_int_table(table);</CodeLine>
+<CodeLine>   cout &lt;&lt; " Age total: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>  }</CodeLine>
+</Figure>
+<Text id="1226">In STL, associative arrays are accomplished using the <i>map</i> object. Figure <CrossRef target="Figure" ref="using_associative_arrays_in_stl"/> shows a somewhat contrived example that stores the age of three people (Alice, Peter and Mary) in an associative array under their own names (lines 19â22). The problem is to write a function that calculates the total age of the people present, without knowing how many there are or what their names are. Of course, this could be solved with a standard numeric array of integers. The example is contrived to demonstrate the features of the <i>map</i> object and bring out the similarity of processing with the <i>list</i> object with an <i>iterator</i>.</Text>
+<Text id="1227">Like <i>list</i>, <i>map</i> is a container class. However, when declaring a variable of this type we must specify two<FootnoteRef id="5"/> things: the index type, and the element type. As can be seen on line 19, we obtain an associative array that stores integers using <i>char*</i>(which is how a string is declared in C++) as the index type followed by <i>int</i> as the element type.</Text>
+<Text id="1228">There are several ways to store elements in the associative array. In the example on lines 20â22 the overloaded array subscript [ ] is used to initialise the table with the ages of the three people. The similarity of <i>total_int_table</i>âwhich performs the main calculation in the programâto <i>total_int_list</i> in Figure <CrossRef target="Figure" ref="programming_a_list_of_integers"/> is striking. In fact, they are nearly identical, and this is no coincidence. STL makes heavy use of inheritance so that different objects still use the same fundamental operations. This is particularly true with iterators. The small differences between the two functions are that the iterator is now derived from <i>map&lt;char*, int&gt;</i>, and access to its elements is with <i>curr-&gt;second()</i>âbecause dereferencing the variable (<i>*curr</i>) is defined to return an object of type <i>pair</i>. This records both the index name (<i>first</i>) and the element value (<i>second</i>), but we only want the latter. Other than that, the code remains the same. The only remaining differenceâchanging the function's only argument from a pointer to a referenceâis superficial.</Text>
+<Text id="1229">Two other STL types widely used in the Greenstone code are <i>vector</i> and <i>set</i>. The former facilitates dynamic arrays, and the latter supports mathematical set operations such as union, intersection and difference.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="bibliography">
+<Title>
+<Text id="1230">Bibliography</Text>
+</Title>
+<Content>
+<Text id="1231">Aulds, C. (2000) <i>Linux Apache Web Server Administration</i>. Sybex.</Text>
+<Text id="1232">Bainbridge, D., Buchanan, G., McPherson, J., Jones, S., Mahoui, A. and Witten, I.H. (2001) âGreenstone: A platform for distributed digital library development.â Research Report, Computer Science Department, University of Waikato, New Zealand.</Text>
+<Text id="1233">Christiansen, T. Torkington, N. and Wall, L. (1998) <i>Perl Cookbook.</i> O'Reilly and Associates.</Text>
+<Text id="1234">Coar, K.A.L. (1998) <i>Apache Server For Dummies</i>. IDG Books.</Text>
+<Text id="1235">Deitel, H.M. and Deitel, P.J. (1994) <i>C++: How to Program</i>. Prentice Hall, Englewood Cliffs, New Jersey.</Text>
+<Text id="1236">Dublin Core (2001) âThe Dublin Core Metadata Initiativeâ at http://purl.org/dc/, accessed 16 January 2001.</Text>
+<Text id="1237">Josuttis, N.M. (1999) <i>The C++ standard library: a tutorial and reference.</i> Addison-Wesley, 1999.</Text>
+<Text id="1238">Keller, M. and Holden, G. (1999) <i>Apache Server for Windows Little Black Book</i>. Coriolis Group.</Text>
+<Text id="1239">Schwartz, R.L. and Christiansen, T. (1997) <i>Learning Perl</i>(2nd Edition). O'Reilly and Associates.</Text>
+<Text id="1240">Slama, D., Garbis, J. and Russell, P. (1999) <i>Enterprise CORBA</i>. Prentice Hall, Englewood Cliffs, New Jersey.</Text>
+<Text id="1241">Stroustroup, B. (1997) <i>The C++ Programming Language</i>. Addison-Wesley.</Text>
+<Text id="1242">Thiele, H. (1997) âThe Dublin Core and Warwick Framework: A Review of the Literature, March 1995âSeptember 1997.â <i>D-Lib Magazine</i>, January. &lt;http://www.dlib.org/dlib/january98/01thiele.html&gt;</Text>
+<Text id="1243">Wall, L., Christiansen, T. and Orwant, J. (2000) <i>Programming Perl</i>(3rd Edition). O'Reilly and Associates.</Text>
+<Text id="1244">Weibel, S. (1999) âThe State of the Dublin Core Metadata Initiative.â <i>D-Lib Magazine</i>, Volume 5 Number 4; April. &lt;http://www.dlib.org/dlib/april99/04weibel.html&gt;</Text>
+<Text id="1245">Witten, I.H., Moffat, A. and Bell, T.C. (1999) <i>Managing gigabytes: compressing and indexing documents and images</i>. Morgan Kaufmann, San Francisco.</Text>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="1246">On Windows 95/98 systems running <i>setup.bat</i> may fail with an <i>Out of environment space</i> error. If this happens, you should edit your system's <i>config.sys</i> file (normally found at <i>C:\config.sys</i>) and add the line <i>shell=C:\command.com /e:4096 /p</i> (where <i>C:</i> is your system drive letter) to expand the size of the environment table. You'll need to reboot for this change to take effect, and then repeat the steps above for Greenstone.</Text>
+</Footnote>
+<Footnote id="2">
+<Text id="1247">Note that in Greenstone, regular expressions are interpreted in the Perl language, which is subtly different from some other conventions. For example, â*â matches zero or more occurrences of the previous character, while â.â matches any characterâso <i>nugget.*</i> matches any string with prefix ânugget,â whether or not it contains a period after the prefix. To insist on a period you would need to escape it, and write <i>nugget\..*</i> instead.</Text>
+</Footnote>
+<Footnote id="3">
+<Text id="1248">Note that more recent versions of the Demo collection use a Hierarchy classifier to display the how to metadata. In this case they will be displayed slightly differently to what is shown in Figure <CrossRef target="Figure" ref="list_classifier"/>.</Text>
+</Footnote>
+<Footnote id="4">
+<Text id="1249">The value for <i>gsdlhome</i> comes from <i>gsdlsite.cfg</i> located in the same directory as the CGI executable <i>library</i>, whereas <i>GSDLHOME</i> is set by running the <i>setup</i> script which accesses a different file, so technically it is possible for the two values to be different. While possible, it is not desirable, and the above text is written assuming they are the same.</Text>
+</Footnote>
+<Footnote id="5">
+<Text id="1250">Technically there are four types, but the last two are optional. Since we are only giving a basic introduction to this STL class, details about these last two types are omitted.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/en/Install_en.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/en/Install_en.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/en/Install_en.xml	(revision 13632)
@@ -0,0 +1,1005 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">GREENSTONE DIGITAL LIBRARY</Text>
+</Heading>
+<Title>
+<Text id="2">INSTALLER'S GUIDE</Text>
+</Title>
+<Author>
+<Text id="3">Ian H. Witten and Stefan Boddie</Text>
+</Author>
+<Affiliation>
+<Text id="4">Department of Computer Science <br/>University of Waikato, New Zealand</Text>
+</Affiliation>
+<Text id="5">Greenstone is a suite of software for building and distributing digital library collections. It provides a new way of organizing information and publishing it on the Internet or on CD-ROM. Greenstone is produced by the New Zealand Digital Library Project at the University of Waikato, and developed and distributed in cooperation with UNESCO and the Human Info NGO. It is open-source software, available from <i>http://greenstone.org</i> under the terms of the Gnu General Public License.</Text>
+<Comment>
+<Text id="6">We want to ensure that this software works well for you. Please report any problems to <i>greenstone@cs.waikato.ac.nz</i></Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">March 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">About this manual</Text>
+</Title>
+<Content>
+<Text id="10">This document explains how to install Greenstone so that you can run it on your own computer. It also describes how to obtain associated software that is freely availableâthe Apache Webserver and Perl. We have striven to make the installation procedure as simple as it possibly can be.</Text>
+<Text id="11">The software runs on different platforms, and in different configurations. Consequently there are many issues that affect (or might affect) the installation procedure. Section <CrossRef target="Chapter" ref="versions_of_greenstone"/> mentions some questions that you will need to consider before installing Greenstone. Section <CrossRef target="Chapter" ref="installation_procedure"/> details the installation procedure for all the different versions; you need only read the part that relates to your operating system. Section <CrossRef target="Chapter" ref="greenstone_collections"/> describes the demonstration digital library collections that are included in the distribution. Section <CrossRef target="Chapter" ref="setting_up_webserver"/> explains how to set up common webservers, Apache and Microsoft PWS/IIS, to work with Greenstone. Section <CrossRef target="Chapter" ref="configuring_your_site"/> describes various Greenstone configuration options, and Section <CrossRef target="Chapter" ref="personalizing"/> shows how to make a personalized home page for your digital library installation. Finally, an Appendix <CrossRef target="Chapter" ref="appendix_associated_software"/> lists pieces of associated software and how to obtain them.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="12">Companion documents</Text>
+</Title>
+<Content>
+<Text id="13">The complete set of Greenstone documents include five volumes:</Text>
+<BulletList>
+<Bullet>
+<Text id="14">Greenstone Digital Library Installer's Guide <i>(this document)</i></Text>
+</Bullet>
+<Bullet>
+<Text id="15">Greenstone Digital Library User's Guide</Text>
+</Bullet>
+<Bullet>
+<Text id="16">Greenstone Digital Library Developer's Guide</Text>
+</Bullet>
+<Bullet>
+<Text id="17">Greenstone Digital Library: From Paper to Collection</Text>
+</Bullet>
+<Bullet>
+<Text id="18">Greenstone Digital Library: Using the Organizer</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">Acknowledgements</Text>
+</Title>
+<Content>
+<Text id="20">The Greenstone software is a collaborative effort between many people. Rodger McNab and Stefan Boddie are the principal architects and implementors. Contributions have been made by David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, and Stuart Yeates. Other members of the New Zealand Digital Library project provided advice and inspiration in the design of the system: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols and Lloyd Smith. We would also like to acknowledge all those who have contributed to the GNU-licensed packages included in this distribution: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE and XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="versions_of_greenstone">
+<Title>
+<Text id="21">Versions of Greenstone</Text>
+</Title>
+<Content>
+<Text id="22">The Greenstone software runs on different platforms, and in different configurations, as summarized in Figure <CrossRef target="Figure" ref="different_options"/>.</Text>
+<Figure id="different_options">
+<Title>
+<Text id="23">The different options for Windows and Unix versions of Greenstone</Text>
+</Title>
+<File width="542" height="264" url="images/Install_Fig_1.gif"/>
+</Figure>
+<Text id="24">There are many issues that affect (or might affect) the installation procedure. Before reading on, you should consider these questions:</Text>
+<BulletList>
+<Bullet>
+<Text id="25">Are you using Windows or Unix?</Text>
+</Bullet>
+<Bullet>
+<Text id="26">If Windows, are you using Windows 3.1/3.11 or a more recent version? Although you can view collections on 3.1/3.11 machines, and serve other computers on the same network, you cannot build new collections. The full Greenstone software runs on 95/98/Me, and NT/2000.</Text>
+</Bullet>
+<Bullet>
+<Text id="27">If Unix, are you using Linux or another version of Unix? For Linux, a binary version of the complete system is provided which is easy to install. For other types of Unix you will have to install the source code and compile it. This may require you to install some additional software on your machine.</Text>
+</Bullet>
+<Bullet>
+<Text id="28">If Windows NT/2000 or Unix, can you log in as the system âadministratorâ or ârootâ? This may be required to configure a webserver appropriately for Greenstone.</Text>
+</Bullet>
+<Bullet>
+<Text id="29">Do you want the source code? If you are using Windows or Linux, you can just install binaries. But you may want the source code as wellâit's in the Greenstone distribution.</Text>
+</Bullet>
+<Bullet>
+<Text id="30">Do you want to build new digital library collections? If so, you need to have Perl, which is freely available for both Windows and Unix.</Text>
+</Bullet>
+<Bullet>
+<Text id="31">Is your computer running a webserver? The Greenstone software comes with a Windows webserver. However, if you are already running a Web server, you may want to stay with it. For Unix, you need to run a webserver.</Text>
+</Bullet>
+<Bullet>
+<Text id="32">Do you know how to reconfigure your webserver? If you don't use the Greenstone webserver, you will have to reconfigure your existing one slightly to recognize the Greenstone software.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Chapter>
+<Chapter id="installation_procedure">
+<Title>
+<Text id="33">The Installation Procedure</Text>
+</Title>
+<Content>
+<Text id="34">Versions of Greenstone are available for both Windows and Unix, as binaries and in source code form. The Greenstone user interface uses a Web browser: Netscape Navigator or Internet Explorer (version 4.0 or greater in both cases) are both suitable. In case you don't already have a Web browser, Windows versions of Netscape are provided on the CD-ROM.</Text>
+<Section id="windows">
+<Title>
+<Text id="35">Windows</Text>
+</Title>
+<Content>
+<Text id="36">If you are a Unix user, please skip ahead to Section <CorssRef target="Section" ref="unix"/>. For Windows users, if you want just a simple, straightforward installation, go through the following âsimple installationâ procedure. The Greenstone system occupies about 40 Mb of disk space.</Text>
+<Text id="37">If you choose anything other than the default setup, you will have to decide whether you want to install the binary code or the source code. If in doubt, choose the binary code. The installation procedure is the same for both. The following sections tell you more about the options you will be presented with.</Text>
+<Text id="38">When you've finished installation you should skip ahead to Section <CorssRef target="Section" ref="how_to_find_greenstone"/>.</Text>
+<Subsection id="simple_installation">
+<Title>
+<Text id="39">Simple installation</Text>
+</Title>
+<Content>
+<Text id="40">To install the Windows version from the CD-ROM, insert the disk into the drive (e.g. into <i>D:</i>). If the installation procedure does not start automatically after about 20 seconds, click on the <i>Start</i> menu, select <i>Run</i> and type <i>D:\setup.exe</i>, where â <i>D</i> â is the letter that identifies your CD-ROM drive. For Windows 3.1, select <i>Run</i> from the âFile managerâ and type <i>D:\Windows\win3.1\setup.exe</i>.</Text>
+<Text id="41">For the simplest installation, just accept the default at each point by clicking the <i>Next</i> button. That's all you need to do! Greenstone is installed in the directory <i>C:\Program Files\gsdl</i>.</Text>
+<Text id="42">Once installation is complete, to start your Greenstone system click on the <i>Start</i> button, open the <i>Program</i> menu, and select <i>Greenstone Digital Library</i>. This brings up a dialogue box: just click <i>Enter Library.</i> This automatically starts your Internet browser and loads the Greenstone Digital Library home page, which should look something like the example in Figure <CrossRef target="Figure" ref="your_greenstone_home_page"/>. You enter the Greenstone Demo collection by clicking on its icon.</Text>
+<Figure id="your_greenstone_home_page">
+<Title>
+<Text id="43">Your Greenstone home page</Text>
+</Title>
+<File width="395" height="327" url="images/Install_Fig_2.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="windows_binaries">
+<Title>
+<Text id="44">Windows binaries</Text>
+</Title>
+<Content>
+<Text id="45">There are two separate Windows binary programs on the CD-ROM: the <i>Local Library</i> and the <i>Web Library</i>. The default installation described above selects the Local Library version. We strongly recommend that you use this version. The Web Library, which is much harder to set up, is only necessary if you already run a web server and want to use it for Greenstone. Despite its modest name, the Local Library offers a complete, self-contained, web-serving capability.</Text>
+<Text id="46">Local Library. This enables any Windows computer to serve pre-built Greenstone collections. The Greenstone Demo collection will automatically be installed; you can also install the other collections on the CD-ROM (Section <CrossRef target="Chapter" ref="greenstone_collections"/>). The Local Library software is the same as that used on CD-ROMs produced by the Greenstone system.</Text>
+<Text id="47">The Local Library is intended for use on standalone computers or computers that do not already have webserver software. It contains a small built-in webserver so that other computers on the same network can also access the library. (However, the webserver has limited configurability.)</Text>
+<Text id="48">The Local Library software automatically determines whether your computer has network software installed or is connected to a network. It operates correctly under any combinations of these conditions. However, there are two possible problems that may be encountered. Greenstone may</Text>
+<BulletList>
+<Bullet>
+<Text id="49">cause an unwanted telephone dialup operation;</Text>
+</Bullet>
+<Bullet>
+<Text id="50">fail to run because network software is installed, but installed incorrectly.</Text>
+</Bullet>
+</BulletList>
+<Text id="51">A restricted version of the Local Library is supplied which is intended for use in these situations. The restricted version only works with Netscape (not Internet Explorer). When you invoke the Local Library version of Greenstone, the dialogue box contains a button that allows you to use the restricted version instead. Unless the above problems arise, you should always use the standard version.</Text>
+<Text id="52"><b>Web Library</b>. This enables any computer with an existing webserver to serve pre-built Greenstone collections. As with the Local Library above, the Greenstone Demo collection will automatically be installed. You can also install the other collections on the CD-ROM (see Section <CrossRef target="Chapter" ref="greenstone_collections"/>).</Text>
+<Text id="53">The Web Library differs from the Local Library because it is intended for computers that already have webserver software.</Text>
+<Text id="54">To run the Web Library, you also need</Text>
+<BulletList>
+<Bullet>
+<Text id="55">Webserver software. One possibility is Apache (see Appendix <CrossRef target="Chapter" ref="appendix_associated_software"/>).</Text>
+</Bullet>
+<Bullet>
+<Text id="56"><b>The Collector</b>. This component, which is included in both the Local Library and the Web Library, allows you to build collections containing material of your choice. (You will not be able to use the Collector on a Windows 3.1/3.11 machine.)</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="windows_webserver_configuration">
+<Title>
+<Text id="57">Windows webserver configuration (Web Library version only)</Text>
+</Title>
+<Content>
+<Text id="58">An advantage of the Local Library version of Greenstone is that it runs âout of the boxâ and does not require any special configuration. For the Web Library version, however, you will have to make some adjustments to your webserver setup.</Text>
+<Text id="59">If you already have a webserver, some small changes have to be made to its configuration to make your Greenstone installation operate. The install script explains what these are for the Apache webserverâsee Section <CrossRef target="Section" ref="pws_and_iis_webservers"/> for instructions for configuring the PWS and IIS webservers. You may need help from a system administrator to reconfigure an existing webserverâthey should be able to understand the instructions printed by the install script.</Text>
+<Text id="60">If you do not already have a webserver, you will have to install one. (See the Appendix <CrossRef target="Chapter" ref="appendix_associated_software"/> for information on the Apache webserver.) Then you will have to configure it appropriately. Section <CrossRef target="Chapter" ref="setting_up_webserver"/> gives a detailed account of the parts of a webserver installation that affect Greenstone, and how they need to be altered. It comes down to including half a dozen or so lines in a configuration file.</Text>
+</Content>
+</Subsection>
+<Subsection id="windows_source">
+<Title>
+<Text id="61">Windows source</Text>
+</Title>
+<Content>
+<Text id="62">The Greenstone source code occupies 50 Mb of disk space, but to compile it you will need about 90 Mb. To compile the source on Windows you need</Text>
+<BulletList>
+<Bullet>
+<Text id="63">The Microsoft Visual C++ compiler. (We are currently sorting out some minor problems in compiling Greenstone with various Windows ports of GNU GCC.)</Text>
+</Bullet>
+</BulletList>
+<Text id="64">(You do not need GDBM, the Gnu database manager, because it is included in the Greenstone source distribution.)</Text>
+<Text id="65">It is unlikely that you will be able to compile Greenstone on a Windows 3.1/3.11 machine.</Text>
+<Text id="66">In the event that you recompile Greenstone and wish to use the recompiled version to create CD-ROMs, you should note that code produced by recent versions of the Visual C++ compiler does not run under Windows 3.1/3.11, although there is no problem with later Windows systems (95, 98, Me, NT, 2000). If you want your CD-ROMs to operate on early Windows machines, you will need a different version of the compiler. Moreover, Greenstone uses STL, the C++ standard template library, and although these compilers sometimes come with STL, the provided version does not always work properly. Hence to recompile Greenstone in such a way that it produces CD-ROMs that work on early versions of Windows, you need</Text>
+<BulletList>
+<Bullet>
+<Text id="67">The Microsoft Visual C++ compiler, Version 4.0 or 4.2.</Text>
+</Bullet>
+<Bullet>
+<Text id="68">An external version of STL, the C++ standard template library. STL is packaged with Greenstone for use with these compiler versions.</Text>
+</Bullet>
+</BulletList>
+<Text id="69">Note that the Windows installation procedure does not attempt to compile Greenstone for you if you choose to install the source code. For platform- and compiler-specific instructions on compiling Greenstone, see the <i>Install.txt</i> document which is placed in the top-level Greenstone directory (<i>C:\Program Files\gsdl</i> by default) during the installation procedure.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="unix">
+<Title>
+<Text id="70">Unix</Text>
+</Title>
+<Content>
+<Text id="71">This section is written for Unix users. (Windows users should skip ahead to Section <CrossRef target="Section" ref="how_to_find_greenstone"/>.) You need to choose whether to install the binary code or the source code. The binary code occupies about 50 Mb of disk space; the source code requires about 160 Mb to compile.</Text>
+<Subsection id="unix_binaries">
+<Title>
+<Text id="72">Unix binaries</Text>
+</Title>
+<Content>
+<Text id="73">The binary code requires an Intel x86-based Linux distribution which includes ELF binary support. Distributions that meet these requirements include:</Text>
+<BulletList>
+<Bullet>
+<Text id="74">RedHat 5.1</Text>
+</Bullet>
+<Bullet>
+<Text id="75">SuSE Linux 6.1</Text>
+</Bullet>
+<Bullet>
+<Text id="76">Debian 2.1</Text>
+</Bullet>
+<Bullet>
+<Text id="77">Slackware 4.0</Text>
+</Bullet>
+</BulletList>
+<Text id="78">More recent versions of these distributions should also work.</Text>
+<Text id="79">You will need a webserver: we recommend Apache. We also strongly recommend you to install your webserver <i>before</i> installing Greenstoneâthis will make it much easier to answer the questions that are asked during the Greenstone installation procedure. If you want to build new digital library collections, you will also need Perl if this is not already on your system. To check, open a terminal window, type <i>perl âv</i>, and see if a message appears specifying, amongst other things, the version number. For most versions of Linux, Perl is installed by default. The Appendix <CrossRef target="Chapter" ref="appendix_associated_software"/> gives information on how to obtain Apache and Perl.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_source">
+<Title>
+<Text id="80">Unix source</Text>
+</Title>
+<Content>
+<Text id="81">The source code is the same for Unix as for Windows. It has been compiled and tested on Linux, Solaris, and Macintosh OS/X; it should be a fairly routine matter to port it to other flavors of Unix.</Text>
+<Text id="82">To compile the Greenstone source code on Unix, you need</Text>
+<BulletList>
+<Bullet>
+<Text id="83">GCC, the Gnu C++ compiler.</Text>
+</Bullet>
+<Bullet>
+<Text id="84">GDBM, the Gnu database manager.</Text>
+</Bullet>
+</BulletList>
+<Text id="85">To run the Greenstone software, you also need a Web server and Perl, as described above under <i>Unix binaries</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_installation">
+<Title>
+<Text id="86">Unix installation</Text>
+</Title>
+<Content>
+<Text id="87">To install the Unix version from the CD-ROM, insert the disk into the drive, and type</Text>
+<Table class="hidden" id="table_commands">
+<Title/>
+<TableContent>
+<tr>
+<th width="151">
+<CodeLine>mount /cdrom</CodeLine>
+</th>
+<th width="246">
+<Text id="88">mount the CD-ROM device (this command may differ from one system to another; for example on OS/X you <i>cd</i> to the <i>/Volumes</i> directory and then to the appropriate subdirectory for the CD-ROM)</Text>
+</th>
+</tr>
+<tr>
+<th width="151">
+<CodeLine>cd /cdrom</CodeLine>
+</th>
+<th width="246">
+<Text id="89">change directory to the CD-ROM's top level</Text>
+</th>
+</tr>
+<tr>
+<th width="151">
+<CodeLine>cd Unix</CodeLine>
+</th>
+<th width="246">
+<Text id="90">change directory to where the Unix install script resides</Text>
+</th>
+</tr>
+<tr>
+<th width="151">
+<CodeLine>sh Install.sh</CodeLine>
+</th>
+<th width="246">
+<Text id="91">begin the installation process (an explicit <i>sh</i> is used because many installations forbid you to execute programs directly from CD-ROM)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="92">The final command begins an interactive dialogue which requests the information that is needed to install Greenstone on your system, and gives detailed feedback on what is happening.</Text>
+<Text id="93">The installation procedure begins by asking you which directory to install Greenstone into. The first file placed there is the âuninstallâ program that cleans up any partial installation, should you encounter problems or terminate the installation prematurely. Next you choose whether you want to install binaries or source code. You are then asked some questions about your webserver setup. You need to have a valid cgi executable directory (normally called âcgi-binâ on Unix systems); you can either create a new one or use your existing one. If you create a new one, you will need to enter this information in your webserver's configuration file. In either case you need to enter the web address of the cgi directory. The installation dialogue will guide you through all these choices. It is important to set the file permissions correctly on certain directories, and you are prompted for the necessary information. Finally, you are prompted for a password for the âadministratorâ user <i>admin</i>.</Text>
+<Text id="94">By default, all Greenstone software is installed in the directory <i>/usr/local/gsdl</i> if it is the root user who is doing the installation, and into the directory ~<i>/gsdl</i> otherwise (where â~â is the user's home directory).</Text>
+<Text id="95">Installing the binaries takes just a few minutes, enough time for you to answer the appropriate questions. If you install the source code, the installation script will compile it, which takes from ten minutes to an hour or so, depending on the speed of your processor.</Text>
+<Text id="96">To uninstall the software, type</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<Text id="97">or <i>/usr/local/gsdl</i> if it was the root user who installed Greenstone</Text>
+<CodeLine>sh Uni nstall.sh</CodeLine>
+<Text id="98">During the installation procedure you will be asked whether you want to install any Greenstone collections. The Greenstone Demo collection is installed automatically; other collections on the CD-ROM are described in Section <CrossRef target="Chapter" ref="greenstone_collections"/>.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_webserver_configuration">
+<Title>
+<Text id="99">Unix webserver configuration</Text>
+</Title>
+<Content>
+<Text id="100">If you already have a webserver, some small changes will have to be made to its configuration to make your Greenstone installation operate. The install script explains what these are. You will probably need help from your system administrator to reconfigure the webserverâhe or she should be able to understand the instructions output by the install script. For your convenience, the output of the install script is written to a file called INSTALL_RECORD in the directory into which you installed Greenstone.</Text>
+<Text id="101">If you do not already have a webserver, you will have to install one. The Appendix <CrossRef target="Chapter" ref="appendix_associated_software"/> gives information on Apache. Then you will have to configure it appropriately. Section <CrossRef target="Chapter" ref="setting_up_webserver"/> gives a detailed account of the parts of an Apache webserver installation that affect Greenstone, and how they need to be altered. It comes down to including half a dozen or so lines in a configuration file.</Text>
+<Text id="102">You do not need to be the Unix ârootâ user to go through the installation procedure above. When it comes to configuring an existing Apache server, however, you may need ârootâ privilegesâit all depends on how Apache is set up. If you install Apache yourself, you can do it as a user without ârootâ privileges. If you need to work your way around an uncooperative system administrator, you can always install a second Apache webserver on your computerâeven if one exists already.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="how_to_find_greenstone">
+<Title>
+<Text id="103">How to find Greenstone</Text>
+</Title>
+<Content>
+<Subsection id="local_library_windows_only">
+<Title>
+<Text id="104">Local library (Windows only)</Text>
+</Title>
+<Content>
+<Text id="105">If you are using the Local Library, simply run the <i>Greenstone</i> program from the <i>Start</i> menu. This automatically opens a dialog box that starts your Internet browser and loads the Greenstone Digital Library home page. The Greenstone Demo collection should be accessible from this page. The dialog box contais a <i>File</i> menu item that allows you to change the default browser used by Greenstone. It doesn't matter whether you use Netscape or Internet Explorer, except that if you are running on Windows 2000, we recommend that you use Internet Explorer.</Text>
+</Content>
+</Subsection>
+<Subsection id="web_library_windows_and_unix">
+<Title>
+<Text id="106">Web library (Windows and Unix)</Text>
+</Title>
+<Content>
+<Text id="107">If you are using the Web Library, once you have installed the software and configured the webserver, use this URL to enter your Greenstone system:</Text>
+<Text id="108"><i>http://localhost/gsdl/cgi-bin/library</i></Text>
+<Text id="109">The Greenstone Demo collection should be accessible from this page.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_collector">
+<Title>
+<Text id="110">The Collector</Text>
+</Title>
+<Content>
+<Text id="111">A link to the Collector is provided on the digital library home page.</Text>
+</Content>
+</Subsection>
+<Subsection id="administration">
+<Title>
+<Text id="112">Administration</Text>
+</Title>
+<Content>
+<Text id="113">A link to the Administration pages is provided on the digital library home page. The âadministratorâ user is called <i>admin</i>, with a password that you specified during the installation process. The administrator is authorized to add new users, and to build collections.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="the_greenstone_librarian_interface_(gli)">
+<Title>
+<Text id="114">The Greenstone Librarian Interface (GLI)</Text>
+</Title>
+<Content>
+<Text id="115">The Greenstone Librarian Interface (GLI) is a tool to assist you with building digital libraries using Greenstone. It gives you access to Greenstone's collection-building functionality from an easy-to-use âpoint and clickâ interface.</Text>
+<Text id="116">GLI is installed automatically with all distributions of Greenstone. It is placed in the subdirectory <i>gli</i> of the top-level Greenstone directory (<i>C:\Program Files\gsdl\gli</i> by default). Note that it runs in conjunction with Greenstone and will not work properly unless it is placed in a subdirectory of your Greenstone installation. If you have downloaded one of the Greenstone distributions, this will be the case.</Text>
+<Text id="117">To use the GLI, your computer needs to have the Java Runtime Environment. If it doesn't, the installer will offer to install a version that is included on the CD-ROM. On Unix, you will also need to ensure that Perl is installed (for Windows, Perl is already included in the Greenstone software). Please report any problems you have running or using the Librarian Interface to <u>greenstone@cs.waikato.ac.nz</u>.</Text>
+<Subsection id="running_under_windows">
+<Title>
+<Text id="118">Running under Windows</Text>
+</Title>
+<Content>
+<Text id="119">To run GLI under Windows, browse to the <i>gli</i> folder in your Greenstone installation (e.g. using Windows Explorer), and double-click on the file called <i>gli.bat</i>. This file checks that Greenstone, the Java Runtime Environment, and Perl are all installed, and starts the Greenstone Librarian Interface.</Text>
+</Content>
+</Subsection>
+<Subsection id="running_under_unix">
+<Title>
+<Text id="120">Running under Unix</Text>
+</Title>
+<Content>
+<Text id="121">To run GLI under Unix, change to the <i>gli</i> directory in your Greenstone installation, then run the <i>gli.sh</i> script. This script checks that Greenstone, the Java Runtime Environment, and Perl are all installed and on your search path, and starts the Greenstone Librarian Interface.</Text>
+</Content>
+</Subsection>
+<Subsection id="getting_help">
+<Title>
+<Text id="122">Getting help</Text>
+</Title>
+<Content>
+<Text id="123">The Greenstone Librarian Interface has extensive on-line help facilities. You get help by clicking the <i>Help</i> button at the top right of the screen. This opens up the text to a section that relates to what you are doingâwhich of the GLI panels you are on. You can click around the help text to learn what you need to know. Use it.</Text>
+</Content>
+</Subsection>
+<Subsection id="compiling_gli">
+<Title>
+<Text id="124">Compiling the Greenstone Librarian Interface</Text>
+</Title>
+<Content>
+<Text id="125">If you have downloaded the Greenstone source distribution, you will have the Java source code of the Librarian Interface. To compile it, your computer needs to have a Java Development Kit. The Appendix <CrossRef target="Chapter" ref="appendix_associated_software"/> gives information on how to obtain this. To compile the source code, run the <i>makegli.bat</i>(Windows) or <i>makegli.sh</i>(Unix) files. Once compiled, you can run GLI as described above.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="testing_and_troubleshooting">
+<Title>
+<Text id="126">Testing and troubleshooting</Text>
+</Title>
+<Content>
+<Text id="127">To test Greenstone, point your Web browser at the Greenstone home page and explore the Demo collection and any other collections that you have installed. Don't worryâyou can't break anything. Click liberally: most images that appear on the screen are clickable. If you hold the mouse stationary over an image, most browsers will soon pop up a message that tells you what will happen if you click. Experiment! Choose common words like âtheâ and âandâ to search forâthat should evoke some responses, and nothing will break.For more information, see the <i>Greenstone Digital Library User's Guide</i>.</Text>
+<Subsection id="troubleshooting">
+<Title>
+<Text id="128">Troubleshooting</Text>
+</Title>
+<Content>
+<Table id="table_troubleshooting">
+<Title/>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="129">Problem</Text>
+</th>
+<th width="246">
+<Text id="130">Try this</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="131">Local Library (Windows only)</Text>
+</th>
+<th width="151">
+<Text id="132">When I start Greenstone my computer asks me to dial up my Internet Service Provider.</Text>
+</th>
+<th width="246">
+<Text id="133">Push the <i>Cancel</i> button in the dialog box. This usually solves the problem.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="134">When I start Greenstone my computer <i>still</i> asks me to dial up my Internet Service Provider.</Text>
+</th>
+<th width="246">
+<Text id="135">Choose the âRestricted versionâ when you run Greenstone. This version only works with Netscape.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="136">When I point my browser at the digital library, it can't find that page.</Text>
+</th>
+<th width="246">
+<Text id="137">Check your Internet Proxy settings and turn proxies off (use <i>Edit preferences</i> on Netscape or <i>Internet options</i> on Explorer).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="138">The Collector seems to be working very slowly!</Text>
+</th>
+<th width="246">
+<Text id="139">Are you using Netscape under Windows 2000? If so, try using Internet Explorer insteadâon Windows 2000 (only) there seems to be some incompatibility with Netscape.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="142">Web Library (Windows and Unix)</Text>
+</th>
+<th width="151">
+<Text id="143">When I start Apache, it quits immediately.</Text>
+</th>
+<th width="246">
+<Text id="144">Add a <i>ServerName localhost</i> directive to the Apache configuration file (see Section <CrossRef target="Section" ref="apache_web_server"/>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="145">When I point my browser at the digital library, it displays garbageâa binary file.</Text>
+</th>
+<th width="246">
+<Text id="146">Check the <i>ScriptAlias</i> directive in the Apache configuration file, making sure it comes before the <i>Alias</i> directive (see Sections 4.2 and 4.3).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="147">I get the Greenstone home page (Figure <CrossRef target="Figure" ref="your_greenstone_home_page"/>), but the Demo collection icon does not appear.</Text>
+</th>
+<th width="246">
+<Text id="148">Run the program <i>library</i> (in the cgi-bin directory) from the DOS (or shell) prompt to generate debugging information that will help you locate the problem.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="149">Both versions</Text>
+</th>
+<th width="151">
+<Text id="150">When I point my browser at the digital library, it can't find that page.</Text>
+</th>
+<th width="246">
+<Text id="151">Try using 127.0.0.1 in place of <i>localhost</i>. This reserved IP number is defined to be a âloopbackâ to your local computer.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="152">My browser complains that it can't find <i>main.cfg</i>.</Text>
+</th>
+<th width="246">
+<Text id="153">Check that the Greenstone files exist and are world-readable. If you are using the Web library, try running the <i>library</i> program from the command line. If it runs OK, the problem is with file permissions (see Section <CrossRef target="Section" ref="file_permissions"/>). If not, the <i>gsdlhome</i> variable is probably set incorrectly in the <i>gsdlsite.cfg</i> configuration file (see Section <CrossRef target="Section" ref="gsdlsite_configuration_file"/>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="154">I'm having trouble using the Collector.</Text>
+</th>
+<th width="246">
+<Text id="155">Read the <i>Greenstone Digital Library User's Guide</i>, Section <CrossRef external="User" lang="en" target="Chapter" ref="making_greenstone_collections"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="156">I've added a new user but they can't seem to log in.</Text>
+</th>
+<th width="246">
+<Text id="157">Check that the directory <i>C:\Program Files\gsdl\etc</i> and all its contents are globally writeable (see Section <CrossRef target="Section" ref="file_permissions"/>).</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="learn_more">
+<Title>
+<Text id="158">To learn more</Text>
+</Title>
+<Content>
+<Text id="159">To learn more about the innards of your Greenstone installation, consult the <i>Greenstone Digital Library Developer's Guide</i>. It includes (for example) details of the directory structure that has been created, and information about how to configure your Greenstone site.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="greenstone_collections">
+<Title>
+<Text id="160">Greenstone Collections</Text>
+</Title>
+<Content>
+<Text id="161">Several demonstration Greenstone collections are included on the CD-ROM. If you have Web access, many others can be downloaded, in either pre-built or unbuilt form, from the New Zealand Digital Library Project website (<i>nzdl.org</i>).</Text>
+<Text id="162">The Greenstone Demo collection is a small subset of the Humanity Development Library (HDL), a polished collection. It illustrates that relatively rich browsing capabilities can be provided (so long as suitable metadata is available). It is included automatically when the software is installed.</Text>
+<Text id="163">Greenstone also comes with some well-documented example collections whose âaboutâ page describes how they are constructed. They demonstrate various capabilities of Greenstone. The install dialogue will ask you whether you want to include them in your Greenstone installation; the approximate amount of disk space needed for each collection is shown below.</Text>
+<Table class="hidden" id="table_collections">
+<Title/>
+<TableContent>
+<tr>
+<th width="60">
+<Text id="164"><i>demo</i></Text>
+</th>
+<th width="182">
+<Text id="165">Greenstone Demo<br/>(7 Mb)</Text>
+</th>
+<th width="294">
+<Text id="166">A small subset of the HDL. If you clone this collection, the full facilities will only appear if your new files provide appropriate metadata information.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="167"><i>dls-e</i></Text>
+</th>
+<th width="182">
+<Text id="168">Development Library Subset collection<br/>(150 Mb)</Text>
+</th>
+<th width="294">
+<Text id="169">Like the Greenstone Demo, this is a subset of the HDLâbut much larger. It contains 250 publicationsâbooks, reports and magazinesâin various areas of human development (the full HDL contains 1,230 publications). It has the same structure as the Greenstone Demo. It's fairly complex, and if you're just starting out you might prefer to look at some other collections first (e.g. <i>MSWord and PDF demonstration</i>, the <i>Greenstone Archives</i>, or the <i>Simple image collection</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="170"><i>wrdpdf-e</i></Text>
+</th>
+<th width="182">
+<Text id="171">MSWord and PDF demonstration<br/>(4 Mb)</Text>
+</th>
+<th width="294">
+<Text id="172">This contains a few documents in PDF, MSWord, RTF, and Postscript formats, demonstrating the ability to build collections from documents in different formats. The collection configuration file is very simple.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="173"><i>gsarch-e</i></Text>
+</th>
+<th width="182">
+<Text id="174">Greenstone Archives collection<br/>(5 Mb)</Text>
+</th>
+<th width="294">
+<Text id="175">A collection of email messages from the Greenstone mailing list archives, this uses the Email plugin, which parses files in email formats. The collection configuration file is very simple.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="176"><i>cltbib-e</i></Text>
+</th>
+<th width="182">
+<Text id="177">Bibliography collection<br/>(7 Mb)</Text>
+</th>
+<th width="294">
+<Text id="178">With about 4,000 bibliography entries, this collection incorporates a form-based search interface that allows fielded searching. It is fairly complex.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="179"><i>cltext-e</i></Text>
+</th>
+<th width="182">
+<Text id="180">Bibliography supplement<br/>(1 Mb)</Text>
+</th>
+<th width="294">
+<Text id="181">This tiny collection of 10 bibliography entries illustrates the "supercollection" facility which searches several collections together, seamlessly. It operates together with the <i>Bibliography</i> collection, and its configuration file is almost the same.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="182"><i>MARC-e</i></Text>
+</th>
+<th width="182">
+<Text id="183">MARC example<br/>(1 Mb)</Text>
+</th>
+<th width="294">
+<Text id="184">Based on some MARC records from the Library of Congress, this is a simple collection (and does not allow form-based searching).</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="185"><i>oai-e</i></Text>
+</th>
+<th width="182">
+<Text id="186">OAI demo collection<br/>(18 Mb)</Text>
+</th>
+<th width="294">
+<Text id="187">Using the Open Archive Protocol and the <i>Import-From</i> feature, this retrieves metadata from an archive and builds a collection from the records. In this case they are images, so both the OAI and Image plugins are used.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="188"><i>image-e</i></Text>
+</th>
+<th width="182">
+<Text id="189">Simple image collection<br/>(1 Mb)</Text>
+</th>
+<th width="294">
+<Text id="190">This very basic image collection contains no text and no explicit metadataâwhich makes it rather unrealistic. The configuration file is about as simple as you can get.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="191"><i>authen-e</i></Text>
+</th>
+<th width="182">
+<Text id="192">Formatting and authentication demo<br/>(8 Mb)</Text>
+</th>
+<th width="294">
+<Text id="193">With the same material as the original Greenstone demo collection, this shows off two independent features: non-standard document formatting, and controlled access to the documents via user authentication.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="194"><i>garish</i></Text>
+</th>
+<th width="182">
+<Text id="195">Garish version of demo collection<br/>(8 Mb)</Text>
+</th>
+<th width="294">
+<Text id="196">This collection also contains the same material as the Greenstone demo. Its appearance has been altered to show how the pages generated can be set out differently. It relies on a non-standard macro file that is supplied with Greenstone.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="197"><i>isis-e</i></Text>
+</th>
+<th width="182">
+<Text id="198">CDS/ISIS example (1 Mb)</Text>
+</th>
+<th width="294">
+<Text id="199">This collection is built from a CDS/ISIS database of about 150 bibliography entries. It uses the ISISPlug plugin, which reads the standard ISIS .mst and .fdt files and converts them to Greenstone metadata.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<Chapter id="setting_up_webserver">
+<Title>
+<Text id="200">Setting up the Webserver</Text>
+</Title>
+<Content>
+<Text id="201">In this section we describe how to set up your webserver to work with Greenstone. Note that all this is unnecessary when using the Windows Local Library, because this software works âout of the boxâ and does not require a webserver.</Text>
+<Text id="202">We discuss both the Apache webserver, which is freely available for both Windows and Unix (see the Appendix <CrossRef target="Chapter" ref="appendix_associated_software"/> for details) and Microsoft's Personal Web Server (PWS) and Internet Information Services (IIS) webserver. PWS is the standard Microsoft server for Windows 95/98; IIS is the standard webserver for Windows 2000 and the forthcoming Win dows XP ; Windows NT can use either. The Apache description applies equally to the Windows Web Library and Unix versions (though we use Windows-style terminology and pathnames); the PWS/IIS section applies only to the Windows Web Library.</Text>
+<Text id="203">Once you have installed your webserver, the next step is to install Greenstone. We will assume that during the install procedure you have taken the default action for each stage by clicking on the <i>Next</i> button. The result is that the directory <i>C:\Program Files\gsdl</i> is created and the Web Library binary is stored there, along with some supporting files.</Text>
+<Text id="204">All webservers use the special URL âlocalhostâ to denote the computer that the webserver is running on. Thus when you install a webserver, you can get at your html documents by typing the URL <i>http://localhost</i> into a browser. If your computer has a domain name set up, this is used instead of localhost to identify your computer from remote sites. Thus on the New Zealand Digital Library's computer, <i>http://nzdl.org</i> and <i>http://localhost</i> are equivalent. If you type <i>http://nzdl.org</i> on your computer you will get the New Zealand Digital Library webserver, whereas if you type <i>http://localhost</i> you will get your own computer's webserver.</Text>
+<Section id="apache_web_server">
+<Title>
+<Text id="205">The Apache web server</Text>
+</Title>
+<Content>
+<Text id="206">The Apache webserver is usually installed in <i>C:\Program Files\Apache Group\Apache</i> and is configured so that the cgi-bin directory is in the subdirectory <i>\cgi-bin</i> and the document root is the subdirectory <i>\htdocs</i>. It is reconfigured by editing the configuration file <i>C:\Program Files\Apache Group\Apache\conf\httpd.conf</i>. This is a text file: it's quite easy to read it to see how things are set up.</Text>
+<Text id="207">Depending on how your computer's networking software is set up, you may have to add this line to Apache's <i>httpd.conf</i> configuration file:</Text>
+<CodeLine>ServerName localhost</CodeLine>
+<Text id="208">If this line is not included, the system attempts to find your server's name. However, there are bugs in some versions of Windows that cause this to fail. In this case, Apache will exit immediately when you start it up. It does display an error message, but it is immediately erased and you probably can't read it.</Text>
+<Subsection id="setting_up_cgi-bin_directory">
+<Title>
+<Text id="209">Setting up the Greenstone cgi-bin directory</Text>
+</Title>
+<Content>
+<Text id="210">Cgi-bin is a directory from which the webserver treats documents as executable programs. Apache's <i>ScriptAlias</i> directive is used to create a cgi-bin directory. Note that this directive can make any directory a cgi executable directoryâit doesn't have to be called âcgi-binâ! Conversely, a directory called âcgi-binâ isn't special unless <i>ScriptAlias</i> has been applied to it.</Text>
+<Text id="211">When installed, Apache has a cgi-bin directory of <i>C:\Program Files\Apache Group\Apache\cgi-bin</i>. This means that if presented with the URL <i>http://localhost/cgi-bin/hello</i>, the webserver will attempt to execute a file called <i>hello</i> from within the above directory.</Text>
+<Text id="212">There is one Greenstone program, which is called âlibrary.exeâ, that needs to be executed by the webserver; it in turn reads a file called the Greenstone site configuration file, or âgsdlsite.cfgâ, which needs to be located in the same directory.</Text>
+<Text id="213">The best way of arranging this is to use Apache's <i>ScriptAlias</i> directive to create a new cgi-bin directory. Here's the excerpt from Apache's <i>httpd.conf</i> configuration file that adds <i>C:\Program Files\gsdl\cgi-bin</i> as an additional cgi-bin directory:</Text>
+<CodeLine>ScriptAlias /gsdl/cgi-bin/ "C:/Program Files/gsdl/cgi-bin/"</CodeLine>
+<CodeLine>&lt;Directory C:/Program Files/gsdl/cgi-bin&gt;</CodeLine>
+<CodeLine>  Options None</CodeLine>
+<CodeLine>  AllowOverride None</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="214">(It's a curious fact that Apache configuration files use forward slashes in place of standard Windows backslashes.)</Text>
+<Text id="215">This means that any URLs of the form <i>http://localhost/gsdl/cgi-bin</i>... will be sought in the directory <i>C:\Program Files\gsdl\cgi-bin</i>, and executed by the web server. For example, if presented with the URL <i>http://localhost/gsdl/cgi-bin/hello</i>, the web server will attempt to retrieve the file <i>C:\Program Files\gsdl\cgi-bin\hello</i> and execute it. However, the URL <i>http://localhost/cgi-bin/hello</i> looks in Apache's regular <i>cgi-bin</i> directory for the file <i>C:\Program Files\Apache Group\Apache\</i> <i>cgi-bin\hello</i> and executes it, just as it did before.</Text>
+</Content>
+</Subsection>
+<Subsection id="document_root_directory">
+<Title>
+<Text id="216">The document root directory</Text>
+</Title>
+<Content>
+<Text id="217">The document root directory is the root of your webserver's directory structure. When installed, Apache has a document root <i>of C:\Program Files\Apache Group\Apache\htdocs</i>. This means that if presented with the URL <i>http://localhost/hello.html</i>, the webserver will attempt to retrieve a file called <i>hello.html</i> from within the above directory.</Text>
+<Text id="218">Several files within Greenstone need to be read by the webserver. The simplest way to arrange this is to use the <i>Alias</i> directive, which is just like <i>ScriptAlias</i> except that it applies to ordinary web pages, not cgi scripts. Insert these lines into your Apache configuration file, after the <i>ScriptAlias</i> directive, to add <i>C:\Program Files\gsdl</i> as an additional place to look for documents.</Text>
+<CodeLine>Alias /gsdl/ "C:/Program Files/gsdl/"</CodeLine>
+<CodeLine>&lt;Directory C:/Program Files/gsdl&gt;</CodeLine>
+<CodeLine> Options Indexes MultiViews FollowSymLinks</CodeLine>
+<CodeLine> AllowOverride None</CodeLine>
+<CodeLine> Order allow,deny</CodeLine>
+<CodeLine> Allow from all</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="219">This means that any URLs that match the first argument of Alias (gsdl) are sought as files in the place corresponding to the second argument. In other words, URLs of the form <i>http://localhost/gsdl/</i>... will be sought as files in the directory <i>C:\Program Files\gsdl</i>. For example, if presented with the URL <i>http://localhost/gsdl/hello.html</i>, the webserver will attempt to retrieve the file <i>C:\Program Files\gsdl\hello.html</i>. However, the URL <i>http://localhost/hello.html</i> looks in the regular <i>htdocs</i> directory for the file <i>C:\Program Files\Apache Group\Apache\htdocs\hello.html</i>, just as it did before.</Text>
+<Text id="220">Be sure to add the <i>Alias</i> directive after the <i>ScriptAlias</i> directive. Instructing Apache to alias <i>/gsdl</i> before <i>/gsdl/cgi-bin</i> would match the URL <i>/gsdl/cgi-bin/library</i> against the Alias directive rather than the ScriptAlias, and it would be interpreted as a request for a document rather than the result of executing a program. The outcome would be to âdisplayâ the binary program file as a page in the Web browser, instead of executing it.</Text>
+</Content>
+</Subsection>
+<Subsection id="security">
+<Title>
+<Text id="221">Security</Text>
+</Title>
+<Content>
+<Text id="222">You should be aware that if the web library version of Greenstone is set up as instructed above, anyone will be allowed to download any file in the <i>gsdl</i> directory structure. This includes the index files and source documents of any collections you make, the user database, usage logs, etc.</Text>
+<Text id="223">If you are concerned about this, you can easily tighten up your webserver configuration to improve security. For the Apache webserver, put these lines into the configuration file instead of those given in the previous subsection:</Text>
+<CodeLine>Alias /gsdl/ "C:/Program Files/gsdl/"</CodeLine>
+<CodeLine>&lt;Directory "C:/Program Files/gsdl"&gt;</CodeLine>
+<CodeLine>   Order allow,deny</CodeLine>
+<CodeLine>   Deny from all</CodeLine>
+<CodeLine>   &lt;FilesMatch</CodeLine>
+<CodeLine>"\.(gif|jpe?g|png|css|mov|mpeg|ps|pdf|doc|rtf|jar|class)$"&gt;</CodeLine>
+<CodeLine>         Order allow,deny</CodeLine>
+<CodeLine>         Allow from all</CodeLine>
+<CodeLine>   &lt;/FilesMatch&gt;</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="224">This means that only files whose extensions match the regular expression in the <i>FilesMatch</i> line may be downloaded.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="pws_and_iis_webservers">
+<Title>
+<Text id="225">The PWS and IIS webservers</Text>
+</Title>
+<Content>
+<Text id="226">Although neither PWS nor IIS is installed by default on current Windows systems, they can easily be installed using the âAdd/Remove programsâ control panel . If they are not already on your Windows distribution CD-ROM you will have to download them from the Microsoft web site (<i>www.microsoft.com</i>).</Text>
+<Text id="227">The setup procedure for Greenstone is identical for both PWS and IIS. Invoke the Personal Web Manager and perform the following actions.</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="228">Select <i>Advanced</i> to get the <i>Advanced Options</i> screen.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="229">Select <i>Home</i> and click <i>Add</i>Fill out the fields as follows:</Text>
+<Text id="230"><i>Directory</i> field:          <i>C:\Program Files\gsdl</i></Text>
+<Text id="231"><i>Alias</i>field:               <i>gsdl</i></Text>
+<Text id="232">Access permissions:              <i>Read</i></Text>
+<Text id="233">Application permissions:         <i>None</i></Text>
+<Text id="234">Click <i>OK</i></Text>
+<Text id="235">This makes Greenstone files accessible to the webserver.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="236">Back in <i>Advanced Options</i>, select <i>gsdl</i> and click <i>Add</i>Fill out the fields as follows:</Text>
+<Text id="237"><i>Directory</i> field:           <i>C:\Program Files\gsdl\cgi-bin</i></Text>
+<Text id="238"><i>Alias</i> field:               <i>cgi-bin</i></Text>
+<Text id="239">Access permissions:               <i>None</i></Text>
+<Text id="240">Application permissions:          <i>Execute</i></Text>
+<Text id="241">Click <i>OK</i></Text>
+<Text id="242">This allows the Greenstone program <i>library.exe</i> to be executed by the webserver.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="243">Go to the URL <i>http://localhost/gsdl/cgi-bin/library.exe</i></Text>
+<Text id="244">Note: you need to specify the <i>.exe</i> file extension with PWS and IIS.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="configuring_your_site">
+<Title>
+<Text id="245">Configuring your Site</Text>
+</Title>
+<Content>
+<Text id="246">For Greenstone to work properly, access permissions for certain files must be set up appropriately. Also, there is a configuration file associated with each Greenstone site. The install procedure creates a generic configuration file based on your installation choices; however its contents can be tailored to cope with different situations. This section explains both of these issues.</Text>
+<Section id="file_permissions">
+<Title>
+<Text id="247">File permissions</Text>
+</Title>
+<Content>
+<Text id="248">This section is irrelevant for Windows 95/98, because these systems don't identify the owners of files.</Text>
+<Text id="249">On Windows NT, 2000 and Unix systems, cgi scripts don't run as normal users, because users can't be identified over the Web. Instead, they run as the user who started up the webserver program (on Windows systems), or as a special user (commonly called <i>nobody</i> on Unix systems). Because of this, all files and directories within <i>C:\Program Files\gsdl</i> need to be globally readable (or at least readable by the cgi-script user, perhaps â<i>nobody</i>â). To test whether file permissions are set up correctly, run the program <i>library.exe</i> from the command line. If the files are in the right places but the permissions are set incorrectly, it will run from the command lineâthat is, when <i>you</i> execute itâbut not from a browserâthat is, when the â<i>nobody</i>â user executes it. Another test is to log in as another user to see if the file permissions are specific to your original user account.</Text>
+<Text id="250">To work through a Web browser, all the Greenstone directories must be globally readable. Also, the <i>C:\Program Files\gsdl\etc</i> directory and all its contents must be globally <i>writable</i>. This is the directory into which the library program writes the usage log, error and initialization logs, and various user databases. If you're reluctant to make this directory globally writable, you can set permissions so that just the files <i>errout.txt</i>, <i>initout.txt</i>, <i>key.db</i>, <i>users.db</i>, <i>history.db</i> and <i>usage.txt</i> are writable by the cgi user.</Text>
+<Text id="251">If file permissions are not set up correctly for <i>C:\Program Files\gsdl\etc</i>, you may find that user authentication and search history do not work, and that no usage log (<i>usage.txt</i>) is generated.</Text>
+</Content>
+</Section>
+<Section id="gsdlsite_configuration_file">
+<Title>
+<Text id="252">The gsdlsite.cfg configuration file</Text>
+</Title>
+<Content>
+<Text id="253">The install procedure creates a generic Greenstone site configuration file based on your installation choices. For our installation this file is <i>C:\Program Files\gsdl\cgi-bin\gsdlsite.cfg</i> and its content is:</Text>
+<CodeLine># Site configuration file for Greenstone.</CodeLine>
+<CodeLine># Lines begining with</CodeLine>
+<CodeLine># are comments.</CodeLine>
+<CodeLine># This file should be placed in the same directory as your library</CodeLine>
+<CodeLine># executable file. it should be edited to suit your site.</CodeLine>
+<CodeLine># points to the GSDLHOME directory</CodeLine>
+<CodeLine>gsdlhome âC:/Program Files/gsdl â</CodeLine>
+<CodeLine># this is the http address of GSDLHOME</CodeLine>
+<CodeLine># if your webservers DocumentRoot is set to $GSDLHOME</CodeLine>
+<CodeLine># then httpprefix can be commented out</CodeLine>
+<CodeLine>httpprefix /gsdl</CodeLine>
+<CodeLine># this is the http address of the directory which</CodeLine>
+<CodeLine># contains the images for the interface.</CodeLine>
+<CodeLine>httpimg /gsdl/images</CodeLine>
+<CodeLine># should contain the http address of this cgi script. This</CodeLine>
+<CodeLine># is not needed if the http server sets the environment variable</CodeLine>
+<CodeLine># SCRIPT_NAME</CodeLine>
+<CodeLine>#gwcgi         /cgi-bin/library</CodeLine>
+<CodeLine># maxrequests is the most requests a fastcgi process</CodeLine>
+<CodeLine># will serve before it exits. This can be set to a</CodeLine>
+<CodeLine># low figure (like 1) while debugging and then set</CodeLine>
+<CodeLine># to a high figure (like 10000) when everything is</CodeLine>
+<CodeLine># working well.</CodeLine>
+<CodeLine>#maxrequests 10000</CodeLine>
+<Text id="254">You can customise your installation by editing this file, although you will probably not need to do so.</Text>
+<Text id="255">The <i>gsdlhome</i> line simply points to the <i>C:\Program Files\gsdl</i> directory.</Text>
+<Text id="256"><i>httpprefix</i> is the web address of the directory that Greenstone is installed in. We explained earlier how to create an alias so that URLs of the form <i>http://localhost/gsdl/</i>... are sought in the <i>C:\Program Files\gsdl</i> directory. Putting a line <i>httpprefix /gsdl</i> into the <i>gsdlsite</i> configuration file establishes the same convention for the Greenstone software.</Text>
+<Text id="257"><i>httpimg</i> is the web address of the <i>C:\Program Files\gsdl\images</i> directory, which contains all the gif images used in the interface. In any standard Greenstone installation this will always be <i>httpprefix/images</i>, and the line in the file above is left untouched.</Text>
+<Text id="258"><i>gwcgi</i> is the web address of the library cgi program. This is not required by most webservers (including Apache), and should remain commented out. Don't uncomment it unless you're sure you need to, because that may introduce problems.</Text>
+<Text id="259"><i>maxrequests</i> is only used by versions of Greenstone that are compiled with the âfast-cgiâ option on. The standard binary distribution does not include this option because not all webservers are configured to support it. Fastcgi speeds up cgi executions by keeping the main executable in memory between invocations of the software, rather than loading it in from disk each time a web page is requested from the Greenstone software. The trade-off is the amount of memory used, which can grow the longer the program remains in memory. Once <i>maxrequests</i> pages have been generated, the cgi program quits, thereby freeing any accumulated memory. To respond to the next request for a Web page, the cgi program is read in from disk again, and a new cycle of page requests is begun. Most installations use the standard cgi protocol, which means that <i>maxrequests</i> can be safely ignored.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="personalizing">
+<Title>
+<Text id="260">Personalizing your Installation</Text>
+</Title>
+<Content>
+<Text id="261">Probably the first thing you will want to do once your Greenstone installation is up and running is personalize the home page. The file that generates the Greenstone home page is called <i>home.dm</i>, and is located in the <i>macros</i> subdirectory of the directory into which you installed Greenstone. (The default for Windows systems is <i>C:\Program Files\gsdl</i>.) This is a plain text file that you will have to edit to create a new home page. Instead of editing it, we recommend creating a new file, say <i>yourhome.dm</i>. This will be like <i>home.dm</i> but will define âpackage homeââwhich is the bit that does the actual workâin a different way.</Text>
+<Text id="262">When you make a different home page, there must be some way of linking in to the digital library pages so that you can search and browse the collections on your system. The solution that Greenstone adopts is to use âmacrosâ. That's why the home-page file is called â.dmâ and not â.htmlââit's a âmacroâ file rather than a regular html file. But don't quail: the macro file basically contains just html, sprinkled with a few mystical incantantations which are explained below. The macro language is a powerful facility, and only a small part of it is described belowâsee the <i>Greenstone Digital Library Developer's Guide</i> for more information.</Text>
+<Section id="example">
+<Title>
+<Text id="263">Example</Text>
+</Title>
+<Content>
+<Figure id="your_own_greenstone_home_page">
+<Title>
+<Text id="264">Your own Greenstone home page</Text>
+</Title>
+<File width="395" height="227" url="images/Install_Fig_3.png"/>
+</Figure>
+<Text id="265">Figure <CrossRef target="Figure" ref="your_own_greenstone_home_page"/> shows an example of a new digital library home page. Each of the âClick hereâ links takes you to the appropriate Greenstone facility. This page was generated by the file called <i>yourhome.dm</i> shown in Figure <CrossRef target="Figure" ref="yourhome_dm"/>.</Text>
+<Figure id="yourhome_dm">
+<Title>
+<Text id="266"><i>yourhome.dm</i> used to create Figure <CrossRef target="Figure" ref="your_own_greenstone_home_page"/></Text>
+</Title>
+<CodeLine>package home</CodeLine>
+<CodeLine>_content_ {</CodeLine>
+<CodeLine>&lt;h2&gt;Your own Greenstone home page&lt;/h2&gt;</CodeLine>
+<CodeLine>&lt;ul&gt;</CodeLine>
+<CodeLine>&lt;table&gt;</CodeLine>
+<CodeLine>&lt;tr valign=top&gt;&lt;td&gt;Search page for the demo collection&lt;br&gt;&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httpquery_&amp;c=demo"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;"About" page for the demo collection&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppageabout_&amp;c=demo"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;Preferences page for the demo collection&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppagepref_&amp;c=demo"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;Home page&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppagehome_"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;Help page&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppagehelp_"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;Administration page&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppagestatus_"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;The Collector&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppagecollector_"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;/table&gt;</CodeLine>
+<CodeLine>&lt;/ul&gt;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine># if you hate the squirly green bar down the left-hand side of the</CodeLine>
+<CodeLine># page, uncomment these lines:</CodeLine>
+<CodeLine># _header_ {</CodeLine>
+<CodeLine># }</CodeLine>
+</Figure>
+<Text id="267">You can use Figure <CrossRef target="Figure" ref="yourhome_dm"/> as a template for creating your own specialized Greenstone home page. Basically, it defines a macro called <i>content</i>. Inside the curly braces is ordinary html. You could insert additional text, along with any html formatting commands, to put the content that you want to see on the page. The text is regular html; if you want you can include hyperlinks and use all the other facilities that html provides.</Text>
+<Text id="268">To make your new home page link in with other digital library pages, you need to use an appropriate magic spell. In this macro language, magic spells are words flanked by underscores. You can see these in Figure <CrossRef target="Figure" ref="yourhome_dm"/>. For example, <i>_httppagehome_</i> takes you to the home page, <i>_httppagehelp_</i> to the help page, and so on. In some cases you need to include a collection name. For example, <i>_httpquery_&amp;c=demo</i> specifies the search page for the demo collection; for other collections you should replace <i>demo</i> by the appropriate collection name.</Text>
+<Text id="269">The definition of the macro called <i>_content_</i> is plain html. Any standard html code may be placed within a macro definition. However, the special characters '{', '}', '\', and '_' must be escaped with a backslash to prevent them from being processed by the macro language interpreter.</Text>
+<Text id="270">Note that the <i>_content_</i> macro definition does not contain any html header or footer. If you want to change the header or footer of your home page, you should define <i>_header_</i> and/or <i>_footer_</i> macros, adding them to the <i>yourhome.dm</i> file in the form</Text>
+<CodeLine>_macroname_ {</CodeLine>
+<CodeLine>...</CodeLine>
+<CodeLine>}</CodeLine>
+<Text id="271">For example, the squirly green bar down the left-hand side of Greenstone pages is defined in the <i>_header_</i> macro, and making this macro null will remove it, as indicated at the end of Figure <CrossRef target="Figure" ref="yourhome_dm"/>.</Text>
+</Content>
+</Section>
+<Section id="how_to_make_it_work">
+<Title>
+<Text id="272">How to make it work</Text>
+</Title>
+<Content>
+<Text id="273">You have to tell Greenstone about the new home page <i>yourhome.dm</i>. The system reads in the macro files that are specified in the main configuration file <i>main.cfg</i>, so if you create a new one you must include it there. Name clashes are handled sensibly: the most recent definition takes precedence.</Text>
+<Text id="274">Thus to make the Greenstone digital library software use the home page in Figure <CrossRef target="Figure" ref="your_own_greenstone_home_page"/> instead of the default, first put the <i>yourhome.dm</i> file in Figure <CrossRef target="Figure" ref="yourhome_dm"/> into the <i>macros</i> directory. Then edit the <i>main.cfg</i> configuration file to replace <i>home.dm</i> with <i>yourhome.dm</i> in the list of macro files that are loaded at startup.</Text>
+</Content>
+</Section>
+<Section id="redirecting_a_url_to_greenstone">
+<Title>
+<Text id="275">Redirecting a URL to Greenstone</Text>
+</Title>
+<Content>
+<Text id="276">You may want to redirect a more convenient URL to your Greenstone cgi program. For example, on our system the URL <i>http://nzdl.org</i> (which is shorthand for <i>http://nzdl.org/index.html)</i> is redirected to <i>http://nzdl.org/cgi-bin/library</i>. The Apache webserver accomplishes this with the <i>Redirect</i> directive. Along with other directives, this goes into the <i>C:\Program Files\Apache Group\Apache\conf\httpd.conf</i> configuration file. To redirect the URL <i>http://www.yourserver.com</i> to <i>http://www.yourserver.com/cgi-bin/library</i>, put this line into <i>httpd.conf</i>:</Text>
+<CodeLine>Redirect /index.html http://www.yourserver.com/cgi-bin/library</CodeLine>
+<Text id="277">Then you will reach your digital library system directly from the URL <i>http://www.yourserver.com</i>. Instead, if you wanted a URL like <i>http://www.yourserver.com/greenstone</i> to be redirected to <i>http://www.yourserver.com/cgi-bin/library</i>, include in the <i>httpd.conf</i> file</Text>
+<CodeLine>Redirect /greenstone http://www.yourserver.com/cgi-bin/library</CodeLine>
+<Text id="278">If your computer doesn't have a domain name (like the âwww.yourserver.comâ above), just replace <i>www.yourserver.com</i> by <i>localhost</i> in the lines above. So long as the browser is running on the same machine as the webserverâwhich it surely is if your computer doesn't have a domain nameâthis has the same effect as the above redirections.</Text>
+<Text id="279">Instead of putting redirect directives into the file <i>httpd.conf</i>, you can equally well put them into a file called <i>.htaccess</i> within your server's document root directory. In fact, doing so has two advantages. First, changes to <i>.htaccess</i> take effect immediately, whereas you have to restart the Apache webserver to see the effect of changes to <i>httpd.conf</i>. Second, on Unix systems you usually have to be logged in as the ârootâ user to edit <i>httpd.conf</i>, whereas you don't to edit <i>.htaccess</i>.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_associated_software">
+<Title>
+<Text id="280">Appendix Associated Software</Text>
+</Title>
+<Content>
+<Text id="281">Here is how to obtain the software packages mentioned above.</Text>
+<Section id="apache_webserver">
+<Title>
+<Text id="282">Apache Webserver</Text>
+</Title>
+<Content>
+<Text id="283">To run any version of Greenstone apart from the Windows Local Library version, you need an external webserver. Many installations, particularly larger ones, will already have a webserver. If you are using Linux, Apache may be on your installation disk but may not have been selected during the installation procedure. The Apache Webserver from <i>www.apache.org</i> is free, and easy to install.</Text>
+</Content>
+</Section>
+<Section id="perl">
+<Title>
+<Text id="284">Perl</Text>
+</Title>
+<Content>
+<Text id="285">Greenstone uses the Perl language when building collections. For Windows, Perl is already included in the Greenstone software. Most Unix systems already have Perl installed, but if not, source code and binaries for a wide range of Unix platforms are freely available at <i>www.perl.com</i>. Perl version 5.0 or higher is needed.</Text>
+</Content>
+</Section>
+<Section id="gcc">
+<Title>
+<Text id="286">GCC</Text>
+</Title>
+<Content>
+<Text id="287">The Unix version of Greenstone compiles under the Gnu C++ compiler, GCC. Greenstone makes extensive use of the C++ standard template library (we've found it to be broken on some older versions of GCC; please tell us if you have STL problems). Note that this version of Greenstone does not compile under GCC 3.0.</Text>
+</Content>
+</Section>
+<Section id="gdbm">
+<Title>
+<Text id="288">GDBM</Text>
+</Title>
+<Content>
+<Text id="289">All versions of Greenstone use the Gnu Database Manager, GDBM. It is supplied with all Windows versions of Greenstone and installed automatically during the installation procedure. Linux systems already have GDBM, so we do not provide it for Linux. Most other Unix systems have it, but if necessary you can download it from <i>www.gnu.org</i>.</Text>
+</Content>
+</Section>
+<Section id="java_runtime_environment">
+<Title>
+<Text id="290">Java runtime environment</Text>
+</Title>
+<Content>
+<Text id="291">To use the Greenstone Librarian Interface, you need a suitable version of the Java Runtime Environment. If you don't already have this, a suitable version is included on the CD-ROM, or you can download the latest version from <u>http://java.sun.com/j2se/downloads.html</u>. Version 1.4.0 or higher is needed.</Text>
+</Content>
+</Section>
+<Section id="java_compiler">
+<Title>
+<Text id="292">Java compiler</Text>
+</Title>
+<Content>
+<Text id="293">To compile the source code of the Greenstone Librarian Interface, you must first install a Java Development Kit. You can download the J2SE Software Development Kit from <u>http://java.sun.com/j2se/downloads.html</u>. Version 1.4.0 or higher is needed.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/en/Paper_en.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/en/Paper_en.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/en/Paper_en.xml	(revision 13632)
@@ -0,0 +1,851 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">GREENSTONE DIGITAL LIBRARY</Text>
+</Heading>
+<Title>
+<Text id="2">FROM PAPER TO COLLECTION</Text>
+</Title>
+<Author>
+<Text id="3">Dr Michel Loots, Dan Camarzan and Ian H. Witten</Text>
+</Author>
+<Affiliation>
+<Text id="4">Human Info NGO, Belgium <br/>Simple Words, Romania <br/>University of Waikato, New Zealand</Text>
+</Affiliation>
+<Text id="5">Greenstone is a suite of software for building and distributing digital library collections. It provides a new way of organizing information and publishing it on the Internet or on CD-ROM. Greenstone is produced by the New Zealand Digital Library Project at the University of Waikato, and developed and distributed in cooperation with UNESCO and the Human Info NGO. It is open-source software, available from <i>http://greenstone.org</i> under the terms of the G nu General Public License.</Text>
+<Comment>
+<Text id="6">We want to ensure that this software works well for you. Please report any problems to <i>greenstone@cs.waikato.ac.nz</i></Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">March 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">About this manual</Text>
+</Title>
+<Content>
+<Text id="10">This document explains how to create CD-ROM collections from paper documents. It describes in full detail the procedures and economics involved in the scanning and optical character recognition (OCR) processes, so that you end up with text in the right format to apply the Greenstone software. It also describes how to create and edit the material associated with a collection.</Text>
+<Text id="11">We have tried to be as plain as possible in our explanation. Reference to any trade mark or company product is purely for illustrative purposes, and does not imply that we endorse or favor this product over any other.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="12">Companion documents</Text>
+</Title>
+<Content>
+<Text id="13">The complete set of Greenstone documents include five volumes:</Text>
+<BulletList>
+<Bullet>
+<Text id="14">Greenstone Digital Library Installer's Guide</Text>
+</Bullet>
+<Bullet>
+<Text id="15">Greenstone Digital Library User's Guide</Text>
+</Bullet>
+<Bullet>
+<Text id="16">Greenstone Digital Library Developer's Guide</Text>
+</Bullet>
+<Bullet>
+<Text id="17">Greenstone Digital Library: From Paper to Collection <i>(this document)</i></Text>
+</Bullet>
+<Bullet>
+<Text id="18">Greenstone Digital Library: Using the Organizer</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">Acknowledgements</Text>
+</Title>
+<Content>
+<Text id="20">The scanning operation and other know-how relating to the creation of collaborative non-profit collections have been developed by Dr Michel Loots, MD, of Human Info NGO and HumanityCD, Dan Camarzan of Simple Words, and their team of collaborators in Brasov, Romania.</Text>
+<Text id="21">The Greenstone software is a collaborative effort between many people. Rodger McNab and Stefan Boddie are the principal architects and implementors. Contributions have been made by David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, and Stuart Yeates. Other members of the New Zealand Digital Library project provided advice and inspiration in the design of the system: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols and Lloyd Smith. We would also like to acknowledge all those who have contributed to the GNU-licensed packages included in this distribution: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE and XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="introduction">
+<Title>
+<Text id="22">Introduction</Text>
+</Title>
+<Content>
+<Text id="23">One goal of the Greenstone Digital Library software is to empower organizations such as universities, United Nations agencies, non-governmental organizations, non-profit organizations and governments to create varied collections of information that can be delivered online or on CD-ROM.</Text>
+<Text id="24">Typical steps that have to be implemented are:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="25">Selecting the documents to be included</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="26">Securing copyrights permissions to use these documents in the digital library</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="27">Scanning and OCR of the hard-copy documents which are not available in to digital form to have a perfect digital format</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="28">Converting all documents to a format (integrating text and images) which can be imported into Greenstone (preferably
+HTML or Microsoft Word, but others are also covered at varying levels of precision by a âpluginâ (see the Greenstone Userâs Manual)</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="29">Tagging the chapters, paragraphs and images of the digital documents</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="30">Organising the collection into a optimally structured digital library</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="31">Building the digital library using the Greenstone software</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="32">Printing and distributing the collection on CD-ROM and/or distributing it over the Internet</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="33">In order to create a digital collection, the publications must be available in digital format. If books, newsletters or other documents are only available on paper, they will need to be scanned and processed into machine-readable form (step iii). Usually this is done using optical character recognition (OCR), but sometimes by manual retyping. This process is covered in Chapters 2-4 of this manual.</Text>
+<Text id="34">Step v. enables the different parts of a document to be independently selected and displayed by readers in the final library, while step vi. involves assigning attributes to the documents such as subject categories, keywords and bibliographic data for ordering and searching the library. These steps are covered in Chapter 5 of this manual.</Text>
+<Text id="35">This manual introduces many issues that affect the editorial process of creating a collection from paper. Before reading on, you should consider these questions:</Text>
+<BulletList>
+<Bullet>
+<Text id="36">What is the goal of your collection?</Text>
+</Bullet>
+<Bullet>
+<Text id="37">What is your target group?</Text>
+</Bullet>
+<Bullet>
+<Text id="38">How big is itâlocal, regional, or global?</Text>
+</Bullet>
+<Bullet>
+<Text id="39">How many documents are you making available?</Text>
+</Bullet>
+<Bullet>
+<Text id="40">How many pages?</Text>
+</Bullet>
+<Bullet>
+<Text id="41">How much graphics content?</Text>
+</Bullet>
+<Bullet>
+<Text id="42">Does the material split into parts that will be consulted by a limited audience and parts that need to be disseminated widely?</Text>
+</Bullet>
+<Bullet>
+<Text id="43">Are the documents already available electronically?</Text>
+</Bullet>
+<Bullet>
+<Text id="44">If so, in which formats? (Note incidentally that PDF files are not automatically equivalent to digital full-text form, as they often contain only page images.)</Text>
+</Bullet>
+<Bullet>
+<Text id="45">What is the copyright status of the documents?</Text>
+</Bullet>
+<Bullet>
+<Text id="46">Who owns the copyright?</Text>
+</Bullet>
+<Bullet>
+<Text id="47">Are there other organizations with the same target audience?</Text>
+</Bullet>
+<Bullet>
+<Text id="48">Are you willing to collaborate with other groups?</Text>
+</Bullet>
+<Bullet>
+<Text id="49">What budget is available for the whole project?</Text>
+</Bullet>
+<Bullet>
+<Text id="50">What human resources are available (in person-months) for co-ordination, editing, scanning and programming?</Text>
+</Bullet>
+<Bullet>
+<Text id="51">How many computers are available for this project?</Text>
+</Bullet>
+<Bullet>
+<Text id="52">How many CD-ROMs do you want to distribute?</Text>
+</Bullet>
+<Bullet>
+<Text id="53">Will they be free, or for sale?</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Chapter>
+<Chapter id="scanners_and_scanning">
+<Title>
+<Text id="54">Scanners and scanning</Text>
+</Title>
+<Content>
+<Text id="55">The first step in converting paper documents into a digital library collection is to obtain images of all pages of all publications in digital format. The next stage is optical character recognition (OCR), and clean, high-quality images are essential for successful OCR. The digitization process requires a scanner capable of working at a resolution of 300 dpi (dots per inch). Most scanning can be done in black-and-white, but if color illustrations are included they must be scanned with a color scanner. In most cases the covers of the book contain colors and will have to be scanned as a color photographic image.</Text>
+<Section id="scanners">
+<Title>
+<Text id="56">Scanners</Text>
+</Title>
+<Content>
+<Text id="57">Scanners are available in all price ranges, and all shapes and sizes. They range from $100 for flat-bed scanners to upwards of $50,000 for large industrial scanners from manufacturers such as Bell &amp; Howell.<FootnoteRef id="1"/>There are many websites that offer a wide range of scanners for sale. To locate them, just search for âscannersâ in search engines like Google, Altavista, or Yahoo.</Text>
+<Text id="58">The output format of a scanned page is a computer file that is usually stored in TIFF or Bitmap format. Compressed TIFF IV is the best format to use. An average page scanned and converted to this format occupies only 50 Kb, compared to perhaps 2 Mb for the equivalent page in uncompressed Bitmap form.</Text>
+<Subsection id="low-cost_flat-bed_scanner">
+<Title>
+<Text id="59">Low-cost flat-bed scanner</Text>
+</Title>
+<Content>
+<Text id="60">Low-cost flat-bed units are the cheapest and most widely available type of scanner. There are many brands: HP, Agfa, Acer, etc. Prices range from $100 to $300. Both black-and-white and color images can be scanned. The low price allows each computer to have its own scanner.</Text>
+<Text id="61">Disadvantages of these scanners include the medium quality of the result, the slow rate of scanning, unreliability in warm environments, and relatively frequent breakdown. Pages must be scanned manually, one by one. Each page must be positioned carefully on the scanning plate to ensure that it is aligned correctly. Productivity of these scanners is low. Despite manufacturers' claims that each page can be scanned in less than a minute, the fact is that rates exceeding twelve pages per hour are rarely achieved. The scanning process monopolizes the computer on which the work is being performed.</Text>
+<Text id="62">Consequently these scanners are useful only for small jobs with limited numbers of pagesâno more than 200 to 400 pages a month on a regular basis, or one-time jobs of up to 1000 or 2000 pages.</Text>
+</Content>
+</Subsection>
+<Subsection id="low-end_scanner_with_sheet_feeder">
+<Title>
+<Text id="63">Low-end scanner with sheet feeder</Text>
+</Title>
+<Content>
+<Text id="64">Low-end scanners with sheet feeders typically cost between $500 and $1200. Ten to fifty pages can be inserted, scanned and processed at once: thus the operator does not have to attend constantly to the machine. This increases capacity up to 150 to 200 pages per day. These scanners are more robust, and have a larger lifespan before repairâusually in the range 30,000 to 50,000 pages.</Text>
+<Text id="65">A disadvantage is that only one side of the page is scanned at a timeâthe stack of pages must be reversed and rescanned in order to obtain an image of both sides. This often creates problems because sheet feeders are never without problems and sometimes pages get blocked.</Text>
+<Text id="66">These scanners are useful for up to 1500 to 3000 pages a month.</Text>
+</Content>
+</Subsection>
+<Subsection id="color_scanners">
+<Title>
+<Text id="67">Color scanners</Text>
+</Title>
+<Content>
+<Text id="68">Any scanning operation invariably involves some color images, so a color scanner will always be required. Generally speaking, less than 5% of any publication contains color images, plus the cover. Thus a low cost flat-bed scanner as described above suffices. It is advisable to select one capable of scanning up to 600 dpi resolution.</Text>
+</Content>
+</Subsection>
+<Subsection id="professional_duplex_scanners">
+<Title>
+<Text id="69">Professional duplex scanners</Text>
+</Title>
+<Content>
+<Text id="70">Professional scanners are reliable, heavy-duty machines capable of processing a large volume of pagesâtypically from 2000 pages to 10,000 pages per day. They have an automatic sheet-feeder tray system that processes batches of about 50 to 200 pages. The best and fastest are duplex machines that scan both sides of the page at once.</Text>
+<Text id="71">Professional duplex scanners require a powerful computer with a hard disk of at least 10 to 20 Gb. Prices range from $5000 to $50,000. For example, the Canon DR-6020 duplex scanner costs $5000 and works with double-sided documents. It has a capacity of about 2000 pages per day and a lifespan of 600,000 to 800,000 pages. Bell &amp; Howell and Fujitsu scanners range from $10,000 to $50,000 and have a lifespan of many millions of pages.</Text>
+<Text id="72">Micro-fiche scanners cost from $15,000 for a semi-manual unit to $80,000 for one that operates fully automatically.</Text>
+</Content>
+</Subsection>
+<Subsection id="scanning_programs">
+<Title>
+<Text id="73">Scanning programs</Text>
+</Title>
+<Content>
+<Text id="74">Every scanner comes with its own software, which means that the program must be installed on the computer that manages the scanner. Some have a computer card that needs to be installed in your computer to speed up the scanning operation.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="preparing_the_documents">
+<Title>
+<Text id="75">Preparing the documents</Text>
+</Title>
+<Content>
+<Text id="76">Before being scanned, documents must be properly prepared. Dusty documents must be cleaned, humid documents dried, clips removed, pages unfolded.</Text>
+<Text id="77">The spine of each book should be removed by cutting it off, straight and precisely. Books provided by libraries must often be rebound, and if so you should be particularly careful when removing spines in order to facilitate smooth rebinding.</Text>
+<Text id="78">If there are just a few documents, cutting can be done manually with a ruler and cutters. Be careful with your hands! For more documents, special manual cutting machines are available.</Text>
+<Text id="79">For high volumesâmore than 20 documentsâwe recommend asking a printer or copy-shop if you can use their professional cutting machine. Do not forget to remove metal clips which could damage the cutting blades.</Text>
+</Content>
+</Section>
+<Section id="the_scanning_process">
+<Title>
+<Text id="80">The scanning process</Text>
+</Title>
+<Content>
+<Text id="81">Using software provided with the scanner, a digital image of each paper page is scanned and transformed into a Bitmap or TIFF image. These images should be stored on hard disk with standard filenames. The OCR process starts once some or all of a batch of documents have been scanned. It can be undertaken by the person who operates the scanner, or by someone else.</Text>
+<Text id="82">Typically a scanning resolution of 300 dpi is needed, although sometimes 200 dpi is acceptable.</Text>
+<Subsection id="quality_control">
+<Title>
+<Text id="83">Quality control</Text>
+</Title>
+<Content>
+<Text id="84">The final goal of scanning is either to OCR the pages to obtain perfect word processor or HTML versions of the publications, or to produce enhanced image files such as PDF image files. In either case the quality of the image is very important. If quality is sub-standard, image files will not look good and will consume more memory. Image quality seriously affects the OCR process: with sub-standard quality, productivity deteriorates by up to 40%. OCR typically represents more than 90% of the total cost, so scanning quality can have a very substantial effect on the final cost.</Text>
+<Text id="85">The quality of the TIFF file can be enhanced by adjusting the scanning process to each type of paper, using settings provided by the scanner software. Relatively transparent kind of paper will require a lighter setting; the contrast must be adjusted depending on the quality of printing, and so on.</Text>
+<Text id="86">First divide the material into batches with similar paper and print qualities. Perform OCR tests on a sample from the first batch to determine the optimal settings. Then scan all material in this batch before proceeding to the next one.</Text>
+</Content>
+</Subsection>
+<Subsection id="filename_conventions">
+<Title>
+<Text id="87">Filename conventions</Text>
+</Title>
+<Content>
+<Text id="88">Give each book or document a job number or unique code, which will become the name of the folder that contains all TIFF images in the document. Depending on the computer system (DOS, Windows, UNIX, LINUX, etc) from 8 characters to 128 characters can be used in a filename. We recommend restricting this unique document identifier to 8 to 16 characters. The first five characters might identify the document, the following letter might contain a language code, and the remaining characters might identify the particular page. For example, the identifier <i>u7548e12.tif</i> might identify the TIFF image of page 12 of a book written in English with code <i>u7548e</i>.</Text>
+<Text id="89">Allocate one directory on the hard disk for scanning jobs, say <i>scanjobs</i>. Then make a subdirectory for each job. Within this make a subdirectory for each publicationâsay <i>u7548e</i> for the above document. Store all the TIFF images of the publication, including color images, in this folder.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="productivity_and_resources">
+<Title>
+<Text id="90">Productivity and resources</Text>
+</Title>
+<Content>
+<Text id="91">You should not underestimate the magnitude of the scanning operationâand particularly the OCR process that follows. It is best to consider scanning and OCR as completely separate activities. The optimal choice from an economic and practical point of view should be madeindividually for each one.</Text>
+<Text id="92">Some points to consider are the investment in scanners and computers that is necessary; the availability of appropriate space and human resources; training the workforce; salary costs; the initial and total number of pages to be scanned; deadlines; and whether documents can be outsourced to third parties.</Text>
+<Subsection id="scanning_costs">
+<Title>
+<Text id="93">Scanning costs</Text>
+</Title>
+<Content>
+<Text id="94">An important decision is whether to invest in scanning equipment and perform all scanning oneself, or outsource it to a scanning company. The main considerations are:</Text>
+<BulletList>
+<Bullet>
+<Text id="95">pressure of time for the scanning job;</Text>
+</Bullet>
+<Bullet>
+<Text id="96">total number of pages;</Text>
+</Bullet>
+<Bullet>
+<Text id="97">salary costs of those who perform the scanning.</Text>
+</Bullet>
+</BulletList>
+<Text id="98">The people who perform the scanning must be highly motivated, technically skilled, and quality-oriented.</Text>
+<Text id="99">The typical cost of scanning by a professional company is $0.06 per page. To this must be added the cost of shipment, which can be up to $0.03 per page for transport from developing countries to developed countries, and $0.015 per page for transport within countries.</Text>
+<Text id="100">Table <CrossRef target="Table" ref="table_scanning_cost"/> estimates the cost of doing it yourself, using various scanner types. Note that all figures are approximate. They are provided as rough guidelines based on the authors' experience. The first three columns concern labor costs. The first is the capacity in pages/month, assuming full-time work. The resources required in person-hours per page is obtained by dividing the number of working hours per month by the pages/month capacity in the second column. It is shown in the second column, which assumes 180 working hours per month.</Text>
+<Table id="table_scanning_cost">
+<Title>
+<Text id="101">Scanning cost</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="90"/>
+<th width="71">
+<Text id="102">Capacity (pages/month)</Text>
+</th>
+<th width="75">
+<Text id="103">Hours/page (180-hour month)</Text>
+</th>
+<th width="83">
+<Text id="104">Cost/page (assuming $4/hour)</Text>
+</th>
+<th width="60">
+<Text id="105">Scanner acquisit- ion</Text>
+</th>
+<th width="66">
+<Text id="106">Scanner lifespan (pages)</Text>
+</th>
+<th width="85">
+<Text id="107">Outsourced pages for scanner cost<br/>(at $.06 each)</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="108">Flat bed scanner</Text>
+</th>
+<th width="71">
+<Text id="109">2,500</Text>
+</th>
+<th width="75">
+<Text id="110">0.072</Text>
+</th>
+<th width="83">
+<Text id="111">$0.288</Text>
+</th>
+<th width="60">
+<Text id="112">$300</Text>
+</th>
+<th width="66">
+<Text id="113">7,000</Text>
+</th>
+<th width="85">
+<Text id="114">5,000</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="115">Scanner with sheet-feeder</Text>
+</th>
+<th width="71">
+<Text id="116">8,000</Text>
+</th>
+<th width="75">
+<Text id="117">0.0225</Text>
+</th>
+<th width="83">
+<Text id="118">$0.09</Text>
+</th>
+<th width="60">
+<Text id="119">$800</Text>
+</th>
+<th width="66">
+<Text id="120">30,000</Text>
+</th>
+<th width="85">
+<Text id="121">13,000</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="122">Professional: low-end duplex</Text>
+</th>
+<th width="71">
+<Text id="123">40,000</Text>
+</th>
+<th width="75">
+<Text id="124">0.0045</Text>
+</th>
+<th width="83">
+<Text id="125">$0.018</Text>
+</th>
+<th width="60">
+<Text id="126">$6,000</Text>
+</th>
+<th width="66">
+<Text id="127">600,000</Text>
+</th>
+<th width="85">
+<Text id="128">100,000</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="129">Professional: high-end duplex</Text>
+</th>
+<th width="71">
+<Text id="130">150,000</Text>
+</th>
+<th width="75">
+<Text id="131">0.0012</Text>
+</th>
+<th width="83">
+<Text id="132">$0.0048</Text>
+</th>
+<th width="60">
+<Text id="133">$50,000</Text>
+</th>
+<th width="66">
+<Text id="134">8,000,000</Text>
+</th>
+<th width="85">
+<Text id="135">833,000</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="136">To determine the price per page, multiply the total hourly salary costs in your situation by the second column of Table <CrossRef target="Table" ref="table_scanning_cost"/>.As an example, the third column gives the price of in-house scanning at a salaryrate of $4/hourânot including investment costs.</Text>
+<Text id="137">These calculations assume that the scanner is used for a sufficient volume to justify the investment. The final three columns of Table <CrossRef target="Table" ref="table_scanning_cost"/> give more information about the cost of the scanner itself. The first of these shows the acquisition cost of the scanner, and the next gives its expected lifetime. The last shows the number of pages that could be scannedcommercially, at a cost of $0.06/page, for the price of the scanner alone.</Text>
+<Text id="138">Of course, many other factors affect the choice of scanner: availability of funds, need to minimize dependence on others, desire to build local capacity, obligations to libraries to scan books locally and not transport them, and so on.</Text>
+<Text id="139">The above figures give some idea of the volume of pages needed to justify different levels of investment. Rarely will an institute or organization need to scan 800,000 pages. At such levels more complex issues ariseâsuch as maintenance and the possibility of recouping costs by offering scanning services to othersâthat we will not discuss here.</Text>
+<Text id="140">It is tempting to regard the development of scanning capacity asa commercial venture, particularly in developing countries. But one shouldalways bear in mind that scanning is not a repetitive business. Oncedocuments have been scanned, clients never place new orders for the same documentsâno matter how good the relationship with the scanning company. From a commercial point of view, intensive marketing efforts are needed. We do not advise NGOs or other non-profit organizations to venture into this realm without thorough initial trials and a carefully-considered business plan.</Text>
+<Text id="141">In conclusion, if 10,000 to 50,000 pages are to be scanned, one should consider outsourcing the job. A low-end professional scanner costing about $6000 can only be justified if more than 100,000 pages have to be scanned. You might consider banding together with a few other institutionsâperhaps NGOs or librariesâto purchase such a scanner.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="ocr">
+<Title>
+<Text id="142">OCR: Optical Character Recognition</Text>
+</Title>
+<Content>
+<Text id="143">An optical character recognition or OCR system transforms a scanned image into text. The input is a digitized image in TIFF or Bitmap formatâpreferably a clean, high-quality image. The output is a word-processor or web file, typically in RTF, Word, or HTML format.</Text>
+<Text id="144">The following steps are involved in converting paper documents to computer form:</Text>
+<BulletList>
+<Bullet>
+<Text id="145">scanning;</Text>
+</Bullet>
+<Bullet>
+<Text id="146">page layout analysis;</Text>
+</Bullet>
+<Bullet>
+<Text id="147">recognition;</Text>
+</Bullet>
+<Bullet>
+<Text id="148">scanning images and tables.</Text>
+</Bullet>
+</BulletList>
+<Text id="149">Following these, you must perform quality checks on the resulting files, and save them in the appropriate format.</Text>
+<Text id="150">On the market are many good OCR programs, with prices ranging from $100 to $400.<FootnoteRef id="2"/>For example, among many others are:</Text>
+<BulletList>
+<Bullet>
+<Text id="151"><i>Read-Iris</i>(http://www.readiris.com/)</Text>
+</Bullet>
+<Bullet>
+<Text id="152"><i>Omnipage</i>(http://www.omnipage.com/)</Text>
+</Bullet>
+<Bullet>
+<Text id="153"><i>Fine-Reader</i>(http://www.finereader.com/)</Text>
+</Bullet>
+</BulletList>
+<Text id="154">All information, including lists of local distributors, can be found on the manufacturers' websites. Among these, in the authors' experience the most user-friendly are Fine-Reader and Omnipage. Fine-Reader is cheapest, costing about $100. It offers a great deal of flexibility, and the widest range of different language options.</Text>
+<Text id="155">A choice must be made between undertaking the scanning and OCR in-house or outsourcing it to a commercial organization. To do it in-house requires a scanner, OCR software program, OCR skill development, and a quality-conscious, highly motivated workforce.</Text>
+<Section id="the_ocr_process">
+<Title>
+<Text id="156">The OCR process</Text>
+</Title>
+<Content>
+<Text id="157">The OCR process differs from one OCR program to another, and each one requires a considerable amount of learning. The program's manual will explain this process in detail. Four points deserve particular attention: quality control, tables, images, and specialized material such as formulas, foreign characters etc.</Text>
+<Subsection id="quality_control_1">
+<Title>
+<Text id="158">Quality control</Text>
+</Title>
+<Content>
+<Text id="159">We cannot place enough emphasis on quality control. Quality checks are best performed by native speakers, or people with an excellent command of the language to check. The best people are at the university or high-school level. We should also note that young people tend to sustain higher concentration than older people for this kind of work.</Text>
+<Text id="160">Normally there are four quality checks.</Text>
+<Text id="161">The first is performed at the same time as OCR. Every OCR program has a built-in spell-checker that highlights every suspect letter. At the same time the image of the word appears too, making it easy to check and correct the error.</Text>
+<Text id="162">The second is a general check of the text once the OCR process is finished. Common errors are to miss a page, a paragraph, chapter titles, and so on. A general overview is necessary to check if pages are missing. It is essential to check titles, chapter headings, paragraphs, and tables.</Text>
+<Text id="163">The third is a spelling check using Microsoft Word. This program has a dictionary that is often more sophisticated than the one embedded in OCR programs. By importing the book into Word and performing a spelling check there, more errors can be found and corrected. Be sure to add to the spell-checker any particularly difficult or error-prone words, or scientific and technical terms common in that type of publication.</Text>
+<Text id="164">Finally, the completed document should be checked by an independent person who samples the complete book and checks for errors, problems with tables and images, tagging, and the general look of the resulting text. Only after this final check can a book be considered ready for digital dissemination.</Text>
+</Content>
+</Subsection>
+<Subsection id="tables">
+<Title>
+<Text id="165">Tables</Text>
+</Title>
+<Content>
+<Text id="166">OCR programs do not cope well with tables. Moreover, tables are hard to check. They contain many digits, sometimes with points and commas, and entries are easily misplaced into the wrong row or column. They require concentrated effort, dedicated work, intensive proof-reading, careful checking, and good quality control. They can be handled in three basically different ways.</Text>
+<Text id="167">First, tables can be treated as images. This involves scanning them as black-and-white images and placing them in this form at the appropriate point in the document. This is the easiest solution. There are no errors, and the only time taken is that involved in creating the image. However, this solution consumes more memory than others. Also, the resolution is not always sufficient when large tables are displayed on a computer screen. If you make the complete table fit, the resolution is too small. If you make the table over-wide, the user must scroll to see all columns and rows, and cannot get an overview of the contents.</Text>
+<Text id="168">Second, tables can be recreated manually by making a table with the same number of rows and columns and filling the entries by typing them in, character by character.</Text>
+<Text id="169">Third, the table can be OCR'd. This saves time compared to the manual process, but has a potential for more errors. Columns sometimes get merged, and commas and points are not recognized.</Text>
+</Content>
+</Subsection>
+<Subsection id="images">
+<Title>
+<Text id="170">Images</Text>
+</Title>
+<Content>
+<Text id="171">Publications contain three different general types of image:</Text>
+<BulletList>
+<Bullet>
+<Text id="172">black and white line art;</Text>
+</Bullet>
+<Bullet>
+<Text id="173">black and white photographs;</Text>
+</Bullet>
+<Bullet>
+<Text id="174">color photographs.</Text>
+</Bullet>
+</BulletList>
+<Text id="175">Black and white line art should be scanned in line art mode and saved as GIF or PNG files. Black and white photographs should be scanned in greyscale mode and saved as GIF or JPEG files. Color photographs should be scanned in color mode and saved as JPEG files. Generally speaking, medium-quality JPEG provides adequate resolution.</Text>
+<Text id="176">For most collections, images consume the bulk of the space required on a hard-disk or CD-ROM. This makes it important to optimize each image for clarity and visibility, while minimizing its size. To save space you might drop some or all of the images if they are not relevant to the text.</Text>
+<Text id="177">Images should be scanned separately, one by one. We recommend giving the image files a name that consists of the first five or six characters used to denote the document followed by the number of the page on which the image was found. An alternative, assuming each document is in its own directory, is to simply use the letter <i>p</i> followed by the page containing the image. If there are several images on a single page, append an additional letter <i>a</i>, <i>b</i>, <i>c</i>âŠ to the filename. For example, if a JPEG image appeared on page 36 of the publication <i>u7548e</i> discussed earlier, it would be placed in a file named <i>u7548e36.jpg</i> or <i>p36.jpg</i>.</Text>
+<Text id="178">Once the images have been scanned, you can put batch-processing programs to work to resize or enhance all the images at once.</Text>
+</Content>
+</Subsection>
+<Subsection id="specialized_material">
+<Title>
+<Text id="179">Specialized material</Text>
+</Title>
+<Content>
+<Text id="180">Many documents contain specialized material such as special characters, formulas, and difficult pages. Special characters generally relate to different languages and diacritical marks. The language option for the OCR program should be set for the specific language being read. Formulas will have to be recreated manually. Sometimes this is not possible in the OCR program, but only in a word processor like MICROSOFT Word. Difficult pages that contain complex material or are damaged so that a clear image cannot be obtained might have to be retyped manually.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="productivity_and_resources_1">
+<Title>
+<Text id="181">Productivity and resources</Text>
+</Title>
+<Content>
+<Text id="182">As mentioned earlier, you should not underestimate the difficulty of OCR. Although the economic and practical options for OCR should be considered separately from scanning, similar points arise: the necessary investment in computers; the availability of human resources and management skills; training the workforce; salary costs; the total number of pages to be processed; and whether documents can be outsourced to third parties.</Text>
+<Text id="183">In this section we share our experience of OCR operations in Belgium, Romania and India. All case studies, calculations and figures assume average situations, documents of standard difficulty (including tables and images) such as are found in most archives or libraries, very high-quality results, and a medium- to long-term operation.</Text>
+<Subsection id="intensive_ocr">
+<Title>
+<Text id="184">Intensive OCR</Text>
+</Title>
+<Content>
+<Text id="185">OCR is difficult. It demands great concentration and much skill. Before attaining peak productivity level and quality, a learning period of about six weeks is needed.</Text>
+<Text id="186">Typically, best results and productivity are achieved during the first hours of each day. After three hours of OCR work, productivity declines very rapidly, perhaps to 50% of the initial level. After six hours most people become very tired.</Text>
+<Text id="187">The same kind of evolution occurs over the initial weeks. In the first few weeks everyone achieves fairly high productivity, but after that up to two-thirds of people become bored and frustrated. These people either quit or perform poorly in terms of quality and productivity. Even those who pass the first three to five critical weeks and become part of the regular work team often leave in search of a better position after 6 to 12 months.</Text>
+<Text id="188">The remarks made in Section <CrossRef target="Section" ref="the_ocr_process"/> about personnel apply particularly to intensive OCR. Quality checks are best undertaken by native speakers or people with a good command of the language being checked. Young people generally sustain higher concentration than older people for OCR work. As a rule-of-the-thumb, people aged between 18 and 23 years tend to be better suited than those over 25.</Text>
+<Text id="189">Finally, OCR can be a boring job, which makes motivation and sustained commitment to quality exceptionally important.</Text>
+<Text id="190">These facts about OCR lead to the following guidelines:</Text>
+<BulletList>
+<Bullet>
+<Text id="191">Young people between 18 and 25 are best suited for this job.</Text>
+</Bullet>
+<Bullet>
+<Text id="192">Because the first hours are always the most productive, the work should either be organized on a part-time basis or only the most motivated and concentrated people should be selected for full-time work.</Text>
+</Bullet>
+<Bullet>
+<Text id="193">Two-thirds of people tend to quit or get bored after about three to five weeks. This translates into poorer quality and low productivity in the last weeks.</Text>
+</Bullet>
+<Bullet>
+<Text id="194">A regular supply of work is needed to justify the necessary training, to maintain concentration, and to keep spirits high.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="achievable_productivity">
+<Title>
+<Text id="195">Achievable productivity</Text>
+</Title>
+<Content>
+<Table id="table_ocr_productivity">
+<Title>
+<Text id="196">OCR productivity</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="161"/>
+<th width="142">
+<Text id="197">Working hours/day</Text>
+</th>
+<th width="123">
+<Text id="198">Pages/day</Text>
+</th>
+<th width="104">
+<Text id="199">Pages/month</Text>
+</th>
+</tr>
+<tr>
+<th width="161">
+<Text id="200">Initial training (6 weeks)</Text>
+</th>
+<th width="142">
+<Text id="201">3</Text>
+</th>
+<th width="123">
+<Text id="202">6</Text>
+</th>
+<th width="104">
+<Text id="203">120</Text>
+</th>
+</tr>
+<tr>
+<th width="161">
+<Text id="204">Optimal productivity level</Text>
+</th>
+<th width="142">
+<Text id="205">3</Text>
+</th>
+<th width="123">
+<Text id="206">9</Text>
+</th>
+<th width="104">
+<Text id="207">150 to 200</Text>
+</th>
+</tr>
+<tr>
+<th width="161"/>
+<th width="142">
+<Text id="208">7</Text>
+</th>
+<th width="123">
+<Text id="209">28</Text>
+</th>
+<th width="104">
+<Text id="210">500 to 600</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="211">Table <CrossRef target="Table" ref="table_ocr_productivity"/> gives typical OCR productivity figures. Documents come in all sizes and qualities, and these figures assume that the mix of documents contains an average number of images or tablesâsay one image and one table of five rows by five columns every 8 pages. They also assume that the page images are of medium to high qualityânote that, as discussed above, this depends on the quality of scanningâand that the OCR workers have a good command of the language.</Text>
+<Text id="212">Table <CrossRef target="Table" ref="table_ocr_productivity"/> gives separate figures for people undergoing training and for those who have reached their optimal productivity level. If a member of the administrative staff were to allocate three hours a day to OCR, they could achieve 180 to 200 pages OCR per month. For full-time staff with proper training, high concentration and dedication to quality, 500 to 600 pages a month can be achieved.</Text>
+<Text id="213">However, the rates that are achieved on difficult pages of low quality, with many columns or many tables, are far lowerâperhaps 300 to 400 pages per month for full-time work.</Text>
+<Text id="214">Assume that the salary cost for dedicated and motivated full-time OCR workers is $400 per month, and the overheadâincluding management costs, computers, office space, utilities, etc.âcomes to another $300 to $400 per person per month. Then the cost of OCR comes to about $1.2 to $1.6 per page. Taking into account the training period, total volume, time-span, and layoff costs should the operation close down for lack of work, these figures rise to $1.5 to $2.5 per page.</Text>
+<Text id="215">The cost of in-house OCR should be weighed against the cost of outsourcing the work to a professional OCR company. These typically charge from $1.5 to $4 per page, including images and tables. Human Info NGO/Simple Words has such a unit in Romania, and charges humanitarian non-profit organizations a special price that ranges from $1.2 to $2 per page. Please contact us at scanning@humaninfo.org for further information and advice.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="alternatives_to_ocr">
+<Title>
+<Text id="216">Alternatives to OCR</Text>
+</Title>
+<Content>
+<Text id="217">There are two alternatives to OCR that we discuss here.</Text>
+<Subsection id="manual_retyping">
+<Title>
+<Text id="218">Manual retyping</Text>
+</Title>
+<Content>
+<Text id="219">One, which eliminates most scanning as well, is to retype the documents manually, using a word processor. This still requires the images and front cover to be scanned, but the remaining pages need not be scannedâthus one can dispense with both powerful scanners and OCR software.</Text>
+<Text id="220">The people who do this work do not have to understand the text. They must be accurate typists and re-key exactly what they see. Retyping does introduce errors, and double-keying is often used to find and correct these. This method involves two people who independently re-key the same document, after which both digital versions are compared word for word using a special software program by an operator who has the original document in front of them. The assumption is that if the same word has been typed independently twice in the same way, it is correct. However, this is not always true, and for extremely high precision, triple-keying is performed.</Text>
+<Text id="221">The advantage of rekeying is that cost is saved because an OCR program is not needed and so the computers can be older, lower-range, or second-hand modelsâwhereas powerful computers are needed for OCR. Also, the work can be performed by people with a lower level of skill. The disadvantages are that a training period of at least two months is needed. Single keying usually produces too many errors, and double or triple keying is needed.</Text>
+<Text id="222">The cost depends entirely on salary level. Typically, re-keyers in developing countries are paid on the order of $150/month. Their productivity could be twenty to thirty pages per dayâcorresponding to 400 pages per month, images included. With double-keying, this makes the total salary costs around $300 per month, plus overheads.</Text>
+</Content>
+</Subsection>
+<Subsection id="image_files">
+<Title>
+<Text id="223">Image files</Text>
+</Title>
+<Content>
+<Text id="224">A very low cost alternative to OCR is simply to use a PDF image version of the document pages. The cost is only a fraction of OCR'sâabout $0.1 per page.</Text>
+<Text id="225">Once scanning has been completed and TIFF files are available, an automatic converter (usually Adobe Acrobat or Adobe Photoshop) converts all TIFF files of book pages into PDF files.</Text>
+<Text id="226">The downside is that these files are not searchable. Also, they are quite largeâusually 50 Kb per page, plus or minus 20% depending on the quality of the original TIFF file.</Text>
+<Text id="227">PDF image files are slowâsometimes, in developing countries, impossible or prohibitively expensiveâto download. They rarely fit on a floppy disk, and do not support text manipulation functions such as cut-and-paste.</Text>
+<Text id="228">The PDF image file method should only be used if no OCR budget is available, and for documents that are likely to be used by a small number of people who have high-speed low-cost Internet access.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="combining_scanning_and_ocr">
+<Title>
+<Text id="229">Combining scanning and OCR</Text>
+</Title>
+<Content>
+<Text id="230">If a scanner is connected directly to the computer that runs the OCR software, most OCR programs can scan a page and perform OCR immediately. Page-by-page scanning and OCR is a reasonable strategy for low volumes, but will prove time-consuming for bigger and more continuous jobs.</Text>
+<Text id="231">For up to 100 to 150 pages per month, this solution may suffice. For higher volumes it is faster and more efficient to scan the document first, then perfom OCR on all the pages as a separate step.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="three_examples">
+<Title>
+<Text id="232">Three examples: 1000 to 100,000 pages</Text>
+</Title>
+<Content>
+<Section id="typical_small_collection">
+<Title>
+<Text id="233">Typical small collection: 500 to 1000 pages</Text>
+</Title>
+<Content>
+<Text id="234">Most NGOs have 500 to 1000 pages to scan. This volume can be OCRed in-house if motivated volunteers are available.</Text>
+<Part id="scanning">
+<Title>
+<Text id="235">Scanning</Text>
+</Title>
+<Content>
+<Text id="236">The first step is to scan the publications to generate a high-quality TIFF file of each page, and a separate line-art, grey-scale or color bitmap image for each illustration. Assuming that 1000 pages have to be scanned, this might represent a part-time job of about one monthâjust for scanning. The TIFF files would consume 60 to 80 Mb of hard-disk space, and a good policy is to create a CD-R containing these files. A low-cost flatbed scanner of $100 to $300 will be sufficient for the job. Scanning can be done after working hours or during the weekends by a volunteer in the office or at home.</Text>
+</Content>
+</Part>
+<Part id="ocr">
+<Title>
+<Text id="237">OCR</Text>
+</Title>
+<Content>
+<Text id="238">The second step is OCR by another volunteer, or team of volunteers, skilled in language and correction. The TIFF files can either be shared between computers, or one computer can be used for the entire job. Typically, it will take five or six months of part-time labor (e.g. 20 hours a week) to convert 1000 pages into perfect Word or HTML documents.</Text>
+</Content>
+</Part>
+<Part id="outsourcing">
+<Title>
+<Text id="239">Outsourcing</Text>
+</Title>
+<Content>
+<Text id="240">An alternative is to outsource the scanning and OCR process. It would probably cost $1500 to $2000 to convert everything into perfect Word and HTML files.</Text>
+</Content>
+</Part>
+</Content>
+</Section>
+<Section id="all_publications_from_an_organization">
+<Title>
+<Text id="241">All publications from an organization: 5000 pages</Text>
+</Title>
+<Content>
+<Text id="242">Many larger organizations have archives of around 5000 pages of currrent or out-of print books, journals, newsletters, grey literature, etc.</Text>
+<Part id="scanning_1">
+<Title>
+<Text id="243">Scanning</Text>
+</Title>
+<Content>
+<Text id="244">This is too much for a flat-bed scanner. Scanning should either be outsourced (approximately $400 for 5000 pages) or a sheet-feeder scanner purchased (approximately $900). Alternatively, a more expensive scanner could be bought together with a few other institutions or NGOs ($6000 costs divided by the number of participants). All 5000 pages in TIFF format will take about 300 to 400 Mb of hard-disk space. Again, a good policy is to create a CD-R containing these files.</Text>
+</Content>
+</Part>
+<Part id="ocr_1">
+<Title>
+<Text id="245">OCR</Text>
+</Title>
+<Content>
+<Text id="246">The second step is OCR by another volunteer, or team of volunteers, skilled in OCR and correction. Again, several computers might be used, or one computer for the whole job. It would take 25 to 30 months of half-time labor (assuming 20 hours a week) to convert 5000 pages into perfect Word or HTML. In practice this is too long and too computer-intensive to manage on a volunteer basis. One would have to pay volunteers, monitor them for performance and quality, provide adequate space, etc, in order to have the job finished within reasonable time at a high level of quality.</Text>
+<Text id="247">Alternatively one could create image PDF files, which would take 300 to 400 Mb of space and would be harder to download over the Internet.</Text>
+</Content>
+</Part>
+<Part id="outsourcing_1">
+<Title>
+<Text id="248">Outsourcing</Text>
+</Title>
+<Content>
+<Text id="249">An alternative is to outsource the scanning and OCR processes. It would probably cost $7500 to $10,000 to convert everything into perfect Word and HTML files.</Text>
+</Content>
+</Part>
+</Content>
+</Section>
+<Section id="a_small_library">
+<Title>
+<Text id="250">A small library: 100,000 pages</Text>
+</Title>
+<Content>
+<Text id="251">Larger organizations, universities, governments, and specialized libraries might have a whole library to digitizeâsay 100,000 pages. The first issue to consider is the copyright status of the publications. If they are not in the public domain, explicit permission to digitize them must be obtained from the copyright holders. You should also check whether the files are already available digitally.</Text>
+<Part id="scanning_2">
+<Title>
+<Text id="252">Scanning</Text>
+</Title>
+<Content>
+<Text id="253">The volume is too high for a sheet-feed scanner. Scanning should either be outsourced ($8000 for 100,000 pages), or a more expensive scanner purchased together with a few other institutions or NGOs ($6000 shared between the participants). 100,000 pages in TIFF format will take 6 to 8 Gb of hard-disk space. The best plan is to create a set of CD-R copies containing these files.</Text>
+</Content>
+</Part>
+<Part id="ocr_2">
+<Title>
+<Text id="254">OCR</Text>
+</Title>
+<Content>
+<Text id="255">The second step is OCR (or creation of PDF files for less widely used documents). It would take 500 to 700 months of half-time labor to convert 100,000 pages into perfect Word or HTML. This is impossible to realize with volunteers, and the job must be done on a professional basis.</Text>
+<Text id="256">To save cost, some of the less-frequently-used pagesâsay 80% or 80,000 pagesâcould be transformed into PDF, and the other 20,000 pages into Word and HTML. The PDFs would take 4 to 6 Gb space and be harder to download on the Internet, but would cost only $0.2 per page to create by a professional organization (total of $16,000). If 80,000 PDF files were created from TIFF files by volunteers using PDF conversion programs like Adobe Acrobat, 10 to 20 months of part-time work would be necessary on a powerful computer.</Text>
+</Content>
+</Part>
+<Part id="outsourcing_2">
+<Title>
+<Text id="257">Outsourcing</Text>
+</Title>
+<Content>
+<Text id="258">An alternative is to outsource the work. If the 80% PDF and 20% HTML mix were maintained, the PDF would cost around $16,000 and the HTML $30,000 to $40,000âa total budget of around $50,000. If everything were OCRed, it would cost $150,000 to $200,000 to convert the entire collection into perfect Word and /HTML files.</Text>
+</Content>
+</Part>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="creating_an_electronic_collection">
+<Title>
+<Text id="259">Creating an electronic collection</Text>
+</Title>
+<Content>
+<Text id="260">Three important aspects should be kept in mind when deciding to create digital collections. First, the collection must be organized. The more content there is, the greater the need for indexes and powerful search systems. For collections of 3000 to 5000 pages or more, indexes and search systems are essential. Second, the needs of end-users must prevail. The target groups that will use the collection should be identified, and a process of regular consultation set up. Third, the available budget will determine how much can be done.</Text>
+<Section id="methods_of_collection_building">
+<Title>
+<Text id="261">Methods of collection building</Text>
+</Title>
+<Content>
+<Text id="262">There are many examples of excellent CD-ROMs that are created on the web-page model. HTML, PDF or Word documents are added and linked using hyperlinks. Navigation is made simple and attractive by the use of hyperlinks, frames, keywords, indexes and so on. Such systems work well up to a few thousand pages, but from 3000 to 5000 pages onwards it is important to have a well-structured collection and a powerful search facility. This is where the Greenstone software can help.</Text>
+<Text id="263">The Greenstone Digital Library software creates a structured digital library including a very powerful search and retrieval engine. Up to 150,000 pages can be indexed on a single CD-ROM. Every CD-ROM can become an Internet server. Greenstone is open-source software, and is freely available under the GNU license.</Text>
+<Text id="264">The companion manuals describe how to build Greenstone collections. There are essentially three different ways of building collections:</Text>
+<BulletList>
+<Bullet>
+<Text id="265">The librarian interface</Text>
+</Bullet>
+<Bullet>
+<Text id="266">The Collector</Text>
+</Bullet>
+<Bullet>
+<Text id="267">Building from the command line.</Text>
+</Bullet>
+</BulletList>
+<Text id="268">The first method is the âlibrarianâ interface, described in the <i>Greenstone Digital Library User's Guide</i>(Chapter 3, âMaking Greenstone Collectionsâ). This is a comprehensive interactive facility for collection-building. With it, you can collect sets of documents, import or assign metadata, and build them into a Greenstone collection. The second method is the âCollectorâ subsystem, described in Chapter 4 of the <i>User's Guide</i>. This is an older facility that provides an alternative way of building collections of web pages or other documents. It guides you through a sequence of interactive web pages that request the information needed. However, it does not provide any way of adding metadata to the documents, andâbecause it is a web interfaceâit is not really suitable for collections that take more than a few minutes to build. The third method is to run the programs for collection-building directly from the command line; this is in the <i>Greenstone Digital Library Developer's Guide</i>(Chapter 1). This gives more flexibility in running programs individually and saving intermediate results, which may be desirable for collections that take many hours to build. You will also need to read Chapter 2 of the <i>Developer's Guide</i> in order to harness the full power of Greenstone to build advanced collections.</Text>
+<Text id="269">There is a fourth method for creating and editing the material associated with a collection, a program called the Collection Organizer. However, its functionality has been superseded by the librarian interface mentioned above. It is described in a legacy document entitled <i>Using the Organizer</i>.</Text>
+</Content>
+</Section>
+<Section id="getting_started_in_seven_steps_and_15_minutes">
+<Title>
+<Text id="270">Getting started in seven steps and 15 minutes</Text>
+</Title>
+<Content>
+<Text id="271">The best way of getting the look and feel of the librarian interface is to actually create a small test library. If you have 15 minutes please follow these steps and you will understand this program much better.</Text>
+<Text id="272">Before getting started, first install Greenstone (see the <i>Greenstone Installer's Guide</i>) which includes the Demo collection in DLS format and its source files. <b>Note, if you wish to be able to add to your collection any of the 140 documents in the DLS collection (instead of just the 11 of these documents in the Greenstone Demo collection), you should install DLS as one of the sample Greenstone libraries.</b> The Demo and DLS collections will be installed in <i>C:\Program Files\gsdl\collect</i>, in subdirectories <i>demo</i> and <i>dls</i> respectively. If you previously installed Greenstone without DLS and wish to install it, then you may re-insert your Greenstone CD-ROM and add this collection. It is not necessary to uninstall Greenstone first.</Text>
+<Text id="273">We suggest that you print the instructions below and follow them step by step:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="274">Launch the librarian interface under Windows by selecting <i>Greenstone Digital Library</i> from the <i>Programs</i> section of the <i>Start</i> menu and choosing <i>Librarian Interface</i>If you are using Unix, instead type</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<CodeLine>cd gli</CodeLine>
+<CodeLine>./gli.sh</CodeLine>
+<Text id="275">where <i>~/gsdl</i> is the directory containing your Greenstone system.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="276">Select <i>New</i> from the File menu in the horizontal menu bar at the top of the window. Give it a title, for example âMy First Collection,â and fill out your email address and a brief description of the collection. In the âBase this collection onâ menu, choose âgreenstone demoâ or âDevelopment Library Subsetâ (the effect is the same because these two collections have the same structure).</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="277">Add some documents from the Demo collection (or the DLS collection if it is installed) to your new collection. To do this, double-click the <i>Greenstone Collections</i> folder in the left-hand panel, then double-click the collection you desire. The documents in it are displayed underneath. Select one of these, drag it, and drop into the right-hand panel. This panel represents the collection you are building. Choose several documents and drag them into it one by one, or using multiple selection in the standard way.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="278">Add some of your own documents that are not in the Demo or DLS collections. Close the <i>Greenstone Collections</i> folder in the left-hand panel and double-click the <i>Local Filespace</i> folder. Navigate to a directory that contains some documents (e.g. small Word or HTML files). Drag a few of these into the right-hand panel to include them in your collection.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="279">Add metadata to the documents in your collection. So far you have been operating under the <i>Gather</i> panel, indicated by the <i>Gather</i> tab underneath the horizontal menu bar at the top of the window. Click the <i>Enrich</i> tab beside it. The documents in your collection now appear in the left-hand panel: click one and examine the metadata associated with it in the â<i>Element âŠ Value</i>â table at the top right. Use the panel underneath to change individual values by selecting the desired <i>Element</i> and either choosing an existing value from the list or typing a new value into the box near the bottom. Add <i>Title</i>, <i>Organization</i>, and <i>Keyword</i> metadata to each of your own documents that you put in the collection. After you type each value you need to click â <i>Appendix</i> to add that value to the metadata.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="280">Click the <i>Create</i> tab to leave the <i>Enrich</i> mode and create your new collection. Click the <i>Build Collection</i> button at the bottom. While the computer is building the collection you will receive some feedback on what it is doing.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="281">When it has finished, click the <i>Preview</i> tab to view the collection from within the librarian interface. Check the <i>titles a-z</i>, <i>organisations</i> and <i>how to</i> lists to ensure that your documents have been included in the collection. You will also find when you visit your Greenstone home page that the collection has been installed as one of the regular collections.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="282">All sums of money mentioned in this document are in US dollars, and were current in 2001.</Text>
+</Footnote>
+<Footnote id="2">
+<Text id="283">Recall that all sums of money are expressed in 2001 US dollars.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/en/User_en.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/en/User_en.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/en/User_en.xml	(revision 13632)
@@ -0,0 +1,2510 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">GREENSTONE DIGITAL LIBRARY</Text>
+</Heading>
+<Title>
+<Text id="2">USER'S GUIDE</Text>
+</Title>
+<Author>
+<Text id="3">Ian H. Witten, Stefan Boddie and John Thompson</Text>
+</Author>
+<Affiliation>
+<Text id="4">Department of Computer Science <br/>University of Waikato, New Zealand</Text>
+</Affiliation>
+<Text id="5">Greenstone is a suite of software for building and distributing digital library collections. It provides a new way of organizing information and publishing it on the Internet or on CD-ROM. Greenstone is produced by the New Zealand Digital Library Project at the University of Waikato, and developed and distributed in cooperation with UNESCO and the Human Info NGO. It is open-source software, available from <i>http://greenstone.org</i> under the terms of the Gnu General Public License.</Text>
+<Comment>
+<Text id="6">We want to ensure that this software works well for you. Please report any problems to <i>greenstone@cs.waikato.ac.nz</i></Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.70</Text>
+</Version>
+<Date>
+<Text id="8">March 2006</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">About this manual</Text>
+</Title>
+<Content>
+<Text id="10">This manual provides a comprehensive description of how to use the Greenstone software for accessing and building digital library collections.</Text>
+<Text id="11">Section <CrossRef target="Chapter" ref="overview_of_greenstone"/> gives an overview of the capabilities of the software. Section <CrossRef target="Chapter" ref="using_greenstone_collections"/> explains how to use Greenstone collections. The interface is self-explanatoryâthe best way to learn is by doingand this section comprises the on-line help information for a typical collection. Section <CrossRef target="Chapter" ref="making_greenstone_collections"/> explains how to build your own library collections using the Greenstone Librarian Interface. Section <CrossRef target="Chapter" ref="administration"/> introduces the administration facility that allows the system administrator to monitor what is going on and control who can build collections.</Text>
+<Text id="12">Appendices list the features of the Greenstone software, and give a glossary of terms used throughout the Greenstone documentation.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="13">Companion documents</Text>
+</Title>
+<Content>
+<Text id="14">The complete set of Greenstone documents includes four volumes:</Text>
+<BulletList>
+<Bullet>
+<Text id="15">Greenstone Digital Library Installer's Guide</Text>
+</Bullet>
+<Bullet>
+<Text id="16">Greenstone Digital Library User's Guide <i>(this document)</i></Text>
+</Bullet>
+<Bullet>
+<Text id="17">Greenstone Digital Library Developer's Guide</Text>
+</Bullet>
+<Bullet>
+<Text id="18">Greenstone Digital Library: From Paper to Collection</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">Acknowledgements</Text>
+</Title>
+<Content>
+<Text id="20">The Greenstone software is a collaborative effort between manypeople. Rodger McNab and Stefan Boddie are the principal architects andimplementors. Contributions have been made by David Bainbridge, GeorgeBuchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, JohnMcPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, ToddReed, Bill Rogers, John Thompson, and Stuart Yeates. Other members of the New ZealandDigital Library project provided advice and inspiration in the design ofthe system: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te TakaKeegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols and Lloyd Smith. We would also like toacknowledge all those who have contributed to the GNU-licensed packagesincluded in this distribution: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE and XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="overview_of_greenstone">
+<Title>
+<Text id="21">Overview of Greenstone</Text>
+</Title>
+<Content>
+<Text id="22">Greenstone is a comprehensive system for constructing and presenting collections of thousands or millions of documents, including text, images, audio and video.</Text>
+<Section id="collections">
+<Title>
+<Text id="23">Collections</Text>
+</Title>
+<Content>
+<Text id="24">A typical digital library built with Greenstone will contain many collections, individually organizedâthough they bear a strong family resemblance. Easily maintained, collections can be augmented and rebuilt automatically.</Text>
+<Text id="25">There are several ways to find information in most Greenstone collections. For example, you can <i>search for particular words</i> that appear in the text, or within a section of a document. You can <i>browse documents by title</i>: just click on a book to read it. You can <i>browse documents by subject</i>. Subjects are represented by bookshelves: just click on a bookshelf to look at the books. Where appropriate, documents come complete with a table of contents: you can click on a chapter or subsection to open it, expand the full table of contents, or expand the full document into your browser window (useful for printing). The New Zealand Digital Library website (<i>nzdl.org</i>) provides numerous example collections.</Text>
+<Text id="26">On the front page of each collection is a statement of its purpose and coverage, and an explanation of how the collection is organized. Most collections can be accessed by both <i>searching</i> and <i>browsing</i>. When searching, the Greenstone software looks through the entire text of all documents in the collection (this is called âfull-text searchâ). In most collections the user can choose between indexes built from different parts of the documents. Some collections have an index of full documents, an index of paragraphs, and an index of titles, each of which can be searched for particular words or phrases. Using these you can find all documents that contain a particular set of words (the words may be scattered far and wide throughout the document), or all paragraphs that contain the set of words (which must all appear in the same paragraph), or all documents whose titles contain the words (the words must all appear in the document's title). There might be other indexes, perhaps an index of sections, and an index of section headings. Browsing involves lists that the user can examine: lists of authors, lists of titles, lists of dates, hierarchical classification structures, and so on. Different collections offer different browsing facilities.</Text>
+</Content>
+</Section>
+<Section id="finding_information">
+<Title>
+<Text id="27">Finding information</Text>
+</Title>
+<Content>
+<Text id="28">Greenstone constructs full-text indexes from the document textâthat is, indexes that enable searching on any words in the full text of the document. Indexes can be searched for particular words, combinations of words, or phrases, and results are ordered according to how relevant they are to the query.</Text>
+<Text id="29">In most collections, descriptive data such as author, title, date, keywords, and so on, is associated with each document. This information is called <i>metadata</i>. Many document collections also contain full-text indexes of certain kinds of metadata. For example, many collections have a searchable index of document titles.</Text>
+<Text id="30">Users can browse interactively around lists, and hierarchical structures, that are generated from the metadata that is associated with each document in the collection. Metadata forms the raw material for browsing. It must be provided explicitly or be derivable automatically from the documents themselves. Different collections offer different searching and browsing facilities. Indexes for both searching and browsing are constructed during a âbuildingâ process, according to information in a collection configuration file.</Text>
+<Text id="31">Greenstone creates all index structures automatically from the documents and suppporting files: nothing is done manually. If new documents in the same format become available, they can be merged into the collection automatically. Indeed, for many collections this is done by processes that awake regularly, scout for new material, and rebuild the indexesâall without manual intervention.</Text>
+</Content>
+</Section>
+<Section id="document_formats">
+<Title>
+<Text id="32">Document formats</Text>
+</Title>
+<Content>
+<Text id="33">Source documents come in a variety of formats, and are converted into a standard XML form for indexing by âplugins.â Plugins distributed with Greenstone process plain text, HTML, WORD and PDF documents, and Usenet and E-mail messages. New ones can be written for different document types (to do this you need to study the <i>Greenstone Digital Library Developer's Guide</i>). To build browsing structures from metadata, an analogous scheme of âclassifiersâ is used. These create browsing indexes of various kinds: scrollable lists, alphabetic selectors, dates, and arbitrary hierarchies. Again, Greenstone programmers can create new browsing structures.</Text>
+</Content>
+</Section>
+<Section id="multimedia_and_multilingual_documents">
+<Title>
+<Text id="34">Multimedia and multilingual documents</Text>
+</Title>
+<Content>
+<Text id="35">Collections can contain text, pictures, audio and video. Non-textual material is either linked into the textual documents or accompanied by textual descriptions (such as figure captions) to allow full-text searching and browsing.</Text>
+<Text id="36">Unicode, which is a standard scheme for representing the character sets used in the world's languages, is used throughout Greenstone. This allows any language to be processed and displayed in a consistent manner. Collections have been built containing Arabic, Chinese, English, French, M 0Ã
+Â 1ori and Spanish. Multilingual collections embody automatic language recognition, and the interface is available in all the above languages (and more).</Text>
+</Content>
+</Section>
+<Section id="distributing_greenstone">
+<Title>
+<Text id="37">Distributing Greenstone</Text>
+</Title>
+<Content>
+<Text id="38">Collections are accessed over the Internet or published, in precisely the same form, on a self-installing Windows CD-ROM. Compression is used to compact the text and indexes. A Corba protocol supports distributed collections and graphical query interfaces.</Text>
+<Text id="39">The New Zealand Digital Library (<i>nzdl.org</i>) provides many example collections, including historical documents, humanitarian and development information, technical reports and bibliographies, literary works, and magazines.</Text>
+<Text id="40">Being open source, Greenstone is readily extensible, and benefits from the inclusion of Gnu-licensed modules for full-text retrieval, database management, and text extraction from proprietary document formats. Only through international cooperative efforts will digital library software become sufficiently comprehensive to meet the world's needs with the richness and flexibility that users deserve.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="using_greenstone_collections">
+<Title>
+<Text id="41">Using Greenstone Collections</Text>
+</Title>
+<Content>
+<Text id="42">The Greenstone software is designed to be easy to use. Web-based and CD-ROM collections have interfaces that are identical. Installing the Greenstone software from CD-ROM on any Windows or Linux computer is very easy indeed; a standard installation setup program is used in conjunction with pre-compiled binaries. A collection can be used locally on the computer where it is installed; also, if this computer is connected to a network, the software automatically and transparently allows all other computers on the network to access the same collection.</Text>
+<Text id="43">The next section describes how to install a Greenstone CD-ROM. Then we look at the searching and browsing facilities offered by a typical Greenstone collection, the âDemoâ collection that is supplied with the Greenstone software. Other collections offer similar facilities; if you can use one, you can use them all. The following section explains how to customize the interface for your own requirements using the Preferences page.</Text>
+<Section id="using_a_greenstone_cd-rom">
+<Title>
+<Text id="44">Using a Greenstone CD-ROM</Text>
+</Title>
+<Content>
+<Text id="45">The Greenstone digital library software itself comes on a CD-ROM, and you or your system manager have probably installed it on your system, following the instructions in the <i>Greenstone Digital Library Installer's Guide.</i> If so, Greenstone is already installed on your computer and you should skip the rest of this section.</Text>
+<Text id="46">Some Greenstone collections come on a self-contained Greenstone CD-ROM that includes enough of the software to run just that collection. To use it, simply put it into the CD-ROM drive on any Windows PC. Most likely (if âautorunâ is enabled on your PC), a window will appear inviting you to install the Greenstone software. If not, find the CD-ROM disk drive (on current Windows systems you can get this by clicking on the <i>My Computer</i> icon on the desktop) and double-click it, then the <i>Setup.exe</i> file inside it. The Greenstone <i>Setup</i> program will be entered, which guides you through the setup procedure. Most people respond <i>yes</i> to all the questions.</Text>
+<Text id="47">When the installation procedure has finished, you'll find the library in the <i>Programs</i> submenu of the Windows <i>Start</i> menu, under the name of the collection (for example, âDevelopment Libraryâ or âUnited Nations Universityâ).</Text>
+<Text id="48">Once the software has been installed, the library will be entered automatically every time you re-insert the CD-ROM if autorun is enabled.</Text>
+</Content>
+</Section>
+<Section id="finding_information_1">
+<Title>
+<Text id="49">Finding information</Text>
+</Title>
+<Content>
+<Text id="50">The easiest way to learn how to use a Greenstone collection is to try it out. Don't worryâyou can't break anything. Click liberally: most images that appear on the screen are clickable. If you hold the mouse stationary over an image, most browsers will soon pop up a message that tells you what will happen if you click.</Text>
+<Text id="51">Experiment! Choose common words like âtheâ and âandâ to search forâthat should evoke some responses, and nothing will break.</Text>
+<Text id="52">Greenstone digital library systems usually comprise several separate collectionsâfor example, computer science technical reports, literary works, internet FAQs, magazines. There will be a home page for the digital library system which allows you to access any publicly-accessible collection; in addition, each collection has its own âaboutâ page that gives you information about how the collection is organized and the principles governing what is included in it. To get back to the âaboutâ page at any time, just click on the âcollectionâ icon that appears at the top left side of all searching and browsing pages.</Text>
+<Text id="53">Figure 1 shows a screenshot of the âDemoâ collection supplied with the Greenstone software, which is a very small subset of the Development Library collection; we will use it as an example to describe the different ways of finding information. (If you can't find the Demo collection, use the Development Library instead; it looks just the same.) First, almost all icons are clickable. Several icons appear at the top of almost every page; Table 1 shows you what they mean.</Text>
+<Figure id="using_the_demo_collection">
+<Title>
+<Text id="54">Using the Demo collection</Text>
+</Title>
+<File width="397" height="286" url="images/User_Fig_1.png"/>
+</Figure>
+<Table id="what_the_icons_at_the_top_of_each_page_mean">
+<Title>
+<Text id="55">What the icons at the top of each page mean</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<File width="68" height="32" url="images/User_Icon_1.png"/>
+</th>
+<th width="397">
+<Text id="56">This takes you to the âaboutâ page</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<File width="36" height="16" url="images/User_Icon_2.png"/>
+</th>
+<th width="397">
+<Text id="57">This takes you to the Digital Library's home page, from which you can select another collection</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<File width="29" height="16" url="images/User_Icon_3.png"/>
+</th>
+<th width="397">
+<Text id="58">This provides help text similar to what you are reading now</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<File width="70" height="16" url="images/User_Icon_4.png"/>
+</th>
+<th width="397">
+<Text id="59">This allows you to set some user interface and searching options that will then be used henceforth</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="60">The â<i>search âŠ subjects âŠ titles a-z âŠ organization âŠ how to</i>â bar underneath gives access to the searching and browsing facilities. The leftmost button is for searching, and the ones to the right of itâfour, in this collectionâevoke different browsing facilities. These last four may differ from one collection to another.</Text>
+<Subsection id="how_to_find_information">
+<Title>
+<Text id="61">How to find information</Text>
+</Title>
+<Content>
+<Text id="62">Table 2 shows the five ways to find information in the Demo collection.</Text>
+<Table id="table_icons_on_the_search_browse_bar">
+<Title>
+<Text id="63">What the icons on the search/browse bar mean</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="123">
+<File width="61" height="11" url="images/User_Icon_5.png"/>
+</th>
+<th width="407">
+<Text id="64">Search for particular words</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="58" height="11" url="images/User_Icon_6.png"/>
+</th>
+<th width="407">
+<Text id="65">Access publications by subject</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="58" height="11" url="images/User_Icon_7.png"/>
+</th>
+<th width="407">
+<Text id="66">Access publications by title</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="71" height="11" url="images/User_Icon_8.png"/>
+</th>
+<th width="407">
+<Text id="67">Access publications by organization</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="58" height="11" url="images/User_Icon_9.png"/>
+</th>
+<th width="407">
+<Text id="68">Access publications by âhow toâ listing</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="69">You can <i>search for particular words</i> that appear in the text from the âsearchâ page. (This is just like the âaboutâ page shown in Figure 1, except that it doesn't contain the <i>about this collection</i> text.) The search page can be reached from other pages by pressing the <i>search</i> button. You can <i>access publications by subject</i> by pressing the <i>subjects</i> button. This brings up a list of subjects, represented by bookshelves that can be further expanded by clicking on them. You can <i>access publications by title</i> by pressing the <i>titles a-z</i> button. This brings up a list of books in alphabetic order. You can <i>access publications by organization</i> by pressing the <i>organization</i> button. This brings up a list of organizations. You can <i>access publications by how to listing</i> by pressing the <i>how to</i> button. This brings up a list of âhow toâ hints. All these buttons are visible in Figure 1.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_to_read_the_documents">
+<Title>
+<Text id="70">How to read the documents</Text>
+</Title>
+<Content>
+<Text id="71">In the Demo collection, you can tell when you have arrived at an individual book because there is a photograph of its front cover (Figure 2). Beside the photograph is a table of contents: the entry in bold face marks where you are, in this case <i>Introduction and Summary</i> âSection 1 of the chosen book. This table is expandable: click on the folders to open them or close them. Click on the open book at the top to close it.</Text>
+<Text id="72">Underneath is the text of the current section (âThe international demand for tropical butterflies âŠâ in the example, beginning at the very bottom of the illustration). When you have read through it, there are arrows at the end to take you on to the next section or back to the previous one.</Text>
+<Text id="73">Below the photograph are four buttons. Click on <i>detach</i> to make a new browser window for this book. (This is useful if you want to compare books, or read two at once.) If you have reached this book through a search, the search terms will be highlighted: the <i>no highlighting</i> button turns this off. Click on <i>expand text</i> to expand out the whole text of the current section, or book. Click on <i>expand contents</i> to expand out the whole table of contents so that you can see the titles of all chapters and subsections.</Text>
+<Text id="74">In some collections, the documents do not have this kind of hierarchical structure. In this case, no table of contents is displayed when you get to an individual documentâjust the document text. In some cases, the document is split into pages, and you can read sequentially or jump about from one page to another.</Text>
+<Figure id="a_book_in_the_demo_collection">
+<Title>
+<Text id="75">A book in the Demo collection</Text>
+</Title>
+<File width="397" height="476" url="images/User_Fig_2.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="what_the_icons_mean">
+<Title>
+<Text id="76">What the icons mean</Text>
+</Title>
+<Content>
+<Text id="77">When you are browsing around the collection, you will encounter the items shown in Table 3.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_to_search_for_particular_words">
+<Title>
+<Text id="78">How to search for particular words</Text>
+</Title>
+<Content>
+<Text id="79">From the search page, follow these simple steps to make a query:</Text>
+<BulletList>
+<Bullet>
+<Text id="80">Specify what units you want to search: in the Demo collection you can search section titles or the full text of the books.</Text>
+</Bullet>
+<Bullet>
+<Text id="81">Say whether you want to search for all or just some of the words</Text>
+</Bullet>
+<Bullet>
+<Text id="82">Type in the words you want to search for into the query box</Text>
+</Bullet>
+<Bullet>
+<Text id="83">Click the <i>Begin Search</i> button</Text>
+</Bullet>
+</BulletList>
+<Text id="84">When you make a query, the titles of up to twenty matching documents will be shown. There is a button at the end to take you on to the next twenty. From there you will find buttons to take you on to the third twenty or back to the first twenty, and so on. However, for efficiency reasons a maximum of 100 is imposed on the number of documents returned. You can change these numbers by clicking the <i>preferences</i> button at the top of the page.</Text>
+<Table id="table_icons_that_you_will_encounter_when_browsing">
+<Title>
+<Text id="85">Icons that you will encounter when browsing</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="123">
+<File width="19" height="12" url="images/User_Icon_10.png"/>
+</th>
+<th width="407">
+<Text id="86">Click on a book icon to read the corresponding book</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="22" height="17" url="images/User_Icon_11.png"/>
+</th>
+<th width="407">
+<Text id="87">Click on a bookshelf icon to look at books on that subject</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="25" height="16" url="images/User_Icon_12.png"/>
+</th>
+<th width="407">
+<Text id="88">View this document</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="25" height="16" url="images/User_Icon_13.png"/>
+</th>
+<th width="407">
+<Text id="89">Open this folder and view contents</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="29" height="25" url="images/User_Icon_14.png"/>
+</th>
+<th width="407">
+<Text id="90">Click on this icon to close the book</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="25" height="17" url="images/User_Icon_15.png"/>
+</th>
+<th width="407">
+<Text id="91">Click on this icon to close the folder</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="32" height="17" url="images/User_Icon_16.png"/>
+</th>
+<th width="407">
+<Text id="92">Click on the arrow to go on to the next section ...</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="32" height="17" url="images/User_Icon_17.png"/>
+</th>
+<th width="407">
+<Text id="93">... or back to the previous section</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="49" height="31" url="images/User_Icon_18.png"/>
+</th>
+<th width="407">
+<Text id="94">Open this page in a new window</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="61" height="32" url="images/User_Icon_19.png"/>
+</th>
+<th width="407">
+<Text id="95">Expand table of contents</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="48" height="32" url="images/User_Icon_20.png"/>
+</th>
+<th width="407">
+<Text id="96">Display all text</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="55" height="31" url="images/User_Icon_21.png"/>
+</th>
+<th width="407">
+<Text id="97">Highlight search terms</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="98">Click the title of any document, or the little icon beside it, to open it. The icon may show a book, or a folder, or a page: it will be a book icon if you are searching books; otherwise if you are searching sections it will be a folder or page icon depending on whether or not the section found has subsections.</Text>
+<Part id="search_terms">
+<Title>
+<Text id="99"><b><i>Search terms</i></b></Text>
+</Title>
+<Content>
+<Text id="100">Whatever you type into the query box is interpreted as a list of words called âsearch terms.â Each search term contains nothing but alphabetic characters and digits. Terms are separated by white space. If any other characters such as punctuation appear, they serve to separate terms just as though they were spaces. And then they are ignored. You can't search for words that include punctuation.</Text>
+<Text id="101">For example, the query</Text>
+<Text type="code" id="102">Agro-forestry in the Pacific Islands: Systems for Sustainability (1993)</Text>
+<Text id="103">will be treated the same as</Text>
+<Text type="code" id="104">Agro forestry in the Pacific Islands Systems for Sustainability 1993</Text>
+</Content>
+</Part>
+<Part id="query_type">
+<Title>
+<Text id="105"><b><i>Query type</i></b></Text>
+</Title>
+<Content>
+<Text id="106">There are two different kinds of query.</Text>
+<BulletList>
+<Bullet>
+<Text id="107">Queries for all the words. These look for documents (or chapters, or titles) that contain all the words you have specified. Documents that satisfy the query are displayed.</Text>
+</Bullet>
+<Bullet>
+<Text id="108">Queries for some of the words. Just list some terms that are likely to appear in the documents you are looking for. Documents are displayed in order of how closely they match the query. When determining the degree of match,</Text>
+<BulletList>
+<Bullet>
+<Text id="109">the more search terms a document contains, the closer it matches;</Text>
+</Bullet>
+<Bullet>
+<Text id="110">rare terms are more important than common ones;</Text>
+</Bullet>
+<Bullet>
+<Text id="111">short documents match better than long ones.</Text>
+</Bullet>
+</BulletList>
+</Bullet>
+</BulletList>
+</Content>
+</Part>
+<Text id="112">Use as many search terms as you likeâa whole sentence, or even a whole paragraph. If you specify only one term, it doesn't much matter whether you use an <i>all</i> or a <i>some</i> query, except that in the second case the results will be sorted by the search term's frequency of occurrence.</Text>
+</Content>
+</Subsection>
+<Subsection id="scope_of_queries">
+<Title>
+<Text id="113">Scope of queries</Text>
+</Title>
+<Content>
+<Text id="114">In most collections you can choose different indexes to search. For example, there might be author or title indexes. Or there might be chapter or paragraph indexes. Generally, the full matching document is returned regardless of which index you search.</Text>
+<Text id="115">If documents are books, they will be opened at the appropriate place.</Text>
+</Content>
+</Subsection>
+<Subsection id="advanced_search_features">
+<Title>
+<Text id="116">Advanced search features</Text>
+</Title>
+<Content>
+<Text id="117">While the above is enough to meet most searching needs, some more advanced search features are provided. These are activated from the Preferences page, which is reached by clicking the <i>preferences</i> button at the top of the pageâsee Section 2.3 below. After changing your preferences, do not click your browser's <i>Back</i> buttonâthat would undo the changes. Instead, click any of the buttons on the search/browse bar.</Text>
+<Part id="case_sensitivity_and_stemming">
+<Title>
+<Text id="118"><i><b>Case sensitivity and stemming</b></i></Text>
+</Title>
+<Content>
+<Text id="119">When you specify search terms, you can choose whether upper and lower case must match between the query and the document: this is called âcase sensitivity.â You can also choose whether to ignore word endings or not: this is called âstemming.â</Text>
+<Text id="120">Under <i>Search options</i> on the Preferences page you will see a pair of buttons labeled <i>ignore case differences</i> and <i>upper/lower case must match</i>; these control the case sensitivity of your queries. Below is a pair of buttons labeled <i>ignore word endings</i> and <i>whole word must match</i>: these control stemming.</Text>
+<Text id="121">For example, if the buttons <i>ignore case differences</i> and <i>ignore word endings</i> are selected, the query</Text>
+<Text type="code" id="122">African building</Text>
+<Text id="123">will be treated the same as</Text>
+<Text type="code" id="124">africa builds</Text>
+<Text id="125">because the uppercase letter in âAfricanâ will be transformed to lowercase, and the suffixes ânâ and âingâ will be removed from âAfricanâ and âbuildingâ respectively (also, âsâ would be removed from âbuildsâ).</Text>
+<Text id="126">Generally case differences and word endings should be ignored unless you are querying for particular names or acronyms.</Text>
+</Content>
+</Part>
+<Part id="phrase_searching">
+<Title>
+<Text id="127"><b><i>Phrase searching</i></b></Text>
+</Title>
+<Content>
+<Text id="128">If your query includes a phrase in quotation marks, only documents containing that phrase, exactly as typed, will be returned.</Text>
+<Text id="129">If you want to use phrase searching, you need to learn a little about how it works. Phrases are processed by a post-retrieval scan. First the query is issued in the normal wayâall the words in the phrase are included as search termsâand then the documents returned are scanned to eliminate those in which that phrase does not appear.</Text>
+<Text id="130">During the post-retrieval scan, phrases are checked just as they are, including any punctuation. For example, the query</Text>
+<Text type="code" id="131">what's a âpost-retrieval scan?â</Text>
+<Text id="132">will first retrieve all documents that match all of the words</Text>
+<CodeLine>what s a post retrieval scan</CodeLine>
+<Text id="133">and then the documents returned will be checked for the phrase</Text>
+<Text type="code" id="134">post-retrieval scan?</Text>
+<Text id="135">Phrase matches are case-insensitive if <i>ignore case differences</i> is set on the Preferences page.</Text>
+</Content>
+</Part>
+<Part id="advanced_query_mode">
+<Title>
+<Text id="136"><b><i>Advanced query mode</i></b></Text>
+</Title>
+<Content>
+<Text id="137">In <i>advanced query mode</i>, which can be selected on the Preferences page, the queries for <i>all</i> of the words, described above, are actually Boolean queries. They consist of a list of terms joined by logical operators &amp; (and), | (or), and ! (not). Absent operatorsbetween search terms are interpreted as &amp; (and): thus a query without any operators returns documents that match <i>all</i> the terms.</Text>
+<Text id="138">If the words AND, OR, and NOT appear in your query they are treated as ordinary search terms, not operators. For operators you must use &amp;, |, and !. In addition, parentheses can be used for grouping.</Text>
+</Content>
+</Part>
+<Part id="using_search_history">
+<Title>
+<Text id="139"><b><i>Using search history</i></b></Text>
+</Title>
+<Content>
+<Text id="140">When you switch on the âsearch historyâ feature on the Preferences page you will be shown your last few searches, along with a summary of how many results they generated. Click the button beside one of the previous searches to copy the text into the search box. This makes it easy to repeat slightly modified versions of previous queries.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="changing_the_preferences">
+<Title>
+<Text id="141">Changing the preferences</Text>
+</Title>
+<Content>
+<Figure id="the_preferences_page">
+<Title>
+<Text id="142">The Preferences page</Text>
+</Title>
+<File width="394" height="439" url="images/User_Fig_3.png"/>
+</Figure>
+<Text id="143">When you click the <i>preferences</i> button at the top of the page you will be able to change some features of the interface to suit your own requirements. The preferences depend on the collection; an example is shown in Figure 3. When you adjust your search preferences, you should press the <i>set preferences</i> button shown in Figure 3. After setting preferences, do not use your browser's âbackâ buttonâthat would unset them! Instead, click one of the buttons on the access bar near the top of the page.</Text>
+<Subsection id="collection_preferences">
+<Title>
+<Text id="144">Collection preferences</Text>
+</Title>
+<Content>
+<Text id="145">Some collections comprise several subcollections, which can be searched independently or together, as one unit. If so, you can select which subcollections to include in your searches on the Preferences page.</Text>
+</Content>
+</Subsection>
+<Subsection id="language_preferences">
+<Title>
+<Text id="146">Language preferences</Text>
+</Title>
+<Content>
+<Text id="147">Each collection has a default presentation language, but you can switch to a different language if you like. You can also alter the encoding scheme used by Greenstone for output to the browserâthe software chooses sensible defaults, but with some browsers better visual results can be used by switching to a different encoding scheme. All collections allow you to switch from the standard graphical interface format to a textual one. This is particularly useful for visually impaired users who use large screen fonts or speech synthesizers for output.</Text>
+</Content>
+</Subsection>
+<Subsection id="presentation_preferences">
+<Title>
+<Text id="148">Presentation preferences</Text>
+</Title>
+<Content>
+<Text id="149">Depending on the collection, there may be other options you can set that control the presentation. Collections of web pages allow you to suppress the Greenstone navigation bar at the top of each document page, so that once you have done a search you land at the exact web page that matches without any Greenstone header. To do another search you will have to use your browser's âbackâ button. These collections also allow you to suppress Greenstone's warning message when you click a link that takes you out of the digital library collection and on to the web itself. And in some web collections you can control whether the links on the âSearch Resultsâ page take you straight to the actual URL in question, rather than to the digital library's copy of the page.</Text>
+</Content>
+</Subsection>
+<Subsection id="search_preferences">
+<Title>
+<Text id="150">Search preferences</Text>
+</Title>
+<Content>
+<Text id="151">Under <i>Search preferences</i> in Figure 3, the first pair of buttons allows you to get a large query box, so that you can easily do paragraph-sized searching. In Greenstone, it is surprisingly quick to search for large amounts of text. The next two pairs of buttons control the kind of text matching in the searches that you make. The first set (labeled âcase differencesâ) controls whether upper and lower case must match. The second (âword endingsâ) controls whether to ignore word endings or not.</Text>
+<Text id="152">Using the next button pair you can switch to the âadvancedâ query mode described above, which allows you to specify more precise queries by combining terms using AND (&amp;), OR (|), and NOT (!). You can turn the search history feature, described above, on and off. Finally, you can control the number of hits returned, and the number presented on each screenful, through the last entry in Figure 3.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="making_greenstone_collections">
+<Title>
+<Text id="153">Making Greenstone Collections</Text>
+</Title>
+<Content>
+<Text id="154">The simplest way to build new collections is to use Greenstone's âlibrarianâ interface (GLI). This allows you to collect sets of documents, import or assign metadata, and build them into a Greenstone collection. It supports five basic activities, which can be interleaved but are nominally undertaken in this order:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="155">Copy documents from the computer's file space, including existing collections, into the new collection. Any existing metadata remains âattachedâ to these documents. Documents may also be gathered from the web through a built-in mirroring facility.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="156">Enrich the documents by adding further metadata to individual documents or groups of documents.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="157">Design the collection by determining its appearance and the access facilities that it will support.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="158">Build the collection using Greenstone.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="159">Preview the newly created collection, which will have been installed on your Greenstone home page as one of the regular collections.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="160">The librarian interface allows you to add what people call âexternalâ metadata to documents, metadata that pertains to the document as a whole. But documents often need to be structured into sections and subsections, and âinternalâ metadata might be associated with each part. In Greenstone, source documents can be tagged with this information, and we explain this in Section 3.3.</Text>
+<Text id="161">Finally, an alternative way of building collections is provided by the Collector, which helps you create new collections, modify or add to existing ones, or delete collections. It predates the librarian interface, and for most practical purposes the librarian interface should be used instead of the Collector. It is described in Section 3.4.</Text>
+<Text id="162">To harness the full power of Greenstone to build advanced collections, you will also need to read Chapter 2 of the <i>Developer's Guide</i>.</Text>
+<Section id="the_librarian_interface">
+<Title>
+<Text id="163">The librarian's interface</Text>
+</Title>
+<Content>
+<Text id="164">To convey the operation of Greenstone's librarian interface, we work through a simple example. Figures 4 to 15 are screen snapshots at various points during the interaction. This example uses documents in the Development Library Subset (DLS) collection, which is distributed with Greenstone. For expository purposes, the walkthrough takes the form of a single pass through the steps listed above. A more realistic pattern of use, however, is for users to switch back and forth through the various stages as the task proceeds.</Text>
+<Text id="165">The librarian interface can be run in one of four modes: Librarian Assistant, Librarian, Library Systems Specialist, and Expert. Modes control the level of detail within the interface, and can be changed through 'Preferences' in the 'File' menu. The walkthrough in this section assumes that the librarian interface is operating in the default mode, Librarian.</Text>
+<Subsection id="getting_started">
+<Title>
+<Text id="166">Getting started</Text>
+</Title>
+<Content>
+<Text id="167">Launch the librarian interface under Windows by selecting <i>Greenstone Digital Library</i> from the <i>Programs</i> section of the <i>Start</i> menu and choosing <i>Librarian Interface</i>. If you are using Unix, instead type</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<CodeLine>cd gli</CodeLine>
+<CodeLine>./gli.sh</CodeLine>
+<Text id="168">where <i>~/gsdl</i> is the directory containing your Greenstone system. To begin, you must either open an existing collection or start a new one. Figure 4 shows the user in the process of starting a new collection. She has selected <i>New</i> from the file menu and begun to fill out general information about the collectionâits title, the E-mail address of the person responsible for it, and a brief description of the contentâin the popup window. The collection title is a short phrase used throughout the digital library to identify the collection's content: existing collections have names like <i>Food and Nutrition Library</i>, <i>World Environmental Library</i>, and so on. When you type the title, the system assigns a unique mnemonic identifier, the collection ânameâ, for internal use (you can change it if you like). The E-mail address specifies the first point of contact for any problems encountered with the collection.</Text>
+<Text id="169">The brief description is a statement describing the principles that govern what is included in the collection. It appears under the heading <i>About this collection</i> on the collection's initial page.</Text>
+<Figure id="starting_a_new_collection">
+<Title>
+<Text id="170">Starting a new collection</Text>
+</Title>
+<File width="407" height="317" url="images/User_Fig_4.png"/>
+</Figure>
+<Figure id="exploring_the_local_file_space">
+<Title>
+<Text id="171">Exploring the local file space</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_5.png"/>
+</Figure>
+<Text id="172">At this point, the user decides whether to base the new collection on the same structure as an existing collection, or to build an entirely new kind of collection. In Figure 4 she has chosen to base it on the <i>Development Library Subset</i> collection. This implies that the âDLSâ metadata set which is used in this collection will be used for the new collection. (In fact, this metadata set has been used to build several Greenstone collections that share a common structure and organization but with different content, including the <i>Development Library Subset</i> and <i>Demo</i> collections delivered as samples with Greenstone.)</Text>
+<Text id="173">The DLS metadata set contains these items:</Text>
+<BulletList>
+<Bullet>
+<Text id="174">Title</Text>
+</Bullet>
+<Bullet>
+<Text id="175">Subject</Text>
+</Bullet>
+<Bullet>
+<Text id="176">Language</Text>
+</Bullet>
+<Bullet>
+<Text id="177">Organization</Text>
+</Bullet>
+<Bullet>
+<Text id="178">Keyword (i.e.âHowtoâ).</Text>
+</Bullet>
+</BulletList>
+<Text id="179">(There is, in addition, a metadata item called <i>AZList</i> which is used to determine which bucket of the alphabetic list contains the document's title, with values like âA-Bâ or âC-D-Eâ. This is used to give precise control over thedivisions in the list. For most other collections it is absent, and Greenstone assigns the buckets itself.)</Text>
+<Text id="180">If, instead, the user had chosen âNew Collectionâ at this point, she would have been asked to select what metadata sets should be used in the new collection. Three standard sets are pre-supplied: Dublin Core, the DLS metadata set mentioned above, and a set that comprises metadata elements extracted automatically by Greenstone from the documents in the collection. The user can also create new metadata sets using a popup panel activated through the âmetadataâ menu.</Text>
+<Text id="181">Several different metadata sets can be associated with the same collection; the system keeps them distinct (so that, for example, documents can have both a Dublin Core <i>Title</i> and a DLS <i>Title</i>). The different sets are clearly distinguished in the interface. Behind the scenes, metadata sets are represented in XML.</Text>
+</Content>
+</Subsection>
+<Subsection id="assembling_the_source_material">
+<Title>
+<Text id="182">Assembling the source material</Text>
+</Title>
+<Content>
+<Text id="183">After clicking the <i>OK</i> button on the ânew collectionâ popup, the remaining parts of the interface, which were grayed out before, become active. The <i>Gather</i> panel, selected by the eponymous tab near the top of Figure 4, is displayed initially. This allows the user to explore the local file space and existing collections, gathering up selected documents for the new collection. The panel is divided into two sections, the left for browsing existing structures and the right for the documents in the collection.</Text>
+<Text id="184">Operations available at this stage include:</Text>
+<BulletList>
+<Bullet>
+<Text id="185">Navigating the existing file structure hierarchy, and the one being created, in the usual way.</Text>
+</Bullet>
+<Bullet>
+<Text id="186">Dragging and dropping files into the new collection.</Text>
+</Bullet>
+<Bullet>
+<Text id="187">Multiple selection of files.</Text>
+</Bullet>
+<Bullet>
+<Text id="188">Dragging and dropping entire sub-hierarchies.</Text>
+</Bullet>
+<Bullet>
+<Text id="189">Deleting documents from the nascent collection.</Text>
+</Bullet>
+<Bullet>
+<Text id="190">Creating new sub-hierarchies within the collection.</Text>
+</Bullet>
+<Bullet>
+<Text id="191">Filtering the files that are visible, in both the local file system and the collection, based on predetermined groups or on standard file matching terms.</Text>
+</Bullet>
+<Bullet>
+<Text id="192">Invoking the appropriate program to display the contents of a selected file, by double-clicking it.</Text>
+</Bullet>
+</BulletList>
+<Text id="193">Care is taken to deal appropriately with name clashes when files of the same name in different parts of the computer's directory structure are copied into the same folder of the collection.</Text>
+<Text id="194">In Figure 5 the user is using the interactive file tree display to explore the local file system. At this stage, the collection on the right is empty; the user populates it by dragging and dropping files of interest from the left to the right panel. Such files are âcopiedâ rather than âmovedâ: so as not to disturb the original file system. The usual techniques for multiple selection, dragging and dropping, structuring the new collection by creating subdirectories (âfoldersâ), and deleting files from it by moving them to a trashcan, are all available.</Text>
+<Text id="195">Existing collections are represented by a subdirectory on the left called âGreenstone Collections,â which can be opened and explored like any other directory. However, the documents therein differ from ordinary files because they already have metadata attached, and this is preserved when they are moved into the new collection. Conflicts may arise because their metadata may have been assigned using a different metadata set from the one in use for the new collection, and the user must resolve these. In Figure 6 the user has selected some documents from an existing collection and dragged them into the new one. The popup window explains that the metadata element <i>Organization</i> cannot be automatically imported, and asks the user to either select a metadata set and press <i>Add</i> to add the metadata element to that set,<FootnoteRef id="1"/>or choose a metadata set, then an element, and press <i>Merge</i> to effectively rename the old metadata element to the new one by merging the two. Metadata in subsequent documents from the same collection will automatically be handled in the same way.</Text>
+<Text id="196">When large file sets are selected, dragged, and dropped into the new collection, the copying operation may take some timeâparticularly if metadata conversion is involved. To indicate progress, the interface shows which file is being copied and what percentage of files has been processed.</Text>
+<Text id="197">Special facilities are provided for dealing with large file sets. For example, the user can choose to filter the file tree to show only certain files, using a dropdown menu of file types displayed underneath the trees. In Figure 7, only the HTM and HTML files are being shown (and only these files will be copied by drag and drop).</Text>
+</Content>
+</Subsection>
+<Subsection id="enriching_the_documents">
+<Title>
+<Text id="198">Enriching the documents</Text>
+</Title>
+<Content>
+<Text id="199">The next phase in collection building is to enrich the documents by adding metadata. The <i>Enrich</i> tab brings up a new panel of information (Figure 8), which shows the document tree representing the collection on the left and on the right allows metadata to be added to individual documents, or groups of documents.</Text>
+<Text id="200">Documents that are copied during the first step come with any applicable metadata attached. If a document is part of a Greenstone collection, previously defined metadata is carried over to the new collection. Of course, this new collection may have a different metadata set, or perhaps just a subset of the defined metadata, and only metadata that pertains to the new collection's set is carried over. Resolution of such conflicts may require user intervention via a supplementary dialog (Figure 6). Any choices made are remembered for subsequent file copies.</Text>
+<Text id="201">The <i>Enrich</i> panel allows metadata values to be assigned to documents in the collection. For example, new values can be added to the set of existing values for an element. If the element's values have a hierarchical structure, the hierarchy can be extended in the same way.</Text>
+<Figure id="importing_existing_metadata">
+<Title>
+<Text id="202">Importing existing metadata</Text>
+</Title>
+<File width="407" height="317" url="images/User_Fig_6.png"/>
+</Figure>
+<Figure id="filtering_the_file_trees">
+<Title>
+<Text id="203">Filtering the file trees</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_7.png"/>
+</Figure>
+<Figure id="assigning_metadata_using_enrich_view">
+<Title>
+<Text id="204">Assigning metadata using <i>Enrich</i> view</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_8.png"/>
+</Figure>
+<Figure id="viewing_all_metadata_for_selected_files">
+<Title>
+<Text id="205">Viewing all metadata for selected files</Text>
+</Title>
+<File width="407" height="317" url="images/User_Fig_9.png"/>
+</Figure>
+<Text id="206">Metadata values can also be assigned to folders, in just the same way. Documents in these folders for which this metadata is unspecified inherit the metadata values. However, they can subsequently be overridden by supplying different ones for the document itself.</Text>
+<Text id="207">Operations at this stage include:</Text>
+<BulletList>
+<Bullet>
+<Text id="208">Assigning new and existing metadata values to documents.</Text>
+</Bullet>
+<Bullet>
+<Text id="209">Assigning metadata to an individual document.</Text>
+</Bullet>
+<Bullet>
+<Text id="210">Assigning metadata to a folder (this is inherited by all documentsin the folder, including those in nested folders).</Text>
+</Bullet>
+<Bullet>
+<Text id="211">Assigning hierarchical metadata, whose structure can be dynamically updated if required.</Text>
+</Bullet>
+<Bullet>
+<Text id="212">Editing or updating assigned metadata.</Text>
+</Bullet>
+<Bullet>
+<Text id="213">Reviewing the metadata assigned to a selection of files and directories.</Text>
+</Bullet>
+</BulletList>
+<Text id="214">For our walkthrough example, in Figure 8 the user has selected the folder <i>ec121e</i> and assigned âEC Courierâ as its <i>Organization</i> metadata. The buttons for updating and removing metadata become active depending on what selections have been made.</Text>
+<Text id="215">During the enrichment phase, or indeed at any other time, the user can choose to view all the metadata that has been assigned to documents in the collection. This is done by selecting a set of documents and choosing <i>Assigned Metadata</i> from the metadata sets menu, which brings up a popup window like that in Figure 9 that shows the metadata in spreadsheet form. For large collections it is useful to be able to view the metadata associated with certain document types only, and if the user has specified a file filter as mentioned above, only the selected documents are shown in the metadata display.</Text>
+<Text id="216">The panel in Figure 10 allows the user to edit metadata sets. Here, the user is looking at the <i>Subject</i> element of the DLS set. The values of this element form a hierarchy, and the user is examining, and perhaps changing, the list of values assigned to it. The same panel also allows you to change the âprofileâ for mapping elements of one metadata set to another. This profile is created when importing documents from collections that have pre-assigned metadata.</Text>
+<Figure id="editing_the_metadata_set">
+<Title>
+<Text id="217">Editing the metadata set</Text>
+</Title>
+<File width="407" height="317" url="images/User_Fig_10.png"/>
+</Figure>
+<Figure id="designing_the_collection">
+<Title>
+<Text id="218">Designing the collection</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_11.png"/>
+</Figure>
+<Figure id="specifying_which_plug-ins_to_use">
+<Title>
+<Text id="219">Specifying which plug-ins to use</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_12.png"/>
+</Figure>
+<Figure id="configuring_arguments_to_a_plug-in">
+<Title>
+<Text id="220">Configuring arguments to a plug-in</Text>
+</Title>
+<File width="407" height="317" url="images/User_Fig_13.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="designing_the_collection_1">
+<Title>
+<Text id="221">Designing the collection</Text>
+</Title>
+<Content>
+<Text id="222">The <i>Design</i> panel (Figures 11â13) allows one to specify the structure, organization, and presentation of the collection being created. As noted earlier, the result of this process is recorded in a âcollection configuration file,â which is Greenstone's way of expressing the facilities that a collection requires. This step involves a series of separate interaction screens, each dealing with one aspect of the collection design. In effect, it serves as a graphical equivalent to the usual process of editing the configuration file manually.</Text>
+<Text id="223">Operations include:</Text>
+<BulletList>
+<Bullet>
+<Text id="224">Reviewing and editing collection-level metadata such as title, author and public availability of the collection.</Text>
+</Bullet>
+<Bullet>
+<Text id="225">Defining what full-text indexes are to be built.</Text>
+</Bullet>
+<Bullet>
+<Text id="226">Creating sub-collections and having indexes built for them.</Text>
+</Bullet>
+<Bullet>
+<Text id="227">Adding or removing support for predefined interface languages.</Text>
+</Bullet>
+<Bullet>
+<Text id="228">Constructing a list of plug-ins to be used, and their arguments.</Text>
+</Bullet>
+<Bullet>
+<Text id="229">Presenting the list to the user for review and modification.</Text>
+</Bullet>
+<Bullet>
+<Text id="230">Configuring individual plug-ins.</Text>
+</Bullet>
+<Bullet>
+<Text id="231">Constructing a list of âclassifiers,â their arguments, assignment and configuration.</Text>
+</Bullet>
+<Bullet>
+<Text id="232">Assigning formatting strings to various controls within the collection, thus altering its appearance.</Text>
+</Bullet>
+<Bullet>
+<Text id="233">Reviewing the metadata sets, and their elements, used in the collection.</Text>
+</Bullet>
+</BulletList>
+<Text id="234">In Figure 11 the user has clicked the <i>Design</i> tab and is reviewing the general information about the collection, entered when the new collection was created. On the left are listed the various facets that the user can configure: General, Document Plug-ins, Search Types, Search Indexes, Partition Indexes, Cross-Collection Search, Browsing Classifiers, Format Features, Translate Text, Metadata Sets. Appearance and functionality varies between these. For example, clicking the <i>Plug-in</i> button brings up the screen shown in Figure 12, which allows you to add, remove or configure plug-ins, and change the order in which the plug-ins are applied to documents.</Text>
+<Text id="235">Plug-ins and classifiers have many different arguments or âoptionsâ that the user can supply. The dialog box in Figure 13 shows the user specifying arguments to some of the plug-ins. The grayed-out fields become active when the user adds the option by clicking the tick-box beside it. Because Greenstone is a continually growing open-source system, the number of options tends to increase as developers add new facilities. To help cope with this, Greenstone has a âplug-in informationâ utility program that lists the options available for each plug-in, and the librarian interface automatically invokes this to determine what options to show. This allows the interactive user interface to automatically keep pace with developments in the software.</Text>
+<Figure id="getting_ready_to_create_new_collection">
+<Title>
+<Text id="236">Getting ready to create new collection</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_14.png"/>
+</Figure>
+<Figure id="previewing_the_newly_built_collection">
+<Title>
+<Text id="237">Previewing the newly built collection</Text>
+</Title>
+<File width="407" height="291" url="images/User_Fig_15.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="building_the_collection">
+<Title>
+<Text id="238">Building the collection</Text>
+</Title>
+<Content>
+<Text id="239">The <i>Create</i> panel (Figure 14) is used to construct a collection based on the documents and assigned metadata. The brunt of this work is borne by the Greenstone code itself. The user controls this external process through a series of separate interaction screens, each dealing with the arguments provided to a certain stage of the creation process.</Text>
+<Text id="240">The user observes the building process though a window that shows not only the text output generated by Greenstone's importing and index-building scripts, but also progress bars that indicate the overall degree of completion of each script.</Text>
+<Text id="241">Figure 14 shows the <i>Create</i> view. At the top are shown some options that can be applied during the creation process. The user selects appropriate values for the options. This figure illustrates a popup âtool tipâ that is available throughout the interface to explain the function of each argument.</Text>
+<Text id="242">When satisfied with the arguments, the user clicks <i>Build Collection</i>. Greenstone continually prints text that indicates progress, and this is shown along with a more informative progress bar.</Text>
+</Content>
+</Subsection>
+<Subsection id="previewing">
+<Title>
+<Text id="243">Previewing</Text>
+</Title>
+<Content>
+<Text id="244">The <i>Preview Collection</i> button (Figure 14) is used to view the collection that has been built. Clicking this button launches a web browser showing the home page of the collection (Figure 15). In practice, previewing often shows up deficiencies in the collection design, or in the individual metadata values, and the user frequently returns to earlier stages to correct these. This button becomes active once the collection has been created. The newly created collection will also have been installed on your Greenstone home page as one of the regular collections.</Text>
+</Content>
+</Subsection>
+<Subsection id="help">
+<Title>
+<Text id="245">Help</Text>
+</Title>
+<Content>
+<Text id="246">On-line help is always available, and is invoked using the <i>Help</i> item at the right of the main menu bar at the top of each of the Figures. This opens up a hierarchically structured file of help text, and account is taken of the user's current context to highlight the section that is appropriate to the present stage of the interaction. Furthermore, as noted above, whenever the mouse is held still over any interactive object a small window pops up to give a textual âtool tip,â as illustrated near the bottom of Figure 14.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="librarian_interface_user_guide">
+<Title>
+<Text id="247">Librarian Interface user guide</Text>
+</Title>
+<Content>
+<Subsection id="starting_off">
+<Title>
+<Text id="248">Starting Off</Text>
+</Title>
+<Content>
+<Text id="249">This section covers how to create, load, save and delete collections.</Text>
+<Part id="creating_a_new_collection">
+<Title>
+<Text id="250">Creating a New Collection</Text>
+</Title>
+<Content>
+<Text id="251">To create a new collection, open the "File" menu and choose "New". Several fields need to be filled out -- but you can change their values later if you need to, in the design view.</Text>
+<Text id="252">"Collection title" is the text displayed at the top of your collection's home page. It can be any length.</Text>
+<Text id="253">"Description of content" should describe, in as much detail as possible, what the collection is about. Use the [Enter] key to break it into paragraphs.</Text>
+<Text id="254">Finally you must specify whether the new collection will have the same appearance and metadata sets as an existing collection, or whether to start a default "New Collection".</Text>
+<Text id="255">Click "OK" to create the collection. If you chose "New Collection" you are prompted for the metadata sets to use in it. You can choose more than one, and you can add others later.</Text>
+<Text id="256">Clicking "Cancel" returns you to the main screen immediately.</Text>
+</Content>
+</Part>
+<Part id="saving_the_collection">
+<Title>
+<Text id="257">Saving the Collection</Text>
+</Title>
+<Content>
+<Text id="258">Save your work regularly by opening the "File" menu and choosing "Save". Saving a collection is not the same as making it ready for use in Greenstone (see Producing Your Collection).</Text>
+<Text id="259">The Librarian Interface protects your work by saving it whenever you exit the program or load another collection.</Text>
+<Text id="260">Saved collections are written to a file named for the collection and with file extension ".col", located in a folder of the same name within your Greenstone installation's "collect" folder.</Text>
+</Content>
+</Part>
+<Part id="opening_an_existing_collection">
+<Title>
+<Text id="261">Opening an Existing Collection</Text>
+</Title>
+<Content>
+<Text id="262">To open an existing collection, choose "Open" from the "File" menu to get the Open Collection prompt. A list of your Greenstone collections appears. Select one to see its description, and click "Open" to load it. If you seek a collection that resides outside Greenstone's "collect" folder, click "Browse" for a file system browsing dialog.</Text>
+<Text id="263">In case more than one Greenstone Librarian Interface program is running concurrently, the relevant directories are "locked" to prevent interference. On opening a collection, a small temporary lock file is created in its folder. Before opening a collection, the Librarian Interface checks to ensure that no lock file already exists. You can tell whether a collection is locked by the colour of its icon: green for a normal collection, red for a locked one. However, when the Librarian Interface is exited prematurely the lock file is sometimes left in place. When you open such a collection, the Librarian asks if you want to "steal" control of it. Never steal a collection that someone else is currently working on.</Text>
+<Text id="264">When you open a collection that the Greenstone Librarian Interface did not create, you will be asked to select a metadata set (or sets). If none are selected, any existing metadata will be ignored. Otherwise, metadata will be imported just as it is when you drag in files with existing metadata. The process is described in the Importing Previously Assigned Metadata section.</Text>
+</Content>
+</Part>
+<Part id="deleting_collections">
+<Title>
+<Text id="265">Deleting Collections</Text>
+</Title>
+<Content>
+<Text id="266">To permanently delete collections from your Greenstone installation, choose "Delete..." from the "File" menu. A list of your Greenstone collections appears. Select one to see its description, then tick the box at the bottom of the dialog and click "Delete" to delete the collection. This action is irreversible, so check carefully that you no longer need the collection before proceeding!</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="downloading_files_from_the_internet">
+<Title>
+<Text id="267">Downloading Files From the Internet</Text>
+</Title>
+<Content>
+<Text id="268">The "Download" view helps you download resources from the internet. This section explains the Librarian Interface's mirroring process.</Text>
+<Part id="the_download_view">
+<Title>
+<Text id="269">The Download view</Text>
+</Title>
+<Content>
+<Text id="270">This section describes how to configure a download task and control the downloading process. Access the "Download" view by clicking its tab. The top half of the screen shows the downloading controls. The bottom half is initially empty, but will show a list of pending and completed downloading jobs.</Text>
+<Text id="271">Files are downloaded into a folder in the workspace called "Downloaded Files" (only present when mirroring is enabled), and can be used in all collections built with the Librarian Interface. Files in this area are named by their full web URL. A new folder is created for each host, followed by others for each part of the path. This ensures that each file is distinct.</Text>
+<Text id="272">Use the first of the download configuration controls, "Source URL", to enter the URL of a target resource. Use the "Download Depth" control to limit how many hyperlinks to follow when downloading: Set this to 0 to download a single web page; set it to 1 to download a page and all the pages it points to. The depth limit is ignored when downloading media other than html pages. Next, there are several checkbox controls which can be set to turn on the specified feature for a specific download. Once the configuration is set up, click "Download" to start the new download job. There are two other button controls: "Preferences", which links to the connection section of the Preferences where proxy settings can be edited; and "Clear Cache", which deletes all previously downloaded files.</Text>
+<Text id="273">The download list has an entry for each web page download. Each entry has a text region that gives details of the task along with a progress bar showing current activity. Three buttons appear to the left of each entry. "Pause" is used for pausing a currently downloading task. "View Log" opens a window showing the download log file. "Close" terminates the download and removes the task from the list.</Text>
+<Text id="274">The Preferences section describes how to establish an Internet connection via a proxy. If authentication is needed, the proxy server prompts for identification and password. The Librarian Interface does not store passwords between sessions.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="collecting_files_for_your_collection">
+<Title>
+<Text id="275">Collecting Files for Your Collection</Text>
+</Title>
+<Content>
+<Text id="276">Once you have a new collection you need to get some files into it. These may come from your ordinary file space, or from other Greenstone collections. Some may already have attached metadata. This section describes how to import files.</Text>
+<Part id="the_gather_view">
+<Title>
+<Text id="277">The Gather View</Text>
+</Title>
+<Content>
+<Text id="278">This section introduces the Gather area that you use to select what files to include in the collection you are building. The Librarian Interface starts with the Gather view. To return to this view later, click the "Gather" tab directly below the menu bar.</Text>
+<Text id="279">The two large areas titled "Workspace" and "Collection" are used to move files into your collection. They contain "file trees", graphical structures that represent files and folders.</Text>
+<Text id="280">Select an item in the tree by clicking it. (There are other ways; see below.) Double-click a folder, or single-click the switch symbol beside it, to expand (or collapse) its contents. Double-click a file to open it using its associated application program (see File Associations).</Text>
+<Text id="281">The Workspace file tree shows the sources of data available to the Librarian Interface -- the local file system (including disk and CD-ROM drives), the contents of existing Greenstone collections, and the cache of downloaded files. You can copy and view these files but you cannot move, delete, or edit them, with the exception of the downloaded files, which can be deleted. Navigate this space to find the files you want to include in the collection.</Text>
+<Text id="282">The Collection file tree represents the contents of the collection so far. Initially, it is empty.</Text>
+<Text id="283">You can resize the spaces by mousing over the grey bar that separates the trees (the shape of the pointer changes) and dragging.</Text>
+<Text id="284">At the bottom of the window is a status area that shows the progress of actions involving files (copying, moving and deleting). These can take some time to complete. The "Stop" button stops any action that is currently in progress.</Text>
+<Text id="285">Two large buttons occupy the lower right corner of the screen. "New Folder", with a picture of a folder, creates new folders (see Creating folders). "Delete", with a garbage can, removes files. Clicking the Delete button will remove any selected files from the Collection file tree. Alternatively, files can be deleted by dragging them onto the Delete button.</Text>
+<Text id="286">To select several sequential items, select the first and then hold down [Shift] and click on the last -- the selection will encompass all intervening items. Select non-sequential files by holding down [Ctrl] while clicking. Use these two methods together to select groups of non-adjacent items.</Text>
+<Text id="287">Certain folders -- such as the one containing your own web pages -- sometimes have special significance. The Librarian Interface can map such folders to the first level of the file tree. To do this, right-click the desired folder. Select "Create Shortcut", and enter a name for the folder. To remove an item, right-click the mapped folder and select "Remove Shortcut".</Text>
+</Content>
+</Part>
+<Part id="creating_folders">
+<Title>
+<Text id="288">Creating Folders</Text>
+</Title>
+<Content>
+<Text id="289">Use folders in the Collection file tree to group files together and make them easier to find. Folders can be placed inside folders. There is virtually no limit to how many folders you can have or how deeply they can be nested.</Text>
+<Text id="290">To create a new folder, optionally select an existing folder in the Collection Tree and click the New Folder button. The new folder appears within the selected one, or at the top level if none is selected. You are prompted for the folder's name (default "New Folder").</Text>
+<Text id="291">Folders can also be created by right-clicking over a folder, choosing "New Folder" and proceeding as above.</Text>
+</Content>
+</Part>
+<Part id="adding_files">
+<Title>
+<Text id="292">Adding Files</Text>
+</Title>
+<Content>
+<Text id="293">Files can be copied into the collection by dragging and dropping. The mouse pointer becomes a ghost of the selected item (or, if more than one is selected, the number of them). Drop the selection into the Collection Tree to copy the files there (if the source was the Workspace Tree) or move them around within the collection (if the source was the Collection Tree).</Text>
+<Text id="294">When copying multiple files, they are all placed in the target folder at the same level, irrespective of the folder structure they occupied originally. When you copy a second file with the same name into the same folder, you are asked whether to overwrite the first one. Respond "No" and the file will not be copied, but the others will be. To cancel all remaining copy actions, click the "stop" button.</Text>
+<Text id="295">Only the "highest" items in a selection are moved. A folder is higher than its children. You cannot select files within a folder and also the folder itself.</Text>
+<Text id="296">When you add a file, the Librarian Interface searches through the source folders for auxiliary files containing metadata previously assigned to the added file and, if it finds one, begins to import this metadata. As the operation proceeds, you may be prompted (perhaps several times) for extra information to match the imported metadata to the metadata sets in your collection. This process involves many different prompts, described in the Importing Previously Assigned Metadata section. For a more detailed explanation of associating metadata with files read Chapter 2 of the Greenstone Developer's Guide -- Getting the most out of your documents.</Text>
+</Content>
+</Part>
+<Part id="removing_files">
+<Title>
+<Text id="297">Removing Files</Text>
+</Title>
+<Content>
+<Text id="298">There are several methods for removing files and folders. You must first indicate what items to remove by selecting one or more files and folders as described in The Gather View.</Text>
+<Text id="299">Once files have been selected, click the "delete" button to remove them, or press the [Delete] key on your keyboard, or drag them from the collection to the delete button and drop them there.</Text>
+</Content>
+</Part>
+<Part id="filtering_the_tree">
+<Title>
+<Text id="300">Filtering the Tree</Text>
+</Title>
+<Content>
+<Text id="301">"Filtering" the collection tree allows you to narrow down the search for particular files.</Text>
+<Text id="302">The "Show Files" pull-down menu underneath each tree shows a list of predefined filters, such as "Images". Choosing this temporarily hides all other files in the tree. To restore the tree, change the filter back to "All Files". These operations do not alter the collection, nor do they affect the folders in the tree.</Text>
+<Text id="303">You can specify a custom filter by typing in a pattern to match files against (Librarian Systems Specialist and Expert modes only). Use standard file system abbreviations such as "*.*" or "*.doc" ("*" matches any characters).</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="enriching_the_collection_with_metadata">
+<Title>
+<Text id="304">Enriching the Collection with Metadata</Text>
+</Title>
+<Content>
+<Text id="305">Having gathered several files into the collection, now enrich them with additional information called "metadata". This section explains how metadata is created, edited, assigned and retrieved, and how to use external metadata sources (also see Chapter 2 of the Greenstone Developer's Guide -- Getting the most out of your documents).</Text>
+<Part id="the_enrich_view">
+<Title>
+<Text id="306">The Enrich View</Text>
+</Title>
+<Content>
+<Text id="307">Use the Enrich view to assign metadata to the documents in the collection. Metadata is data about data -- typically title, author, creation date, and so on. Each metadata item has two parts: "element" tells what kind of item it is (such as author), and "value" gives the value of that metadata element (such as the author's name).</Text>
+<Text id="308">On the left of the "Enrich" view is the Collection Tree. To the right is the Metadata Table, which shows metadata for any selected files or folders in the Collection Tree. Columns are named in grey at the top, and can be resized by dragging the separating line. If several files are selected, black text indicates that the value is common to all of the selected files, while grey text indicates that it is not. Black values may be updated or removed, while grey ones can be removed from those that have it, or appended to the others.</Text>
+<Text id="309">A folder icon may appear beside some metadata entries. This indicates that the values are inherited from a parent (or ancestor) folder. Inherited metadata cannot be edited or removed, only appended to or overwritten. Click on the folder icon to go immediately to the folder where the metadata is assigned.</Text>
+<Text id="310">Clicking on a metadata element in the table will display the existing values for that element in the "Existing values for..." area below the table. The Value Tree expands and collapses. Usually it is a list that shows all values entered previously for the selected element. Clicking an entry automatically places it into the value field. Conversely, typing in the text field selects the Value Tree entry that starts with the characters you have typed. Pressing [Tab] auto-completes the typing with the selected value.</Text>
+<Text id="311">Metadata values can be organised into a hierarchy. This is shown in the Value Tree using folders for internal levels. Hierarchical values can be entered using the character "|" to separate the levels. For example, "Cards|Red|Diamonds|Seven" might be used in a hierarchy that represents a pack of playing cards. This enables values to be grouped together. Groups can also be assigned as metadata to files.</Text>
+<Text id="312">Greenstone extracts metadata automatically from documents into a metadata set whose elements are prefixed by "ex.". This has no value tree and cannot be edited.</Text>
+</Content>
+</Part>
+<Part id="selecting_metadata_sets">
+<Title>
+<Text id="313">Selecting Metadata Sets</Text>
+</Title>
+<Content>
+<Text id="314">Sets of predefined metadata elements are known as "metadata sets". An example is the Dublin Core metadata set. When you add a metadata set to your collection, its elements become available for selection. You can have more than one set; to prevent name clashes a short identifier that identifies the metadata set is pre-pended to the element name. For instance the Dublin Core element Creator becomes "dc.Creator". Metadata sets are stored in the Librarian Interface's metadata folder and have the suffix ".mds".</Text>
+<Text id="315">To control the metadata sets used in a collection, use the "Metadata Sets" entry on the Design view.</Text>
+</Content>
+</Part>
+<Part id="appending_new_metadata">
+<Title>
+<Text id="316">Appending New Metadata</Text>
+</Title>
+<Content>
+<Text id="317">We now add a metadata item -- both element and value -- to a file. First select the file from the Collection file tree on the left. The action causes any metadata previously assigned to this file to appear in the table at the right.</Text>
+<Text id="318">Next select the metadata element you want to add by clicking its row in the table.</Text>
+<Text id="319">Type the value into the value field. Use the "|" character to add structure, as described in The Enrich View. Pressing the [Up] or [Down] arrow keys will save the metadata value and move the selection appropriately. Pressing [Enter] will save the metadata value and create a new empty entry for the metadata element, allowing you to assign multiple values to a metadata element.</Text>
+<Text id="320">You can also add metadata to a folder, or to several multiply selected files at once. It is added to all files within the folder or selection, and to child folders. Keep in mind that if you assign metadata to a folder, any new files in it automatically inherit the folder's values.</Text>
+</Content>
+</Part>
+<Part id="adding_previously_defined_metadata">
+<Title>
+<Text id="321">Adding Previously Defined Metadata</Text>
+</Title>
+<Content>
+<Text id="322">To add metadata that has an existing value, first select the file, then select the required value from the value tree, expanding hierarchy folders as necessary. The value of the selected entry automatically appears in the Value field (alternatively, use the value tree's auto-select and auto-complete features).</Text>
+<Text id="323">The process of adding metadata with already-existing values to folders or multiple files is just the same.</Text>
+</Content>
+</Part>
+<Part id="editing_or_removing_metadata">
+<Title>
+<Text id="324">Editing or Removing Metadata</Text>
+</Title>
+<Content>
+<Text id="325">To edit or remove a piece of metadata, first select the appropriate file, and then the metadata value from the table. Edit the value field, deleting all text if you wish to remove the metadata.</Text>
+<Text id="326">The process is the same when updating a folder with child folders or multiple files, but you can only update metadata that is common to all files/folders selected.</Text>
+<Text id="327">The value tree shows all currently assigned values as well as previous values for the current session, so changed or deleted values will remain in the tree. Closing the collection and then re-opening it will remove the values which are no longer assigned.</Text>
+</Content>
+</Part>
+<Part id="reviewing_assigned_metadata">
+<Title>
+<Text id="328">Reviewing Assigned Metadata</Text>
+</Title>
+<Content>
+<Text id="329">Sometimes you need to see the metadata assigned to many or all files at once -- for instance, to determine how many files are left to work on, or to get some idea of the spread of dates.</Text>
+<Text id="330">Select the files you wish to examine, then right-click and choose "Assigned Metadata...". A window called "All Metadata", dominated by a large table with many columns, appears. The first column shows file names; the rows show all metadata values assigned to those files.</Text>
+<Text id="331">Drawing the table can take some time if many files are selected. You can continue to use the Librarian Interface while the "All Metadata" window is open.</Text>
+<Text id="332">When it gets too large, you can filter the "All Metadata" table by applying filters to the columns. As new filters are added, only those rows that match them remain visible. To set, modify or clear a filter, click on the "funnel" icon at the top of a column. You are prompted for information about the filter. Once a filter is set, the column header changes colour.</Text>
+<Text id="333">The prompt has a "Simple" and an "Advanced" tab. The Simple version filters columns so that they only show rows that contain a certain metadata value ("*" matches all values). You can select metadata values from the pull-down list. The Advanced version allows different matching operations: must start with, does not contain, alphabetically less than and is equal to. The value to be matched can be edited to be any string (including "*"), and you can choose whether the matching should be case insensitive. Finally, you can specify a second matching condition that you can use to specify a range of values (by selecting AND) or alternative values (by selecting OR). Below this area is a box that allows you to change the sort order (ascending or descending). Once you have finished, click "Set Filter" to apply the new filter to the column. Click "Clear Filter" to remove a current filter. Note that the filter details are retained even when the filter is cleared.</Text>
+<Text id="334">For example, to sort the "All Metadata" table, choose a column, select the default filter setting (a Simple filter on "*"), and choose ascending or descending ordering.</Text>
+</Content>
+</Part>
+<Part id="importing_previously_assigned_metadata">
+<Title>
+<Text id="335">Importing Previously Assigned Metadata</Text>
+</Title>
+<Content>
+<Text id="336">This section describes how to import previously assigned metadata: metadata assigned to documents before they were added to the collection.</Text>
+<Text id="337">If metadata in a form recognized by the Librarian Interface has been previously assigned to a file -- for example, when you choose documents from an existing Greenstone collection -- it is imported automatically when you add the file. To do this, the metadata must be mapped to the metadata sets available in the collection.</Text>
+<Text id="338">The Librarian Interface prompts for the necessary information. The prompt gives brief instructions and then shows the name of the metadata element that is being imported, just as it appears in the source file. This field cannot be edited or changed. Next you choose what metadata set the new element should map to, and then the appropriate metadata element in that set. The system automatically selects the closest match, in terms of set and element, for the new metadata.</Text>
+<Text id="339">Having checked the mapping, you can choose "Add" to add the new metadata element to the chosen metadata set. (This is only enabled if there is no element of the same name within the chosen set.) "Merge" maps the new element to the one chosen by the user. Finally, "Ignore" does not import any metadata with this element name. Once you have specified how to import a certain piece of metadata, the mapping information is retained for the collection's lifetime.</Text>
+<Text id="340">For details on the metadata.xml files which Greenstone uses to store the metadata, see Chapter 2 of the Greenstone Developer's Guide -- Getting the most out of your documents.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="designing_your_collection_appearance">
+<Title>
+<Text id="341">Designing Your Collection's Appearance</Text>
+</Title>
+<Content>
+<Text id="342">Once your files are marked up with metadata, you next decide how it should appear to users as a Greenstone collection. What kind of information is searchable? What ways are provided to browse through the documents? What languages are supported? Where do the buttons appear on the page? These things can be customized; this section describes how to do it.</Text>
+<Part id="the_design_view">
+<Title>
+<Text id="343">The Design View</Text>
+</Title>
+<Content>
+<Text id="344">This section introduces you to the design view and explains how to navigate between the various views within this pane.</Text>
+<Text id="345">With the Librarian Interface, you can configure how the collection appears to the user. The configuration options are divided into different sections, each associated with a particular stage of navigating or presenting information.</Text>
+<Text id="346">On the left is a list of different views, and on the right are the controls associated with the current one. To change to a different view, click its name in the list.</Text>
+<Text id="347">To understand the stages and terms involved in designing a collection, first read Chapters 1 and 2 of the Greenstone Developer's Guide.</Text>
+</Content>
+</Part>
+<Part id="general">
+<Title>
+<Text id="348">General</Text>
+</Title>
+<Content>
+<Text id="349">This section explains how to review and alter the general settings associated with your collection. First, under "Design Sections", click "General".</Text>
+<Text id="350">Here the values provided during collection creation can be modified.</Text>
+<Text id="351">First are the contact emails of the collection's creator and maintainer. The following field allows you to change the collection title. The folder that the collection is stored in is shown next, but this cannot be edited. The next one specifies (in the form of a URL) the icon to show at the top left of the collection's "About" page, and the next is the icon used in the Greenstone library page to link to the collection. Then, a checkbox controls whether the collection should be publicly accessible. Finally comes the "Collection Description" text area as described in Creating A New Collection.</Text>
+</Content>
+</Part>
+<Part id="document_plugins">
+<Title>
+<Text id="352">Document Plugins</Text>
+</Title>
+<Content>
+<Text id="353">This section describes how to configure the document plugins the collection uses. It explains how you specify what plugins to use, what parameters to pass to them, and in what order they occur. Under "Design Sections", click "Document Plugins".</Text>
+<Text id="354">To add a plugin, select it using the "Select plugin to add" pull-down list near the bottom and then click "Add Plugin". A window appears entitled "Configuring Arguments"; it is described later. Once you have configured the new plugin, it is added to the end of the "Currently Assigned Plugins" list. Note that, except for UnknownPlug, each plugin may only occur once in the list.</Text>
+<Text id="355">To remove a plugin, select it in the list and click "Remove Plugin".</Text>
+<Text id="356">Plugins are configured by providing arguments. To alter them, select the plugin from the list and click "Configure Plugin" (or double-click the plugin). A "Configuring Arguments" dialog appears with various controls for specifying arguments.</Text>
+<Text id="357">There are different kinds of controls. Some are checkboxes, and clicking one adds the appropriate option to the plugin. Others are text strings, with a checkbox and a text field. Click the box to enable the argument, then type appropriate text (regular expression, file path etc) in the box. Others are pull-down menus from which you can select from a given set of values. To learn what an argument does, let the mouse hover over its name for a moment and a description will appear.</Text>
+<Text id="358">When you have changed the configuration, click "OK" to commit the changes and close the dialog, or "Cancel" to close the dialog without changing any plugin arguments.</Text>
+<Text id="359">The plugins in the list are executed in order, and the ordering is sometimes important. The order of the plugins can be changed in Library Systems Specialist and Expert modes only (see Preferences).</Text>
+</Content>
+</Part>
+<Part id="search_types">
+<Title>
+<Text id="360">Search Types</Text>
+</Title>
+<Content>
+<Text id="361">This section explains how to modify a new design feature in Greenstone, Search Types, which allow fielded searching. The search types specify what kind of search interface should be provided: form, for fielded searching, and/or plain for regular searching. Under "Design Sections", click "Search Types".</Text>
+<Text id="362">When you enter the Search Types view, first check "Enable Advanced Searches", which activates the other controls. This changes the collection to use an indexing mechanism that allows fielded searching. Index specification is slightly different in this mode. (When switching between standard and advanced searching, the GLI does its best to convert the index specification, but may not get it completely right.)</Text>
+<Text id="363">To add a search type, select it from the "Search Types" list and click "Add Search Type". Each type can only appear in the list once. The first search type will be the default, and will appear on the search page of the built collection. Any others will be selectable from the preferences page.</Text>
+<Text id="364">To remove a search type, select it from the "Currently Assigned Search Types" list and click "Remove Search Type". The list must contain at least one search type.</Text>
+</Content>
+</Part>
+<Part id="search_indexes">
+<Title>
+<Text id="365">Search Indexes</Text>
+</Title>
+<Content>
+<Text id="366">Indexes specify what parts of the collection are searchable. This section explains how to add and remove indexes, and set a default index. Under "Design Sections", click "Search Indexes".</Text>
+<Text id="367">To add an index, type a name for it into the "Index Name" field. Select which of the possible information sources to index by clicking the checkboxes beside them. The list shows all the assigned metadata elements, as well the full text. Having selected the data sources, choose the granularity of the index, using the "At the level" menu. Once these details are complete, "Add Index" becomes active (unless there is an existing index with the same settings). Click it to add the new index.</Text>
+<Text id="368">To edit an index, select it and change the index details, then click "Replace Index".</Text>
+<Text id="369">To remove an index, select it from the list of assigned indexes and click "Remove Index".</Text>
+<Text id="370">To create an index covering text and all metadata, click "Add All".</Text>
+<Text id="371">The default index, the one used on the collection's search page, is tagged with "[Default Index]" in the "Assigned Indexes" list. To set it, select an index from the list and click "Set Default".</Text>
+<Text id="372">If advanced searching is enabled (via the Search Types view), the index controls are different. There is a new pseudo-data source "allfields" which provides searching across all specified indexes at once. Levels are not assigned to a specific index, but apply across all indexes: thus indexes and levels are added separately. "Add All" creates a separate index for each metadata field in this mode.</Text>
+<Text id="373">The name of each index will default to the source name. To change the name, select an index, change its details, and click "Replace Index".</Text>
+</Content>
+</Part>
+<Part id="partition_indexes">
+<Title>
+<Text id="374">Partition Indexes</Text>
+</Title>
+<Content>
+<Text id="375">Indexes are built on particular text or metadata sources. The search space can be further controlled by partitioning the index, either by language or by a predetermined filter. This section describes how to do this. Under "Design Sections", click "Partition Indexes".</Text>
+<Text id="376">The "Partition Indexes" view has three tabs; "Define Filters", "Assign Partitions" and "Assign Languages". To learn more about partitions read about subcollections and subindexes in Chapter 2 of the Greenstone Developer's Guide.</Text>
+<Text id="377">The Partition Indexes screen is only enables in Library Systems Specialist and Expert modes (see Preferences). Note that the total number of partitions generated is a combination of all indexes, subcollection filters and languages chosen. Two indexes with two subcollection filters in two languages would yield eight index partitions.</Text>
+</Content>
+</Part>
+<Part id="define_filters">
+<Title>
+<Text id="378">Define Filters</Text>
+</Title>
+<Content>
+<Text id="379">Filters allow you to group together into a subcollection all documents in an index for which a metadata value matches a given pattern.</Text>
+<Text id="380">To create a filter, click the "Define Filters" tab and enter a name for the new filter into the "Subcollection filter name:" field. Next choose a document attribute to match against, either a metadata element or the name of the file in question. Enter a regular expression to use during the matching. You can toggle between "Including" documents that match the filter, or "Excluding" them. Finally, you can specify any of the standard PERL regular expression flags to use when matching (e.g. "i" for case-insensitive matching). Finally, click "Add Filter" to add the filter to the "Defined Subcollection Filters" list.</Text>
+<Text id="381">To remove a filter, select it from the list and click "Remove Filter".</Text>
+<Text id="382">To alter a filter, select it from the list, change any of the values that appear in the editing controls and click "Replace Filter" to commit the changes.</Text>
+</Content>
+</Part>
+<Part id="assign_partitions">
+<Title>
+<Text id="383">Assign Partitions</Text>
+</Title>
+<Content>
+<Text id="384">Having defined a subcollection filter, use the "Assign Partitions" tab to build indexes for it (or for a group of filters). Select the desired filter (or filters) from the "Defined Subcollection Filters" list, enter a name for your partition in the "Partition Name" field, and click "Add Partition".</Text>
+<Text id="385">To remove a partition, select it from the list and click "Remove Partition".</Text>
+<Text id="386">To make a partition the default one, select it from the list and click "Set Default".</Text>
+</Content>
+</Part>
+<Part id="assign_languages">
+<Title>
+<Text id="387">Assign Languages</Text>
+</Title>
+<Content>
+<Text id="388">This section details how to restrict search indexes to particular languages. You do this by generating a partition using the "Assign Languages" tab of the "Partition Indexes" view.</Text>
+<Text id="389">To add a new language to partition by, use the "Assign Languages" tab to build an index for it. Select the desired language from the "Language to add" pull-down list and click "Add Language".</Text>
+<Text id="390">To remove a language, select it from the "Language Selection" list and click "Remove Language".</Text>
+<Text id="391">To set the default language, select it from the list and click "Set Default".</Text>
+</Content>
+</Part>
+<Part id="cross-collection_search">
+<Title>
+<Text id="392">Cross-Collection Search</Text>
+</Title>
+<Content>
+<Text id="393">Greenstone can search across several different collections as though they were one. This is done by specifying a list of other collections to be searched along with the current one. Under "Design Sections", click "Cross-Collection Search".</Text>
+<Text id="394">The Cross-Collection Search view shows a checklist of available collections. The current collection is ticked and cannot be deselected. To add another collection to be searched in parallel, click it in the list (click again to remove it). If only one collection is selected, there is no cross-collection searching.</Text>
+<Text id="395">If the individual collections do not have the same indexes (including subcollection partitions and language partitions) as each other, cross-collection searching will not work properly. The user will only be able to search using indexes common to all collections.</Text>
+<Text id="396">For further details, see Chapter 1 of the Greenstone Developer's Guide.</Text>
+</Content>
+</Part>
+<Part id="browsing_classifiers">
+<Title>
+<Text id="397">Browsing Classifiers</Text>
+</Title>
+<Content>
+<Text id="398">This section explains how to assign "classifiers", which are used for browsing, to the collection. Under "Design Sections", click "Browsing Classifiers".</Text>
+<Text id="399">To add a classifier, select it using the "Select classifier to add" pull-down list near the bottom and then click "Add Classifier". A window appears entitled "Configuring Arguments"; instructions for this dialog are just the same as for plugins (see Document Plugins). Once you have configured the new classifier, it is added to the end of the "Currently Assigned Classifiers" list.</Text>
+<Text id="400">To remove a classifier, select it from the list and click "Remove Classifier".</Text>
+<Text id="401">To change the arguments a classifier, select it from the list and click "Configure Classifier" (or double-click on the classifier in the list).</Text>
+<Text id="402">The ordering of classifiers in the collection's navigation bar is reflected in their order here. To change it, select the classifier you want to move and click "Move Up" or "Move Down".</Text>
+<Text id="403">For further information on classifiers read Chapter 2, Greenstone Developer's Guide -- Getting the most out of your documents.</Text>
+</Content>
+</Part>
+<Part id="format_features">
+<Title>
+<Text id="404">Format Features</Text>
+</Title>
+<Content>
+<Text id="405">The web pages you see when using Greenstone are not pre-stored but are generated 'on the fly' as they are needed. Format commands are used to change the appearance of these generated pages. They affect such things as where buttons appear when a document is shown, and what links are displayed by the DateList classifier. Format commands are not easy to develop, and you should read Chapter 2 of the Greenstone Developer's Guide. This section discusses the format settings, and how the Librarian Interface gives access to them. Under "Design Sections", click "Format Features".</Text>
+<Text id="406">You can apply a format command to anything in the "Choose Feature" pull-down list, which includes each classifier and a predefined list of features. When you select a feature, there are two types of control. Some features are simply enabled or disabled, and this is controlled by a checkbox. Others require a format string to be specified. For these there is a pull-down list ("Affected Component") for selecting which part of the feature the string applies to (if necessary), a text area ("HTML Format String") for entering the string, and a selection of predefined "Variables". To insert a variable into the current position in the format string, select it from the pull-down list and click "Insert".</Text>
+<Text id="407">You can specify a default format for a particular component by selecting the blank feature. This format is then applied to all applicable features unless otherwise specified.</Text>
+<Text id="408">To add a new format command, fill out the information as explained above and click "Add Format". The new format command appears in the list of "Currently Assigned Format Commands". Only one format command can be assigned to each feature/component combination.</Text>
+<Text id="409">To remove a format command, select it from the list and click "Remove Format".</Text>
+<Text id="410">To change a format command, select it from the list, modify the settings, and click "Replace Format".</Text>
+<Text id="411">For more information about variables and the feature components, read Chapter 2 of the Greenstone Developer's Guide.</Text>
+<Text id="412">If the "Allow Extended Options" checkbox is ticked, some advanced formatting options are enabled. The list of features that can be formatted is changed slightly, and more variables are available to be used in the format command, providing greater control over the page layout.</Text>
+</Content>
+</Part>
+<Part id="translate_text">
+<Title>
+<Text id="413">Translate Text</Text>
+</Title>
+<Content>
+<Text id="414">This section describes the translation view, where you can define language-specific text fragments for parts of the collection's interface. Under "Design Sections", click "Translate Text".</Text>
+<Text id="415">First choose an entry from the "Features" list. The language-specific strings associated with this feature appear below. Use the "Language of translation" pull-down list to select the target language, and type the translated text into the text area, referring to the "Initial Text Fragment" if necessary. Click "Add Translation" when finished.</Text>
+<Text id="416">To remove an existing translation, select it in the "Assigned Translations" table and click "Remove Translation".</Text>
+<Text id="417">To edit a translation, select it, edit it in the "Translated Text" text area, and click "Replace Translation".</Text>
+</Content>
+</Part>
+<Part id="metadata_sets">
+<Title>
+<Text id="418">Metadata Sets</Text>
+</Title>
+<Content>
+<Text id="419">This section explains the metadata set review panel. Under "Design Sections", click "Metadata Sets".</Text>
+<Text id="420">This view is used to review the metadata sets that the collection uses, and the elements that are available within each set. Choose from the list of "Available Metadata Sets" in order to see details of their elements.</Text>
+<Text id="421">To use another metadata set with the loaded collection, click "Add Metadata Set" and select the metadata set file (.mds) for the new metadata set.</Text>
+<Text id="422">Editing metadata sets is done with the Greenstone Editor for Metadata Sets (GEMS). Clicking the "Edit Metadata Set" button provides information on how to run the GEMS.</Text>
+<Text id="423">If you no longer need a metadata set, select it and press "Remove Metadata Set" to remove it. If you have assigned any metadata to elements in the removed set you will be asked how to deal with this metadata when you next open the collection.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="producing_your_collection">
+<Title>
+<Text id="424">Producing Your Collection</Text>
+</Title>
+<Content>
+<Text id="425">Having collected the documents for the collection, annotated them with metadata, and designed how the collection will appear, you can now produce the collection using Greenstone. This section explains how.</Text>
+<Part id="the_create_view">
+<Title>
+<Text id="426">The Create View</Text>
+</Title>
+<Content>
+<Text id="427">The Create view is used to create the collection by running Greenstone collection-building scripts on the information you have provided. Clicking "Build Collection" initiates the collection building process. The time this takes depends on the size of the collection and the number of indexes being created (for huge collections it can be hours). A progress bar indicates how much of the process has been completed. To cancel the process at any time, click "Cancel Build".</Text>
+<Text id="428">Once the collection has successfully built, clicking "Preview Collection" will launch a web browser showing the home page of the collection.</Text>
+<Text id="429">In Expert mode, you can use the "Message Log" entry at the left to review previous attempts to build the collection, whether successful or not. Select the log you want by clicking on the desired date in the "Log History" list.</Text>
+</Content>
+</Part>
+<Part id="import_and_build_settings">
+<Title>
+<Text id="430">Import and Build Settings</Text>
+</Title>
+<Content>
+<Text id="431">This section explains how to access the various import and build settings. For more information of importing and building read Chapter 1 of the Greenstone Developer's Guide -- Understanding the collection-building process.</Text>
+<Text id="432">Controlling the various settings is done in a similar way to the "Configuring Arguments" window described in the Document Plugins section. Some fields require numeric arguments, and you can either type these in or use the up and down arrows to increase or decrease the current value (in some cases, the interface restricts the range you can enter). Others are enabled by clicking a checkbox (click again to disable).</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="miscellaneous">
+<Title>
+<Text id="433">Miscellaneous</Text>
+</Title>
+<Content>
+<Text id="434">This section describes features of the Librarian Interface that are not associated with any particular view.</Text>
+<Part id="preferences">
+<Title>
+<Text id="435">Preferences</Text>
+</Title>
+<Content>
+<Text id="436">This section explains the preferences dialog, accessed by opening "File" -&gt; "Preferences".</Text>
+<Text id="437">The first "General" option is a text field for entering your e-mail address. This will be used for the "creator" and "maintainer" collection metadata items. The next option is a pull-down list of the languages in which the Librarian Interface can be presented. If you change the dictionary by choosing one from the list, you must restart the Librarian Interface in order to load the new language strings from the dictionary.</Text>
+<Text id="438">If "View Extracted Metadata" is checked, the various controls dealing with metadata always show all metadata that has been extracted automatically from documents. Deselecting it hides this metadata (although it is still available during collection design, and within the final Greenstone collection). If "Show file sizes" is checked, the file size is shown next to each file in the Workspace and Collection file trees in the Gather and Enrich views.</Text>
+<Text id="439">The "Mode" panel is used to control the level of detail within the interface. At its lowest setting, "Library Assistant", the design view is disabled, arguments requiring regular expressions are hidden and the collection building produces a minimal log of events. In contrast the highest setting, "Expert", provides access to all of the features of design, including plugin positioning and regular expression arguments, and also allows the full output from the collection building to be recorded in the logs. To change or review modes, click the radio button next to the mode you are interested in. You can quickly review what mode you are in by looking at the Librarian Interface's title bar.</Text>
+<Text id="440">The Librarian Interface can support different workflows by determining which of the various view tabs are visible. Use the "Workflow" tab to customise what views are available by checking the boxes next to the views that you want to be available. Alternatively, use the pull-down list at the bottom to select predetermined configurations. Closing the preferences dialog establishes these workflow settings. These settings are stored with the collection, not in the Librarian Interface configuration file.</Text>
+<Text id="441">The "Connection" tab lets you alter the path to the locally-running Greenstone library server, which is used when Previewing collections. It also lets you set proxy information for connecting to the Internet (e.g. when downloading files; see the Downloading Files From the Internet section for details). Check the box to enable proxy connection and supply details of the proxy host address and port number. The proxy connection is established when you close the Preferences dialog.</Text>
+<Text id="442">During the course of a session the Librarian Interface may give warning messages which inform you of possibly unforeseen consequences of an action. You can disable the messages by checking the "Do not show this warning again" box. You can re-enable warning messages using the "Warnings" tab. Check the box next to warning messages you want to see again.</Text>
+</Content>
+</Part>
+<Part id="file_associations">
+<Title>
+<Text id="443">File Associations</Text>
+</Title>
+<Content>
+<Text id="444">The Librarian Interface uses particular application programs to open particular file types. To alter file associations open the "File" menu and click "File Associations...".</Text>
+<Text id="445">To add an association, select the target file extension from the pull-down list, or type in a new extension (do not include the "."). Next either type command that launches the desired application in the appropriate field, or choose the application from the "Browse" dialog. "%1" can be used in the launch command to insert the name of the file being opened. Once these are filled out, "Add" is enabled and can be clicked to add the association.</Text>
+<Text id="446">To edit an association, select an existing file extension. Any existing associated command is shown in the launch command field. Edit it, and then click "Replace".</Text>
+<Text id="447">To remove an association, select an existing file extension and click "Remove". (The file extension remains in the "For Files Ending" pull-down list.)</Text>
+<Text id="448">File associations are stored in the Librarian Interface's main folder, in a file called "associations.xml".</Text>
+</Content>
+</Part>
+<Part id="exporting_collections_to_cddvd">
+<Title>
+<Text id="449">Exporting Collections to CD/DVD</Text>
+</Title>
+<Content>
+<Text id="450">Greenstone can export one or more collections to a self-installing CD/DVD for Windows. To do so, Greenstone's "Export to CD-ROM" package must be installed. This is not included by default, so you may need to modify your installation to include it.</Text>
+<Text id="451">To export a collection, open the "File" menu and choose "Write CD/DVD Image". A list of Greenstone collections appears; click on any one to see its description. Tick the check boxes of the collections to export. You can enter the CD/DVD's name in the box: this is what will appear in the Start menu when the CD/DVD has been installed. Then click "Export". The process involves copying many files and may take a few minutes.</Text>
+<Text id="452">Upon completion, Greenstone will show the name of a folder containing the exported collections. Use a CD/DVD writer to copy its contents to a blank CD/DVD.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="tagging_document_files">
+<Title>
+<Text id="453">Tagging document files</Text>
+</Title>
+<Content>
+<Text id="454">Source documents often need to be structured into sections and subsections, and this information needs to be communicated to Greenstone so that it can preserve the hierarchical structure. Also, metadata - typically the title - might be associated with each section and subsection.</Text>
+<Text id="455">The source documents from an OCR process are typically a set of word processor files, including images. If these are represented as MicrosoftWord files, they can be input into Greenstone using the Word plugin. Alternatively, they can be converted to HTML and input using the HTML plugin.</Text>
+<Text id="456">In either case, the hierarchical structure of a document may be indicated by inserting tags in the text as follows:</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<Text type="code" id="457">&lt;Metadata name="Title"&gt;Realizing human rights for poor people: Strategies for achieving the international development targets&lt;/Metadata&gt;</Text>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="458"><i>(text of section goes here)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="459">The &lt;!-- ... --&gt; markers are used because they indicate comments in HTML; thus these section tags will not affect document formatting. You must include these markers around your section tags, even if the document you are working with is not HTML (e.g. if it's a Microsoft Word file).</Text>
+<Text id="460">In the Description part (between the &lt;Description&gt; and &lt;/Description&gt; tags) other kinds of metadata can be specified, but this is not done for the style of collections we are describing here.</Text>
+<Text id="461">It is important to remember that you are creating a hierarchical table of contents when you insert section tags into your document. This means that sections can be nested within other sections. In fact, all sections must be nested within a single enclosing section that encompasses the entire document.</Text>
+<Text id="462">The following example demonstrates a document with two chapters, the second of which contains two subsections. For real examples of sourcedocuments tagged in this way, look at the source documents for the Demo or DLS collections.</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>&lt;Metadata name="Title"&gt;My Document&lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>&lt;Metadata name="Title"&gt;Chapter 1&lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text type="code" id="463">(text of chapter 1 goes here)</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>&lt;Metadata name="Title"&gt;Chapter 2&lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>&lt;Metadata name="Title"&gt;Subsection 1&lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text type="code" id="464">(text of sub-section 1 goes here)</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>&lt;Metadata name="Title"&gt;Subsection 2&lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text type="code" id="465">(text of sub-section 2 goes here)</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="466">Note that metadata assigned from within a section tag in a source document takes precedence over that assigned to the document as a whole. This means that you should not explicitly specify Title metadata for the top-level section within a source document unless you want it to override the title you gave it when specifying metadata. In the above example, unless you want to override the document's existing title you should omit the line that reads:</Text>
+<CodeLine>&lt;Metadata name="Title"&gt;My Document&lt;/Metadata&gt;</CodeLine>
+</Content>
+</Section>
+<Section id="the_collector">
+<Title>
+<Text id="467">The Collector</Text>
+</Title>
+<Content>
+<Text id="468">The Collector is a facility that helps you create new collections, modify or add to existing ones, or delete collections. To do this you will be guided through a sequence of web pages which request the information that is needed. The sequence is self-explanatory: this section takes you through it. As an alternative to using the Collector, you can also build collections from the command lineâthe first few pages of the Developer's Guide give a detailed walk-through of how to do this. The Collector predates the librarian interface described in Section 3.1, and for most practical purposes the librarian interface should be used instead of the Collector.</Text>
+<Text id="469">Building and distributing information collections carries responsibilities that you should reflect on before you begin. There are legal issues of copyright: being able to access documents doesn't mean you can necessarily give them to others. There are social issues: collections should respect the customs of the community out of which the documents arise. And there are ethical issues: some things simply should not be made available to others. The pen is mightier than the sword!âbe sensitive to the power of information and use it wisely.</Text>
+<Text id="470">To access the Collector, click the appropriate link on the digital library home page.</Text>
+<Text id="471">In Greenstone, the structure of a particular collection is determined when the collection is set up. This includes such things as the format of the source documents, how they should be displayed on the screen, the source of metadata, what browsing facilities should be provided, what full-text search indexes should be provided, and how the search results should be displayed. Once the collection is in place, it is easy to add new documents to itâso long as they have the same format as the existing documents, and the same type of metadata is provided, in exactly the same way.</Text>
+<Text id="472">The Collector has the following basic functions:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="473">create a new collection with the same structure as an existing one;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="474">create a new collection with a different structure from existing ones;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="475">add new material to an existing collection;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="476">modify the structure of an existing collection;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="477">delete a collection; and</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="478">write an existing collection to a self-contained, self-installing cd-rom.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="479">Figure 16 shows the Collector being used to create a new collection, in this case from a set of html files stored locally. You must first decide whether to work with an existing collection or build a new one. The former case covers options 1 and 2 above; the latter covers options 3â6. In Figure 16a, the user opts to create a new collection.</Text>
+<Figure id="using_the_collector_to_build_a_new_collection">
+<Title>
+<Text id="480">Using the Collector to build a new collection (continued on next pages)</Text>
+<SubTitle>
+<Text id="481">(a)</Text>
+</SubTitle>
+</Title>
+<File width="369" height="440" url="images/User_Fig_16a.png"/>
+</Figure>
+<Subsection id="logging_in">
+<Title>
+<Text id="482">Logging in</Text>
+</Title>
+<Content>
+<Text id="483">Either way it is necessary to log in before proceeding. Note that in general, people use their web browser to access the collection-building facility on a remote computer, and build the collection on that server. Of course, we cannot allow arbitrary people to build collections (for reasons of propriety if nothing else), so Greenstone contains a security system which forces people who want to build collections to log in first. This allows a central system to offer a service to those wishing to build information collections and use that server to make them available to others. Alternatively, if you are running Greenstone on your own computer you can build collections locally, but it is still necessary to log in because other people who use the Greenstone system on your computer should not be allowed to build collections without prior permission.</Text>
+</Content>
+</Subsection>
+<Subsection id="dialog_structure">
+<Title>
+<Text id="484">Dialog structure</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_1">
+<Title>
+<Text id="485">Using the Collector to build a new collection (Continued)</Text>
+<SubTitle>
+<Text id="486">(b)</Text>
+</SubTitle>
+</Title>
+<File width="369" height="435" url="images/User_Fig_16b.png"/>
+</Figure>
+<Text id="487">Upon completion of login, the page in Figure 16b appears. This shows the sequence of steps that are involved in collection building. They are:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="488">Collection information</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="489">Source data</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="490">Configuring the collection</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="491">Building the collection</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="492">Viewing the collection.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="493">The first step is to specify the collection's name and associated information. The second is to say where the source data is to come from. The third is to adjust the configuration options, a step that becomes more useful as you gain experience with Greenstone. The fourth step is where all the (computer's) work is done. During the âbuildingâ process the system makes all the indexes and gathers together any other information that is required to make the collection operate. The fifth step is to view the collection that has been created.</Text>
+<Text id="494">These five steps are displayed as a linear sequence of gray buttons at the bottom of the screen in Figure 16b, and at the bottom of all other pages generated by the Collector. This display helps users keep track of where they are in the process. The button that should be clicked to continue the sequence is shown in green (<i>collection information</i> in Figure 16b). The gray buttons (all the others, in Figure 16b) are inactive. The buttons change to yellow as you proceed through the sequence, and the user can return to an earlier step by clicking the corresponding yellow button in the diagram. This display is modeled after the âwizardsâ that are widely used in commercial software to guide users through the steps involved in installing new software.</Text>
+</Content>
+</Subsection>
+<Subsection id="collection_information">
+<Title>
+<Text id="495">Collection information</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_2">
+<Title>
+<Text id="496">Using the Collector to build a new collection (Continued)</Text>
+<SubTitle>
+<Text id="497">(c)</Text>
+</SubTitle>
+</Title>
+<File width="369" height="504" url="images/User_Fig_16c.png"/>
+</Figure>
+<Text id="498">The next step in the sequence, collection information, is shown in Figure 16c. When creating a new collection, it is necessary to enter some information about it:</Text>
+<BulletList>
+<Bullet>
+<Text id="499">title,</Text>
+</Bullet>
+<Bullet>
+<Text id="500">contact E-mail address, and</Text>
+</Bullet>
+<Bullet>
+<Text id="501">brief description.</Text>
+</Bullet>
+</BulletList>
+<Text id="502">The collection title is a short phrase used through the digital library to identify the content of the collection. Example titles include <i>Food and Nutrition Library</i>, <i>World Environmental Library</i>, <i>Development Library</i>, and so on. The E-mail address specifies the first point of contact for any problems encountered with the collection. If the Greenstone software detects a problem, a diagnostic report may be sent to this address. Finally, the brief description is a statement describing the principles that govern what is included in the collection. It appears under the heading <i>About this collection</i> on the first page when the collection is presented.</Text>
+<Text id="503">The user's current position in the collection-building sequence is indicated by an arrow that appears in the display at the bottom of each screenâin this case, as Figure 16c shows, the collection information stage. The user proceeds to Figure 16d by clicking the green source data button.</Text>
+</Content>
+</Subsection>
+<Subsection id="source_data">
+<Title>
+<Text id="504">Source data</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_3">
+<Title>
+<Text id="505">Using the Collector to build a new collection (Continued)</Text>
+<SubTitle>
+<Text id="506">(d)</Text>
+</SubTitle>
+</Title>
+<File width="368" height="532" url="images/User_Fig_16d.png"/>
+</Figure>
+<Text id="507">Figure 16d is the point where the user specifies the source text that comprises the collection. You may either base your collection on a default structure that is provided, or on the structure of an existing collection.</Text>
+<Text id="508">If you opt for the default structure, the new collection may contain html documents (files ending in <i>.htm, .html</i>), or plain text documents (files ending in <i>.txt, .text</i>), Microsoft Word documents (files ending in <i>.doc</i>), PDF documents (files ending in <i>.pdf</i>) or E-mail documents (files ending in <i>.email</i>). More information about the different document formats that can be accommodated is given in the section on âDocument formatsâ below.</Text>
+<Text id="509">If you base your new collection on an existing one, the files in the new collection must be exactly the same type as those used to build the existing one. Note that some collections use non-standard input file formats, while others use metadata specified in auxiliary files. If your new input lacks this information, some browsing facilities may not work properly. For example, if you clone the Demo collection you may find that the <i>subjects</i>, <i>organization</i>, and <i>how to</i> buttons don't work.</Text>
+<Text id="510">Boxes are provided to indicate where the source documents are located: up to three separate input sources can be specified in Figure 16d. If you need more, just click the button marked âmore sources.â</Text>
+<Text id="511">There are three kinds of specification:</Text>
+<BulletList>
+<Bullet>
+<Text id="512">a directory name on the Greenstone server system (beginning with âfile://â)</Text>
+</Bullet>
+<Bullet>
+<Text id="513">an address beginning with âhttp://â for files to be downloaded from the web</Text>
+</Bullet>
+<Bullet>
+<Text id="514">an address beginning with âftp://â for files to be downloaded using anonymous FTP.</Text>
+</Bullet>
+</BulletList>
+<Text id="515">If you use <i>file://</i> or <i>ftp://</i> to specify a file, that file will be downloaded.</Text>
+<Text id="516">If you use <i>http://</i> it depends on whether the URL gives you a normal web page in your browser, or a list of files. If a page, that page will be downloadedâand so will all pages it links to, and all pages they link to, etc.âprovided they reside on the same site, below the URL.</Text>
+<Text id="517">If you use <i>file://</i> or <i>ftp://</i> to specify a folder or directory, or give a <i>http://</i> URL that leads to a list of files, everything in the folder and all its subfolders will be included in the collection.</Text>
+<Text id="518">You can specify sources of more than one type.</Text>
+<Text id="519">In this case (Figure 16d) the new collection will contain documents taken from a local file system as well as a remote web site, which will be mirrored during the building process.</Text>
+<Text id="520">When you click the <i>configure collection</i> button to proceed to the next stage of building, the Collector checks that all the sources of input you specified can be reached. This might take a few seconds, or even a few minutes if you have specified several sources. If one or more of the input sources you specified is unavailable, you will be presented with a page like that in Figure 16e, where the unavailable sources are marked (both of them in this case).</Text>
+<Figure id="using_the_collector_to_build_a_new_collection_4">
+<Title>
+<Text id="521">Using the Collector to build a new collection (Continued)</Text>
+<SubTitle>
+<Text id="522">(e)</Text>
+</SubTitle>
+</Title>
+<File width="368" height="531" url="images/User_Fig_16e.png"/>
+</Figure>
+<Text id="523">Sources might be unavailable because</Text>
+<BulletList>
+<Bullet>
+<Text id="524">the file, FTP site or URL does not exist;</Text>
+</Bullet>
+<Bullet>
+<Text id="525">you need to dial up your ISP first;</Text>
+</Bullet>
+<Bullet>
+<Text id="526">you are trying to access a URL from behind a firewall.</Text>
+</Bullet>
+</BulletList>
+<Text id="527">The last case is potentially the most mysterious. It occurs if you normally have to present a username and password to access the Internet Sometimes it happens that you can see the page from your Web browser if you enter the URL, but the Collector claims that it is unavailable. The explanation is that the page in your browser may be coming from a locally cached copy. Unfortunately, locally cached copies are invisible to the Collector. In this case we recommend that you download the pages using your browser first.</Text>
+</Content>
+</Subsection>
+<Subsection id="configuring_the_collection">
+<Title>
+<Text id="528">Configuring the collection</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_5">
+<Title>
+<Text id="529">Using the Collector to build a new collection (Continued)</Text>
+<SubTitle>
+<Text id="530">(f)</Text>
+</SubTitle>
+</Title>
+<File width="369" height="467" url="images/User_Fig_16f.png"/>
+</Figure>
+<Text id="531">Figure 16f shows the next stage. The construction and presentation of all collections is controlled by specifications in a special collection configuration file (see below). Advanced users may use this page to alter the configuration settings. Most, however, will proceed directly to the final stage. Indeed, in Figure 16d both the <i>configure collection</i> and the <i>build collection</i> buttons are displayed in green, signifying that step 3 can be bypassed completely.</Text>
+<Text id="532">In our example the user has made a small modification to the default configuration file by including the <i>file_is_url</i> flag with the html plugin. This flag causes URL metadata to be inserted in each document, based on the filename convention that is adopted by the mirroring package. This metadata is used in the collection to allow readers to refer to the original source material, rather than to a local copy.</Text>
+</Content>
+</Subsection>
+<Subsection id="building_the_collection_1">
+<Title>
+<Text id="533">Building the collection</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_6">
+<Title>
+<Text id="534">Using the Collector to build a new collection (Continued)</Text>
+<SubTitle>
+<Text id="535">(g)</Text>
+</SubTitle>
+</Title>
+<File width="369" height="304" url="images/User_Fig_16g.png"/>
+</Figure>
+<Text id="536">Figure 16g shows the âbuildingâ stage. Up until now, the responses to the dialog have merely been recorded in a temporary file. The building stage is where the action takes place.</Text>
+<Text id="537">During building, indexes for both browsing and searching are constructed according to instructions in the collection configuration file. The building process takes some time: minutes to hours, depending on the size of the collection and the speed of your computer. Some very large collections take a day or more to build.</Text>
+<Text id="538">When you reach this stage in the interaction, a status line at the bottom of the web page gives feedback on how the operation is progressing, updated every five seconds. The message visible in Figure 16f indicates that when the snapshot was taken, Title metadata was being extracted from an input file.</Text>
+<Text id="539">Warnings are written if input files or URLs are requested that do not exist, or exist but there is no plugin that can process them, or the plugin cannot find an associated file, such as an image file embedded in a html document. The intention is that you will monitor progress by keeping this window open in your browser. If any errors cause the process to terminate, they are recorded in this status area.</Text>
+<Text id="540">You can stop the building process at any time by clicking on the <i>stop building</i> button in Figure 16g. If you leave the web page (and have not cancelled the building process with the <i>stop building</i> button), the building operation will continue, and the new collection will be installed when the operation completes.</Text>
+</Content>
+</Subsection>
+<Subsection id="viewing_the_collection">
+<Title>
+<Text id="541">Viewing the collection</Text>
+</Title>
+<Content>
+<Text id="542">When the collection is built and installed, the sequence of buttons visible at the bottom of Figures 16bâf appears at the bottom of Figure 16g, with the View collection button active. This takes the user directly to the newly built collection.</Text>
+<Text id="543">Finally, there is a facility for E-mail to be sent to the collection's contact E-mail address, and to the system's administrator, whenever a collection is created (or modified.) This allows those responsible to check when changes occur, and monitor what is happening on the system. The facility is disabled by default but can be enabled by editing the <i>main.cfg</i> configuration file (see the <i>Greenstone Digital Library Developer's Guide</i>, Section <CrossRef target="Chapter" external="Develop" lang="en" ref="configuring_your_greenstone_site"/>).</Text>
+</Content>
+</Subsection>
+<Subsection id="working_with_existing_collections">
+<Title>
+<Text id="544">Working with existing collections</Text>
+</Title>
+<Content>
+<Text id="545">When you enter the Collector you have to specify whether you want to create an entirely new collection or work with an existing one, adding data to it or deleting it. By creating all searching and browsing structures automatically from the documents themselves Greenstone makes it easy to add new information to existing collections. Because no links are inserted by hand, when new documents in the same format become available they can be merged into the collection automatically.</Text>
+<Text id="546">To work with an existing collection, you first select the collection from a list that is provided. Some collections are âwrite protectedâ and cannot be altered: these ones don't appear in the selection list. With the collection, you can</Text>
+<BulletList>
+<Bullet>
+<Text id="547">Add more data and rebuild the collection</Text>
+</Bullet>
+<Bullet>
+<Text id="548">Edit the collection configuration file</Text>
+</Bullet>
+<Bullet>
+<Text id="549">Delete the collection entirely</Text>
+</Bullet>
+<Bullet>
+<Text id="550">Export the collection to CD-ROM.</Text>
+</Bullet>
+</BulletList>
+<Part id="add_new_data">
+<Title>
+<Text id="551">Add new data</Text>
+</Title>
+<Content>
+<Text id="552">The files that you specify will be added to the collection. Make sure that you do not re-specify files that are already in the collectionâotherwise two copies will be included. Files are identified by their full pathname, web pages by their absolute web address. You specify directories and files just as you do when building a new collection.</Text>
+<Text id="553">If you add data to a collection and for some reason the building process fails, the old version of the collection remains unchanged.</Text>
+</Content>
+</Part>
+<Part id="edit_configuration_file">
+<Title>
+<Text id="554">Edit configuration file</Text>
+</Title>
+<Content>
+<Text id="555">Advanced users can edit the collection configuration file, just as they can when a new collection is built.</Text>
+</Content>
+</Part>
+<Part id="delete_the_collection">
+<Title>
+<Text id="556">Delete the collection</Text>
+</Title>
+<Content>
+<Text id="557">You will be asked to confirm whether you really want to delete the collection. Once deleted, Greenstone can not bring the collection back!</Text>
+</Content>
+</Part>
+<Part id="export_the_collection">
+<Title>
+<Text id="558">Export the collection</Text>
+</Title>
+<Content>
+<Text id="559">You can export the collection in a form that allows it to be written to a self-contained, self-installing Greenstone CD-ROM for Windows. Because commercial software that creates self-installing CD-ROMs is expensive, this facility includes a homegrown installer module.</Text>
+<Text id="560">When you export the collection, the dialogue informs you of the directory name in which the result has been placed. The entire contents of the directory should be written on to CD-ROM using a standard CD-writing utility.</Text>
+<Text id="561">The immense variety of different possible Windows configurations has made it difficult for us to test and debug the Greenstone installer under all possible conditions. Although the installer produces CD-ROMs that operate on most Windows systems, it is still under development. If you experience problems and you possess a commercial installation package (e.g. InstallShield), you can use it to create CD-ROMs from the information that Greenstone provides. The above-mentioned export directory contains four files that relate to the installation process, and three subdirectories that contain the complete collection and software. Remove the four files and use InstallShield to make a CD-ROM image that installs these directories and creates a shortcut to the program <i>gsdl\server.exe</i>.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="document_formats_1">
+<Title>
+<Text id="562">Document formats</Text>
+</Title>
+<Content>
+<Text id="563">When building collections, Greenstone processes each different format of source document by seeking a âpluginâ that can deal with that particular format. Plugins are specified in the collection configuration file. Greenstone generally uses the filename to determine document formatsâfor example, <i>foo.txt</i> is processed as a text file, <i>foo.html</i> as html, and <i>foo.doc</i> as a Word file.</Text>
+<Text id="564">Here is a summary of the plugins that are available for widely-used document formats. More detail about these plugins, and additional plugins for less commonly-used formats, can be found in the <i>Greenstone Digital Library Developer's Guide</i>.</Text>
+<Part id="textplug">
+<Title>
+<Text id="565">TEXTPlug (*.txt, *.text)</Text>
+</Title>
+<Content>
+<Text id="566">TEXTPlug interprets a plain text file as a simple document. It adds <i>title</i> metadata based on the first line of the file.</Text>
+</Content>
+</Part>
+<Part id="htmlplug">
+<Title>
+<Text id="567">HTMLPlug (*.htm, *.html; also .shtml, .shm, .asp, .php, .cgi)</Text>
+</Title>
+<Content>
+<Text id="568">HTMLPlug processes html files. It extracts <i>title</i> metadata based on the &lt;title&gt; tag; other metadata expressed using html's metatag syntax can be extracted too. There are many options available with this plugin, documented in the <i>Greenstone Digital Library Developer's Guide</i>.</Text>
+</Content>
+</Part>
+<Part id="wordplug">
+<Title>
+<Text id="569">WORDPlug (*.doc)</Text>
+</Title>
+<Content>
+<Text id="570">WORDPlug imports Microsoft Word documents. There are many different variants on the Word formatâand even Microsoft programs frequently make conversion errors. Greenstone uses independent programs to convert Word files to html. For some older Word formats the system resorts to a simple extraction algorithm that finds all text strings in the input file.</Text>
+</Content>
+</Part>
+<Part id="pdfplug">
+<Title>
+<Text id="571">PDFPlug (*.pdf)</Text>
+</Title>
+<Content>
+<Text id="572">PDFPlug imports documents in PDF Adobe's Portable Document Format. Like WORDPlug, it uses an independent program, in this case <i>pdftohtml</i>, to convert PDF files to html.</Text>
+<Text id="573">As with WORDPlug, by default collections will display the html equivalent of the file when the user clicks the <i>document</i> icon; however, the format strings in the collection configuration file can be adjusted to give the user access to the original PDF file instead, and we recommend that you do this. Again, just replace the <i>&lt;link&gt; âŠ &lt;/link&gt;</i> tags by <i>&lt;srclink&gt; âŠ &lt;/srclink&gt;</i> ones.</Text>
+<Text id="574">The <i>pdftohtml</i> program fails on some PDF files. What happens is that the conversion process takes an exceptionally long time, and often an error message relating to the conversion process appears on the screen. If this occurs, the only solution that we can offer is to remove the offending document from the collection. Also, PDFPlug cannot handle encrypted PDF files.</Text>
+</Content>
+</Part>
+<Part id="psplug">
+<Title>
+<Text id="575">PSPlug (*.ps)</Text>
+</Title>
+<Content>
+<Text id="576">PSPlug imports documents in PostScript. It works best if a standard Linux program, called <i>ps2ascii</i>, is already installed on your computer. This is available on most Linux installations, but not on Windows. If this program is not available, PSPlug resorts to a simple text extraction algorithm.</Text>
+</Content>
+</Part>
+<Part id="emailplug">
+<Title>
+<Text id="577">EMAILPlug (*.email)</Text>
+</Title>
+<Content>
+<Text id="578">EMAILPlug imports files containing E-mail, and deals with common E-mail formats such as are used by the Netscape, Eudora, and Unix mail readers. Each source document is examined to see if it contains an E-mail, or several E-mails joined together in one file, and if so its contents are processed. The plugin extracts <i>Subject</i>, <i>To</i>, <i>From</i>, and <i>Date</i> metadata. However, this plugin does not yet handle MIME-encoded E-mails properlyâalthough legible, they often look rather strange.</Text>
+</Content>
+</Part>
+<Part id="zipplug">
+<Title>
+<Text id="579">ZIPPlug (.gz, .z, .tgz, .taz, .bz, .zip, .tar)</Text>
+</Title>
+<Content>
+<Text id="580">ZIPPlug plugin handles the following compressed and/or archived input formats : gzip (.<i>gz</i>, .<i>z</i>, .<i>tgz</i>, .<i>taz</i>) , bzip (.<i>bz</i>) , zip (.<i>zip</i>, .<i>jar</i>) , and tar (.<i>tar</i>). It relies on the programs <i>gunzip</i>, <i>bunzip</i>, <i>unzip</i>, and <i>tar</i>, which are standard Linux utilities. ZIPPlug is disabled on Windows computers.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="administration">
+<Title>
+<Text id="581">Administration</Text>
+</Title>
+<Content>
+<Text id="582">An âadministrativeâ facility is included with every Greenstone installation.To access this facility, click the appropriate link on the front page.</Text>
+<Text id="583">The entry page, shown in Figure 17, gives information about each of the collections offered by the system. Note that <i>all</i> collections are includedâfor there may be âprivateâ ones that do not appear on the Greenstone home page. With each is given its short name, full name, whether it is publicly displayed, and whether or not it is running. Clicking a particular collection's abbreviation (the first column of links in Figure 17) brings up information about that collection, gathered from its collection configuration file and from other internal structures created for that collection. If the collection is both public and running, clicking the collection's full name (the second link) takes you to the collection itself.</Text>
+<Text id="584">A collection named <i>wohiex</i>, for <i>Women's History Excerpt</i>, is visible near the bottom of Figure 17. Figure 18 shows the information that is displayed when this link is clicked. The first section gives some information from the configuration file, and the size of the collection (about 1000 documents, about a million words, over 6 Mb). The next sections contain internal information related to the communication protocol through which collections are accessed. For example, the filter options for âQueryFilterâ show the options and possible values that can be used when querying the collection.</Text>
+<Text id="585">The administrative facility also presents configuration information about the installation and allows it to be modified. It facilitates examination of the error logs that record internal errors, and the user logs that record usage. It enables a specified user (or users) to authorize others to build collections and add new material to existing ones. All these facilities are accessed interactively from the menu items at the left-hand side of Figure 17.</Text>
+<Figure id="greenstone_administration_facility">
+<Title>
+<Text id="586">Greenstone Administration facility</Text>
+</Title>
+<File width="335" height="699" url="images/User_Fig_17.png"/>
+</Figure>
+<Figure id="information_about_the_womens_history_excerpt_collection">
+<Title>
+<Text id="587">Information about the <i>Women's History Excerpt</i> collection</Text>
+</Title>
+<File width="331" height="699" url="images/User_Fig_18.png"/>
+</Figure>
+<Section id="configuration_files">
+<Title>
+<Text id="588">Configuration files</Text>
+</Title>
+<Content>
+<Text id="589">There are two configuration files that control Greenstone's operation, the site configuration file <i>gsdlsite.cfg</i> and the main configuration file <i>main.cfg</i>.</Text>
+<Text id="590">The <i>gsdlsite.cfg</i> file is used to configure the Greenstone software for the site where it is installed. It is designed for keeping configuration options that are particular to a given site. Examples include the name of the directory where the Greenstone software is kept, the http address of the Greenstone system, and whether the <i>fastcgi</i> facility is being used.The entries in this file are described in the <i>Greenstone Digital Library Installation Guide</i>.</Text>
+<Text id="591">The <i>main.cfg</i> file contains information that is common to the interface of all collections served by a Greenstone site. It includes the E-mail address of the system maintainer, whether the status and collector pages are enabled, whether logs of user activity are kept, and whether Internet âcookiesâ are used to identify users.</Text>
+</Content>
+</Section>
+<Section id="logs">
+<Title>
+<Text id="592">Logs</Text>
+</Title>
+<Content>
+<Text id="593">Three kinds of logs can be examined: usage logs, error logs and initialization logs. The last two are only really of interest to people maintaining the software.</Text>
+<Text id="594">All user activityâevery page that each user visitsâcan be recorded by the Greenstone software, though no personal names are included in the logs. Logging, disabled by default, is enabled by including the lines</Text>
+<CodeLine>logcgiargs true</CodeLine>
+<CodeLine>usecookies true</CodeLine>
+<Text id="595">in the main system configuration file. Both options are false by default, so that no logging is done unless they are set. It is the <i>logcgiargs</i> line that actually turns logging on and off. By activating <i>usecookies</i> a unique identification code is assigned to each user, which enables individual user's interactions to be traced through the log file.</Text>
+<Text id="596">Each line in the user log records a page visitedâeven the pages generated to inspect the log files! It contains (a) the IP address of the user's computer, (b) a timestamp in square brackets, (c) the CGI arguments in parentheses, and (d) the name of the user's browser (Netscape is called âMozillaâ). Here is a sample line, split and annotated for ease of reading:</Text>
+<CodeLine>/fast-cgi-bin/niupepalibrary</CodeLine>
+<CodeLine>(a) its-www1.massey.ac.nz</CodeLine>
+<CodeLine>(b) [ Thu Dec07 23:47:00 NZDT2000]</CodeLine>
+<CodeLine>(c) (a=p, b=0, bcp=, beu=, c=niupepa, cc=, ccp=0, ccs=0, cl=, cm=, cq2=, d=, e=, er=, f=0, fc=1, gc=0, gg=text, gt=0, h=, h2=, hl=1, hp=, il=l, j=, j2=, k=1, ky=, l=en, m=50, n=, n2=, o=20, p=home, pw=, q=, q2=, r=1, s=0, sp=frameset, t=1, ua=, uan=, ug=, uma=listusers, umc=, umnpw1=, umnpw2=, umpw=, umug=, umun=, umus=, un=, us=invalid, v=0, w=w, x=0, z=130.123.128.4-950647871)</CodeLine>
+<CodeLine>(d) âMozilla/4.08 [en] (Win95; I ;Nav)â</CodeLine>
+<Text id="597">The last CGI argument, âzâ, is an identification code or âcookieâ generated by the user's browser: it comprises the user's IP number followed by the timestamp when they first accessed the digital library.</Text>
+<Text id="598">The log file <i>usage.txt</i> is placed in the <i>etc</i> directoryin the Greenstone file structure (see the <i>Greenstone Digital Library Developer's Guide</i>).When logging is enabled, every action by every user is logged. However, only the last 100 entries in the log file are displayed by the <i>usage log</i> link in Figure 17.</Text>
+</Content>
+</Section>
+<Section id="user_management">
+<Title>
+<Text id="599">User management</Text>
+</Title>
+<Content>
+<Text id="600">Greenstone incorporates an authentication scheme which can be used to control access to certain facilities. At the moment this is only used to restrict the people who are allowed to enter the Collectorand certain administration functions. If, for a particular collection, it were necessary to authenticate users before returning information to them, this is possible tooâfor example, documents could be protected on an individual basis so that they can only be accessed by registered users on presentation of a password. However, no current collections use this facility). Authentication is done by requesting a user name and password, as illustrated in Figure 16a.</Text>
+<Text id="601">From the administration page users can be listed, new ones added, and old ones deleted. The ability to do this is of course also protected: only users who have administrative privileges can add new users. It is also possible for each user to belong to different âgroupsâ. At present, the only extant groups are âadministratorâ and âcolbuilderâ. Members of the first group can add and remove users, and change their groups. Members of the second can access the facilities described above to build new collections and alter (and delete) existing ones.</Text>
+<Text id="602">When Greenstone is installed, there is one user called <i>admin</i> who belongs to both groups. The password for this user is set during the installation process. This user can create new names and passwords for users who belong just to the <i>colbuilder</i> group, which is the recommended way of giving other users the ability to build collections. User information is recorded in two databases that are placed in the Greenstone file structure (see the <i>Greenstone Digital Library Developer's Guide</i>).</Text>
+</Content>
+</Section>
+<Section id="technical_information">
+<Title>
+<Text id="603">Technical information</Text>
+</Title>
+<Content>
+<Text id="604">The links under the <i>Technical information</i> heading show further information on the installation.The <i>general</i> link gives access to technical information, including the directories where things are stored.The <i>protocols</i> menu item gives, for each possible protocol type, information about each of the collections supported by that protocol.</Text>
+<Text id="605">Finally, user interface code (called the âreceptionistâ) uses <i>actions</i> to communicate the wishes of the user. These actions correspond to the CGI argument labeled <i>a</i>. For example, if <i>a=status</i> the receptionist invokes the <i>status</i> action (which displays the status page). A menu item gives access to lists of all actions supported by the system, and another leads to the arguments that these actions take.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_a_software_features">
+<Title>
+<Text id="606">Appendix A Software features</Text>
+</Title>
+<Content>
+<Table class="hidden" id="table_appendixa">
+<Title/>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="607"><i>Accessible via web browser</i></Text>
+</th>
+<th width="397">
+<Text id="608">Collections are accessed through a standard web browser (Netscape or Internet Explorer) and combine easy-to-use browsing with powerful search facilities.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="609"><i>Full-text and fielded search</i></Text>
+</th>
+<th width="397">
+<Text id="610">The user can search the full text of the documents, or choose between indexes built from different parts of the documents. For example, some collections have an index of full documents, an index of sections, an index of titles, and an index of authors, each of which can be searched for particular words or phrases. Results can be ranked by relevance or sorted by a metadata element.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="611"><i>Flexible browsing facilities</i></Text>
+</th>
+<th width="397">
+<Text id="612">The user can browse lists of authors, lists of titles, lists of dates, classification structures, and so on. Different collections may offer different browsing facilities and even within a collection, a broad variety of browsing interfaces are available. Browsing and searching interfaces are constructed during the building process, according to collection configuration information.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="613"><i>Creates access structures automatically</i></Text>
+</th>
+<th width="397">
+<Text id="614">The Greenstone software creates information collections that are very easy to maintain. All searching and browsing structures are built directly from the documents themselves. No links are inserted by hand, but existing links in originals are maintained. This means that if new documents in the same format become available, they can be merged into the collection automatically. Indeed, for some collections this is done by processes that wake up regularly, scout for new material, and rebuild the indexesâall without manual intervention.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="615"><i>Makes use of available metadata</i></Text>
+</th>
+<th width="397">
+<Text id="616">Metadata, which is descriptive information such as author, title, date, keywords, and so on, may be associated with each document, or with individual sections within documents. Metadata is used as the raw material for browsing indexes. It must be either provided explicitly or derivable automatically from the source documents. The Dublin Core metadata scheme is used for most electronic documents, however, provision is made for other schemes.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="617"><i>Plugins extend the system's capabilities</i></Text>
+</th>
+<th width="397">
+<Text id="618">In order to accommodate different kinds of source documents, the software is organized in such a way that âpluginsâ can be written for new document types. Plugins currently exist for plain text, html, Word, PDF, PostScript, E-mail, some proprietary formats, and for recursively traversing directory structures and compressed archives containing such documents. A collection may have source documents in different forms. In order to build browsing indexes from metadata, an analogous scheme of âclassifiersâ is used: classifiers create browsing indexes of various kinds based on metadata.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="619"><i>Designed for multi-gigabyte collections</i></Text>
+</th>
+<th width="397">
+<Text id="620">Collections can contain millions of documents, making the Greenstone system suitable for collections up to several gigabytes.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="621"><i>Documents can be in any language</i></Text>
+</th>
+<th width="397">
+<Text id="622">Unicode is used throughout the software, allowing any language to be processed in a consistent manner. To date, collections have been built containing French, Spanish, Maori, Chinese, Arabic and English. On-the-fly conversion is used to convert from Unicode to an alphabet supported by the user's web browser.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="623"><i>User interface available in multiple languages</i></Text>
+</th>
+<th width="397">
+<Text id="624">The interface can be presented in multiple languages. Currently, the interface is available in Arabic, Chinese, Dutch, English, French, German, Maori, Portuguese, and Spanish. New languages can be added easily.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="625"><i>Collections can contain text, pictures, audio, and video</i></Text>
+</th>
+<th width="397">
+<Text id="626">Greenstone collections can contain text, pictures, audio and video clips. Most non-textual material is either linked in to the textual documents or accompanied by textual descriptions (such as figure captions) to allow full-text searching and browsing. However, the architecture permits implementation of plugins and classifiers even for non-textual data.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="627"><i>Uses advanced compression techniques</i></Text>
+</th>
+<th width="397">
+<Text id="628">Compression techniques are used to reduce the size of the indexes and text. Reducing the size of the indexes via compression has the added advantage of increasing the speed of text retrieval.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="629"><i>Administrative function provided</i></Text>
+</th>
+<th width="397">
+<Text id="630">An âadministrativeâ function enables specified users to authorize new users to build collections, protect documents so that they can only be accessed by registered users on presentation of a password, examine the composition of all collections, and so on. Logs of user activity can record all queries made to every Greenstone collection.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="631"><i>New collections appear dynamically</i></Text>
+</th>
+<th width="397">
+<Text id="632">Collections can be updated and new ones brought on-line at any time, without bringing the system down; the process responsible for the user interface will notice (through periodic polling) when new collections appear and add them to the list presented to the user.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="633"><i>Collections can be published on the Internet or on CD-ROM</i></Text>
+</th>
+<th width="397">
+<Text id="634">The software can be used to serve collections over the World-Wide Web. Greenstone collections can be made available, in precisely the same form, on CD-ROM. The user interface is through a standard web browser (Netscape is provided on each disk), and the interaction is identical to accessing the collection on the webâexcept that response times are more predictable. The CD-ROMs run under all versions of the Windows operating system.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="635"><i>Collections can be distributed amongst different computers</i></Text>
+</th>
+<th width="397">
+<Text id="636">A flexible process structure allows different collections to be served by different computers, yet be presented to the user in the same way, on the same web page, as part of the same digital library.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="637"><i>Operates on both Windows and Unix</i></Text>
+</th>
+<th width="397">
+<Text id="638">Greenstone runs under both Windows (3.1/3.11, 95/98/Me, NT/2000) and Unix (Linux and SunOS). Any of these systems can be used as a webserver. Collections cannot be built on low-end Windows systems (3.1/3.11), but pre-built collections can be transferred to them.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="639"><i>What you get with Greenstone</i></Text>
+</th>
+<th width="397">
+<Text id="640">The Greenstone Digital Library is open-source software, available from the New Zealand Digital Library (<i>nzdl.org</i>) under the terms of the Gnu General Public License. The software includes everything described above: web serving, CD-ROM creation, collection building, multi-lingual capability, plugins and classifiers for a variety of different source document types. It includes an autoinstall feature to allow easy installation on both Windows and Unix. In the spirit of open-source software, users are encouraged to contribute modifications and enhancements.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<Chapter id="appendix_b_glossary_of_terms">
+<Title>
+<Text id="641">Appendix B Glossary of terms</Text>
+</Title>
+<Content>
+<Table id="appendixb" class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="123">
+<Text id="642"><b>Term</b></Text>
+</th>
+<th width="406">
+<Text id="643"><b>Meaning</b></Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="644"><i>autoconf</i></Text>
+</th>
+<th width="406">
+<Text id="645">Unix program used to configure the Greenstone software installation package to suit your system</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="646"><i>Autorun</i></Text>
+</th>
+<th width="406">
+<Text id="647">Windows feature that starts a program automatically whenever a CD-ROM is inserted</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="648">Boolean query</Text>
+</th>
+<th width="406">
+<Text id="649">Query to an information retrieval system that may contain AND, OR, NOT</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="650">Browsing</Text>
+</th>
+<th width="406">
+<Text id="651">Accessing a collection by scanning an organized list of metadata values associated with the documents (such as author, title, date, keywords)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="652"><i>buildcol.pl</i></Text>
+</th>
+<th width="406">
+<Text id="653">Greenstone program used to build collections</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="654">Building</Text>
+</th>
+<th width="406">
+<Text id="655">Process of creating the indexing and browsing structures that are used to access a collection</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="656">C++</Text>
+</th>
+<th width="406">
+<Text id="657">Programming language in which the majority of the Greenstone software is written</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="658">Casefolding</Text>
+</th>
+<th width="406">
+<Text id="659">Making uppercase and lowercase words look the same, for searching purposes</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="660">CGI</Text>
+</th>
+<th width="406">
+<Text id="661">Common Gateway Interface, a scheme that allows users to activate programs on the host computer by clicking on web pages</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="662">CGI script</Text>
+</th>
+<th width="406">
+<Text id="663">Code associated with a button, menu, or link on a web page that specifies what the host computer is to do when it is clicked</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="664"><i>cgi-bin</i></Text>
+</th>
+<th width="406">
+<Text id="665">Directory in which CGI scripts are stored</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="666">Classifier</Text>
+</th>
+<th width="406">
+<Text id="667">Greenstone code module that examines document metadata to form an index for browsing</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="668">Collection</Text>
+</th>
+<th width="406">
+<Text id="669">Set of documents that are brought together under a uniform searching and browsing interface</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="670">Collection configuration file</Text>
+</th>
+<th width="406">
+<Text id="671">File that specifies how a collection is to be imported and built, what indexes and language interfaces are to be provided, etc.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="672">Collection server</Text>
+</th>
+<th width="406">
+<Text id="673">Program responsible for providing access to a collection when it is being used</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="674">Configuration file</Text>
+</th>
+<th width="406">
+<Text id="675">See collection configuration file, main configuration file, site configuration file</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="676">CVS</Text>
+</th>
+<th width="406">
+<Text id="677">Concurrent Versioning System, a scheme for maintaining source code used throughout Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="678"><i>db2txt</i></Text>
+</th>
+<th width="406">
+<Text id="679">Greenstone tool for viewing a GDBM database as text (see GDBM)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="680">Demo collection</Text>
+</th>
+<th width="406">
+<Text id="681">A subset of the Humanities Development Library, distributed with the Greenstone software and used for illustration in this tutorial</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="682">Digital library</Text>
+</th>
+<th width="406">
+<Text id="683">Collection of digital objects (text, audio, video), along with methods for access and retrieval, and for selection, organization, and maintenance</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="684">DL</Text>
+</th>
+<th width="406">
+<Text id="685">Development Library, A Greenstone collection of humanitarian information for developing countries</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="686">Document</Text>
+</th>
+<th width="406">
+<Text id="687">Basic unit from which digital library collections are constructed; it may include text, graphics, sound, video, etc.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="688">Dublin core</Text>
+</th>
+<th width="406">
+<Text id="689">A standard way of describing metadata</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="690">Fast CGI</Text>
+</th>
+<th width="406">
+<Text id="691">Facility that allows CGI scripts to remain continuously active so that they do not have to be restarted from scratch every time they are invoked</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="692">Filter program</Text>
+</th>
+<th width="406">
+<Text id="693">That part of a Greenstone collection server that implements querying and browsing operations</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="694">Format string</Text>
+</th>
+<th width="406">
+<Text id="695">A string that specifies how documents and other listings are to be displayed in Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="696">GB-encoding</Text>
+</th>
+<th width="406">
+<Text id="697">Standard way of encoding the Chinese language</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="698">GDBM</Text>
+</th>
+<th width="406">
+<Text id="699">Gnu DataBase Manager, a program used within the Greenstone software to store metadata for each document</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="700">GIMP</Text>
+</th>
+<th width="406">
+<Text id="701">Gnu Image-Manipulation Program used (on Unix) to create icons in Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="702">GML</Text>
+</th>
+<th width="406">
+<Text id="703">Greenstone Markup Language, an XML-compliant format used for storing documents internally</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="704">Gnu license</Text>
+</th>
+<th width="406">
+<Text id="705">Software license that permits users to copy and distribute computer programs freely, and modify themâso long as all modifications are made publicly available</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="706">Greenstone</Text>
+</th>
+<th width="406">
+<Text id="707">The name of this digital library software</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="708">GSDL</Text>
+</th>
+<th width="406">
+<Text id="709">Abbreviation for Greenstone Digital Library</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="710"><i>%GSDLHOME%</i></Text>
+</th>
+<th width="406">
+<Text id="711">Operating system variable that represents the top-level directory in which all Greenstone programs and collections are stored (<i>$GSDLHOME</i> on Unix systems)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="712"><i>%GSDLOS%</i></Text>
+</th>
+<th width="406">
+<Text id="713">Operating system variable that represents the operating system currently being used (<i>$GSDLOS</i> on Unix systems)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="714"><i>hashfile</i></Text>
+</th>
+<th width="406">
+<Text id="715">Greenstone program used at import or build time to generate the OID of each document</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="716">HTML</Text>
+</th>
+<th width="406">
+<Text id="717">HyperText Markup Language, the language in which web documents are written</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="718"><i>import.pl</i></Text>
+</th>
+<th width="406">
+<Text id="719">Greenstone program used to import documents</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="720">Importing</Text>
+</th>
+<th width="406">
+<Text id="721">Process of bringing collections of documents into the Greenstone system</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="722">Index</Text>
+</th>
+<th width="406">
+<Text id="723">Information structure that is used for searching or browsing a collection</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="724">InstallShield</Text>
+</th>
+<th width="406">
+<Text id="725">Windows program, used by Greenstone CD-ROMs, that allows a system to be installed from a CD-ROM</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="726">Main configuration file</Text>
+</th>
+<th width="406">
+<Text id="727">File that contains specifications common to all collections served by this site</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="728">Metadata</Text>
+</th>
+<th width="406">
+<Text id="729">Descriptive data such as author, title, date, keywords, and so on, that is associated with a document (or document collection)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="730">MG</Text>
+</th>
+<th width="406">
+<Text id="731">Managing Gigabytes, a program used by the Greenstone system for full-text indexing, that incorporates compression techniques (see Witten, I.H., Moffat, A. and Bell, T. <i>Managing Gigabytes: compressing and indexing documents and images</i>, Morgan Kaufmann, second edition, 1999)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="732"><i>mgbuild</i></Text>
+</th>
+<th width="406">
+<Text id="733">MG program for building a compressed full-text index</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="734"><i>mgquery</i></Text>
+</th>
+<th width="406">
+<Text id="735">MG program for querying a compressed full-text index</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="736"><i>mkcol.pl</i></Text>
+</th>
+<th width="406">
+<Text id="737">Greenstone program that creates and initializes the directory structure for a new collection</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="738">New ZealandÂ <br/>Digital Library Project</Text>
+</th>
+<th width="406">
+<Text id="739">Research project in the Computer Science Department at the University of Waikato, New Zealand, that created the Greenstone software (<i>nzdl.org</i>)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="740">OID</Text>
+</th>
+<th width="406">
+<Text id="741">Object Identifier, a unique identification code associated with a document</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="742">Perl</Text>
+</th>
+<th width="406">
+<Text id="743">Programming language used for many of the text-processing operations that occur during the building process</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="744">Ping</Text>
+</th>
+<th width="406">
+<Text id="745">Message sent to a system to determine whether it is running or not</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="746">Plugin</Text>
+</th>
+<th width="406">
+<Text id="747">Code module for handling documents of different formats, used during the importing and building processes</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="748">Protocol</Text>
+</th>
+<th width="406">
+<Text id="749">Set of conventions by which a Greenstone receptionist communicates with a collection server</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="750">Ranked query</Text>
+</th>
+<th width="406">
+<Text id="751">Natural-language query to an information retrieval system, for which the documents that match the query are sorted in order of relevance</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="752">Receptionist</Text>
+</th>
+<th width="406">
+<Text id="753">Program that organizes the Greenstone user interface</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="754">RTF</Text>
+</th>
+<th width="406">
+<Text id="755">Rich Text Format, a standard format for interchange of text documents</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="756">Searching</Text>
+</th>
+<th width="406">
+<Text id="757">Accessing a collection through a full-text search of its contents (or parts of contents, such as section titles)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="758">Server</Text>
+</th>
+<th width="406">
+<Text id="759">See Collection server and Web server</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="760"><i>setup.bat, setup.sh, setup.csh</i></Text>
+</th>
+<th width="406">
+<Text id="761">Script used to set up your environment to recognize the Greenstone software</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="762">Site configuration file</Text>
+</th>
+<th width="406">
+<Text id="763">File that contains specifications used to configure the Greenstone software for the site on which it is installed</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="764">Stemming</Text>
+</th>
+<th width="406">
+<Text id="765">Stripping endings off a query term to make it more general</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="766">STL</Text>
+</th>
+<th width="406">
+<Text id="767">Standard template library, a widely-available library of C++ code developed by Silicon Graphics</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="768">txt2db</Text>
+</th>
+<th width="406">
+<Text id="769">Greenstone program used at build time to create the GDBM database</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="770">Unicode</Text>
+</th>
+<th width="406">
+<Text id="771">Standard scheme for representing the character sets used in the world's languages</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="772">UNU</Text>
+</th>
+<th width="406">
+<Text id="773">The United Nations University; also used to refer to a Greenstone collection created for that organization</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="774">Web server</Text>
+</th>
+<th width="406">
+<Text id="775">Standard program that computers use to make information accessible over the World Wide Web</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="776">XML</Text>
+</th>
+<th width="406">
+<Text id="777">A standard format for structured documents and data on the web (the Greenstone Markup Language is an XML-compliant format)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="778">This option is disabled if an element of the same name already exists.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/es/Develop_es.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/es/Develop_es.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/es/Develop_es.xml	(revision 13632)
@@ -0,0 +1,5252 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">BIBLIOTECA DIGITAL GREENSTONE</Text>
+</Heading>
+<Title>
+<Text id="2">GUÃA DEL PROGRAMADOR</Text>
+</Title>
+<Author>
+<Text id="3">David Bainbridge, Dana McKay e Ian H. Witten</Text>
+</Author>
+<Affiliation>
+<Text id="4">Departamento de InformÃ¡tica<br/>Universidad de Waikato, Nueva Zelandia</Text>
+</Affiliation>
+<Text id="5">Greenstone es un conjunto de programas informÃ¡ticos destinado a la creaciÃ³n y difusiÃ³n de colecciones documentales digitales que ofrece un nuevo procedimiento para organizar la informaciÃ³n y publicarla en Internet o en forma de CD-ROM. Elaborado dentro del proyecto de Biblioteca Digital de Nueva Zelandia de la Universidad de Waikato, este producto se distribuye en colaboraciÃ³n con la UNESCO y el Proyecto de Bibliotecas sobre Aspectos Humanitarios y de Desarrollo. Es un programa informÃ¡tico de cÃ³digo fuente abierto (<i>open-source software</i>), que puede descargarse en la direcciÃ³n <i>http://greenstone.org</i> segÃºn las condiciones estipuladas en la Licencia PÃºblica General de GNU</Text>
+<Comment>
+<Text id="6">Nuestro deseo es garantizar el correcto funcionamiento de este programa, por lo que alentamos a sus usuarios a notificar cualquier problema que detecten a:Â <i>greenstone@cs.waikato.ac.nz</i></Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">Marzo de 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">Acerca de este manual</Text>
+</Title>
+<Content>
+<Text id="10">En este manual se explica cÃ³mo funciona Greenstone. Se dirige a aquellos que desean personalizar las colecciones y desarrollar y mantener al dÃ­a el programa.</Text>
+<Text id="11">En la SecciÃ³n <CrossRef target="Chapter" ref="understanding_the_collection-building_process"/> se da una idea general del proceso de creaciÃ³n de colecciones, que comprende la estructura de los directorios, el formato de documento interno y el archivo de configuraciÃ³n por el que se rige la estructura de cada colecciÃ³n. En la SecciÃ³n <CrossRef target="Chapter" ref="getting_the_most_out_of_your_documents"/> se describen las partes de Greenstone que tratan los documentos de origen (y los metadatos) y se muestra cÃ³mo se accede a la informaciÃ³n mediante la interfaz de usuario. Se definen asimismo los componentes âexternosâ del programa distribuidos con Greenstone. En la SecciÃ³n <CrossRef target="Chapter" ref="the_greenstone_runtime_system"/> se explica la estructura del sistema de ejecuciÃ³n de Greenstone y se proporciona informaciÃ³n sobre el programa que permite comprender su funcionamiento y el modo de modificar el sistema para adaptarlo a las distintas necesidades. En la SecciÃ³n <CrossRef target="Chapter" ref="configuring_your_greenstone_site"/> se exponen los archivos de configuraciÃ³n, y en el ApÃ©ndice se presenta la biblioteca estÃ¡ndar de plantillas C++ (Â <i>SLT</i>).</Text>
+<Text id="12">Es posible que cuando utilice el programa Greenstone aparezcan referencias a caracterÃ­sticas que no figuran en este manual, ya que Greenstone se encuentra en constante evoluciÃ³n. Para estar al tanto de las modificaciones, inscrÃ­base a la lista de correo electrÃ³nico de Greenstone (siga las instrucciones enÂ <i>greenstone.org</i>).</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="13">Conjunto de documentos</Text>
+</Title>
+<Content>
+<Text id="14">La serie completa de documentos Greenstone comprende cinco volÃºmenes:</Text>
+<BulletList>
+<Bullet>
+<Text id="15">La GuÃ­a del Instalador de la Biblioteca Digital Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">La GuÃ­a del Usuario de la Biblioteca Digital Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="17">La GuÃ­a del Programador de la Biblioteca Digital Greenstone (el presente documento)</Text>
+</Bullet>
+<Bullet>
+<Text id="18">La Biblioteca Digital Greenstone: del Papel a la ColecciÃ³n</Text>
+</Bullet>
+<Bullet>
+<Text id="19">La Biblioteca Digital Greenstone: uso del Organizador</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="20">Agradecimientos</Text>
+</Title>
+<Content>
+<Text id="21">El programa Greenstone es fruto de la colaboraciÃ³n de muchas personas. Rodger McNab y Stefan Boddie son los principales arquitectos y programadores. TambiÃ©n han contribuido David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson y Stuart Yeates. Otros miembros del proyecto Biblioteca Digital de Nueva Zelanda que proporcionaron asesorÃ­a y valiosas ideas para la concepciÃ³n del sistema son: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols y Lloyd Smith. TambiÃ©n queremos dar las gracias a todos aquellos que contribuyeron a los paquetes de programas con licencias GNU incluidos en esta distribuciÃ³n: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE y XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="understanding_the_collection-building_process">
+<Title>
+<Text id="22">FUNCIONAMIENTO DEL PROCESO DE CREACIÃN DE UNA COLECCIÃN</Text>
+</Title>
+<Content>
+<Text id="23">Los usuarios de Greenstone pueden crear colecciones utilizando el Colector, cuyo funcionamiento se explica en laÂ <i>GuÃ­a del Usuario de la Biblioteca Digital Greenstone</i>Â (SecciÃ³n 3). Este procedimiento permite crear colecciones muy fÃ¡cilmente basÃ¡ndose en los modelos ya existentes pero con un contenido nuevo. Sin embargo, el Colector no permite realmente crear colecciones con estructuras completamente nuevas. Le invita a modificar el archivo de configuraciÃ³n de la colecciÃ³n por el que se rige la estructura de la colecciÃ³n, pero usted necesita tener sÃ³lidos conocimientos de Greenstone para efectuar cambios radicales pero efectivos. En esta secciÃ³n se le indica lo que necesita saber para hacerlo. TambiÃ©n se explica la estructura de directorios de Greenstone y el formato en el que se almacenan internamente los documentos.</Text>
+<Text id="24">En este manual suponemos que usted ha instalado Greenstone en su computadora, bien con Windows o bien con Unix. Si aÃºn no lo ha hecho, deberÃ­a consultar laÂ <i>GuÃ­a de InstalaciÃ³n de la Biblioteca Digital Greenstone.</i>Â Utilizamos el nombreÂ <i>GSDLHOME</i>Â a lo largo de este manual para referirnos al directorio principal de Greenstone, que se denominaÂ <i>%GSDLHOME%</i>Â en los sistemas Windows yÂ <i>$GSDLHOME</i>Â en los sistemas Unix. Este directorio se estableciÃ³ durante el procedimiento de instalaciÃ³n.</Text>
+<Section id="building_collections_from_the_command_line">
+<Title>
+<Text id="25">CreaciÃ³n de colecciones desde la lÃ­nea de comandos</Text>
+</Title>
+<Content>
+<Text id="26">A fin de comprender mejor este proceso, empecemos por recorrer las operaciones necesarias para crear una colecciÃ³n a partir de la lÃ­nea de comandos. Por supuesto, el mÃ©todo mÃ¡s fÃ¡cil es utilizar el Colector. La colecciÃ³n que tomamos como ejemplo es la que se incluye en el CD-ROM de distribuciÃ³n del programa Greenstone, que contiene las pÃ¡ginas Web de muchas de las personas que han colaborado en el proyecto de Biblioteca Digital de Nueva Zelandia y el programa Greenstone.</Text>
+<Text id="27">En las siguientes subsecciones se explica la creaciÃ³n de una colecciÃ³n con Windows y con Unix. De hecho, las dos subsecciones son casi idÃ©nticas, sÃ³lo tiene que leer la que corresponda a su sistema. Algunas de las instrucciones le podrÃ¡n parecer misteriosas e indescifrables, pero sÃ­galas atentamente, su significado se explicarÃ¡ mÃ¡s adelante. Tras las instrucciones se resumen las diferencias entre la creaciÃ³n de una colecciÃ³n con cada uno de los sistemas.</Text>
+<Subsection id="collection_building_under_windows">
+<Title>
+<Text id="28">CreaciÃ³n de colecciones bajo Windows</Text>
+</Title>
+<Content>
+<Text id="29">El primer desafÃ­o para crear una colecciÃ³n de Greenstone a partir de la lÃ­nea de comandos en el sistema Windows es llegar al âindicador de comandosâ, el lugar en el que se teclean los comandos. Trate de buscar en el menÃºÂ <i>Inicio</i>, o en el submenÃºÂ <i>Programas</i>, una entrada comoÂ <i>indicador MS-DOS</i>,Â <i>indicador DOS</i>Â oÂ <i>indicador de comandos</i>. Si no logra encontrarla, abra la funciÃ³nÂ <i>Ejecutar</i>Â y tecleeÂ <i>command (</i>Â oÂ <i>cmd)</i>Â en la ventana de diÃ¡logo. Si todo esto falla, pida ayuda a algÃºn entendido, como su administrador de sistema.</Text>
+<Text id="30">Vaya al directorio en el que estÃ¡ instalado Greenstone. Si Greenstone estÃ¡ instalado en su ubicaciÃ³n por defecto, puede acceder tecleando:</Text>
+<CodeLine>cd âC:\Program Files\gsdlâ</CodeLine>
+<Text id="31">(Son necesarias las comillas debido a los espacios existentes enÂ <i>Program Files</i>.) A continuaciÃ³n, teclee en el indicador:</Text>
+<CodeLine>setup.bat</CodeLine>
+<Text id="32">Este archivo de ejecuciÃ³n por lotes (que puede usted leer si lo desea) indica al sistema dÃ³nde encontrar los programas Greenstone<FootnoteRef id="1"/>. Si, mÃ¡s adelante durante su sesiÃ³n interactiva en el indicador de DOS, desea volver al directorio principal de Greenstone, puede hacerlo tecleandoÂ <i>cd â%GSDLHOME%â</i>Â (una vez mÃ¡s, son necesarias las comillas debido a los espacios existentes en el nombre de archivo). Si cierra su ventana DOS y abre otra, tendrÃ¡ que volver a teclearÂ <i>setup.bat</i>.</Text>
+<Text id="33">Ahora estÃ¡ en condiciones de constituir, crear y recrear colecciones. El primer programa que examinaremos es el programa PerlÂ <i>mkcol.pl</i>, cuyo nombre corresponde a âÂ <i>make a collection</i>Â â (constituir una colecciÃ³n). En primer lugar, active el programa tecleandoÂ <i>perl -S mkcol.pl</i>Â para obtener en pantalla una descripciÃ³n de la sintaxis y una lista de argumentos. Si su entorno Windows estÃ¡ programado para asociar la aplicaciÃ³n Perl con archivos terminados enÂ <i>.pl</i>, puede expresarlo de manera mÃ¡s concisa tecleandoÂ <i>mkcol.pl</i>. Como puede comprobarlo en el mensaje que aparece, el Ãºnico argumento necesario esÂ <i>creator</i>, que se utiliza para especificar quiÃ©n ha creado la colecciÃ³n.</Text>
+<Text id="34">Utilicemos ahora este comando para crear los archivos y subdirectorios iniciales necesarios para nuestra colecciÃ³n de las pÃ¡ginas personales de los miembros del proyecto de Biblioteca Digital Greenstone. Para asignar a la colecciÃ³n el nombreÂ <i>dlpeople</i>Â (abreviaciÃ³n en inglÃ©s de âpersonas de la biblioteca digitalâ), esto fue lo que escribÃ­:</Text>
+<CodeLine>perl âS mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<Text id="35">(oÂ <i>mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</i>, si Perl estÃ¡ asociado con la extensiÃ³n de archivosÂ <i>.pl</i>). Â¡No olvide sustituir mi direcciÃ³n de correo electrÃ³nico por la suya!</Text>
+<Text id="36">Para poder visualizar los archivos reciÃ©n creados, vaya al directorio reciÃ©n creado de la colecciÃ³n tecleando:</Text>
+<CodeLine>cd â%GSDLHOME%\collect\dlpeopleâ</CodeLine>
+<Figure id="figure_archivo_de_configuraciÃ³n_de_la_colecciÃ³n_creado_porÂ mkcol.pl">
+<Title>
+<Text id="37">Archivo de configuraciÃ³n de la colecciÃ³n creado porÂ <i>mkcol.pl</i></Text>
+</Title>
+<CodeLine>creatorÂ Â Â Â Â Â  me@cs.waikato.ac.nz</CodeLine>
+<CodeLine>maintainerÂ Â Â  me@cs.waikato.ac.nz</CodeLine>
+<CodeLine>publicÂ Â Â Â Â Â Â  true</CodeLine>
+<CodeLine>betaÂ Â Â Â Â Â Â Â Â  true</CodeLine>
+<CodeLine>indexesÂ Â Â Â Â Â Â  document:text</CodeLine>
+<CodeLine>defaultindexÂ Â  document:text </CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â  ZIPPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â  GAPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â  TEXTPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â  Â Â HTMLPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â  EMAILPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â  ArcPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â  RecPlug</CodeLine>
+<CodeLine>classifyÂ Â Â Â Â Â  AZList -metadata "Title"</CodeLine>
+<CodeLine>collectionmeta collectionnameÂ Â Â  "dlpeople"</CodeLine>
+<CodeLine>collectionmeta iconcollectionÂ Â Â  ""</CodeLine>
+<CodeLine>collectionmeta collectionextraÂ Â  ""</CodeLine>
+<CodeLine>collectionmeta .document:textÂ Â Â  "documents"</CodeLine>
+</Figure>
+<Text id="38">Puede acceder al contenido de este directorio tecleandoÂ <i>dir</i>. DeberÃ­a haber siete subdirectorios:Â <i>archives, building, etc, images, import, index</i>Â yÂ <i>perllib</i>.</Text>
+<Text id="39">Ahora debemos introducir documentos de muestra en la colecciÃ³n. Los documentos de origen para la colecciÃ³nÂ <i>dlpeople</i>Â pueden encontrarse en el directorioÂ <i>collect\dlpeople</i>Â del CD-ROM de distribuciÃ³n Greenstone. En primer lugar, inserte el CD-ROM en el lector (por ejemplo en la unidadÂ <i>D:\</i>). A continuaciÃ³n, copie el contenido del directorioÂ <i>D:\collect\dlpeople</i>Â en el directorioÂ <i>import</i>Â de la colecciÃ³nÂ <i>dlpeople</i>. Para ello, proceda de la manera siguiente:</Text>
+<Indented>
+<Text id="40">seleccione el contenido del directorioÂ <i>dlpeople</i> y arrÃ¡strelo al directorioÂ <i>import</i>Â de la colecciÃ³nÂ <i>dlpeople</i>.</Text>
+</Indented>
+<Text id="41">Como alternativa, puede teclear el comando</Text>
+<CodeLine>xcopyÂ  /sÂ  d:\collect\dlpeople\* import</CodeLine>
+<Text id="42">En el directorioÂ <i>etc</i>Â de la colecciÃ³n hay un archivo denominadoÂ <i>collect.cfg</i>. Ãbralo con el editor de texto que prefiera; uno bÃ¡sico pero que es fÃ¡cil de conseguir se llamaÂ <i>edit</i>. El resultado deberÃ­a parecerse a la Figura <CrossRef target="Figure" ref="collection_configuration_file_created_by_mkcol"/>, que muestra el archivo de configuraciÃ³n de la colecciÃ³n creado mediante el comandoÂ <i>perlÂ  âS mkcol.pl âcreatorme@cs.waikato.ac.nz dlpeople</i>.</Text>
+<Text id="43">Ahora puede âimportarâ la colecciÃ³n. Se trata del proceso por el que se traen los documentos al sistema Greenstone, normalizando el formato de los documentos, el modo en que se especifican los metadatos y la estructura de los archivos en que se almacenan los documentos. TecleeÂ <i>perl âS import.pl</i>Â en el indicador para obtener una lista de todas las opciones del programa de importaciÃ³n. Para simplificar, limÃ­tese al comando bÃ¡sico</Text>
+<CodeLine>perl âS import.pl dlpeople</CodeLine>
+<Text id="44">No se preocupe por el texto que desfila rÃ¡pidamente en la pantalla: es sÃ³lo un informe de la progresiÃ³n de la importaciÃ³n. Tenga en cuenta que importar esta colecciÃ³n lleva unos cinco minutos en una computadora de 1 GHz y, por consiguiente, mÃ¡s tiempo en mÃ¡quinas mÃ¡s lentas. ObsÃ©rvese que no es necesario encontrarse en los directoriosÂ <i>collect</i>Â oÂ <i>dlpeople</i>Â cuando se selecciona este comando, porque ya se ha introducido la variable GSDLHOME y el programa Greenstone puede encontrar todos los archivos necesarios.</Text>
+<Text id="45">Ahora vamos a introducir algunas modificaciones en el archivo de configuraciÃ³n de la colecciÃ³n para personalizar su apariencia. En primer lugar, demos un nombre a la colecciÃ³n. SerÃ¡ el que utilicen los navegadores Web como tÃ­tulo de pÃ¡gina de la portada de la colecciÃ³n, y servirÃ¡ como icono de la colecciÃ³n si no se proporciona ninguna otra imagen. Sustituya la lÃ­nea que diceÂ <i>collectionmeta collectionname âdlpeopleâ</i>Â por algo comoÂ <i>collectionmeta collectionname âLos miembros del proyecto NZDLâ.</i></Text>
+<Text id="46">AÃ±ada una descripciÃ³n de su colecciÃ³n entre las comillas de la lÃ­neaÂ <i>collectionmeta collectionextra</i>Â ââ, la cual servirÃ¡ como texto delÂ <i>Acerca de esta colecciÃ³n</i>Â en la pÃ¡gina principal de la colecciÃ³n. Yo escribÃ­ âEsta colecciÃ³n comprende las pÃ¡ginas personales de algunas de las personas que han colaborado en el proyecto NZDLâ. Es importante escribir este texto en el editor en una sola lÃ­nea: si el cursor llega al margen derecho de la ventana del editor no pulse la tecla âIntroâ aunque tenga que aÃ±adir mÃ¡s texto; siga escribiendo de continuo, de lo contrario el archivo de configuraciÃ³n no podrÃ¡ ser analizado correctamente. Si desea que su colecciÃ³n pueda utilizarse con diferentes interfaces de lenguas, existe una opciÃ³n para que este texto aparezca de manera diferente segÃºn la interfaz lingÃŒÃ­stica elegida, que se describe mÃ¡s adelante en la SecciÃ³n <CrossRef target="Section" ref="import_and_build_processes"/>.</Text>
+<Text id="47">Puede utilizar cualquier imagen que pueda visualizarse en un navegador como icono de la colecciÃ³n; la imagen que yo creÃ© se muestra en la Figura <CrossRef target="Figure" ref="collection_icon"/>. Escriba la ubicaciÃ³n de la imagen entre las comillas de la lÃ­neaÂ <i>collectionmeta iconcollection ââ</i>Â en el archivo de configuraciÃ³n. Como abreviaciÃ³n, y para contribuir a la portabilidad, puede utilizarse <i>_httpprefix_</i>Â como inicio de una direcciÃ³n URL que remite a una imagen situada en la zona de archivos de Greenstone. Por ejemplo, puede usted escribir: _Â <i>httpprefix_/collect/dlpeople/images/icon.gif</i>Â si ha introducido una imagen adecuada en el directorioÂ <i>images</i>Â de la colecciÃ³n (Â <i>collect\dlpeople\images</i>Â en nuestro ejemplo).</Text>
+<Text id="48">Guarde el archivo de configuraciÃ³n de la colecciÃ³n y ciÃ©rrelo; no lo necesitarÃ¡ de nuevo en este manual de instrucciones.</Text>
+<Text id="49">La siguiente fase consiste en âcrearâ la colecciÃ³n, es decir, elaborar todos los Ã­ndices y archivos que permiten su funcionamiento. TecleeÂ <i>perl âS buildcol.pl</i>Â en el indicador de comandos para acceder a una lista de opciones de creaciÃ³n de colecciÃ³n, que se explican mÃ¡s detalladamente en la SecciÃ³n <CrossRef target="Section" ref="import_and_build_processes"/>. Por ahora, cÃ­Ã±ase a los valores por defecto y teclee:</Text>
+<CodeLine>perl âS buildcol.pl dlpeople</CodeLine>
+<Text id="50">Una vez mÃ¡s, no se preocupe por los textos de âinforme de progresiÃ³nâ que desfilan por la pantalla.</Text>
+<Text id="51">Active la colecciÃ³n como sigue: </Text>
+<Text id="52">seleccione el contenido del directorioÂ <i>building</i>Â de la colecciÃ³nÂ <i>dlpeople</i> y arrÃ¡strelo hasta el directorioÂ <i>index</i>.</Text>
+<Text id="53">Como alternativa, puede suprimir el directorioÂ <i>index</i>Â (y todo su contenido) con el comando:</Text>
+<CodeLine>rd /s indexÂ Â Â Â Â Â Â Â  # con Windows NT/2000</CodeLine>
+<CodeLine>deltree /Y indexÂ Â Â  # con Windows 95/98</CodeLine>
+<Text id="54">y luego cambiar el nombre del directorioÂ <i>building</i>Â por el deÂ <i>index</i>Â tecleando:</Text>
+<CodeLine>ren building index</CodeLine>
+<Text id="55">Por Ãºltimo, teclee:</Text>
+<CodeLine>mkdir building </CodeLine>
+<Text id="56">en preparaciÃ³n para cualquier recreaciÃ³n futura. Es importante que estos comandos se efectÃºen en el directorio correcto (a diferencia de los comandosÂ <i>mkcol.pl</i>,Â <i>import.pl</i>Â yÂ <i>buildcol.pl</i>Â de Greenstone). Si el directorio que se encuentra en uso no esÂ <i>dlpeople</i>, tecleeÂ <i>cd â%GSDLHOME%\collect\dlpeopleâ</i>Â antes de proceder a la secuencia de operacionesÂ <i>rd</i>,Â <i>ren</i>Â yÂ <i>mkdir</i>Â antes expuestas.</Text>
+<Text id="57">DeberÃ­a poder acceder a la colecciÃ³n reciÃ©n creada desde la pÃ¡gina principal de Greenstone. TendrÃ¡ que volver a cargar la pÃ¡gina si ya la habÃ­a abierto en su navegador, o tal vez incluso tenga que cerrar el navegador y arrancarlo de nuevo (para evitar problemas de âÂ <i>cache</i>Â â). En cambio, si estÃ¡ utilizando la versiÃ³n âBiblioteca Localâ de Greenstone tendrÃ¡ que volver a arrancar el programaÂ <i>library</i>. Para visualizar la nueva colecciÃ³n, haga clic en la imagen. El resultado deberÃ­a parecerse a la Figura <CrossRef target="Figure" ref="about_page_for_the_new_collection"/>.</Text>
+<Figure id="collection_icon">
+<Title>
+<Text id="58">Icono de la colecciÃ³n</Text>
+</Title>
+<File width="150" height="80" url="images/Dev_Fig_2.png"/>
+</Figure>
+<Text id="59">En resumen, los comandos que se han de teclear para general la colecciÃ³nÂ <i>dlpeople</i>Â son los siguientes:</Text>
+<CodeLine>cd âC:\Program Files\gsdlâ # se supone la ubicaciÃ³n por defecto</CodeLine>
+<CodeLine>setup.bat</CodeLine>
+<CodeLine>perl âS mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<CodeLine>cd â%GSDLHOME%\collect\dlpeopleâ</CodeLine>
+<CodeLine>xcopy /s d:\collect\dlpeople\* import # se supone la unidad D</CodeLine>
+<CodeLine>perl âS import.pl dlpeople</CodeLine>
+<CodeLine>perl âS buildcol.pl dlpeople</CodeLine>
+<CodeLine>rdÂ  /s indexÂ Â Â Â Â Â Â Â Â Â Â Â Â Â  # con Windows NT/2000</CodeLine>
+<CodeLine>deltreeÂ  /Y index Â Â Â Â Â Â Â Â  # con Windows 95/98</CodeLine>
+<CodeLine>ren building index</CodeLine>
+<CodeLine>mkdir building</CodeLine>
+</Content>
+</Subsection>
+<Subsection id="collection_building_under_unix">
+<Title>
+<Text id="60">CreaciÃ³n de colecciones bajo Unix</Text>
+</Title>
+<Content>
+<Text id="61">En primer lugar vaya al directorio donde estÃ¡ instalado Greenstone. Por ejemplo, si Greenstone estÃ¡ instalado en vuestro directorio de inicio de sesiÃ³n, con su nombre por defecto, puede dirigirse allÃ­ tecleando</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<Text id="62">Luego en el indicador, teclee</Text>
+<CodeLine>source setup.bashÂ Â  # si estÃ¡ utilizando el shell BASH</CodeLine>
+<CodeLine>source setup.cshÂ Â Â  # si estÃ¡ utilizando el shell C</CodeLine>
+<Text id="63">Estos archivos de ejecuciÃ³n por lotes (que puede usted leer si lo desea) indican al sistema dÃ³nde buscar los programas Greenstone. Si mÃ¡s adelante, durante su sesiÃ³n de introducciÃ³n de lÃ­neas de comando en Greenstone, desea volver al directorio principal de Greenstone, puede hacerlo escribiendoÂ <i>cd $GSDLHOME</i>.</Text>
+<Text id="64">Si no estÃ¡ seguro del tipo de intÃ©rprete de comandos (<i>shell</i>) que estÃ¡ utilizando, tecleeÂ <i>echo $0</i>Â en su indicador de lÃ­nea de comandos y obtendrÃ¡ la informaciÃ³n buscada. Si utiliza un intÃ©rprete de comandos diferente, contacte a su administrador de sistema para que le asesore.</Text>
+<Text id="65">Una vez localizado el archivo de instalaciÃ³n adecuado, estamos en condiciones de constituir, crear y recrear colecciones. El primer programa que examinaremos es el programa PerlÂ <i>mkcol.pl</i>, cuyo nombre corresponde a âmake a collectionâ (constituir una colecciÃ³n). En primer lugar, active el programa escribiendo sÃ³loÂ <i>mkcol.pl</i>Â para obtener en pantalla una descripciÃ³n de la sintaxis y una lista de argumentos. Como puede comprobarlo en el mensaje que aparece, el Ãºnico argumento necesario esÂ <i>creator</i>, que se utiliza para especificar quiÃ©n ha creado la colecciÃ³n.</Text>
+<Figure id="about_page_for_the_new_collection">
+<Title>
+<Text id="66">PÃ¡gina âAcerca deâ de la nueva colecciÃ³n</Text>
+</Title>
+<File width="604" height="415" url="images/Dev_Fig_3.png"/>
+</Figure>
+<Text id="67">Utilicemos ahora este comando para crear los archivos y subdirectorios iniciales necesarios para nuestra colecciÃ³n de las pÃ¡ginas personales de los miembros del proyecto de Biblioteca Digital Greenstone. Para asignar a la colecciÃ³n el nombreÂ <i>dlpeople</i>, esto fue lo que escribÃ­:</Text>
+<CodeLine>mkcol.pl âcreatorme@cs.waikato.ac.nzdlpeople</CodeLine>
+<Text id="68">Â¡No olvide sustituir mi direcciÃ³n de correo electrÃ³nico por la suya!</Text>
+<Text id="69">Para poder visualizar los archivos reciÃ©n creados, vaya al directorio reciÃ©n creado de la colecciÃ³n tecleando:</Text>
+<CodeLine>cd $GSDLHOME/collect/dlpeople</CodeLine>
+<Text id="70">Puede acceder al contenido de este directorio tecleandoÂ <i>ls</i>. DeberÃ­a haber siete subdirectorios:Â <i>archives, building, etc, images, import, index</i>Â yÂ <i>perllib</i>.</Text>
+<Text id="71">Ahora debemos introducir documentos de muestra en la colecciÃ³n. Los documentos de origen para la colecciÃ³nÂ <i>dlpeople</i>Â pueden encontrarse en el directorioÂ <i>collect\dlpeople</i>Â del CD-ROM de distribuciÃ³n Greenstone. Para leer la informaciÃ³n de un CD-ROM con Linux, inserte el disco en el lector y teclee:</Text>
+<CodeLine>mount /cdrom</CodeLine>
+<Text id="72">en el indicador (este comando puede cambiar de un sistema a otro). Una vez montado, el CD-ROM puede usarse como cualquier otro directorio, por consiguiente puede teclearÂ <i>ls /cdrom/collect</i>. Esto deberÃ­a darle acceso a un directorio denominadoÂ <i>dlpeople</i>Â en el CD-ROM.</Text>
+<Text id="73">A continuaciÃ³n, copie el contenido del directorioÂ <i>/cdrom/collect/dlpeople</i>Â en el directorioÂ <i>GSDLHOME/collect/dlpeople/import</i>. Para ello, teclee el comando:</Text>
+<CodeLine>cp âr /cdrom/collect/dlpeople/*Â  import/</CodeLine>
+<Text id="74">Luego teclee:</Text>
+<CodeLine>umount /cdrom</CodeLine>
+<Text id="75">para cerrar la unidad del CD-ROM.</Text>
+<Text id="76">En el directorioÂ <i>etc</i>Â de la colecciÃ³n hay un archivo denominadoÂ <i>collect.cfg</i>. Ãbralo con el editor de texto que prefiera;Â <i>emacs</i>Â es un editor muy utilizado en Linux. El resultado deberÃ­a parecerse a la Figura <CrossRef target="Figure" ref="collection_configuration_file_created_by_mkcol"/>, que muestra el archivo de configuraciÃ³n de la colecciÃ³n creado mediante el comandoÂ <i>mkcol.pl âcreatorme@cs.waikato.ac.nz dlpeople</i>.</Text>
+<Text id="77">Ahora puede âimportarâ la colecciÃ³n. Se trata del proceso por el que se traen los documentos al sistema Greenstone, normalizando el formato de los documentos, el modo en que se especifican los metadatos y la estructura de los archivos en que se almacenan los documentos. TecleeÂ <i>import.pl</i>Â en el indicador para obtener una lista de todas las opciones del programa de importaciÃ³n. Para simplificar, limÃ­tese al comando bÃ¡sico</Text>
+<CodeLine>import.pl dlpeople</CodeLine>
+<Text id="78">No se preocupe por el texto que desfila rÃ¡pidamente en la pantalla: es sÃ³lo un informe de la progresiÃ³n de la importaciÃ³n. Tenga en cuenta que importar esta colecciÃ³n lleva unos cinco minutos en una computadora de 1 GHz y, por consiguiente, mÃ¡s tiempo en mÃ¡quinas mÃ¡s lentas. ObsÃ©rvese que no es necesario encontrarse en los directoriosÂ <i>collect</i>Â oÂ <i>dlpeople</i>Â cuando se selecciona este comando, porque ya se ha introducido la variable GSDLHOME y el programa Greenstone puede encontrar todos los archivos necesarios.</Text>
+<Text id="79">Ahora vamos a introducir algunas modificaciones en el archivo de configuraciÃ³n de la colecciÃ³n para personalizar su apariencia. En primer lugar, demos un nombre a la colecciÃ³n. SerÃ¡ el que utilicen los navegadores Web como tÃ­tulo de pÃ¡gina de la portada de la colecciÃ³n, y servirÃ¡ como icono de la colecciÃ³n si no se proporciona ninguna otra imagen. Sustituya la lÃ­nea que diceÂ <i>collectionmeta collectionname âdlpeopleâ</i>Â por algo comoÂ <i>collectionmeta collectionname âLos miembro+s del proyecto NZDLâ.</i></Text>
+<Text id="80">AÃ±ada una descripciÃ³n de su colecciÃ³n entre las comillas de la lÃ­neaÂ <i>collectionmeta collectionextra</i>Â ââ, la cual servirÃ¡ como texto delÂ <i>Acerca de esta colecciÃ³n</i>Â en la pÃ¡gina principal de la colecciÃ³n. Yo escribÃ­ âEsta colecciÃ³n comprende las pÃ¡ginas personales de algunas de las personas que han colaborado en el proyecto NZDLâ. Es importante escribir este texto en el editor en una sola lÃ­nea: si el cursor llega al margen derecho de la ventana del editor no pulse la tecla âIntroâ aunque tenga que aÃ±adir mÃ¡s texto; siga escribiendo de continuo, de lo contrario el archivo de configuraciÃ³n no podrÃ¡ ser analizado correctamente. Si desea que su colecciÃ³n pueda utilizarse con diferentes interfaces de lenguas, existe una opciÃ³n para que este texto aparezca de manera diferente segÃºn la interfaz lingÃŒÃ­stica elegida, que se describe mÃ¡s adelante en la SecciÃ³n <CrossRef target="Section" ref="import_and_build_processes"/>.</Text>
+<Text id="81">Puede utilizar cualquier imagen que pueda visualizarse en un navegador como icono de la colecciÃ³n; la imagen que yo creÃ© se muestra en la Figura <CrossRef target="Figure" ref="collection_icon"/>. Escriba la ubicaciÃ³n de la imagen entre las comillas de la lÃ­neaÂ <i>collectionmeta iconcollection ââ</i>Â en el archivo de configuraciÃ³n. Como abreviaciÃ³n, y para contribuir a la portabilidad, puede utilizarse _Â <i>httpprefix_</i>Â como inicio de una direcciÃ³n URL que remite a una imagen situada en la zona de archivos de Greenstone. Por ejemplo, puede usted escribir: _Â <i>httpprefix_/collect/dlpeople/images/icon.gif</i>Â si ha introducido una imagen adecuada en el directorioÂ <i>images</i>Â de la colecciÃ³n (Â <i>collect\dlpeople\images</i>Â en nuestro ejemplo).</Text>
+<Text id="82">Guarde el archivo de configuraciÃ³n de la colecciÃ³n y ciÃ©rrelo; no lo necesitarÃ¡ de nuevo en este manual de instrucciones.</Text>
+<Text id="83">La siguiente fase consiste en âcrearâ la colecciÃ³n, es decir, elaborar todos los Ã­ndices y archivos que permiten su funcionamiento. TecleeÂ <i>buildcol.pl</i>Â en el indicador de comandos para acceder a una lista de opciones de creaciÃ³n de colecciÃ³n, que se explican mÃ¡s detalladamente en la SecciÃ³n <CrossRef target="Section" ref="import_and_build_processes"/>. Por ahora, cÃ­Ã±ase a los valores por defecto por defecto y teclee:</Text>
+<CodeLine>buildcol.pl dlpeople</CodeLine>
+<Text id="84">Una vez mÃ¡s, no se preocupe por los textos de âinforme de progresiÃ³nâ que desfilan por la pantalla.</Text>
+<Text id="85">Active la colecciÃ³n trasladando al directorioÂ <i>index</i>Â todos los datos que acaba de introducir en el directorioÂ <i>building</i>Â de la colecciÃ³n. Si ya ha creado esta colecciÃ³n anteriormente, en primer lugar suprima el antiguo Ã­ndice tecleando:</Text>
+<CodeLine>rm âr index/*</CodeLine>
+<Text id="86">(suponiendo que se encuentre en el directorioÂ <i>dlpeople</i>) en el indicador. A continuaciÃ³n teclee:</Text>
+<CodeLine>mv building/*Â  index/</CodeLine>
+<Table id="collection-building_differences_between_windows_and_linux">
+<Title>
+<Text id="87">Diferencias entre Windows y Linux para la creaciÃ³n de colecciones</Text>
+</Title>
+<TableContent>
+<tr>
+<th>
+<Text id="88"><b>Windows</b></Text>
+</th>
+<th>
+<Text id="89"><b>Linux</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="90">EjecutarÂ <i>setup.bat</i>Â para poder acceder a los programas Greenstone</Text>
+</th>
+<th>
+<Text id="91">CargarÂ <i>setup.bash</i>Â oÂ <i>setup.csh</i>Â para poder acceder a los programas</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="92">Copiar los archivos del CD-ROM utilizando el administrador grÃ¡fico de archivos o los comandos de Windows</Text>
+</th>
+<th>
+<Text id="93">Copiar los archivos del CD-ROM utilizandoÂ <i>mount</i>Â y los comandos de Unix</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="94">El directorioÂ <i>index</i>Â de la antigua colecciÃ³n se sustituye tecleandoÂ <i>rd /s index</i>, luegoÂ <i>ren building index</i>Â seguido deÂ <i>mkdir building</i>, o utilizando el administrador de archivos grÃ¡ficos.</Text>
+</th>
+<th>Â </th>
+<th>
+<Text id="95">El directorioÂ <i>index</i>Â de la antigua colecciÃ³n se sustituye tecleandoÂ <i>rm âr index/</i>Â * luegoÂ <i>mv building/* index</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="96">DeberÃ­a poder acceder a la colecciÃ³n reciÃ©n creada desde la pÃ¡gina principal de Greenstone. TendrÃ¡ que volver a cargar la pÃ¡gina si ya la habÃ­a abierto en su navegador, o tal vez incluso tenga que cerrar el navegador y arrancarlo de nuevo (para evitar problemas de âÂ <i>cache</i>Â â). Para visualizar la nueva colecciÃ³n, haga clic en la imagen. El resultado deberÃ­a parecerse a la Figura <CrossRef target="Figure" ref="about_page_for_the_new_collection"/>.</Text>
+<Text id="97">En resumen, los comandos que se han de teclear para generar la colecciÃ³nÂ <i>dlpeople</i>Â son los siguientes:</Text>
+<CodeLine>cd ~/gsdlÂ Â Â Â Â Â Â Â Â Â  # suponiendo que Greenstone estÃ¡ por defecto</CodeLine>
+<CodeLine># en vuestro directorio de inicio de sesiÃ³n</CodeLine>
+<CodeLine>source setup.bashÂ Â  # si estÃ¡ utilizando el shell BASH</CodeLine>
+<CodeLine>source setup.cshÂ Â Â  # si estÃ¡ utilizando el shell C</CodeLine>
+<CodeLine>mkcol.pl âcreatorme@cs.waikato.ac.nzdlpeople</CodeLine>
+<CodeLine>cd $GSDLHOME/collect/dlpeople</CodeLine>
+<CodeLine>mount /cdromÂ Â Â Â Â Â Â  # suponiendo que el CD-ROM se asigna ahÃ­</CodeLine>
+<CodeLine>cp âr /cdrom/collect/dlpeople/ * import/</CodeLine>
+<CodeLine>umount /cdrom</CodeLine>
+<CodeLine>import.pl dlpeople</CodeLine>
+<CodeLine>buildcol.pl dlpeople</CodeLine>
+<CodeLine>rm âr index/*</CodeLine>
+<CodeLine>mv building/* index</CodeLine>
+</Content>
+</Subsection>
+<Subsection id="differences_between_windows_and_unix">
+<Title>
+<Text id="98">Diferencias entre Windows y Unix</Text>
+</Title>
+<Content>
+<Text id="99">El proceso de creaciÃ³n de una colecciÃ³n con Unix es muy parecido al de Windows, pero hay algunas pequeÃ±as diferencias que se resumen en el Cuadro <CrossRef target="Table" ref="collection-building_differences_between_windows_and_linux"/>.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="greenstone_directories">
+<Title>
+<Text id="100">Directorios de Greenstone</Text>
+</Title>
+<Content>
+<Text id="101">En la Figura <CrossRef target="Figure" ref="structure_of_the_gsdlhome_directory"/> se muestra la estructura del directorioÂ <i>GSDLHOME</i>. En el Cuadro <CrossRef target="Table" ref="where_to_find_information_about_directories"/> se presenta una breve descripciÃ³n del contenido de cada uno de los directorios que aparecen en el diagrama. En una secciÃ³n ulterior del manual se detallan mÃ¡s algunos directorios; utilice la guÃ­a de secciones del Cuadro <CrossRef target="Table" ref="where_to_find_information_about_directories"/> para saber dÃ³nde hallar mÃ¡s informaciÃ³n.</Text>
+<Figure id="structure_of_the_gsdlhome_directory">
+<Title>
+<Text id="102">Estructura del directorio GSDLHOME</Text>
+</Title>
+<File width="603" height="197" url="images/Dev_Fig_4.png"/>
+</Figure>
+<Table id="where_to_find_information_about_directories">
+<Title>
+<Text id="103">DÃ³nde encontrar informaciÃ³n sobre los directorios</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="@width"/>
+<th>
+<Text id="104"><b>Contenido</b></Text>
+</th>
+<th>
+<Text id="105"><b>SecciÃ³n</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="106"><i>bin</i></Text>
+</th>
+<th>
+<Text id="107">CÃ³digo ejecutable, que incluye binarios en el directorio que lleva el nombre de su sistema operativo.</Text>
+</th>
+<th>
+<Text id="108">-</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="109"><i>bin/script</i></Text>
+</th>
+<th>
+<Text id="110">Guiones Perl utilizados para crear y constituir colecciones (por ejemplo,Â <i>import.pl</i>Â yÂ <i>buildcol.pl</i>). Para obtener una descripciÃ³n de cualquiera de estos programas, teclee su nombre en el indicador de comandos.</Text>
+</th>
+<th>
+<Text id="111">1.3</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="112"><i>perllib</i></Text>
+</th>
+<th>
+<Text id="113">MÃ³dulos Perl utilizados durante la importaciÃ³n y la creaciÃ³n (conectores, por ejemplo).</Text>
+</th>
+<th>
+<Text id="114">2.1</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="115"><i>perllib/plugins</i></Text>
+</th>
+<th>
+<Text id="116">CÃ³digo Perl para los conectores de tratamiento de documentos.</Text>
+</th>
+<th>
+<Text id="117">2.1</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="118"><i>perllib/classify</i></Text>
+</th>
+<th>
+<Text id="119">CÃ³digo Perl para clasificadores (por ejemplo, el cÃ³digo AZList que elabora una lista de documentos basada en el orden alfabÃ©tico de un atributo).</Text>
+</th>
+<th>
+<Text id="120">2.2</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="121"><i>cgi-bin</i></Text>
+</th>
+<th>
+<Text id="122">Todos los guiones CGI de Greenstone que se trasladan al directorioÂ <i>cgi-bin</i>Â del sistema.</Text>
+</th>
+<th>
+<Text id="123">-</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="124"><i>tmp</i></Text>
+</th>
+<th>
+<Text id="125">Directorio utilizado por Greenstone para almacenar archivos temporales.</Text>
+</th>
+<th>
+<Text id="126">-</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="127"><i>etc</i></Text>
+</th>
+<th>
+<Text id="128">Archivos de configuraciÃ³n, registros de inicializaciÃ³n y de errores, bases de datos de autorizaciÃ³n de usuarios.</Text>
+</th>
+<th>
+<Text id="129">-</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="130"><i>src</i></Text>
+</th>
+<th>
+<Text id="131">CÃ³digo C++ utilizado para suministrar colecciones a travÃ©s de un servidor Web.</Text>
+</th>
+<th>
+<Text id="132">3</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="133"><i>src/colservr</i></Text>
+</th>
+<th>
+<Text id="134">CÃ³digo C++ para suministrar colecciones, responder a consultas y demÃ¡s.</Text>
+</th>
+<th>
+<Text id="135"><CrossRef target="Section" ref="protocol"/></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="136"><i>src/recpt</i></Text>
+</th>
+<th>
+<Text id="137">CÃ³digo C++ para obtener consultas desde la interfaz de usuario y formatear las respuestas para esta interfaz.</Text>
+</th>
+<th>
+<Text id="138">3.8</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="139"><i>packages</i></Text>
+</th>
+<th>
+<Text id="140">CÃ³digos fuente para paquetes de programas informÃ¡ticos ajenos a Greenstone pero utilizados por Ã©ste.</Text>
+</th>
+<th>
+<Text id="141">2.5</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="142"><i>packages/mg</i></Text>
+</th>
+<th>
+<Text id="143">El cÃ³digo fuente de MG, programa de compresiÃ³n e indizaciÃ³n utilizado por Greenstone.</Text>
+</th>
+<th>
+<Text id="144">2.5</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="145"><i>mappings</i></Text>
+</th>
+<th>
+<Text id="146">Cuadros de correspondencia Unicode (por ejemplo para los caracteres chinos GB).</Text>
+</th>
+<th>
+<Text id="147">-</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="148"><i>macros</i></Text>
+</th>
+<th>
+<Text id="149">Los archivos de macros utilizados para la interfaz de usuario.</Text>
+</th>
+<th>
+<Text id="150">2.4</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="151"><i>collect</i></Text>
+</th>
+<th>
+<Text id="152">Colecciones que se suministran a partir de este ejemplar de Greenstone.</Text>
+</th>
+<th>
+<Text id="153">1.1 </Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="154"><i>lib</i></Text>
+</th>
+<th>
+<Text id="155">CÃ³digo fuente C++ utilizado por el servidor de colecciÃ³n y por el recepcionista. </Text>
+</th>
+<th>
+<Text id="156">3.1</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="157"><i>images</i></Text>
+</th>
+<th>
+<Text id="158">ImÃ¡genes utilizadas en la interfaz de usuario.</Text>
+</th>
+<th>
+<Text id="159">-</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="160"><i>docs</i></Text>
+</th>
+<th>
+<Text id="161">DocumentaciÃ³n.</Text>
+</th>
+<th>
+<Text id="162">-</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Section>
+<Section id="import_and_build_processes">
+<Title>
+<Text id="163">Procesos de importaciÃ³n y de creaciÃ³n</Text>
+</Title>
+<Content>
+<Text id="164">En el proceso de creaciÃ³n de la colecciÃ³n explicado en la SecciÃ³n <CrossRef target="Section" ref="building_collections_from_the_command_line"/> se utiliza un comando,Â <i>import.pl</i>, para importar los documentos y otro,Â <i>buildcol.pl</i>, para crear la colecciÃ³n. En esta secciÃ³n ampliamos la informaciÃ³n sobre las funciones y opciones de estos programas. Empleamos la variableÂ <i>nombre_col</i>Â para referirnos a la colecciÃ³n en proceso de creaciÃ³n o importaciÃ³n.</Text>
+<Text id="165">Los procesos de importaciÃ³n y creaciÃ³n guardan muchas semejanzas y, por consiguiente, muchas de sus opciones, expuestas en el Cuadro <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/>, son iguales. (Recuerde que para ver las opciones de cualquier guiÃ³n de Greenstone sÃ³lo tiene que escribir su nombre sin opciones en el indicador de comandos).</Text>
+<Table id="options_for_the_import_and_build_processes">
+<Title>
+<Text id="166">Opciones de los procesos de importaciÃ³n y de creaciÃ³n</Text>
+</Title>
+<TableContent>
+<tr>
+<th>Â </th>
+<th>
+<Text id="167"><b>Argumento</b></Text>
+</th>
+<th>
+<Text id="168"><b>FunciÃ³n</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="169"><i>-verbosity</i></Text>
+</th>
+<th>
+<Text id="170">NÃºmero 0-3</Text>
+</th>
+<th>
+<Text id="171">Controla la cantidad de informaciÃ³n sobre el proceso que se visualiza como error estÃ¡ndar: 0 significa un poco, 3 mucho.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="172"><i>-archivedir</i></Text>
+</th>
+<th>
+<Text id="173">Nombre de directorio</Text>
+</th>
+<th>
+<Text id="174">Especifica dÃ³nde estÃ¡n almacenados los archivos en el Format de Archivo Greenstone (<i>Greenstone Archive Files</i>), esto es, dÃ³nde los guardaÂ <i>import.pl</i>Â y donde los encuentraÂ <i>buildcol.pl</i>. El valor por defecto esÂ <i>GSDLHOME/collect/nombre_col/archives.</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="175"><i>-maxdocs</i></Text>
+</th>
+<th>
+<Text id="176">NÃºmero &gt;0</Text>
+</th>
+<th>
+<Text id="177">Indica el nÃºmero mÃ¡ximo de documentos que se pueden importar o crear. Esta opciÃ³n es Ãºtil cuando se prueba el archivo de configuraciÃ³n de una nueva colecciÃ³n o se ensayan nuevos conectores.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="178"><i>-collectdir</i></Text>
+</th>
+<th>
+<Text id="179">Nombre de directorio</Text>
+</th>
+<th>
+<Text id="180">Especifica dÃ³nde se puede encontrar la colecciÃ³n. El valor por defecto esÂ <i>GSDLHOME/collect</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="181"><i>-out</i></Text>
+</th>
+<th>
+<Text id="182">Nombre de archivo</Text>
+</th>
+<th>
+<Text id="183">Especifica un archivo en el que se escriben todos los mensajes producidos, que por defecto se visualizan como error estÃ¡ndar (esto es, en la pantalla). OpciÃ³n Ãºtil cuando se trabaja con niveles de depuraciÃ³n.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="184"><i>-keepold</i></Text>
+</th>
+<th>
+<Text id="185">Ninguno</Text>
+</th>
+<th>
+<Text id="186">No suprime el resultado de la operaciÃ³n de importaciÃ³n o creaciÃ³n anterior. En caso de importaciÃ³n, no suprime el contenido del directorioÂ <i>archives</i>Â ; en caso de creaciÃ³n, no suprime el contenido del directorioÂ <i>building</i>.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="187"><i>-debug</i></Text>
+</th>
+<th>
+<Text id="188">Ninguno</Text>
+</th>
+<th>
+<Text id="189">Muestra la salida del conector en la salida estÃ¡ndar.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Subsection id="subsection_el_proceso_de_importaciÃ³n">
+<Title>
+<Text id="190">El proceso de importaciÃ³n</Text>
+</Title>
+<Content>
+<Text id="191">La principal funciÃ³n del proceso de importaciÃ³n es pasar los documentos de su formato original al Formato de Archivo Greenstone (<i>Greenstone Archive Format</i>), asÃ­ como crear un archivo de resumen (denominadoÂ <i>archives.inf</i>) que se utilizarÃ¡ para crear la colecciÃ³n.Â <i>import.pl</i>Â necesita saber quÃ© conectores se han de utilizar y dÃ³nde encontrar los archivos de los documentos originales. En el Cuadro <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/> se muestran las opciones comunes de los procesos de importaciÃ³n y de creaciÃ³n; en el Cuadro <CrossRef target="Table" ref="additional_options_for_the_import_process"/> se presentan las opciones adicionales aplicables sÃ³lo al proceso de importaciÃ³n. La opciÃ³nÂ <i>OIDtype</i>Â requiere ciertas explicaciones. Cada documento tiene un identificador de objeto asociado (Â <i>Object Identifier</i>) u OID. La mejor manera de calcularlo es que el programa desmenuce el contenido del documento (Â <i>hash</i>). Sin embargo, este procedimiento es lento, por ello se propone una alternativa mÃ¡s sencilla (Â <i>incremental</i>) que simplemente numera los documentos secuencialmente en el orden de importaciÃ³n (mÃ©todo por incremento gradual). Puede usted utilizar el mÃ©todoÂ <i>incremental</i>Â para ir mÃ¡s rÃ¡pido, pero debe emplearÂ <i>hash</i>Â si quiere aÃ±adir documentos a su colecciÃ³n en una fecha ulterior (sin volver a importar).</Text>
+<Table id="additional_options_for_the_import_process">
+<Title>
+<Text id="192">Opciones adicionales del proceso de importaciÃ³n</Text>
+</Title>
+<TableContent>
+<tr>
+<th>Â </th>
+<th>
+<Text id="193"><b>Argumento</b></Text>
+</th>
+<th>
+<Text id="194"><b>FunciÃ³n</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="195"><i>-importdir</i></Text>
+</th>
+<th>
+<Text id="196">Nombre de directorio</Text>
+</th>
+<th>
+<Text id="197">Indica dÃ³nde se puede encontrar el material que se ha de importar. El valor por defecto esÂ <i>GSDLHOME/collect/nombre_col/archives.</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="198"><i>-removeold</i></Text>
+</th>
+<th>
+<Text id="199">Ninguno</Text>
+</th>
+<th>
+<Text id="200">Suprime el contenido del directorioÂ <i>archives</i>Â antes de importar.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="201"><i>-gzip</i></Text>
+</th>
+<th>
+<Text id="202">Ninguno</Text>
+</th>
+<th>
+<Text id="203">Comprime los documentos de archivos de Greenstone producidos porÂ <i>import</i>Â (ZIPPlug debe formar parte de la lista de conectores yÂ <i>gzip</i>Â ha de estar instalado en su computadora).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="204"><i>-groupsize</i></Text>
+</th>
+<th>
+<Text id="205">NÃºmero &gt;0</Text>
+</th>
+<th>
+<Text id="206">NÃºmero de documentos que se pueden reunir en un archivo en el Format de Archivo de Greenstone. El valor por defecto es 1 (esto es, un documento por archivo).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="207"><i>-sortmeta</i></Text>
+</th>
+<th>
+<Text id="208">Nombre de etiqueta de metadatos</Text>
+</th>
+<th>
+<Text id="209">Clasifica alfabÃ©ticamente los documentos segÃºn el contenido de la etiqueta de metadatos. Sin embargo, esta funciÃ³n queda invalidada si la colecciÃ³n tiene mÃ¡s de un grupo en la colecciÃ³n (por ejemplo,Â <i>groupsize</i>Â &gt;1).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="210"><i>-OIDtype</i></Text>
+</th>
+<th>
+<Text id="211">hasho incremental</Text>
+</th>
+<th>
+<Text id="212">MÃ©todo de creaciÃ³n de las OID para los documentos:Â <i>hash</i>Â desmenuza el contenido pero es lento;Â <i>incremental</i>Â simplemente asigna nÃºmeros de manera secuencial a los documentos y es mÃ¡s rÃ¡pido.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Figure id="steps_in_the_import_process">
+<Title>
+<Text id="213">Etapas del proceso de importaciÃ³n</Text>
+</Title>
+<File width="604" height="384" url="images/Dev_Fig_5.png"/>
+</Figure>
+<Text id="214">La Figura <CrossRef target="Figure" ref="steps_in_the_import_process"/> representa el proceso de importaciÃ³n efectuado por el programaÂ <i>import.pl</i>. Cada Ã³valo representa un mÃ³dulo utilizado para llevar a cabo tareas relacionadas con una parte especÃ­fica del sistema Greenstone. Todos estos mÃ³dulos pueden encontrarse en el directorioÂ <i>GSDLHOME/perllib</i>.</Text>
+<Text id="215">En la etapa 3, nÃ³tese que las variables de importaciÃ³n comoÂ <i>importdir</i>Â yÂ <i>archivedir</i>Â pueden definirse en el archivo de configuraciÃ³n de la colecciÃ³n o desde la lÃ­nea de comandos. Si se definen desde la lÃ­nea de comandos, se ignorarÃ¡n todos los valores especificados en el archivo de configuraciÃ³n.</Text>
+<Text id="216">En la etapa 6 se crea el archivo de informaciÃ³n de los archivos (<i>archives.inf</i>).</Text>
+<Text id="217">En la etapa 7 se crea un objeto que sabrÃ¡ dÃ³nde guardar los documentos y obedecerÃ¡ a todas las instrucciones especiales de memorizaciÃ³n (tales comoÂ <i>sortmeta</i>, que clasifica los documentos segÃºn una etiqueta de metadatos especificada).</Text>
+<Text id="218">De hecho, la mayorÃ­a de las tareas del proceso de importaciÃ³n corren a cargo de conectores, que se activan mediante el mÃ³duloÂ <i>plugin</i>. Dicho mÃ³dulo establece una secuencia de los conectores especificados en el archivo de configuraciÃ³n de la colecciÃ³n y maneja asimismo la escritura de los documentos en el Formato de Archivo Greenstone (utilizando un objetoÂ <i>document</i>).</Text>
+</Content>
+</Subsection>
+<Subsection id="the_build_process">
+<Title>
+<Text id="219">El proceso de creaciÃ³n</Text>
+</Title>
+<Content>
+<Text id="220">Durante el proceso de creaciÃ³n de la colecciÃ³n se comprime el texto y se crean los Ã­ndices de texto completo especificados en el archivo de configuraciÃ³n de la colecciÃ³n. AdemÃ¡s, se calculan con antelaciÃ³n y se incorporan a la colecciÃ³n los datos relativos a la apariencia de la colecciÃ³n en Internet, por ejemplo las informaciones sobre los iconos y los tÃ­tulos, asÃ­ como la informaciÃ³n producida por los clasificadores.Â <i>buildcol.pl</i>Â comparte numerosas opciones conÂ <i>import.pl</i>, como se muestra en el Cuadro <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/>. En el Cuadro <CrossRef target="Table" ref="additional_options_for_the_build_process"/> se muestran otras que le son propias.</Text>
+<Table id="additional_options_for_the_build_process">
+<Title>
+<Text id="221">Opciones adicionales del proceso de creaciÃ³n</Text>
+</Title>
+<TableContent>
+<tr>
+<th>Â </th>
+<th>
+<Text id="222"><b>Argumento</b></Text>
+</th>
+<th>
+<Text id="223"><b>FunciÃ³n</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="224"><i>-builddir</i></Text>
+</th>
+<th>
+<Text id="225">Nombre de directorio</Text>
+</th>
+<th>
+<Text id="226">Especifica dÃ³nde se ha de almacenar el resultado de la creaciÃ³n. (El valor por defecto esÂ <i>GSDLHOME/collect/nombre_col/building).</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="227"><i>-index</i></Text>
+</th>
+<th>
+<Text id="228">Nombre del Ã­ndice (por ejemplo,Â <i>section:Title</i>)</Text>
+</th>
+<th>
+<Text id="229">Especifica quÃ© Ã­ndices crear. El valor por defecto es la totalidad de los Ã­ndices indicados en el archivo de configuraciÃ³n de la colecciÃ³n.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="230"><i>-allclassifications</i></Text>
+</th>
+<th>
+<Text id="231">Ninguno</Text>
+</th>
+<th>
+<Text id="232">Evita que el proceso de creaciÃ³n elimine las clasificaciones que no contienen documentos (por ejemplo, la clasificaciÃ³n âXâ en los tÃ­tulos, si no hay documentos cuyo tÃ­tulo empiece por la letra X).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="233"><i>-create_images</i></Text>
+</th>
+<th>
+<Text id="234">Ninguno</Text>
+</th>
+<th>
+<Text id="235">Crea automÃ¡ticamente los iconos de colecciÃ³n (para ello es necesario haber instalado GIMP y el mÃ³dulo Gimp Perl).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="236"><i>-mode</i></Text>
+</th>
+<th>
+<Text id="237">all, compress_text, infodb, o build_index</Text>
+</th>
+<th>
+<Text id="238">Determina lo que debe hacer el proceso de creaciÃ³n. (El valor por defecto esÂ <i>all</i>).Â <i>all</i>Â lleva a cabo una creaciÃ³n completa,Â <i>compress_text</i>Â sÃ³lo comprime el texto del documento,Â <i>infodb</i>Â crea una base de datos de informaciones sobre la colecciÃ³n (nombres, archivos, archivos asociados, informaciÃ³n sobre la clasificaciÃ³n y otros) yÂ <i>build_index</i>Â crea los Ã­ndices especificados en el archivo de configuraciÃ³n de la colecciÃ³n o en la lÃ­nea de comandos.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="239"><i>-no_text</i></Text>
+</th>
+<th>Â </th>
+<th>
+<Text id="240">No almacena texto comprimido. Esta opciÃ³n es Ãºtil para minimizar el tamaÃ±o de los Ã­ndices creados si desea visualizar siempre los documentos originales en el momento de la ejecuciÃ³n.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Figure id="steps_in_the_build_process">
+<Title>
+<Text id="241">Etapas del proceso de creaciÃ³n</Text>
+</Title>
+<File width="605" height="306" url="images/Dev_Fig_6.png"/>
+</Figure>
+<Text id="242">El diagrama de la Figura <CrossRef target="Figure" ref="steps_in_the_build_process"/> representa la ejecuciÃ³n del programaÂ <i>buildcol.pl</i>. Muchas de las etapas son iguales a las del proceso de importaciÃ³n. La primera que no coincide es la etapa 4 (a la izquierda), que sÃ³lo se ejecuta si se ha activado la opciÃ³nÂ <i>create_images</i>. A continuaciÃ³n, las imÃ¡genes se crean y se registran en el archivo de configuraciÃ³n de la colecciÃ³n mediante una funciÃ³n del guiÃ³nÂ <i>buildcol.pl</i>. Para que todo esto funcione adecuadamente, deben haberse instalado y configurado apropiadamente GIMP (Â <i>GNU Image Manipulation Program</i>, o Programa de manipulaciÃ³n de imÃ¡genes de GNU) y el mÃ³dulo Gimp Perl. Debe existir asimismo un permiso de escritura (asÃ­ como de lectura) al archivo de configuraciÃ³n de la colecciÃ³n.</Text>
+<Text id="243">En la etapa 5 se comprueba primero si existe un proceso de creaciÃ³n especÃ­fico de la colecciÃ³n. Algunas colecciones requieren un tratamiento especial durante la creaciÃ³n, en cuyo caso se debe escribir un creador especÃ­fico de la colecciÃ³n y colocarlo en su directorioÂ <i>perllib</i>, que lleva el nombre de la colecciÃ³n seguido de âÂ <i>builder</i>Â â (creador). Los creadores especÃ­ficos de colecciÃ³n provienen deÂ <i>mgbuilder</i>. En la etapa 5, se inicializa el creador (ya sea el instalado por defecto o uno especÃ­fico de la colecciÃ³n) con informaciÃ³n sobre el nÃºmero de documentos que se va a incluir, el mantenimiento o no de la antigua versiÃ³n de la colecciÃ³n y la ubicaciÃ³n de los directoriosÂ <i>building</i>Â yÂ <i>archive</i>.</Text>
+<Text id="244">La etapa 6 es la de la creaciÃ³n. El texto de los documentos se comprime y se indiza, los tÃ­tulos y los iconos se almacenan en una base de datos de informaciones de la colecciÃ³n y se crean las estructuras de datos para apoyar los clasificadores activados por los conectores de la colecciÃ³n. El archivoÂ <i>mgbuilder</i>Â (o el creador especÃ­fico de la colecciÃ³n) maneja todas esas etapas y utiliza el programa MG (âÂ <i>Managing Gigabytes</i>Â â, o gestiÃ³n de gigabytes; vÃ©ase WittenÂ <i>et al.</i>, 1999) para comprimir e indizar.</Text>
+<Text id="245">La opciÃ³nÂ <i>mode</i>Â permite especificar las partes de la colecciÃ³n que se crean, pero por defecto se crea todo: el texto comprimido, los Ã­ndices y las bases de datos de informaciones de colecciÃ³n.</Text>
+<Text id="246">Una vez concluido el proceso de creaciÃ³n, si desea que la colecciÃ³n pueda consultarse en Internet, es preciso trasladarla del directorioÂ <i>building</i>Â de la colecciÃ³n al directorioÂ <i>index</i>. Las colecciones no se crean directamente en el directorioÂ <i>index</i>Â porque la creaciÃ³n de las colecciones voluminosas puede tardar horas o dÃ­as. Es importante que el proceso de creaciÃ³n no afecte una copia existente de la colecciÃ³n hasta que la operaciÃ³n no haya concluido.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="greenstone_archive_documents">
+<Title>
+<Text id="247">Documentos en el Formato de Archivo Greenstone</Text>
+</Title>
+<Content>
+<Text id="248">Todos los documentos de origen se importan al sistema Greenstone despuÃ©s de su conversiÃ³n en el Formato de Archivo Greenstone, que es un estilo XML que divide los documentos en secciones y puede contener metadatos para cada documento o secciÃ³n. No tendrÃ¡ que crear manualmente los archivos en el Format de Archivo Greenstone, ya que los conectores que tratan los documentos cumplen esta funciÃ³n, tal como se explica en el capÃ­tulo siguiente. Sin embargo, puede resultar Ãºtil comprender el formato de los archivos Greenstone, que describimos a continuaciÃ³n.</Text>
+<Text id="249">En XML, las etiquetas van entre corchetes angulares para el marcado. El Formato de Archivo Greenstone codifica los documentos que ya estÃ¡n en HTML, y todos los signos &lt;, &gt; o â incluidos en el texto original se eluden mediante la convenciÃ³n estÃ¡ndar &amp;lt;, &amp;gt; y &amp;quot;.</Text>
+<Figure id="greenstone_archive_format">
+<Title>
+<Text id="250">Formato de Archivo Greenstone:</Text>
+<SubTitle>
+<Text id="251">(a)Â DefiniciÃ³n de tipo de documento (DTD);</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;!DOCTYPE GreenstoneArchive [</CodeLine>
+<CodeLine>Â  &lt;!ELEMENT Section (Description,Content,Section*)&gt;</CodeLine>
+<CodeLine>Â  &lt;!ELEMENT Description (Metadata*)&gt;</CodeLine>
+<CodeLine>Â  &lt;!ELEMENT Content (#PCDATA)&gt;</CodeLine>
+<CodeLine>Â  &lt;!ELEMENT Metadata (#PCDATA)&gt;</CodeLine>
+<CodeLine>Â  &lt;ATTLIST Metadata name CDATA #REQUIRED&gt;</CodeLine>
+<CodeLine>]&gt;</CodeLine>
+</Figure>
+<Figure id="greenstone_archive_format_1">
+<Title>
+<Text id="252"/>
+<SubTitle>
+<Text id="253">(b) Documento de ejemplo.</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;?xml version="1.0" ?&gt;</CodeLine>
+<CodeLine>&lt;!DOCTYPE GreenstoneArchive SYSTEM</CodeLine>
+<CodeLine>"http://greenstone.org/dtd/GreenstoneArchive/1.0/GreenstoneArchive.dtd"&gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>Â  &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Metadata name="gsdlsourcefilename"&gt;ec158e.txt&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Metadata name="Title"&gt;Freshwater Resources in Arid Lands&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Metadata name="Identifier"&gt;HASH0158f56086efffe592636058&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Metadata name="gsdlassocfile"&gt;cover.jpg:image/jpeg:&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Metadata name="gsdlassocfile"&gt;p07a.png:image/png:&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>Â  &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;Metadata name="Title"&gt;PrÃ³logo&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  Eso es el texto del prÃ³logo</CodeLine>
+<CodeLine>Â Â Â  &lt;/Content&gt;</CodeLine>
+<CodeLine>Â  &lt;/Section&gt;</CodeLine>
+<CodeLine>Â  &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;Metadata name="Title"&gt;Primer y Ãºnico capÃ­tulo&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Section&gt; </CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;Description&gt; </CodeLine>
+<CodeLine>Â Â Â Â Â Â Â  &lt;Metadata name="Title"&gt;Parte 1&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â  Eso es la primera parte del primer y Ãºnico capÃ­tulo</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â  Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â  &lt;Metadata name="Title"&gt;Parte 2&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;Content&gt; </CodeLine>
+<CodeLine>Â Â Â Â Â Â Â  Eso es la segunda parte del primer y Ãºnico capÃ­tulo</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;/Section&gt; </CodeLine>
+<CodeLine>Â  &lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+</Figure>
+<Text id="254">En la Figura <CrossRef target="Figure" ref="greenstone_archive_format"/> se muestra la definiciÃ³n de tipo de documento (DTD) XML para el Formato de Archivo Greenstone. BÃ¡sicamente, un documento se divide enÂ <i>Sections</i>Â (Secciones), que pueden a su vez subdividirse. CadaÂ <i>Section</i>Â tiene unaÂ <i>Description</i>Â (descripciÃ³n) que comprende cero o varios elementosÂ <i>Metadata</i>Â (metadatos) y una parteÂ <i>Content</i>Â (contenido) (que puede estar vacÃ­a), donde se guardan los datos propiamente dichos del documento. Cada elementoÂ <i>Metadata</i>Â va asociado con un atributo de nombre (puede ser cualquier nombre) y algunos datos textuales. En XML,Â <i>PCDATA</i>Â corresponde a âÂ <i>parsed character data</i>Â â (datos de caracteres analizados), es decir, bÃ¡sicamente texto.</Text>
+<Text id="255">En la Figura <CrossRef target="Figure" ref="greenstone_archive_format_1"/> se muestra un documento simple escrito en este formato, que es un pequeÃ±o libro con dos imÃ¡genes asociadas. El libro tiene dos secciones denominadasÂ <i>PrÃ³logo</i>Â yÂ <i>Primer y Ãºnico capÃ­tulo</i>,Â <i/>Â respectivamente; la segunda secciÃ³n se divide en dos subsecciones. ObsÃ©rvese que no existe nociÃ³n de âcapÃ­tuloâ como tal: se lo representa simplemente como una secciÃ³n de nivel superior.</Text>
+<Table id="greenstone_archive_format_values">
+<Title>
+<Text id="256">Formato de Archivo Greenstone: Valores del atributoÂ <i>name</i>Â de la etiquetaÂ <i>Metadata</i>.</Text>
+</Title>
+<TableContent>
+<tr>
+<th>
+<Text id="257"><i>gsdlsourcefilename</i></Text>
+</th>
+<th>
+<Text id="258">Archivo original a partir del cual se generÃ³ el archivo de archivo de Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="259"><i>gsdlassocfile</i></Text>
+</th>
+<th>
+<Text id="260">Archivo asociado con el documento (un archivo grÃ¡fico, por ejemplo) </Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="261">La etiqueta &lt;Section&gt; indica el principio de cada secciÃ³n del documento y la correspondiente etiqueta de cierre &lt;/Section&gt; seÃ±ala el final de dicha secciÃ³n. Tras cada etiqueta &lt;Section&gt; hay una secciÃ³n &lt;Description&gt; que incluye una serie cualquiera de elementos &lt;Metadata&gt;. De este modo, se pueden asociar diferentes metadatos con las distintas secciones de un documento. En su mayorÃ­a son tipos particulares de metadatos, como âTitleâ (tÃ­tulo), por ejemplo. Los dos valores del atributoÂ <i>name</i>Â (nombre) que se muestran en el Cuadro <CrossRef target="Table" ref="greenstone_archive_format_values"/> reciben un tratamiento especial por parte de Greenstone; todos los demÃ¡s se consideran metadatos vinculados a esa secciÃ³n.</Text>
+<Text id="262">En algunas colecciones, los documentos estÃ¡n divididos en pÃ¡ginas que se tratan como secciones. Por ejemplo, un libro puede contener secciones de primer nivel que corresponden a los capÃ­tulos, en los que se definen una serie de âseccionesâ que, en realidad, corresponden a las diferentes pÃ¡ginas del capÃ­tulo.</Text>
+<Subsection id="document_metadata">
+<Title>
+<Text id="263">Metadatos del documento</Text>
+</Title>
+<Content>
+<Text id="264">Los metadatos son informaciÃ³n descriptiva asociada a un documento, como por ejemplo, autor, tÃ­tulo, fecha, palabras clave, etc. Ya se ha mencionado que los metadatos se almacenan con los documentos. En la Figura <CrossRef target="Figure" ref="greenstone_archive_format"/> se puede ver que las etiquetas &lt;Metadata&gt; especifican el nombre del tipo de metadatos y les asignan un valor. Un ejemplo es la lÃ­nea &lt;Â <i>Metadata name=âTitleâ</i>Â &gt;Â <i>Primer y Ãºnico capÃ­tulo&lt;/Metadata</i>Â &gt; de la Figura <CrossRef target="Figure" ref="greenstone_archive_format_1"/>: el tÃ­tulo de un documento es un elemento de metadato asociado a Ã©l. Se utiliza la norma de metadatos Dublin Core para definir los tipos de metadatos (Dublin Core, 2001; Weibel, 1999; Thiele, 1997)</Text>
+<Text id="265">En el Cuadro <CrossRef target="Table" ref="dublin_core_metadata_standard"/> se muestran los tipos de metadatos disponibles en la norma; los que van seÃ±alados con un asterisco se utilizan en las colecciones que se pueden consultar actualmente en el sitio Web de la Biblioteca Digital de Nueva Zelandia. Si ninguno de estos tipos corresponde exactamente a una clase determinada de metadatos, se pueden utilizar tambiÃ©n otros tipos de metadatos que no figuran en la norma Dublin Core. Por ejemplo, la colecciÃ³n de demostraciÃ³n contiene los metadatosÂ <i>how to</i>Â (CÃ³mo...) yÂ <i>Magazine</i>Â (Revista).</Text>
+<Table id="dublin_core_metadata_standard">
+<Title>
+<Text id="266">Norma de metadatos Dublin Core</Text>
+</Title>
+<TableContent>
+<tr>
+<th>
+<Text id="267"><b>Nombre</b></Text>
+</th>
+<th>
+<Text id="268"><b>Subetiqueta de metadato</b></Text>
+</th>
+<th>
+<Text id="269"><b>DefiniciÃ³n</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="270">*TÃ­tulo</Text>
+</th>
+<th>
+<Text id="271"><i>Title</i></Text>
+</th>
+<th>
+<Text id="272">Nombre que se da al recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="273">*Creador</Text>
+</th>
+<th>
+<Text id="274"><i>Creator</i></Text>
+</th>
+<th>
+<Text id="275">Entidad encargada principalmente de crear el contenido del recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="276">*Tema y palabras clave</Text>
+</th>
+<th>
+<Text id="277"><i>Subject</i></Text>
+</th>
+<th>
+<Text id="278">Tema del contenido del recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="279">*DescripciÃ³n</Text>
+</th>
+<th>
+<Text id="280"><i>Description</i></Text>
+</th>
+<th>
+<Text id="281">ExplicaciÃ³n del contenido del recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="282">*Editor</Text>
+</th>
+<th>
+<Text id="283"><i>Publisher</i></Text>
+</th>
+<th>
+<Text id="284">Entidad encargada de publicar el recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="285">Contribuidor</Text>
+</th>
+<th>
+<Text id="286"><i>Contributor</i></Text>
+</th>
+<th>
+<Text id="287">Entidad encargada de aportar contribuciones al contenido del recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="288">*Fecha</Text>
+</th>
+<th>
+<Text id="289"><i>Date</i></Text>
+</th>
+<th>
+<Text id="290">Fecha en que se publicÃ³ el recurso o cualquier otra fecha importante asociada con el recurso.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="291">Tipo de recurso</Text>
+</th>
+<th>
+<Text id="292"><i>Type</i></Text>
+</th>
+<th>
+<Text id="293">Ãndole o tipo del contenido del recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="294">Formato</Text>
+</th>
+<th>
+<Text id="295"><i>Format</i></Text>
+</th>
+<th>
+<Text id="296">RepresentaciÃ³n fÃ­sica o digital del recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="297">*Identificador de recurso</Text>
+</th>
+<th>
+<Text id="298"><i>Identifier</i></Text>
+</th>
+<th>
+<Text id="299">Referencia inequÃ­voca al recurso en un contexto determinado: se trata del identificador de objeto u OID</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="300">*Fuente</Text>
+</th>
+<th>
+<Text id="301"><i>Source</i></Text>
+</th>
+<th>
+<Text id="302">Referencia a un recurso del que deriva el presente recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="303">*Lengua</Text>
+</th>
+<th>
+<Text id="304"><i>Language</i></Text>
+</th>
+<th>
+<Text id="305">Lengua del contenido intelectual del recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="306">RelaciÃ³n</Text>
+</th>
+<th>
+<Text id="307"><i>Relation</i></Text>
+</th>
+<th>
+<Text id="308">Referencia a un recurso conexo</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="309">*Cobertura</Text>
+</th>
+<th>
+<Text id="310"><i>Coverage</i></Text>
+</th>
+<th>
+<Text id="311">ExtensiÃ³n o alcance del contenido del recurso</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="312">GestiÃ³n de los derechos</Text>
+</th>
+<th>
+<Text id="313"><i>Rights</i></Text>
+</th>
+<th>
+<Text id="314">InformaciÃ³n sobre los derechos relacionados con el recurso o atinentes a Ã©ste</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="inside_greenstone_archive_documents">
+<Title>
+<Text id="315">Los documentos en el Format de Archivo de Greenstone vistos por dentro</Text>
+</Title>
+<Content>
+<Text id="316">El Formato de Archivo de Greenstone impone poca estructura a los documentos individuales. Los documentos se dividen en pÃ¡rrafos. Pueden subdividirse jerÃ¡rquicamente en secciones y subsecciones que pueden a su vez subdividirse indefinidamente. Cada documento va asociado con un identificador de objeto u OID que tambiÃ©n sirve para identificar las secciones y subsecciones mediante nÃºmeros separados por puntos en los OID de los documentos. Por ejemplo, el OID HASHa7.2.3 se referirÃ¡ a la subsecciÃ³n 3 de la secciÃ³n 2 del documento HASHa7.</Text>
+<Text id="317">Cuando se lee un libro en una colecciÃ³n de Greenstone, la jerarquÃ­a de las secciones figura en el Ã­ndice del libro. Por ejemplo, los libros de la colecciÃ³n de demostraciÃ³n disponen de un Ã­ndice jerÃ¡rquico compuesto de capÃ­tulos, secciones y subsecciones como se muestra en la Figura <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection"/>. Los documentos de la colecciÃ³nÂ <i>Computer Science Technical Reports</i>Â no presentan una estructura jerÃ¡rquica en subsecciones, pero cada documento estÃ¡ dividido en pÃ¡ginas y se puede navegar por las pÃ¡ginas de un documento recuperado. Los capÃ­tulos, las secciones, las subsecciones y las pÃ¡ginas se consideran simplemente âseccionesâ del documento.</Text>
+<Figure id="hierarchical_structure_in_the_demo_collection">
+<Title>
+<SubTitle>
+<Text id="318a">(a)</Text>
+</SubTitle>
+<Text id="318">Estructura jerÃ¡rquica de la colecciÃ³n de demostraciÃ³n</Text>
+</Title>
+<File width="605" height="296" url="images/Dev_Fig_8a.png"/>
+</Figure>
+<Figure id="hierarchical_structure_in_the_demo_collection_1">
+<Title>
+<Text id="318b">Estructura jerÃ¡rquica de la colecciÃ³n de demostraciÃ³n</Text>
+<SubTitle>
+<Text id="318c">(b)</Text>
+</SubTitle>
+</Title>
+<File width="605" height="296" url="images/Dev_Fig_8b.png"/>
+</Figure>
+<Text id="319">La estructura del documento sirve tambiÃ©n para los Ã­ndices de bÃºsqueda. Existen tres niveles posibles de Ã­ndices:Â <i>documento</i>,Â <i>secciÃ³n</i>Â yÂ <i>pÃ¡rrafo</i>, aunque la mayorÃ­a de las colecciones no utilizan los tres niveles. Un Ã­ndice deÂ <i>documento</i>Â contiene el documento completo; se lo utiliza para encontrar todos los documentos en los que figura un conjunto determinado de palabras (los tÃ©rminos pueden estar repartidos por todo el documento, lejos unos de otros). Cuando se crea un Ã­ndice deÂ <i>secciÃ³n</i>, cada porciÃ³n de texto que se indiza se extiende desde una etiqueta &lt;Section&gt; hasta la siguiente etiqueta &lt;Section&gt;; por consiguiente, un capÃ­tulo que empieza directamente con una nueva secciÃ³n producirÃ¡ un documento vacÃ­o en el Ã­ndice. Las secciones y subsecciones se tratan de la misma manera: la estructura jerÃ¡rquica del documento se allana con objeto de crear Ã­ndices de bÃºsqueda. Para los Ã­ndices de pÃ¡rrafos, Ãºtiles para bÃºsquedas mÃ¡s especÃ­ficas, cada pÃ¡rrafo se considera un documento aparte.</Text>
+<Text id="320">En el menÃº desplegable de la Figura <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection_1"/> se muestran los Ã­ndices de bÃºsqueda de la colecciÃ³n de demostraciÃ³n. Los âcapÃ­tulosâ y los âtÃ­tulos de las seccionesâ son Ã­ndices de nivel de la secciÃ³n, mientras que los âlibros enterosâ son Ã­ndices de nivel del documento. Al igual que los Ã­ndices de texto, se pueden crear Ã­ndices de cualquier tipo de metadatos. Por ejemplo, algunas colecciones proponen Ã­ndices de bÃºsqueda de tÃ­tulos de secciÃ³n, como se muestra en la Figura <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection_1"/>.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="configuration_file">
+<Title>
+<Text id="321">Archivo de configuraciÃ³n de la colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="322">El archivo de configuraciÃ³n de la colecciÃ³n rige la estructura de una colecciÃ³n tal como la ve el usuario, lo que permite personalizar su aspecto y estilo, asÃ­ como el modo en que se tratan y presentan los documentos. Cuando usted ejecutaÂ <i>mkcol.pl</i>, se crea un simple archivo de configuraciÃ³n de colecciÃ³n en el que queda registrada su direcciÃ³n electrÃ³nica como creador y responsable de la actualizaciÃ³n. RecuÃ©rdese que el argumentoÂ <i>creator</i>Â es obligatorio, y a menos que se especifique por separado, se registra la misma informaciÃ³n para el elementoÂ <i>maintainer</i>Â (actualizador).</Text>
+<Table id="items_in_the_collection_configuration_file">
+<Title>
+<Text id="323">Elementos del archivo de configuraciÃ³n de la colecciÃ³n</Text>
+</Title>
+<TableContent>
+<tr>
+<th>
+<CodeLine>creator</CodeLine>
+</th>
+<th>
+<Text id="324">DirecciÃ³n electrÃ³nica del creador de la colecciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>maintainer</i></CodeLine>
+</th>
+<th>
+<Text id="325">DirecciÃ³n electrÃ³nica del actualizador de la colecciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>public</i></CodeLine>
+</th>
+<th>
+<Text id="326">Determina si la colecciÃ³n va a ponerse a disposiciÃ³n del pÃºblico o no</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>beta</i></CodeLine>
+</th>
+<th>
+<Text id="327">Determina si la colecciÃ³n es una versiÃ³n beta o no</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>indexes</i></CodeLine>
+</th>
+<th>
+<Text id="328">Lista de Ã­ndices por crear</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>defaultindex</i></CodeLine>
+</th>
+<th>
+<Text id="329">Ãndice por defecto</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>subcollection</i></CodeLine>
+</th>
+<th>
+<Text id="330">Define una subcolecciÃ³n basada en metadatos</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>indexsubcollections</i></CodeLine>
+</th>
+<th>
+<Text id="331">Especifica quÃ© subcolecciones indizar</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>defaultsubcollection</i></CodeLine>
+</th>
+<th>
+<Text id="332">Ãndice de subcolecciÃ³n por defecto</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>languages</i></CodeLine>
+</th>
+<th>
+<Text id="333">Lista de lenguas en las que hay que crear los Ã­ndices</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>defaultlanguage</i></CodeLine>
+</th>
+<th>
+<Text id="334">Ãndice de lengua por defecto</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>collectionmeta</i></CodeLine>
+</th>
+<th>
+<Text id="335">Define los metadatos al nivel de la colecciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>plugin</i></CodeLine>
+</th>
+<th>
+<Text id="336">Especifica un conector que habrÃ¡ de utilizarse durante la creaciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>format</i></CodeLine>
+</th>
+<th>
+<Text id="337">Cadena de formato (se explica mÃ¡s adelante)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>classify</i></CodeLine>
+</th>
+<th>
+<Text id="338">Especifica un clasificador que habrÃ¡ de utilizarse durante la creaciÃ³n</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="339">Cada lÃ­nea del archivo de configuraciÃ³n de colecciÃ³n es bÃ¡sicamente un par âatributo, valorâ. Cada atributo aporta una parte de informaciÃ³n sobre la colecciÃ³n que determina su apariencia y el modo en que se van a tratar los documentos. En el Cuadro <CrossRef target="Table" ref="items_in_the_collection_configuration_file"/> se muestran los elementos que se pueden incluir en un archivo de configuraciÃ³n de colecciÃ³n y su utilizaciÃ³n. AdemÃ¡s, se pueden especificar todas las opciones de lÃ­nea de comandos de los programasÂ <i>import.pl</i>Â yÂ <i>buildcol.pl</i>Â en un archivo de configuraciÃ³n de colecciÃ³n; por ejemplo, una lÃ­nea que digaÂ <i>no_text true</i>Â propondrÃ¡ la opciÃ³nÂ <i>no_text</i>Â deÂ <i>buildcol.pl</i>.</Text>
+<Text id="340">El archivo de configuraciÃ³n de la colecciÃ³n creado por la secuencia de comandosÂ <i>mkcol.pl</i>, que se muestra en el Cuadro <CrossRef target="Table" ref="collection_configuration_file_created_by_mkcd"/>, es muy simple y no contiene sino la informaciÃ³n estrictamente necesaria. Las lÃ­neas 1 y 2, que proceden del valorÂ <i>creator</i>Â suministrado al programaÂ <i>mkcol.pl</i>, contienen las direcciones electrÃ³nicas de la persona encargada de la creaciÃ³n de la colecciÃ³n y de la persona encargada de actualizarla (no es necesariamente la misma).</Text>
+<Table id="collection_configuration_file_created_by_mkcd">
+<Title>
+<Text id="341">Archivo de configuraciÃ³n de colecciÃ³n creado medianteÂ <i>mkcol.pl</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="342"><b>Atributo</b></Text>
+</th>
+<th width="265">
+<Text id="343"><b>Valor</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>1</CodeLine>
+</th>
+<th width="132">
+<CodeLine>creator</CodeLine>
+</th>
+<th width="265">
+<Text id="344">nombre_del_usuario@email.com</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>2</CodeLine>
+</th>
+<th width="132">
+<CodeLine>maintainer</CodeLine>
+</th>
+<th width="265">
+<Text id="345">nombre_del_usuario@email.com</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>3</CodeLine>
+</th>
+<th width="132">
+<CodeLine>public</CodeLine>
+</th>
+<th width="265">
+<Text id="346">True</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>4</CodeLine>
+</th>
+<th width="132">
+<CodeLine>beta</CodeLine>
+</th>
+<th width="265">
+<Text id="347">True</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>5</CodeLine>
+</th>
+<th width="132">
+<CodeLine>indexes</CodeLine>
+</th>
+<th width="265">
+<Text id="348">document:text</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>6</CodeLine>
+</th>
+<th width="132">
+<CodeLine>defaultindex</CodeLine>
+</th>
+<th width="265">
+<Text id="349">document:text</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>7</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="350">ZIPPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>8</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="351">GAPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>9</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="352">TextPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>10</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="353">HTMLPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>11</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="354">EMAILPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>12</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="355">ArcPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>13</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="356">RecPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>14</CodeLine>
+</th>
+<th width="132">
+<CodeLine>classify</CodeLine>
+</th>
+<th width="265">
+<Text id="357">AZList metadata Title</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>15</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="358">collectioname âcolecciÃ³n de muestrasâ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>16</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="359">iconcollection       ""</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>17</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="360">collectionextra     ""</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>18</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="361">.document:text     "documents"</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="362">La lÃ­nea 3 indica si la colecciÃ³n se pondrÃ¡ a disposiciÃ³n del pÃºblico una vez creada, mediante los valoresÂ <i>true</i>Â (el parÃ¡metro por defecto, que significa que la colecciÃ³n se podrÃ¡ consultar pÃºblicamente) oÂ <i>false</i>Â (que significa lo contrario). Esta Ãºltima opciÃ³n es Ãºtil cuando se crean colecciones para probar programas o para uso personal. La lÃ­nea 4 indica si la colecciÃ³n es beta o no (el valor por defecto tambiÃ©n esÂ <i>true</i>Â (verdadero), lo que significa que la colecciÃ³n es una versiÃ³n beta).</Text>
+<Text id="363">La lÃ­nea 5 determina los Ã­ndices de colecciÃ³n que han de constituirse en el momento de la creaciÃ³n: en este ejemplo sÃ³lo se indizarÃ¡ el texto del documento. Existen tres niveles posibles de Ã­ndices:Â <i>document (</i>Â documentoÂ <i>)</i>,Â <i>section (</i>Â secciÃ³nÂ <i>)</i>Â yÂ <i>paragraph (</i>Â pÃ¡rrafoÂ <i>)</i>. Pueden contener datos en formatoÂ <i>text</i>Â (texto) o en cualquier tipo de metadatos, por lo generalÂ <i>Title</i>Â (tÃ­tulo). La forma que se utiliza para especificar el tipo de Ã­ndice esÂ <i>nivel:datos</i>. Por ejemplo, para incluir tambiÃ©n un Ã­ndice de tÃ­tulos de secciÃ³n, habrÃ­a que sustituir la lÃ­nea 5 porÂ <i>indexes document:text section:Title</i>. Se puede incluir mÃ¡s de un tipo de datos en el mismo Ã­ndice separando los tipos de datos por comas. Por ejemplo, para crear un Ã­ndice en el nivel de secciÃ³n que incluya tÃ­tulos, texto y datos, la lÃ­nea deberÃ­a rezarÂ <i>indexes section:text,Title,Date</i>. El Ã­ndice por defecto que se define en la lÃ­nea 6 es el valor por defecto que se utiliza en la pÃ¡gina de bÃºsqueda de la colecciÃ³n.</Text>
+<Text id="364">Las lÃ­neas 7-13 especifican los conectores que se han de utilizar para convertir los documentos en el Formato de Archivo Greenstone y para crear colecciones a partir de archivos en el Formato de Archivo Greenstone. En la SecciÃ³n <CrossRef target="Section" ref="plugins"/> se proporciona informaciÃ³n sobre los conectores disponibles. Los conectores se prueban en cada documento siguiendo el orden de su enumeraciÃ³n y cuando se encuentra un conector capaz de tratar un documento, no se prueba ninguno mÃ¡s.</Text>
+<Text id="365">La lÃ­nea 14 especifica que se va a crear una lista alfabÃ©tica de tÃ­tulos para facilitar la consulta. Las estructuras de consulta estÃ¡n compuestas por âclasificadoresâ. En la SecciÃ³n <CrossRef target="Section" ref="classifiers"/> se proporciona informaciÃ³n sobre los clasificadores y sus funciones.</Text>
+<Text id="366">Las lÃ­neas 15-18 sirven para especificar los metadatos de nivel de colecciÃ³n. Se utiliza la forma larga delÂ <i>collectionname</i>Â como âtÃ­tuloâ de la colecciÃ³n para el navegador de Internet. El atributoÂ <i>collectionicon</i>Â proporciona la URL del icono de la colecciÃ³n. Si se especifica un Ã­ndice (como en la lÃ­nea 18), la cadena siguiente aparece en la pÃ¡gina de bÃºsqueda de la colecciÃ³n como el nombre de ese Ã­ndice. Un metadato de nivel de colecciÃ³n particularmente importante esÂ <i>collectionextra</i>, que suministra un texto entrecomillado en que se describe la colecciÃ³n. Este atributo aparecerÃ¡ como texto en âAcerca de esta colecciÃ³nâ. Se pueden introducir distintas versiones deÂ <i>collectionextra</i>Â para las diferentes interfaces lingÃŒÃ­sticas aÃ±adiendo la especificaciÃ³n de la lengua entre corchetes. Por ejemplo:</Text>
+<Indented>
+<Text id="367">collectionmeta collectionextra âdescripciÃ³n de la coleciÃ³nâ</Text>
+</Indented>
+<Indented>
+<Text id="368">collectionmeta collectionextra [l=fr] âdescripciÃ³n en francÃ©sâ</Text>
+</Indented>
+<Indented>
+<Text id="369">collectionmeta collectionextra [l=mi] âdescripciÃ³n en maorÃ­â</Text>
+</Indented>
+<Text id="370">Si se introduce âfrâ o âmiâ como idioma de la interfaz, aparecerÃ¡ en pantalla la correspondiente versiÃ³n lingÃŒÃ­stica de la descripciÃ³n. Para otras lenguas aparecerÃ¡ la versiÃ³n por defecto.</Text>
+<Text id="371">Este archivo simple de configuraciÃ³n de colecciÃ³n no incluye ningÃºn ejemplo de cadenas de formato, ni de las posibilidades de subcolecciÃ³n o de idiomas que ofrece el archivo de configuraciÃ³n. Las cadenas de formato se examinan mÃ¡s en detalle en la SecciÃ³n <CrossRef target="Section" ref="formatting_greenstone_output"/>, pero las subcolecciones y las posibilidades lingÃŒÃ­sticas se abordarÃ¡n en este capÃ­tulo.</Text>
+<Subsection id="subcollections">
+<Title>
+<Text id="372">Las subcolecciones</Text>
+</Title>
+<Content>
+<Text id="373">Greenstone le permite definir subcolecciones y crear Ã­ndices separados para cada una. Por ejemplo, en una colecciÃ³n hay un amplio subconjunto de documentos denominadoÂ <i>Food and Nutrition Bulletin</i>Â (boletÃ­n de los alimentos y la nutriciÃ³n). Utilizaremos esta colecciÃ³n como ejemplo.</Text>
+<Text id="374">Esta colecciÃ³n posee tres Ã­ndices, todos de nivel de secciÃ³n: el primero para toda la colecciÃ³n, el segundo para elÂ <i>Food and Nutrition Bulletin</i>Â y el tercero para el resto de los documentos. A continuaciÃ³n se presentan las correspondientes lÃ­neas del archivo de configuraciÃ³n de la colecciÃ³n:</Text>
+<CodeLine>indexesÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  section:text</CodeLine>
+<CodeLine>subcollectionÂ Â Â Â Â Â  fn âTitle/^Food and Nutrition Bulletin/iâ</CodeLine>
+<CodeLine>subcollectionÂ Â Â Â Â Â  other â!Title/^Food and Nutrition Bulletin/iâ</CodeLine>
+<CodeLine>indexsubcollections Â Â Â Â Â Â  fn Â Â Â  otherÂ  fn,other</CodeLine>
+<Text id="375">La segunda y la tercera lÃ­neas definen las subcolecciones denominadasÂ <i>fn</i>, que contendrÃ¡ los documentos deÂ <i>Food and Nutrition Bulletin</i>, yÂ <i>other</i>, que contendrÃ¡ el resto de los documentos. El tercer campo de estas definiciones es una expresiÃ³n regular en Perl que identifica estos subconjuntos mediante el metadatoÂ <i>Title</i>Â : en el primer caso, buscamos tÃ­tulos que empiecen porÂ <i>Food and Nutrition Bulletin</i>Â y, en el segundo, otros tÃ­tulos que no empiezan asÃ­ (obsÃ©rvese el â!â). LaÂ <i>i</i>Â final permite que la bÃºsqueda se haga sin distinciÃ³n entre mayÃºsculas y minÃºsculas. El campo de metadatos, en este casoÂ <i>Title</i>, puede ser cualquier campo vÃ¡lido, oÂ <i>Filename</i>Â (nombre de archivo) que coincida con el nombre de archivo original del documento. La cuarta lÃ­nea,Â <i>indexsubcollections</i>, especifica tres Ã­ndices: uno para la subcolecciÃ³nÂ <i>fn</i>, otro para la subcolecciÃ³nÂ <i>other</i>, y el tercero para ambas subcolecciones (esto es, para todos los documentos). ObsÃ©rvese que si se hubiesen especificado dos entradas en la lÃ­neaÂ <i>indexes</i>, el nÃºmero total de Ã­ndices generado hubiese sido seis en lugar de tres.</Text>
+<Text id="376">Si una colecciÃ³n contiene documentos en distintas lenguas, se pueden crear Ã­ndices separados para cada lengua. La lengua es una instrucciÃ³n de metadato; los valores se especifican a travÃ©s de la norma ISO 639 que consta de un cÃ³digo de dos letras para representar los idiomas, por ejemplo,Â <i>en</i>Â para inglÃ©s,Â <i>zh</i>Â para chino yÂ <i>mi</i>Â para maorÃ­. Puesto que los valores de los metadatos pueden especificarse en el nivel de la secciÃ³n, las diferentes partes de un documento pueden estar en distintos idiomas.</Text>
+<Text id="377">Por ejemplo, si el archivo de configuraciÃ³n incluyese:</Text>
+<CodeLine>indexes section:text section:Title document:text paragraph:text</CodeLine>
+<CodeLine>languages en zh mi</CodeLine>
+<Text id="378">los Ã­ndices correspondientes al texto de la secciÃ³n, al tÃ­tulo de la secciÃ³n, al texto del documento y al texto de los pÃ¡rrafos se crearÃ­an en inglÃ©s, chino y maorÃ­: doce Ã­ndices en total. Si se aÃ±aden un par de subcolecciones se multiplica de nuevo el nÃºmero de Ã­ndices. Es preciso tener cuidado a fin de evitar recargar el Ã­ndice.</Text>
+<Text id="379">(Esta especificaciÃ³n del Ã­ndice podrÃ­a definirse mediante la funciÃ³nÂ <i>subcollection</i>Â en vez de la funciÃ³nÂ <i>languages</i>. Sin embargo, como la sintaxis impide crear subcolecciones de subcolecciones, serÃ­a imposible indizar cada lengua por separado en las subcolecciones.)</Text>
+</Content>
+</Subsection>
+<Subsection id="cross-collection_searching">
+<Title>
+<Text id="380">BÃºsqueda transversal en las colecciones</Text>
+</Title>
+<Content>
+<Text id="381">Greenstone tiene una funciÃ³n de âbÃºsqueda transversal en las coleccionesâ que permite buscar en varias colecciones a la vez y combinar los resultados âentre bastidoresâ como si se estuviera buscando en una sola colecciÃ³n unificada. Se puede buscar en cualquier subconjunto de colecciones: la pÃ¡gina deÂ <i>Preferencias</i>Â le permite elegir las colecciones que se han de incluir en las bÃºsquedas.</Text>
+<Text id="382">La bÃºsqueda transversal en las colecciones se activa mediante la lÃ­nea siguiente:</Text>
+<CodeLine>supercollection col_1 col_2 ...</CodeLine>
+<Text id="383">en que las colecciones en cuestiÃ³n se denominanÂ <i>col_1</i>,Â <i>col_2</i>, ... La misma lÃ­nea debe figurar en el archivo de configuraciÃ³n de cada una de las colecciones en cuestiÃ³n.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="getting_the_most_out_of_your_documents">
+<Title>
+<Text id="384">EXPLOTACIÃN ÃPTIMA DE SUS DOCUMENTOS</Text>
+</Title>
+<Content>
+<Text id="385">Las colecciones pueden personalizarse para que la informaciÃ³n que contienen sea accesible de distintas maneras. En este capÃ­tulo se explica la manera en que Greenstone extrae la informaciÃ³n de los documentos y la presenta al usuario: el tratamiento de los documentos (SecciÃ³n <CrossRef target="Section" ref="plugins"/>), las estructuras de clasificaciÃ³n (SecciÃ³n <CrossRef target="Section" ref="classifiers"/>) y las herramientas de la interfaz de usuario (Secciones <CrossRef target="Section" ref="formatting_greenstone_output"/> y <CrossRef target="Section" ref="controlling_the_greenstone_user_interface"/>).</Text>
+<Section id="plugins">
+<Title>
+<Text id="386">Conectores (<i>plugins</i>)</Text>
+</Title>
+<Content>
+<Text id="387">Los conectores analizan los documentos importados y extraen los metadatos. El conector HTML, por ejemplo, convierte las pÃ¡ginas HTML en el Formato de Archivo Greenstone y extrae los metadatos que estÃ¡n explÃ­citos en el formato del documento, como los tÃ­tulos entre etiquetas &lt;title&gt; &lt;/title&gt;.</Text>
+<Text id="388">Los conectores se escriben en lenguaje Perl. Todos proceden de un conector bÃ¡sico denominadoÂ <i>BasPlug</i>, que realiza todas las operaciones necesarias como crear un nuevo documento en el Formato de Archivo Greenstone con que trabajar, asignar un identificador de objeto (OID) y manejar las secciones de un documento. Los conectores se guardan en el directorioÂ <i>perllib/plugins</i>.</Text>
+<Text id="389">Para saber mÃ¡s sobre un conector cualquiera, escribaÂ <i>pluginfo.pl nombre-de-conector</i>Â en la lÃ­nea de comandos. (Es preciso que active primero el guiÃ³n de configuraciÃ³n âÂ <i>setup</i>Â --adecuado, si aÃºn no lo ha hecho, y en Windows ha de teclearÂ <i>perlÂ  âS pluginfo.pl nombre de conector</i>Â si su sistema no estÃ¡ configurado para reconocer los archivos que terminan enÂ <i>.pl</i>Â como ejecutables de Perl). Aparece entonces en la pantalla la informaciÃ³n sobre el conector: quÃ© opciones especÃ­ficas admite y quÃ© opciones generales se autorizan.</Text>
+<Text id="390">Puede usted escribir fÃ¡cilmente nuevos conectores para tratar formatos de documentos que los conectores existentes no manejan, formatear documentos de determinada manera o extraer un nuevo tipo de metadatos.</Text>
+<Subsection id="general_options">
+<Title>
+<Text id="391">Opciones generales</Text>
+</Title>
+<Content>
+<Text id="392">En el Cuadro <CrossRef target="Table" ref="options_applicable_to_all_plugins"/> se muestran las opciones que admite cualquier conector derivado de BasPlug.</Text>
+<Table id="options_applicable_to_all_plugins">
+<Title>
+<Text id="393">Opciones vÃ¡lidas para todos los conectores</Text>
+</Title>
+<TableContent>
+<tr>
+<th>
+<CodeLine><i>input_encoding</i></CodeLine>
+</th>
+<th>
+<Text id="394">CodificaciÃ³n de los caracteres utilizados en los documentos de origen. Por defecto Greenstone averigua automÃ¡ticamente la codificaciÃ³n de cada documento. Sin embargo, algunas veces conviene definir este valor. Por ejemplo, si se sabe con certeza que todos los documentos estÃ¡n en ASCII, el hecho de establecer la codificaciÃ³n de los datos de entrada enÂ <i>ascii</i>Â incrementa considerablemente la velocidad de importaciÃ³n y creaciÃ³n de la colecciÃ³n. Hay muchos valores posibles: tecleeÂ <i>pluginfo.pl BasPlug</i>Â para obtener una lista completa.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>default_encoding</i></CodeLine>
+</th>
+<th>
+<Text id="395">CodificaciÃ³n utilizada siÂ <i>input_encoding</i>Â estÃ¡ enÂ <i>auto</i>Â y falla la detecciÃ³n automÃ¡tica de la codificaciÃ³n.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>process_exp</i></CodeLine>
+</th>
+<th>
+<Text id="396">ExpresiÃ³n regular en Perl para detectar los nombres de archivo (por ejemplo, para localizar un tipo determinado de extensiÃ³n de archivo). Esto determina quÃ© archivos debe tratar un conector. Todo conector tiene una extensiÃ³n por defecto (el valor por defecto deÂ <i>HTMLPlug</i>Â esÂ <i>(?i).html?</i>, o sea, cualquier archivo con la extensiÃ³nÂ <i>.htm</i>Â oÂ <i>.html</i>).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>block_exp</i></CodeLine>
+</th>
+<th>
+<Text id="397">Una expresiÃ³n regular para detectar los nombres de archivo que no van a pasarse a otros conectores. Esta operaciÃ³n puede evitar la apariciÃ³n de mensajes de error molestos sobre archivos que no interesan. Algunos conectores tienen expresiones de bloqueo por defecto, por ejemplo,Â <i>HTMLPlug</i>Â bloquea los archivos con extensionesÂ <i>.gif</i>,Â <i>.jpg</i>,Â <i>.jpeg</i>,Â <i>.png</i>,Â <i>.rtf</i>Â yÂ <i>.css</i>.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>cover_image</i></CodeLine>
+</th>
+<th>
+<Text id="398">Busca un archivoÂ <i>.jpg</i>Â (con el mismo nombre que el archivo en curso de tratamiento) y lo asocia con el documento como imagen de portada.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>extract_acronyms</i></CodeLine>
+</th>
+<th>
+<Text id="399">Extrae siglas de los documentos y las aÃ±ade como metadatos a los correspondientes documentos en el Formato de Archivo Greenstone.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>markup_acronyms</i></CodeLine>
+</th>
+<th>
+<Text id="400">AÃ±ade informaciÃ³n sobre las siglas al texto del documento.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>extract_language</i></CodeLine>
+</th>
+<th>
+<Text id="401">Identifica la lengua de cada documento y la asocia como metadato. ObsÃ©rvese que esto se hace de forma automÃ¡tica si la opciÃ³nÂ <i>input_encoding</i>Â estÃ¡ en posiciÃ³nÂ <i>auto</i>.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>default_language</i></CodeLine>
+</th>
+<th>
+<Text id="402">Si falla la extracciÃ³n automÃ¡tica de la lengua, el metadato de lengua adopta este valor.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>first</i></CodeLine>
+</th>
+<th>
+<Text id="403">Extrae una lista separada por comas de la primera porciÃ³n de texto y la incorpora como metadatoÂ <i>FirstNNN</i>Â (se utiliza a menudo como sustituto delÂ <i>Title</i>).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>extract_email</i></CodeLine>
+</th>
+<th>
+<Text id="404">Extrae las direcciones electrÃ³nicas y las aÃ±ade como metadatos del documento.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<CodeLine><i>extract_date</i></CodeLine>
+</th>
+<th>
+<Text id="405">Extrae las fechas relacionadas con el contenido de documentos histÃ³ricos y los incluye como metadatos de tipoÂ <i>Coverage</i>.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="subsection_conectores_de_tratamiento_de_documentos">
+<Title>
+<Text id="406">Conectores de tratamiento de documentos</Text>
+</Title>
+<Content>
+<Table id="table_conectores_de_greenstone">
+<Title>
+<Text id="407">Conectores de Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="@width"/>
+<th width="@width"/>
+<th>
+<Text id="408"><b>Objetivo</b></Text>
+</th>
+<th>
+<Text id="409"><b>Tipos de archivo</b></Text>
+</th>
+<th>
+<Text id="410"><b>Ignora archivos</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="411"><b>Generales</b></Text>
+</th>
+<th>
+<Text id="412">ArcPlug</Text>
+</th>
+<th>
+<Text id="413">Trata los archivos mencionados en el archivoÂ <i>archives.inf</i>, que se utiliza como vector de comunicaciÃ³n entre los procesos de importaciÃ³n y de creaciÃ³n. Debe incluirse (a menos que no se vaya a utilizarÂ <i>import.pl</i>)</Text>
+</th>
+<th>
+<Text id="414"><i>-</i></Text>
+</th>
+<th>
+<Text id="415"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="416"><i>RecPlug</i></Text>
+</th>
+<th>
+<Text id="417">Explora recursivamente una estructura de directorios para comprobar si un nombre de archivo corresponde a un directorio y, de ser asÃ­, insertar todos los archivos del directorio en la secuencia de los conectores. Asigna metadatos si la opciÃ³nÂ <i>âuse_metadata_files</i>Â estÃ¡ activada y los archivosÂ <i>metadata.xml</i>Â estÃ¡n presentes.</Text>
+</th>
+<th>
+<Text id="418"><i>-</i></Text>
+</th>
+<th>
+<Text id="419"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="420"><i>GAPlug</i></Text>
+</th>
+<th>
+<Text id="421">Trata los archivos en el Formato de Archivo Greenstone generados porÂ <i>import.pl</i>. Debe incluirse (a menos que no se vaya a utilizarÂ <i>import.pl</i>).</Text>
+</th>
+<th>
+<Text id="422"><i>.xml</i></Text>
+</th>
+<th>
+<Text id="423"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="424"><i>TEXTPlug</i></Text>
+</th>
+<th>
+<Text id="425">Trata texto sin formato colocÃ¡ndolo entre etiquetas &lt;pre&gt; &lt;/pre&gt; (tratÃ¡ndolo como si estuviera previamente formateado).</Text>
+</th>
+<th>
+<Text id="426"><i>.txt, .text</i></Text>
+</th>
+<th>
+<Text id="427"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="428"><i>HTMLPlug</i></Text>
+</th>
+<th>
+<Text id="429">Trata el HTML, sustituyendo adecuadamente los hipervÃ­nculos. Si el documento al que apunta el hipervÃ­nculo no se encuentra en la colecciÃ³n, se inserta una pÃ¡gina intermedia que avisa al usuario de que estÃ¡ saliendo de la colecciÃ³n. Extrae los metadatos ya disponibles, comoÂ <i>Title</i>.</Text>
+</th>
+<th>
+<Text id="430"><i>.htm, .html, .cgi, .php, .asp, .shm, .shtml</i></Text>
+</th>
+<th>
+<Text id="431"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="432"><i>WordPlug</i></Text>
+</th>
+<th>
+<Text id="433">Trata los documentos en formato Word de Microsoft, extrae el autor y el tÃ­tulo cuando estÃ¡n disponibles y mantiene los diagramas e imÃ¡genes en sus lugares adecuados. Las aplicaciones de conversiÃ³n utilizadas por este conector generan algunas veces HTML mal formateados y, por consiguiente, le recomendamos que proporcione los documentos originales para su visualizaciÃ³n cuando cree colecciones de archivos WORD. Sin embargo, el texto que se extrae de los documentos es apropiado a efectos de bÃºsqueda e indizaciÃ³n.</Text>
+</th>
+<th>
+<Text id="434"><i>.doc</i></Text>
+</th>
+<th>
+<Text id="435"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="436"><i>PDFPlug</i></Text>
+</th>
+<th>
+<Text id="437">Trata documentos PDF y extrae la primera lÃ­nea del texto como tÃ­tulo. El programaÂ <i>pdftohtml</i>Â no logra tratar algunos archivos PDF. Lo que ocurre es que el proceso de conversiÃ³n lleva un tiempo excesivo y a menudo aparece en pantalla un mensaje de error al respecto. Si esto ocurre, la Ãºnica soluciÃ³n que podemos proponerle es suprimir de la colecciÃ³n el documento problemÃ¡tico y volverla a importar.</Text>
+</th>
+<th>
+<Text id="438"><i>.pdf</i></Text>
+</th>
+<th>
+<Text id="439"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="440"><i>PSPlug</i></Text>
+</th>
+<th>
+<Text id="441">Trata documentos PostScript y opcionalmente extrae los metadatos de fecha, tÃ­tulo y nÃºmero de pÃ¡gina.</Text>
+</th>
+<th>
+<Text id="442"><i>.ps</i></Text>
+</th>
+<th>
+<Text id="443"><i>.eps</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="444"><i>EMAILPlug</i></Text>
+</th>
+<th>
+<Text id="445">Trata los mensajes de correo electrÃ³nico y reconoce el autor, el asunto, la fecha, etc. Este conector aÃºn no maneja adecuadamente los correos electrÃ³nicos codificados con MIME; aunque son legibles, suelen tener un aspecto bastante extraÃ±o.</Text>
+</th>
+<th>
+<Text id="446">Debe terminar por dÃ­gitos o por dÃ­gitos seguidos de .Email</Text>
+</th>
+<th>
+<Text id="447"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="448"><i>BibTexPlug</i></Text>
+</th>
+<th>
+<Text id="449">Trata los archivos bibliogrÃ¡ficos en formatoÂ <i>BibTeX</i></Text>
+</th>
+<th>
+<Text id="450"><i>.bib</i></Text>
+</th>
+<th>
+<Text id="451"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="452"><i>ReferPlug</i></Text>
+</th>
+<th>
+<Text id="453">Trata los archivos bibliogrÃ¡ficos en formatoÂ <i>refer</i></Text>
+</th>
+<th>
+<Text id="454"><i>.bib</i></Text>
+</th>
+<th>
+<Text id="455"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="456"><i>SRCPlug</i></Text>
+</th>
+<th>
+<Text id="457">Trata los archivos de cÃ³digo fuente</Text>
+</th>
+<th>
+<Text id="458"><i>Makefile, Readme, .c, .cc, .cpp, .h, .hpp, .pl, .pm, .sh</i></Text>
+</th>
+<th>
+<Text id="459"><i>.o, .obj, .a, .so, .dll</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="460"><i>ImagePlug</i></Text>
+</th>
+<th>
+<Text id="461">Trata los archivos de imÃ¡genes para crear una biblioteca de imÃ¡genes. SÃ³lo funciona con UNIX.</Text>
+</th>
+<th>
+<Text id="462"><i>.jpeg, .jpg, .gif, .png, .bmp, .xbm, .tif, .tiff</i></Text>
+</th>
+<th>
+<Text id="463"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="464"><i>SplitPlug</i></Text>
+</th>
+<th>
+<Text id="465">Como BasPlug y ConvertToPlug, este conector no debe activarse directamente; en cambio, puede ser heredado por conectores que necesiten tratar archivos que contengan varios documentos</Text>
+</th>
+<th>
+<Text id="466"><i>-</i></Text>
+</th>
+<th>
+<Text id="467"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="468"><i>FOXPlug</i></Text>
+</th>
+<th>
+<Text id="469">Trata los archivos dbt de FoxBASE</Text>
+</th>
+<th>
+<Text id="470"><i>.dbt, .dbf,</i></Text>
+</th>
+<th>
+<Text id="471"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="472"><i>ZIPPlug</i></Text>
+</th>
+<th>
+<Text id="473">Descomprime archivosÂ <i>gzip</i>,Â <i>bzip</i>,Â <i>zip</i>Â yÂ <i>tar</i>Â siempre que se disponga de las herramientas GNU adecuadas</Text>
+</th>
+<th>
+<Text id="474"><i>.gzip, .bzip, .zip, .tar, .gz, .bz, .tgz, .taz</i></Text>
+</th>
+<th>
+<Text id="475"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="476"><b>EspecÃ­ficos de una colecciÃ³n</b></Text>
+</th>
+<th>
+<Text id="477"><i>PrePlug</i></Text>
+</th>
+<th>
+<Text id="478">Trata la salida HTML utilizando PRESCRIPT y divide los documentos en pÃ¡ginas para la colecciÃ³nÂ <i>Computer Science Tecnical Reports</i></Text>
+</th>
+<th>
+<Text id="479"><i>.html, .html.gz</i></Text>
+</th>
+<th>
+<Text id="480"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="481"><i>GBPlug</i></Text>
+</th>
+<th>
+<Text id="482">Trata el texto electrÃ³nico del Proyecto Gutenberg, que incluye informaciÃ³n sobre tÃ­tulos introducida manualmente.</Text>
+</th>
+<th>
+<Text id="483"><i>.txt.gz, .html, .htm</i></Text>
+</th>
+<th>
+<Text id="484"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="485"><i>TCCPlug</i></Text>
+</th>
+<th>
+<Text id="486">Trata los documentos de correo electrÃ³nico procedentes deÂ <i>ComputistsÂŽ Weekly</i>Â (el semanario de los informÃ¡ticos)</Text>
+</th>
+<th>
+<Text id="487">Debe empezar por <i>tcc o cw</i></Text>
+</th>
+<th>
+<Text id="488"><i>-</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="489">Los programas de creaciÃ³n de colecciÃ³n utilizan conectores de tratamiento de documentos para analizar los documentos de origen en funciÃ³n de su formato. En el archivo de configuraciÃ³n de colecciÃ³n se enumeran todos los conectores utilizados durante el proceso de creaciÃ³n. Durante la operaciÃ³n de importaciÃ³n, cada archivo o directorio pasa uno a uno por todos los conectores, siguiendo el orden establecido, hasta que encuentra uno que puede tratarlo; asÃ­ pues, los primeros conectores de la lista tienen prioridad sobre los Ãºltimos. Si ningÃºn conector puede tratar el archivo, aparece un aviso (en error estÃ¡ndar) y el tratamiento pasa al archivo siguiente. (En este caso la opciÃ³nÂ <i>block_exp</i>Â puede resultar Ãºtil a fin de evitar estos mensajes de error para los archivos que pueden estar presentes pero no necesitan tratamiento.) Durante la etapa de creaciÃ³n de la colecciÃ³n se aplica el mismo procedimiento, pero se trata el directorioÂ <i>archives</i>Â en lugar del directorioÂ <i>import</i>.</Text>
+<Text id="490">Los conectores estÃ¡ndar de Greenstone se enumeran en el Cuadro <CrossRef target="Table" ref="greenstone_plugins"/>. Es preciso utilizar un procedimiento recursivo para recorrer transversalmente jerarquÃ­as de directorios. Aunque los programas de importaciÃ³n y creaciÃ³n no efectÃºan una recursiÃ³n explÃ­cita, algunos conectores provocan una recursiÃ³n indirecta al introducir nombres de archivos o de directorios en la secuencia de los conectores. Por ejemplo, el modo estÃ¡ndar de recursiÃ³n a travÃ©s de una jerarquÃ­a de directorio consiste en especificarÂ <i>RecPlug</i>, que realiza exactamente esta operaciÃ³n. Si estÃ¡ presente, deberÃ­a ser el Ãºltimo elemento en la secuencia. SÃ³lo los dos primeros conectores del Cuadro <CrossRef target="Table" ref="greenstone_plugins"/> provocan una recursiÃ³n indirecta.</Text>
+<Text id="491">Algunos conectores estÃ¡n escritos para colecciones especÃ­ficas que tienen un formato de documento que no se encuentra en ninguna otra parte, como el texto electrÃ³nico utilizado en la colecciÃ³n Gutenberg. Estos conectores especÃ­ficos de una colecciÃ³n se encuentran en el directorioÂ <i>perllib/plugins</i>Â de la colecciÃ³n. Los conectores especÃ­ficos de colecciÃ³n pueden utilizarse para invalidar los conectores generales que llevan el mismo nombre.</Text>
+<Text id="492">Algunos conectores de tratamiento de documentos utilizan programas externos que analizan determinados formatos patentados, como por ejemplo Word de Microsoft, y los transforman en texto normal o en HTML. Un conector general denominadoÂ <i>ConvertToPlug</i>Â activa el programa de conversiÃ³n correspondiente y pasa el resultado aÂ <i>TEXTPlug</i>Â o aÂ <i>HTMLPlug</i>. MÃ¡s adelante se explicarÃ¡ mÃ¡s detalladamente esta operaciÃ³n.</Text>
+<Text id="493">Algunos conectores disponen de opciones especÃ­ficas que permiten controlar sus operaciones de manera mÃ¡s precisa que las opciones generales. VÃ©ase al respecto el Cuadro <CrossRef target="Table" ref="plugin-specific_options"/>.</Text>
+<Table id="plugin-specific_options">
+<Title>
+<Text id="494">Opciones especÃ­ficas de los conectores</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="@width"/>
+<th>
+<Text id="495"><b>OpciÃ³n</b></Text>
+</th>
+<th>
+<Text id="496"><b>Objetivo</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="497">HTMLPlug</Text>
+</th>
+<th>
+<Text id="498"><i>nolinks</i></Text>
+</th>
+<th>
+<Text id="499">No guarda enlaces dentro de la colecciÃ³n. Esto acelera el proceso de importaciÃ³n/creaciÃ³n, pero se pierden todos los enlaces de la colecciÃ³n.</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="500"><i>description_tags</i></Text>
+</th>
+<th>
+<Text id="501">Interpreta los archivos de documentos etiquetados como se explica en la subsecciÃ³n siguiente.</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="502"><i>keep_head</i></Text>
+</th>
+<th>
+<Text id="503">No quita los encabezados HTML.</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="504"><i>no_metadata</i></Text>
+</th>
+<th>
+<Text id="505">No busca ningÃºn metadato (esto puede acelerar el proceso de importaciÃ³n/creaciÃ³n).</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="506"><i>metadata_fields</i></Text>
+</th>
+<th>
+<Text id="507">Toma una lista separada por comas de tipos de metadatos (cuyo valor por defecto esÂ <i>Title</i>) que se han de extraer. Para cambiar el nombre de los metadatos en el archivo en el Formato de Archivo Greenstone, utiliceÂ <i>tag&lt;nuevo_nombre&gt;</i>, en queÂ <i>tag</i>Â es la etiqueta HTML buscada yÂ <i>nuevo_nombre</i>Â su nuevo nombre.</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="508"><i>hunt_creator_metadata</i></Text>
+</th>
+<th>
+<Text id="509">Encuentra el mayor nÃºmero posible de metadatos sobre la autorÃ­a del documento y los consigna en el documento en el Formato de Archivo Greenstone como metadatosÂ <i>Creator</i>. Se debe incluir tambiÃ©nÂ <i>Creator</i>Â mediante la opciÃ³nÂ <i>metadata_fields</i>.</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="510"><i>file_is_url</i></Text>
+</th>
+<th>
+<Text id="511">Utilice esta opciÃ³n si se ha usado un programa de duplicaciÃ³n o espejo Web para crear la estructura de los documentos por importar.</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="512"><i>assoc_files</i></Text>
+</th>
+<th>
+<Text id="513">Asigna una expresiÃ³n regular de Perl que define los tipos de archivos que se han de tratar como archivos asociados. Los tipos por defecto son:Â <i>.jpg</i>,Â <i>.jpeg</i>,Â <i>.gif</i>,Â <i>.png</i>,Â <i>.css.</i></Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="514"><i>rename_assoc_files</i></Text>
+</th>
+<th>
+<Text id="515">Cambia el nombre de los archivos asociados con los documentos. Durante este proceso, la estructura de directorio de todo archivo asociado reducirÃ¡ mucho su volumen (opciÃ³n Ãºtil si se ha de almacenar la colecciÃ³n en un espacio limitado).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="516"><i>HTMLPlug</i> y <br/><i>TEXTPlug</i></Text>
+</th>
+<th>
+<Text id="517"><i>title_sub</i></Text>
+</th>
+<th>
+<Text id="518">ExpresiÃ³n de sustituciÃ³n Perl para modificar los tÃ­tulos.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="519"><i>PSPlug</i></Text>
+</th>
+<th>
+<Text id="520"><i>extract_date</i></Text>
+</th>
+<th>
+<Text id="521">Extrae la fecha de creaciÃ³n del encabezado PostScript y la almacena como metadato.</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="522"><i>extract_title</i></Text>
+</th>
+<th>
+<Text id="523">Extrae el tÃ­tulo del documento del encabezado PostScript y lo almacena como metadato de tÃ­tulo.</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="524"><i>extract_pages</i></Text>
+</th>
+<th>
+<Text id="525">Extrae los nÃºmeros de pÃ¡gina del documento PostScript y los incluye en las secciones adecuadas como metadatos con la etiquetaÂ <i>Pages</i>.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="526"><i>RecPlug</i></Text>
+</th>
+<th>
+<Text id="527"><i>use_metadata_files</i></Text>
+</th>
+<th>
+<Text id="528">Asigna metadatos desde un archivo, como se explica en la subsecciÃ³n siguiente.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="529"><i>ImagePlug</i></Text>
+</th>
+<th>
+<Text id="530">Diversas opciones</Text>
+</th>
+<th>
+<Text id="531">VÃ©aseÂ <i>ImagePlug.pm</i>. </Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="532"><i>SRCPlug</i></Text>
+</th>
+<th>
+<Text id="533"><i>remove_prefix</i></Text>
+</th>
+<th>
+<Text id="534">Especifica en forma de expresiÃ³n regular de Perl,Â un patrÃ³n inicial que debe eliminarse del nombre del archivo. El comportamiento por defecto es suprimir toda la ruta.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="plugins_to_import_proprietary_formats">
+<Title>
+<Text id="535">Conectores de importaciÃ³n de formatos patentados</Text>
+</Title>
+<Content>
+<Text id="536">Los formatos patentados plantean serias dificultades para cualquier sistema de biblioteca digital. Aunque se disponga de documentaciÃ³n sobre su funcionamiento, pueden ser modificados sin aviso y resulta difÃ­cil mantenerse al tanto de los cambios. Greenstone ha optado por utilizar las aplicaciones de conversiÃ³n publicadas segÃºn los tÃ©rminos de la GPL (Licencia PÃºblica General de GNU) y elaboradas por personas dedicadas a esta tarea. Los instrumentos para convertir formatos Word y PDF se encuentran en el directorioÂ <i>packages</i>. Estos convierten los documentos en texto normal o en HTML. Se utilizan posteriormenteÂ <i>HTMLPlug</i>Â yÂ <i>TEXTPlug</i>Â para convertirlos en el Formato de Archivo Greenstone.Â <i>ConvertToPlug</i>Â sirve para incluir los instrumentos de conversiÃ³n y, al igual queÂ <i>BasPlug</i>, nunca se activa directamente, sino que los conectores de tratamiento de formatos especÃ­ficos derivan o heredan de Ã©l, como se ilustra en la Figura <CrossRef target="Figure" ref="plugin_inheritance_hierarchy"/>.Â <i>ConvertToPlug</i>Â emplea el sistema de herencia dinÃ¡mico de Perl para heredar deÂ <i>TEXTPlug</i>Â o deÂ <i>HTMLPlug</i>, segÃºn el formato en el que se ha convertido el documento de origen.</Text>
+<Figure id="plugin_inheritance_hierarchy">
+<Title>
+<Text id="537">JerarquÃ­a de herencia de los conectores</Text>
+</Title>
+<File width="206" height="229" url="images/Dev_Fig_9.png"/>
+</Figure>
+<Text id="538">CuandoÂ <i>ConvertToPlug</i>Â recibe un documento, acude aÂ <i>gsConvert.pl</i>Â (que se encuentra enÂ <i>GSDLHOME/bin/script</i>) para activar el instrumento de conversiÃ³n adecuado. Una vez convertido, el documento es devuelto aÂ <i>ConvertToPlug</i>, que aplica el conector texto o HTML, segÃºn convenga. Todo conector derivado deÂ <i>ConvertToPlug</i>Â dispone de una opciÃ³nÂ <i>convert_to</i>Â (convertir en), cuyo argumento esÂ <i>text</i>Â oÂ <i>html</i>, para especificar el formato intermedio que se prefiere. El formato texto es mÃ¡s rÃ¡pido, pero HTML suele tener una mejor presentaciÃ³n e incluye imÃ¡genes.</Text>
+<Text id="539">Existen a veces varios instrumentos de conversiÃ³n para un formato particular yÂ <i>gsConvert</i>Â puede probar varios de ellos en un documento. Por ejemplo, el instrumento de conversiÃ³n mÃ¡s comÃºn de Word,Â <i>wvWare</i>, sÃ³lo funciona con Word 6, y para convertir los documentos Word 5 se utiliza un programa denominadoÂ <i>AnyToHTML</i>, cuya principal funciÃ³n es extraer todas las cadenas de texto que puede encontrar.</Text>
+<Text id="540">Las etapas necesarias para agregar un nuevo programa de conversiÃ³n de documentos externos son las siguientes:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="541">Instale el nuevo programa de conversiÃ³n para que sea accesible por Greenstone (colÃ³quelo en el directorioÂ <i>packages</i>).</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="542">ModifiqueÂ <i>gsConvert.pl</i>Â para utilizar el nuevo programa de conversiÃ³n. Esto implica aÃ±adir una nueva clÃ¡usula a la instrucciÃ³nÂ <i>if</i>Â de la funciÃ³nÂ <i>main</i>, y agregar una funciÃ³n que active el programa de conversiÃ³n.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="543">Escriba un conector de nivel superior que herede deÂ <i>ConvertToPlug</i>Â para interceptar el formato y luego dejarlo âpasar adelanteâ.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Subsection>
+<Subsection id="assigning_metadata_from_a_file">
+<Title>
+<Text id="544">Asignar metadatos desde un archivo</Text>
+</Title>
+<Content>
+<Text id="545">El conector estÃ¡ndarÂ <i>RecPlug</i>Â incorpora asimismo la posibilidad de asignar metadatos a los documentos a partir de archivos XML creados manual o automÃ¡ticamente. Vamos a explicar detalladamente el proceso para que pueda usted crear archivos de metadatos en el formato adecuado. Si se especifica la opciÃ³nÂ <i>use_metadata_files</i>,Â <i>RecPlug</i>Â utiliza un archivo de metadatos auxiliar llamadoÂ <i>metadata.xml</i>. En la Figura <CrossRef target="Figure" ref="xml_format"/> se muestra la DefiniciÃ³n de Tipo de Documento (DTD) XML para el formato de archivo de metadatos, mientras que la figura <CrossRef target="Figure" ref="xml_format_1"/> muestra un ejemplo de archivoÂ <i>metadata.xml</i>.</Text>
+<Figure id="xml_format">
+<Title>
+<Text id="546">Formato XML:</Text>
+<SubTitle>
+<Text id="547">a) DefiniciÃ³n de Tipo de Documento (DTD);</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;!DOCTYPE GreenstoneDirectoryMetadataÂ Â  [</CodeLine>
+<CodeLine>&lt;!ELEMENT DirectoryMetadata (FileSet*)&gt;</CodeLine>
+<CodeLine>&lt;!ELEMENT FileSet (FileName+,Description)&gt;</CodeLine>
+<CodeLine>&lt;!ELEMENT FileName (#PCDATA)&gt;</CodeLine>
+<CodeLine>&lt;!ELEMENT Description (Metadata*)&gt;</CodeLine>
+<CodeLine>&lt;!ELEMENT Metadata (#PCDATA)&gt;</CodeLine>
+<CodeLine>&lt;ATTLIST Metadata name CDATA #REQUIRED&gt;</CodeLine>
+<CodeLine>&lt;ATTLIST Metadata mode (accumulate | override) âoverrideâ&gt;</CodeLine>
+<CodeLine>]&gt;</CodeLine>
+</Figure>
+<Figure id="xml_format_1">
+<Title>
+<Text id="548"/>
+<SubTitle>
+<Text id="549">b) Ejemplo de archivo de metadatos</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;?xml version="1.0"Â ?&gt;</CodeLine>
+<CodeLine>&lt;!DOCTYPE GreenstoneDirectoryMetadata SYSTEM</CodeLine>
+<CodeLine>"http://greenstone.org/dtd/GreenstoneDirectoryMetadata/1.0/GreenstoneDirectoryMetadata.dtdâ&gt;</CodeLine>
+<CodeLine>&lt;DirectoryMetadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â  &lt;FileSet&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;FileName&gt;nugget.*&lt;/FileName&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;Metadata name=âTitleâ&gt;Nugget Point Lighthouse&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;Metadata name=âPlaceâ mode=âaccumulateâ&gt;Nugget Point&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â  &lt;/FileSet&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â  &lt;FileSet&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;FileName&gt;nugget-point-1.jpg&lt;/FileName&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Â Â Â Â Â Â  &lt;Metadata name=âTitleâ&gt;Nugget Point Lighthouse, The Catlins&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Â Â Â Â Â Â  &lt;Metadata name=âSubjectâ&gt;Lighthouse&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â  &lt;FileSet&gt;</CodeLine>
+<CodeLine>&lt;/DirectoryMetadata&gt;</CodeLine>
+</Figure>
+<Text id="550">El archivo de ejemplo contiene dos estructuras de metadatos. En cada una de ellas, el elementoÂ <i>filename</i>Â describe los archivos a los que se aplican los metadatos en forma de expresiÃ³n regular. AsÃ­ pues, &lt;FileName&gt;nugget.*&lt;/FileName&gt;Â <i/>Â indica que el primer registro de metadatos se aplica a todos los archivos cuyo nombre empieza por âÂ <i>nugget</i>Â â<FootnoteRef id="2"/>. Para estos archivos, el metadatoÂ <i>Title</i>Â se aplica a âNugget Point Lighthouseâ.</Text>
+<Text id="551">Los elementos de metadatos se tratan en el orden en que aparecen. La segunda estructura establece que el metadatoÂ <i>Title</i>Â para el archivoÂ <i>nugget-point-1.jpg</i>Â se aplica a âNugget Point Lighthouse, The Catlinsâ e invalida la especificaciÃ³n anterior. AÃ±ade asimismo un campo de metadatosÂ <i>Subject</i>.</Text>
+<Text id="552">Algunas veces los metadatos poseen varios valores y los nuevos valores deben acumularse en vez de invalidar los anteriores. El atributoÂ <i>mode=accumulate</i>Â activa esta opciÃ³n. Se aplica al metadatoÂ <i>Place</i>Â en la primera especificaciÃ³n que, por consiguiente, podrÃ¡ adoptar mÃºltiples valores. Para volver a un metadato simple, teclee &lt;Metadata name=âPlaceâ mode=âoverrideâ&gt;New Zealand&lt;/Metadata&gt;Â <i>.</i>Â De hecho, se podrÃ­a omitir esta especificaciÃ³n de modo porque todo elemento invalida el anterior, salvo si se indica lo contrario. Para acumular metadatos en un campo particular, se debe especificarÂ <i>mode=accumulate</i>Â en cada apariciÃ³n.</Text>
+<Text id="553">Cuando se activa la opciÃ³nÂ <i>use_metadata_files</i>,Â <i>RecPlug</i>Â comprueba en cada directorio de entrada la presencia de un archivo XML denominadoÂ <i>metadata.xml</i>Â y aplica su contenido a todos los archivos y subdirectorios del directorio.</Text>
+<Text id="554">El mecanismoÂ <i>metadata.xml</i>Â incorporado aÂ <i>RecPlug</i>Â es sÃ³lo un modo de especificar los metadatos para los documentos. Es fÃ¡cil escribir diferentes conectores que aceptan especificaciones de metadatos con formatos completamente diferentes.</Text>
+</Content>
+</Subsection>
+<Subsection id="tagging_document_files">
+<Title>
+<Text id="555">Etiquetado de los archivos de documentos</Text>
+</Title>
+<Content>
+<Text id="556">Los documentos de origen necesitan a menudo estructurarse en secciones y subsecciones, y es preciso comunicar esta informaciÃ³n a Greenstone a fin de que pueda mantener la estructura jerÃ¡rquica. Asimismo, se pueden asociar metadatos âen particular el tÃ­tuloâ con cada secciÃ³n y subsecciÃ³n.</Text>
+<Text id="557">La manera mÃ¡s sencilla de efectuar esta operaciÃ³n suele ser modificando los archivos de origen. El conector HTML dispone de una opciÃ³nÂ <i>description_tags</i>Â que trata las etiquetas en el texto como sigue:</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â  &lt;Metadata name=âTitleâ&gt; Realizing human rights for poor people: Strategies for achieving the international development targets &lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="558"><i>(el texto de la secciÃ³n va aquÃ­)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="559">Se utilizan los marcadores &lt;!-- ... --&gt; porque indican comentarios en formato HTML; en consecuencia, estas etiquetas de secciÃ³n no afectarÃ¡n al formateo del documento. En la parteÂ <i>Description</i>Â se pueden especificar otros tipos de metadatos, pero esto no ocurre para el estilo de colecciÃ³n que mencionamos aquÃ­. Asimismo, las etiquetas pueden subdividirse, de tal modo que la lÃ­nea anterior seÃ±alada por marcadoresÂ <i>el texto de la secciÃ³n va aquÃ­</i>Â pueda incluir a su vez otras subsecciones, como por ejemplo:</Text>
+<Text id="560"><i>(el texto de la primera parte de la secciÃ³n va aquÃ­)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â  &lt;Metadata name=âTitleâ&gt; The international development targets &lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="561"><i>(el texto de la subsecciÃ³n va aquÃ­)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="562"><i>(el texto de la Ãºltima parte de la secciÃ³n va aquÃ­)</i></Text>
+<Text id="563">Cualquier conector que utilice HTMLPlug hereda esta funciÃ³n. El conector Word, en particular, convierte en formato HTML los datos que recibe y por ello se pueden especificar los metadatos exactamente de la misma manera en los archivos Word (y RTF). (Esto supone un poco de trabajo âentre bastidoresâ, porque cuando los documentos Word se convierten en HTML, el programa por lo general procura neutralizar la interpretaciÃ³n especial que suele hacer HTML de los signos sueltos â&lt;â y â&gt;â; nos las hemos arreglado para invalidar esto en el caso de las especificaciones antes mencionadas.) ObsÃ©rvese que se utiliza exactamente el mismo formato que antes, incluso en los archivos Word, asÃ­ como los signos de comentarios â&lt;!--â y â--&gt;â. El tipo de letra y el espaciado no se tienen en cuenta.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="classifiers">
+<Title>
+<Text id="564">Clasificadores</Text>
+</Title>
+<Content>
+<Text id="565">Los clasificadores sirven para crear los Ã­ndices de consulta de la colecciÃ³n. Valgan como ejemplos el Ã­ndiceÂ <i>tÃ­tulos A-Z</i>Â de la colecciÃ³nÂ <i>dlpeople</i>, asÃ­ como los Ã­ndicesÂ <i>tema</i>,Â <i>cÃ³mo...</i>,Â <i>organizaciones</i>Â yÂ <i>tÃ­tulos A-Z</i>Â de la Biblioteca sobre Aspectos Humanitarios y de Desarrollo, de la que la colecciÃ³n de demostraciÃ³n es un subconjunto. La barra de desplazamiento que aparece en la parte superior de la pantalla en las Figuras 3 y 8a incluye la funciÃ³nÂ <i>bÃºsqueda</i>, que siempre estÃ¡ disponible, seguida de botones correspondientes a todos los clasificadores que se han definido. La informaciÃ³n utilizada para facilitar la consulta se encuentra en la base de datos de informaciones de la colecciÃ³n, donde es colocada por los clasificadores activados durante la fase final del programaÂ <i>buildcol.pl</i>.</Text>
+<Figure id="azlist_classifier">
+<Title>
+<Text id="566">ClasificadorÂ <i>AZList</i></Text>
+</Title>
+<File width="604" height="245" url="images/Dev_Fig_11.png"/>
+</Figure>
+<Text id="567">Los clasificadores, al igual que los conectores, se especifican en el archivo de configuraciÃ³n de la colecciÃ³n. Todos tienen una lÃ­nea que empieza por la palabra claveÂ <i>classify</i>Â seguida del nombre del clasificador y las opciones que admite. El archivo bÃ¡sico de configuraciÃ³n de la colecciÃ³n mencionado en la SecciÃ³n <CrossRef target="Section" ref="import_and_build_processes"/> comprende la lÃ­neaÂ <i>classify AZList âmetadata Title</i>, que crea una lista alfabÃ©tica de tÃ­tulos reuniendo todos aquÃ©llos que estÃ¡n provistos del campo de metadatosÂ <i>Title</i>, y los clasifica y divide por orden alfabÃ©tico. En la Figura <CrossRef target="Figure" ref="azlist_classifier"/> se muestra un ejemplo.</Text>
+<Figure id="list_classifier">
+<Title>
+<Text id="568">ClasificadorÂ <i>List</i></Text>
+</Title>
+<File width="605" height="280" url="images/Dev_Fig_12.png"/>
+</Figure>
+<Text id="569">Un clasificador mÃ¡s simple, llamadoÂ <i>List</i>, que se muestra en la Figura <CrossRef target="Figure" ref="list_classifier"/>, crea una lista clasificada de un elemento de metadato determinado y lo presenta sin ninguna subsecciÃ³n alfabÃ©tica. Un ejemplo es el metadatoÂ <i>cÃ³mo</i>Â de la colecciÃ³n de demostraciÃ³n, que es generado por la lÃ­neaÂ <i>classify List âmetadata Howto</i>Â en el archivo de configuraciÃ³n de la colecciÃ³n. Otro clasificador general esÂ <i>DateList</i>, ilustrado en la Figura <CrossRef target="Figure" ref="datelist_classifier"/>, que genera una lista de selecciÃ³n de intervalos de fechas. (El clasificadorÂ <i>DateList</i>Â se utiliza tambiÃ©n en la colecciÃ³n âArchivos de Greenstoneâ.)</Text>
+<Figure id="datelist_classifier">
+<Title>
+<Text id="570">ClasificadorÂ <i>DateList</i></Text>
+</Title>
+<File width="604" height="304" url="images/Dev_Fig_13.png"/>
+</Figure>
+<Text id="571">Otros clasificadores generan estructuras de consulta que son explÃ­citamente jerÃ¡rquicas. Las clasificaciones jerÃ¡rquicas son Ãºtiles para las clasificaciones y subclasificaciones temÃ¡ticas, asÃ­ como para las jerarquÃ­as relativas a organizaciones. El archivo de configuraciÃ³n de la colecciÃ³n de demostraciÃ³n incluye la lÃ­neaÂ <i>classify Hierarchy âhfile sub.txt âmetadata Subject âsort Title</i>, y en la Figura <CrossRef target="Figure" ref="hierarchy_classifier"/> se muestra la jerarquÃ­a de temas que esta lÃ­nea produce. El estante que lleva un tÃ­tulo en negrita es el que se estÃ¡ examinando en este momento; encima de Ã©l se puede ver la clasificaciÃ³n temÃ¡tica a la que pertenece. En este ejemplo la jerarquÃ­a de clasificaciÃ³n se guarda en un formato de texto sencillo que lleva el nombre deÂ <i>sub.txt</i>.</Text>
+<Figure id="hierarchy_classifier">
+<Title>
+<Text id="572">ClasificadorÂ <i>Hierarchy</i></Text>
+</Title>
+<File width="605" height="321" url="images/Dev_Fig_14.png"/>
+</Figure>
+<Text id="573">Todos los clasificadores generan una estructura jerÃ¡rquica que se utiliza para mostrar un Ã­ndice de consulta. Normalmente, los niveles inferiores de la jerarquÃ­a (esto es, las hojas) son los documentos, pero en algunos clasificadores son las secciones. Los nodos internos de la jerarquÃ­a sonÂ <i>Vlist</i>,Â <i>Hlist</i>Â oÂ <i>Datelist</i>. UnaÂ <i>Vlist</i>Â es una lista de elementos dispuestos verticalmente en la pÃ¡gina, como el Ã­ndice âÂ <i>cÃ³mo...</i>Â â de la colecciÃ³n de demostraciÃ³n (vÃ©ase la Figura <CrossRef target="Figure" ref="list_classifier"/>). UnaÂ <i>Hlist</i>Â tiene una presentaciÃ³n horizontal. Por ejemplo, laÂ <i>AZList</i>Â de la Figura <CrossRef target="Figure" ref="azlist_classifier"/> es una jerarquÃ­a de nodos internos de dos niveles compuesta por unaÂ <i>Hlist</i>Â (que da el selector A-Z) cuyos elementos secundarios son nodosÂ <i>Vlists</i>Â ; los documentos son a su vez elementos secundarios de esta Ãºltima lista. Un nodoÂ <i>Datelist</i>Â (Figura <CrossRef target="Figure" ref="datelist_classifier"/>) es un tipo especial del nodoÂ <i>Vlist</i>Â que permite efectuar selecciones por aÃ±o y por mes.</Text>
+<Text id="574">Las lÃ­neas que se utilizan para especificar los clasificadores en los archivos de configuraciÃ³n de colecciÃ³n contienen un argumentoÂ <i>metadata</i>Â que identifica los metadatos mediante los cuales se clasifican y seleccionan los documentos. El clasificador omitirÃ¡ todo documento de la colecciÃ³n para el que no se haya definido este metadato (pero se lo indizarÃ¡ y, por consiguiente, la funciÃ³n bÃºsqueda lo tendrÃ¡ en cuenta). Si no se especifica un argumentoÂ <i>metadata</i>, todos los documentos se incluyen en el clasificador, en el orden en que aparecieron durante el proceso de creaciÃ³n. Esto es Ãºtil si desea obtener una lista de todos los documentos de su colecciÃ³n.</Text>
+<Table id="greenstone_classifiers">
+<Title>
+<Text id="575">Clasificadores de Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th>
+<Text id="576"><b>Argumento</b></Text>
+</th>
+<th>
+<Text id="577"><b>Finalidad</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="578"><i>Hierarchy</i></Text>
+</th>
+<th>
+<Text id="579">ClasificaciÃ³n jerÃ¡rquica</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="580"><i>hfile</i></Text>
+</th>
+<th>
+<Text id="581">Archivo de clasificaciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="582"><i>metadata</i></Text>
+</th>
+<th>
+<Text id="583">Elemento de metadato para cotejar con el identificadorÂ <i>hfile</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="584"><i>sort</i></Text>
+</th>
+<th>
+<Text id="585">Elemento de metadato utilizado para clasificar los documentos en las hojas (el valor por defecto esÂ <i>Title</i>)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="586"><i>buttonname</i></Text>
+</th>
+<th>
+<Text id="587">Nombre del botÃ³n utilizado para acceder a este clasificador (el valor por defecto es el valor del argumentoÂ <i>metadata</i>)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="588">List</Text>
+</th>
+<th>
+<Text id="589">Lista alfabÃ©tica de los documentos</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="590"><i>metadata</i></Text>
+</th>
+<th>
+<Text id="591">Incluye los documentos que contienen este elemento de metadato</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="592"><i>buttonname</i></Text>
+</th>
+<th>
+<Text id="593">Nombre del botÃ³n utilizado para acceder a este clasificador (el valor por defecto es el valor del argumentoÂ <i>metadata</i>)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="594"><i>SectionList</i></Text>
+</th>
+<th>
+<Text id="595">Lista de las secciones en los documentos</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="596"><i>AZList</i></Text>
+</th>
+<th>
+<Text id="597">Lista de documentos dividida por intervalos alfabÃ©ticos</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="598"><i>metadata</i></Text>
+</th>
+<th>
+<Text id="599">Incluye todos los documentos que contienen este elemento de metadato</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="600"><i>buttonname</i></Text>
+</th>
+<th>
+<Text id="601">Nombre del botÃ³n utilizado para acceder a este clasificador (el valor por defecto es el valor del argumentoÂ <i>metadata</i>)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="602"><i>AZSectionList</i></Text>
+</th>
+<th>
+<Text id="603">ComoÂ <i>AZList</i>Â pero incluye cada secciÃ³n del documento</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="604"><i>DateList</i></Text>
+</th>
+<th>
+<Text id="605">Similar aÂ <i>AZList</i>Â pero ordenada por fechas</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="606">La lista de los clasificadores actualmente disponibles aparece en el Cuadro <CrossRef target="Table" ref="greenstone_classifiers"/>. Al igual que se puede utilizar el programaÂ <i>pluginfo.pl</i>Â para obtener informaciÃ³n sobre cualquier conector, el programaÂ <i>classinfo.pl</i>Â le facilita informaciÃ³n sobre cualquier clasificador y las opciones que ofrece.</Text>
+<Text id="607">Todos los clasificadores aceptan el argumentoÂ <i>buttonname</i>, que define el contenido del botÃ³n de consulta de Greenstone que activa el clasificador (el valor por defecto es el nombre del argumentoÂ <i>metadata</i>). Existen botones para cada tipo de metadato del sistema Dublin Core y para algunos otros tipos de metadatos.</Text>
+<Text id="608">Cada clasificador recibe un nombre implÃ­cito con arreglo a su posiciÃ³n en el archivo de configuraciÃ³n. Por ejemplo, el tercer clasificador especificado en el archivo se denomina CL3. Esos nombres se emplean para nombrar los campos de la base de datos de informaciones de la colecciÃ³n que definen la jerarquÃ­a de los clasificadores.</Text>
+<Text id="609">Se pueden escribir clasificadores especÃ­ficos para una colecciÃ³n, que se almacenan en el directorioÂ <i>perllib/classify</i>Â de la colecciÃ³n. La Biblioteca sobre Aspectos Humanitarios y de Desarrollo tiene un clasificador especÃ­fico de colecciÃ³n que se llamaÂ <i>HDLList</i>, que es una variante menor deÂ <i>AZList</i>.</Text>
+<Subsection id="list_classifiers">
+<Title>
+<Text id="610">Clasificadores de listas</Text>
+</Title>
+<Content>
+<Text id="611">A continuaciÃ³n figuran los diversos tipos de clasificadores de listas:</Text>
+<BulletList>
+<Bullet>
+<Text id="612"><i>SectionList</i>Â : es comoÂ <i>List</i>Â pero las hojas son secciones y no documentos. Se incluyen todas las secciones del documento excepto las del nivel superior. Este clasificador sirve para crear listas de secciones (o de artÃ­culos, capÃ­tulos, etc.), como en la colecciÃ³nÂ <i>Computistsâ Weekly</i>Â (el semanario de los informÃ¡ticos, disponible en el sitio WebÂ <i>nzdl.org</i>), en la que cada nÃºmero es un solo documento que comprende varios artÃ­culos independientes, cada uno en su propia secciÃ³n.</Text>
+</Bullet>
+<Bullet>
+<Text id="613"><i>AZList</i>Â : genera una jerarquÃ­a de dos niveles que comprende un nodoÂ <i>Hlist</i>Â cuyos elementos secundarios son nodosÂ <i>Vlists</i>, cuyos elementos secundarios, a su vez, son documentos. El nodoÂ <i>Hlist</i>Â es un selector A-Z que divide los documentos en intervalos alfabÃ©ticos.</Text>
+</Bullet>
+<Bullet>
+<Text id="614"><i>AZSectionList</i>Â : es como AZList pero las hojas son secciones y no documentos.</Text>
+</Bullet>
+<Bullet>
+<Text id="615"><i>DateList</i>Â : es comoÂ <i>AZList</i>Â excepto que el nodoÂ <i>Hlist</i>Â de nivel superior permite seleccionar por aÃ±o y sus elementos secundarios son nodos de tipoÂ <i>DateList</i>Â y no de tipoÂ <i>Vlist</i>. El valor por defecto del argumentoÂ <i>metadata</i>Â esÂ <i>Date</i>.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="the_hierarchy_classifier">
+<Title>
+<Text id="616">El clasificadorÂ <i>hierarchy</i></Text>
+</Title>
+<Content>
+<Text id="617">Todos los clasificadores son jerÃ¡rquicos. Sin embargo, los clasificadores de listas antes mencionados disponen de un nÃºmero fijo de niveles, mientras que los clasificadores âÂ <i>hierarchy</i>Â â (jerÃ¡rquicos) tratados en esta secciÃ³n pueden crear una serie arbitraria de niveles y son mÃ¡s complejos de especificar que los clasificadores de listas.</Text>
+<Figure id="part_of_the_file_sub">
+<Title>
+<Text id="618">Parte del archivoÂ <i>sub.txt</i></Text>
+</Title>
+<CodeLine>1Â Â Â Â Â  1Â Â Â Â Â  "General reference"</CodeLine>
+<CodeLine>1.2Â Â Â  1.2Â Â Â  "Dictionaries, glossaries, language courses, terminology</CodeLine>
+<CodeLine>2Â Â Â Â Â  2Â Â Â Â Â  "Sustainable Development, International cooperation, Pro</CodeLine>
+<CodeLine>2.1Â Â Â  2.1Â Â Â  "Development policy and theory, international cooperatio</CodeLine>
+<CodeLine>2.2Â Â Â  2.2Â Â Â  "Development, national planning, national plans"</CodeLine>
+<CodeLine>2.3Â Â Â  2.3Â Â Â  "Project planning and evaluation (incl. project managem</CodeLine>
+<CodeLine>2.4Â Â Â  2.4Â Â Â  "Regional development and planning incl. regional profil</CodeLine>
+<CodeLine>2.5Â Â Â  2.5Â Â Â  "Nongovernmental organisations (NGOs) in general, self-</CodeLine>
+<CodeLine>2.6Â Â Â  2.6Â Â Â  "Organisations, institutions, United Nations (general, d</CodeLine>
+<CodeLine>2.6.1Â  2.6.1Â  "United Nations"</CodeLine>
+<CodeLine>2.6.2Â  2.6.2Â  "International organisations"</CodeLine>
+<CodeLine>2.6.3Â  2.6.3Â  "Regional organisations"</CodeLine>
+<CodeLine>2.6.5Â  2.6.5Â  "European Community - European Union"</CodeLine>
+<CodeLine>2.7Â Â Â  2.7Â Â Â  "Sustainable Development, Development models and example</CodeLine>
+<CodeLine>2.8Â Â Â  2.8Â Â Â  "Basic Human Needs"</CodeLine>
+<CodeLine>2.9Â Â Â  2.9Â Â Â  "Hunger and Poverty Alleviation"</CodeLine>
+</Figure>
+<Text id="619">El argumentoÂ <i>hfile</i>Â da el nombre de un archivo, como el de la Figura <CrossRef target="Figure" ref="part_of_the_file_sub"/>, que define la jerarquÃ­a de metadatos. Cada lÃ­nea describe una clasificaciÃ³n y las descripciones constan de tres partes:</Text>
+<BulletList>
+<Bullet>
+<Text id="620">Un identificador, que hace corresponder el valor del metadato (proporcionado por el argumentoÂ <i>metadata</i>) con la clasificaciÃ³n.</Text>
+</Bullet>
+<Bullet>
+<Text id="621">Un marcador de posiciÃ³n en la jerarquÃ­a, con forma numÃ©rica en varias partes, por ejemplo, 2, 2.12, 2.12.6.</Text>
+</Bullet>
+<Bullet>
+<Text id="622">El nombre de la clasificaciÃ³n. (Si contiene espacios, deberÃ¡ ponerse entre comillas)</Text>
+</Bullet>
+</BulletList>
+<Text id="623">La Figura <CrossRef target="Figure" ref="part_of_the_file_sub"/> forma parte del archivoÂ <i>sub.txt</i>Â utilizado para crear la jerarquÃ­a temÃ¡tica en la Biblioteca sobre Aspectos Humanitarios y de Desarrollo (y en la colecciÃ³n de demostraciÃ³n). Este ejemplo es un poco confuso porque el nÃºmero que representa la jerarquÃ­a aparece dos veces en cada lÃ­nea. El tipo de metadatoÂ <i>Hierarchy</i>Â se representa en los documentos con valores que adoptan una forma numÃ©rica jerÃ¡rquica, lo que corresponde a su primera apariciÃ³n. La segunda apariciÃ³n se utiliza para determinar la jerarquÃ­a que se aplica en el navegador.</Text>
+<Text id="624">El clasificadorÂ <i>hierarchy</i>Â tiene un argumento opcional,Â <i>sort</i>, que determina el modo en que se ordenan los documentos en las hojas. Se puede especificar cualquier metadato como criterio de ordenaciÃ³n. La lista se crea por defecto siguiendo el orden en que se encuentran los documentos durante el proceso de creaciÃ³n. El orden de los nodos internos viene determinado por el orden en que se especifican los elementos en el argumentoÂ <i>hfile</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_classifiers_work">
+<Title>
+<Text id="625">Funcionamiento de los clasificadores</Text>
+</Title>
+<Content>
+<Text id="626">Los clasificadores son objetos Perl, derivados deÂ <i>BasClas.pm</i>, y se almacenan en el directorioÂ <i>perllib/classify</i>. Se utilizan durante la creaciÃ³n de la colecciÃ³n. Su ejecuciÃ³n se hace en cuatro etapas:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="627">El mÃ©todoÂ <i>new</i>Â crea el objeto Clasificador.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="628">El mÃ©todoÂ <i>init</i>Â inicializa el objeto con parÃ¡metros como el tipo de metadato, el nombre del botÃ³n y el criterio de clasificaciÃ³n.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="629">El mÃ©todoÂ <i>classify</i>Â interviene una vez para cada documento, y guarda la informaciÃ³n sobre la clasificaciÃ³n efectuada dentro del objeto de clasificador.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="630">El mÃ©todoÂ <i>get_classify_info</i>Â transmite la informaciÃ³n de la clasificaciÃ³n localmente almacenada hacia el proceso de creaciÃ³n, que entonces la incluye en la base de datos de informaciones de la colecciÃ³n para su uso cuando la colecciÃ³n se visualiza en el momento de la ejecuciÃ³n.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="631">El mÃ©todoÂ <i>classify</i>Â recupera el OID de cada documento, el valor de metadato con el que se va a clasificar el documento y, si es necesario, el valor de metadato con el que se van a ordenar los documentos. El mÃ©todoÂ <i>get_classify_info</i>Â efectÃºa todas las funciones de ordenaciÃ³n y clasificaciÃ³n especÃ­ficas del clasificador. Por ejemplo, en el caso del clasificadorÂ <i>AZList</i>Â divide la lista en intervalos alfabÃ©ticos.</Text>
+<Text id="632">El proceso de creaciÃ³n de la colecciÃ³n activa los clasificadores en cuanto se crea el objetoÂ <i>builder</i>. Las clasificaciones se realizan durante la fase de creaciÃ³n, cuando se crea la base de datos de informaciones medianteÂ <i>classify.pm</i>, que se encuentra en el directorioÂ <i>perllib</i>Â de Greenstone.</Text>
+<Table id="items_appearing_in_format_strings">
+<Title>
+<Text id="633">Elementos que aparecen en las cadenas de formato</Text>
+</Title>
+<TableContent>
+<tr>
+<th>
+<Text id="634"><i>[Text]</i></Text>
+</th>
+<th>
+<Text id="635">El texto del documento</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="636"><i>[link]...[/link]</i></Text>
+</th>
+<th>
+<Text id="637">El HTML que debe enlazarse al propio documento</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="638"><i>[icon]</i></Text>
+</th>
+<th>
+<Text id="639">Un icono apropiado (por ejemplo, el pequeÃ±o icono de texto en una cadenaÂ <i>Resultados de la bÃºsqueda</i>)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="640"><i>[num]</i></Text>
+</th>
+<th>
+<Text id="641">El nÃºmero del documento (Ãºtil para depurar)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="642"><i>[metadata-name]</i></Text>
+</th>
+<th>
+<Text id="643">El valor de este elemento de metadato para el documento, por ejemplo,Â <i>[Title]</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="formatting_greenstone_output">
+<Title>
+<Text id="644">Formateo de la salida de Greenstone</Text>
+</Title>
+<Content>
+<Text id="645">Las pÃ¡ginas Web que usted ve cuando utiliza Greenstone no han sido almacenadas previamente sino que son generadas âal instanteâ a medida que se las necesita. La apariencia de numerosos aspectos de las pÃ¡ginas se controla a travÃ©s de las âcadenas de formatoâ. Las cadenas de formato se encuentran en el archivo de configuraciÃ³n de la colecciÃ³n y se introducen con la palabra claveÂ <i>format</i>Â seguida del nombre del elemento al que se aplica el formato. Las cadenas de formato controlan dos tipos diferentes de elementos de pÃ¡gina. El primero comprende los elementos de la pÃ¡gina que muestran documentos o partes de documentos. El segundo incluye las listas generadas por los clasificadores y las bÃºsquedas. Todas las cadenas de formato se interpretan en el momento en que se visualizan las pÃ¡ginas. Es rÃ¡pido y sencillo experimentar con las cadenas de formato ya que surten efecto en cuanto se guarda cualquier modificaciÃ³n en el archivoÂ <i>collect.cfg</i>.</Text>
+<Text id="646">En el Cuadro <CrossRef target="Table" ref="items_appearing_in_format_strings"/> se muestran las instrucciones de formato que afectan la apariencia de los documentos. La opciÃ³nÂ <i>DocumentButtons</i>Â controla los botones que aparecen en una pÃ¡gina de documento. En este caso,Â <i>cadena</i>Â es una lista de botones (separados por |) y sus valores posibles sonÂ <i>Detach</i>Â (separar),Â <i>Highlight</i>Â (resaltar),Â <i>Expand Text</i>Â (texto completo) yÂ <i>Expand contents</i>Â (expandir Ã­ndice). La modificaciÃ³n del orden de la lista modifica en consecuencia el orden de los botones.</Text>
+<Table id="the_format_options">
+<Title>
+<Text id="647">Las opciones de la palabra claveÂ <i>format</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th>
+<Text id="648"><i>format DocumentImages true/false</i></Text>
+</th>
+<th>
+<Text id="649">Si el valor esÂ <i>true</i>, muestra una imagen de portada en la parte superior izquierda de la pÃ¡gina del documento (el valor por defecto esÂ <i>false</i>).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="650"><i>format DocumentHeading cadena_de_formato</i></Text>
+</th>
+<th>
+<Text id="651">Si el valor deÂ <i>DocumentImages</i>Â esÂ <i>false</i>, la cadena de formato controla la apariencia del encabezado del documento que aparece en la parte superior izquierda de la pÃ¡gina del documento (el valor por defecto esÂ <i>[Title]</i>).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="652"><i>format DocumentContents true/false</i></Text>
+</th>
+<th>
+<Text id="653">Muestra el Ã­ndice (si el documento tiene una estructura jerÃ¡rquica), o flechas para ir a la secciÃ³n siguiente/anterior y el texto âpÃ¡gina k de nâ (en caso contrario).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="654"><i>format DocumentButtons cadena</i></Text>
+</th>
+<th>
+<Text id="655">Controla los botones que figuran en una pÃ¡gina de documento (el valor por defecto esÂ <i>Separar/Resaltar</i>).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="656"><i>format DocumentText cadena_de_formato</i></Text>
+</th>
+<th>
+<Text id="657">Formato de texto que se muestra en una pÃ¡gina de documento. El valor por defecto es:</Text>
+<CodeLine><i>&lt;center&gt;&lt;table width=537&gt;</i>
+</CodeLine>
+<CodeLine><i>&lt;tr&gt;&lt;td&gt;[Text]&lt;/td&gt;&lt;/tr&gt;</i>
+</CodeLine>
+<CodeLine><i>&lt;/table&gt;&lt;/center&gt;</i>
+</CodeLine>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="658"><i>format DocumentArrowsBottom true/false</i></Text>
+</th>
+<th>
+<Text id="659">Muestra las flechas para ir a la secciÃ³n siguiente/anterior en la parte inferior de la pÃ¡gina del documento (el valor por defecto esÂ <i>true</i>).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="660"><i>format DocumentUseHTML true/false</i></Text>
+</th>
+<th>
+<Text id="661">Si el valor esÂ <i>true</i>, cada documento aparece en un marco separado. La pÃ¡gina deÂ <i>Preferencias</i>Â cambia tambiÃ©n ligeramente, ya que propone opciones aplicables a una colecciÃ³n de documentos HTML, como la posibilidad de acudir directamente al documento original (en cualquier sitio de la Web) en lugar de ir a la copia efectuada por Greenstone.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Subsection id="formatting_greenstone_lists">
+<Title>
+<Text id="662">Formateo de las listas de Greenstone</Text>
+</Title>
+<Content>
+<Text id="663">Las cadenas de formato que controlan la apariencia de las listas pueden aplicarse a distintos niveles de la estructura de presentaciÃ³n. Pueden modificar todas las listas de determinado tipo dentro de una colecciÃ³n (por ejemplo,Â <i>DateList</i>) o todas las partes de una lista (por ejemplo, todas las entradas de la listaÂ <i>Search</i>Â (bÃºsqueda)) o determinadas partes de una lista particular (por ejemplo, la porciÃ³n vertical de la lista de un clasificadorÂ <i>AZList</i>Â aplicado a tÃ­tulos).</Text>
+<Text id="664">DespuÃ©s de la palabra claveÂ <i>format</i>Â hay otra palabra clave en dos partes, de las que sÃ³lo una es obligatoria. La primera parte identifica la lista a la que se aplica el formato. La lista que se obtiene mediante una bÃºsqueda se llamaÂ <i>Search</i>Â (bÃºsqueda), mientras que las listas generadas por clasificadores se denominanÂ <i>CL1, CL2, CL3</i>, etc., para el primer, segundo, tercer, etc., clasificador especificado en el archivoÂ <i>collect.cfg</i>. La segunda parte de la palabra clave se refiere a la porciÃ³n de la lista a la que se aplica el formateo, esto es,Â <i>Hlist</i>Â (para una lista horizontal, como el selector A-Z en un nodoÂ <i>AZList</i>),Â <i>Vlist</i>Â (para una lista vertical, como la lista de tÃ­tulos en un nodoÂ <i>AZList</i>) oÂ <i>DateList</i>. Por ejemplo:</Text>
+<Indented>
+<Text id="665"><i>format CL4Vlist ...</i>Â Â Â Â Â Â Â Â Â Â Â Â Â Â  se aplica a todos los VLists de CL4</Text>
+</Indented>
+<Indented>
+<Text id="666"><i>format CL2Hlist ...</i>Â Â Â Â Â Â Â Â Â Â Â Â Â Â  se aplica a todos los HListsde CL2</Text>
+</Indented>
+<Indented>
+<Text id="667"><i>format CL1DateList ...</i>Â Â Â Â Â Â Â  se aplica a todos los DateListsde CL1</Text>
+</Indented>
+<Indented>
+<Text id="668"><i>format SearchVList ...</i>Â Â Â Â Â Â Â Â  se aplica a la lista de resultados de bÃºsqueda</Text>
+</Indented>
+<Indented>
+<Text id="669"><i>format CL3 ...</i>Â Â Â Â Â Â Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  se aplica a todos los nodos de CL3, a menos que se especifique lo contrario</Text>
+</Indented>
+<Indented>
+<Text id="670"><i>format Vlist ...</i>Â Â Â Â Â Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  se aplica a todos los Vlistsde todos los clasificadores, a menos que se especifique lo contrario</Text>
+</Indented>
+<Text id="671">En los ejemplos de la figura 16, las comillas (â...â) representan las especificaciones de formato HTML que controlan la informaciÃ³n y su presentaciÃ³n, tal como aparecen en las pÃ¡ginas Web que muestran el clasificador. Al igual que las especificaciones HTML, cualquier metadato puede aparecer entre corchetes: su valor se interpola en el lugar indicado. Asimismo, cualquiera de los elementos del Cuadro <CrossRef target="Table" ref="the_format_options"/> puede aparecer en las cadenas de formato. La sintaxis de las cadenas incluye tambiÃ©n una instrucciÃ³n condicional que se ilustra en un ejemplo mÃ¡s adelante.</Text>
+<Text id="672">Recuerde que todos los clasificadores producen jerarquÃ­as. Cada nivel de la jerarquÃ­a se visualiza en una de cuatro formas posibles. Ya hemos vistoÂ <i>Hlist</i>,Â <i>Vlist</i>Â yÂ <i>DateList</i>. Existe ademÃ¡sÂ <i>Invisible</i>, que es el modo en que se visualizan los niveles superiores de las jerarquÃ­as: en efecto, el nombre del clasificador aparece ya separadamente en la barra de desplazamiento de Greenstone.</Text>
+</Content>
+</Subsection>
+<Subsection id="examples_of_classifiers_and_format_strings">
+<Title>
+<Text id="673">Ejemplos de clasificadores y cadenas de formato</Text>
+</Title>
+<Content>
+<Figure id="excerpt_from_the_demo_collection_collect" class="withLineNumber">
+<Title>
+<Text id="674">Extracto del archivoÂ <i>collect.cfg</i>Â de la colecciÃ³n de demostraciÃ³n</Text>
+</Title>
+<CodeLine>classify Hierarchy Â Â Â Â Â  âhfile sub.txt âmetadata Subject âsort Title</CodeLine>
+<CodeLine>classify AZList -metadata Title</CodeLine>
+<CodeLine>classify HierarchyÂ Â Â Â Â Â  -hfile org.txt âmetadata Organisation âsort Title</CodeLine>
+<CodeLine>classify ListÂ Â Â Â Â Â Â Â Â Â Â  -metadata Howto</CodeLine>
+<CodeLine>format SearchVList Â Â Â Â Â  â&lt;td valign=top&gt;Â Â Â Â  [link][icon][/link]&lt;/td&gt;&lt;td&gt;{If}</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  {[parent (Allâ: â):Title], [parent (Allâ:â):Title]:}</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  [link][Title][/link]&lt;/td&gt;â</CodeLine>
+<CodeLine>format CL4Vlist â&lt;br&gt;[link][Howto][/link]â</CodeLine>
+<CodeLine>format DocumentImagesÂ Â Â  Â Â  true</CodeLine>
+<CodeLine>format DocumentTextÂ Â Â Â Â  Â Â  â&lt;h3&gt; [Title] &lt;/h3&gt;\\n\\n&lt;p&gt;[Text]â</CodeLine>
+<CodeLine>format DocumentButtonsÂ Â  Â Â  âExpand Text|Expand contents|Detach|Highlightâ</CodeLine>
+</Figure>
+<Text id="675">En la Figura <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/> se muestra una parte del archivo de configuraciÃ³n de la colecciÃ³n de demostraciÃ³n. La utilizamos como ejemplo porque comprende varios clasificadores con un formato muy elaborado. ObsÃ©rvese que las instrucciones de los archivos de configuraciÃ³n no deben contener caracteres de nueva lÃ­nea; en el Cuadro, hemos cortado las lÃ­neas mÃ¡s largas para facilitar su legibilidad.</Text>
+<Text id="676">La lÃ­nea 4 especifica el clasificadorÂ <i>How To</i>Â (cÃ³mo...) de la colecciÃ³n de demostraciÃ³n. Es la cuarta en el archivo de configuraciÃ³n de la colecciÃ³n y, por consiguiente, se denomina CL4. La instrucciÃ³n de formato correspondiente es la lÃ­nea 7 de la Figura <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>. La informaciÃ³n âcÃ³moâ se genera a partir del clasificadorÂ <i>List</i>Â y su estructura es la lista completa de tÃ­tulos que aparecen en la Figura <CrossRef target="Figure" ref="list_classifier"/>. Los tÃ­tulos tienen un enlace con los propios documentos: cuando se hace clic en un tÃ­tulo se abre el documento correspondiente. Los elementos secundarios del primer nivel de la jerarquÃ­a se visualizan comoÂ <i>Vlist</i>Â (lista vertical), es decir, las secciones se muestran verticalmente. Como indica la instrucciÃ³nÂ <i>format</i>Â asociada, cada elemento de la lista estÃ¡ en una nueva lÃ­nea (â&lt;br&gt;â) y contiene el texto del metadatoÂ <i>Howto</i>, vinculado por hipervÃ­nculo al documento en cuestiÃ³n.</Text>
+<Text id="677">La lÃ­nea 1 especifica la clasificaciÃ³nÂ <i>Subject</i>Â (tema) de la colecciÃ³n de demostraciÃ³n, denominada CL1 (la primera en el archivo de configuraciÃ³n); la lÃ­nea 3 especifica la clasificaciÃ³nÂ <i>Organisation</i>Â y se denomina CL3. Ambas son generadas por el clasificadorÂ <i>Hierarchy</i>Â y, por consiguiente, comprenden una estructura jerÃ¡rquica de objetosÂ <i>VList</i>.</Text>
+<Text id="678">La lÃ­nea 2 especifica el resto de la clasificaciÃ³n de la colecciÃ³n de demostraciÃ³n,Â <i>TÃ­tulos A-Z</i>Â (CL2). ObsÃ©rvese que no existen cadenas de formato asociadas a los clasificadores CL1 a CL3. Greenstone dispone de valores por defecto para cada tipo de cadena de formato y por lo tanto no es necesario configurar una cadena de formato a menos que se desee invalidar el valor por defecto.</Text>
+<Figure id="formatting_the_document">
+<Title>
+<Text id="679">Formateo del documento</Text>
+</Title>
+<File width="604" height="329" url="images/Dev_Fig_17.png"/>
+</Figure>
+<Text id="680">Estas explicaciones corresponden a las cuatro lÃ­neasÂ <i>classify</i>Â de la Figura <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>. Hay tambiÃ©n cuatro lÃ­neasÂ <i>format</i>. Ya hemos explicado la lÃ­neaÂ <i>CL4Vlist</i>. Las otras tres pertenecen al primer tipo de cadena de formato, ilustrado en el Cuadro <CrossRef target="Table" ref="items_appearing_in_format_strings"/>. La lÃ­nea 8, por ejemplo, coloca la imagen de portada en la parte superior izquierda de cada pÃ¡gina del documento. La lÃ­nea 9 formatea el texto del documento propiamente dicho, y coloca el tÃ­tulo del capÃ­tulo o secciÃ³n correspondiente justo ante del texto. Todos estos efectos se ilustran en la Figura <CrossRef target="Figure" ref="formatting_the_document"/>.</Text>
+<Figure id="formatting_the_search_results">
+<Title>
+<Text id="681">Formateo de los resultados de la bÃºsqueda</Text>
+</Title>
+<File width="604" height="291" url="images/Dev_Fig_18.png"/>
+</Figure>
+<Text id="682">La lÃ­nea 5 de la Figura <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/> es una especificaciÃ³n algo complicada que formatea la lista de resultados generada por una bÃºsqueda, cuyas porciones se muestran en la Figura <CrossRef target="Figure" ref="formatting_the_search_results"/>. Presentamos a continuaciÃ³n, una versiÃ³n simplificada de la cadena de formato:</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;</CodeLine>
+<CodeLine>&lt;td&gt;[link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="683">EstÃ¡ diseÃ±ada para aparecer como una lÃ­nea en un cuadro, que es como se formatea la lista de resultados de una consulta. Va acompaÃ±ada, como de costumbre, por un pequeÃ±o icono vinculado al texto, y por el tÃ­tulo del documento que establece un hipervÃ­nculo con el documento en cuestiÃ³n. </Text>
+<Text id="684">En esta colecciÃ³n, los documentos son jerÃ¡rquicos. De hecho, el hipervÃ­nculo anterior remite al tÃ­tulo de la secciÃ³n obtenido por la consulta. Sin embargo, serÃ­a preferible que incluyese tambiÃ©n el tÃ­tulo de la secciÃ³n que la contiene, del capÃ­tulo que contiene esta Ãºltima y del libro en el que se encuentra. Existe un elemento de metadato especial,Â <i>parent</i>, que no se guarda en los documentos pero que estÃ¡ implÃ­cito en cualquier documento jerÃ¡rquico y que genera este tipo de lista. Ãste remite al documento principal, o si se utiliza con el calificadorÂ <i>All</i>, remite a la lista de documentos principales emparentados jerÃ¡rquicamente, separada por una cadena de caracteres que se pueden precisar tras el calificadorÂ <i>All</i>. AsÃ­ pues,</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;</CodeLine>
+<CodeLine>&lt;td&gt;{[parent(AllÂŽ: ÂŽ):Title]: }[link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="685">produce una lista que contiene el tÃ­tulo del libro, el tÃ­tulo del capÃ­tulo, etc. que encierra la secciÃ³n buscada, separados por dos puntos, y mÃ¡s adelante por otro carÃ¡cter de dos puntos seguido de un hipervÃ­nculo con el tÃ­tulo de la secciÃ³n buscada.</Text>
+<Text id="686">Lamentablemente, si el objetivo buscado es un libro, no hay documento emparentado y, por lo tanto, aparecerÃ¡ una cadena vacÃ­a seguida de dos puntos. Para evitar tales problemas puede usted utilizar en una cadena de formato las instrucciones condicionalesÂ <i>if</i>Â yÂ <i>or</i>Â ...Â <i>else</i>Â :</Text>
+<CodeLine>{If} {[metadato],acciÃ³n-si-no-vacio, acciÃ³n-si-vacio}</CodeLine>
+<CodeLine>{Or} {acciÃ³n,else otra-acciÃ³n, else otra-acciÃ³n, etc}</CodeLine>
+<Text id="687">En cualquiera de los casos, se utilizan las llaves para seÃ±alar que las instrucciones deben interpretarse y no sÃ³lo considerarse como texto. La instrucciÃ³nÂ <i>if</i>Â comprueba si el metadato estÃ¡ vacÃ­o y elige la primera opciÃ³n si no es asÃ­; de lo contrario pasa a la segunda (si es que existe). Se puede utilizar cualquier elemento de metadato, incluso el metadato especialÂ <i>parent</i>. La instrucciÃ³nÂ <i>Or</i>Â evalÃºa todas las acciones por turno hasta que encuentra una que no estÃ© vacÃ­a. La envÃ­a entonces a la lista de resultados e ignora el resto de la lÃ­nea.</Text>
+<Text id="688">Volviendo a la lÃ­nea 5 de la Figura <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>, la cadena de formato completa es:</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;</CodeLine>
+<CodeLine>&lt;td&gt;{If}{[parent (AllÂŽ: ÂŽ):Title],</CodeLine>
+<CodeLine>Â Â Â  Â Â Â Â Â [parent (AllÂŽ: ÂŽ):Title]:}</CodeLine>
+<CodeLine>Â Â Â  [link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="689">De este modo la especificaciÃ³nÂ <i>parent</i>Â va precedida de un condicional que comprueba si el resultado estÃ¡ vacÃ­o y sÃ³lo muestra la cadena completa (Â <i>parent</i>) cuando estÃ¡ presente. Algunas veces,Â <i>parent</i>Â puede ser calificado porÂ <i>Top</i>Â en vez deÂ <i>All</i>, lo cual da el nombre del documento de nivel superior que encierra una secciÃ³n: en este caso, el nombre del libro. ConÂ <i>Top</i>Â no es necesaria una cadena de separaciÃ³n.</Text>
+<Text id="690">Para concluir, presentamos algunos ejemplos que ilustran otras funciones. En la Figura <CrossRef target="Figure" ref="datelist_classifier"/>,Â <i>DateList</i>Â se utiliza en la clasificaciÃ³nÂ <i>Fechas</i>Â de la colecciÃ³nÂ <i>Computistsâ Weekly</i>Â (el semanario de los informÃ¡ticos) y resulta ser el segundo clasificador, esto es, CL2. El clasificador y las especificaciones de formato se muestran mÃ¡s adelante. El clasificadorÂ <i>DateList</i>Â difiere deÂ <i>AZList</i>Â en que siempre clasifica por metadatosÂ <i>Date</i>Â y en que las ramas inferiores de la jerarquÃ­a de consulta utilizanÂ <i>DateList</i>Â en vez deÂ <i>Vlist</i>, con lo que se agrega el aÃ±o y el mes a la izquierda de las listas de documentos.</Text>
+<CodeLine>classify AZSectionList metadata=Creator</CodeLine>
+<CodeLine>format CL2Vlist â&lt;td&gt;[link][icon][/link]&lt;/td&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;td&gt;[Creator]&lt;/td&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;td&gt;&amp;nbsp;&amp;nbsp;[Title]&lt;/td&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;td&gt;[parent(Top):Date]&lt;/td&gt;â</CodeLine>
+<Text id="691">La especificaciÃ³n de formato muestra esosÂ <i>Vlists</i>Â de manera apropiada.</Text>
+<Text id="692">El mecanismo de cadena de formato es flexible pero difÃ­cil de aprender. La mejor manera de proceder es estudiando los archivos de configuraciÃ³n de colecciones existentes.</Text>
+</Content>
+</Subsection>
+<Subsection id="linking_to_different_document_versions">
+<Title>
+<Text id="693">Enlaces con diferentes versiones de documentos</Text>
+</Title>
+<Content>
+<Text id="694">El mecanismoÂ <i>[link] ... [/link]</i>Â en una cadena de formato, se crea un enlace con el formato HTML del documento, donde el hipervÃ­nculo es el tÃ­tulo del documento: cuando se hace clic en el enlace se abre la versiÃ³n HTML del documento. En algunas colecciones es Ãºtil poder visualizar otras versiones del documento. En una colecciÃ³n de documentos con formato Word de Microsoft, por ejemplo, es bueno poder abrir una versiÃ³n Word de cada documento en lugar de la HTML que se ha extraÃ­do de ella; lo mismo ocurre con los documentos PDF.</Text>
+<Text id="695">Para poder mostrar diferentes versiones de un documento, la soluciÃ³n es incorporar la informaciÃ³n necesaria (es decir, dÃ³nde se encuentran las demÃ¡s versiones) al formato de archivo de Greenstone del documento. Esta informaciÃ³n se representa en forma de metadatos. Recuerde que al colocar:</Text>
+<CodeLine>[link][Title][/link]</CodeLine>
+<Text id="696">en una cadena de formato, se crea un enlace con el formato HTML del documento, donde elÂ  hipervÃ­nculo es el tÃ­tulo del documento. Tanto los conectores de Word como los de PDF generan metadatosÂ <i>srclink</i>, de modo que si se introduce:</Text>
+<CodeLine>[srclink][Title][/srclink]</CodeLine>
+<Text id="697">en una cadena de formato, se crea un enlace con la versiÃ³n Word o PDF del documento, donde el hipervÃ­nculo es tambiÃ©n en este caso el tÃ­tulo del documento. A fin de que aparezcan los iconos correspondientes a los documentos Word y PDF, estos conectores generan tambiÃ©n metadatosÂ <i>srcicon</i>Â de tal forma que:</Text>
+<CodeLine>[srclink][srcicon][/srclink]</CodeLine>
+<Text id="698">crea un enlace etiquetado por el icono estÃ¡ndar de Word o PDF (segÃºn el caso) y no por el tÃ­tulo del documento.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="controlling_the_greenstone_user_interface">
+<Title>
+<Text id="699">Control de la interfaz de usuario de Greenstone</Text>
+</Title>
+<Content>
+<Text id="700">El conjunto de la interfaz de usuario de Greenstone se controla mediante macros que se encuentran listados en el directorioÂ <i>GSDLHOME/macrosÂ </i>. Estas macros estÃ¡n escritas en un lenguaje especialmente concebido para Greenstone y se utilizan en el momento de la ejecuciÃ³n para generar pÃ¡ginas Web. La traducciÃ³n del lenguaje macro al formato HTML es la Ãºltima etapa para mostrar una pÃ¡gina. AsÃ­ pues, las modificaciones de un archivo de macros afectan inmediatamente la presentaciÃ³n en pantalla y permiten experimentar rÃ¡pida y fÃ¡cilmente. Todos los archivos de macros que utiliza Greenstone se encuentran enÂ <i>GSDLHOME/etc/main.cfg</i>Â y se cargan cada vez que se arranca el programa. La Ãºnica excepciÃ³n es cuando se utiliza la Biblioteca Local de Windows: en este caso es necesario reiniciar el proceso.</Text>
+<Text id="701">Las pÃ¡ginas Web se generan al instante por numerosas razones y el sistema de macros le permite a Greenstone funcionar con la flexibilidad necesaria. Las pÃ¡ginas pueden presentarse en diversos idiomas y existe un archivo de macros diferente para almacenar todo el texto de la interfaz en cada lengua. Cuando Greenstone presenta una pÃ¡gina, el intÃ©rprete de macros comprueba la variable de idioma y carga la pÃ¡gina en la lengua apropiada (aunque no llega a traducir el contenido del documento). AdemÃ¡s, los valores de determinadas variables de visualizaciÃ³n, como el nÃºmero de documentos encontrados en una bÃºsqueda, no se conocen de antemano, sino que se interpolan en el texto de la pÃ¡gina mediante macros.</Text>
+<Subsection id="the_macro_file_format">
+<Title>
+<Text id="702">El formato de los archivos de macros</Text>
+</Title>
+<Content>
+<Text id="703">Los archivos de macros tienen la extensiÃ³nÂ <i>.dm</i>. Cada archivo define uno o mÃ¡sÂ <i>paquetes</i>Â (Â <i>packages</i>), cada uno de los cuales contiene una serie de macros utilizadas con un fin preciso y Ãºnico. Al igual que los clasificadores y los conectores, hay una base a partir de la cual se elaboran las macros, que se llamaÂ <i>base.dm</i>Â ; este archivo define el contenido bÃ¡sico de una pÃ¡gina.</Text>
+<Text id="704">Los nombres de las macros empiezan y terminan con una rayita de subrayado y su contenido se define mediante llaves. El contenido puede ser texto llano, HTML (incluidos los enlaces con pequeÃ±os programas (Â <i>applets</i>) de Java y JavaScript), nombres de macros o cualquier combinaciÃ³n de estos elementos. La siguiente macro procedente deÂ <i>base.dm</i>Â define el contenido de una pÃ¡gina en ausencia de cualquier otra macro que la invalide:</Text>
+<CodeLine>_content_ {&lt;p&gt;&lt;h2&gt;Oops&lt;/h2&gt;_textdefaultcontent_}</CodeLine>
+<Text id="705">En la parte superior de la pÃ¡gina aparecerÃ¡ el mensaje âOopsâ, seguido de la macro _textdefaultcontent_, que en inglÃ©s equivale aÂ  The requested page could not be found. Please use your browsers âbackâ button or the above home button to return to the Greenstone Digital Library, y en otros idiomas aparecerÃ¡ la correspondiente traducciÃ³n de esta frase. En espaÃ±ol, por ejemplo, se podrÃ¡ leer: No se pudo encontrar la pÃ¡gina solicitada. Pulse el botÃ³n âAtrÃ¡sâ o el botÃ³n de âPÃ¡gina principalâ para volver a la Biblioteca Digital Greenstone.</Text>
+<Text id="706">Las macros <i>_textdefaultcontent_</i>Â (contenido del texto por defecto) y <i>_content_</i>Â (contenido) se encuentran en el paqueteÂ <i>global</i>Â porque son necesarias para todas las partes de la interfaz de usuario. Las macros pueden utilizar como contenido macros de otros paquetes, mas para ello deben anteponer sus nombres y el de su paquete. Por ejemplo, la macro:</Text>
+<CodeLine>_collectionextra_ {Esta colecciÃ³n contiene_about:numdocs_documentos. Se constituyÃ³ por Ãºltima vez hace _about:builddate_ dÃ­as.}</CodeLine>
+<Text id="707">procede del archivoÂ <i>english.dm</i>Â y se utiliza como descripciÃ³n por defecto de una colecciÃ³n. Forma parte del paqueteÂ <i>global</i>, peroÂ <i>_numdocs_</i>Â y _Â <i>builddate</i>Â _ pertenecen ambas al paqueteÂ <i>about</i>, por elloÂ <i>about:</i>Â precede sus nombres.</Text>
+<Text id="708">Las macros suelen contener instrucciones condicionales que se parecen a las cadenas de formato condicionales antes mencionadas, aunque su apariencia difiere un poco. El formato bÃ¡sico es _Â <i>If</i>Â _Â <i>(x,y,z)</i>, en queÂ <i>x</i>Â es una condiciÃ³n,Â <i>y</i>Â es el contenido de la macro que se debe utilizar si esta condiciÃ³n se cumple, yÂ <i>z</i>Â el contenido que se debe utilizar en caso contrario. Los operadores de comparaciÃ³n son los mismos que los operadores simples utilizados en Perl (menor que, mayor que, igual a, diferente de). El siguiente ejemplo procedente del archivoÂ <i>base.dm</i>Â se utiliza para determinar cÃ³mo visualizar la parte superior de la pÃ¡ginaÂ <i>acerca de</i>Â de una colecciÃ³n:</Text>
+<CodeLine>_imagecollection_ {</CodeLine>
+<CodeLine>Â Â  _If_("_iconcollection_" ne "",</CodeLine>
+<CodeLine>Â Â Â Â Â Â  &lt;a href = "_httppageabout_"&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â  &lt;img src = "_iconcollection_" border = 0&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â  &lt;/a&gt;,</CodeLine>
+<CodeLine>Â Â Â Â Â Â  _imagecollectionv_)</CodeLine>
+<CodeLine>}</CodeLine>
+<Text id="709">Esto puede parecer un poco crÃ­ptico. La macroÂ <i>_iconcollection</i>Â _ desemboca en la cadena vacÃ­a si la colecciÃ³n carece de icono, o en el nombre del archivo de una imagen. Haciendo la parÃ¡frasis del cÃ³digo antes mencionado: si existe una imagen de colecciÃ³n, presentar el encabezado de pÃ¡ginaÂ <i>acerca de esta colecciÃ³n</i>Â (al que se remite mediante <i>_httppageabout_</i>) y luego esa imagen; de otro modo, utilizar la presentaciÃ³n alternativa <i>_imagecollectionv_</i>.</Text>
+<Text id="710">Las macros pueden incluir argumentos. Hay aquÃ­ una segunda definiciÃ³n de la macro <i>_imagecollection_</i> que sigue inmediatamente la definiciÃ³n antes indicada en el archivoÂ <i>base.dm</i>:</Text>
+<CodeLine>_imagecollection_[v=1]{_imagecollectionv_}</CodeLine>
+<Text id="711">El argumentoÂ <i>[v=1]</i>Â especifica que la segunda definiciÃ³n se utiliza cuando Greenstone se ejecuta en modo âsÃ³lo textoâ. Las macros de idiomas funcionan de la misma manera: todas especifican su lengua como argumento, salvoÂ <i>english.dm</i>Â porque es el idioma por defecto. Por ejemplo:</Text>
+<CodeLine>_textimagehome_ {Home Page}</CodeLine>
+<Text id="712">aparece en el archivo de macro de lengua inglesa, mientras que la versiÃ³n alemana es:</Text>
+<CodeLine>_textimagehome_ [l=de] {Hauptaseite}</CodeLine>
+<Text id="713">Las versiones inglesa y alemana se encuentran en el mismo paquete, aunque en archivos diferentes (las definiciones de paquetes pueden ocupar mÃ¡s de un archivo). Greenstone utiliza su argumentoÂ <i>l</i>Â en el momento de la ejecuciÃ³n para determinar quÃ© idioma se debe visualizar.</Text>
+<Figure id="part_of_the_aboutdm_macro_file">
+<Title>
+<Text id="714">Parte del archivo de macrosÂ <i>about.dm</i></Text>
+</Title>
+<CodeLine>package about</CodeLine>
+<CodeLine>############################################</CodeLine>
+<CodeLine># about page content</CodeLine>
+<CodeLine>############################################</CodeLine>
+<CodeLine>_pagetitle_ {_collectionname_}</CodeLine>
+<CodeLine>_content_ {</CodeLine>
+<CodeLine>&lt;center&gt;</CodeLine>
+<CodeLine>_navigationbar_</CodeLine>
+<CodeLine>&lt;/center&gt;</CodeLine>
+<CodeLine>_query:queryform_ </CodeLine>
+<CodeLine>&lt;p&gt;_iconblankbar_</CodeLine>
+<CodeLine>&lt;p&gt;_textabout_</CodeLine>
+<CodeLine>_textsubcollections_</CodeLine>
+<CodeLine>&lt;h3&gt;_help:textsimplehelpheading_&lt;/h3&gt;</CodeLine>
+<CodeLine>_help:simplehelp_</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine>_textabout_ {</CodeLine>
+<CodeLine>&lt;h3&gt;_textabcol_&lt;/h3&gt;</CodeLine>
+<CodeLine>_Global:collectionextra_</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="715">Por Ãºltimo, en la Figura <CrossRef target="Figure" ref="part_of_the_aboutdm_macro_file"/> se muestra un extracto del archivo de macrosÂ <i>about.dm</i>Â que se utiliza para configurar la pÃ¡ginaÂ <i>acerca de</i>Â de cada colecciÃ³n. Este ejemplo muestra la definiciÃ³n de tres macros: <i>_pagetitle_</i>, <i>_content_</i>Â y <i>_textabout_</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="using_macros">
+<Title>
+<Text id="716">UtilizaciÃ³n de las macros</Text>
+</Title>
+<Content>
+<Text id="717">Las macros son instrumentos de alta potencia que pueden parecer un poco complicados y crÃ­pticos. Sin embargo, con unos buenos conocimientos de HTML y un poco de prÃ¡ctica pueden convertirse en una manera rÃ¡pida y fÃ¡cil de personalizar su sitio Greenstone.</Text>
+<Text id="718">Supongamos, por ejemplo, que usted querÃ­a crear una pÃ¡gina estÃ¡tica parecida a su sitio Greenstone actual. Puede usted crear un nuevo paquete, que se llamarÃ¡Â <i>static</i>Â por ejemplo, en un nuevo archivo, e invalidar la macro _Â <i>content_</i>. Agregue el nuevo nombre de archivo a la lista de macros situadas enÂ <i>GSDLHOME/etc/main.cfg</i>Â que Greenstone carga cada vez que arranca. Por Ãºltimo, acceda a la nueva pÃ¡gina utilizando su URL Greenstone normal y aÃ±ada los argumentosÂ <i>?a=p&amp;p=static</i>Â (por ejemplo:Â <i>http://servidor/cgi-bin/library?a=p&amp;p=static</i>).</Text>
+<Text id="719">Para cambiar el âaspecto y estiloâ de Greenstone puede modificar los paquetesÂ <i>base</i>Â yÂ <i>style (estilo)</i>. Para cambiar la pÃ¡gina principal de Greenstone, modifique el paqueteÂ <i>home</i>Â (como se explica en laÂ <i>GuÃ­a de InstalaciÃ³n de la Biblioteca Digital Greenstone</i>). Para cambiar la pÃ¡gina de bÃºsqueda, modifiqueÂ <i>query.dm</i>.</Text>
+<Text id="720">Experimente sin miedo con las macros. Las modificaciones aparecen instantÃ¡neamente porque las macros se interpretan a medida que se visualizan las pÃ¡ginas. El lenguaje de macros es un instrumento Ãºtil que puede servirle para personalizar a su gusto el sitio Greenstone.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="the_packages_directory">
+<Title>
+<Text id="721">El directorioÂ <i>packages</i></Text>
+</Title>
+<Content>
+<Table id="the_packages_directory_1">
+<Title>
+<Text id="722">El directorioÂ <i>packages</i>Â (paquetes)</Text>
+</Title>
+<TableContent>
+<tr>
+<th>Â </th>
+<th>
+<Text id="723"><b>Paquete</b></Text>
+</th>
+<th>
+<Text id="724"><b>URL</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="725">mg</Text>
+</th>
+<th>
+<Text id="726">MG, abreviaciÃ³n inglesa de âManaging Gigabytesâ (gestiÃ³n de gigabytes). Programa de compresiÃ³n, indizaciÃ³n y bÃºsqueda que se utiliza para administrar la informaciÃ³n textual en las colecciones Greenstone.</Text>
+</th>
+<th>
+<Text id="727"><i>www.citri.edu.au/mg</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="728"><i>wget</i></Text>
+</th>
+<th>
+<Text id="729">Programa de duplicaciÃ³n de Web (espejo) utilizado por Greenstone. Escrito en C++.</Text>
+</th>
+<th>
+<Text id="730"><i>www.tuwien.ac.at/~prikryl/wget.html</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="731"><i>w3mir</i></Text>
+</th>
+<th>
+<Text id="732">Programa de duplicaciÃ³n de Web escrito en Perl. Este no es el programa de duplicaciÃ³n preferido por Greenstone porque se basa en una versiÃ³n obsoleta de un mÃ³dulo Perl (que se distribuye en el directorioÂ <i>w3mir</i>).</Text>
+</th>
+<th>
+<Text id="733"><i>www.math.uio.no/~janl/w3mir</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="734"><i>windows</i></Text>
+</th>
+<th>
+<Text id="735">Paquetes que se utilizan cuando se funciona con Windows.</Text>
+</th>
+<th>
+<Text id="736"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="737"><i>windows/gdbm</i></Text>
+</th>
+<th>
+<Text id="738">VersiÃ³n del administrador de base de datos de GNU creada para Windows. GDBM viene con las versiones estÃ¡ndar de Linux.</Text>
+</th>
+<th>
+<Text id="739"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="740"><i>windows/crypt</i></Text>
+</th>
+<th>
+<Text id="741">Programa de codificaciÃ³n utilizado para las contraseÃ±as en las funciones administrativas de Greenstone.</Text>
+</th>
+<th>
+<Text id="742"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="743"><i>windows/stlport</i></Text>
+</th>
+<th>
+<Text id="744">Biblioteca EstÃ¡ndar de Plantillas que se utiliza para compilar Greenstone con determinados compiladores de Windows.</Text>
+</th>
+<th>
+<Text id="745"><i>-</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="746"><i>wv</i></Text>
+</th>
+<th>
+<Text id="747">Convertidor del formato Word de Microsoft (para crear colecciones a partir de documentos Word), aligerado para Greenstone.</Text>
+</th>
+<th>
+<Text id="748"><i>sourceforge.net/projects/wvware</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="749"><i>pdftohtml</i></Text>
+</th>
+<th>
+<Text id="750">Convertidor del formato PDF que se utiliza para crear colecciones a partir de documentos PDF.</Text>
+</th>
+<th>
+<Text id="751"><i>www.ra.informatik.uni-stuttgart.de/~gosho/pdftohtml</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="752"><i>yaz</i></Text>
+</th>
+<th>
+<Text id="753">Programa cliente Z39.50 que se utiliza para lograr la compatibilidad de Greenstone con el protocolo Z39.50. El archivoÂ <i>README.gsdl</i>. informa de los progresos al respecto.</Text>
+</th>
+<th>
+<Text id="754"><i>www.indexdata.dk</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="755">El directorioÂ <i>packages</i>Â (paquetes), cuyo contenido se muestra en el Cuadro <CrossRef target="Table" ref="the_packages_directory_1"/>, es donde se guardan todos los cÃ³digos utilizados por Greenstone pero elaborados por otros equipos de investigadores. Todos los programas informÃ¡ticos distribuidos con Greenstone cumplen los requisitos de la Licencia PÃºblica General de GNU. Los ejecutables producidos por esos paquetes se colocan en el directorioÂ <i>bin</i>Â de Greenstone. Cada paquete se guarda en su propio directorio. Sus funciones varÃ­an considerablemente, desde indizar y comprimir hasta convertir documentos de Word de Microsoft en el formato HTML. Cada paquete tiene un archivo README (LÃAME) que proporciona informaciones complementarias sobre el mismo.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="the_greenstone_runtime_system">
+<Title>
+<Text id="756">EL SISTEMA DE EJECUCIÃN DE GREENSTONE</Text>
+</Title>
+<Content>
+<Text id="757">En este capÃ­tulo se explica el sistema de ejecuciÃ³n de Greenstone a fin de que usted pueda comprender, aumentar y ampliar sus posibilidades. El programa estÃ¡ escrito en C++ y hace un uso importante de la âherencia virtualâ. Si no conoce bien este lenguaje, es preferible que lo aprenda antes de seguir adelante. Deitel y Deitel (1994) propone un manual de introducciÃ³n general, pero Stroustroup (1997) es la referencia de mayor autoridad.</Text>
+<Text id="758">Empezaremos explicando la filosofÃ­a conceptual que sustenta el sistema de ejecuciÃ³n, ya que influye considerablemente en su implementaciÃ³n. Luego pasaremos a examinarÂ  detalladamente la implementaciÃ³n, que constituye la parte principal de este capÃ­tulo. La versiÃ³n de Greenstone que se expone aquÃ­ es la versiÃ³n CGI (Biblioteca Web para los usuarios de Windows). La versiÃ³n Biblioteca Local de Windows utiliza el mismo cÃ³digo fuente pero tiene un servidor Web incorporado como interfaz de usuario. AdemÃ¡s, la Biblioteca Local es un proceso de tipo persistente.</Text>
+<Section id="process_structure">
+<Title>
+<Text id="759">Estructura de los procesos</Text>
+</Title>
+<Content>
+<Figure id="overview_of_a_general_greenstone_system">
+<Title>
+<Text id="760">Resumen grÃ¡fico de un sistema Greenstone general</Text>
+</Title>
+<File width="483" height="468" url="images/Dev_Fig_20.png"/>
+</Figure>
+<Text id="761">En la Figura <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/> aparecen varios usuarios, representados por computadoras en la parte superior del diagrama, que acceden a tres colecciones de Greenstone. Antes de ser puestas en lÃ­nea, estas colecciones pasan por los procesos de importaciÃ³n y creaciÃ³n expuestos en los capÃ­tulos anteriores. En primer lugar, los documentos, que aparecen en la parte inferior de la figura, se importan en el Formato de ArchivoÂ  Greenstone, que es un formato XML. A continuaciÃ³n, los archivos en el Formato de Archivo Greenstone se incorporan a varios Ã­ndices de bÃºsqueda y a una base de datos de informaciones de la colecciÃ³n que incluye las estructuras jerÃ¡rquicas necesarias para las operaciones de consulta. Una vez hecho esto, la colecciÃ³n estÃ¡ lista para ser puesta en lÃ­nea y responder a las solicitudes de informaciÃ³n.</Text>
+<Text id="762">Los dos componentes fundamentales en la concepciÃ³n del sistema de ejecuciÃ³n son los ârecepcionistasâ y los âservidores de colecciÃ³nâ. Desde el punto de vista del usuario, un recepcionista es el punto de contacto con la biblioteca digital. Recibe los datos proporcionados por los usuarios mediante el teclado y los clics del ratÃ³n, los analiza y luego transmite una solicitud al correspondiente servidor (o servidores) de la colecciÃ³n. Este Ãºltimo localiza la informaciÃ³n solicitada y la envÃ­a al recepcionista para que la presente al usuario. Los servidores de colecciÃ³n actÃºan como un mecanismo abstracto que administra el contenido de la colecciÃ³n, mientras que los recepcionistas se encargan de la interfaz de usuario.</Text>
+<Figure id="greenstone_system_using_the_null_protocol">
+<Title>
+<Text id="763">Resumen grÃ¡fico de un sistema Greenstone general</Text>
+</Title>
+<File width="483" height="468" url="images/Dev_Fig_21.png"/>
+</Figure>
+<Text id="764">Como se muestra en la Figura <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/>, los recepcionistas se comunican con los servidores de colecciÃ³n mediante un protocolo definido. La implementaciÃ³n de este protocolo depende de la configuraciÃ³n de la computadora en la que se ejecuta el sistema de biblioteca digital. El caso mÃ¡s comÃºn, y el mÃ¡s sencillo, es cuando hay un recepcionista y un servidor de colecciÃ³n y ambos operan en la misma computadora. Eso es lo que se obtiene con la instalaciÃ³n por defecto de Greenstone. En este caso, los dos procesos se combinan para formar un solo ejecutable (denominadoÂ <i>library</i>) y, por consiguiente, la utilizaciÃ³n del protocolo se reduce a llamadas de funciÃ³n. A esto lo llamamosÂ <i>null protocol</i>Â (protocolo nulo) y es la base del sistema estÃ¡ndar de biblioteca digital Greenstone en su estado original. Esta configuraciÃ³n simplificada aparece en la Figura <CrossRef target="Figure" ref="greenstone_system_using_the_null_protocol"/>, en la que el recepcionista, el protocolo y el servidor de colecciÃ³n estÃ¡n unidos en una sola entidad, el programaÂ <i>library</i>Â (biblioteca). La finalidad de este capÃ­tulo es explicar cÃ³mo funciona.</Text>
+<Text id="765">Normalmente, un âservidorâ es un proceso persistente que, una vez iniciado, funciona indefinidamente y responde a cualquier solicitud que le llegue. No obstante, a pesar de su nombre, el servidor de colecciÃ³n en la configuraciÃ³n de protocolo nulo no es un servidor en el sentido estricto. De hecho, cada vez que se solicita una pÃ¡gina Web de Greenstone, se arranca el programaÂ <i>library</i>Â (mediante el mecanismo CGI), Ã©ste responde a la solicitud y luego se cierra. Lo llamamos âservidorâ porque tambiÃ©n estÃ¡ diseÃ±ado para funcionar con una configuraciÃ³n mÃ¡s general como la de la Figura <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/>.</Text>
+<Text id="766">Por mÃ¡s sorprendente que parezca, este ciclo de arranque, tratamiento y cierre no es tan lento como se podrÃ­a imaginar y el resultado es un servicio perfectamente utilizable. Sin embargo, el sistema es poco eficiente. Existe un mecanismo llamado Fast-CGI (<i>www.fastcgi.com</i>) que ofrece una buena soluciÃ³n de compromiso. Gracias a su utilizaciÃ³n, el programaÂ <i>library</i>Â puede permanecer en memoria despuÃ©s de la primera ejecuciÃ³n y recibir las subsiguientes series de argumentos CGI, con lo que se evita repetir la inicializaciÃ³n y su funciÃ³n se asemeja mÃ¡s a la de un servidor convencional. La utilizaciÃ³n de Fast-CGI es una opciÃ³n de Greenstone y se activa volviendo a compilar el cÃ³digo fuente con las bibliotecas adecuadas.</Text>
+<Text id="767">Como alternativa al protocolo nulo, hemos elaborado tambiÃ©n el protocolo Greenstone utilizando el famoso sistema CORBA (SlamaÂ <i>et al.</i>, 1999), que utiliza un paradigma unificado orientado a objetos, para permitir a distintos procesos ejecutÃ¡ndose en distintas plataformas informÃ¡ticas e implementados en diferentes lenguajes de programaciÃ³n, acceder a la misma serie de objetos distribuidos por Internet (o cualquier otra red). AsÃ­ pues, una situaciÃ³n como la de la Figura <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/>, en la que todos los recepcionistas y los servidores de colecciÃ³n operan en diferentes computadoras, es perfectamente viable.</Text>
+<Figure id="graphical_query_interface_to_greenstone">
+<Title>
+<Text id="768">Interfaz grÃ¡fica de consultas de Greenstone</Text>
+</Title>
+<File width="397" height="347" url="images/Dev_Fig_22.png"/>
+</Figure>
+<Text id="769">Ello permite la instalaciÃ³n de interfaces mucho mÃ¡s complejas para distribuir exactamente las mismas colecciones de biblioteca digital. A modo de ejemplo, en la Figura <CrossRef target="Figure" ref="graphical_query_interface_to_greenstone"/> se muestra una interfaz grÃ¡fica de consultas, basada en los diagramas de Venn, que permite a los usuarios manipular directamente las consultas booleanas. Escrita en Java, la interfaz funciona localmente en la computadora del usuario. Con el sistema CORBA, se puede acceder a un servidor remoto de colecciÃ³n de Greenstone, escrito en C++.</Text>
+<Text id="770">No nos extenderemos mÃ¡s sobre este tema en el presente manual, ya que el protocolo distribuido sigue siendo objeto de perfeccionamiento y mejoras para su utilizaciÃ³n (para obtener mÃ¡s informaciÃ³n, vÃ©ase BainbridgeÂ <i>et al</i>., 2001).</Text>
+</Content>
+</Section>
+<Section id="conceptual_framework">
+<Title>
+<Text id="771">Marco conceptual</Text>
+</Title>
+<Content>
+<Figure id="generating_the_about_this_collection_page">
+<Title>
+<Text id="772">GeneraciÃ³n de la pÃ¡gina âAcerca de esta colecciÃ³nâ</Text>
+</Title>
+<File width="604" height="457" url="images/Dev_Fig_23.png"/>
+</Figure>
+<Text id="773">En la Figura <CrossRef target="Figure" ref="generating_the_about_this_collection_page"/> se muestra la pÃ¡gina âAcerca de esta colecciÃ³nâ de una colecciÃ³n Greenstone particular (la colecciÃ³n del Proyecto Gutenberg). FÃ­jese en la direcciÃ³n URL que aparece en la parte superior: esta pÃ¡gina se obtiene activando el programa CGIÂ <i>library</i>, que es el ejecutable anteriormente mencionado en que el recepcionista y el servidor de colecciÃ³n estÃ¡n conectados mediante el protocolo nulo. Los argumentos del programaÂ <i>library</i>Â sonÂ <i>c=gberg</i>,Â <i>a=p</i>,Â <i>p=about</i>Â yÂ <i>l=es</i>. Pueden interpretarse del modo siguiente:</Text>
+<Indented>
+<Text id="774">Para acceder a la colecciÃ³n del Proyecto Gutenberg (c=gberg), la acciÃ³n consiste en crear una pÃ¡gina (a=p) y la pÃ¡gina que hay que generar se llama âaboutâ (p=about), en espaÃ±ol (l=es).</Text>
+</Indented>
+<Figure id="greenstone_runtime_system">
+<Title>
+<Text id="775">Sistema de ejecuciÃ³n de Greenstone</Text>
+</Title>
+<File width="287" height="467" url="images/Dev_Fig_24.png"/>
+</Figure>
+<Text id="776">La Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/> ilustra las principales partes del sistema de ejecuciÃ³n de Greenstone. En la parte superior, el recepcionista inicializa primero sus componentes, luego analiza los argumentos CGI para decidir quÃ© acciÃ³n activar. Al ejecutar la acciÃ³n (que incluye nuevos tratamientos de los argumentos CGI), el programa utiliza el protocolo para acceder al contenido de la colecciÃ³n. Se utiliza la respuesta para generar una pÃ¡gina Web, con la asistencia del componente de formato y del lenguaje de macros.</Text>
+<Text id="777">El lenguaje de macros, que ya examinamos en la SecciÃ³n <CrossRef target="Section" ref="controlling_the_greenstone_user_interface"/>, se utiliza para conferir al sistema de Biblioteca Digital Greenstone un estilo coherente y crear interfaces en diferentes lenguas. La interacciÃ³n con la biblioteca genera la estructura bÃ¡sica de las pÃ¡ginas Web y las macros del directorioÂ <i>GSDLHOME/macros</i>Â aportan el contenido.</Text>
+<Text id="778">El objeto Lenguaje de macros representado en la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/> se encarga de leer estos archivos y de memorizar el resultado del anÃ¡lisis. Cualquier acciÃ³n puede utilizar este objeto para ampliar una macro. Puede incluso crear nuevas definiciones de macro e invalidar las anteriores, aportando asÃ­ una dimensiÃ³n dinÃ¡mica al uso de las macros.</Text>
+<Text id="779">La representaciÃ³n de la pÃ¡gina âAcerca de esta colecciÃ³nâ (Figura <CrossRef target="Figure" ref="generating_the_about_this_collection_page"/>) se conoce antes de la ejecuciÃ³n y estÃ¡ codificada en el archivo de macrosÂ <i>about.dm</i>. Los encabezados, los pies de pÃ¡gina y la imagen de fondo ni siquiera se mencionan porque se encuentran en el paquete de macrosÂ <i>Global</i>. Sin embargo, el texto especÃ­fico de âacerca deâ correspondiente a una colecciÃ³n particular no se conoce de antemano, sino que se guarda en la base de datos de informaciones de la colecciÃ³n durante el proceso de creaciÃ³n. Esta informaciÃ³n se recupera mediante el protocolo y se guarda como macro _Â <i>collectionextra_</i>Â en el paquete de macrosÂ <i>Global</i>. ObsÃ©rvese que este nombre de macro es prÃ¡cticamente el mismo que se empleÃ³ para expresar esta informaciÃ³n en el archivo de configuraciÃ³n de colecciÃ³n mencionado en la SecciÃ³n <CrossRef target="Section" ref="import_and_build_processes"/>. Para generar el contenido de la pÃ¡gina, se amplÃ­a la macro _Â <i>content</i>Â _ en el paqueteÂ <i>about</i>Â (que se muestra en la Figura <CrossRef target="Figure" ref="part_of_the_aboutdm_macro_file"/>). Esta operaciÃ³n amplÃ­a a su vez _Â <i>textabout</i>Â _, que accede a la macro _Â <i>collectionextra</i>Â _ que acababa de colocarse allÃ­ de manera dinÃ¡mica.</Text>
+<Text id="780">Otro componente importante es el objeto Formato. Las instrucciones de formato en el archivo de configuraciÃ³n de colecciÃ³n inciden en la presentaciÃ³n de determinados elementos de informaciÃ³n, como se explica en la SecciÃ³n <CrossRef target="Section" ref="formatting_greenstone_output"/>. Su gestiÃ³n corre a cargo del objeto Formato representado en la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/>. La principal tarea de este objeto es analizar y evaluar instrucciones como las cadenas de formato de la Figura <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>. Tal como vimos en la SecciÃ³n <CrossRef target="Section" ref="formatting_greenstone_output"/>, Ã©stas pueden comprender referencias a metadatos entre corchetes (por ejemplo,Â <i>[Title]</i>), que han de recuperarse del servidor de colecciÃ³n. Se producen interacciones entre el objeto Formato y el objeto Lenguaje de macros, ya que las instrucciones de formato pueden incluir macros, que cuando se amplÃ­an incluyen metadatos, y cuando Ã©stos se amplÃ­an a su vez incluyen macros, y asÃ­ sucesivamente.</Text>
+<Text id="781">El servidor de colecciÃ³n, visible en la parte inferior de la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/>, experimenta tambiÃ©n un proceso de inicializaciÃ³n, en el que establece objetos Filtro y de fuente para responder a las solicitudes que recibe del protocolo, y un objeto BÃºsqueda para prestar asistencia en esta tarea. En Ãºltima instancia, los objetos acceden a los Ã­ndices y las bases de datos de informaciones de colecciÃ³n, ambos elaborados durante la creaciÃ³n de la colecciÃ³n.</Text>
+<Text id="782">Sin contar las lÃ­neas en blanco, el recepcionista contiene 15.000 lÃ­neas de cÃ³digo. El servidor de colecciÃ³n sÃ³lo contiene 5.000 lÃ­neas, el 75% de las cuales estÃ¡n ocupadas por archivos de encabezado. El servidor de colecciÃ³n es mÃ¡s compacto porque la recuperaciÃ³n de los datos se lleva a cabo mediante dos programas precompilados. Se utiliza MG, un sistema de recuperaciÃ³n de texto completo, para las bÃºsquedas y GDBM, un sistema de gestiÃ³n de bases de datos, para la gestiÃ³n de la base de datos de informaciones de colecciÃ³n.</Text>
+<Text id="783">Para facilitar la extensibilidad y la flexibilidad, Greenstone utiliza considerablemente el mÃ©todo de herencia, en particular, en los objetos AcciÃ³n, Filtro, Fuente y BÃºsqueda. Esto significa que, para manejar una simple biblioteca digital que sÃ³lo contenga colecciones de textos, usted tiene que aprender un poco mÃ¡s para programar el sistema. No obstante, esto tambiÃ©n significa que MG y GDBM podrÃ­an sustituirse fÃ¡cilmente si ello fuera necesario. AdemÃ¡s, la arquitectura del programa es lo suficientemente rica para admitir todas las posibilidades multimedia, como el control de la interfaz por medio de sistemas de reconocimiento de voz oÂ  consultas en forma de grÃ¡fica.</Text>
+</Content>
+</Section>
+<Section id="how_the_conceptual_framework_fits_together">
+<Title>
+<Text id="784">Ajuste del marco conceptual</Text>
+</Title>
+<Content>
+<Text id="785">En las Secciones <CrossRef target="Section" ref="collection_server"/> y <CrossRef target="Section" ref="receptionist"/> se explica mÃ¡s detalladamente el funcionamiento del servidor de colecciÃ³n y del recepcionista, se amplÃ­a la informaciÃ³n sobre los mÃ³dulos de la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/> y se explica su implementaciÃ³n. Es conveniente, en primer lugar, ilustrar con ejemplos la interacciÃ³n de un usuario con el programa Greenstone y luego explicar lo que sucede âentre bastidoresâ. De momento, supondremos que todos los objetos estÃ¡n inicializados correctamente. La inicializaciÃ³n es un procedimiento bastante complejo que reexaminaremos en la SecciÃ³n <CrossRef target="Section" ref="initialisation"/>.</Text>
+<Subsection id="performing_a_search">
+<Title>
+<Text id="786">Efectuar una bÃºsqueda</Text>
+</Title>
+<Content>
+<Figure id="searching_gutenberg_for_darcy">
+<Title>
+<Text id="787">BÃºsqueda deÂ <i>Darcy</i>Â en el Proyecto Gutenberg</Text>
+</Title>
+<File width="604" height="375" url="images/Dev_Fig_25.png"/>
+</Figure>
+<Text id="788">Cuando un usuario introduce una consulta y pulsaÂ <i>Iniciar la bÃºsqueda</i>Â en la pÃ¡gina de bÃºsqueda, se activa una acciÃ³n Greenstone que culmina generando una nueva pÃ¡gina HTML mediante el lenguaje de macros. En la Figura <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/> se muestra el resultado de la bÃºsqueda del nombreÂ <i>Darcy</i>Â en la colecciÃ³n del Proyecto Gutenberg. La instrucciÃ³nÂ <i>a=q</i>Â se encuentra oculta en el HTML de la pÃ¡gina original de bÃºsqueda. Cuando se pulsa el botÃ³n de bÃºsqueda se activa esta instrucciÃ³n y se ejecuta la nueva acciÃ³nÂ <i>queryaction</i>. La ejecuciÃ³n deÂ <i>queryaction</i>Â consiste en una llamada al objeto Filtro de la colecciÃ³n designada (Â <i>c=gberg</i>) a travÃ©s del protocolo.</Text>
+<Text id="789">Los filtros desempeÃ±an una funciÃ³n bÃ¡sica importante en los servidores de colecciÃ³n. Adaptados a las actividades de bÃºsqueda y consulta, los filtros permiten seleccionar un subconjunto de informaciÃ³n en una colecciÃ³n. En este caso,Â <i>queryaction</i>Â inicia una solicitud de filtro:</Text>
+<BulletList>
+<Bullet>
+<Text id="790">estableciendo que el tipo de solicitud de filtro esÂ <i>QueryFilter</i>Â (los distintos tipos de filtro se explican en la SecciÃ³n <CrossRef target="Section" ref="collection_server"/>);</Text>
+</Bullet>
+<Bullet>
+<Text id="791">memorizando las preferencias de bÃºsqueda del usuario â reconocimiento de mayÃºsculas y minÃºsculas, truncamiento, etc.â en la solicitud de filtro;</Text>
+</Bullet>
+<Bullet>
+<Text id="792">activando la funciÃ³nÂ <i>filter( )</i>Â mediante el protocolo nulo.</Text>
+</Bullet>
+</BulletList>
+<Text id="793">Las llamadas al protocolo son sÃ­ncronicas. El recepcionista queda efectivamente bloqueado hasta que el servidor de colecciÃ³n trata la solicitud de filtro y se envÃ­an los datos generados.</Text>
+<Text id="794">Cuando se hace una llamada de protocolo de tipoÂ <i>QueryFilter</i>, el objeto de filtro (vÃ©ase la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/>) descodifica las opciones y llama al objeto BÃºsqueda, que utiliza MG para efectuar la bÃºsqueda propiamente dicha. La funciÃ³n del objeto BÃºsqueda es proporcionar una interfaz abstracta de programa que permita la bÃºsqueda, independientemente de la herramienta de bÃºsqueda subyacente que se utilice. El formato utilizado para enviar los resultados recurre tambiÃ©n a la abstracciÃ³n, lo cual obliga el objeto BÃºsqueda a traducir los datos generados por la herramienta de bÃºsqueda a una forma normalizada.</Text>
+<Text id="795">Una vez enviados los resultados de bÃºsqueda al recepcionista, se procede a formatearlos para su presentaciÃ³n utilizando los objetos Formato y Lenguaje de macros. Como se muestra en la Figura <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/>, esta operaciÃ³n supone: la creaciÃ³n del encabezado, el pie de pÃ¡gina, la barra de desplazamiento y la imagen de fondo normalizados de Greenstone; la repeticiÃ³n de la parte principal de la pÃ¡gina de consulta justo debajo de la barra de desplazamiento; y la presentaciÃ³n de un icono de libro, asÃ­ como el tÃ­tulo y el autor para cada uno de los resultados de la bÃºsqueda. El formato de esta Ãºltima parte depende de la instrucciÃ³nÂ <i>format SearchVList</i>Â que se encuentra en el archivo de configuraciÃ³n de la colecciÃ³n. Para poder mostrar los metadatos de tÃ­tulo y autor, Ã©stos han de recuperarse antes del servidor de colecciÃ³n, lo que requiere nuevas llamadas al protocolo, pero esta vez utilizandoÂ <i>BrowseFilter</i>Â (filtro de consulta).</Text>
+</Content>
+</Subsection>
+<Subsection id="retrieving_a_document">
+<Title>
+<Text id="796">RecuperaciÃ³n de un documento</Text>
+</Title>
+<Content>
+<Text id="797">Siguiendo con la bÃºsqueda anterior deÂ <i>Darcy</i>, obsÃ©rvese lo que sucede cuando visualiza un documento. En la Figura <CrossRef target="Figure" ref="the_golf_course_mystery"/> se muestra el resultado de pulsar el icono que se encuentra junto aÂ <i>The Golf Course Mystery</i>Â en la Figura <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/>.</Text>
+<Figure id="the_golf_course_mystery">
+<Title>
+<Text id="798"><i>The Golf Course Mystery</i></Text>
+</Title>
+<File width="465" height="461" url="images/Dev_Fig_26.png"/>
+</Figure>
+<Text id="799">El texto de origen de la colecciÃ³n Gutenberg consiste en un extenso archivo por cada libro. Durante la creaciÃ³n de la colecciÃ³n, dichos archivos se dividen en pÃ¡ginas separadas cada 200 lÃ­neas aproximadamente, y las informaciones importantes de cada pÃ¡gina se guardan en los Ã­ndices y en la base de datos de informaciones de la colecciÃ³n. En la parte superior de la Figura <CrossRef target="Figure" ref="the_golf_course_mystery"/> se indica que este libro tiene 104 pÃ¡ginas electrÃ³nicas, y justo debajo aparece el principio de la primera pÃ¡gina: el nombre de la persona que introdujo el texto, el tÃ­tulo, el autor y el principio de un Ã­ndice (dicho Ã­ndice forma parte del texto de origen del Proyecto Gutenberg y no ha sido generado por Greenstone). En la parte superior izquierda se ven los botones que controlan la presentaciÃ³n del documento: una sola pÃ¡gina o la totalidad del documento, si se resalta o no el tÃ©rmino de la consulta, y si se muestra o no el libro en su propia ventana, separado de la actividad principal de bÃºsqueda y consulta. En la parte superior derecha hay un asistente de consulta que proporciona acceso directo a cualquier pÃ¡gina del libro: basta con escribir el nÃºmero de la pÃ¡gina y pulsar el botÃ³n âir a la pÃ¡ginaâ. Asimismo, se pueden consultar las pÃ¡ginas anteriores y posteriores haciendo clic en los iconos de flecha situados de cada lado del dispositivo de selecciÃ³n de pÃ¡gina.</Text>
+<Text id="800">La operaciÃ³n de recuperaciÃ³n de documentos,Â <i>documentaction</i>, se especifica mediante la configuraciÃ³nÂ <i>a=d</i>Â y requiere varios argumentos suplementarios. Lo mÃ¡s importante es el documento por recuperar: Ã©ste se define mediante la variableÂ <i>d</i>. En la Figura <CrossRef target="Figure" ref="the_golf_course_mystery"/> su valor esÂ <i>d=HASH51e598821ed6cbbdf0942b.1</i>Â para recuperar la primera pÃ¡gina del documento cuyo identificador esÂ <i>HASH51e598821ed6cbbdf0942b</i>, y que en tÃ©rminos mÃ¡s convencionales se conoce comoÂ <i>The Golf Course Mystery</i>. Hay otras variables mediante las cuales se determina si el tÃ©rmino de bÃºsqueda ha de resaltarse o no (Â <i>hl</i>) y quÃ© pÃ¡gina del libro se debe mostrar (Â <i>gt</i>). Estas variables complementan las opciones propuestas por los botones de la pÃ¡gina Web representados en la Figura <CrossRef target="Figure" ref="the_golf_course_mystery"/> y antes mencionados. Se utilizan los valores por defecto cuando se omite cualquiera de estas variables.</Text>
+<Text id="801">Esta acciÃ³n sigue un procedimiento similar aÂ <i>queryaction</i>Â : examen de los argumentos CGI, acceso al servidor de colecciÃ³n mediante el protocolo y utilizaciÃ³n del resultado para generar una pÃ¡gina Web. Las opciones relativas al documento se descodifican a partir de los argumentos CGI y se guardan en el objeto para operaciones ulteriores. Para recuperar el documento desde el servidor de colecciÃ³n, sÃ³lo se necesita el identificador de documento para efectuar la llamada de protocoloÂ <i>get_document( )</i>. Una vez enviado el documento, queda por hacer un trabajo considerable de formateo. Para ello, el cÃ³digo deÂ <i>documentaction</i>Â accede a los argumentos almacenados y utiliza los objetos Formato y Lenguaje de macros.</Text>
+</Content>
+</Subsection>
+<Subsection id="browsing_a_hierarchical_classifier">
+<Title>
+<Text id="802">Consulta de un clasificador jerÃ¡rquico</Text>
+</Title>
+<Content>
+<Text id="803">En la Figura <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/> se muestra un ejemplo de consulta, en que el usuario ha elegidoÂ <i>tÃ­tulos a-z</i>Â y ha accedido al hipervÃ­nculo de la letraÂ <i>K</i>. Esta operaciÃ³n se basa tambiÃ©n enÂ <i>documentaction,</i>Â funciÃ³n proporcionada por la especificaciÃ³n del argumento CGIÂ <i>a=d</i>, como en el caso anterior. Sin embargo, la diferencia es que antes se incluyÃ³ la variableÂ <i>d</i>Â y esta vez no. En su lugar, el nodo de la jerarquÃ­a de clasificaciÃ³n por visualizar se especifica con la variableÂ <i>cl</i>, que en este caso representa los tÃ­tulos agrupados bajo la letraÂ <i>K</i>. Esta lista se constituyÃ³ durante el proceso de creaciÃ³n y estÃ¡ guardada en la base de datos de informaciones de la colecciÃ³n.</Text>
+<Figure id="browsing_titles_in_the_gutenberg_collection">
+<Title>
+<Text id="804">Consulta de los tÃ­tulos de la colecciÃ³n Gutenberg</Text>
+</Title>
+<File width="605" height="519" url="images/Dev_Fig_27.png"/>
+</Figure>
+<Text id="805">Los registros que representan nodos de clasificador en la base de datos utilizan el prefijoÂ <i>CL</i>, seguido de nÃºmeros separados por puntos (.) para indicar dÃ³nde se encuentran dentro de la estructura de subdivisiones. Si se ignora el botÃ³n de bÃºsqueda (visible en el extremo izquierdo de la barra de desplazamiento), los clasificadores se numeran secuencialmente por orden ascendente, de izquierda a derecha, empezando por 1. AsÃ­ pues, el nodo de clasificador de primer nivel para los tÃ­tulos en nuestro ejemplo esÂ <i>CL1</i>, y la pÃ¡gina buscada se obtiene indicandoÂ <i>cl=CL1.11</i>, como puede verse en la direcciÃ³n URL que aparece en la parte superior de la Figura <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/>.</Text>
+<Text id="806">Para tratar una solicitud de documento de tipoÂ <i>cl</i>, se utiliza el objeto Filtro para recuperar el nodo a travÃ©s del protocolo. SegÃºn los datos enviados, se efectÃºan ulteriores llamadas de protocolo para recuperar los metadatos de los documentos. En este caso, se obtienen los tÃ­tulos de los libros. Sin embargo, si se tratara de un nodo interno cuyos elementos secundarios fueran a su vez nodos, se recuperarÃ­an tambiÃ©n los tÃ­tulos de los nodos secundarios. Desde el punto de vista de la codificaciÃ³n es lo mismo y de ello se encarga el mismo mecanismo.</Text>
+<Text id="807">Por Ãºltimo, toda la informaciÃ³n recuperada se interconecta mediante el lenguaje de macros a fin de crear la pÃ¡gina Web que se muestra en la Figura <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/>.</Text>
+</Content>
+</Subsection>
+<Subsection id="generating_the_home_page">
+<Title>
+<Text id="808">GeneraciÃ³n de la pÃ¡gina principal</Text>
+</Title>
+<Content>
+<Figure id="greenstone_home_page">
+<Title>
+<Text id="809">PÃ¡gina principal de Greenstone</Text>
+</Title>
+<File width="604" height="571" url="images/Dev_Fig_28.png"/>
+</Figure>
+<Text id="810">Como Ãºltimo ejemplo, examinaremos el caso de la generaciÃ³n de la pÃ¡gina principal de Greenstone. En la Figura <CrossRef target="Figure" ref="greenstone_home_page"/> se muestra âen el caso de la instalaciÃ³n por defecto de Greenstoneâ su pÃ¡gina principal tras la instalaciÃ³n de algunas colecciones de prueba. La direcciÃ³n URL, que puede verse en la parte superior de la pantalla, incluye los argumentosÂ <i>a=p</i>Â yÂ <i>p=home</i>. AsÃ­ pues, al igual que en el caso de la pÃ¡gina âAcerca de esta colecciÃ³nâ, Ã©sta se genera mediante unaÂ <i>pageaction</i>Â (a=p), pero esta vez la pÃ¡gina creada esÂ <i>home</i>Â (Â <i>p=home</i>). Por consiguiente, el lenguaje de macros accede al contenido del archivoÂ <i>home.dm</i>. En este caso no es necesario especificar una colecciÃ³n (mediante la variableÂ <i>c</i>).</Text>
+<Text id="811">La finalidad de la pÃ¡gina principal es mostrar las colecciones disponibles. Cuando el usuario hace clic en un icono, aparece la pÃ¡gina âAcerca de esta colecciÃ³nâ de la colecciÃ³n correspondiente. Cada vez que se carga la pÃ¡gina, se genera dinÃ¡micamente el menÃº de las colecciones basÃ¡ndose en las colecciones que se encuentran en el sistema de archivos en ese momento. Cuando una nueva colecciÃ³n se pone en lÃ­nea, aparece automÃ¡ticamente en la pÃ¡gina principal cuando Ã©sta se vuelve a cargar, siempre que se haya especificado que la colecciÃ³n es âpÃºblicaâ.</Text>
+<Text id="812">Para ello, el recepcionista utiliza, desde luego, el protocolo. Como parte de su funciÃ³n de evaluaciÃ³n de los argumentos CGI, la acciÃ³nÂ <i>pageaction</i>Â estÃ¡ programada para detectar el caso particularÂ <i>p=home</i>. A continuaciÃ³n, la acciÃ³n utiliza la llamada de protocoloÂ <i>get_collection_list()</i>Â para establecer el conjunto de colecciones que se encuentran en lÃ­nea y activaÂ <i>get_collectinfo()</i>Â a fin de obtener informaciÃ³n sobre cada una de ellas. Dicha informaciÃ³n indica si la colecciÃ³n puede consultarse pÃºblicamente, cuÃ¡l es la direcciÃ³n URL del icono de la colecciÃ³n (si es que existe) y el nombre completo de la colecciÃ³n. Estos datos se utilizan para generar una entrada apropiada de la colecciÃ³n en la pÃ¡gina principal.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="source_code">
+<Title>
+<Text id="813">El cÃ³digo fuente</Text>
+</Title>
+<Content>
+<Table id="standalone_programs_included_in_greenstone">
+<Title>
+<Text id="814">Programas autÃ³nomos incluidos en Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="815"><i>setpasswd/</i></Text>
+</th>
+<th width="397">
+<Text id="816">Ayuda para las contraseÃ±as bajo Windows.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="817"><i>getpw/</i></Text>
+</th>
+<th width="397">
+<Text id="818">Ayuda para las contraseÃ±as bajo Unix.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="819"><i>txt2db/</i></Text>
+</th>
+<th width="397">
+<Text id="820">Convierte un formato de texto ASCII de tipo XML en formato de base de datos de GNU.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="821"><i>db2txt/</i></Text>
+</th>
+<th width="397">
+<Text id="822">Convierte el formato de base de datos de GNU en formato de texto ASCII de tipo XML. </Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="823"><i>phind/</i></Text>
+</th>
+<th width="397">Â Â Â Â Â Â Â Â Â Â Â Â  
+<Text id="824">Herramienta de consulta jerÃ¡rquica en los grupos de palabras.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="825"><i>hashfile/</i></Text>
+</th>
+<th width="397">Â Â Â Â Â Â Â Â  
+<Text id="826">Calcula un identificador de documento Ãºnico, basÃ¡ndose en el contenido del archivo.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="827"><i>mgpp/</i></Text>
+</th>
+<th width="397">Â Â Â Â Â Â Â Â Â Â Â Â Â  
+<Text id="828">VersiÃ³n reescrita y actualizada del paqueteÂ <i>Managing Gigabytes</i>Â en C++</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="829"><i>w32server/</i></Text>
+</th>
+<th width="397">Â Â Â Â  
+<Text id="830">Servidor de Biblioteca Local para Windows.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="831"><i>checkis/</i></Text>
+</th>
+<th width="397">Â Â Â Â Â Â Â Â Â  
+<Text id="832">Ayuda especÃ­fica para la instalaciÃ³n de Greenstone bajo Windows.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="833">El cÃ³digo fuente del sistema de ejecuciÃ³n se encuentra enÂ <i>GSDLHOME/src</i>. Ocupa dos subdirectorios,Â <i>recpt</i>Â para el cÃ³digo del recepcionista yÂ <i>colservr</i>Â para el del servidor de colecciÃ³n. Greenstone funciona bajo Windows a partir de la versiÃ³n Windows 3.1, lo cual impone desafortunadamente un mÃ¡ximo de ocho caracteres en los nombres de archivos y directorios. Esto explica la utilizaciÃ³n de abreviaciones crÃ­pticas comoÂ <i>recpt</i>Â yÂ <i>colservr</i>. Los demÃ¡s subdirectorios incluyen programas independientes que se utilizan principalmente para reforzar el proceso de creaciÃ³n (vÃ©ase el Cuadro <CrossRef target="Table" ref="standalone_programs_included_in_greenstone"/>).</Text>
+<Text id="834">Otro directorio,Â <i>GSDLHOME/lib</i>, incluye objetos de nivel inferior que el recepcionista y el servidor de colecciÃ³n utilizan. En la SecciÃ³n <CrossRef target="Section" ref="common_greenstone_types"/> se explica este cÃ³digo.</Text>
+<Text id="835">Greenstone utiliza considerablemente la Biblioteca EstÃ¡ndar de Plantillas (STL), una biblioteca C++ de amplia difusiÃ³n concebida por Silicon Graphics (Â <i>www.sgi.com</i>), y que es el resultado de numerosos aÃ±os de investigaciÃ³n y desarrollo. Como todas las bibliotecas de programaciÃ³n requiere un tiempo de aprendizaje. En el ApÃ©ndice A se presenta un breve resumen de las principales porciones que se utilizan en el cÃ³digo de Greenstone. Para una descripciÃ³n mÃ¡s completa, consulte el manual oficial de referencia de STL disponible en la direcciÃ³n InternetÂ <i>www.sgi.com</i>, o alguno de los numerosos manuales sobre STL, como por ejemplo el de Josuttis (1999).</Text>
+</Content>
+</Section>
+<Section id="common_greenstone_types">
+<Title>
+<Text id="836">Tipos bÃ¡sicos de Greenstone</Text>
+</Title>
+<Content>
+<Text id="837">Los elementos definidos en el directorioÂ <i>GSDLHOME/lib</i>Â son objetos Greenstone de nivel inferior, creados por encima de STL, y que se utilizan en todo el cÃ³digo fuente. En primer lugar, describimos con detallesÂ <i>text_t</i>, un objeto utilizado para representar texto Unicode y luego resumimos la finalidad de cada uno de los archivos de biblioteca.</Text>
+<Subsection id="the_text_t_object">
+<Title>
+<Text id="838">El objetoÂ <i>text_t</i></Text>
+</Title>
+<Content>
+<Text id="839">Greenstone funciona con mÃºltiples idiomas, tanto en lo que se refiere al contenido de una colecciÃ³n como a la interfaz de usuario. Para ello, se utiliza Unicode a todo lo largo del cÃ³digo fuente. El objeto subyacente que realiza una cadena Unicode esÂ <i>text_t</i>.</Text>
+<Figure id="the_text_t_api" class="withLineNumber">
+<Title>
+<Text id="840">La API deÂ <i>text_t</i>Â (abreviada)</Text>
+</Title>
+<CodeLine>typedef vector&lt;unsigned short&gt; usvector;</CodeLine>
+<CodeLine/>
+<CodeLine>class text_t {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>usvector text;</CodeLine>
+<CodeLine>unsigned short encoding; // 0 = unicode, 1 = other</CodeLine>
+<CodeLine/>
+<CodeLine>public:</CodeLine>
+<CodeLine>Â  // constructors</CodeLine>
+<CodeLine>Â  text_t ();</CodeLine>
+<CodeLine>Â  text_t (int i);</CodeLine>
+<CodeLine>Â  text_t (char *s); // assumed to be a normal c string</CodeLine>
+<CodeLine/>
+<CodeLine>Â  void setencoding (unsigned short theencoding);</CodeLine>
+<CodeLine>Â  unsigned short getencoding ();</CodeLine>
+<CodeLine/>
+<CodeLine>Â  // STL container support</CodeLine>
+<CodeLine>Â  iterator begin ();</CodeLine>
+<CodeLine>Â  iterator end (); </CodeLine>
+<CodeLine/>
+<CodeLine>Â  void erase(iterator pos);</CodeLine>
+<CodeLine>Â  void push_back(unsigned short c);</CodeLine>
+<CodeLine>Â  void pop_back();</CodeLine>
+<CodeLine/>
+<CodeLine>Â  void reserve (size_type n);</CodeLine>
+<CodeLine/>
+<CodeLine>Â  bool empty () const {return text.empty();}</CodeLine>
+<CodeLine>Â  size_type size() const {return text.size();}</CodeLine>
+<CodeLine/>
+<CodeLine>Â  // added functionality</CodeLine>
+<CodeLine>Â  void clear ();</CodeLine>
+<CodeLine>Â  void append (const text_t &amp;t);</CodeLine>
+<CodeLine/>
+<CodeLine>Â  // support for integers</CodeLine>
+<CodeLine>Â  void appendint (int i);</CodeLine>
+<CodeLine>Â  void setint (int i);</CodeLine>
+<CodeLine>Â  int getint () const;</CodeLine>
+<CodeLine/>
+<CodeLine>Â  // support for arrays of chars</CodeLine>
+<CodeLine>Â  void appendcarr (char *s, size_type len);</CodeLine>
+<CodeLine>Â  void setcarr (char *s, size_type len);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="841">Unicode necesita dos bytes para almacenar cada carÃ¡cter. En la Figura <CrossRef target="Figure" ref="the_text_t_api"/> se muestran las caracterÃ­sticas principales de la interfaz para programas de aplicaciÃ³n (API, esto es,Â <i>Application Program Interface</i>) deÂ <i>text_t</i>. El requisito de los dos bytes se cumple utilizando el tipo estÃ¡ndar C++Â <i>short</i>, que se define como un nÃºmero entero de dos bytes. El principal tipo de datos del objetoÂ <i>text_t</i>Â es una matriz dinÃ¡mica deÂ <i>unsigned</i><i>shorts</i>Â elaborada mediante la declaraciÃ³n STLÂ <i>vector&lt;unsigned short&gt;</i>Â y que recibe el nombre abreviado deÂ <i>usvector</i>.</Text>
+<Text id="842">Las funciones de creaciÃ³n (lÃ­neas 10-12) admiten explÃ­citamente tres formas de inicializaciÃ³n: creaciÃ³n sin parÃ¡metros, que genera una cadena Unicode vacÃ­a; creaciÃ³n con un parÃ¡metro entero, que genera una versiÃ³n de texto Unicode con el valor numÃ©rico proporcionado; y creaciÃ³n con un parÃ¡metroÂ <i>char*</i>, que trata el argumento como una cadena C++ terminada en cero y genera una versiÃ³n Unicode del mismo.</Text>
+<Text id="843">A continuaciÃ³n, la mayor parte del cÃ³digo (lÃ­neas 17-28) se ocupa de mantener un contenedor de tipo vector STL:Â <i>begin( )</i>,Â <i>end( )</i>,Â <i>push_back( )</i>,Â <i>empty( )</i>, etc. Permite asimismo borrar y concatenar cadenas, asÃ­ como convertir un nÃºmero entero en una cadena de texto Unicode y remitir el correspondiente valor entero a un texto que representa un nÃºmero.</Text>
+<Figure id="overloaded_operators_to_text_t" class="withLineNumber">
+<Title>
+<Text id="844">Operadores sobrecargados paraÂ <i>text_t</i></Text>
+</Title>
+<CodeLine>class text_t{</CodeLine>
+<CodeLine>Â Â Â Â Â  // ...</CodeLine>
+<CodeLine>Â Â Â Â Â  public:</CodeLine>
+<CodeLine>Â Â Â Â Â  text_t &amp;operator=(const text_t &amp;x);</CodeLine>
+<CodeLine>Â Â Â Â Â  text_t &amp;operator+=(const text_t &amp;t);</CodeLine>
+<CodeLine>Â Â Â Â Â  reference operator[](size_type n);</CodeLine>
+<CodeLine/>
+<CodeLine>Â Â Â Â Â  text_t &amp;operator=(int i);</CodeLine>
+<CodeLine>Â Â Â Â Â  text_t &amp;operator+= (int i);</CodeLine>
+<CodeLine>Â Â Â Â Â  text_t &amp;operator= (char *s);</CodeLine>
+<CodeLine>Â Â Â Â Â  text_t &amp;operator+= (char *s);</CodeLine>
+<CodeLine/>
+<CodeLine>Â Â Â Â Â  friend inline bool operator!=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>Â Â Â Â Â  friend inline bool operator==(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>Â Â Â Â Â  friend inline bool operator&lt; (const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>Â Â Â Â Â  friend inline bool operator&gt; (const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>Â Â Â Â Â  friend inline bool operator&gt;=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>Â Â Â Â Â  friend inline bool operator&lt;=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>Â Â Â Â Â  // ...</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="845">Existen numerosos operadores sobrecargados que no aparecen en la Figura <CrossRef target="Figure" ref="the_text_t_api"/>. La Figura <CrossRef target="Figure" ref="overloaded_operators_to_text_t"/> nos da una idea general de las operaciones posibles. La lÃ­nea 4 permite asignar un objetoÂ <i>text_t</i>Â a otro, y la lÃ­nea 5 sobrecarga el operador += para poder concatenar de modo mÃ¡s natural un objetoÂ <i>text_t</i>Â al final de otro. La lÃ­nea 6 permite asimismo tener acceso a un carÃ¡cter Unicode particular (representado como unÂ <i>short</i>) utilizando subÃ­ndices de matriz [ ]. Se proporcionan asimismo operadores de asignaciÃ³n y concatenaciÃ³n para los nÃºmeros enteros y las cadenas C++. Las lÃ­neas 12-18 suministran operadores booleanos para comparar dos objetosÂ <i>text_t</i>Â : igual a, diferente de, precede alfabÃ©ticamente, etc.</Text>
+<Text id="846">Existen asimismo funciones miembro que toman argumentos de tipoÂ <i>const</i>Â en lugar de argumentos noÂ <i>-const</i>, pero no se muestran aquÃ­. Dicha repeticiÃ³n es habitual en los objetos C++: aumenta el volumen de la API pero sin incrementarla conceptualmente. En realidad, muchas de estas funciones se implementan como instrucciones individuales de una sola lÃ­nea. Para mayor informaciÃ³n, consulte el archivo fuenteÂ <i>GSDLHOME/lib/text_t.h</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_greenstone_library_code">
+<Title>
+<Text id="847">El cÃ³digo de biblioteca Greenstone</Text>
+</Title>
+<Content>
+<Text id="848">Los archivos de encabezados situados en el directorioÂ <i>GSDLHOME/lib</i>Â comprenden una mezcla de funciones y objetos que contribuyen Ãºtilmente al sistema de ejecuciÃ³n de Greenstone. Cuando lo importante es la eficiencia, las funciones y las funciones miembro se especificanÂ <i>inline</i>. En la mayorÃ­a de los casos, los detalles de implementaciÃ³n se incluyen en el archivoÂ <i>.cpp</i>Â correspondiente al archivo de encabezados.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="100">
+<Text id="849"><b>cfgread.h</b></Text>
+</th>
+<th width="450">
+<Text id="850">Funciones de lectura y escritura de archivos de configuraciÃ³n. Por ejemplo, la funciÃ³nÂ <i>read_cfg_line( )</i>Â (leer archivo de configuraciÃ³n) toma como argumentos el flujo de entrada y la matrizÂ <i>text_tarray</i>Â (abreviaciÃ³n deÂ <i>vector&lt;text_t&gt;</i>) para rellenar con los datos leÃ­dos.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="851"><b>display.h</b></Text>
+</th>
+<th width="450">
+<Text id="852">Objeto complejo utilizado por el recepcionista para definir, almacenar y ampliar macros, y para manejar tipos. En la SecciÃ³n <CrossRef target="Section" ref="receptionist"/> se proporciona mayor informaciÃ³n al respecto.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="853"><b>fileutil.h</b></Text>
+</th>
+<th width="450">
+<Text id="854">Auxiliar para funciones de gestiÃ³n de archivos independientes del sistema operativo. Por ejemplo,Â <i>filename_cat( )</i>Â admite hasta seis argumentosÂ <i>text_t</i>Â y devuelve unÂ <i>text_t</i>Â que es el resultado de concatenar los elementos utilizando el separador de directorio adecuado para el sistema operativo en cuestiÃ³n.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="855"><b>gsdlconf.h</b></Text>
+</th>
+<th width="450">
+<Text id="856">Funciones especÃ­ficas del sistema que contestan a preguntas como: Â¿el sistema operativo que se estÃ¡ utilizando para la compilaciÃ³n necesita acceder al archivoÂ Â <i>strings.h</i>Â asÃ­ como al archivoÂ <i>string.h</i>Â ? Â¿Se han definido correctamente todos los valores apropiados para el bloqueo de archivos?</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="857"><b>gsdltimes.h</b></Text>
+</th>
+<th width="450">
+<Text id="858">FunciÃ³n de apoyo para fechas y horas. Por ejemplo,Â <i>time2text( )</i>Â toma la hora de la computadora, expresada como el nÃºmero de segundos transcurridos desde el 1Âº de enero de 1970, y la convierte en el formato AAAA/MM/DD hh:mm:ss, que devuelve como tipoÂ <i>text_t</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="859"><b>gsdltools.h</b></Text>
+</th>
+<th width="450">
+<Text id="860">Apoyo variado al sistema de ejecuciÃ³n de Greenstone: determina si se trata deÂ <i>littleEndian</i>Â oÂ <i>bigEndian</i>Â ; comprueba si Perl estÃ¡ disponible; ejecuta un comando del sistema (con âcampaneos y silbidosâ, esto es, con ciertas cualidades avanzadas y exageradas del programa); y elude los caracteres especiales de macro en una cadenaÂ <i>text_t</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="861"><b>gsdlunicode.h</b></Text>
+</th>
+<th width="450">
+<Text id="862">Serie de objetos heredados que admiten tratar las cadenasÂ <i>text_t</i>Â de Unicode a travÃ©s de flujos de entrada y salida, como las conversiones de Unicode en UTF-8 y viceversa; y la supresiÃ³n de los espacios de ancho cero. Administra asimismo los archivos de correspondencia mediante el objetoÂ <i>mapconvert</i>, y carga los cuadros de correspondencia en el directorioÂ <i>GSDLHOME/mappings</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="863"><b>text_t.h</b></Text>
+</th>
+<th width="450">
+<Text id="864">Principalmente el objeto de texto de Unicode antes expuesto. Proporciona asimismo dos clases de conversiÃ³n de flujos:Â <i>inconvertclass</i>Â yÂ <i>outconvertclass</i>. Son las clases de base utilizadas en el archivoÂ <i>gsdlunicode.h</i>.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="collection_server">
+<Title>
+<Text id="865">El servidor de colecciones</Text>
+</Title>
+<Content>
+<Text id="866">Ahora pasaremos a explicar sistemÃ¡ticamente todos los objetos del marco conceptual de la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/>. Empezaremos por la parte inferior del diagrama, que constituye ademÃ¡s la base del sistema, con los objetos BÃºsqueda (<i>Search</i>), Fuente (Â <i>Source</i>) y Filtro (Â <i>Filter</i>), y recorreremos las capas del protocolo hasta llegar a los componentes centrales del Recepcionista, Acciones, Formato y Lenguaje de macros. Luego nos centraremos en la inicializaciÃ³n de los objetos, ya que es mÃ¡s fÃ¡cil entender este proceso una vez que se conoce la funciÃ³n de los distintos objetos.</Text>
+<Text id="867">La mayorÃ­a de las clases fundamentales del marco conceptual se expresan mediante la herencia virtual para facilitar la extensibilidad. Mediante la herencia virtual, los objetos heredados se pueden transferir como su clase base, pero cuando se activa una funciÃ³n miembro, la versiÃ³n definida en el objeto heredado es la que se ejecuta. Como el cÃ³digo fuente de Greenstone utiliza la clase base en todas partes, excepto donde se crean los objetos, esto significa que se pueden insertar fÃ¡cilmente diferentes implementaciones, utilizando tal vez tecnologÃ­as subyacentes radicalmente diferentes.</Text>
+<Text id="868">Por ejemplo, supongamos que una clase de base denominadaÂ <i>BaseCalc</i>Â se encarga de la aritmÃ©tica elemental: suma, resta, multiplicaciÃ³n y divisiÃ³n. Si todas sus funciones se declaran virtuales, y todos los argumentos y tipos devueltos se declaran como cadenas, podemos implementar fÃ¡cilmente las versiones heredadas del objeto. Una de ellas, llamadaÂ <i>FixedPrecisionCalc</i>, podrÃ­a utilizar las funciones de la biblioteca C para las conversiones entre cadenas y nÃºmeros enteros e implementar los cÃ¡lculos con los operadores aritmÃ©ticos habituales: +, -, *,Â  y /. La otra, llamadaÂ <i>InfinitePrecisionCalc</i>, podrÃ­a acceder a los argumentos de cadena carÃ¡cter por carÃ¡cter, efectuando operaciones aritmÃ©ticas que en principio son de una precisiÃ³n infinita. Escribiendo un programa principal que utilizaÂ <i>BaseCalc</i>Â por doquier, la implementaciÃ³n puede pasar de la precisiÃ³n finita a la precisiÃ³n infinita modificando una sola lÃ­nea: el lugar donde se crea el objeto de cÃ¡lculo.</Text>
+<Subsection id="the_search_object">
+<Title>
+<Text id="869">El objeto BÃºsqueda (<i>Search</i>)</Text>
+</Title>
+<Content>
+<Figure id="search_base_class_api">
+<Title>
+<Text id="870">API de la clase base BÃºsqueda (<i>Search</i>)</Text>
+</Title>
+<CodeLine>class searchclass {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>Â  searchclass ();</CodeLine>
+<CodeLine>Â  virtual ~searchclass ();</CodeLine>
+<CodeLine>Â  // the index directory must be set before any searching</CodeLine>
+<CodeLine>Â  // is done </CodeLine>
+<CodeLine>Â  virtual void setcollectdir (const text_t &amp;thecollectdir);</CodeLine>
+<CodeLine>Â  // the search results are returned in queryresults</CodeLine>
+<CodeLine>Â  // search returns âtrueâ if it was able to do a search</CodeLine>
+<CodeLine>Â  virtual bool search(const queryparamclass &amp;queryparams,</CodeLine>
+<CodeLine>Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  queryresultsclass &amp;queryresults)=0;</CodeLine>
+<CodeLine>Â  // the document text for âdocnumâ is placed in âoutputâ</CodeLine>
+<CodeLine>Â  // docTargetDocument returns âtrueâ if it was able to</CodeLine>
+<CodeLine>Â  // try to get a document</CodeLine>
+<CodeLine>Â  // collection is needed to see if an index from the</CodeLine>
+<CodeLine>Â  // collection is loaded. If no index has been loaded</CodeLine>
+<CodeLine>Â  // defaultindex is needed to load one</CodeLine>
+<CodeLine>Â  virtual bool docTargetDocument(const text_t &amp;defaultindex,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const text_t &amp;defaultsubcollection,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const text_t &amp;defaultlanguage,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const text_t &amp;collection,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  int docnum,</CodeLine>
+<CodeLine>Â Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â text_t &amp;output)=0;</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>Â  querycache *cache;</CodeLine>
+<CodeLine>Â  text_t collectdir; // the collection directory</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="871">En la Figura <CrossRef target="Figure" ref="search_base_class_api"/> se muestra el API de la clase de base para el objeto de bÃºsqueda de la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/>. Define dos funciones miembro virtuales:Â <i>search( )</i>Â yÂ <i>docTargetDocument( )</i>. Tal como indica elÂ <i>=0</i>Â que sigue la declaraciÃ³n de argumento, se trata de funciones puras, lo que significa que una clase que hereda este objeto debe implementar ambas funciones (de otro modo el compilador se quejarÃ¡).</Text>
+<Text id="872">La clase incluye asimismo dos campos de datos protegidos:Â <i>collectdir</i>Â yÂ <i>cache</i>. Cuando se instancia un objeto de bÃºsqueda para una colecciÃ³n particular, se utiliza el campoÂ <i>collectdir</i>Â para determinar dÃ³nde estÃ¡ guardada esa colecciÃ³n (y, lo que es mÃ¡s importante, sus archivos de Ã­ndice) en el sistema de archivos. El campoÂ <i>cache</i>Â retiene el resultado de una consulta. Se utiliza para acelerar el tratamiento de consultas ulteriores que repiten la primera (y sus parÃ¡metros). Puede parecer improbable que se efectÃºen consultas idÃ©nticas, pero de hecho esto ocurre con bastante frecuencia. El protocolo de Greenstone es sin estado. A fin de generar una pÃ¡gina de resultados como la de la Figura <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/>, pero con los resultados 11-20 de la misma consulta, se transmite de nuevo la bÃºsqueda especificando, en este caso, que se presente la serie de documentos 11-20. El campoÂ <i>cache</i>Â acelera esta operaciÃ³n, puesto que se comprueba que la bÃºsqueda ya ha sido ejecutada y los resultados se sacan directamente de este campo.</Text>
+<Text id="873">Ambos campos de datos son aplicables a todos los objetos heredados que implementan un mecanismo de bÃºsqueda. Por ello aparecen en la clase de base y se declaran dentro de una secciÃ³n protegida de la clase, a fin de que las clases heredadas puedan acceder directamente a ellos.</Text>
+</Content>
+</Subsection>
+<Subsection id="search_and_retrieval_with_mg">
+<Title>
+<Text id="874">BÃºsqueda y recuperaciÃ³n con MG</Text>
+</Title>
+<Content>
+<Text id="875">Greenstone utiliza MG (abreviaciÃ³n deÂ <i>Managing Gigabytes</i>Â ; vÃ©ase WittenÂ <i>et al</i>., 1999) para indizar y recuperar documentos, y su cÃ³digo fuente se incluye en el directorioÂ <i>GSDLHOME/packages</i>. MG emplea tÃ©cnicas de compresiÃ³n para optimizar la utilizaciÃ³n del espacio de disco sin alterar la rapidez de ejecuciÃ³n. En el caso de una colecciÃ³n de documentos en inglÃ©s, el texto comprimido y los Ã­ndices suelen ocupar un tercio del espacio que necesitarÃ­a el texto original sin comprimir. La bÃºsqueda y recuperaciÃ³n suelen ser mÃ¡s rÃ¡pidas que las operaciones equivalentes en la versiÃ³n sin comprimir porque requieren menos operaciones en el disco duro.</Text>
+<Figure id="api_for_direct_access_to_mg">
+<Title>
+<Text id="876">API para acceder directamente a MG (abreviada)</Text>
+</Title>
+<CodeLine>enum result_kinds {</CodeLine>
+<CodeLine>Â  result_docs,Â Â Â Â Â  // Return the documents found in last search</CodeLine>
+<CodeLine>Â  result_docnums,Â Â  // Return document id numbers and weights</CodeLine>
+<CodeLine>Â  result_termfreqs, // Return terms and frequencies</CodeLine>
+<CodeLine>Â  result_termsÂ Â Â Â Â  // Return matching query terms</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>int mgq_ask(char *line);</CodeLine>
+<CodeLine>int mgq_results(enum result_kinds kind, int skip, int howmany,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  int (*sender)(char *, int, int, float, void *),</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â  Â Â Â Â Â Â Â void *ptr);</CodeLine>
+<CodeLine>int mgq_numdocs(void);</CodeLine>
+<CodeLine>int mgq_numterms(void);</CodeLine>
+<CodeLine>int mgq_equivterms</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â  (unsigned char *wordstem,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â  Â int (*sender)(char *, int, int, float, void *),</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â  Â void *ptr);</CodeLine>
+<CodeLine>int mgq_docsretrieved (int *total_retrieved, int *is_approx);</CodeLine>
+<CodeLine>int mgq_getmaxstemlen ();</CodeLine>
+<CodeLine>void mgq_stemword (unsigned char *word);</CodeLine>
+</Figure>
+<Text id="877">MG se utiliza por lo general de manera interactiva tecleando las instrucciones desde la lÃ­nea de comandos, y un modo de implementarÂ <i>mgsearchclass</i>Â serÃ­a activando la llamadaÂ <i>system( )</i>Â de la biblioteca C dentro del objeto para ejecutar los comandos MG apropiados. Sin embargo, un mÃ©todo mÃ¡s eficaz consiste en intervenir directamente en el cÃ³digo de MG utilizando las llamadas de funciÃ³n. Aunque esto requiere un mayor conocimiento del cÃ³digo de MG, una gran parte de la complejidad puede ocultarse tras una nueva API que pasarÃ¡ a ser el punto de contacto para el objetoÂ <i>mgsearchclass</i>. Ãsta es la funciÃ³n del archivoÂ <i>colserver/mgq.c</i>, cuya API se muestra en la Figura <CrossRef target="Figure" ref="api_for_direct_access_to_mg"/>.</Text>
+<Text id="878">Para proporcionar parÃ¡metros a MG, se usaÂ <i>mgq_ask( )</i>, que admite opciones de texto en un formato idÃ©ntico al que se usa en la lÃ­nea de comandos, como por ejemplo:</Text>
+<CodeLine>mgq_ask(â.set casefold offâ);</CodeLine>
+<Text id="879">Se utiliza asimismo para activar una consulta. Se accede a los resultados mediante la funciÃ³nÂ <i>mgq_results</i>, que adopta como cuarto parÃ¡metro un puntero dirigido hacia una funciÃ³n. Ello proporciona un modo flexible de convertir la informaciÃ³n devuelta en estructuras de datos de MG en el formato que requiereÂ <i>mgsearchclass</i>. Las operaciones comoÂ <i>mgq_numdocs( )</i>,Â <i>mgq_numterms( )</i>Â yÂ <i>mgq_docsretrieved( )</i>Â tambiÃ©n devuelven informaciÃ³n, pero prescritas de manera mÃ¡s precisa. Las dos Ãºltimas contribuyen a la funciÃ³n de truncamiento.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_source_object">
+<Title>
+<Text id="880">El objeto Fuente (<i>Source</i>)</Text>
+</Title>
+<Content>
+<Figure id="source_base_class_api">
+<Title>
+<Text id="881">API de la clase base Fuente (<i>Source</i>)</Text>
+</Title>
+<CodeLine>class sourceclass {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>Â  sourceclass ();</CodeLine>
+<CodeLine>Â  virtual ~sourceclass ();</CodeLine>
+<CodeLine>Â  // configure should be called once for each configuration line</CodeLine>
+<CodeLine>Â  virtual void configure (const text_t &amp;key, </CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>Â  // init should be called after all the configuration is done but</CodeLine>
+<CodeLine>Â  // before any other methods are called</CodeLine>
+<CodeLine>Â  virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>Â  // translate_OID translates OIDs using ".pr", ."fc" etc.</CodeLine>
+<CodeLine>Â  virtual bool translate_OID (const text_t &amp;OIDin, text_t &amp;OIDout,</CodeLine>
+<CodeLine>Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>Â  // get_metadata fills out the metadata if possible, if it is not</CodeLine>
+<CodeLine>Â  // responsible for the given OID then it returns false.</CodeLine>
+<CodeLine>Â  virtual bool get_metadata (const text_t &amp;requestParams, </CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Â Â const text_t &amp;refParams,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Â Â bool getParents,</CodeLine>
+<CodeLine>Â Â Â Â Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â const text_tset &amp;fields,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Â Â const text_t &amp;OID,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Â Â MetadataInfo_tmap &amp;metadata,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Â Â comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>Â  virtual bool get_document (const text_t &amp;OID, text_t &amp;doc,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Â Â comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>}; </CodeLine>
+</Figure>
+<Text id="882">La funciÃ³n del objeto Fuente (<i>Source</i>) de la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/> es acceder a los metadatos y al texto del documento; la API de su clase de base se muestra en la Figura <CrossRef target="Figure" ref="source_base_class_api"/>. Una funciÃ³n miembro se asigna a cada tarea: las funcionesÂ <i>get_metadata( )</i>Â yÂ <i>get_document( )</i>, respectivamente. Ambas se declaranÂ <i>virtual</i>, por lo que la versiÃ³n suministrada por una implementaciÃ³n particular de la clase de base se activa durante la ejecuciÃ³n. Una versiÃ³n heredada de este objeto utiliza GDBM para implementarÂ <i>get_metadata( )</i>Â y MG para implementarÂ <i>get_document( )</i>Â : a continuaciÃ³n explicaremos en detalle esta versiÃ³n.</Text>
+<Text id="883">Las otras funciones miembro que aparecen en la Figura <CrossRef target="Figure" ref="source_base_class_api"/> sonÂ <i>configure( )</i>,Â <i>init( )</i>Â yÂ <i>translate_OID( )</i>. Las dos primeras se relacionan con el proceso de inicializaciÃ³n que se explica en la SecciÃ³n <CrossRef target="Section" ref="initialisation"/>.</Text>
+<Text id="884">La otra,Â <i>translate_OID( )</i>, maneja la sintaxis para expresar los identificadores de documento. En la Figura <CrossRef target="Figure" ref="the_golf_course_mystery"/> vimos que el nÃºmero de una pÃ¡gina podÃ­a anexarse a un identificador de documento para recuperar Ãºnicamente esa pÃ¡gina. Esto era posible porque, al crearse la colecciÃ³n, las pÃ¡ginas se almacenaban como âseccionesâ. Si se agrega â.1â a un OID, se recupera la primera secciÃ³n del documento correspondiente. Las secciones pueden subdividirse y para acceder a ellas es preciso concatenar nÃºmeros de secciones separados por puntos.</Text>
+<Text id="885">AdemÃ¡s de los nÃºmeros jerÃ¡rquicos de secciones, la sintaxis del identificador de documento admite una forma de acceso relativo. En el caso de la secciÃ³n en uso de un documento, se puede acceder alÂ <i>primer hijo</i>Â anexandoÂ <i>.fc (first child)</i>, alÂ <i>Ãºltimo niÃ±o</i>Â anexandoÂ <i>.lc (last child)</i>, alÂ <i>padre</i>Â anexandoÂ <i>.pr (parent)</i>, alÂ <i>hermano</i><i>siguiente</i>Â anexandoÂ <i>.ns</i><i>(next sibling)</i>Â y alÂ <i>hermano anterior</i>Â anexandoÂ <i>.ps (previous sibling)</i>.</Text>
+<Text id="886">La funciÃ³nÂ <i>translate_OID</i>Â utiliza los parÃ¡metrosÂ <i>OIDin</i>Â yÂ <i>OIDout</i>Â para retener la fuente y el resultado de la conversiÃ³n. Incluye otros dos parÃ¡metros:Â <i>err</i>Â yÂ <i>logout</i>. Ãstos comunican cualquier estado de error que se pueda producir durante la operaciÃ³n de traducciÃ³n, y determina dÃ³nde enviar la informaciÃ³n de registro (Â <i>logging information</i>). Como veremos en la SecciÃ³n <CrossRef target="Section" ref="protocol"/>, estos parÃ¡metros dependen estrechamente del protocolo.</Text>
+<Part id="database_retrieval_with_gdbm">
+<Title>
+<Text id="887">RecuperaciÃ³n de base de datos con gdbm</Text>
+</Title>
+<Content>
+<Text id="888">GDBM es el programa de gestiÃ³n de base de datos de GNU (<i>www.gnu.org</i>). Establece una estructura de registros planos de pares clave/datos, y es compatible con versiones anteriores de DBM y NDBM. Las operaciones incluyen el almacenamiento, la recuperaciÃ³n y la supresiÃ³n de registros por clave, y un recorrido no ordenado de todas las claves.</Text>
+<Figure id="gdbm_database_for_the_gutenberg_collection">
+<Title>
+<Text id="889">La base de datos GDBM para la colecciÃ³n Gutenberg (extracto)</Text>
+</Title>
+<CodeLine>[HASH01d7b30d4827b51282919e9b]</CodeLine>
+<CodeLine>&lt;doctype&gt; doc</CodeLine>
+<CodeLine>&lt;hastxt&gt;Â Â Â Â Â Â Â Â Â Â  0</CodeLine>
+<CodeLine>&lt;Title&gt;Â Â Â Â Â Â Â Â Â Â Â  The Winterâs Tale</CodeLine>
+<CodeLine>&lt;Creator&gt; William Shakespeare</CodeLine>
+<CodeLine>&lt;archivedir&gt;Â Â Â Â Â Â  HASH01d7/b30d4827.dir</CodeLine>
+<CodeLine>&lt;thistype&gt; Â Â Â Â Â Â Â  Invisible</CodeLine>
+<CodeLine>&lt;childtype&gt; Â Â Â Â Â Â  Paged</CodeLine>
+<CodeLine>&lt;contains&gt; Â Â Â Â Â Â Â  ".1;".2;".3;".4;".5;".6;".7;".8;".9;".10;".11;".12; \</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ".13;".14;".15;".16;".17;".18;".19;".20;".21;".22; \</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ".23;".24;".25;".26;".27;".28;".29;".30;".31;".32; \</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ".33;".34;".35</CodeLine>
+<CodeLine>&lt;docnum&gt;Â Â Â Â Â Â Â Â Â Â  168483</CodeLine>
+<CodeLine>------------------------</CodeLine>
+<CodeLine>[CL1]</CodeLine>
+<CodeLine>&lt;doctype&gt; classify</CodeLine>
+<CodeLine>&lt;hastxt&gt;Â Â Â Â Â Â Â Â Â Â  0</CodeLine>
+<CodeLine>&lt;childtype&gt;Â Â Â Â Â Â Â  HList</CodeLine>
+<CodeLine>&lt;Title&gt;Â Â Â Â Â Â Â Â Â Â Â  Title</CodeLine>
+<CodeLine>&lt;numleafdocs&gt;Â Â Â Â Â  1818</CodeLine>
+<CodeLine>&lt;thistype&gt;Â Â Â Â Â Â Â Â  Invisible</CodeLine>
+<CodeLine>&lt;contains&gt;Â Â Â Â Â Â Â Â  ".1;".2;".3;".4;".5;".6;".7;".8;".9;".10;".11;".12; \</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ".13;".14;".15;".16;".17;".18;".19;".20;".21;".22; \</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ".23;".24</CodeLine>
+<CodeLine>------------------------</CodeLine>
+<CodeLine>[CL1.1]</CodeLine>
+<CodeLine>&lt;doctype&gt; classify</CodeLine>
+<CodeLine>&lt;hastxt&gt;Â Â Â Â Â Â Â Â Â Â  0</CodeLine>
+<CodeLine>&lt;childtype&gt;Â Â Â Â Â Â Â  VList</CodeLine>
+<CodeLine>&lt;Title&gt;Â Â Â Â Â Â Â Â Â Â Â  A</CodeLine>
+<CodeLine>&lt;numleafdocs&gt;Â Â Â Â Â  118</CodeLine>
+<CodeLine>&lt;contains&gt;Â Â Â Â Â Â Â Â  HASH0130bc5f9f90089b3723431f;HASH9cba43bacdab5263c98545;\</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â  Â Â Â Â Â Â Â Â Â HASH12c88a01da6e8379df86a7;HASH9c86579a83e1a2e4cf9736;Â  \</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  HASHdc2951a7ada1f36a6c3aca;HASHea4dda6bbc7cdeb4abfdee;Â  \</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  HASHce55006513c47235ac38ba;HASH012a33acaa077c0e612b9351;\</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  HASH010dd1e923a123826ae30e4b;HASHaf674616785679fed4b7ee;\</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  HASH0147eef4b9d1cb135e096619;HASHe69b9dbaa83ffb045d963b;\</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  HASH01abc61c646c8e7a8ce88b10;HASH5f9cd13678e21820e32f3a;\</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  HASHe8cbba1594c72c98f9aa1b;HASH01292a2b7b6b60dec96298bc;\</CodeLine>
+<CodeLine>...</CodeLine>
+</Figure>
+<Text id="890">En la Figura <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> se muestra un extracto de la base de datos de informaciones de la colecciÃ³n elaborada durante la creaciÃ³n de la colecciÃ³n Gutenberg. El extracto se obtuvo utilizando la aplicaciÃ³nÂ <i>db2txt</i>Â de Greenstone que convierte el formato binario de base de datos GDBM en forma textual. La Figura <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> contiene tres registros separados por lÃ­neas horizontales. El primero es una entrada de documento, los otros dos forman parte de la jerarquÃ­a creada por el clasificadorÂ <i>AZList</i>Â para los tÃ­tulos de la colecciÃ³n. La primera lÃ­nea de cada registro es su clave.</Text>
+<Text id="891">El registro del documento guarda el tÃ­tulo del libro, el autor y cualquier otro metadato proporcionado (o extraÃ­do) durante la creaciÃ³n de la colecciÃ³n. Contiene asimismo valores para uso interno: dÃ³nde se encuentran los archivos asociados con ese documento (&lt;Â <i>archivedir</i>Â &gt;) y el nÃºmero de documento utilizado internamente por MG (&lt;Â <i>docnum</i>Â &gt;).</Text>
+<Text id="892">En el campo &lt;Â <i>contains</i>Â &gt; se almacena una lista de elementos, separados por caracteres de punto y coma, que remiten a registros conexos en la base de datos. Para un registro de documento, el campo &lt;Â <i>contains</i>Â &gt; sirve para seÃ±alar las secciones subdivididas. Las subsiguientes claves de registro se forman concatenando la clave en curso con uno de los elementos secundarios (separado por un punto).</Text>
+<Text id="893">El segundo registro de la Figura <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> es el nodo principal de la jerarquÃ­a de clasificaciÃ³n de tÂ <i>Ã­tulos a-z</i>. Sus elementos secundarios, a los que se accede a travÃ©s del campo &lt;Â <i>contains</i>Â &gt;, incluyenÂ <i>CL1.1</i>,Â <i>CL1.2</i>,Â <i>CL1.3</i>Â y asÃ­ sucesivamente, y corresponden a las distintas pÃ¡ginas para las letrasÂ <i>A</i>,Â <i>B</i>,Â <i>C</i>, etc. Hay Ãºnicamente 24 elementos secundarios: el clasificadorÂ <i>AZList</i>Â fusionÃ³ las letrasÂ <i>Q-R</i>Â eÂ <i>Y-Z</i>Â porque sÃ³lo incluÃ­an unos cuantos tÃ­tulos.</Text>
+<Text id="894">Los elementos secundarios en el campo &lt;Â <i>contains</i>Â &gt; del tercer registro,Â <i>CL1.1</i>, son los documentos propiamente dichos. Es posible establecer estructuras mÃ¡s complicadas: el campo &lt;Â <i>contains</i>Â &gt; puede incluir una combinaciÃ³n de documentos y otros nodosÂ <i>CL</i>. Las claves relacionadas con la clave en curso se distinguen de las claves absolutas porque llevan comillas (â) antepuestas.</Text>
+</Content>
+</Part>
+<Part id="using_mg_and_gdbm_to_implement_a_source_object">
+<Title>
+<Text id="895">El uso de MG y GDBM para implementar un objeto Fuente (Source)</Text>
+</Title>
+<Content>
+<Figure id="api_for_mg_and_gdbm_based_version_of_sourceclass">
+<Title>
+<Text id="896">API de la versiÃ³n deÂ <i>sourceclass</i>Â basada en MG y GDBM (abreviada)</Text>
+</Title>
+<CodeLine>class mggdbmsourceclass : public sourceclass {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>Â  // Omitted, data fields that store:</CodeLine>
+<CodeLine>Â  // Â Â collection specific file information</CodeLine>
+<CodeLine>Â  // Â Â index substructure</CodeLine>
+<CodeLine>Â  // Â Â information about parent</CodeLine>
+<CodeLine>Â  // Â Â pointers to gdbm and mgsearch objects</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>Â  mggdbmsourceclass ();</CodeLine>
+<CodeLine>Â  virtual ~mggdbmsourceclass ();</CodeLine>
+<CodeLine>Â  void set_gdbmptr (gdbmclass *thegdbmptr);</CodeLine>
+<CodeLine>Â  void set_mgsearchptr (searchclass *themgsearchptr);</CodeLine>
+<CodeLine>Â  void configure (const text_t &amp;key, const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>Â  bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>Â  bool translate_OID (const text_t &amp;OIDin, text_t &amp;OIDout,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>Â  bool get_metadata (const text_t &amp;requestParams,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const text_t &amp;refParams,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  bool getParents, const text_tset &amp;fields,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const text_t &amp;OID, MetadataInfo_tmap &amp;metadata,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>Â  bool get_document (const text_t &amp;OID, text_t &amp;doc,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="897">El objeto que reÃºne MG y GDBM para efectuar una implementaciÃ³n deÂ <i>sourceclass</i>Â se denominaÂ <i>mggdbmsourceclass</i>. En la Figura <CrossRef target="Figure" ref="api_for_mg_and_gdbm_based_version_of_sourceclass"/> se presenta su API. Las dos nuevas funciones miembroÂ <i>set_gdbmptr( )</i>Â yÂ <i>set_mgsearchptr( )</i>Â almacenan punteros dirigidos hacia sus respectivos objetos, de modo que las implementaciones deÂ <i>get_metadata( )</i>Â yÂ <i>get_document( )</i>Â puedan acceder a las herramientas apropiadas para llevar a cabo su tarea.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="the_filter_object">
+<Title>
+<Text id="898">El objeto Filtro (<i>Filter</i>)</Text>
+</Title>
+<Content>
+<Figure id="api_for_the_filter_base_class">
+<Title>
+<Text id="899">API de la clase base de Filtro</Text>
+</Title>
+<CodeLine>class filterclass {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>Â  text_t gsdlhome;</CodeLine>
+<CodeLine>Â  text_t collection;</CodeLine>
+<CodeLine>Â  text_t collectdir;</CodeLine>
+<CodeLine>Â  FilterOption_tmap filterOptions;</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>Â  filterclass ();</CodeLine>
+<CodeLine>Â  virtual ~filterclass ();</CodeLine>
+<CodeLine>Â  virtual void configure (const text_t &amp;key,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>Â  virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>Â  // returns the name of this filter</CodeLine>
+<CodeLine>Â  virtual text_t get_filter_name ();</CodeLine>
+<CodeLine>Â  // returns the current filter options</CodeLine>
+<CodeLine>Â  virtual void get_filteroptions</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  (InfoFilterOptionsResponse_t &amp;response, </CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>Â  virtual void filter (const FilterRequest_t &amp;request,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  FilterResponse_t &amp;response,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="900">La API de la clase de base para el objeto Filtro de la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/> se presenta en la Figura <CrossRef target="Figure" ref="api_for_the_filter_base_class"/>. Empieza con los campos de datos protegidosÂ <i>gsdlhome</i>,Â <i>collection</i>Â yÂ <i>collectdir</i>. Estos suelen emplearse en las clases que necesitan acceder a archivos de colecciones especÃ­ficas:</Text>
+<BulletList>
+<Bullet>
+<Text id="901"><i>gsdlhome</i>Â es lo mismo queÂ <i>GSDLHOME</i>, de modo que el objeto pueda localizar los archivos de Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="902"><i>collection</i>Â es el nombre del directorio que corresponde a la colecciÃ³n</Text>
+</Bullet>
+<Bullet>
+<Text id="903"><i>collectdir</i>Â es el nombre de ruta completo del directorio de la colecciÃ³n (es necesario porque una colecciÃ³n no tiene por quÃ© encontrarse necesariamente en la zonaÂ <i>GSDLHOME</i>).</Text>
+</Bullet>
+</BulletList>
+<Text id="904"><i>mggdbsourceclass</i>Â es otra clase que incluye estos tres campos de datos.</Text>
+<Text id="905">El proceso de inicializaciÃ³n utiliza las funciones miembroÂ <i>configure( )</i>Â eÂ <i>init( )</i>Â (que ya vimos en la funciÃ³nÂ <i>sourceclass</i>). El propio objeto se alinea estrechamente con la porciÃ³n de filtro que le corresponde en el protocolo; las funcionesÂ <i>get_filteroptions( )</i>Â yÂ <i>filter( )</i>, en particular, coinciden exactamente.</Text>
+<Figure id="how_a_filter_option_is_stored">
+<Title>
+<Text id="906">Manera en que se almacena una opciÃ³n de filtro</Text>
+</Title>
+<CodeLine>struct FilterOption_t {</CodeLine>
+<CodeLine>Â  void clear (); \ void check_defaultValue ();</CodeLine>
+<CodeLine>Â  FilterOption_t () {clear();}</CodeLine>
+<CodeLine>Â  text_t name;</CodeLine>
+<CodeLine>Â  enum type_t {booleant=0, integert=1, enumeratedt=2, stringt=3};</CodeLine>
+<CodeLine>Â  type_t type;</CodeLine>
+<CodeLine>Â  enum repeatable_t {onePerQuery=0, onePerTerm=1, nPerTerm=2};</CodeLine>
+<CodeLine>Â  repeatable_t repeatable;</CodeLine>
+<CodeLine>Â  text_t defaultValue; </CodeLine>
+<CodeLine>Â  text_tarray validValues;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>struct OptionValue_t {</CodeLine>
+<CodeLine>Â  void clear ();</CodeLine>
+<CodeLine>Â  text_t name;</CodeLine>
+<CodeLine>Â  text_t value;</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="907">Las dos clases que se muestran en la Figura <CrossRef target="Figure" ref="how_a_filter_option_is_stored"/> son fundamentales para las opciones de filtro.Â <i>FilterOption_t</i>Â almacena elÂ <i>nombre (name)</i>Â de la opciÃ³n, suÂ <i>tipo (type)</i>, y si se puede repetir o no (Â <i>repeatable)</i>. La interpretaciÃ³n deÂ <i>validValues</i>Â depende del tipo de opciÃ³n. Para un tipo booleano, el primer valor esÂ <i>false</i>Â y el segundoÂ <i>true</i>. Para un tipo entero, el primer valor es el nÃºmero mÃ­nimo y el segundo el mÃ¡ximo. Para un tipo enumerado todos los valores estÃ¡n en la lista. Para un tipo de cadena se ignora el valor. Para las situaciones mÃ¡s simples, se empleaÂ <i>OptionValue_t</i>Â que registra elÂ <i>nombre</i>Â de la opciÃ³n y suÂ <i>valor</i>Â comoÂ <i>text_t</i>.</Text>
+<Text id="908">Los objetos de bÃºsqueda y de respuesta transmitidos como parÃ¡metros aÂ <i>filterclass</i>Â se crean a partir de estas dos clases, utilizando matrices asociativas para almacenar un conjunto de opciones como las que se requieren paraÂ <i>InfoFilterOptionsResponse_t</i>. Para obtener mÃ¡s detalles vÃ©aseÂ <i>GSDLHOME/src/recpt/comtypes.h</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="inherited_filter_objects">
+<Title>
+<Text id="909">Objetos Filtro heredados (<i>Inherited Filter</i>)</Text>
+</Title>
+<Content>
+<Figure id="inheritance_hierarchy_for_filter">
+<Title>
+<Text id="910">JerarquÃ­a de herencia para el objeto de filtro</Text>
+</Title>
+<File width="342" height="332" url="images/Dev_Fig_38.png"/>
+</Figure>
+<Text id="911">Tal como se muestra en la Figura <CrossRef target="Figure" ref="inheritance_hierarchy_for_filter"/>, los filtros utilizan dos niveles de herencia. En primer lugar, se establece una distinciÃ³n entre filtros de bÃºsqueda y consulta, y luego para los primeros se procede a una implementaciÃ³n especÃ­fica basada en MG. Para que funcione correctamente,Â <i>mgqueryfilterclass</i>Â necesita acceder a MG a travÃ©s deÂ <i>mgsearchclass</i>Â y a GDBM a travÃ©s deÂ <i>gdbmclass</i>.Â <i>browsefilterclass</i>Â sÃ³lo necesita tener acceso a GDBM. Los punteros de estos objetos se guardan como campos de datos protegidos dentro de las respectivas clases.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_collection_server_code">
+<Title>
+<Text id="912">El cÃ³digo del servidor de colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="913">A continuaciÃ³n presentamos los archivos de encabezado del directorioÂ <i>GSDLHOME/src/colservr</i>. El nombre del archivo coincide por lo general con el nombre del objeto que define. </Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="120">
+<Text id="914"><b>browsefilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="915">Heredado deÂ <i>filterclass</i>, este objeto proporciona acceso a GDBM (se explica mÃ¡s arriba).</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="916"><b>collectserver.h</b></Text>
+</th>
+<th width="420">
+<Text id="917">Este objeto enlaza los objetos Filtro y de Fuente de una colecciÃ³n a fin de formar el objeto ColecciÃ³n representado en la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="918"><b>colservrconfig.h</b></Text>
+</th>
+<th width="420">
+<Text id="919">FunciÃ³n de apoyo para la lectura de los archivos especÃ­ficos de una colecciÃ³nÂ <i>etc/collect.cfg</i>Â eÂ <i>index/build.cfg</i>. El primero es el archivo de configuraciÃ³n de la colecciÃ³n y el segundo es un archivo generado por el proceso de creaciÃ³n que registra la hora de la Ãºltima creaciÃ³n llevada satisfactoriamente a cabo, una lista de las correspondencias de Ã­ndice, el nÃºmero de documentos indizados y su tamaÃ±o en bytes (sin comprimir).</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="920"><b>filter.h</b></Text>
+</th>
+<th width="420">
+<Text id="921">La clase de base del objeto de filtroÂ <i>filterclass</i>Â antes mencionado.</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="922"><b>maptools.h</b></Text>
+</th>
+<th width="420">
+<Text id="923">Define una clase llamadaÂ <i>stringmap</i>Â que proporciona una correspondencia que recuerda el orden original de una correspondenciaÂ <i>text_t</i>, pero cuya consulta es rÃ¡pida. Se utiliza enÂ <i>mggdbmsourceclass</i>Â yÂ <i>queryfilterclass</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="924"><b>mggdbmsource.h</b></Text>
+</th>
+<th width="420">
+<Text id="925">Heredado deÂ <i>sourceclass</i>, este objeto proporciona acceso a MG y GDBM (se explica mÃ¡s arriba).</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="926"><b>mgppqueryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="927">Heredado deÂ <i>queryfilterclass</i>, este objeto proporciona una implementaciÃ³n deÂ <i>QueryFilter</i>Â basada en MG++, una versiÃ³n mejorada de MG escrita en C++. ObsÃ©rvese que Greenstone estÃ¡ configurado para utilizar MG por defecto, ya que MG++ se encuentra todavÃ­a en fase de desarollo.</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="928"><b>mgppsearch.h</b></Text>
+</th>
+<th width="420">
+<Text id="929">Heredado deÂ <i>searchclass</i>, este objeto proporciona une implementaciÃ³n del objeto BÃºsqueda utilizando MG++. ComoÂ <i>mgppqueryfilterclass</i>, tampoco se utiliza por defecto.</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="930"><b>mgq.h</b></Text>
+</th>
+<th width="420">
+<Text id="931">Interfaz funcional para el paquete MG. Sus principales funciones sonÂ <i>mg_ask( )</i>Â yÂ <i>mg_results( )</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="932"><b>mgqueryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="933">Heredado deÂ <i>queryfilterclass</i>, este objeto proporciona una implementaciÃ³n deÂ <i>QueryFilter</i>Â basada en MG.</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="934"><b>mgsearch.h</b></Text>
+</th>
+<th width="420">
+<Text id="935">Heredado deÂ <i>searchclass</i>, este objeto proporciona una implementaciÃ³n de SearchÂ <i/>Â (bÃºsqueda) utilizando MG (se explica mÃ¡s arriba).</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="936"><b>phrasequeryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="937">Heredado deÂ <i>mgqueryclass</i>, este objeto proporciona una clase de consulta basada en frases. No se utiliza en la instalaciÃ³n por defecto. En su lugarÂ <i>mgqueryfilterclass</i>Â ofrece esta posibilidad a travÃ©s del apoyo funcional deÂ <i>phrasesearch.h</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="938"><b>phrasesearch.h</b></Text>
+</th>
+<th width="420">
+<Text id="939">FunciÃ³n de apoyo para efectuar una bÃºsqueda de grupos de palabras como operaciÃ³n posterior al tratamiento.</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="940"><b>querycache.h</b></Text>
+</th>
+<th width="420">
+<Text id="941">Utilizado porÂ <i>searchclass</i>Â y sus clases heredadas para almacenar en el campo cachÃ© los resultados de una consulta, a fin de que la generaciÃ³n de las pÃ¡ginas resultantes de bÃºsquedas posteriores resulte mÃ¡s eficaz (se explica mÃ¡s arriba).</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="942"><b>queryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="943">Heredado de la clase base de filtroÂ <i>filterclass</i>, este objeto establece una clase base para los objetos Filtro y BÃºsqueda (se explica mÃ¡s arriba).</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="944"><b>queryinfo.h</b></Text>
+</th>
+<th width="420">
+<Text id="945">Ayuda para la bÃºsqueda: estructuras de datos y objetos para guardar los parÃ¡metros de consulta, los resultados de documentos y las frecuencias de tÃ©rminos.</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="946"><b>search.h</b></Text>
+</th>
+<th width="420">
+<Text id="947">La clase de base del objeto BÃºsquedaÂ <i>searchclass</i>Â (se explica mÃ¡s arriba).</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="948"><b>source.h</b></Text>
+</th>
+<th width="420">
+<Text id="949">La clase de base del objeto FuenteÂ <i>sourceclass</i>Â (se explica mÃ¡s arriba).</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="protocol">
+<Title>
+<Text id="950">Protocolo</Text>
+</Title>
+<Content>
+<Table id="list_of_protocol_calls">
+<Title>
+<Text id="951">Lista de llamadas del protocolo</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="952"><i>get_protocol_name( )</i></Text>
+</th>
+<th width="397">
+<Text id="953">Devuelve el nombre de este protocolo. Las opciones incluyenÂ <i>nullproto</i>,Â <i>corbaproto</i>Â yÂ <i>z3950proto</i>. Utilizado por las partes del sistema de ejecuciÃ³n que dependen del protocolo para decidir quÃ© cÃ³digo ejecutar.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="954"><i>get_collection_list( )</i></Text>
+</th>
+<th width="397">
+<Text id="955">Devuelve la lista de colecciones que este protocolo conoce.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="956"><i>has_collection( )</i></Text>
+</th>
+<th width="397">
+<Text id="957">Devuelve el valorÂ <i>true</i>Â (Â <i>verdadero)</i>Â si el protocolo puede comunicar con la colecciÃ³n nombrada, es decir, si se encuentra en su lista de colecciones.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="958"><i>ping( )</i></Text>
+</th>
+<th width="397">
+<Text id="959">ReenvÃ­a el valorÂ <i>true (verdadero)</i>Â si se ha logrado establecer una conexiÃ³n con la colecciÃ³n nombrada. En el caso del protocolo nulo, la implementaciÃ³n es idÃ©ntica a la deÂ <i>has_collection( )</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="960"><i>get_collectinfo( )</i></Text>
+</th>
+<th width="397">
+<Text id="961">Obtiene informaciÃ³n general sobre la colecciÃ³n nombrada: fecha de la Ãºltima creaciÃ³n, nÃºmero de documentos que contiene, etc. Incluye tambiÃ©n metadatos del archivo de configuraciÃ³n de la colecciÃ³n: texto de âAcerca de esta colecciÃ³nâ, el icono de la colecciÃ³n que ha de utilizarse, etc.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="962"><i>get_filterinfo( )</i></Text>
+</th>
+<th width="397">
+<Text id="963">Obtiene una lista de todos los objetos Filtro para la colecciÃ³n nombrada.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="964"><i>get_filteroptions( )</i></Text>
+</th>
+<th width="397">
+<Text id="965">Obtiene todas las opciones para un objeto Filtro particular en la colecciÃ³n nombrada.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="966"><i>filter( )</i></Text>
+</th>
+<th width="397">
+<Text id="967">Permite la bÃºsqueda y la consulta. Para un tipo de filtro determinado y unas configuraciones de opciones, accede al contenido de las colecciones nombradas para producir un conjunto de resultados que es filtrado segÃºn las configuraciones de opciones. Los campos de datos devueltos dependen tambiÃ©n de las configuraciones de opciones, por ejemplo: la frecuencia de los tÃ©rminos de consulta y los metadatos de documento.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="968"><i>get_document( )</i></Text>
+</th>
+<th width="397">
+<Text id="969">Obtiene un documento o secciÃ³n de un documento.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="970">En el Cuadro <CrossRef target="Table" ref="list_of_protocol_calls"/> se presenta una lista de las llamadas de funciÃ³n al protocolo, y un resumen de cada una de ellas. Los ejemplos de la SecciÃ³n <CrossRef target="Section" ref="how_the_conceptual_framework_fits_together"/> ilustran la mayorÃ­a de esas llamadas. Las funciones no mencionadas anteriormente sonÂ <i>has_collection( )</i>,Â <i>ping( )</i>,Â <i>get_protocol_name( )</i>Â yÂ <i>get_filteroptions( )</i>. Las dos primeras responden afirmativa o negativamente a las preguntas âÂ¿existe la colecciÃ³n en este servidor?â y âÂ¿se encuentra en funcionamiento?â, respectivamente. La finalidad de las otras dos es admitir protocolos mÃºltiples en una arquitectura repartida en diferentes computadoras, y no sÃ³lo el ejecutable individual basado en el protocolo nulo que se menciona aquÃ­. Una de ellas detecta quÃ© protocolo se encuentra en uso. La otra permite que un recepcionista consulte al servidor de una colecciÃ³n para averiguar quÃ© opciones admite, a fin de configurarse dinÃ¡micamente y sacar el mÃ¡ximo provecho de los servicios ofrecidos por un servidor particular.</Text>
+<Figure id="null_protocol_api">
+<Title>
+<Text id="971">API del protocolo nulo (abreviado)</Text>
+</Title>
+<CodeLine>class nullproto : public recptproto {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>Â  virtual text_t get_protocol_name ();</CodeLine>
+<CodeLine>Â  virtual void get_collection_list (text_tarray &amp;collist,</CodeLine>
+<CodeLine>Â Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>Â  virtual void has_collection (const text_t &amp;collection,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  bool &amp;hascollection,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>Â  virtual void ping (const text_t &amp;collection,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  bool &amp;wassuccess,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>Â  virtual void get_collectinfo (const text_t &amp;collection,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ColInfoResponse_t &amp;collectinfo, </CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>virtual void get_filterinfo (const text_t &amp;collection,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  InfoFiltersResponse_t &amp;response,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>virtual void get_filteroptions (const text_t &amp;collection,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const InfoFilterOptionsRequest_t &amp;request,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  InfoFilterOptionsResponse_t &amp;response,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>Â  virtual void filter (const text_t &amp;collection,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â  Â Â Â Â Â Â Â Â Â Â FilterRequest_t &amp;request,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  FilterResponse_t &amp;response,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>Â Â virtual void get_document (const text_t &amp;collection,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const DocumentRequest_t &amp;request,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  DocumentResponse_t &amp;response,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="972">En la Figura <CrossRef target="Figure" ref="null_protocol_api"/> se muestra la API para el protocolo nulo. Se han omitido los comentarios y determinados detalles de nivel inferior (vÃ©ase el archivo fuenteÂ <i>recpt/nullproto.h</i>Â para obtener mÃ¡s informaciÃ³n al respecto).</Text>
+<Text id="973">Este protocolo hereda de la clase de baseÂ <i>recptproto</i>. Se utiliza la herencia virtual a fin de poder admitir fÃ¡cilmente mÃ¡s de un tipo de protocolo âincluso protocolos aÃºn no concebidosâ en el resto del cÃ³digo fuente. Ello es posible porque el objeto de clase de baseÂ <i>recptproto</i>Â se utiliza a lo largo de todo el cÃ³digo fuente, excepto en el punto de creaciÃ³n, donde especificamos la variedad concreta de protocolo que deseamos utilizar que, en este caso, es el protocolo nulo.</Text>
+<Text id="974">Con la excepciÃ³n deÂ <i>get_protocol_name( )</i>, que no toma parÃ¡metros y devuelve el nombre del protocolo como una cadena de texto codificada en Unicode, todas las funciones de protocolo incluyen un parÃ¡metro de error y un flujo de salida como argumentos finales. El parÃ¡metro de error registra cualquier error que se produce durante la ejecuciÃ³n de la llamada de protocolo y la secuencia de salida se utiliza a efectos de registro (Â <i>logging</i>). Las funciones son del tipoÂ <i>void</i>, esto es, no reenvÃ­an explÃ­citamente la informaciÃ³n en su instrucciÃ³n final, sino que reenvÃ­an datos a travÃ©s de parÃ¡metros designados como el parÃ¡metro de error antes mencionado. En algunos lenguajes de programaciÃ³n, estos subprogramas se definirÃ­an como âprocedimientosâ en vez de âfuncionesâ, pero C++ no establece ninguna distinciÃ³n sintÃ¡ctica.</Text>
+<Text id="975">La mayorÃ­a de las funciones toman el nombre de la colecciÃ³n como argumento. Tres de las funciones miembro,Â <i>get_filteroptions( )</i>,Â <i>filter( )</i>Â yÂ <i>get_document( )</i>Â siguen el esquema de proporcionar un parÃ¡metro de consulta y de recibir los resultados en un parÃ¡metro de respuesta Response.</Text>
+</Content>
+</Section>
+<Section id="receptionist">
+<Title>
+<Text id="976">El recepcionista</Text>
+</Title>
+<Content>
+<Text id="977">La capa final del modelo conceptual es el recepcionista. Una vez analizados los argumentos CGI, la actividad principal es la ejecuciÃ³n de una acciÃ³n con la asistencia de los objetos Formato y Lenguaje de macros, que se explican mÃ¡s adelante. Aunque se representen como objetos en el marco conceptual, los objetos Formato y Lenguaje de macros no son estrictamente objetos en el sentido de C++. En realidad, el objeto de formato es una colecciÃ³n de estructuras de datos con un conjunto de funciones que operan en aquÃ©llas, y el objeto de lenguaje de macros se crea en torno aÂ <i>displayclass</i>, definido enÂ <i>lib/display.h</i>Â con un apoyo de conversiÃ³n de flujo procedente deÂ <i>lib/gsdlunicode.h</i>.</Text>
+<Subsection id="actions">
+<Title>
+<Text id="978">Acciones</Text>
+</Title>
+<Content>
+<Table id="actions_in_greenstone">
+<Title>
+<Text id="979">Las acciones en Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="980"><i>action</i></Text>
+</th>
+<th width="397">
+<Text id="981">Clase base para la herencia virtual.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="982"><i>authenaction</i></Text>
+</th>
+<th width="397">
+<Text id="983">Presta ayuda a la autenticaciÃ³n del usuario: pide al usuario una contraseÃ±a si no se ha introducido ninguna, comprueba su validez y obliga al usuario a introducir la contraseÃ±a de nuevo si transcurre demasiado tiempo entre dos accesos.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="984"><i>collectoraction</i></Text>
+</th>
+<th width="397">
+<Text id="985">Genera las pÃ¡ginas para el Colector.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="986"><i>documentaction</i></Text>
+</th>
+<th width="397">
+<Text id="987">Recupera documentos, secciones de documentos, porciones de la jerarquÃ­a de clasificaciÃ³n o informaciÃ³n sobre formatos.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="988"><i>extlinkaction</i></Text>
+</th>
+<th width="397">
+<Text id="989">Lleva un usuario directamente a una direcciÃ³n URL que es externa a la colecciÃ³n, generando eventualmente antes una pÃ¡gina de alerta (segÃºn lasÂ <i>preferencias</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="990"><i>pageaction</i></Text>
+</th>
+<th width="397">
+<Text id="991">Genera una pÃ¡gina en conjunciÃ³n con el lenguaje de macros.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="992"><i>pingaction</i></Text>
+</th>
+<th width="397">
+<Text id="993">Comprueba si una colecciÃ³n estÃ¡ en lÃ­nea.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="994"><i>queryaction</i></Text>
+</th>
+<th width="397">
+<Text id="995">EfectÃºa una bÃºsqueda.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="996"><i>statusaction</i></Text>
+</th>
+<th width="397">
+<Text id="997">Genera las pÃ¡ginas de administraciÃ³n.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="998"><i>tipaction</i></Text>
+</th>
+<th width="397">
+<Text id="999">Facilita de forma aleatoria una sugerencia al usuario.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1000"><i>usersaction</i></Text>
+</th>
+<th width="397">
+<Text id="1001">Administra la adiciÃ³n, la supresiÃ³n y la gestiÃ³n de los accesos de usuario.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="1002">Greenstone admite las once acciones que se resumen en el Cuadro <CrossRef target="Table" ref="actions_in_greenstone"/>.</Text>
+<Figure id="using_the_cgiargsinfoclass_from_pageactioncpp" class="withLineNumber">
+<Title>
+<Text id="1003">UtilizaciÃ³n deÂ <i>cgiargsinfoclass</i>Â desdeÂ <i>pageaction.cpp</i></Text>
+</Title>
+<CodeLine>cgiarginfo arg_ainfo;</CodeLine>
+<CodeLine>arg_ainfo.shortname = "a";</CodeLine>
+<CodeLine>arg_ainfo.longname = "action";</CodeLine>
+<CodeLine>arg_ainfo.multiplechar = true;</CodeLine>
+<CodeLine>arg_ainfo.argdefault = "p";</CodeLine>
+<CodeLine>arg_ainfo.defaultstatus = cgiarginfo::weak;</CodeLine>
+<CodeLine>arg_ainfo.savedarginfo = cgiarginfo::must;</CodeLine>
+<CodeLine>argsinfo.addarginfo (NULL, arg_ainfo);</CodeLine>
+<CodeLine/>
+<CodeLine>arg_ainfo.shortname = "p";</CodeLine>
+<CodeLine>arg_ainfo.longname = "page";</CodeLine>
+<CodeLine>arg_ainfo.multiplechar = true;</CodeLine>
+<CodeLine>arg_ainfo.argdefault = "home";</CodeLine>
+<CodeLine>arg_ainfo.defaultstatus = cgiarginfo::weak;</CodeLine>
+<CodeLine>arg_ainfo.savedarginfo = cgiarginfo::must;</CodeLine>
+<CodeLine>argsinfo.addarginfo (NULL, arg_ainfo);</CodeLine>
+</Figure>
+<Text id="1004">Los argumentos CGI necesarios para una acciÃ³n se declaran formalmente en la funciÃ³n constructora utilizandoÂ <i>cgiarginfo</i>Â (definida enÂ <i>recpt/cgiargs.h</i>). En la Figura <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/> se muestra un extracto de la funciÃ³n constructoraÂ <i>pageaction</i>, que define el tamaÃ±o y las propiedades de los argumentos CGIÂ <i>a</i>Â yÂ <i>p</i>.</Text>
+<Text id="1005">Para cada argumento CGI, el constructor debe especificar su nombre corto (lÃ­neas 2 y 10), que es el nombre de la variable CGI propiamente dicha; un nombre largo (lÃ­neas 3 y 11) que se utiliza para proporcionar una descripciÃ³n mÃ¡s elocuente de la acciÃ³n; si representa un valor de carÃ¡cter simple o mÃºltiple (lÃ­neas 4 y 12); un posible valor por defecto (lÃ­neas 5 y 13); lo que ocurre cuando se proporcionan varios valores por defecto (lÃ­neas 6 y 14) (ya que pueden introducirse valores por defecto en los archivos de configuraciÃ³n); y si es preciso preservar o no el valor al final de esta acciÃ³n (lÃ­neas 7 y 15).</Text>
+<Text id="1006">Puesto que estÃ¡ integrada en el cÃ³digo, se pueden generar automÃ¡ticamente pÃ¡ginas Web que detallan esta informaciÃ³n. La acciÃ³nÂ <i>statusaction</i>Â produce esta informaciÃ³n, que puede visualizarse introduciendo la direcciÃ³n URL de la pÃ¡gina de administraciÃ³n de Greenstone.</Text>
+<Text id="1007">Las doce acciones heredadas se construyen enÂ <i>main( )</i>, la funciÃ³n de alto nivel del ejecutableÂ <i>library</i>, cuya definiciÃ³n figura en el archivoÂ <i>recpt/librarymain.cpp</i>. Es aquÃ­ tambiÃ©n donde se forma el objeto Recepcionista (definido enÂ <i>recpt/receptionist.cpp</i>). La responsabilidad de todas las acciones recae en el objeto de recepcionista, que las trata manteniendo, como un campo de datos, una matriz asociativa de la clase base AcciÃ³n, indizada por nombres de acciÃ³n.</Text>
+<Figure id="action_base_class_api">
+<Title>
+<Text id="1008">API de la clase base AcciÃ³n</Text>
+</Title>
+<CodeLine>class action {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>Â  cgiargsinfoclass argsinfo;</CodeLine>
+<CodeLine>Â  text_t gsdlhome;</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>Â  action ();</CodeLine>
+<CodeLine>Â  virtual ~action ();</CodeLine>
+<CodeLine>Â  virtual void configure (const text_t &amp;key,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>Â  virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>Â  virtual text_t get_action_name ();</CodeLine>
+<CodeLine>Â  cgiargsinfoclass getargsinfo ();</CodeLine>
+<CodeLine>Â  virtual bool check_cgiargs (cgiargsinfoclass &amp;argsinfo,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  cgiargsclass &amp;args,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ostream &amp;logout);</CodeLine>
+<CodeLine>virtual bool check_external_cgiargs (cgiargsinfoclass &amp;argsinfo,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  cgiargsclass &amp;args,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  outconvertclass &amp;outconvert,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const text_t &amp;saveconf,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ostream &amp;logout); </CodeLine>
+<CodeLine>virtual void get_cgihead_info (cgiargsclass &amp;args,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  recptprotolistclass *protos,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  response_t &amp;response,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  text_t &amp;response_data,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ostream &amp;logout);</CodeLine>
+<CodeLine>virtual bool uses_display (cgiargsclass &amp;args);</CodeLine>
+<CodeLine>virtual void define_internal_macros (displayclass &amp;disp,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  cgiargsclass &amp;args,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  recptprotolistclass *protos,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ostream &amp;logout);</CodeLine>
+<CodeLine>virtual void define_external_macros (displayclass &amp;disp,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  cgiargsclass &amp;args,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  recptprotolistclass *protos,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ostream &amp;logout);</CodeLine>
+<CodeLine>virtual bool do_action (cgiargsclass &amp;args,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  recptprotolistclass *protos,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  browsermapclass *browsers,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  displayclass &amp;disp,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  outconvertclass &amp;outconvert,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ostream &amp;textout,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1009">En la Figura <CrossRef target="Figure" ref="action_base_class_api"/> se muestra la API de la clase base AcciÃ³n. Cuando se ejecuta una acciÃ³n, el objeto Recepcionista activa diversas funciones, empezando porÂ <i>check_cgiarsgs( )</i>. La mayorÃ­a de estas funciones contribuyen a verificar, configurar y definir valores y macros, mientras queÂ <i>do_action( )</i>Â genera efectivamente la pÃ¡gina resultante. Si un objeto heredado particular no dispone de una definiciÃ³n para una funciÃ³n miembro determinada, pasa a la definiciÃ³n de la clase base que implementa un comportamiento por defecto apropiado.</Text>
+<Text id="1010">La explicaciÃ³n de las funciones miembro es la siguiente:</Text>
+<BulletList>
+<Bullet>
+<Text id="1011"><i>get_action_name( )</i>Â devuelve el valor del argumento CGIÂ <i>a</i>Â que especifica esta acciÃ³n. El nombre deberÃ­a ser corto pero puede incluir mÃ¡s de un carÃ¡cter.</Text>
+</Bullet>
+<Bullet>
+<Text id="1012"><i>check_cgiargs( )</i>Â es llamada antes queÂ <i>get_cgihead_info( )</i>,Â <i>define_external_macros( )</i>Â yÂ <i>do_action( )</i>. En caso de error aparece un mensaje escrito enÂ <i>logout</i>Â ; si el error es importante, la funciÃ³n devuelve el valorÂ <i>false</i>Â (falso) y no genera ningÃºn contenido de pÃ¡gina.</Text>
+</Bullet>
+<Bullet>
+<Text id="1013"><i>check_external_cgiargs( )</i>Â se activa despuÃ©s deÂ <i>check_cgiargs( )</i>Â para todas las acciones. Su uso se limita a invalidar otros comportamientos por defecto, como por ejemplo, mostrar una pÃ¡gina de conexiÃ³n cuando la pÃ¡gina solicitada requiere una autenticaciÃ³n.</Text>
+</Bullet>
+<Bullet>
+<Text id="1014"><i>get_cgihead_info( )</i>Â establece la informaciÃ³n del encabezado CGI. SiÂ <i>response</i>Â tiene el valor deÂ <i>location</i>, entoncesÂ <i>response_data</i>Â contiene la direcciÃ³n de redirecciÃ³n. SiÂ <i>response</i>Â equivale aÂ <i>content</i>, entoncesÂ <i>response_data</i>Â contiene el tipo de contenido.</Text>
+</Bullet>
+<Bullet>
+<Text id="1015"><i>uses_display( )</i>Â devuelveÂ <i>true</i>Â (Â <i>verdadero)</i>Â si se necesitaÂ <i>displayclass</i>Â para mostrar el contenido de la pÃ¡gina (comportamiento por defecto).</Text>
+</Bullet>
+<Bullet>
+<Text id="1016"><i>define_internal_macros( )</i>Â define todas las macros relacionadas con las pÃ¡ginas generadas por esta acciÃ³n.</Text>
+</Bullet>
+<Bullet>
+<Text id="1017"><i>define_external_macros( )</i>Â define todas las macros que podrÃ­an ser utilizadas por otras acciones para producir pÃ¡ginas.</Text>
+</Bullet>
+<Bullet>
+<Text id="1018"><i>do_action( )</i>Â genera la pÃ¡gina resultante, normalmente en un flujo a travÃ©s del objeto Lenguaje de macrosÂ <i>display</i>Â y el objeto de conversiÃ³n de salidaÂ <i>textout</i>. ReenvÃ­a el valorÂ <i>false</i>Â si un error ha impedido que la acciÃ³n produzca un resultado.</Text>
+</Bullet>
+</BulletList>
+<Text id="1019">Situado en el principio de la definiciÃ³n de clase,Â <i>argsinfo</i>Â es el campo de datos protegidos (utilizado en el extracto de cÃ³digo que se muestra en la Figura <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/>) que almacena la informaciÃ³n de argumento CGI especificada en una funciÃ³n constructora de acciÃ³n heredada. El otro campo de datos,Â <i>gsdlhome</i>, registraÂ <i>GSDLHOME</i>Â para facilitar el acceso<FootnoteRef id="3"/>. El objeto incluye asimismo las funcionesÂ <i>configure( )</i>Â eÂ <i>init( )</i>Â a efectos de inicializaciÃ³n.</Text>
+</Content>
+</Subsection>
+<Subsection id="formatting">
+<Title>
+<Text id="1020">Formateo</Text>
+</Title>
+<Content>
+<Figure id="core_data_structures_in_format">
+<Title>
+<Text id="1021">Estructuras de datos centrales de la clase Formato</Text>
+</Title>
+<CodeLine>enum command_t {comIf, comOr, comMeta, comText, comLink, comEndLink,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comNum, comIcon, comDoc,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  comHighlight, comEndHighlight};</CodeLine>
+<CodeLine>enum pcommand_t {pNone, pImmediate, pTop, pAll};</CodeLine>
+<CodeLine>enum dcommand_t {dMeta, dText};</CodeLine>
+<CodeLine>enum mcommand_t {mNone, mCgiSafe};</CodeLine>
+<CodeLine>struct metadata_t {</CodeLine>
+<CodeLine>Â  void clear();</CodeLine>
+<CodeLine>Â  metadata_t () {clear();}</CodeLine>
+<CodeLine>Â  text_t metaname;</CodeLine>
+<CodeLine>Â  mcommand_t metacommand;</CodeLine>
+<CodeLine>Â  pcommand_t parentcommand;</CodeLine>
+<CodeLine>Â  text_t parentoptions;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>// The decision component of an {If}{decision,true-text,false-text}</CodeLine>
+<CodeLine>// formatstring. The decision can be based on metadata or on text;</CodeLine>
+<CodeLine>// normally that text would be a macro like</CodeLine>
+<CodeLine>// _cgiargmode_.</CodeLine>
+<CodeLine>struct decision_t {</CodeLine>
+<CodeLine>Â  void clear();</CodeLine>
+<CodeLine>Â  decision_t () {clear();}</CodeLine>
+<CodeLine>Â  dcommand_t command;</CodeLine>
+<CodeLine>Â  metadata_t meta;</CodeLine>
+<CodeLine>Â  text_t text;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>struct format_t {</CodeLine>
+<CodeLine>Â  void clear();</CodeLine>
+<CodeLine>Â  format_t () {clear();}</CodeLine>
+<CodeLine>Â  command_t command;</CodeLine>
+<CodeLine>Â  decision_t decision;</CodeLine>
+<CodeLine>Â  text_t text;</CodeLine>
+<CodeLine>Â  metadata_t meta;</CodeLine>
+<CodeLine>Â  format_t *nextptr;</CodeLine>
+<CodeLine>Â  format_t *ifptr;</CodeLine>
+<CodeLine>Â  format_t *elseptr;</CodeLine>
+<CodeLine>Â  format_t *orptr;</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1022">Aunque en la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/> el formateo se representa como una entidad Ãºnica, en realidad estÃ¡ constituida por un conjunto de estructuras de datos y funciones, que se encuentran en el archivo de encabezadoÂ <i>recpt/formattools.h</i>. Las estructuras de datos centrales aparecen en la Figura <CrossRef target="Figure" ref="core_data_structures_in_format"/>.</Text>
+<Figure id="data_structures_built_for_sample_format_statement">
+<Title>
+<Text id="1023">Estructuras de datos creadas para el ejemplo de instrucciÃ³n de formato</Text>
+</Title>
+<File width="605" height="187" url="images/Dev_Fig_43.png"/>
+</Figure>
+<Text id="1024">Es mÃ¡s fÃ¡cil explicar la implementaciÃ³n con un ejemplo. Cuando la instrucciÃ³n de formato:</Text>
+<CodeLine>Â Â Â Â Â Â  Format CL1Vlist</CodeLine>
+<Text id="1025" type="code">â[link][Title]{If}{[Creator], por [Creator]}[/link]}â</Text>
+<Text id="1026">es leÃ­da desde un archivo de configuraciÃ³n de colecciÃ³n, las funciones deÂ <i>formattools.cpp</i>Â la analizan y se forma la estructura de datos interconectados que se muestra en la Figura <CrossRef target="Figure" ref="data_structures_built_for_sample_format_statement"/>. Cuando es necesario que una acciÃ³n evalÃºe la instrucciÃ³n de formato, se recorre la estructura de datos. La ruta que se toma a nivel de los nodosÂ <i>comIf</i>Â yÂ <i>comOr</i>Â depende de los metadatos devueltos por una llamada al protocolo.</Text>
+<Text id="1027">Al recuperar los metadatos, puede ocurrir que el resultado contenga otras macros y sintaxis de formato. Esto se resuelve avanzando y retrocediendo entre el anÃ¡lisis y la evaluaciÃ³n, segÃºn convenga.</Text>
+</Content>
+</Subsection>
+<Subsection id="macro_language">
+<Title>
+<Text id="1028">El lenguaje de macros</Text>
+</Title>
+<Content>
+<Text id="1029">La entidad de Lenguaje de macros de la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/>, al igual que la de Formato, no corresponde a una Ãºnica clase C++. En este caso existe una clase principal, pero la implementaciÃ³n del lenguaje de macros depende tambiÃ©n de funciones y clases de apoyo.</Text>
+<Text id="1030">La mejor manera de explicarlo es, una vez mÃ¡s, mediante un ejemplo. En primer lugar presentaremos unos ejemplos de definiciones de macros que ilustran las prioridades de las macros, luego, mediante un diagrama, describiremos las estructuras de datos principales creadas para apoyar esta actividad. Por Ãºltimo, presentaremos y explicaremos las funciones miembro pÃºblicas deÂ <i>displayclass</i>, el objeto de macro de primer nivel.</Text>
+<Figure id="illustration_of_macro_precedence">
+<Title>
+<Text id="1031">IlustraciÃ³n de la prioridad entre las macros</Text>
+</Title>
+<CodeLine>package query</CodeLine>
+<CodeLine>_header_ [] Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  {_querytitle_}</CodeLine>
+<CodeLine>_header_ [l=en] Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  {Search page}</CodeLine>
+<CodeLine>_header_ [c=demo] Â Â Â Â Â Â Â Â Â  {&lt;table</CodeLine>
+<CodeLine>bgcolor=green&gt;&lt;tr&gt;&lt;td&gt;_querytitle_&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;}</CodeLine>
+<CodeLine>_header_ [v=1] Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  {_textquery_}</CodeLine>
+<CodeLine>_header_ [l=fr,v=1,c=hdl] Â  {HDL Page de recherche}</CodeLine>
+</Figure>
+<Text id="1032">En una colecciÃ³n Greenstone clÃ¡sica, la prioridad entre las macros es normalmente:Â <i>c</i>Â (para la colecciÃ³n) tiene prioridad sobreÂ <i>v</i>Â (para la interfaz grÃ¡fica o textual), que tiene prioridad sobreÂ <i>l</i>Â (para el idioma). Esto se establece con la lÃ­nea:</Text>
+<CodeLine>macroprecedence c, v, l</CodeLine>
+<Text id="1033">en el archivo de configuraciÃ³n principalÂ <i>main.cfg</i>. Las instrucciones de macros de la Figura <CrossRef target="Figure" ref="illustration_of_macro_precedence"/> definen ejemplos de macros para _Â <i>header</i>Â _ en el paqueteÂ <i>query</i>Â para distintos valores deÂ <i>c</i>,Â <i>v</i>Â yÂ <i>l</i>. Si los argumentos CGI proporcionados cuando se solicita una acciÃ³n incluyenÂ <i>c=hdl</i>,Â <i>v=1</i>Â yÂ <i>l=en</i>, se seleccionarÃ­a entonces la presentaciÃ³n de la macro _Â <i>header</i>Â _Â <i>[v=1]</i>. Se seleccionarÃ­a antes que _Â <i>content</i>Â _Â <i>[l=en]</i>Â porqueÂ <i>v</i>Â tiene prioridad sobreÂ <i>l</i>. La macro _Â <i>content</i>Â _Â <i>[l=fr, v=1, c=hdl]</i>Â no serÃ­a seleccionada porque el parÃ¡metro de pÃ¡gina paraÂ <i>l</i>Â es diferente.</Text>
+<Figure id="data_structures_representing_the_default_macros">
+<Title>
+<Text id="1034">Estructuras de datos que representan las macros por defecto</Text>
+</Title>
+<File width="605" height="224" url="images/Dev_Fig_45.png"/>
+</Figure>
+<Text id="1035">En la Figura <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/> se muestra la estructura de datos principales creada por la lectura de los archivos de macros especificados enÂ <i>etc/main.cfg</i>. Se trata esencialmente de una matriz asociativa de matrices asociativas de matrices asociativas. El nivel superior (que aparece a la izquierda) indiza el paquete del que procede la macro, y el segundo nivel indiza el nombre de la macro. El Ãºltimo nivel indiza todos los parÃ¡metros especificados, guardando cada uno de ellos como tipoÂ <i>mvalue</i>Â que registra el valor de la macro y el archivo del que procede. Por ejemplo, podemos ver el texto definido para _Â <i>header</i>Â _Â <i>[l=en]</i>Â de la Figura <CrossRef target="Figure" ref="illustration_of_macro_precedence"/> almacenado en el mÃ¡s bajo de los dos registrosÂ <i>mvalue</i>Â de la Figura <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/>.</Text>
+<Figure id="displayclass_api">
+<Title>
+<Text id="1036">API de la claseÂ <i>displayclass</i>Â (abreviada)</Text>
+</Title>
+<CodeLine>class displayclass</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>Â  displayclass ();</CodeLine>
+<CodeLine>Â  ~displayclass ();</CodeLine>
+<CodeLine>Â  int isdefaultmacro (text_t package, const text_t &amp;macroname);</CodeLine>
+<CodeLine>Â  int setdefaultmacro (text_t package, const text_t &amp;macroname,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  text_t params, const text_t &amp;macrovalue); </CodeLine>
+<CodeLine>Â  int loaddefaultmacros (text_t thisfilename);</CodeLine>
+<CodeLine>Â  void openpage (const text_t &amp;thispageparams,</CodeLine>
+<CodeLine>Â  const text_t &amp;thisprecedence);</CodeLine>
+<CodeLine>Â  void setpageparams (text_t thispageparams,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  text_t thisprecedence);</CodeLine>
+<CodeLine>Â  int setmacro (const text_t &amp;macroname,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  text_t package,</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  const text_t &amp;macrovalue);</CodeLine>
+<CodeLine>Â  void expandstring (const text_t &amp;inputtext, text_t &amp;outputtext);</CodeLine>
+<CodeLine>Â  void expandstring (text_t package, const text_t &amp;inputtext,</CodeLine>
+<CodeLine>Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â text_t &amp;outputtext, int recursiondepth = 0);</CodeLine>
+<CodeLine>Â  void setconvertclass (outconvertclass *theoutc) {outc = theoutc;}</CodeLine>
+<CodeLine>Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â outconvertclass *getconvertclass () {return outc;}</CodeLine>
+<CodeLine>Â Â Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ostream *setlogout (ostream *thelogout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1037">El objeto principal de apoyo al lenguaje de macros esÂ <i>displayclass</i>, definido enÂ <i>lib/display.h</i>. Sus funciones miembro pÃºblicas aparecen en la Figura <CrossRef target="Figure" ref="displayclass_api"/>. La clase lee los archivos de macros especificados utilizandoÂ <i>loaddefaultmacros( )</i>Â y guarda en una secciÃ³n protegida de la clase (que no se muestra) el tipo de la estructura de datos que se muestra en la Figura <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/>. Es posible asimismo que el sistema de ejecuciÃ³n cree macros utilizandoÂ <i>setmacro( )</i>Â (en el Ãºltimo ejemplo de la SecciÃ³n <CrossRef target="Section" ref="how_the_conceptual_framework_fits_together"/>,Â <i>pageaction</i>Â establece que _Â <i>homeextra</i>Â _ sea el cuadro generado dinÃ¡micamente para las colecciones disponibles que utilizan esta funciÃ³n). Todo ello con la ayuda de un conjunto de matrices asociativas semejantes a las que se utilizan para representar los archivos de macros (no es idÃ©ntico porque el primero no requiere la capa âparÃ¡metroâ). EnÂ <i>displayclass</i>, las macros que se leen desde el archivo se denominanÂ <i>macros por defecto</i>. Las macros locales que se especifican a travÃ©s deÂ <i>setmacro( )</i>Â se denominanÂ <i>macros en curso</i>, y son borradas de la memoria tras generarse la pÃ¡gina.</Text>
+<Text id="1038">Cuando se va a generar una pÃ¡gina, se llama primeroÂ <i>openpage( )</i>Â para comunicar las configuraciones en curso de los parÃ¡metros de la pÃ¡gina en cuestiÃ³n (Â <i>l=en</i>, etc.). A continuaciÃ³n, el texto y las macros fluyen a travÃ©s de la clase â normalmente desde unaÂ <i>actionclass</i>Â â utilizando el cÃ³digo:</Text>
+<CodeLine>cout &lt;&lt; text_t2ascii &lt;&lt; display &lt;&lt; â_unamacro_â</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  &lt;&lt; â_otramacro_â;</CodeLine>
+<Text id="1039">El resultado es que las macros se amplÃ­an siguiendo las configuraciones de los parÃ¡metros de la pÃ¡gina. En caso necesario, estas configuraciones pueden modificarse durante el proceso mediante una acciÃ³n que utilizaÂ <i>setpageparams( )</i>. Las demÃ¡s funciones miembro pÃºblicas proporcionan el apoyo de nivel inferior.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_receptionist_code">
+<Title>
+<Text id="1040">El cÃ³digo del recepcionista</Text>
+</Title>
+<Content>
+<Text id="1041">Hemos explicado ya los objetos principales del recepcionista. A continuaciÃ³n, detallaremos las clases de apoyo que se encuentran en el directorioÂ <i>GSDLHOME/src/recpt</i>. Excepto cuando la eficiencia es prioritaria, en cuyo caso las definiciones estÃ¡nÂ <i>inline</i>Â (en lÃ­nea), los detalles de la implementaciÃ³n se encuentran en el archivoÂ <i>.cpp</i>Â correspondiente al archivo de encabezados. Los archivos de apoyo suelen incluir la palabraÂ <i>tool</i>Â como parte del nombre del archivo, como enÂ <i>OIDtools.h</i>Â yÂ <i>formattools.h</i>.</Text>
+<Text id="1042">Un segundo conjunto de archivos de alcance lÃ©xico comprenden el prefijoÂ <i>z3950</i>. Los archivos proporcionan acceso remoto a las bases de datos y los catÃ¡logos en lÃ­nea pÃºblicamente accesibles mediante el protocolo Z39.50.</Text>
+<Text id="1043">Otro amplio grupo de archivos de apoyo comprende el tÃ©rminoÂ <i>browserclass</i>. Estos archivos estÃ¡n relacionados mediante una jerarquÃ­a de herencia virtual. Como grupo apoyan la nociÃ³n abstracta de consulta: generaciÃ³n de pÃ¡ginas en serie que comportan contenidos de documentos compartimentados o metadatos. Las posibilidades de consulta incluyen el examen de documentos ordenados alfabÃ©ticamente por tÃ­tulo o cronolÃ³gicamente por fecha, la consulta de los resultados de una bÃºsqueda por grupos de diez, y el acceso a las pÃ¡ginas individuales de un libro utilizando el mecanismo âir a la pÃ¡ginaâ. Todas las actividades de consulta heredan la clase de baseÂ <i>browserclass</i>Â :</Text>
+<BulletList>
+<Bullet>
+<Text id="1044"><i>datelistbrowserclass</i>Â para apoyo para las listas cronolÃ³gicas;</Text>
+</Bullet>
+<Bullet>
+<Text id="1045"><i>hlistbrowserclass</i>Â para apoyo para las listas horizontales;</Text>
+</Bullet>
+<Bullet>
+<Text id="1046"><i>htmlbrowserclass</i>Â para apoyo para las pÃ¡ginas HTML;</Text>
+</Bullet>
+<Bullet>
+<Text id="1047"><i>invbrowserclass</i>Â para apoyo para las listas invisibles;</Text>
+</Bullet>
+<Bullet>
+<Text id="1048"><i>pagedbrowserclass</i>Â para apoyo para ir a una pÃ¡gina particular;</Text>
+</Bullet>
+<Bullet>
+<Text id="1049"><i>vlistbrowserclass</i>Â para apoyo para las listas verticales.</Text>
+</Bullet>
+</BulletList>
+<Text id="1050">Las acciones acceden a los objetosÂ <i>browserclass</i>Â a travÃ©s del archivoÂ <i>browsetools.h</i>.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="140">
+<Text id="1051"><b>OIDtools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1052">FunciÃ³n de apoyo para la evaluaciÃ³n de los identificadores de documento en el protocolo.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1053"><b>action.h</b></Text>
+</th>
+<th width="390">
+<Text id="1054">Clase de base para la entidad AcciÃ³n expuesta en la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1055"><b>authenaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1056">AcciÃ³n heredada para la gestiÃ³n de la autenticaciÃ³n de un usuario.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1057"><b>browserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1058">Clase de base para las actividades de consulta abstractas.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1059"><b>browsetools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1060">FunciÃ³n de apoyo para el acceso a la jerarquÃ­aÂ <i>browserclass</i>. Las funciones incluyen la ampliaciÃ³n y contracciÃ³n de contenidos, la creaciÃ³n de un Ã­ndice y la generaciÃ³n de controles como el mecanismo âir a la pÃ¡ginaâ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1061"><b>cgiargs.h</b></Text>
+</th>
+<th width="390">
+<Text id="1062">DefineÂ <i>cgiarginfo</i>, utilizado en la Figura <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/>, asÃ­ como el apoyo de otras estructuras de datos para los argumentos CGI.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1063"><b>cgiutils.h</b></Text>
+</th>
+<th width="390">
+<Text id="1064">FunciÃ³n de apoyo para los argumentos CGI que utilizan las estructuras de datos definidas enÂ <i>cgiargs.h</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1065"><b>cgiwrapper.h</b></Text>
+</th>
+<th width="390">
+<Text id="1066">FunciÃ³n de apoyo que hace todo lo necesario para generar una pÃ¡gina utilizando el protocolo CGI. El acceso se hace mediante la funciÃ³n:</Text>
+<CodeLine>void cgiwrapper (receptionist &amp;recpt,</CodeLine>
+<CodeLine>Â  text_t collection);</CodeLine>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1067">que es la Ãºnica funciÃ³n declarada en el archivo de encabezados. Todo el resto del archivoÂ <i>.cpp</i>Â tiene un alcance lÃ©xico de carÃ¡cter local en el archivo (utilizando la palabra clave C++Â <i>static</i>). Si se utiliza la funciÃ³n para una colecciÃ³n particular, entonces se debe introducirÂ <i>collection</i>, o si no la cadena vacÃ­a ââ. El cÃ³digo incluye apoyo para Fast-CGI.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1068"><b>collectoraction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1069">AcciÃ³n heredada que facilita la creaciÃ³n de colecciones por parte del usuario final mediante el Colector. La pÃ¡gina generada procede deÂ <i>collect.dm</i>Â y es controlada por el argumento CGIÂ <i>p=page</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1070"><b>comtypes.h</b></Text>
+</th>
+<th width="390">
+<Text id="1071">Tipos centrales delÂ <i>protocolo</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1072"><b>converter.h</b></Text>
+</th>
+<th width="390">
+<Text id="1073">Objeto de apoyo para los convertidores de flujo.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1074"><b>datelistbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1075">Heredado deÂ <i>browserclass</i>, este objeto presta apoyo para la consulta de las listas cronolÃ³gicas, como las que se ven en la colecciÃ³nÂ <i>Archivos Greenstone</i>Â en âÂ <i>dates</i>Â â (fechas) de la barra de desplazamiento.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1076"><b>documentaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1077">AcciÃ³n heredada que se utiliza para recuperar un documento o porciÃ³n de una jerarquÃ­a de clasificaciÃ³n.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1078"><b>extlinkaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1079">AcciÃ³n heredada que controla si un usuario va directamente a un enlace externo o si debe pasar por una pÃ¡gina de aviso que le informa de que se dispone a salir del sistema de biblioteca digital.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1080"><b>formattools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1081">FunciÃ³n de apoyo para analizar y evaluar las instruccionesÂ <i>format</i>Â de configuraciÃ³n de colecciÃ³n. Se explica con mÃ¡s detalles en la SecciÃ³n <CrossRef target="Subsection" ref="formatting"/>Â <i>supra</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1082"><b>historydb.h</b></Text>
+</th>
+<th width="390">
+<Text id="1083">Estructuras de datos y funciÃ³n de apoyo para la gestiÃ³n de una base de datos de bÃºsquedas anteriores, de modo que un usuario pueda iniciar una nueva bÃºsqueda que incluya tÃ©rminos de bÃºsquedas anteriores.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1084"><b>hlistbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1085">Heredado deÂ <i>browserclass</i>, este objeto presta apoyo para la consulta de las listas horizontales.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1086"><b>htmlbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1087">Heredado deÂ <i>browserclass</i>, este objeto presta apoyo para la consulta de las pÃ¡ginas HTML.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1088"><b>htmlgen.h</b></Text>
+</th>
+<th width="390">
+<Text id="1089">FunciÃ³n de apoyo para resaltar los tÃ©rminos de bÃºsqueda en una cadenaÂ <i>text_t</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1090"><b>htmlutils.h</b></Text>
+</th>
+<th width="390">
+<Text id="1091">FunciÃ³n de apoyo que convierte una cadenaÂ <i>text_t</i>Â en el HTML equivalente. Los sÃ­mbolos â, &amp;, &lt; y &gt; se convierten respectivamente enÂ <i>&amp;quot;</i>,Â <i>&amp;amp;</i>,Â <i>&amp;lt;</i>Â yÂ <i>&amp;gt;</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1092"><b>infodbclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1093">Define dos clases:Â <i>gdbmclass</i>Â eÂ <i>infodbclass</i>. La primera proporciona la API de Greenstone para GDBM; la segunda es la clase de objeto utilizada para guardar una entrada de registro leÃ­da en una base de datos GDBM, y es esencialmente una matriz asociativa formada por matrices de cadenasÂ <i>text_t</i>Â indizadas por nÃºmeros enteros.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1094"><b>invbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1095">Heredado deÂ <i>browserclass</i>, este objeto presta apoyo para la consulta de listas que no se presentarÃ¡n en pantalla (invisibles).</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1096"><b>nullproto.h</b></Text>
+</th>
+<th width="390">
+<Text id="1097">Heredada deÂ <i>recptproto</i>, este clase realiza el protocolo nulo a travÃ©s de las llamadas de funciones del recepcionista al servidor de colecciÃ³n.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1098"><b>pageaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1099">AcciÃ³n heredada que, en combinaciÃ³n con el archivo de macros indicado enÂ <i>p=page</i>, genera una pÃ¡gina Web.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1100"><b>pagedbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1101">Heredado deÂ <i>browserclass</i>, este objeto presta apoyo para el mecanismo âir a la pÃ¡ginaâ, como vimos por ejemplo en la colecciÃ³n Gutenberg.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1102"><b>pingaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1103">AcciÃ³n heredada que comprueba si una colecciÃ³n particular responde.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1104"><b>queryaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1105">AcciÃ³n heredada que toma la bÃºsqueda formulada, las configuraciones y las preferencias, efectÃºa la bÃºsqueda y genera como resultado el subconjunto de documentos correspondientesÂ <i>o=num</i>Â empezando en la posiciÃ³nÂ <i>r=num</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1106"><b>querytools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1107">FunciÃ³n de apoyo para las bÃºsquedas.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1108"><b>receptionist.h</b></Text>
+</th>
+<th width="390">
+<Text id="1109">Objeto de alto nivel del recepcionista. Mantiene un registro de las informaciones de argumentos CGI, las instancias de cada acciÃ³n heredada, las instancias de cada objeto de consulta heredado, el objeto central de lenguaje de macrosÂ <i>displayclass</i>, asÃ­ como todos los convertidores posibles.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1110"><b>recptconfig.h</b></Text>
+</th>
+<th width="390">
+<Text id="1111">FunciÃ³n de apoyo para la lectura de los principales archivos de configuraciÃ³n y de sitio.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1112"><b>recptproto.h</b></Text>
+</th>
+<th width="390">
+<Text id="1113">Clase de base para el protocolo.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1114"><b>statusaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1115">AcciÃ³n heredada que genera, conjuntamente conÂ <i>status.dm</i>, las diversas pÃ¡ginas de administraciÃ³n.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1116"><b>tipaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1117">AcciÃ³n heredada que genera, conjuntamente conÂ <i>tip.dm</i>, una pÃ¡gina Web que contiene una sugerencia elegida de forma aleatoria a partir de una lista de sugerencias que se encuentra enÂ <i>tip.dm</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1118"><b>userdb.h</b></Text>
+</th>
+<th width="390">
+<Text id="1119">Estructura de datos y funciÃ³n de apoyo para mantener una base de datos GDBM de usuarios: su contraseÃ±a, sus grupos, etc.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1120"><b>usersaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1121">Una acciÃ³n de administraciÃ³n heredada de la clase de base que permite aÃ±adir y suprimir usuarios, asÃ­ como modificar los grupos a los que pertenecen.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1122"><b>vlistbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1123">Heredado deÂ <i>browserclass</i>, este objeto presta apoyo para la consulta de las listas verticales, que constituyen la base de los clasificadores. Por ejemplo, los elementos secundarios del nodo de tÃ­tulos que empiezan con la letraÂ <i>N</i>Â forman unaÂ <i>Vlist</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1124"><b>z3950cfg.h</b></Text>
+</th>
+<th width="390">
+<Text id="1125">Apoyo de estructura de datos para el protocolo Z39.50. Utilizado porÂ <i>z3950proto.cpp</i>, que define la clase de protocolo principal (heredada de la clase de baseÂ <i>recptproto</i>) y el analizador del archivo de configuraciÃ³nÂ <i>zparse.y</i>Â (escrito en YACC).</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1126"><b>z3950proto.h</b></Text>
+</th>
+<th width="390">
+<Text id="1127">Heredado deÂ <i>recptproto</i>, esta clase implementa el protocolo Z39.50 de tal modo que el recepcionista de Greenstone pueda acceder a los sitios de bibliotecas remotas que funcionan con servidores Z39.50.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1128"><b>z3950server.h</b></Text>
+</th>
+<th width="390">
+<Text id="1129">Apoyo complementario para el protocolo Z39.50.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="initialisation">
+<Title>
+<Text id="1130">InicializaciÃ³n</Text>
+</Title>
+<Content>
+<Text id="1131">En Greenstone, la inicializaciÃ³n es una operaciÃ³n compleja que trata archivos de configuraciÃ³n y asigna valores por defecto a los campos de datos. AdemÃ¡s de las funciones de herencia y de creaciÃ³n, los objetos centrales definen las funcionesÂ <i>init( )</i>Â yÂ <i>configure( )</i>Â para contribuir a normalizar la tarea. Aun asÃ­, el orden de ejecuciÃ³n puede ser difÃ­cil de seguir. En esta secciÃ³n se explica lo que sucede.</Text>
+<Text id="1132">Greenstone utiliza varios archivos de configuraciÃ³n con diferentes fines, pero todos respetan la misma sintaxis. A menos que una lÃ­nea empiece por el sÃ­mbolo â#â o sÃ³lo contenga espacios en blanco, la primera palabra define un tÃ©rmino clave y las demÃ¡s representan una configuraciÃ³n particular de dicho tÃ©rmino clave.</Text>
+<Text id="1133">Las lÃ­neas de los archivos de configuraciÃ³n se transmiten de una en una a la funciÃ³nÂ <i>configure( )</i>Â y contienen dos argumentos: el tÃ©rmino clave y una matriz de las palabras restantes. BasÃ¡ndose en el tÃ©rmino clave, una versiÃ³n particular deÂ <i>configure( )</i>Â determina si la informaciÃ³n es de interÃ©s, y si es asÃ­ la guarda. Por ejemplo,Â <i>collectserver</i>Â (que corresponde al objeto ColecciÃ³n de la Figura <CrossRef target="Figure" ref="greenstone_runtime_system"/>) trata las instrucciones de formato del archivo de configuraciÃ³n de una colecciÃ³n. Cuando la funciÃ³nÂ <i>configure( )</i>Â recibe el tÃ©rmino claveÂ <i>format</i>, se activa una instrucciÃ³nÂ <i>if</i>Â que guarda en el objeto una copia del segundo argumento de la funciÃ³n.</Text>
+<Text id="1134">Tras tratar el tÃ©rmino clave y antes de que concluya la funciÃ³n, algunas versiones deÂ <i>configure( )</i>Â transmiten los datos a las funcionesÂ <i>configure( )</i>Â de otros objetos. El objeto Recepcionista activa la funciÃ³nÂ <i>configure( )</i>Â de los objetos Acciones, Protocolos y Consulta. El objeto Protocolo nulo activa la funciÃ³nÂ <i>configure( )</i>Â de cada objeto ColecciÃ³n; el objeto ColecciÃ³n activa los objetos Filtro y Fuente.</Text>
+<Text id="1135">En C++, los campos de datos se inicializan normalmente mediante la funciÃ³n de creaciÃ³n del objeto. Sin embargo, en Greenstone algunas inicializaciones dependen de los valores leÃ­dos en los archivos de configuraciÃ³n, por ello es preciso proceder a una segunda tanda de inicializaciones. Esta es la finalidad de las funciones miembroÂ <i>init( )</i>, y en algunos casos requiere posteriores llamadas de la funciÃ³nÂ <i>configure( )</i>.</Text>
+<Figure id="initialising_greenstone_using_the_null_protocol">
+<Title>
+<Text id="1136">InicializaciÃ³n de Greenstone utilizando el protocolo nulo</Text>
+</Title>
+<CodeLine>============</CodeLine>
+<CodeLine>Main program</CodeLine>
+<CodeLine>============</CodeLine>
+<CodeLine>Statically construct Receptionist</CodeLine>
+<CodeLine>Statically construct NullProtocol</CodeLine>
+<CodeLine>Establish the value for âgsdlhomeâ by reading gsdlsite.cfg</CodeLine>
+<CodeLine>Foreach directory in GSDLHOME/collect that isnât "modelcol":</CodeLine>
+<CodeLine>Â  Add directory name (now treated as collection name) to NullProtocol:</CodeLine>
+<CodeLine>Â Â Â  Dynamically construct Collection</CodeLine>
+<CodeLine>Â Â Â  Dynamically construct Gdbm class</CodeLine>
+<CodeLine>Â Â Â  Dynamically construct the Null Filter</CodeLine>
+<CodeLine>Â Â Â  Dynamically construct the Browse Filter</CodeLine>
+<CodeLine>Â Â Â  Dynamically construct MgSearch</CodeLine>
+<CodeLine>Â Â Â  Dynamically construct the QueryFilter</CodeLine>
+<CodeLine>Â Â Â  Dynamically construct the MgGdbmSource</CodeLine>
+<CodeLine>Â Â Â  Configure Collection with âcollectionâ</CodeLine>
+<CodeLine>Â Â Â Â Â  Passing âcollectionâ value on to Filters and Sources:</CodeLine>
+<CodeLine>Configure Receptionist with âcollectinfoâ:</CodeLine>
+<CodeLine>Â Â Â Â Â  Passing âcollectinfoâ value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>Add NullProtocol to Receptionist</CodeLine>
+<CodeLine>Add in UTF-8 converter</CodeLine>
+<CodeLine>Add in GB converter</CodeLine>
+<CodeLine>Add in Arabic converter</CodeLine>
+<CodeLine>Foreach Action:</CodeLine>
+<CodeLine>Â  Statically construct Action</CodeLine>
+<CodeLine>Â  Add Action to Receptionist</CodeLine>
+<CodeLine>Foreach Browsers:</CodeLine>
+<CodeLine>Â  Statically construct Browser</CodeLine>
+<CodeLine>Â  Add Browser to Receptionist</CodeLine>
+<CodeLine>Call function cgiwrapper:</CodeLine>
+<CodeLine>Â  =================</CodeLine>
+<CodeLine>Â  Configure objects</CodeLine>
+<CodeLine>Â  =================</CodeLine>
+<CodeLine>Â  Configure Receptionist with âcollectionâ</CodeLine>
+<CodeLine>Â Â Â  Passing âcollectionâ value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>Â Â Â  NullProtocol not interested in âcollectionâ</CodeLine>
+<CodeLine>Â  Configure Receptionist with âhttpimgâ</CodeLine>
+<CodeLine>Â Â Â  Passing âhttpimgâ value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>Â Â Â  NullProtocol passing âhttpimgâ on to Collection</CodeLine>
+<CodeLine>Â Â Â  Passing âhttpimgâ value on to Filters and Sources:</CodeLine>
+<CodeLine>Â  Configure Receptionist with âgwcgiâ</CodeLine>
+<CodeLine>Â Â Â  Passing âgwcgiâ value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>Â Â Â  NullProtocol passing âgwcgiâ on to Collection</CodeLine>
+<CodeLine>Â Â Â  Passing âgwcgiâ value on to Filters and Sources:</CodeLine>
+<CodeLine>Â  Reading in site configuration file gsdlsite.cfg</CodeLine>
+<CodeLine>Â Â Â  Configure Recptionist with âgsdlhomeâ</CodeLine>
+<CodeLine>Â Â Â Â Â  Passing âgsdlhomeâ value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>Â Â Â Â Â  NullProtocol passing âgsdlhomeâ on to Collection</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â  Passing âgsdlhomeâ value on to Filters and Sources:</CodeLine>
+<CodeLine>Â Â Â  Configure Recptionist with ...</CodeLine>
+<CodeLine>Â Â Â  ... and so on for all entries in gsdlsite.cfg </CodeLine>
+<CodeLine>Â  Reading in main configuration file main.cfg</CodeLine>
+<CodeLine>Â Â Â  Configure Recptionist with ...</CodeLine>
+<CodeLine>Â Â Â  ... and so on for all entries in main.cfg</CodeLine>
+<CodeLine>Â  ====================</CodeLine>
+<CodeLine>Â  Initialising objects</CodeLine>
+<CodeLine>Â  ====================</CodeLine>
+<CodeLine>Â  Initialise the Receptionist</CodeLine>
+<CodeLine>Â Â Â  Configure Receptionist with âcollectdirâ</CodeLine>
+<CodeLine>Â Â Â Â Â  Passing âcollectdirâ value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>Â Â Â Â Â  NullProtocol not interested in âcollectdirâ</CodeLine>
+<CodeLine>Â Â Â  Read in Macro files</CodeLine>
+<CodeLine>Â Â Â  Foreach Actions</CodeLine>
+<CodeLine>Â Â Â Â Â  Initialise Action</CodeLine>
+<CodeLine>Â Â Â  Foreach Protocol</CodeLine>
+<CodeLine>Â Â Â Â Â  Initialise Protocol</CodeLine>
+<CodeLine>Â Â Â Â Â  When Protocol==NullProtocol:</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â  Foreach Collection</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â  Reading Collectionâs build.cfg</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â  Reading Collectionâs collect.cfg</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â  Configure Collection with âcreatorâ</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â  Â Â Â Passing âcreatorâ value on to Filters and Sources:</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â  Configure Collection with âmaintainerâ</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â  Passing âmaintainerâ value on to Filters and Sources:</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â  ... and so on for all entries in collect.cfg</CodeLine>
+<CodeLine>Â Â Â  Foreach Browsers</CodeLine>
+<CodeLine>Â Â Â  Â Â Initialise Browser</CodeLine>
+<CodeLine>Â  =============</CodeLine>
+<CodeLine>Â  Generate page</CodeLine>
+<CodeLine>Â  =============</CodeLine>
+<CodeLine>Â  Parse CGI arguments</CodeLine>
+<CodeLine>Â  Execute designated Action to produce page</CodeLine>
+<CodeLine>End.</CodeLine>
+</Figure>
+<Text id="1137">En la Figura <CrossRef target="Figure" ref="initialising_greenstone_using_the_null_protocol"/> se presentan los mensajes de diagnÃ³stico generados por una versiÃ³n de Greenstone configurada para resaltar el proceso de inicializaciÃ³n. El programa arranca con la funciÃ³nÂ <i>main( )</i>Â del archivoÂ <i>recpt/librarymain.cpp</i>. Crea un objeto Recepcionista y un objeto Protocolo nulo, luego recorre el archivoÂ <i>gsdlsite.cfg</i>Â (ubicado en el mismo directorio que el ejecutableÂ <i>library</i>) enÂ  busca deÂ <i>gsdlhome</i>Â y guarda su valor en una variable. Para cada colecciÃ³n en lÃ­nea âlista establecida leyendo los directorios deÂ <i>GSDLHOME/collect</i>Â â el programa crea un objeto de colecciÃ³n mediante el objeto Protocolo nulo, que contiene objetos Filtro, BÃºsqueda y Fuente, asÃ­ como algunas llamadas cableadas aÂ <i>configure( )</i>.</Text>
+<Text id="1138">A continuaciÃ³n, la funciÃ³nÂ <i>main( )</i>Â agrega el objeto Protocolo nulo al recepcionista, que mantiene una matriz de clase de base de protocolos en un campo de datos protegidos, y luego activa varios convertidores. La funciÃ³nÂ <i>main( )</i>Â crea todos los objetos AcciÃ³n y Consulta que se utilizan en el ejecutable y los incorpora al recepcionista. La funciÃ³n concluye al activar la funciÃ³nÂ <i>cgiwrapper( )</i>Â ubicada enÂ <i>cgiwrapper.cpp</i>, que efectÃºa a su vez un nÃºmero importante de inicializaciones de objetos.</Text>
+<Text id="1139">La funciÃ³nÂ <i>cgiwrapper( )</i>Â comprende tres partes: configuraciÃ³n, inicializaciÃ³n y generaciÃ³n de pÃ¡gina. En primer lugar, se efectÃºan algunas llamadas cableadas a la funciÃ³nÂ <i>configure( )</i>, luego se lee el archivoÂ <i>gsdlsite.cfg</i>Â y se aplicaÂ <i>configure</i>Â a cada lÃ­nea. Lo mismo ocurre con el archivoÂ <i>etc/main.cfg</i>.</Text>
+<Text id="1140">La segunda fase deÂ <i>cgiwrapper( )</i>Â activaÂ <i>init( )</i>. El objeto Recepcionista sÃ³lo hace una llamada a su funciÃ³nÂ <i>init( )</i>, pero esta acciÃ³n invoca las funcionesÂ <i>init( )</i>Â de los diferentes objetos que contiene. Primero una llamada cableada aÂ <i>configure( )</i>Â para instalarÂ <i>collectdir</i>, y luego se leen los archivos de macros. Se activa la funciÃ³nÂ <i>init( )</i>Â de cada acciÃ³n. Lo mismo ocurre con cada protocolo almacenado en el recepcionista, pero en el sistema que se describe aquÃ­ sÃ³lo se almacena el protocolo nulo. La activaciÃ³n de la funciÃ³nÂ <i>init( )</i>Â de este objeto suscita otras configuraciones: en cada colecciÃ³n del protocolo nulo se leen y se tratan los archivos especÃ­ficos de la colecciÃ³nÂ <i>build.cfg</i>Â yÂ <i>collect.cfg</i>, y cada lÃ­nea activa la funciÃ³nÂ <i>configure( )</i>.</Text>
+<Text id="1141">La fase final deÂ <i>cgiwrapper( )</i>Â consiste en analizar los argumentos CGI y luego activar la acciÃ³n adecuada. Ambas acciones se efectÃºan con la asistencia del objeto Recepcionista.</Text>
+<Text id="1142">Los cÃ³digos de configuraciÃ³n, inicializaciÃ³n y generaciÃ³n de pÃ¡ginas estÃ¡n separados porque Greenstone estÃ¡ concebido para funcionar como servidor (con Fast-CGI, el protocolo CORBA, o la versiÃ³n Biblioteca Local de Windows). En ese modo de funcionamiento, el cÃ³digo de configuraciÃ³n y de inicializaciÃ³n sÃ³lo se ejecuta una vez, y luego el programa permanece en memoria y genera numerosas pÃ¡ginas Web en respuesta a las consultas de los usuarios sin necesidad de volverse a inicializar.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="configuring_your_greenstone_site">
+<Title>
+<Text id="1143">CONFIGURACIÃN DEL SITIO GREENSTONE</Text>
+</Title>
+<Content>
+<Text id="1144">En Greenstone, se utilizan dos archivos de configuraciÃ³n para configurar las diversas caracterÃ­sticas del sitio Greenstone: el archivo de configuraciÃ³n âprincipalâÂ <i>main.cfg</i>, que se encuentra en el directorioÂ <i>GSDLHOME/etc</i>, y el archivo de configuraciÃ³n âde sitioâÂ <i>gsdlsite.cfg</i>, que se encuentra en el directorioÂ <i>GSDLHOME/cgi-bin</i>. Ambos archivos controlan aspectos especÃ­ficos de la configuraciÃ³n del sitio y pueden visualizarse desde la pÃ¡gina de administraciÃ³n de Greenstone.</Text>
+<Section id="main_configuration_file">
+<Title>
+<Text id="1145">Archivo de configuraciÃ³n principal</Text>
+</Title>
+<Content>
+<Text id="1146">El archivo de configuraciÃ³n principalÂ <i>main.cfg</i>Â sirve para configurar el recepcionista, esto es, la parte de Greenstone que procesa las consultas y muestra las pÃ¡ginas. Se puede controlar todo, desde las lenguas que la interfaz puede utilizar hasta los registros que se llevarÃ¡n.</Text>
+<Subsection id="site_maintenance_and_logging">
+<Title>
+<Text id="1147">Mantenimiento del sitio y registro de utilizaciÃ³n (<i>logging</i>)</Text>
+</Title>
+<Content>
+<Text id="1148">Las lÃ­neas del archivo de configuraciÃ³n establecen la manera en que su sitio Greenstone se mantendrÃ¡, quÃ© funciones ofrecerÃ¡, quÃ© eventos se registrarÃ¡n y quÃ© notificaciones se harÃ¡n al responsable del mantenimiento. En el Cuadro <CrossRef target="Table" ref="configuration_options_for_site_maintenance_and_logging"/> se muestran algunas de las opciones disponibles; las restantes se exponen en las secciones siguientes.</Text>
+<Table id="configuration_options_for_site_maintenance_and_logging">
+<Title>
+<Text id="1149">Opciones de configuraciÃ³n para el mantenimiento del sitio y el registro de utilizaciÃ³n (<i>logging</i>)</Text>
+</Title>
+<TableContent>
+<tr>
+<th>Â </th>
+<th>
+<Text id="1150"><b>Valor</b></Text>
+</th>
+<th>
+<Text id="1151"><b>Finalidad</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1152">maintainer</Text>
+</th>
+<th>
+<Text id="1153">NULL o una direcciÃ³n de correo electrÃ³nico</Text>
+</th>
+<th>
+<Text id="1154">DirecciÃ³n de correo electrÃ³nico del encargado del mantenimiento del sitio que se utiliza para algunas notificaciones. Si es NULL se desactivan los eventos de correo electrÃ³nico.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1155">MailServer </Text>
+</th>
+<th>
+<Text id="1156">NULL o un nombre de servidor</Text>
+</th>
+<th>
+<Text id="1157">Servidor de correo electrÃ³nico de salida para el sitio. Si es NULL, se utilizaÂ <i>mail.dominio_del_encargado_del_mantenimiento</i>Â (por ejemplo, si el encargado del mantenimiento esÂ <i>ayuda@ejemplo.com</i>Â el valor por defecto serÃ¡Â <i>mail.ejemplo.com</i>.) Si ello no lleva a un servidor SMTP vÃ¡lido, los eventos de correo electrÃ³nico no funcionarÃ¡n.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1158"><i>status</i></Text>
+</th>
+<th>
+<Text id="1159"><i>enabled</i>Â (activado) oÂ <i>disabled</i>Â (desactivado)</Text>
+</th>
+<th>
+<Text id="1160">Determina si la pÃ¡gina de âMantenimiento y administraciÃ³nâ debe estar disponible.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1161"><i>collector</i></Text>
+</th>
+<th>
+<Text id="1162"><i>enabled</i>Â (activado) oÂ <i>disabled</i>Â (desactivado)</Text>
+</th>
+<th>
+<Text id="1163">Determina si la aplicaciÃ³n âColectorâ de creaciÃ³n de colecciÃ³n para el usuario final debe estar disponible.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1164"><i>logcgiargs</i></Text>
+</th>
+<th>
+<Text id="1165"><i>true</i>Â (verdadero) oÂ <i>false</i>Â (falso)</Text>
+</th>
+<th>
+<Text id="1166">Si el valor esÂ <i>true</i>Â (verdadero), se conserva un registro de utilizaciÃ³n enÂ <i>usage.txt</i>.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1167"><i>usecookies</i></Text>
+</th>
+<th>
+<Text id="1168"><i>true</i>Â (verdadero) oÂ <i>false</i>Â (falso)</Text>
+</th>
+<th>
+<Text id="1169">Si el valor esÂ <i>true</i>Â (verdadero), se acopia informaciÃ³n relativa a los usuarios del sitio (mediante registros de identificaciÃ³n oÂ <i>cookies</i>) que se guarda enÂ <i>usage.txt</i>Â (sÃ³lo funciona si la opciÃ³nÂ <i>logcgiargs</i>Â tiene el valorÂ <i>true</i>).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1170"><i>LogDateFormat</i></Text>
+</th>
+<th>
+<Text id="1171"><i>LocalTime</i>Â (hora local) oÂ <i>UTCTime</i>Â (hora universal) oÂ <i>Absolute</i>Â (hora absoluta)</Text>
+</th>
+<th>
+<Text id="1172">Formato en el que se consignan las fechas y las horas en los registros.Â <i>LocalTime</i>Â genera el formato âThu Dec 07 12:34 NZDT 2000â,Â <i>UTCTime</i>Â es el mismo formato pero en tiempo universal (o GMT), yÂ <i>absolute</i>Â es un nÃºmero entero que representa el nÃºmero de segundos transcurridos desde â00:00:00 01/01/1970 GMTâ</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1173"><i>LogEvents</i></Text>
+</th>
+<th>
+<Text id="1174"><i>AllEvents</i>Â (todos los eventos) oÂ <i>CollectorEvents</i>Â (eventos del Colector) oÂ <i>disabled</i>Â (desactivado)</Text>
+</th>
+<th>
+<Text id="1175">Registra determinados eventos enÂ <i>events.txt.</i><i>AllEvents</i>Â consigna todos los eventos de Greenstone,Â <i>CollectorEvents</i>Â sÃ³lo registra los eventos relacionados con el Colector, yÂ <i>disabled</i>Â no registra ningÃºn evento.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1176"><i>EmailEvents</i></Text>
+</th>
+<th>
+<Text id="1177"><i>enabled</i>Â (activado) oÂ <i>disabled</i>Â (desactivado)</Text>
+</th>
+<th>
+<Text id="1178">EnvÃ­a un mensaje por correo electrÃ³nico al encargado del mantenimiento (en caso de haberlo - vÃ©ase la opciÃ³nÂ <i>mantainer</i>) cada vez que se produce un evento.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1179"><i>EmailUserEvents</i></Text>
+</th>
+<th>
+<Text id="1180"><i>enabled</i>Â (activado) oÂ <i>disabled</i>Â (desactivado)</Text>
+</th>
+<th>
+<Text id="1181">EnvÃ­a un mensaje por correo electrÃ³nico al usuario sobre determinados eventos (por ejemplo, cuando el Colector finaliza la creaciÃ³n de una colecciÃ³n). </Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1182"><i>macrofiles</i></Text>
+</th>
+<th>
+<Text id="1183">lista de nombres de archivos de macros</Text>
+</th>
+<th>
+<Text id="1184">Determina quÃ© macros se encuentran a disposiciÃ³n del programa de interfaz de usuario de Greenstone</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="language_support">
+<Title>
+<Text id="1185">SelecciÃ³n de lenguas</Text>
+</Title>
+<Content>
+<Text id="1186">El archivo de configuraciÃ³nÂ <i>main.cfg</i>Â contiene dos tipos de entradas que inciden en la gestiÃ³n de las diferentes lenguas. Ãstas determinan quÃ© idiomas y quÃ© cÃ³digos estarÃ¡n disponibles en la pÃ¡gina de preferencias. Las lÃ­neasÂ <i>encoding</i>Â (codificaciÃ³n) especifican los diferentes tipos de codificaciÃ³n de caracteres que pueden seleccionarse. Las lÃ­neasÂ <i>language</i>Â (lengua) especifican quÃ© idiomas se podrÃ¡n seleccionar para la interfaz de usuario (por supuesto, es preciso que exista una macro de lengua para cada lengua posible).</Text>
+<Text id="1187">La lÃ­neaÂ <i>encoding</i>Â (codificaciÃ³n) puede contener cuatro valores posibles:Â <i>shortname</i>Â (nombre corto),Â <i>longname</i>Â (nombre largo),Â <i>map</i>Â (correspondencia) yÂ <i>multibyte</i>. El valorÂ <i>shortname</i>Â es la etiqueta del juego de caracteres estÃ¡ndar y debe especificarse en todas las codificaciones. El valorÂ <i>longname</i>Â da el nombre de codificaciÃ³n que se especifica en la pÃ¡gina deÂ <i>preferencias</i>. En su ausencia, el valor por defecto es el deÂ <i>shortname</i>. El valorÂ <i>map</i>Â es obligatorio para todas las codificaciones, excepto para UTF-8, que se maneja internamente (y que deberÃ­a siempre estar activado). El valorÂ <i>multibyte</i>Â deberÃ­a aplicarse a todos los juegos de caracteres que necesitan mÃ¡s de un byte por carÃ¡cter. El archivoÂ <i>main.cfg</i>Â especifica numerosas codificaciones, la mayorÃ­a de las cuales estÃ¡ desactivada, pues estÃ¡n comentadas de manera que la programaciÃ³n nos las toma en consideraciÃ³n. Para activar una codificaciÃ³n, suprima el carÃ¡cter de comentario â#â.</Text>
+<Text id="1188">Cada lÃ­neaÂ <i>language</i>Â (idioma) puede contener tres valores posibles:Â <i>shortname</i>Â (nombre corto),Â <i>longname</i>Â (nombre largo) yÂ <i>default_encoding</i>Â (codificaciÃ³n por defecto). El valorÂ <i>shortname</i>Â es el sÃ­mbolo de idioma de dos letras ISO 639 y es obligatorio. El valorÂ <i>longname</i>Â da el nombre de la lengua especificada en la pÃ¡gina deÂ <i>preferencias</i>. En su ausencia, el valor por defecto es el deÂ <i>shortname</i>. La opciÃ³nÂ <i>default_encoding</i>Â sirve para especificar la codificaciÃ³n preferida para esa lengua.</Text>
+</Content>
+</Subsection>
+<Subsection id="page_parameters_and_cgi_arguments">
+<Title>
+<Text id="1189">ParÃ¡metros de pÃ¡gina y argumentos CGI</Text>
+</Title>
+<Content>
+<Text id="1190">Se pueden definir parÃ¡metros de pÃ¡gina y argumentos CGI en el archivo de configuraciÃ³nÂ <i>main.cfg</i>. Recuerde que en la Figura <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/> la mayorÃ­a de los argumentos CGI se definen en el seno mismo del cÃ³digo C++ de la biblioteca. Sin embargo, a veces resulta Ãºtil definir nuevos argumentos o modificar los argumentos existentes en los archivos de configuraciÃ³n, lo cual evita recompilar la biblioteca.</Text>
+<Text id="1191">Para ello, utilice la opciÃ³n de configuraciÃ³nÂ <i>cgiarg</i>, que puede contener hasta seis argumentos:Â <i>shortname</i>Â (nombre corto),Â <i>longname</i>Â (nombre largo),Â <i>multiplechar</i>Â (caracteres mÃºltiples),Â <i>argdefault</i>Â (argumento por defecto),Â <i>defaultstatus</i>Â (estado por defecto) yÂ <i>savedarginfo</i>Â (informaciÃ³n de Resguardo (Â <i>backup</i>) de argumentos). Estos argumentos corresponden a opciones de argumentos CGI descritos en la SecciÃ³n <CrossRef target="Section" ref="receptionist"/>. Por ejemplo, en el archivoÂ <i>main.cfg</i>Â por defecto, la opciÃ³n de configuraciÃ³nÂ <i>cgiarg</i>Â sirve para establecer los valores por defecto de los argumentos CGI existentesÂ <i>a</i>Â yÂ <i>p</i>Â con los valoresÂ <i>p</i>Â yÂ <i>home</i>Â respectivamente.</Text>
+<Text id="1192">Los parÃ¡metros de pÃ¡gina son un caso particular de argumentos CGI que corresponden a los parÃ¡metros de los archivos de macros de Greenstone. Por ejemplo, el argumento CGIÂ <i>l</i>Â corresponde directamente al parÃ¡metroÂ <i>l=</i>Â en los archivos de macros. Se utiliza la opciÃ³n de configuraciÃ³nÂ <i>pageparam</i>Â para definir un argumento CGI tambiÃ©n como parÃ¡metro de pÃ¡gina.</Text>
+<Text id="1193">El mejor modo de aprender las diferentes opciones de configuraciÃ³n posibles en el archivo de configuraciÃ³nÂ <i>main.cfg</i>Â es experimentar con Ã©ste. Recuerde que si estÃ¡ utilizando la versiÃ³n Biblioteca Local de Greenstone con Windows, es preciso volver a arrancar el servidor para que toda modificaciÃ³n de los archivos de configuraciÃ³n surta efecto.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="site_configuration_file">
+<Title>
+<Text id="1194">Archivo de configuraciÃ³n de sitio</Text>
+</Title>
+<Content>
+<Table id="lines_in_gsdlsitecfg">
+<Title>
+<Text id="1195">LÃ­neas del archivoÂ <i>gsdlsite.cfg</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th>
+<Text id="1196"><b>LÃ­nea</b></Text>
+</th>
+<th>
+<Text id="1197"><b>FunciÃ³n</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1198">gsdlhome</Text>
+</th>
+<th>
+<Text id="1199">Una ruta hacia el directorioÂ <i>GSDLHOME</i>.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1200"><i>httpprefix</i></Text>
+</th>
+<th>
+<Text id="1201">La direcciÃ³n Web deÂ <i>GSDLHOME</i>. Si la raÃ­z de documentos de su servidor Web contiene el valorÂ <i>GSDLHOME</i>, no necesita esta lÃ­nea.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1202"><i>httpimage</i></Text>
+</th>
+<th>
+<Text id="1203">La direcciÃ³n Web del directorio que contiene las imÃ¡genes de la interfaz de usuario. Si la raÃ­z de documentos de su servidor Web contiene el valorÂ <i>GSDLHOME</i>, Ã©ste serÃ¡Â <i>/images</i>.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1204"><i>gwcgi</i></Text>
+</th>
+<th>
+<Text id="1205">La direcciÃ³n Web del presente guiÃ³n CGI (acaba generalmente porÂ <i>library</i>). No se necesita si su servidor Web contiene la variable de entornoÂ <i>SCRIPT_NAME</i>Â (nombre de guiÃ³n).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="1206"><i>maxrequests</i></Text>
+</th>
+<th>
+<Text id="1207">(SÃ³lo se aplica si se utiliza Fast-CGI). NÃºmero de consultas que Fast-CGI debe tratar antes de terminar. Durante la depuraciÃ³n de la biblioteca, deberÃ¡ fijarse un valor bajo a esta funciÃ³n, y en el caso contrario, esto es, en producciÃ³n, un valor elevado.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="1208">El archivo de configuraciÃ³n del sitioÂ <i>gsdlsite.cfg</i>, que se encuentra en el mismo directorio que el programaÂ <i>library</i>, establece variables utilizadas por el programa de biblioteca y el servidor Web durante la ejecuciÃ³n. En el Cuadro <CrossRef target="Table" ref="lines_in_gsdlsitecfg"/> se enumeran las lÃ­neas de este archivo cuya explicaciÃ³n aparece en la SecciÃ³n 5 de laÂ <i>GuÃ­a de InstalaciÃ³n de la Biblioteca Digital Greenstone</i>.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_a_stl">
+<Title>
+<Text id="1209">APÃNDICE A: LA BIBLIOTECA ESTÃNDAR DE PLANTILLAS C++ (<i>STL</i>)</Text>
+</Title>
+<Content>
+<Text id="1210">La Biblioteca EstÃ¡ndar de Plantillas (<i>Standard Template Library - STL</i>) es una biblioteca de cÃ³digo C++ de amplia difusiÃ³n concebida por Silicon Graphics (Â <i>www.sgi.com</i>). En el presente ApÃ©ndice se presenta un breve resumen de sus principales funciones, que se utilizan a todo lo largo del cÃ³digo Greenstone. Para una explicaciÃ³n mÃ¡s completa, consulte el manual oficial de referencia STL disponible en la siguiente direcciÃ³n Internet:Â <i>www.sgi.com</i>, o alguno de los numerosos libros sobre STL, como el de Josuttis (1999).</Text>
+<Text id="1211">Tal como lo sugiere el tÃ©rmino âplantillaâ, STL no es sÃ³lo una biblioteca de objetos lista para usar. Unida al mecanismo de plantillas de C++, proporciona a los programadores una soluciÃ³n para desarrollar de manera concisa sus propios objetos, recurriendo a las funciones algorÃ­tmicas de STL. Esto aÃ±ade un grado mÃ¡s de complejidad pero vale la pena.</Text>
+<Text id="1212">A fin de ayudar a comprender los extractos del cÃ³digo de Greenstone que figuran en el presente manual, citaremos algunos ejemplos didÃ¡cticos de utilizaciÃ³n de la STL.</Text>
+<Section id="lists">
+<Title>
+<Text id="1213">Listas (<i>Lists</i>)</Text>
+</Title>
+<Content>
+<Figure id="programming_a_list_of_integers" class="withLineNumber">
+<Title>
+<Text id="1214">ProgramaciÃ³n de una lista de nÃºmeros enteros</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>#define nil 0</CodeLine>
+<CodeLine/>
+<CodeLine>struct intlist {</CodeLine>
+<CodeLine>Â  int val; </CodeLine>
+<CodeLine>Â  struct intlist* next;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_list(intlist* head)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>Â  int total = 0;</CodeLine>
+<CodeLine>Â  intlist* curr = head;</CodeLine>
+<CodeLine>Â  while (curr!=nil)</CodeLine>
+<CodeLine>Â  {</CodeLine>
+<CodeLine>Â Â Â  total += curr-&gt;val;</CodeLine>
+<CodeLine>Â Â Â  curr = curr-&gt;next;</CodeLine>
+<CodeLine>Â  }</CodeLine>
+<CodeLine/>
+<CodeLine>Â  return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>void main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>Â  intlist node1 = { 5, nil };</CodeLine>
+<CodeLine>Â  intlist node2 = { 4, nil };</CodeLine>
+<CodeLine>Â  node2.next = &amp;node1;</CodeLine>
+<CodeLine/>
+<CodeLine>Â  int total = total_int_list(&amp;node2);</CodeLine>
+<CodeLine>Â  cout &lt;&lt; "Total de los objetos: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="1215">En primer lugar, estudiaremos dos programas que implementan una lista de nÃºmeros enteros. Uno de ellos utiliza tipos C++ bÃ¡sicas (la âmanera tradicional de procederâ), mientras que el otro utiliza STL. En la Figura <CrossRef target="Figure" ref="programming_a_list_of_integers"/> se muestra la implementaciÃ³n del cÃ³digo fuente queÂ <i>no</i>Â utiliza STL. Las lÃ­neas 5-8 definen la estructura de datos bÃ¡sica que vamos a utilizar: en el campoÂ <i>val</i>Â se almacena el valor del nÃºmero entero, yÂ <i>next</i>Â indica el siguiente elemento de la lista. Como puede advertirse se trata, en suma, de una implementaciÃ³n clÃ¡sica de una lista enlazada.</Text>
+<Text id="1216">Para ilustrar la utilizaciÃ³n de la estructura de datos, el programa principal (lÃ­neas 23-32) inicializa una lista de nÃºmeros enteros con los elementos [5, 4]. Luego activa la funciÃ³nÂ <i>total_int_list</i>Â (definida en las lÃ­neas 10-21), que tiene como Ãºnico parÃ¡metro un puntero dirigido hacia el principio de una lista y que suma los valores que Ã©sta contiene. El valor que devuelve (9 en nuestro ejemplo) aparece en la pantalla.</Text>
+<Text id="1217">Las lÃ­neas 12-18 llevan a cabo las tareas principales. Se comienza por un poco de inicializaciÃ³n: la variable localÂ <i>total</i>Â se fija en cero, yÂ <i>curr</i>Â apunta hacia el principio de la lista. A continuaciÃ³n, un bucleÂ <i>while</i>Â agrega el elemento de nÃºmero entero actual al subtotal vigente (total += curr-&gt;val;) antes de pasar al siguiente elemento (curr = curr-&gt;next;). El bucleÂ <i>while</i>Â termina cuandoÂ <i>curr</i>Â equivale aÂ <i>nil</i>Â (nada), lo que significa que no queda ningÃºn elemento por tratar.</Text>
+<Figure id="programming_a_list_of_integers_using_stl">
+<Title>
+<Text id="1218">ProgramaciÃ³n de una lista de nÃºmeros enteros mediante la STL</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine>#include &lt;list&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_list(list&lt;int&gt;* head)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>Â  int total = 0;</CodeLine>
+<CodeLine>Â  list&lt;int&gt;::iterator curr = head-&gt;begin();</CodeLine>
+<CodeLine>Â  while (curr!=head-&gt;end())</CodeLine>
+<CodeLine>Â  {</CodeLine>
+<CodeLine>Â Â Â  total += *curr;</CodeLine>
+<CodeLine>Â Â Â  curr++;</CodeLine>
+<CodeLine>Â  }</CodeLine>
+<CodeLine/>
+<CodeLine>Â  return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>void main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>Â  list&lt;int&gt; vals;</CodeLine>
+<CodeLine>Â  vals.push_back(5);</CodeLine>
+<CodeLine>Â  vals.push_back(4);</CodeLine>
+<CodeLine/>
+<CodeLine>Â  int total = total_int_list(&amp;vals);</CodeLine>
+<CodeLine>Â  cout &lt;&lt; "Total de los objetos: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="1219">En la Figura <CrossRef target="Figure" ref="programming_a_list_of_integers_using_stl"/> se muestra un programa equivalente que utiliza STL. Ya no es necesario definir una estructura de datos adecuada en el cÃ³digo, sino que basta con la directiva #include &lt;list&gt; de la lÃ­nea 2 que contiene la plantilla para la lista definida en STL. El objeto se denomina âclase Contenedorâ ya que cuando se declara una variable de este tipo se especifica tambiÃ©n el tipo que se desea que almacene. En la lÃ­nea 19 se elabora una lista de nÃºmeros enteros con la instrucciÃ³n list&lt;int&gt; vals;. Se pueden agregar elementos al objeto mediante la funciÃ³n miembroÂ <i>push_back ( )</i>, como se hace en las lÃ­neas 20-21.</Text>
+<Text id="1220">Las lÃ­neas 6-12 efectÃºan el trabajo principal. Sigue habiendo dos inicializaciones y un bucleÂ <i>while</i>, pero por lo demÃ¡s la nueva sintaxis tiene poco en comÃºn con la antigua. En esta nueva forma de tratamiento es fundamental una variable de tipoÂ <i>iterator</i>Â (lÃ­nea 7). Numerosas clases STL incluyen tiposÂ <i>iterator</i>Â para ofrecer una manera uniforme de recorrer una secuencia de objetos de contenedor. El primer elemento se devuelve conÂ <i>begin( )</i>Â y el elemento que sigue al Ãºltimo elemento se devuelve conÂ <i>end( )</i>. Se pasa al elemento siguiente mediante la operaciÃ³n de incremento ++, que es sobrecargada por la claseÂ <i>iterator</i>Â para implementar esta tarea, y se accede al valor almacenado mediante una operaciÃ³n de derreferenciaciÃ³n (Â <i>*curr</i>Â en la lÃ­nea 10) tambiÃ©n sobrecargada.</Text>
+<Text id="1221">La implementaciÃ³n STL de este programa es un poco mÃ¡s concisa que el cÃ³digo convencional (25 lÃ­neas, en lugar de 31). Las ventajas son mÃ¡s importantes en proyectos mÃ¡s voluminosos, ya que el objetoÂ <i>list</i>Â de STL tiene un potencial mayor de lo que muestra el ejemplo. Este objeto incluye, por ejemplo, una lista doblemente enlazada que admite diversas formas de inserciÃ³n y supresiÃ³n. Se requerirÃ­an tareas de programaciÃ³n suplementarias para integrar estas funciones en la versiÃ³n de lista de nÃºmeros enteros bÃ¡sica.</Text>
+<Text id="1222">ObsÃ©rvese que el parÃ¡metroÂ <i>total_int_list</i>Â de la Figura <CrossRef target="Figure" ref="programming_a_list_of_integers_using_stl"/> se ha implementado como puntero para que corresponda con el puntero utilizado enÂ <i>total_int_list</i>Â de la Figura <CrossRef target="Figure" ref="programming_a_list_of_integers"/>. En STL, suele ser mÃ¡s natural (y preferible) utilizar referencias en lugar de punteros. AsÃ­ pues, el parÃ¡metro se convierte enÂ <i>list&lt;int&gt;&amp; head</i>, y sus funciones miembro se activan con la sintaxisÂ <i>head.begin( );</i>Â y asÃ­ sucesivamente.</Text>
+</Content>
+</Section>
+<Section id="section_correspondencias_(maps)">
+<Title>
+<Text id="1223">Correspondencias (<i>Maps</i>)</Text>
+</Title>
+<Content>
+<Text id="1224">Cuando se implementa un sistema de biblioteca digital, es Ãºtil poder almacenar elementos en una matriz indizada por secuencias de texto en lugar de nÃºmeros. En Greenstone, por ejemplo, esto simplifica considerablemente el almacenamiento de los archivos de macros despuÃ©s de su lectura; lo mismo ocurre con los diversos archivos de configuraciÃ³n. El tipo de datos que permite esta clase de acceso se denominaÂ <i>matriz asociativa</i>Â y suele encontrarse en los lenguajes de programaciÃ³n modernos de alto nivel. Se lo conoce tambiÃ©n con el nombre de âÂ <i>hash array</i>Â â (matriz de desmenuzamiento, sobre todo en Perl) ya que la tÃ©cnica habitual utilizada para implementar los Ã­ndices de texto es el desmenuzamiento (eso es, calcular una suma de control).</Text>
+<Figure id="using_associative_arrays_in_stl" class="withLineNumber">
+<Title>
+<Text id="1225">UtilizaciÃ³n de matrices asociativas en STL</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine>#include &lt;map&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_table(map&lt;char*, int&gt;&amp; table)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>Â  int total = 0;</CodeLine>
+<CodeLine>Â  map&lt;char*, int&gt;::iterator curr = table.begin();</CodeLine>
+<CodeLine> Â while (curr!=table.end())</CodeLine>
+<CodeLine>Â  {</CodeLine>
+<CodeLine>Â Â Â  total += (curr-&gt;second);</CodeLine>
+<CodeLine>Â Â Â  curr++;</CodeLine>
+<CodeLine>Â  }</CodeLine>
+<CodeLine/>
+<CodeLine>  return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>int main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>Â  map&lt;char*, int&gt; table;</CodeLine>
+<CodeLine>Â  table["Alicia"] = 31;</CodeLine>
+<CodeLine>Â  table["Pedro"] = 24;</CodeLine>
+<CodeLine>Â  table["Maria"] = 47;</CodeLine>
+<CodeLine/>
+<CodeLine>Â  int total = total_int_table(table);</CodeLine>
+<CodeLine>Â  cout &lt;&lt; "Edad total: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="1226">En STL, las matrices asociativas se constituyen mediante el objetoÂ <i>map</i>Â (correspondencia). En la Figura <CrossRef target="Figure" ref="using_associative_arrays_in_stl"/> se presenta un ejemplo un tanto artificial que almacena la edad de tres personas (Alicia, Pedro y Maria) en una matriz asociativa indizada con sus nombres (lÃ­neas 19-22). El problema es escribir una funciÃ³n que calcule la edad total de todas las personas presentes, sin saber ni cuÃ¡ntas ni quiÃ©nes son. Por supuesto, se podrÃ­a resolver este problema con una matriz clÃ¡sica de nÃºmeros enteros indizados numÃ©ricamente. Este ejemplo estÃ¡ concebido para ilustrar las funciones del objetoÂ <i>map</i>Â y poner de manifiesto las semejanzas de tratamiento con el objetoÂ <i>list</i>Â acompaÃ±ado de unÂ <i>iterator</i>.</Text>
+<Text id="1227">Al igual queÂ <i>list</i>,Â <i>map</i>Â es una clase de contenedor. Sin embargo, cuando se declara una variable de este tipo, es preciso especificar dos cosas: el tipo de Ã­ndice y el tipo de elemento<FootnoteRef id="4"/>. Como se puede apreciar en la lÃ­nea 19, se obtiene una matriz asociativa que almacena nÃºmeros enteros indizados por cadenas utilizandoÂ <i>char*</i>Â (que es la manera de declarar una cadena en C++) como tipo de Ã­ndice, seguido deÂ <i>int</i>Â como tipo de elemento.</Text>
+<Text id="1228">Existen diversas maneras de almacenar elementos en la matriz asociativa. En las lÃ­neas 20-22 del ejemplo se utiliza el Ã­ndice de la matriz sobrecargada [ ] para inicializar el cuadro con la edad de las tres personas. La semejanza entreÂ <i>total_int_table</i>, que efectÃºa el cÃ¡lculo principal en el programa, yÂ <i>total_int_list</i>Â en la Figura <CrossRef target="Figure" ref="programming_a_list_of_integers"/> es notable. De hecho, estos dos objetos son casi idÃ©nticos y no es una coincidencia. STL recurre en gran medida a la herencia, de tal modo que objetos diferentes utilizan las mismas operaciones fundamentales. AsÃ­ ocurre sobre todo con losÂ <i>iterators</i>. Las pequeÃ±as diferencias entre las dos funciones consisten en que elÂ <i>iterator</i>Â procede aquÃ­ deÂ <i>map&lt;char*, int&gt;</i>, y que el acceso a sus elementos se hace con la instrucciÃ³n curr-&gt;second(); en efecto, la derreferenciaciÃ³n de la variableÂ <i>(*curr)</i>Â estÃ¡ definida para devolver un objeto de tipoÂ <i>pair</i>. Esta operaciÃ³n registra el nombre del Ã­ndice (Â <i>first</i>) y el valor del elemento (Â <i>second</i>), pero sÃ³lo nos interesa este Ãºltimo. Por lo demÃ¡s, el cÃ³digo permanece igual. La Ãºnica diferencia que persiste âel cambio del Ãºnico argumento de la funciÃ³n de puntero a referenciaâ esÂ  superficial.</Text>
+<Text id="1229">El cÃ³digo de Greenstone utiliza ampliamente otros dos tipos STL:Â <i>vector</i>Â (vector) yÂ <i>set</i>Â (conjunto). El primero facilita las matrices dinÃ¡micas y el segundo admite las operaciones matemÃ¡ticas de conjunto como la uniÃ³n, la intersecciÃ³n y la diferencia.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="bibliography">
+<Title>
+<Text id="1230">BIBLIOGRAFÃA</Text>
+</Title>
+<Content>
+<Text id="1231">Aulds, C. (2000),Â <i>Linux Apache Web Server Administration</i>, Sybex.</Text>
+<Text id="1232">Bainbridge, D., Buchanan, G., McPherson, J., Jones, S., Mahoui, A. y Witten, I.H. (2001) âGreenstone: A platform for distributed digital library developmentâ. Informe de investigaciÃ³n, Departamento de informÃ¡tica, Universidad de Waikato, Nueva Zelandia.</Text>
+<Text id="1233">Christiansen, T. Torkington, N. and Wall, L. (1998),Â <i>Perl Cookbook</i>, OÂŽReilly and Associates.</Text>
+<Text id="1234">Coar, K.A.L. (1998),Â <i>Apache Server For Dummies</i>, IDG Books.</Text>
+<Text id="1235">Deitel, H.M. y Deitel, P.J. (1994),Â <i>C++: How to Program</i>, Prentice Hall, Englewood Cliffs, Nueva Jersey.</Text>
+<Text id="1236">Dublin Core (2001) âThe Dublin Core Metadata Initiativeâ enÂ <i>http://purl.org/dc/</i>, consultado el 16 de enero de 2001. </Text>
+<Text id="1237">Josuttis, N.M. (1999)Â <i>The C++ standard library: a tutorial and reference</i>, Addison-Wesley, 1999.</Text>
+<Text id="1238">Keller, M. y Holden, G. (1999),Â <i>Apache Server for Windows Little Black Book</i>, Grupo Coriolis.</Text>
+<Text id="1239">Schwartz, R.L. y Christiansen, T. (1997),Â <i>Learning Perl</i>Â (2Âª ediciÃ³n), OÂŽReilly and Associates.</Text>
+<Text id="1240">Slama, D., Garbis, J. y Russell, P. (1999),Â <i>Enterprise CORBA</i>, Prentice Hall, Englewood Cliffs, Nueva Jersey.</Text>
+<Text id="1241">Stroustroup, B. (1997),Â <i>The C++ Programming Language</i>, Addison-Wesley.</Text>
+<Text id="1242">Thiele, H. (1997) âThe Dublin Core and Warwick Framework: A Review of the Literature, March 1995-September 1997.âÂ <i>D-Lib Magazine</i>, enero, &lt;Â <i>http://www.dlib.org/dlib/january98/01thiele.html</i>Â &gt;</Text>
+<Text id="1243">Wall, L., Christiansen, T. y Orwant, J. (2000),Â <i>Programming Perl</i>Â (3Âª ediciÃ³n), OÂŽReilly and Associates.</Text>
+<Text id="1244">Weibel, S. (1999), âThe State of the Dublin Core Metadata Initiativeâ,Â <i>D-Lib Magazine</i>, Volumen 5 NÂº 4, abril, &lt;http://www.dlib.org/dlib/april99/04weibel.html&gt;.</Text>
+<Text id="1245">Witten, I.H., Moffat, A. y Bell, T.C. (1999),Â <i>Managing gigabytes: compressing and indexing documents and images</i>, Morgan Kaufmann, San Francisco.</Text>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="1246">Es posible que al ejecutarÂ <i>setup.bat</i>Â en los sistemas Windows 95/98, aparezca el mensaje de errorÂ <i>âSin espacio en entornoâ</i>. Si ello sucede, deberÃ¡ modificar su archivo de sistemaÂ <i>config.sys</i>Â (que normalmente se encuentra enÂ <i>C:\config.sys</i>) y aÃ±adir la lÃ­neaÂ <i>shell=C:\command.com /e:4096 /p</i>Â (dondeÂ <i>C:</i>Â es la letra correspondiente a la unidad de sistema) para ampliar el tamaÃ±o de su cuadro de entorno. SerÃ¡ necesario volver a arrancar la computadora para que esta modificaciÃ³n surta efecto, y luego repetir los pasos anteriores para Greenstone.</Text>
+</Footnote>
+<Footnote id="2">
+<Text id="1247">ObsÃ©rvese que en Greenstone, las expresiones usuales se interpretan en lenguaje Perl, que difiere levemente de otras convenciones. Por ejemplo, â*â corresponde a cero o mÃ¡s apariciones del carÃ¡cter anterior, mientras que â.â corresponde a cualquier carÃ¡cter, por lo tantoÂ <i>nugget.*</i>Â corresponde a toda cadena que comienza por el prefijo ânuggetâ, seguido o no por un punto. Para insistir en la presencia de un punto serÃ­a necesario aÃ±adir un caracter de escape y escribir en su lugarÂ <i>nugget\...*</i>.</Text>
+</Footnote>
+<Footnote id="3">
+<Text id="1248"/>
+</Footnote>
+<Footnote id="4">
+<Text id="1249">El valor deÂ <i>gsdlhome</i>Â procede del archivoÂ <i>gsdlsite.cfg</i>Â ubicado en el mismo directorio que el ejecutable CGIÂ <i>library</i>, mientras queÂ <i>GSDLHOME</i>Â se activa ejecutando el guiÃ³nÂ <i>setup</i>Â que da acceso a un archivo diferente; asÃ­ pues, es posible tÃ©cnicamente que los dos valores sean diferentes, pero no es deseable. El texto que figura mÃ¡s arriba estÃ¡ escrito partiendo de la hipÃ³tesis de que ambos valores son iguales.</Text>
+</Footnote>
+<Footnote id="5">
+<Text id="1250">TÃ©cnicamente son cuatro tipos, pero los dos Ãºltimos son opcionales. Puesto que nos limitamos a una introducciÃ³n bÃ¡sica de esta clase STL, omitiremos los detalles sobre estos dos Ãºltimos tipos.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/es/Install_es.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/es/Install_es.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/es/Install_es.xml	(revision 13632)
@@ -0,0 +1,1002 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">BIBLIOTECA DIGITAL GREENSTONE</Text>
+</Heading>
+<Title>
+<Text id="2">GUÃA DE INSTALACIÃN</Text>
+</Title>
+<Author>
+<Text id="3">Ian H. Witten y Stefan Boddie</Text>
+</Author>
+<Affiliation>
+<Text id="4">Departamento de InformÃ¡tica <br/>Universidad de Waikato, Nueva Zelanda</Text>
+</Affiliation>
+<Text id="5">Greenstone es un conjunto de programas y aplicaciones de software especialmente diseÃ±ados para la creaciÃ³n y difusiÃ³n de colecciones documentales digitales, el cual le ofrece una nueva forma de organizar la informaciÃ³n y publicarla en Internet o CD-ROM. Greenstone ha sido elaborado como parte del proyecto de Biblioteca Digital de Nueva Zelanda de la Universidad de Waikato y actualmente es desarrollado y distribuido en colaboraciÃ³n con la UNESCO y la ONG Human Info. Es un software de cÃ³digo abierto disponible enÂ <i>http://greenstone.org</i>Â bajo los tÃ©rminos y condiciones de la Licencia PÃºblica General de GNU .</Text>
+<Comment>
+<Text id="6">Queremos estar seguros que este software trabaje bien para usted.Â Por favor comunÃ­quenos cualquier problema que tenga con Ã©l a la siguiente direcciÃ³n:greenstone@cs.waikato.ac.nz</Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">Marzo de 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">Acerca de este manual</Text>
+</Title>
+<Content>
+<Text id="10">En este documento se explica cÃ³mo instalar Greenstone para que usted pueda utilizarlo en su propia computadora. Se indica tambiÃ©n cÃ³mo obtener otros programas asociados disponibles gratuitamente: el servidor Web Apache y Perl. Hemos procurado que el procedimiento de instalaciÃ³n sea lo mÃ¡s sencillo posible.</Text>
+<Text id="11">El programa funciona en diferentes plataformas y con distintas configuraciones. Por consiguiente, son muchos los factores que inciden (o pueden incidir) en el procedimiento de instalaciÃ³n. En la SecciÃ³n <CrossRef target="Chapter" ref="versions_of_greenstone"/> se mencionan algunos puntos que tendrÃ¡ usted que examinar antes de instalar Greenstone. En la <CrossRef target="Chapter" ref="installation_procedure"/> se detalla el procedimiento de instalaciÃ³n para todas las distintas versiones; sÃ³lo es necesario que lea usted la parte correspondiente a su sistema operativo. La SecciÃ³n <CrossRef target="Chapter" ref="greenstone_collections"/> trata de las colecciones de demostraciÃ³n de la biblioteca digital que estÃ¡n incluidas en la distribuciÃ³n. En la SecciÃ³n <CrossRef target="Chapter" ref="setting_up_webserver"/> se explica cÃ³mo instalar servidores Web comunes, Apache y PWS/IIS de Microsoft, para que funcionen con Greenstone. En la SecciÃ³n <CrossRef target="Chapter" ref="configuring_your_site"/> se mencionan varias opciones de configuraciÃ³n de Greenstone y en la SecciÃ³n <CrossRef target="Chapter" ref="personalizing"/> se muestra cÃ³mo crear una pÃ¡gina principal personalizada para la instalaciÃ³n de su biblioteca digital. Por Ãºltimo, en el ApÃ©ndice <CrossRef target="Chapter" ref="appendix_associated_software"/> se enumeran los programas asociados y se indica cÃ³mo obtenerlos.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="12">Conjunto de documentos</Text>
+</Title>
+<Content>
+<Text id="13">La serie completa de documentos comprende cinco volÃºmenes:</Text>
+<BulletList>
+<Bullet>
+<Text id="14">La GuÃ­a de InstalaciÃ³n de la Biblioteca Digital Greenstone (<i>el presente documento</i>)</Text>
+</Bullet>
+<Bullet>
+<Text id="15">La GuÃ­a del Usuario de la Biblioteca Digital Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">La GuÃ­a del Programador de la Biblioteca Digital Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="17">La Biblioteca Digital Greenstone: del Papel a la ColecciÃ³n</Text>
+</Bullet>
+<Bullet>
+<Text id="18">La Biblioteca Digital Greenstone: uso del Organizador</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">Agradecimientos</Text>
+</Title>
+<Content>
+<Text id="20">El programa Greenstone es fruto de la colaboraciÃ³n de muchas personas. Rodger McNab y Stefan Boddie son los principales arquitectos y programadores. TambiÃ©n han contribuido David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson y Stuart Yeates. Otros miembros del proyecto Biblioteca Digital de Nueva Zelanda que proporcionaron asesorÃ­a y valiosas ideas para la concepciÃ³n del sistema son: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols y Lloyd Smith. TambiÃ©n queremos dar las gracias a todos aquellos que contribuyeron a los paquetes de programas con licencias GNU incluidos en esta distribuciÃ³n: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE y XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="versions_of_greenstone">
+<Title>
+<Text id="21">VERSIONES DE GREENSTONE</Text>
+</Title>
+<Content>
+<Text id="22">El programa Greenstone funciona en diferentes plataformas y con distintas configuraciones, como se resume en la Figura <CrossRef target="Figure" ref="different_options"/>.</Text>
+<Figure id="different_options">
+<Title>
+<Text id="23">Las distintas opciones para las versiones Windows y Unix de Greenstone</Text>
+</Title>
+<File width="642" height="295" url="images/Install_Fig_1.png"/>
+</Figure>
+<Text id="24">Hay muchos factores que inciden (o pueden incidir) en el procedimiento de instalaciÃ³n. Antes de proseguir la lectura, detÃ©ngase en los siguientes puntos:</Text>
+<BulletList>
+<Bullet>
+<Text id="25">Â¿EstÃ¡ usted utilizando Windows o Unix?</Text>
+</Bullet>
+<Bullet>
+<Text id="26">Si es Windows, Â¿estÃ¡ usted utilizando Windows 3.1/3.11 o una versiÃ³n mÃ¡s reciente? Aunque se pueden visualizar las colecciones en las mÃ¡quinas que funcionan con las versiones 3.1 Ã³ 3.11, y dar servicio a otras computadoras en la misma red, no puede usted crear nuevas colecciones. El programa Greenstone completo funciona con 95/98/Me y NT/2000.</Text>
+</Bullet>
+<Bullet>
+<Text id="27">Si es Unix, Â¿estÃ¡ usted utilizando Linux u otra versiÃ³n de Unix? Para Linux, se proporciona una versiÃ³n binaria del sistema completo que es fÃ¡cil de instalar. Para otros tipos de Unix tendrÃ¡ usted que instalar el cÃ³digo fuente y compilarlo. Para ello, puede ser preciso instalar en su computadora programas suplementarios.</Text>
+</Bullet>
+<Bullet>
+<Text id="28">Si es Windows NT/2000 o Unix, Â¿puede usted iniciar la sesiÃ³n como âadministradorâ del sistema oÂ <i>root</i>Â ? Esto puede ser necesario para configurar adecuadamente un servidor Web para Greenstone.</Text>
+</Bullet>
+<Bullet>
+<Text id="29">Â¿Quiere usted el cÃ³digo fuente? Si estÃ¡ usted utilizando Windows o Linux, puede usted instalar solamente los binarios. Pero es posible que quiera usted tambiÃ©n el cÃ³digo fuente: Ã©ste viene en la distribuciÃ³n de Greenstone.</Text>
+</Bullet>
+<Bullet>
+<Text id="30">Â¿Quiere usted crear nuevas colecciones de biblioteca digital? En tal caso, es necesario que tenga Perl, disponible gratuitamente para Windows y Unix.</Text>
+</Bullet>
+<Bullet>
+<Text id="31">Â¿Su computadora maneja un servidor Web? Greenstone viene con un servidor Web Windows. No obstante, si ya estÃ¡ usted utilizando un servidor Web, es muy posible que quiera conservarlo. Para Unix, es necesario utilizar un servidor Web.</Text>
+</Bullet>
+<Bullet>
+<Text id="32">Â¿Sabe usted como volver a configurar su servidor Web? Si usted no utiliza el servidor Web de Greenstone, tendrÃ¡ que modificar ligeramente la configuraciÃ³n del suyo para que reconozca el programa Greenstone.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Chapter>
+<Chapter id="installation_procedure">
+<Title>
+<Text id="33">EL PROCEDIMIENTO DE INSTALACIÃN</Text>
+</Title>
+<Content>
+<Text id="34">Existen sendas versiones de Greenstone disponibles para Windows y Unix, como binarios y en forma de cÃ³digo fuente. La interfaz de usuario de Greenstone utiliza cualquiera de los dos navegadores Web siguientes: Netscape Navigator o Internet Explorer (versiÃ³n 4.0 o superior en ambos casos). En caso de que no tenga usted todavÃ­a un navegador Web, puede usted instalar una de las versiones Windows de Netscape que vienen en el CD-ROM.</Text>
+<Section id="windows">
+<Title>
+<Text id="35">Windows</Text>
+</Title>
+<Content>
+<Text id="36">Si es usted un usuario de Unix, pase directamente a la SecciÃ³n 2.2. Para los usuarios de Windows, si sÃ³lo desea una instalaciÃ³n sencilla siga el siguiente procedimiento de âinstalaciÃ³n simpleâ. El sistema Greenstone ocupa unos 40 Mb de espacio de memoria en el disco duro.</Text>
+<Text id="37">Si no escoge usted la instalaciÃ³n por defecto, tendrÃ¡ que decidir si quiere instalar el cÃ³digo binario o el cÃ³digo fuente. En caso de duda, escoja el cÃ³digo binario. El procedimiento de instalaciÃ³n es el mismo para ambos. En las secciones siguientes encontrarÃ¡ usted mÃ¡s informaciÃ³n sobre las opciones ofrecidas.</Text>
+<Text id="38">Una vez terminada la instalaciÃ³n, pase directamente a la SecciÃ³n 2.3.</Text>
+<Subsection id="simple_installation">
+<Title>
+<Text id="39">InstalaciÃ³n simple</Text>
+</Title>
+<Content>
+<Text id="40">Para instalar la versiÃ³n Windows a partir del CD-ROM, inserte el disco en el lector (por ejemplo,Â <i>D:</i>). Si al cabo de unos 20 segundos el procedimiento de instalaciÃ³n no comienza automÃ¡ticamente, pulse en el menÃºÂ <i>Inicio</i>, seleccioneÂ <i>Ejecutar</i>Â y tecleeÂ <i>D:\Windows\Setup.exe</i>, donde âÂ <i>D</i>Â â es la letra que designa su lector de CD-ROM. Para Windows 3.1, seleccioneÂ <i>Ejecutar</i>Â en el âAdministrador de archivosâ y tecleeÂ <i>D:\Windows\Setup.exe</i>.</Text>
+<Text id="41">Para proceder a la instalaciÃ³n mÃ¡s simple, basta con aceptar el parÃ¡metro por defecto en cada etapa, pulsando el botÃ³nÂ <i>Next</i>Â (siguiente). Â¡Eso es todo! Greenstone queda instalado en el directorioÂ <i>C:\Program Files\gsdl</i>.</Text>
+<Text id="42">Una vez concluida la instalaciÃ³n, para arrancar su sistema Greenstone pulse el botÃ³nÂ <i>Inicio</i>, abra el menÃºÂ <i>Programas</i>Â y seleccioneÂ <i>Biblioteca Digital Greenstone (Greenstone Digital Library)</i>. Esto hace aparecer un cuadro de diÃ¡logo: haga clic enÂ <i>Entrar en la biblioteca (Enter Library)</i>. Esto activa automÃ¡ticamente el navegador Internet y carga la pÃ¡gina principal de la Biblioteca Digital Greenstone, cuyo aspecto debe ser parecido al del ejemplo de la Figura <CrossRef target="Figure" ref="your_greenstone_home_page"/>. Se entra en la colecciÃ³n de demostraciÃ³n de Greenstone pulsando en su icono.</Text>
+<Figure id="your_greenstone_home_page">
+<Title>
+<Text id="43">Su pÃ¡gina principal Greenstone</Text>
+</Title>
+<File width="642" height="527" url="images/Install_Fig_2.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="windows_binaries">
+<Title>
+<Text id="44">Binarios Windows</Text>
+</Title>
+<Content>
+<Text id="45">En el CD-ROM hay dos programas binarios Windows distintos: laÂ <i>Biblioteca Local</i>Â y laÂ <i>Biblioteca Web</i>. La instalaciÃ³n por defecto mencionada mÃ¡s arriba selecciona la versiÃ³nÂ <i>Biblioteca Local</i>. Le recomendamos encarecidamente que utilice esta versiÃ³n. La Biblioteca Web, que es mucho mÃ¡s difÃ­cil de instalar, sÃ³lo es necesaria si usted utiliza ya un servidor Web y experimenta conflictos de asignaciÃ³n de puerto al usar la Biblioteca Local. A pesar de su modesto nombre, la Biblioteca Local ofrece una capacidad completa y autÃ³noma de servidor Web.</Text>
+<Text id="46"><b>La Biblioteca Local.</b>Â Este programa permite, a cualquier computadora equipada con Windows,Â  distribuir colecciones Greenstone previamente creadas. La colecciÃ³n de demostraciÃ³n de Greenstone se instalarÃ¡ automÃ¡ticamente; se pueden instalar tambiÃ©n las demÃ¡s colecciones que figuran en el CD-ROM (vÃ©ase la SecciÃ³n <CrossRef target="Chapter" ref="greenstone_collections"/>). El programa de Biblioteca Local es el mismo utilizado en los CD-ROM producidos por el sistema Greenstone.</Text>
+<Text id="47">La Biblioteca Local estÃ¡ destinada a utilizarse en computadoras autÃ³nomas o en computadoras que aÃºn no estÃ¡n equipadas con un servidor Web. Contiene un pequeÃ±o servidor Web incorporado para que otras computadoras en la misma red puedan tambiÃ©n acceder a la biblioteca. (Sin embargo, este servidor Web tiene una capacidad de configuraciÃ³n limitada.)</Text>
+<Text id="48">El programa de Biblioteca Local detecta automÃ¡ticamente si su computadora tiene un programa de red instalado o si estÃ¡ conectada a una red. Funciona correctamente en cualquier combinaciÃ³n de estas condiciones. No obstante, pueden plantearse eventualmente dos problemas. Greenstone puede:</Text>
+<BulletList>
+<Bullet>
+<Text id="49">provocar una operaciÃ³n no deseada de marcado telefÃ³nico;</Text>
+</Bullet>
+<Bullet>
+<Text id="50">no funcionar debido a la presencia de un programa de red instalado incorrectamente.</Text>
+</Bullet>
+</BulletList>
+<Text id="51">Se suministra una versiÃ³n limitada de la Biblioteca Local que se puede utilizar en tales situaciones. La versiÃ³n limitada sÃ³lo funciona con Netscape (pero no con Internet Explorer). Cuando se activa la versiÃ³n de la Biblioteca Local de Greenstone, en el cuadro de diÃ¡logo aparece un botÃ³n que permite seleccionar la versiÃ³n limitada. Se deberÃ¡ siempre utilizar la versiÃ³n estÃ¡ndar, a menos que se planteen los problemas antes mencionados.</Text>
+<Text id="52"><b>Biblioteca Web.</b>Â Este programa permite que cualquier computadora con un servidor Web existente distribuya colecciones Greenstone previamente creadas. Como en el caso de la Biblioteca Local, la colecciÃ³n de demostraciÃ³n de Greenstone se instalarÃ¡ automÃ¡ticamente. Se pueden instalar tambiÃ©n las demÃ¡s colecciones que figuran en el CD-ROM (vÃ©ase la SecciÃ³n <CrossRef target="Chapter" ref="greenstone_collections"/>).</Text>
+<Text id="53">La Biblioteca Web difiere de la Biblioteca Local porque estÃ¡ destinada a computadoras que ya disponen de un programa de servidor Web.</Text>
+<Text id="54">Para activar la Biblioteca Web, se requiere tambiÃ©n</Text>
+<BulletList>
+<Bullet>
+<Text id="55">Un programa de servidor Web, como por ejemplo Apache (vÃ©ase el ApÃ©ndice <CrossRef target="Chapter" ref="appendix_associated_software"/>).</Text>
+</Bullet>
+</BulletList>
+<Text id="56"><b>El Colector.</b>Â Este componente, que viene tanto en la Biblioteca Local como en la Biblioteca Web, permite crear colecciones que contengan el material elegido por usted. Para activarlo, se requiere tambiÃ©n Perl. Recomendamos ActivePerl (vÃ©ase el ApÃ©ndice). (No se podrÃ¡ utilizar el Colector con un sistema Windows 3.1 Ã³ 3.11.)</Text>
+</Content>
+</Subsection>
+<Subsection id="windows_webserver_configuration">
+<Title>
+<Text id="57">ConfiguraciÃ³n del servidor Web de Windows (en las versiones de Biblioteca Web Ãºnicamente)</Text>
+</Title>
+<Content>
+<Text id="58">Una ventaja de la versiÃ³n de la Biblioteca Local de Greenstone es que estÃ¡ lista para funcionar y no requiere ninguna configuraciÃ³n especial. Para la versiÃ³n Biblioteca Web, en cambio, tendrÃ¡ usted que hacer algunos ajustes a su instalaciÃ³n del servidor Web.</Text>
+<Text id="59">Si ya dispone usted de un servidor Web, habrÃ¡ que hacer algunos pequeÃ±os cambios en su configuraciÃ³n para que la instalaciÃ³n de Greenstone funcione correctamente. El guiÃ³n (<i>script</i>) de instalaciÃ³n explica cuÃ¡les son esos cambios para el servidor Web Apache (vÃ©ase la SecciÃ³n <CrossRef target="Section" ref="pws_and_iis_webservers"/> para las instrucciones relativas a la configuraciÃ³n de los servidores Web PWS e IIS). Es posible que necesite la ayuda de un administrador de sistema para volver a configurar un servidor Web ya instalado. Esta persona entenderÃ¡ seguramente las instrucciones del guiÃ³n de instalaciÃ³n, que pueden imprimirse.</Text>
+<Text id="60">Si no dispone usted todavÃ­a de un servidor Web, tendrÃ¡ que instalar uno (vÃ©ase el ApÃ©ndice <CrossRef target="Chapter" ref="appendix_associated_software"/> para la informaciÃ³n relativa al servidor Web Apache) y luego tendrÃ¡ que configurarlo adecuadamente. En la SecciÃ³n <CrossRef target="Chapter" ref="setting_up_webserver"/> se explica detalladamente quÃ© partes de la instalaciÃ³n de un servidor Web afectan a Greenstone y cÃ³mo deben modificarse. Esto supone incluir una media docena de lÃ­neas en un archivo de configuraciÃ³n.</Text>
+</Content>
+</Subsection>
+<Subsection id="windows_source">
+<Title>
+<Text id="61">Fuente Windows</Text>
+</Title>
+<Content>
+<Text id="62">El cÃ³digo fuente de Greenstone ocupa 50 Mb en el disco, aunque para compilarlo se necesitarÃ¡n unos 90 Mb. Para compilar la fuente en Windows se necesita</Text>
+<BulletList>
+<Bullet>
+<Text id="63">El compilador Microsoft Visual C++. (Estamos resolviendo actualmente algunos problemas menores en la compilaciÃ³n de Greenstone con varios puertos Windows de GNU GCC.)</Text>
+</Bullet>
+</BulletList>
+<Text id="64">(No se necesita el GDBM, el administrador de la base de datos de GNU, porque viene incluido en la distribuciÃ³n de Greenstone.)</Text>
+<Text id="65">Es poco probable que logre usted compilar Greenstone en una computadora que funcione con un sistema Windows 3.1 Ã³ 3.11.</Text>
+<Text id="66">En caso de que usted vuelva a compilar Greenstone y desee utilizar la versiÃ³n nuevamente compilada para crear discos CD-ROM, debe tomar nota de que el cÃ³digo producido por las versiones recientes del compilador Visual C++ no funciona con Windows 3.1 Ã³ 3.11, no habiendo en cambio problema alguno con sistemas Windows ulteriores (95, 98, Me, NT, 2000). Si desea que sus CD-ROM puedan leerse en mÃ¡quinas con sistemas Windows antiguos, se necesitarÃ¡ otra versiÃ³n del compilador. AdemÃ¡s, Greenstone utiliza STL (<i>Standard Template Library</i>), la biblioteca estÃ¡ndar de plantillas para C++, y aunque esos compiladores vienen a veces con STL, la versiÃ³n proporcionada no siempre funciona correctamente. Por consiguiente, para volver a compilar Greenstone de tal modo que produzca discos CD-ROM que funcionen con versiones antiguas de Windows, se necesita:</Text>
+<BulletList>
+<Bullet>
+<Text id="67">el compilador Microsoft Visual C++, versiÃ³n 4.0 Ã³ 4.2.</Text>
+</Bullet>
+<Bullet>
+<Text id="68">una versiÃ³n externa de STL, la biblioteca estÃ¡ndar de plantillas para C++. STL viene incluida en el sistema Greenstone para poder utilizarla con esas versiones del compilador.</Text>
+</Bullet>
+</BulletList>
+<Text id="69">Cabe seÃ±alar que el procedimiento de instalaciÃ³n de Windows no propone compilar Greenstone si se escoge instalar el cÃ³digo fuente. Para obtener instrucciones sobre la compilaciÃ³n de Greenstone relativas a su plataforma y su compilador, vÃ©ase el documentoÂ <i>Install</i>Â que aparece en el directorio principal de Greenstone (<i>C:\Program Files\gsdl</i>Â por defecto) durante el procedimiento de instalaciÃ³n.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="unix">
+<Title>
+<Text id="70">Unix</Text>
+</Title>
+<Content>
+<Text id="71">Esta secciÃ³n estÃ¡ destinada a los usuarios de Unix. (Los usuarios de Windows pueden pasar directamente a la SecciÃ³n <CrossRef target="Section" ref="how_to_find_greenstone"/>.) Tiene usted que escoger entre instalar el cÃ³digo binario o el cÃ³digo fuente. El cÃ³digo binario ocupa unos 50 Mb en el disco duro; el cÃ³digo fuente necesita unos 160 Mb para compilar.</Text>
+<Subsection id="unix_binaries">
+<Title>
+<Text id="72">Binarios Unix</Text>
+</Title>
+<Content>
+<Text id="73">El cÃ³digo binario requiere una distribuciÃ³n Linux basada en Intel x86 que incluye un soporte binario ELF. Las distribuciones que cumplen estos requisitos son:</Text>
+<BulletList>
+<Bullet>
+<Text id="74">RedHat 5.1</Text>
+</Bullet>
+<Bullet>
+<Text id="75">SuSE Linux 6.1</Text>
+</Bullet>
+<Bullet>
+<Text id="76">Debian 2.1</Text>
+</Bullet>
+<Bullet>
+<Text id="77">Slackware 4.0</Text>
+</Bullet>
+</BulletList>
+<Text id="78">Deben funcionar tambiÃ©n las versiones mÃ¡s recientes de estos productos.</Text>
+<Text id="79">Se necesitarÃ¡ un servidor Web: recomendamos Apache. Le recomendamos tambiÃ©n encarecidamente que instale su servidor WebÂ <i>antes</i>Â de instalar Greenstone, esto facilitarÃ¡ considerablemente la respuesta a las preguntas que se formulan durante el procedimiento de instalaciÃ³n de Greenstone. Si desea crear nuevas colecciones de biblioteca digital, necesitarÃ¡ tambiÃ©n Perl si Ã©ste no se encuentra ya en su sistema. Para comprobarlo, abra una ventana de terminal, tecleeÂ <i>perl -v</i>, y vea si aparece un mensaje en que se especifica, entre otras cosas, el nÃºmero de la versiÃ³n. En la mayorÃ­a de las versiones de Linux, Perl viene instalado por defecto. En el ApÃ©ndice <CrossRef target="Chapter" ref="appendix_associated_software"/> se proporciona informaciÃ³n sobre cÃ³mo obtener Apache y Perl.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_source">
+<Title>
+<Text id="80">Fuente Unix</Text>
+</Title>
+<Content>
+<Text id="81">El cÃ³digo fuente para Unix es el mismo que para Windows. Se ha compilado y probado en Linux, Solaris y Macintosh OS/X; deberÃ­a resultar sencillo adaptarlo a otras variantes de Unix.</Text>
+<Text id="82">Para compilar el cÃ³digo fuente de Greenstone en Unix, se necesita</Text>
+<BulletList>
+<Bullet>
+<Text id="83">el compilador de GNU C++, GCC</Text>
+</Bullet>
+<Bullet>
+<Text id="84">el administrador de la base de datos GNU, GDBM.</Text>
+</Bullet>
+</BulletList>
+<Text id="85">Para activar el programa Greenstone, se necesita tambiÃ©n un servidor Web y el programa Perl, como se indica mÃ¡s arriba enÂ <i>Binarios Unix</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_installation">
+<Title>
+<Text id="86">InstalaciÃ³n en Unix</Text>
+</Title>
+<Content>
+<Text id="87">Para instalar la versiÃ³n destinada a Unix a partir del CD-ROM, inserte el disco en el lector y teclee</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="151">
+<CodeLine>mount /cdrom</CodeLine>
+</th>
+<th width="246">
+<Text id="88">monta el dispositivo de CD-ROM (este comando puede diferir de un sistema a otro; por ejemplo, en OS/X se tecleaÂ <i>cd</i>Â en el directorioÂ <i>/Volumes</i>Â y luego se pasa al subdirectorio correspondiente al CD-ROM)</Text>
+</th>
+</tr>
+<tr>
+<th width="151">
+<CodeLine>cd /cdrom</CodeLine>
+</th>
+<th width="246">
+<Text id="89">cambia de directorio y pasa al directorio principal del CD-ROM</Text>
+</th>
+</tr>
+<tr>
+<th width="151">
+<CodeLine>cd Unix</CodeLine>
+</th>
+<th width="246">
+<Text id="90">cambia de directorio y pasa adonde se encuentra el guiÃ³n de instalaciÃ³n para Unix</Text>
+</th>
+</tr>
+<tr>
+<th width="151">
+<CodeLine>sh Install.sh</CodeLine>
+</th>
+<th width="246">
+<Text id="91">inicia el proceso de instalaciÃ³n (se utiliza unÂ <i>sh</i>Â explÃ­cito porque muchas instalaciones prohiben la ejecuciÃ³n de programas directamente a partir del CD-ROM)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="92">Este Ãºltimo comando inicia un diÃ¡logo interactivo en que se le pregunta a usted la informaciÃ³n necesaria para instalar Greenstone en su sistema, proporcionando datos precisos sobre las operaciones efectuadas.</Text>
+<Text id="93">El procedimiento de instalaciÃ³n comienza preguntÃ¡ndole en quÃ© directorio quiere usted instalar Greenstone. El primer archivo que se instala allÃ­ es el programa de âdesinstalaciÃ³nâ que despeja toda instalaciÃ³n parcial, en caso de que se topara usted con problemas o terminara la instalaciÃ³n prematuramente. A continuaciÃ³n, usted escoge si quiere instalar los binarios o el cÃ³digo fuente. Luego se formulan algunas preguntas sobre la instalaciÃ³n de su servidor Web. Es necesario tener un directorio de CGI ejecutable vÃ¡lido (que en los sistemas Unix suele llamarse â<i>cgi-bin</i>Â â); puede usted crear uno o utilizar el existente. En caso de crear uno nuevo, serÃ¡ necesario que introduzca esta informaciÃ³n en el archivo de configuraciÃ³n de su servidor Web. En cualquier caso, es necesario introducir la direcciÃ³n Web del directorio CGI. El diÃ¡logo de instalaciÃ³n lo guiarÃ¡ a travÃ©s de todas estas opciones. Es importante establecer correctamente los permisos de archivo en determinados directorios, y se le invita a proporcionar la informaciÃ³n necesaria. Por Ãºltimo, se le invita a escoger una clave de acceso para el usuario âadministradorâÂ <i>admin</i>.</Text>
+<Text id="94">Todo el programa Greenstone se instala por defecto en el directorioÂ <i>/usr/local/gsdl</i>Â si es el usuarioÂ <i>root</i>Â quien efectÃºa la instalaciÃ³n, y de otro modo en el directorioÂ <i>~/gsdl</i>Â (en que â~â es el directorio principal del usuario).</Text>
+<Text id="95">La instalaciÃ³n de los binarios tarda apenas unos minutos, tiempo suficiente para que usted responda a las preguntas correspondientes. Si usted instala el cÃ³digo fuente, el guiÃ³n de instalaciÃ³n lo compilarÃ¡, lo cual lleva entre diez minutos y una hora, segÃºn la velocidad de su procesador.</Text>
+<Text id="96">Para desinstalar el programa, teclee</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<Text id="97">o bien /usr/local/gsdl si quien instalÃ³ Greenstone fue el usuarioÂ <i>root</i></Text>
+<CodeLine>sh Uni nstall.sh</CodeLine>
+<Text id="98">Durante el procedimiento de instalaciÃ³n se le preguntarÃ¡ si quiere usted instalar alguna colecciÃ³n Greenstone. La colecciÃ³n de demostraciÃ³n Greenstone se instala automÃ¡ticamente; las demÃ¡s colecciones que figuran en el CD-ROM se describen en la SecciÃ³n <CrossRef target="Chapter" ref="greenstone_collections"/>.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_webserver_configuration">
+<Title>
+<Text id="99">ConfiguraciÃ³n del servidor Web para Unix</Text>
+</Title>
+<Content>
+<Text id="100">Si ya dispone usted de un servidor Web, tendrÃ¡ que hacerle algunos pequeÃ±os cambios en su configuraciÃ³n para poder instalar Greenstone. El guiÃ³n de instalaciÃ³n explica en quÃ© consisten. Es probable que necesite la ayuda del administrador del sistema para volver a configurar el servidor Web; esta persona comprenderÃ¡ seguramente las instrucciones que figuran en el guiÃ³n de instalaciÃ³n y que pueden imprimirse. Para su conveniencia, la informaciÃ³n imprimible del guiÃ³n de instalaciÃ³n estÃ¡ escrita en un archivo llamadoÂ <i>INSTALL_RECORD</i>Â situado en el directorio en que usted instalÃ³ Greenstone.</Text>
+<Text id="101">Si no dispone usted todavÃ­a de un servidor Web, tendrÃ¡ que instalar uno. En el ApÃ©ndice <CrossRef target="Chapter" ref="appendix_associated_software"/> se proporciona informaciÃ³n sobre Apache. DespuÃ©s tendrÃ¡ que configurarlo adecuadamente. En la SecciÃ³n <CrossRef target="Chapter" ref="setting_up_webserver"/> se explica detalladamente quÃ© partes de la instalaciÃ³n de un servidor Web Apache afectan a Greenstone y cÃ³mo hay que modificarlas. Ello supone incluir una media docena de lÃ­neas en un archivo de configuraciÃ³n.</Text>
+<Text id="102">No es necesario que sea usted el usuario â<i>root</i>Â â de Unix para ejecutar el procedimiento de instalaciÃ³n antes expuesto. Sin embargo, tratÃ¡ndose de la configuraciÃ³n de un servidor Apache, serÃ¡ preciso disponer de privilegios de â<i>root</i>Â â, todo depende de cÃ³mo se instale Apache. Si instala Apache usted mismo, puede hacerlo como un usuario carente de privilegios de â<i>root</i>Â â. Si resulta necesario eludir un administrador de sistema poco dispuesto a cooperar, es posible instalar en su computadora un segundo servidor Web Apache, aun si ya existe uno.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="how_to_find_greenstone">
+<Title>
+<Text id="103">CÃ³mo encontrar Greenstone</Text>
+</Title>
+<Content>
+<Subsection id="local_library_windows_only">
+<Title>
+<Text id="104">Biblioteca Local (sÃ³lo con Windows)</Text>
+</Title>
+<Content>
+<Text id="105">Si estÃ¡ utilizando la Biblioteca Local, ejecute simplemente el programa Greenstone a partir del menÃº deÂ <i>Inicio</i>. Esto activa automÃ¡ticamente su navegador Internet y carga la pÃ¡gina principal de la Biblioteca Digital Greenstone. A partir de esta pÃ¡gina se podrÃ¡ tener acceso a la colecciÃ³n de demostraciÃ³n de Greenstone. </Text>
+</Content>
+</Subsection>
+<Subsection id="web_library_windows_and_unix">
+<Title>
+<Text id="106">Biblioteca Web (Windows y Unix)</Text>
+</Title>
+<Content>
+<Text id="107">Si estÃ¡ utilizando la Biblioteca Web, una vez instalado el programa y configurado el servidor Web, utilice esta URL para entrar en su sistema Greenstone:</Text>
+<Text id="108"><i>http://localhost/gsdl/cgi-bin/library</i></Text>
+<Text id="109">A partir de esta pÃ¡gina se podrÃ¡ tener acceso a la colecciÃ³n de demostraciÃ³n de Greenstone.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_collector">
+<Title>
+<Text id="110">El Colector</Text>
+</Title>
+<Content>
+<Text id="111">En la pÃ¡gina principal de la biblioteca digital figura un enlace hacia el Colector.</Text>
+</Content>
+</Subsection>
+<Subsection id="administration">
+<Title>
+<Text id="112">AdministraciÃ³n</Text>
+</Title>
+<Content>
+<Text id="113">En la pÃ¡gina principal de la biblioteca digital figura un enlace hacia las pÃ¡ginas de AdministraciÃ³n. El usuario âadministradorâ se llamaÂ <i>admin</i>, con una clave de acceso que usted escogiÃ³ durante el proceso de instalaciÃ³n. El administrador estÃ¡ autorizado a aÃ±adir nuevos usuarios y a crear colecciones.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="section_la_interfaz_de_bibliotecario_de_greenstone_(gli)">
+<Title>
+<Text id="114">La Interfaz de Bibliotecario de Greenstone (GLI)</Text>
+</Title>
+<Content>
+<Text id="115">La Interfaz de Bibliotecario de Greenstone (GLI por sus siglas en inglÃ©s) es una herramienta grÃ¡fica que le ayuda a construir bibliotecas digitales dÃ¡ndole acceso a todas las funciones de Greenstone por medio de una interfaz fÃ¡cil de usar con la que sÃ³lo tiene que apuntar y hacer click.</Text>
+<Text id="116">GLI se instala automÃ¡ticamente con todas las versiones de Greenstone en el subdirectorioÂ <i>gli</i>Â del directorio principal de la biblioteca digital (<i>C:\Program Files\gsdl\gli</i>Â por omisiÃ³n). Recuerde que la interfaz corre en conjunto con los programas de Greenstone y no funcionarÃ¡ adecuadamente a menos que se encuentre en un subdirectorio de Greenstone. Si usted ya bajÃ³ alguna de las versiones de Greenstone, entonces Ã©ste serÃ¡ el caso.</Text>
+<Text id="117">Para poder usar la GLI su computadora deberÃ¡ contar con el Ambiente de EjecuciÃ³n Java. Si todavÃ­a no lo tiene, el programa de instalaciÃ³n se ofrecerÃ¡ a instalar la versiÃ³n que estÃ© incluida en el CD-ROM. En el caso de UNIX tambiÃ©n deberÃ¡ asegurarse de que Perl estÃ© instalado (en el caso de Windows Perl ya viene incluido en el software Greenstone). Por favor infÃ³rmenos sobre cualquier problema que tenga al correr o usar la Interfaz de Bibliotecario a la siguiente direcciÃ³n:Â <u>greenstone@cs.waikato.ac.nz</u>.</Text>
+<Subsection id="running_under_windows">
+<Title>
+<Text id="118">EjecuciÃ³n bajo Windows</Text>
+</Title>
+<Content>
+<Text id="119">Para correr la GLI bajo Windows explore la carpetaÂ <i>gli</i>Â que se encuentra en su instalaciÃ³n de Greenstone (por ejemplo usando el Explorador de Windows) y haga doble click en el archivoÂ <i>gli.bat</i>. Este archivo verificarÃ¡ que Greenstone, el Ambiente de EjecuciÃ³n Java y Perl estÃ¡n instalados e iniciarÃ¡ la Interfaz de Bibliotecario.</Text>
+</Content>
+</Subsection>
+<Subsection id="running_under_unix">
+<Title>
+<Text id="120">EjecuciÃ³n bajo UNIX</Text>
+</Title>
+<Content>
+<Text id="121">Para correr la GLI bajo UNIX cambie al directorioÂ <i>gli</i>Â que se encuentra en su instalaciÃ³n de Greenstone y ejecute el guiÃ³nÂ <i>gli.sh</i>. Este guiÃ³n verificarÃ¡ que Greenstone, el Ambiente de EjecuciÃ³n Java y Perl estÃ©n instalados y en su ruta de bÃºsqueda e iniciarÃ¡ la Interfaz de Bibliotecario.</Text>
+</Content>
+</Subsection>
+<Subsection id="getting_help">
+<Title>
+<Text id="122">CÃ³mo obtener ayuda</Text>
+</Title>
+<Content>
+<Text id="123">La Interfaz de Bibliotecario de Greenstone cuenta con una extensa variedad de opciones de ayuda en lÃ­nea. Usted puede obtenerla haciendo click en el botÃ³nÂ <i>Ayuda</i>Â que se encuentra en la parte superior derecha de la pantalla. Esto abrirÃ¡ una secciÃ³n relacionada con lo que usted estÃ© haciendo, es decir, con el panel GLI en el que usted se encuentre en ese momento. Una vez abierta haga click en la parte del texto de ayuda sobre la que usted quiera saber mÃ¡s. Ãsela. Â¡Se la recomendamos!</Text>
+</Content>
+</Subsection>
+<Subsection id="compiling_gli">
+<Title>
+<Text id="124">Compilando la Interfaz de Bibliotecario de Greenstone</Text>
+</Title>
+<Content>
+<Text id="125">Si usted bajÃ³ la versiÃ³n con el cÃ³digo fuente de Greenstone, entonces tendrÃ¡ con usted el cÃ³digo fuente Java de la Interfaz de Bibliotecario. Para compilarlo su computadora necesitarÃ¡ contar con una versiÃ³n adecuada del Kit de Desarrollo de Software Java. En el ApÃ©ndice <CrossRef target="Chapter" ref="appendix_associated_software"/> usted encontrarÃ¡ mayor informaciÃ³n sobre la forma de obtenerla. Para compilar el cÃ³digo fuente ejecute los archivosÂ <i>makegli.bat</i>Â (Windows) oÂ <i>makegli.sh</i>Â (UNIX). Una vez que haya hecho esto usted podrÃ¡ correr la GLI tal como se describe arriba.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="testing_and_troubleshooting">
+<Title>
+<Text id="126">Pruebas y soluciÃ³n de problemas</Text>
+</Title>
+<Content>
+<Text id="127">Para probar Greenstone, dirija su navegador Web hacia la pÃ¡gina principal de Greenstone y explore la colecciÃ³n de demostraciÃ³n y cualquier otra colecciÃ³n que haya usted instalado. No se preocupe, no va a romper nada. Pulse libremente: se puede hacer clic en la mayorÃ­a de las imÃ¡genes que aparecen en la pantalla. Si se mantiene el cursor quieto sobre una imagen, en la mayorÃ­a de los navegadores aparece un mensaje en que se explica lo que sucederÃ¡ si se hace clic. Â¡Experimente y verÃ¡! Elija palabras comunes como â<i>the</i>Â â (el) y â<i>and</i>Â â (y) para ejercitarse en la bÃºsqueda y no tema, que nada se va a romper. Para mÃ¡s informaciÃ³n, vÃ©ase laÂ <i>GuÃ­a del Usuario de la Biblioteca Digital Greenstone</i>.</Text>
+<Subsection id="troubleshooting">
+<Title>
+<Text id="128">SoluciÃ³n de problemas</Text>
+</Title>
+<Content>
+<Table id="table_troubleshooting">
+<Title/>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="129">Problema</Text>
+</th>
+<th width="246">
+<Text id="130">SoluciÃ³n posible</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="131">Biblioteca local (sÃ³lo con Windows)</Text>
+</th>
+<th width="151">
+<Text id="132">Cuando arranco el programa Greenstone mi computadora me invita a conectarme a mi proveedor de servicio Internet. </Text>
+</th>
+<th width="246">
+<Text id="133">Pulse el botÃ³nÂ <i>Cancelar</i>Â en el cuadro de diÃ¡logo. Esto suele resolver el problema.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="134">Cuando arranco el programa Greenstone mi computadora meÂ <i>sigue invitando</i>Â a conectarme a mi proveedor de servicio Internet.</Text>
+</th>
+<th width="246">
+<Text id="135">Escoja la âversiÃ³n limitadaâ cuando active Greenstone. Esta versiÃ³n sÃ³lo funciona con Netscape.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="136">Cuando dirijo mi navegador hacia la Biblioteca Digital, no puede encontrar esa pÃ¡gina.</Text>
+</th>
+<th width="246">
+<Text id="137">Verifique su configuraciÃ³n de Internet Proxy y desconecte los proxies (utiliceÂ <i>Edit preferences</i>Â en Netscape oÂ <i>Internet options</i>Â en Explorer).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="138">Â¡El Colector parece estar funcionando muy lentamente!</Text>
+</th>
+<th width="246">
+<Text id="139">Â¿EstÃ¡ usted utilizando Netscape con Windows 2000? En ese caso, intente utilizar mÃ¡s bien Internet Explorer. Parece haber cierta incompatibilidad entre Netscape y Windows 2000.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="142">Biblioteca Web (Windows y Unix)</Text>
+</th>
+<th width="151">
+<Text id="143">Cuando arranco Apache, se cierra de inmediato.</Text>
+</th>
+<th width="246">
+<Text id="144">AÃ±ada en el archivo de configuraciÃ³n de Apache una directivaÂ <i>ServerName localhost</i>Â (vÃ©ase SecciÃ³n <CrossRef target="Section" ref="apache_web_server"/>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">Â </th>
+<th width="151">
+<Text id="145">Cuando dirijo mi navegador a la biblioteca digital, aparece un archivo binario.</Text>
+</th>
+<th width="246">
+<Text id="146">Verifique la directivaÂ <i>ScriptAlias</i>Â en el archivo de configuraciÃ³n de Apache y cerciÃ³rese de que aparece antes de la directivaÂ <i>Alias</i>Â (vÃ©ase Secciones 4.2 y 4.3).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">Â </th>
+<th width="151">
+<Text id="147">Logro llegar a la pÃ¡gina principal de Greenstone (Figura <CrossRef target="Figure" ref="your_greenstone_home_page"/>), pero el icono de la colecciÃ³n de demostraciÃ³n no aparece.</Text>
+</th>
+<th width="246">
+<Text id="148">Abra el programaÂ <i>library</i>Â (en el directorioÂ <i>cgi-bin</i>) a partir del indicador de DOS (o del âshellâ) para obtener informaciÃ³n sobre depuraciÃ³n que le ayudarÃ¡ a localizar el problema.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="149">Ambas versiones</Text>
+</th>
+<th>
+<Text id="150">Cuando dirijo mi navegador hacia la Biblioteca Digital, no puede encontrar esa pÃ¡gina.</Text>
+</th>
+<th>
+<Text id="151">Intente utilizar 127.0.0.1 en lugar deÂ <i>localhost</i>. Este nÃºmero IP reservado se define como un âbucle de retrocesoâ hacia su computadora local.</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="152">Mi navegador se queja de que no puede encontrarÂ <i>main.cfg</i>.</Text>
+</th>
+<th>
+<Text id="153">Verifique que los archivos de Greenstone existen y que son legibles por todos. Si estÃ¡ usando la biblioteca Web, intente activar el programaÂ <i>library</i>Â a partir de la lÃ­nea de comandos. Si funciona bien, el problema es con los permisos de archivo (vÃ©ase la SecciÃ³n <CrossRef target="Section" ref="file_permissions"/>). En caso contrario, es probable que la variableÂ <i>gsdlhome</i>Â estÃ© configurada incorrectamente en el archivo de configuraciÃ³nÂ <i>gsdlsite.cfg</i>Â (vÃ©ase la SecciÃ³n <CrossRef target="Section" ref="gsdlsite_configuration_file"/>).</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="154">Tengo problemas con la utilizaciÃ³n del Colector.</Text>
+</th>
+<th>
+<Text id="155">Lea la GuÃ­a del Usuario de la Biblioteca Digital Greenstone, SecciÃ³n <CrossRef external="User" lang="es" target="Chapter" ref="making_greenstone_collections"/>.</Text>
+</th>
+</tr>
+<tr>
+<th>Â </th>
+<th>
+<Text id="156">He aÃ±adido un nuevo usuario, pero no parece poder iniciar la sesiÃ³n.</Text>
+</th>
+<th>
+<Text id="157">Verifique que el directorioÂ <i>C:\Program Files\gsdl\etc</i>Â y todo su contenido son modificables (vÃ©ase SecciÃ³n <CrossRef target="Section" ref="file_permissions"/>).</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="learn_more">
+<Title>
+<Text id="158">Para obtener mÃ¡s informaciÃ³n</Text>
+</Title>
+<Content>
+<Text id="159">Para obtener mÃ¡s informaciÃ³n sobre los entresijos de su instalaciÃ³n Greenstone, consulte laÂ <i>GuÃ­a del Programador de la Biblioteca Digital Greenstone</i>, que comprende, entre otras cosas, los detalles sobre la estructura de los directorios que se ha creado e informaciÃ³n sobre cÃ³mo configurar su sitio Greenstone.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="greenstone_collections">
+<Title>
+<Text id="160">COLECCIONES GREENSTONE</Text>
+</Title>
+<Content>
+<Text id="161">El CD-ROM incluye varias colecciones Greenstone de muestra. Si usted tiene acceso a Internet tambiÃ©n podrÃ¡ bajar muchas otras desde el sitio Web del Proyecto de Biblioteca Digital de Nueva Zelanda (<i>nzdl.org</i>), ya sea armadas previamente o sin armar.</Text>
+<Text id="162">La colecciÃ³n de muestra Greenstone es un pequeÃ±o subconjunto de la Biblioteca para el Desarrollo Humano (HDL por sus siglas en inglÃ©s), una colecciÃ³n perfectamente acabada que muestra la forma en que se puede lograr una amplia capacidad de exploraciÃ³n y bÃºsqueda (siempre que se cuente con los metadatos adecuados). Esta colecciÃ³n se incluye automÃ¡ticamente al momento de instalar el software.</Text>
+<Text id="163">Greenstone tambiÃ©n incluye otros ejemplos de colecciones documentadas cuyas pÃ¡ginas informativas describen la forma en que estÃ¡n construidas, demostrando las diferentes capacidades de Greenstone. Un cuadro de diÃ¡logo le preguntarÃ¡ si quiere incluirlas junto con su instalaciÃ³n. La cantidad aproximada de espacio de disco que se necesita para cada una se muestra a continuaciÃ³n.</Text>
+<Table class="hidden" id="table_collections">
+<Title/>
+<TableContent>
+<tr>
+<th>
+<Text id="164"><i>demo</i></Text>
+</th>
+<th>
+<Text id="165">ColecciÃ³n de muestra GreenstoneÂ <br/>(7Â Mb)</Text>
+</th>
+<th>
+<Text id="166">Un pequeÃ±o subconjunto de la Biblioteca para el Desarrollo Humano (HDL por sus siglas en inglÃ©s). Si se clona esta colecciÃ³n las funciones completas sÃ³lo estarÃ¡n disponibles si sus nuevos archivos proporcionan la informaciÃ³n de metadatos apropiada.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="167"><i>dls-e</i></Text>
+</th>
+<th>
+<Text id="168">Subconjunto de la Biblioteca para el DesarrolloÂ <br/>(150 Mb)</Text>
+</th>
+<th>
+<Text id="169">Al igual que la ColecciÃ³n de muestra Greenstone, Ã©sta es un subconjunto de la Biblioteca para el Desarrollo Humano, sÃ³lo que mucho mayor. Contiene 250 publicaciones entre libros, informes y revistas relacionadas con diferentes Ã¡reas del saber humano (la HDL contiene un total de 1,230 publicaciones). Tiene la misma estructura que la ColecciÃ³n de muestra Greenstone y es bastante compleja, por lo que si apenas estÃ¡ empezando a familiarizarse con su uso quizÃ¡ sea mejor que se fije primero en alguna otra (p. ej. laÂ <i>demostraciÃ³n en MSWord y PDF</i>, losÂ <i>Archivos Greenstone</i>Â o laÂ <i>colecciÃ³n de ImÃ¡genes Sencillas</i>).</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="170"><i>wrdpdf-e</i></Text>
+</th>
+<th>
+<Text id="171">DemostraciÃ³n en MSWord y PDFÂ <br/>(4 Mb)</Text>
+</th>
+<th>
+<Text id="172">Esta colecciÃ³n contiene unos cuantos documentos en formatos PDF, MSWord, RTF y PostScript, y muestra la capacidad de construir colecciones a partir de diferentes tipos de documentos. El archivo de configuraciÃ³n de la colecciÃ³n es sumamente sencillo.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="173"><i>gsarch-e</i></Text>
+</th>
+<th>
+<Text id="174">ColecciÃ³n de Archivos GreenstoneÂ <br/>(5 Mb)</Text>
+</th>
+<th>
+<Text id="175">Una colecciÃ³n de mensajes de correo electrÃ³nico hecha a partir de los archivos de las listas de correo de Greenstone. Utiliza el pluginÂ <i>Email</i>Â que descompone y analiza los archivos en formatos de correo electrÃ³nico. El archivo de configuraciÃ³n de la colecciÃ³n es sumamente sencillo.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="176"><i>cltbib-e</i></Text>
+</th>
+<th>
+<Text id="177">ColecciÃ³n bibliogrÃ¡ficaÂ <br/>(7 Mb)</Text>
+</th>
+<th>
+<Text id="178">Con aproximadamente 4,000 entradas bibliogrÃ¡ficas, esta colecciÃ³n incorpora una interfase de bÃºsqueda basada en formas que permite la bÃºsqueda por campos. Es bastante compleja.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="179"><i>cltext-e</i></Text>
+</th>
+<th>
+<Text id="180">Suplemento bibliogrÃ¡ficoÂ <br/>(1 Mb)</Text>
+</th>
+<th>
+<Text id="181">Esta pequeÃ±a colecciÃ³n de 10 entradas bibliogrÃ¡ficas ilustra el programa âsupercolecciÃ³nâ de Greenstone, el cual busca en varias colecciones al mismo tiempo. Opera junto con la colecciÃ³nÂ <i>BibliogrÃ¡fica</i>Â y su archivo de configuraciÃ³n es casi idÃ©ntico.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="182"><i>MARC-e</i></Text>
+</th>
+<th>
+<Text id="183">ColecciÃ³n de muestra MARCÂ <br/>(1 Mb)</Text>
+</th>
+<th>
+<Text id="184">Basada en algunos registros MARC de la Biblioteca del Congreso, Ã©sta es una colecciÃ³n sencilla, aunque no permite la bÃºsqueda basada en formas.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="185"><i>oai-e</i></Text>
+</th>
+<th>
+<Text id="186">ColecciÃ³n de muestra OAIÂ <br/>(18 Mb)</Text>
+</th>
+<th>
+<Text id="187">Por medio del Protocolo de Archivo Abierto y la funciÃ³nÂ <i>Import-From</i>, Ã©sta recupera metadatos de un archivo y construye una colecciÃ³n a partir de los registros. En este caso se trata de imÃ¡genes, por lo que se utilizan tanto el plugin OAI como el pluginÂ <i>ImagePlug</i>.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="188"><i>image-e</i></Text>
+</th>
+<th>
+<Text id="189">ColecciÃ³n de imÃ¡genes sencillasÂ <br/>(1 Mb)</Text>
+</th>
+<th>
+<Text id="190">Esta colecciÃ³n de imÃ¡genes es sumamente bÃ¡sica y no contiene texto ni metadatos explÃ­citos, lo que mÃ¡s bien la hace poco prÃ¡ctica. El archivo de configuraciÃ³n es lo mÃ¡s simple que se puede encontrar.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="191"><i>authen-e</i></Text>
+</th>
+<th>
+<Text id="192">DemostraciÃ³n de formateo y autenticaciÃ³nÂ <br/>(8 Mb)</Text>
+</th>
+<th>
+<Text id="193">Con el mismo material que la colecciÃ³n de muestra Greenstone original, Ã©sta muestra dos funciones independientes: el formateo de documentos que no sean estÃ¡ndar y el acceso controlado a los documentos por medio de la autenticaciÃ³n de los usuarios.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="194"><i>garish</i></Text>
+</th>
+<th>
+<Text id="195">VersiÃ³n Garish de la colecciÃ³n de muestraÂ <br/>(8 Mb)</Text>
+</th>
+<th>
+<Text id="196">Esta colecciÃ³n tambiÃ©n contiene el mismo material que la colecciÃ³n de muestra Greenstone, sÃ³lo que su apariencia ha sido alterada para mostrar la forma en que las pÃ¡ginas generadas pueden configurarse de manera diferente. Se basa en un archivo de macros no estÃ¡ndar que se proporciona junto con Greenstone.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="197"><i>Isis-e</i></Text>
+</th>
+<th>
+<Text id="198">ColecciÃ³n de muestra CDS/ISIS (1 Mb)</Text>
+</th>
+<th>
+<Text id="199">Esta colecciÃ³n estÃ¡ construida a partir de una base de datos CDS/ISIS de cerca de 150 referencias bibliogrÃ¡ficas. Usa el plugin ISISPlug, el cual lee archivos estÃ¡ndar ISIS (.mst y .fdt) y los convierte a metadatos de Greenstone.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<Chapter id="setting_up_webserver">
+<Title>
+<Text id="200">InstalaciÃ³n del servidor Web</Text>
+</Title>
+<Content>
+<Text id="201">En esta secciÃ³n explicaremos cÃ³mo instalar su servidor Web para que funcione con Greenstone. Cabe seÃ±alar que estas explicaciones son innecesarias cuando se utiliza la Biblioteca Local Windows, ya que este programa estÃ¡ concebido para funcionar de entrada sin servidor Web.</Text>
+<Text id="202">Nos referiremos al servidor Web Apache, que se puede conseguir libremente para Windows y Unix (vÃ©ase el ApÃ©ndice <CrossRef target="Chapter" ref="appendix_associated_software"/> para mÃ¡s detalles), el Personal Web Server (PWS) y el servidor Web Internet Information Services (IIS) de Microsoft. El PWS es el servidor Microsoft estÃ¡ndar para Windows 95/98; el IIS es el de las versiones 2000 y XP de Windows; Windows NT puede utilizar cualquiera de los dos. Las explicaciones relativas a Apache se aplican igualmente a la biblioteca Web Windows y a las versiones de Unix (aunque utilizamos la terminologÃ­a y los nombres de las rutas de acceso propios de Windows); la secciÃ³n relativa a PWS/IIS sÃ³lo se aplica a la biblioteca Web Windows.</Text>
+<Text id="203">Una vez instalado el servidor Web, el siguiente paso es instalar Greenstone. Supondremos que durante el procedimiento de instalaciÃ³n usted ha escogido la opciÃ³n por defecto en cada fase pulsando el botÃ³nÂ <i>Next</i>Â (siguiente). El resultado es la creaciÃ³n del directorioÂ <i>C:\Program Files\gsdl</i>, donde se instala el binario de la biblioteca Web, junto con algunos archivos auxiliares.</Text>
+<Text id="204">Todos los servidores Web utilizan la URL especial âlocalhostâ que representa la computadora en que estÃ¡ funcionando el servidor Web. AsÃ­, cuando se instala un servidor Web, se puede acceder a los documentos HTML tecleando la URLÂ <i>http://localhost</i>Â en un navegador. Si su computadora tiene instalado un nombre de dominio, Ã©ste se utiliza en lugar delÂ <i>localhost</i>Â para poder identificar su computadora desde sitios remotos. En la computadora de la Biblioteca Digital de Nueva Zelanda, por ejemplo, las URLÂ <i>http://nzdl.org</i>Â yÂ <i>http://localhost</i>Â son equivalentes. Si usted tecleaÂ <i>http://nzdl.org</i>Â en su computadora obtendrÃ¡ el servidor Web de la Biblioteca Digital de Nueva Zelanda, mientras que si tecleaÂ <i>http://localhost</i>Â obtendrÃ¡ el servidor Web de su propia computadora.</Text>
+<Section id="apache_web_server">
+<Title>
+<Text id="205">El servidor Web Apache</Text>
+</Title>
+<Content>
+<Text id="206">El servidor Web Apache suele instalarse enÂ <i>C:\Program Files\Apache Group\Apache</i>Â y se configura de tal modo que el directorioÂ <i>cgi-bin</i>Â estÃ© en el subdirectorioÂ <i>\cgi-bin</i>Â y la raÃ­z de documentos es el subdirectorioÂ <i>\htdocs</i>. Se vuelve a configurar modificando el archivo de configuraciÃ³n enÂ <i>C:\Program Files\Apache Group\Apache\conf\httpd.conf</i>. Se trata de un archivo de texto: es muy fÃ¡cil leerlo para ver cÃ³mo se ha efectuado la configuraciÃ³n.</Text>
+<Text id="207">SegÃºn cÃ³mo estÃ© configurado el programa de conexiÃ³n en red de su computadora, podrÃ¡ ser necesario aÃ±adir la siguiente lÃ­nea en su archivo de configuraciÃ³nÂ <i>httpd.conf</i>Â de Apache:</Text>
+<CodeLine>ServerNameÂ  localhost</CodeLine>
+<Text id="208">Si esta lÃ­nea no figura, el sistema intenta encontrar el nombre de su servidor. Sin embargo, en algunas versiones de Windows hay algunos errores que impiden esta operaciÃ³n. En tal caso, Apache se cierra inmediatamente despuÃ©s de arrancarlo. Aparece un mensaje de error, pero Ã©ste se borra de inmediato y es muy probable que usted no lo alcance a leer.</Text>
+<Subsection id="setting_up_cgi-bin_directory">
+<Title>
+<Text id="209">InstalaciÃ³n del directorioÂ <i>cgi-bin</i>Â de Greenstone</Text>
+</Title>
+<Content>
+<Text id="210"><i>cgi-bin</i>Â es un directorio desde el cual el servidor Web trata documentos como programas ejecutables. La directivaÂ <i>ScriptAlias</i>Â de Apache se utiliza para crear un directorioÂ <i>cgi-bin</i>. Cabe seÃ±alar que esta directiva puede hacer de cualquier directorio un directorio CGI ejecutable, Â¡sin que se llame forzosamente âcgi-binâ! A la inversa, un directorio llamado âcgi-binâ no tiene nada especial si no se le ha aplicado la directivaÂ <i>ScriptAlias</i>.</Text>
+<Text id="211">Una vez instalado, Apache tiene un directorio cgi-bin en C:\Program Files\Apache Group\Apache\cgi-bin. Esto significa que si se le presenta la URL <i>http://localhost/cgi-bin/hello</i>, el servidor Web intentarÃ¡ ejecutar un archivo llamado hello en el directorio antes mencionado.</Text>
+<Text id="212">Hay un programa Greenstone, llamado â<i>library.exe</i>Â â, que tiene que ser ejecutado por el servidor Web y que a su vez lee un archivo llamado el archivo de configuraciÃ³n de sitio de Greenstone, o â<i>gsdlsite.cfg</i>Â â, que debe estar situado en el mismo directorio.</Text>
+<Text id="213">La mejor manera de obtener este resultado es utilizar la directivaÂ <i>ScriptAlias</i>Â de Apache para crear un nuevo directorioÂ <i>cgi-bin</i>. Este es el pasaje del archivo de configuraciÃ³nÂ <i>httpd.conf</i>Â de Apache que aÃ±adeÂ <i>C:\Program Files\gsdl\cgi-bin</i>Â como un directorioÂ <i>cgi-bin</i>Â suplementario:</Text>
+<CodeLine>ScriptAlias /gsdl/cgi-bin/ âC:/Program Files/gsdl/cgi-binâ</CodeLine>
+<CodeLine>&lt;Directory C:/Program Files/gsdl/cgi-bin&gt;</CodeLine>
+<CodeLine>Â  Options None</CodeLine>
+<CodeLine>Â  AllowOverride None</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="214">(Curiosamente, los archivos de configuraciÃ³n de Apache utilizan barras oblicuas hacia adelante en lugar de las barras oblicuas hacia atrÃ¡s que se suelen utilizar en Windows.)</Text>
+<Text id="215">Esto significa que el servidor Web buscarÃ¡ en el directorioÂ <i>C:\Program Files\gsdl\cgi-bin</i>Â cualquier URL que tenga la formaÂ <i>http://localhost/gsdl/cgi-bin</i>... y la ejecutarÃ¡. Por ejemplo, si se le presenta la URLÂ <i>http://localhost/gsdl/cgi-bin/hello</i>, el servidor Web intentarÃ¡ recuperar el archivoÂ <i>C:\Program Files\gsdl\cgi-bin\hello</i>Â y ejecutarlo. Sin embargo, la URLÂ <i>http://localhost/cgi-bin/hello</i>Â busca en el directorioÂ <i>cgi-bin</i>Â normal de Apache el archivoÂ <i>C:\Program Files\Apache Group\Apache\cgi-bin\hello</i>Â y lo ejecuta, tal como lo hizo antes.</Text>
+</Content>
+</Subsection>
+<Subsection id="document_root_directory">
+<Title>
+<Text id="216">El directorio raÃ­z de los documentos</Text>
+</Title>
+<Content>
+<Text id="217">El directorio raÃ­z de los documentos es la raÃ­z de la estructura de directorios de su servidor Web. Una vez instalado, Apache dispone como raÃ­z de documentos deÂ <i>C:\Program Files\Apache Group\Apache\htdocs</i>. Esto significa que si se le presenta la URLÂ <i>http://localhost/hello.html</i>, el servidor Web intentarÃ¡ recuperar un archivo llamadoÂ <i>hello.html</i>Â desde dentro del directorio antes mencionado.</Text>
+<Text id="218">Greenstone contiene varios archivos que el servidor Web tiene que leer. La manera mÃ¡s sencilla de proceder es utilizando la directivaÂ <i>Alias</i>, que es comoÂ <i>ScriptAlias</i>Â salvo que se aplica a las pÃ¡ginas Web ordinarias, no a los guiones CGI. Inserte las siguientes lÃ­neas en su archivo de configuraciÃ³n Apache, despuÃ©s de la directivaÂ <i>ScriptAlias</i>, a fin de aÃ±adirÂ <i>C:\Program Files\gsdl</i>Â como lugar suplementario donde buscar documentos.</Text>
+<CodeLine>Alias /gsdl/Â  âC:/Program Files/gsdl/â</CodeLine>
+<CodeLine>&lt;Directory C:/Program Files/gsdl&gt;</CodeLine>
+<CodeLine>Â  Options Indexes MultiViews FollowSymLinks</CodeLine>
+<CodeLine>Â  AllowOverride None</CodeLine>
+<CodeLine>Â  Order allow, deny</CodeLine>
+<CodeLine>Â  Allow from all</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="219">Esto significa que cualquier URL que se ajuste al primer argumento de la directivaÂ <i>Alias</i>Â (gsdl) se busca como archivo en el lugar correspondiente al segundo argumento. Dicho de otro modo, las URL con la formaÂ <i>http://localhost/gsdl/...</i>Â se buscarÃ¡n como archivos en el directorioÂ <i>C:\Program Files\gsdl</i>. Por ejemplo, si se le presenta la URLÂ <i>http://localhost/gsdl/hello.html</i>, el servidor Web intentarÃ¡ recuperar el archivoÂ <i>C:\Program Files\gsdl\hello.html</i>. Sin embargo, la URLÂ <i>http://localhost/hello.html</i>Â busca el archivoÂ <i>C:\Program Files\Apache Group\Apache\htdocs\hello.html</i>Â en el directorioÂ <i>htdocs</i>Â normal, tal como lo hizo antes.</Text>
+<Text id="220">AsegÃºrese de aÃ±adir la directivaÂ <i>Alias</i>Â despuÃ©s de la directivaÂ <i>ScriptAlias</i>. Si se le da la instrucciÃ³n a Apache de aÃ±adir el aliasÂ <i>/gsdl</i>Â antes deÂ <i>/gsdl/cgi-bin</i>Â se harÃ­a corresponder la URLÂ <i>/gsdl/cgi-bin/library</i>Â con la directivaÂ <i>Alias</i>Â y no con la directivaÂ <i>ScriptAlias</i>, lo cual se interpretarÃ­a como una solicitud de un documento y no como el resultado de la ejecuciÃ³n de un programa. La consecuencia serÃ­a que se âvisualizarÃ­aâ el archivo del programa binario como una pÃ¡gina en el servidor Web, en vez de ejecutarlo.</Text>
+</Content>
+</Subsection>
+<Subsection id="security">
+<Title>
+<Text id="221">Seguridad</Text>
+</Title>
+<Content>
+<Text id="222">Debe usted saber que si la versiÃ³n de biblioteca Web de Greenstone se instala como se indica mÃ¡s arriba, cualquier persona podrÃ¡ descargar cualquier archivo en la estructura de directoriosÂ <i>gsdl</i>. Esto comprende los archivos de Ã­ndice y los documentos fuente de cualquiera de las colecciones que haya usted creado, la base de datos del usuario, los registros de utilizaciÃ³n, etc.</Text>
+<Text id="223">Para evitar esto, puede usted reforzar fÃ¡cilmente las medidas de seguridad modificando la configuraciÃ³n de su servidor Web. En el caso del servidor Web Apache, sustituya las lÃ­neas en el archivo de configuraciÃ³n indicadas en el apartado anterior por las siguientes:</Text>
+<CodeLine>Alias /gsdl/Â  âC:/Program Files/gsdl/â</CodeLine>
+<CodeLine>&lt;Directory C:/Program Files/gsdl&gt;</CodeLine>
+<CodeLine>Â  Order allow, deny</CodeLine>
+<CodeLine>Â  Deny from all</CodeLine>
+<CodeLine>Â  &lt;FilesMatch â\.(gif|jpe?g|png|css|mov|mpeg|ps|pdf|doc|rtf|jar|class)$â&gt;</CodeLine>
+<CodeLine>Â Â Â Â  Order allow, deny</CodeLine>
+<CodeLine>Â Â Â Â  Allow from all</CodeLine>
+<CodeLine>Â  &lt;/FilesMatch&gt;</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="224">Esto significa que sÃ³lo se podrÃ¡n descargar los archivos cuyas extensiones se ajustan a la expresiÃ³n regular indicada en la lÃ­neaÂ <i>FilesMatch</i>.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="pws_and_iis_webservers">
+<Title>
+<Text id="225">Los servidores Web PWS e IIS</Text>
+</Title>
+<Content>
+<Text id="226">Aunque ni el PWS ni el IIS estÃ¡n instalados por defecto en los actuales sistemas Windows, Ã©stos se pueden instalar fÃ¡cilmente usando el icono âAgregar o quitar programasâ del panel de control. Si no estÃ¡n ya en su CD-ROM de Windows, tendrÃ¡ que descargarlos del sitio Web de Microsoft (<i>www.microsoft.com</i>).</Text>
+<Text id="227">El procedimiento de instalaciÃ³n de Greenstone es idÃ©ntico para el PWS y el IIS. Abra el Administrador Personal de Web y sigas las instrucciones siguientes:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="228">SeleccioneÂ <i>Avanzadas</i>Â para llegar a la pantallaÂ <i>Opciones avanzadas</i></Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="229">SeleccioneÂ <i>Inicio</i>Â y pulseÂ <i>AÃ±adir</i>Rellene los campos del modo siguiente:</Text>
+<Text id="230">CampoÂ <i>Directorio</i>Â :Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>C:\Program Files\gsdl</i></Text>
+<Text id="231">CampoÂ <i>Alias</i>Â :Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>gsdl</i></Text>
+<Text id="232">Permisos de acceso:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>Read</i></Text>
+<Text id="233">Permisos de aplicaciones:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>None</i></Text>
+<Text id="234">PulseÂ <i>OK</i></Text>
+<Text id="235">Esto hace que los archivos Greenstone sean accesibles para el servidor Web.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="236">Regrese aÂ <i>Opciones avanzadas</i>, seleccioneÂ <i>gsdl</i>Â y pulseÂ <i>AÃ±adir</i>Rellene los campos del modo siguiente:</Text>
+<Text id="237">Campo Directorio:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  C:\Program Files\gsdl\cgi-bin</Text>
+<Text id="238">Campo Alias:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  cgi-bin</Text>
+<Text id="239">Permisos de acceso:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  None</Text>
+<Text id="240">Permisos de aplicaciones:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Execute</Text>
+<Text id="241">Pulse OK</Text>
+<Text id="242">Esto permite que el servidor Web ejecute el programa de GreenstoneÂ <i>library.exe</i></Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="243">Vaya a la URL http://localhost/cgi-bin/library.exe.</Text>
+<Text id="244">Nota: con el PWS y el IIS se debe especificar la extensiÃ³n de archivoÂ <i>.exe</i></Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="configuring_your_site">
+<Title>
+<Text id="245">CONFIGURACIÃN DE SU SITIO</Text>
+</Title>
+<Content>
+<Text id="246">Para que Greenstone funcione correctamente, se deben instalar adecuadamente los permisos de acceso para determinados archivos. Asimismo, cada sitio Greenstone tiene un archivo de configuraciÃ³n asociado. El procedimiento de instalaciÃ³n crea una configuraciÃ³n genÃ©rica basada en las opciones de instalaciÃ³n escogidas por usted; no obstante, su contenido puede personalizarse para hacer frente a distintas situaciones. En esta secciÃ³n se explican ambas cosas.</Text>
+<Section id="file_permissions">
+<Title>
+<Text id="247">Permisos de archivo</Text>
+</Title>
+<Content>
+<Text id="248">Esta secciÃ³n no ataÃ±e a los usuarios de Windows 95/98, ya que esos sistemas no identifican a los propietarios de los archivos.</Text>
+<Text id="249">En Windows NT, 2000 y en los sistemas Unix, los guiones CGI no funcionan como usuarios normales, ya que no se puede identificar a los usuarios en la Web. En cambio, se ejecutan en nombre del usuario que arrancÃ³ el programa del servidor Web (en los sistemas Windows), o de un usuario especial (que en los sistemas Unix suele llamarseÂ <i>nobody</i>). Debido a esto, todos los archivos y directorios dentro deÂ <i>C:\Program Files\gsdl</i>Â deben ser legibles por todos (o al menos legibles por el usuario de guiones CGI, que puede ser âÂ <i>nobody</i>Â â). Para comprobar si los permisos de archivo estÃ¡n configurados correctamente, ejecute el programaÂ <i>library.exe</i>Â a partir de la lÃ­nea de comando. Si los archivos estÃ¡n en los lugares correctos pero los permisos estÃ¡n mal configurados, el programa arrancarÃ¡ desde la lÃ­nea de comando âesto es, cuandoÂ <i>usted</i>Â la ejecuta- pero no desde un navegador âesto es, cuando el usuario âÂ <i>nobody</i>Â â la ejecuta. Otra prueba es iniciar la sesiÃ³n como otro usuario para ver si los permisos de archivo corresponden especÃ­ficamente a su cuenta de usuario original.</Text>
+<Text id="250">Para funcionar desde un navegador Web, todos los directorios de Greenstone deben ser legibles por todos. Asimismo, el directorioÂ <i>C:\Program Files\gsdl\etc</i>Â y todo su contenido deben serÂ <i>modificables</i>Â por cualquier persona. Ãste es el directorio en el que el programa de biblioteca escribe el registro de uso, los registros de error y de inicializaciÃ³n y varias bases de datos del usuario. Si no desea usted que cualquier persona pueda modificar este directorio, puede establecer permisos para que el usuario de CGI sÃ³lo pueda modificar los archivosÂ <i>errout.txt, initout.txt, key.db, users.db, history.db</i>Â yÂ <i>usage.txt</i>.</Text>
+<Text id="251">Si los permisos de archivo no estÃ¡n configurados correctamente paraÂ <i>C:\Program Files\gsdl\etc</i>, es posible que no funcione la autenticaciÃ³n de usuario y el historial de bÃºsqueda, y que no se genere un registro de uso (Â <i>usage.txt</i>).</Text>
+</Content>
+</Section>
+<Section id="gsdlsite_configuration_file">
+<Title>
+<Text id="252">El archivo de configuraciÃ³nÂ <i>gsdlsite.cfg</i></Text>
+</Title>
+<Content>
+<Text id="253">El procedimiento de instalaciÃ³n crea un archivo de configuraciÃ³n de sitio genÃ©rico de Greenstone basado en las opciones de instalaciÃ³n que usted ha escogido. Para nuestra instalaciÃ³n este archivo esÂ <i>C:\Program Files\gsdl\cgi-bin\gsdlsite.cfg</i>Â y su contenido es el siguiente:</Text>
+<CodeLine># Site configuration file por Greenstone.</CodeLine>
+<CodeLine># Lines begining with</CodeLine>
+<CodeLine># are comments.</CodeLine>
+<CodeLine># This file should be placed in the same directory as your library</CodeLine>
+<CodeLine># executable file. It should be edited to suit your site.</CodeLine>
+<CodeLine># points to the GSDLHOME directory</CodeLine>
+<CodeLine>gsdlhomeÂ Â Â Â Â  âC:/Program Files/gsdlâ</CodeLine>
+<CodeLine># this is the http address of GSDLHOME</CodeLine>
+<CodeLine># if your webservers DocumentRoot is set to $GSDLHOME</CodeLine>
+<CodeLine># then httpprefix can be commented out</CodeLine>
+<CodeLine>httpprefixÂ Â Â  /gsdl</CodeLine>
+<CodeLine># this is the http address of the directory which</CodeLine>
+<CodeLine># contains the image for the interface.</CodeLine>
+<CodeLine>httpimgÂ Â Â Â Â Â  /gsdl/images</CodeLine>
+<CodeLine># should contain the http address of this cgi script. This</CodeLine>
+<CodeLine># is not needed if the http server sets the environment variable</CodeLine>
+<CodeLine># SCRIPT_NAME</CodeLine>
+<CodeLine>#gwcgiÂ Â Â Â Â Â Â  /cgi-bin/library</CodeLine>
+<CodeLine># maxrequests is the most requests a fastcgi process</CodeLine>
+<CodeLine># will serve before it exits. This can be set to a</CodeLine>
+<CodeLine># low figure (like 1) while debugging and then set</CodeLine>
+<CodeLine># to a high figure (like 10000) when everything is</CodeLine>
+<CodeLine># working well.</CodeLine>
+<CodeLine>#maxrequests 10000</CodeLine>
+<Text id="254">Puede usted personalizar su instalaciÃ³n modificando este archivo, aunque es muy probable que no tenga que hacerlo.</Text>
+<Text id="255">La lÃ­neaÂ <i>gsdlhome</i>Â seÃ±ala simplemente hacia el directorioÂ <i>C:\Program Files\gsdl</i>.</Text>
+<Text id="256"><i>httpprefix</i>Â es la direcciÃ³n Web del directorio en que Greenstone estÃ¡ instalado. Explicamos antes cÃ³mo crear un alias de tal modo que las URL con la formaÂ <i>http://localhost/gsdl/...</i>Â se busquen en el directorioÂ <i>C:\Program Files\gsdl</i>. AÃ±adiendo una lÃ­neaÂ <i>httpprefix /gsdl</i>Â en el archivo de configuraciÃ³nÂ <i>gsdlsite.cfg</i>Â se establece la misma convenciÃ³n para el programa Greenstone.</Text>
+<Text id="257"><i>httpimg</i>Â es la direcciÃ³n Web del directorioÂ <i>C:\Program Files\gsdl|images</i>, que contiene todas las imÃ¡genes en formato GIF utilizadas en la interfaz. En cualquier instalaciÃ³n estÃ¡ndar de Greenstone Ã©ste serÃ¡ siempreÂ <i>httpprefix/images</i>, y no se toca la lÃ­nea correspondiente en el archivo antes indicado.</Text>
+<Text id="258"><i>gwcgi</i>Â es la direcciÃ³n Web del programa CGI de la biblioteca. La mayorÃ­a de los servidores Web (incluido Apache) no la necesitan y debe permanecer marcado como comentario, por lo tanto inactiva. No se debe quitar la marca de comentario a menos de estar seguro de que es necesario, pues eso puede traer problemas.</Text>
+<Text id="259"><i>maxrequests</i>Â sÃ³lo es utilizado por las versiones de Greenstone que se compilaron con la opciÃ³n âfast-cgiâ. La distribuciÃ³n binaria estÃ¡ndar no comprende esta opciÃ³n porque no todos los servidores Web estÃ¡n configurados para admitirla. La opciÃ³n âfast-cgiâ acelera las ejecuciones de los guiones CGI manteniendo en memoria el ejecutable principal entre dos utilizaciones del programa, en vez de cargarlo a partir del disco cada vez que el programa Greenstone solicita una pÃ¡gina Web. Se debe conseguir un equilibrio con la cantidad de memoria utilizada, que puede aumentar mientras mÃ¡s tiempo permanezca el programa en memoria. Una vez generadas las pÃ¡ginasÂ <i>maxrequests</i>, el programa CGI se cierra, liberando asÃ­ el espacio de memoria ocupado. Para responder a la siguiente solicitud de pÃ¡gina Web, el programa CGI se lee de nuevo a partir del disco duro y se inicia un nuevo ciclo de solicitudes de pÃ¡gina. La mayorÃ­a de las instalaciones utilizan el protocolo CGI estÃ¡ndar, lo que significa que el parÃ¡metroÂ <i>maxrequests</i>Â puede ser ignorado sin problema.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="personalizing">
+<Title>
+<Text id="260">PERSONALIZACIÃN DE SU INSTALACIÃN</Text>
+</Title>
+<Content>
+<Text id="261">Es probable que lo primero que usted quiera hacer una vez que Greenstone estÃ© instalado y en funcionamiento es personalizar la pÃ¡gina principal. El archivo que genera la pÃ¡gina principal de Greenstone se llamaÂ Â <i>home.dm</i>Â y estÃ¡ situado en el subdirectorio deÂ <i>macros</i>Â del directorio en el que usted instalÃ³ Greenstone. (El directorio por defecto para los sistemas Windows esÂ <i>C:\Program Files\gsdl</i>.) Se trata de un archivo de texto sin formato que tendrÃ¡ usted que modificar para crear una nueva pÃ¡gina principal. En vez de modificarla, le recomendamos que cree un nuevo archivo, por ejemploÂ <i>yourhome.dm</i>. Ãste serÃ¡ semejante aÂ <i>home.dm</i>,Â <i/>Â pero definirÃ¡ el âÂ <i>package home</i>Â â âque es la parte que efectÃºa el trabajo efectivo- de un modo distinto.</Text>
+<Text id="262">Al crear una pÃ¡gina principal diferente, hay que poder vincularla a las pÃ¡ginas de la biblioteca digital para que usted pueda efectuar bÃºsquedas y consultar las colecciones en su sistema. La soluciÃ³n adoptada por Greenstone es utilizar âmacrosâ. Por esa razÃ³n, el archivo de la pÃ¡gina principal tiene por sufijo âÂ <i>.dm</i>Â â y no âÂ <i>.html</i>Â â: es un archivo âmacroâ y no un archivo HTML ordinario. Pero no se preocupe: el archivo macro sÃ³lo contiene bÃ¡sicamente el HTML, acompaÃ±ado de unos cuantos ensalmos mÃ¡gicos que se explican mÃ¡s abajo. El lenguaje macro es una funciÃ³n potente y sÃ³lo se describe una pequeÃ±a parte de ella mÃ¡s abajo. VÃ©ase laÂ <i>GuÃ­a del Programador de la Biblioteca Digital Greenstone</i>Â para obtener mÃ¡s informaciÃ³n al respecto.</Text>
+<Section id="example">
+<Title>
+<Text id="263">Ejemplo</Text>
+</Title>
+<Content>
+<Figure id="your_own_greenstone_home_page">
+<Title>
+<Text id="264">Su propia pÃ¡gina principal Greenstone</Text>
+</Title>
+<File width="630" height="412" url="images/Install_Fig_3.png"/>
+</Figure>
+<Text id="265">En la Figura <CrossRef target="Figure" ref="your_own_greenstone_home_page"/> se muestra un ejemplo de una nueva pÃ¡gina principal de la biblioteca digital. Cada uno de los enlaces âÂ <i>Presione aquÃ­</i>Â â lo lleva a la funciÃ³n de Greenstone apropiada. Esta pÃ¡gina se produjo mediante un archivo llamadoÂ <i>yourhome.dm</i>Â que se muestra en la Figura <CrossRef target="Figure" ref="yourhome_dm"/>.</Text>
+<Figure id="yourhome_dm">
+<Title>
+<Text id="266"><i>yourhome.dm</i>Â utilizado para crear la Figura <CrossRef target="Figure" ref="your_own_greenstone_home_page"/></Text>
+</Title>
+<CodeLine>package home</CodeLine>
+<CodeLine>_content_ {</CodeLine>
+<CodeLine>&lt;h2&gt;Su propia pÃ¡gina principal para Greenstone&lt;/h2&gt;</CodeLine>
+<CodeLine>&lt;ul&gt;</CodeLine>
+<CodeLine>&lt;table&gt;</CodeLine>
+<CodeLine>&lt;tr valign=top&gt;&lt;td&gt;PÃ¡gina de bÃºsqueda para la colecciÃ³n demo&lt;br&gt;&lt;/td&gt;</CodeLine>
+<CodeLine>Â Â  Â &lt;td&gt;&lt;a href="_httpquery_&amp;c=demo"&gt;Presione aquÃ­&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;PÃ¡gina Â«sobreÂ» para la colecciÃ³n demo&lt;/td&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;td&gt;&lt;a href="_httppageabout_&amp;c=demo"&gt;Presione aquÃ­&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;PÃ¡gina de preferencias para la colecciÃ³n demo&lt;/td&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;td&gt;&lt;a href="_httppagepref_&amp;c=demo"&gt;Presione aquÃ­&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;PÃ¡gina principal&lt;/td&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;td&gt;&lt;a href="_httppagehome_"&gt;Presione aquÃ­&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;PÃ¡gina de ayuda&lt;/td&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;td&gt;&lt;a href="_httppagehelp_"&gt;Presione aquÃ­&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;PÃ¡gina de administraciÃ³n&lt;/td&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;td&gt;&lt;a href="_httppagestatus_"&gt;Presione aquÃ­&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;El Colector&lt;/td&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;td&gt;&lt;a href="_httppagecollector_"&gt;Presione aquÃ­&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;/table&gt;</CodeLine>
+<CodeLine>&lt;/ul&gt;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine># if you hate the squirly green bar down the left-hand side of the page,</CodeLine>
+<CodeLine># uncomment these lines:</CodeLine>
+<CodeLine># _header_ {</CodeLine>
+<CodeLine># }</CodeLine>
+</Figure>
+<Text id="267">Puede usted utilizar la Figura <CrossRef target="Figure" ref="yourhome_dm"/> como plantilla para crear su propia pÃ¡gina principal de Greenstone personalizada. BÃ¡sicamente, define una macro llamadoÂ <i>content</i>. Entre llaves hay un HTML ordinario. Puede usted insertar texto suplementario, asÃ­ como cualquiera de los comandos de formato HTML, para introducir el contenido que usted quiera ver en la pÃ¡gina. El texto es HTML normal; si lo desea, puede incluir hypervÃ­nculos y utilizar todas las demÃ¡s funciones que ofrece HTML.</Text>
+<Text id="268">Para vincular su nueva pÃ¡gina principal con otras pÃ¡ginas de la biblioteca digital, debe usted hacer uso de un conjuro mÃ¡gico adecuado. En este lenguaje macro, los conjuros mÃ¡gicos son palabras flanqueadas por signos de subrayado, como se puede ver en la Figura <CrossRef target="Figure" ref="yourhome_dm"/>. Por ejemplo,Â <i>_httppagehome_</i>Â lo lleva a la pÃ¡gina principal,Â <i>_httppagehelp_</i>Â a la pÃ¡gina de ayuda, y asÃ­ sucesivamente. En algunos casos es necesario incluir un nombre de colecciÃ³n. Por ejemplo,Â <i>_httpquery_&amp;c=demo</i>Â especifica la pÃ¡gina de bÃºsqueda de la colecciÃ³n de demostraciÃ³n; para otras colecciones se debe reemplazarÂ <i>demo</i>Â por el nombre de la colecciÃ³n correspondiente.</Text>
+<Text id="269">La definiciÃ³n de la macro llamadaÂ <i>_content_</i>Â es HTML simple. Cualquier cÃ³digo HTML estÃ¡ndar puede colocarse dentro de una definiciÃ³n de macro. Sin embargo, los caracteres especiales â{â, â}â, â\â y â_â deben ser precedidos de una barra inversa para evitar que sean procesados por el intÃ©rprete del lenguaje macro.</Text>
+<Text id="270">ObsÃ©rvese que la definiciÃ³n de la macroÂ <i>_content_</i>Â no contiene ningÃºn encabezado o pie de pÃ¡gina HTML. Si desea usted cambiar el encabezado o el pie de su pÃ¡gina principal, debe definir macrosÂ <i>_header_</i>Â y/oÂ <i>_footer_</i>, aÃ±adiÃ©ndolas a su archivoÂ <i>yourhome.dm</i>Â de la siguiente forma:</Text>
+<CodeLine>_macroname_ {</CodeLine>
+<CodeLine>...</CodeLine>
+<CodeLine>}</CodeLine>
+<Text id="271">Por ejemplo, la barra verde ondulada que aparece en el lado izquierdo de las pÃ¡ginas de Greenstone estÃ¡ definida en la macroÂ <i>_header_</i>Â y al anular esta macro se la harÃ¡ desaparecer, como se indica al final de la Figura <CrossRef target="Figure" ref="yourhome_dm"/>.</Text>
+</Content>
+</Section>
+<Section id="how_to_make_it_work">
+<Title>
+<Text id="272">CÃ³mo hacer que funcione</Text>
+</Title>
+<Content>
+<Text id="273">Hay que indicar a Greenstone que se ha creado una nueva pÃ¡gina principalÂ <i>yourhome.dm</i>. El sistema lee en los archivos macro especificados en el archivo de configuraciÃ³n principalÂ <i>main.cfg</i>Â y, por lo tanto, si usted crea uno nuevo debe incluirlo allÃ­. Los conflictos de nombres se manejan con el siguiente criterio: la definiciÃ³n mÃ¡s reciente tiene prioridad sobre las demÃ¡s.</Text>
+<Text id="274">Por consiguiente, para que el programa Greenstone de biblioteca digital utilice la pÃ¡gina principal de la Figura <CrossRef target="Figure" ref="your_own_greenstone_home_page"/> en vez de la instalada por defecto, primero ponga el archivoÂ <i>yourhome.dm</i>Â de la Figura <CrossRef target="Figure" ref="yourhome_dm"/> en el directorio deÂ <i>macros</i>. Luego modifique el archivo de configuraciÃ³nÂ <i>main.cfg</i>Â para reemplazarÂ <i>home.dm</i>Â porÂ <i>yourhome.dm</i>Â en la lista de archivos macro que se cargan al inicio.</Text>
+</Content>
+</Section>
+<Section id="redirecting_a_url_to_greenstone">
+<Title>
+<Text id="275">Reenviar una URL a Greenstone</Text>
+</Title>
+<Content>
+<Text id="276">Es posible que desee usted reenviar una URL mÃ¡s apropiada a su programa CGI de Greenstone. Por ejemplo, en nuestro sistema la URLÂ <i>http://nzdl.org</i>Â (que es la abreviatura deÂ <i>http://nzdl.org/index.html</i>) se reenvÃ­a aÂ <i>http://nzdl.org/cgi-bin/library</i>. El servidor Web Apache efectÃºa esto mediante la directivaÂ <i>Redirect</i>. Como las demÃ¡s directivas, Ã©sta va al archivo de configuraciÃ³nÂ <i>C:\Program Files\Apache Group\Apache\conf\httpd.conf</i>. Para reenviar la URLhttp://www.servidor.comahttp://www.servidor.com/cgi-bin/library, aÃ±ada la lÃ­nea siguiente enÂ <i>httpd.conf</i>Â :</Text>
+<CodeLine>Redirect /index.html http://www.servidor.com/cgi-bin/library</CodeLine>
+<Text id="277">AsÃ­ llegarÃ¡ usted a su sistema de biblioteca digital directamente desde la URLÂ <i>http://www.servidor.com</i>. En cambio, si usted deseara reenviar una URL comoÂ <i>http://www.servidor.com/greenstone</i>Â aÂ <i>http://www.servidor.com/cgi-bin/library,</i>Â introduzca en el archivoÂ <i>httpd.conf</i>Â la lÃ­nea siguiente:</Text>
+<CodeLine>Redirect /greenstone http://www.servidor.com/cgi-bin/library</CodeLine>
+<Text id="278">Si su computadora carece de nombre de dominio (como el âwww.servidor.comâ mencionado mÃ¡s arriba), basta con reemplazarÂ <i>www.servidor.com</i>Â porÂ <i>localhost</i>Â en las lÃ­neas que figuran mÃ¡s arriba. Mientras el navegador estÃ© funcionando en la misma mÃ¡quina que el servidor Web âlo cual es seguramente el caso si su computadora no tiene un nombre de dominio- esto tiene el mismo efecto que los reenvÃ­os antes mencionados.</Text>
+<Text id="279">En lugar de introducir las directivas de reenvÃ­o en el archivoÂ <i>httpd.conf</i>,Â  puede usted ponerlas en un archivo llamadoÂ <i>.htaccess</i>Â dentro del directorio raÃ­z de los documentos de su servidor. De hecho, esta soluciÃ³n tiene dos ventajas. En primer lugar, las modificaciones efectuadas en el archivoÂ <i>.htaccess</i>Â surten efecto de inmediato, mientras que es necesario volver a arrancar el servidor Web Apache para ver los efectos de los cambios en el archivoÂ <i>httpd.conf</i>. En segundo lugar, en los sistemas Unix suele ser necesario iniciar la sesiÃ³n como el usuario âÂ <i>root</i>Â â para poder modificar el archivoÂ <i>httpd.conf</i>, mientras que no lo es para modificar el archivoÂ <i>.htaccess</i>.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_associated_software">
+<Title>
+<Text id="280">APÃNDICE: PROGRAMAS ASOCIADOS</Text>
+</Title>
+<Content>
+<Text id="281">A continuaciÃ³n se explica cÃ³mo conseguir los paquetes de programas mencionados en este documento.</Text>
+<Section id="apache_webserver">
+<Title>
+<Text id="282">Servidor Web Apache</Text>
+</Title>
+<Content>
+<Text id="283">Para hacer funcionar cualquier versiÃ³n de Greenstone aparte de la versiÃ³n de Biblioteca Local de Windows, se necesita un servidor Web externo. Muchas instalaciones, en particular las mÃ¡s voluminosas, tendrÃ¡n ya un servidor Web. Si usted utiliza Linux, Apache puede encontrarse en su disco de instalaciÃ³n pero puede no haber sido seleccionado durante el procedimiento de instalaciÃ³n. El servidor Web Apache deÂ <i>www.apache.org</i>Â es libre y fÃ¡cil de instalar.</Text>
+</Content>
+</Section>
+<Section id="perl">
+<Title>
+<Text id="284">Perl</Text>
+</Title>
+<Content>
+<Text id="285">Para crear colecciones con Greenstone se necesita el lenguaje Perl, versiÃ³n 5 o superior. Para Windows, recomendamos ActivePerl deÂ <i>www.activestate.com</i>. La mayorÃ­a de los sistemas Unix ya tienen Perl instalado, pero si no es el caso, los cÃ³digos fuente y los binarios de una amplia gama de plataformas Unix pueden descargarse libremente enÂ <i>www.perl.com</i>.</Text>
+</Content>
+</Section>
+<Section id="gcc">
+<Title>
+<Text id="286">GCC</Text>
+</Title>
+<Content>
+<Text id="287">La versiÃ³n Unix de Greenstone se compila con el compilador C++ de GNU, GCC. Greenstone hace un amplio uso de la biblioteca estÃ¡ndar de plantillas C++ (hemos observado que estÃ¡ rota en algunas antiguas versiones de GCC, sÃ­rvase avisarnos si tiene usted problemas con STL). Cabe seÃ±alar que esta versiÃ³n de Greenstone no compila con la versiÃ³n 3.0 de GCC.</Text>
+</Content>
+</Section>
+<Section id="gdbm">
+<Title>
+<Text id="288">GDBM</Text>
+</Title>
+<Content>
+<Text id="289">Todas las versiones de Greenstone utilizan el Administrador de Base de Datos GNU, GDBM (GNU Database Manager). Viene con todas las versiones Windows de Greenstone y se instala automÃ¡ticamente durante el procedimiento de instalaciÃ³n. Los sistemas Linux ya tienen GDBM, por lo que no lo proporcionamos para Linux. La mayorÃ­a de los demÃ¡s sistemas Unix lo tienen, pero si es necesario puede usted descargarlo en la URLÂ <i>www.gnu.org</i>.</Text>
+</Content>
+</Section>
+<Section id="java_runtime_environment">
+<Title>
+<Text id="290">Ambiente de EjecuciÃ³n Java</Text>
+</Title>
+<Content>
+<Text id="291">Para poder usar la Interfaz de Bibliotecario de Greenstone es necesario contar con una versiÃ³n adecuada del Ambiente de EjecuciÃ³n Java (JRE por sus siglas en inglÃ©s). Si todavÃ­a no lo tiene, el CD-ROM incluye una versiÃ³n apropiada, o tambiÃ©n puede bajar la versiÃ³n mÃ¡s reciente desdeÂ <u>http://java.sun.com/j2se/downloads.html</u>. Se requiere la versiÃ³n 1.4.0 o superior.</Text>
+</Content>
+</Section>
+<Section id="java_compiler">
+<Title>
+<Text id="292">Compilador Java</Text>
+</Title>
+<Content>
+<Text id="293">Para compilar el cÃ³digo fuente de la Interfaz de Bibliotecario de Greenstone primero deberÃ¡ instalar un Kit de Desarrollo de Software Java (SDK por sus siglas en inglÃ©s). Usted puede bajar el Kit de Desarrollo de Software J2SE desdeÂ <u>http://java.sun.com/j2se/downloads.html</u>. Se requiere la versiÃ³n 1.4.0 o superior.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/es/Paper_es.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/es/Paper_es.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/es/Paper_es.xml	(revision 13632)
@@ -0,0 +1,853 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">BIBLIOTECA DIGITAL GREENSTONE</Text>
+</Heading>
+<Title>
+<Text id="2">DEL PAPEL A LA COLECCIÃN</Text>
+</Title>
+<Author>
+<Text id="3">Dr. Michel Loots, Dan Camarzan e Ian H. Witten</Text>
+</Author>
+<Affiliation>
+<Text id="4">Human Info (BÃ©lgica) <br/>Simple Words (Rumania)<br/>Universidad de Waikato (Nueva Zelanda)</Text>
+</Affiliation>
+<Text id="5">Greenstone es un conjunto de programas y aplicaciones de software especialmente diseÃ±ados para la creaciÃ³n y difusiÃ³n de colecciones documentales digitales, el cual le ofrece una nueva forma de organizar la informaciÃ³n y publicarla en Internet o CD-ROM. Greenstone ha sido elaborado como parte del proyecto de Biblioteca Digital de Nueva Zelanda de la Universidad de Waikato y actualmente es desarrollado y distribuido en colaboraciÃ³n con la UNESCO y la ONG Human Info. Es un software de cÃ³digo abierto disponible en <i>http://greenstone.org</i> bajo los tÃ©rminos y condiciones de la Licencia PÃºblica General de GNU.</Text>
+<Comment>
+<Text id="6">Queremos estar seguros que este software trabaje bien para usted. Por favor comunÃ­quenos cualquier problema que tenga con Ã©l a la siguiente direcciÃ³n: <i>greenstone@cs.waikato.ac.nz</i>
+</Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">Marzo de 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">Acerca de este manual</Text>
+</Title>
+<Content>
+<Text id="10">El presente documento explica la forma de crear colecciones en CD-ROM a partir de documentos impresos y expone con detalle los procedimientos y costos de los procesos de escaneado y reconocimiento Ã³ptico de caracteres (OCR por sus siglas en inglÃ©s) para obtener al final un texto con el formato adecuado para los programas Greenstone. TambiÃ©n se describe la forma de crear y editar el material asociado a una colecciÃ³n.</Text>
+<Text id="11">Hemos procurado formular nuestras explicaciones de la manera mÃ¡s sencilla posible. Cualquier referencia a productos o empresas responde a un propÃ³sito meramente ilustrativo, y no presupone por nuestra parte valoraciÃ³n o preferencia alguna por tales productos en perjuicio de cualquier otro.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="12">Conjunto de documentos</Text>
+</Title>
+<Content>
+<Text id="13">La serie completa de documentos comprende cinco volÃºmenes:</Text>
+<BulletList>
+<Bullet>
+<Text id="14">La GuÃ­a de InstalaciÃ³n de la Biblioteca Digital Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="15">La GuÃ­a del Usuario de la Biblioteca Digital Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">La GuÃ­a del Programador de la Biblioteca Digital Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="17">La Biblioteca Digital Greenstone: del Papel a la ColecciÃ³n (<i>el presente documento</i>)</Text>
+</Bullet>
+<Bullet>
+<Text id="18">La Biblioteca Digital Greenstone: uso del Organizador</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">Agradecimientos</Text>
+</Title>
+<Content>
+<Text id="20">Los capÃ­tulos dedicados al escaneado, el Organizador y demÃ¡s informaciÃ³n relativa a la creaciÃ³n de colecciones documentales colectivas sin fines de lucro son obra del Dr. Michel Loots , Gerente de la ONG Human Info y de HumanityCD , Dan Camarzan de Simple Words y el equipo que colabora con ambos desde Brasov (Rumania).</Text>
+<Text id="21">El programa Greenstone es fruto de la colaboraciÃ³n de muchas personas. Rodger McNab y Stefan Boddie son los principales arquitectos y programadores. TambiÃ©n han contribuido David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson y Stuart Yeates. Otros miembros del proyecto Biblioteca Digital de Nueva Zelanda que proporcionaron asesorÃ­a y valiosas ideas para la concepciÃ³n del sistema son: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols y Lloyd Smith. TambiÃ©n queremos dar las gracias a todos aquellos que contribuyeron a los paquetes de programas con licencias GNU incluidos en esta distribuciÃ³n: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE y XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="introduction">
+<Title>
+<Text id="22">IntroducciÃ³n</Text>
+</Title>
+<Content>
+<Text id="23">Uno de los objetivos de la Biblioteca Digital Greenstone es hacer posible que instituciones como las universidades, organismos del sistema de las Naciones Unidas, organizaciones no gubernamentales, gobiernos y organizaciones no lucrativas puedan crear diversas colecciones de informaciÃ³n y difundirlas por Internet o en forma de CD-ROM.</Text>
+<Text id="24">El proceso suele comprender los siguientes pasos:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="25">Determinar los documentos que han de figurar en la colecciÃ³n.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="26">Obtener la autorizaciÃ³n de los titulares de los derechos de autor para incluir esos documentos en la biblioteca digital.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="27">Escanear y reconocer por medio de OCR los documentos impresos que no estÃ©n disponibles en formato digital.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="28">Convertir todos los documentos en un formato que integre texto e imÃ¡genes y se pueda importar a Greenstone, de preferencia en formato HTML o Word de Microsoft, aunque tambiÃ©n se cuenta con plugins que reconocen otros formatos con un nivel variable de precisiÃ³n (vÃ©ase laÂ <i>GuÃ­a del Usuario de la Biblioteca Digital Greenstone</i>).</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="29">Etiquetar los capÃ­tulos, pÃ¡rrafos e imÃ¡genes de los documentos electrÃ³nicos.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="30">Dotar a la colecciÃ³n de la estructura idÃ³nea para que funcione como biblioteca digital.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="31">Crear la biblioteca digital utilizando los programas Greenstone.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="32">Editar y distribuir la colecciÃ³n en CD-ROM y/o distribuirla por Internet.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="33">Para crear una colecciÃ³n digital es preciso que las publicaciones existan antes en formato digital. Los libros, revistas u otros documentos que sÃ³lo existan en forma impresa deberÃ¡n ser escaneados, procesados y convertidos en un formato que la computadora reconozca (paso iii). El procedimiento mÃ¡s usual para ello es el reconocimiento Ã³ptico de caracteres (OCR por sus siglas en inglÃ©s), aunque a veces se opta por capturar Ã­ntegramente el texto. De este proceso tratan los capÃ­tulos 2 a 4 del presente manual.</Text>
+<Text id="34">El paso v) sirve para que, una vez finalizada la biblioteca, el usuario pueda seleccionar y ver en pantalla por separado las distintas partes de un documento. El paso vi) consiste en asignar atributos a cada documento, como por ejemplo categorÃ­as temÃ¡ticas, palabras clave y datos bibliogrÃ¡ficos con arreglo a los cuales se pueda ordenar y consultar la biblioteca. Estos pasos se explican en el CapÃ­tulo 5 del presente manual.</Text>
+<Text id="35">Asimismo, en el presente manual se tratan numerosas cuestiones relativas al procedimiento editorial y a la creaciÃ³n de una colecciÃ³n digital a partir de documentos impresos. Antes de seguir adelante, el lector debe plantearse las siguientes preguntas:</Text>
+<BulletList>
+<Bullet>
+<Text id="36">Â¿CuÃ¡l es el objetivo de mi colecciÃ³n?</Text>
+</Bullet>
+<Bullet>
+<Text id="37">Â¿A quÃ© grupo de usuarios se dirige?</Text>
+</Bullet>
+<Bullet>
+<Text id="38">Â¿CuÃ¡n grande es dicho grupo? Â¿Tiene dimensiÃ³n local, regional o mundial?</Text>
+</Bullet>
+<Bullet>
+<Text id="39">Â¿CuÃ¡ntos documentos tengo pensado incluir en la colecciÃ³n?</Text>
+</Bullet>
+<Bullet>
+<Text id="40">Â¿CuÃ¡ntas pÃ¡ginas?</Text>
+</Bullet>
+<Bullet>
+<Text id="41">Â¿CuÃ¡nta informaciÃ³n grÃ¡fica contienen?</Text>
+</Bullet>
+<Bullet>
+<Text id="42">Â¿Cabe subdividir la documentaciÃ³n en partes que sean de interÃ©s para un pÃºblico reducido y otras que requieran una difusiÃ³n mÃ¡s amplia?</Text>
+</Bullet>
+<Bullet>
+<Text id="43">Â¿Existen ya en forma electrÃ³nica los documentos?</Text>
+</Bullet>
+<Bullet>
+<Text id="44">De ser asÃ­, Â¿en quÃ© formato? (SeÃ±alemos de paso que un archivo PDF no equivale automÃ¡ticamente al texto completo en formato electrÃ³nico, pues a menudo contiene sÃ³lo la imagen de las pÃ¡ginas.)</Text>
+</Bullet>
+<Bullet>
+<Text id="45">Â¿A quÃ© derechos de autor estÃ¡n sujetos los documentos?</Text>
+</Bullet>
+<Bullet>
+<Text id="46">Â¿QuiÃ©n es el titular de los derechos de autor?</Text>
+</Bullet>
+<Bullet>
+<Text id="47">Â¿Hay otras organizaciones que se dirijan al mismo pÃºblico? </Text>
+</Bullet>
+<Bullet>
+<Text id="48">Â¿Tengo deseos de colaborar con otros grupos?</Text>
+</Bullet>
+<Bullet>
+<Text id="49">Â¿De quÃ© presupuesto dispongo para el conjunto del proyecto?</Text>
+</Bullet>
+<Bullet>
+<Text id="50">Â¿De quÃ© recursos humanos (en personas-mes) dispongo para las labores de coordinaciÃ³n, ediciÃ³n, escaneado y programaciÃ³n?</Text>
+</Bullet>
+<Bullet>
+<Text id="51">Â¿De cuÃ¡ntas computadoras dispongo para el proyecto?</Text>
+</Bullet>
+<Bullet>
+<Text id="52">Â¿CuÃ¡ntos CD-ROM tengo pensado distribuir?</Text>
+</Bullet>
+<Bullet>
+<Text id="53">Â¿Voy a distribuirlos gratuitamente o a venderlos?</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Chapter>
+<Chapter id="scanners_and_scanning">
+<Title>
+<Text id="54">EscÃ¡neres y escaneado</Text>
+</Title>
+<Content>
+<Text id="55">En el proceso de conversiÃ³n de documentos impresos en una colecciÃ³n de biblioteca digital, el primer paso consiste en obtener imÃ¡genes digitales de todas las pÃ¡ginas de todas las publicaciones. La siguiente etapa es la del reconocimiento Ã³ptico de caracteres (OCR), proceso que requiere, para un resultado Ã³ptimo, imÃ¡genes de partida limpias y de buena calidad. Para el proceso de digitalizaciÃ³n se necesita un escÃ¡ner que pueda trabajar a una resoluciÃ³n de 300 ppp (puntos por pulgada). Gran parte del trabajo puede hacerse en blanco y negro, aunque deberÃ¡ utilizarse un escÃ¡ner capaz de obtener imÃ¡genes en color cuando el documento las contenga. La mayorÃ­a de las cubiertas de libro son en color, por lo que hay que escanearlas en forma de imagen fotogrÃ¡fica en color.</Text>
+<Section id="scanners">
+<Title>
+<Text id="56">EscÃ¡neres</Text>
+</Title>
+<Content>
+<Text id="57">Existen escÃ¡neres de todos los precios, formas y tamaÃ±os, que pueden costar desde 100 dÃ³lares (un escÃ¡ner plano) hasta mÃ¡s de 50.000 dÃ³lares (los grandes escÃ¡neres industriales de fabricantes como Bell &amp; Howell<FootnoteRef id="1"/>). Hay muchos sitios Web en los que se ofrece a la venta un amplio surtido de escÃ¡neres. Para encontrarlos basta con introducir la palabra âscannerâ (escÃ¡ner) en buscadores como Google, Altavista o Yahoo.</Text>
+<Text id="58">El formato de salida de una pÃ¡gina escaneada es un archivo informÃ¡tico, por lo general en formato TIFF o Bitmap. El mejor formato es el TIFF IV comprimido. Una pÃ¡gina normal, escaneada y convertida en este formato, ocupa sÃ³lo 50 Kb de memoria, mientras que una pÃ¡gina equivalente en formato Bitmap no comprimido puede llegar a los 2 Mb.</Text>
+<Subsection id="low-cost_flat-bed_scanner">
+<Title>
+<Text id="59">EscÃ¡neres planos (o de sobremesa) de gama baja</Text>
+</Title>
+<Content>
+<Text id="60">Los escÃ¡neres de este tipo son los mÃ¡s econÃ³micos y difundidos. Existen muchas marcas: HP, Agfa, Acer, etc., con precios que van de los 100 a los 300 dÃ³lares. Con ellos pueden obtenerse imÃ¡genes tanto en blanco y negro como en color.Â <b/>Â El bajo precio de estas mÃ¡quinas permite conectar cada computadora a su propio escÃ¡ner.</Text>
+<Text id="61">Entre sus inconvenientes cabe citar la mediocre calidad del resultado, la lentitud con que trabajan, su escasa fiabilidad a temperaturas altas y la relativa frecuencia con que se averÃ­an. Es preciso escanear las pÃ¡ginas manualmente, una por una, colocÃ¡ndolas cuidadosamente en la placa de escaneado para que queden correctamente alineadas. De ahÃ­ que su productividad resulte baja. Aunque los fabricantes aseguran que se puede escanear una pÃ¡gina en menos de un minuto, en la prÃ¡ctica rara vez se consiguen resultados superiores a las doce pÃ¡ginas por hora. AdemÃ¡s, el proceso de escaneado monopoliza la computadora con la que se estÃ¡ realizando el trabajo.</Text>
+<Text id="62">Por todo lo dicho, estos escÃ¡neres sÃ³lo son Ãºtiles para realizar trabajos de escasa envergadura y pocas pÃ¡ginas: no mÃ¡s de 200 a 400 pÃ¡ginas al mes cuando se trate de un trabajo sistemÃ¡tico, y de 1.000 a 2.000 pÃ¡ginas para operaciones de carÃ¡cter esporÃ¡dico.</Text>
+</Content>
+</Subsection>
+<Subsection id="low-end_scanner_with_sheet_feeder">
+<Title>
+<Text id="63">EscÃ¡neres de gama baja con alimentador de papel</Text>
+</Title>
+<Content>
+<Text id="64">Los escÃ¡neres de este tipo suelen costar entre 500 y 1.200 dÃ³lares. Ofrecen la posibilidad de escanear y procesar de 10 a 50 pÃ¡ginas de una vez, lo que evita que el operador tenga que estar continuamente pendiente de la mÃ¡quina y aumenta la productividad hasta unas 150 a 200 pÃ¡ginas diarias. Estos escÃ¡neres son mÃ¡s robustos y gozan de una vida Ãºtil mÃ¡s larga antes de necesitar reparaciones (lo que suele ocurrir al cabo de 30.000 a 50.000 pÃ¡ginas).</Text>
+<Text id="65">Una de sus desventajas es que sÃ³lo pueden escanear una cara a la vez, lo que obliga a invertir el paquete de pÃ¡ginas y escanearlas de nuevo para obtener imÃ¡genes por ambas caras. Ello da lugar a frecuentes problemas, pues los alimentadores nunca funcionan a la perfecciÃ³n y a veces las pÃ¡ginas se atascan.</Text>
+<Text id="66">Estos escÃ¡neres son Ãºtiles para trabajos de 1.500 a 3.000 pÃ¡ginas mensuales.</Text>
+</Content>
+</Subsection>
+<Subsection id="color_scanners">
+<Title>
+<Text id="67">EscÃ¡neres en color</Text>
+</Title>
+<Content>
+<Text id="68">Toda operaciÃ³n de escaneado conlleva siempre imÃ¡genes en color, lo que hace imprescindible un escÃ¡ner capaz de procesarlas. Por regla general, menos del 5% de una publicaciÃ³n contiene imÃ¡genes en color, sin contar la cubierta. En consecuencia, serÃ¡ suficiente un escÃ¡ner plano de gama baja como los mencionados mÃ¡s arriba. Es aconsejable elegir una mÃ¡quina que pueda trabajar a una resoluciÃ³n de hasta 600 ppp.</Text>
+</Content>
+</Subsection>
+<Subsection id="professional_duplex_scanners">
+<Title>
+<Text id="69">EscÃ¡neres dÃºplex profesionales</Text>
+</Title>
+<Content>
+<Text id="70">Los escÃ¡neres profesionales son mÃ¡quinas fiables y resistentes, capaces de tratar un gran nÃºmero de pÃ¡ginas (normalmente entre 2.000 y 10.000 pÃ¡ginas diarias). EstÃ¡n provistos de una bandeja de alimentaciÃ³n automÃ¡tica con capacidad para 50 a 200 pÃ¡ginas. Los mejores y mÃ¡s rÃ¡pidos son los dÃºplex, es decir, capaces de escanear simultÃ¡neamente las dos caras de una hoja.</Text>
+<Text id="71">Para utilizar un escÃ¡ner dÃºplex profesional se requiere una computadora potente, dotada de un disco duro de 10 a 20 Gb de capacidad como mÃ­nimo. El precio de estos escÃ¡neres oscila entre los 5.000 y los 50.000 dÃ³lares. El escÃ¡ner dÃºplex Canon DR-6020, por ejemplo, cuesta 5.000 dÃ³lares y puede trabajar con documentos impresos por ambas caras. Ofrece un rendimiento de unas 2.000 pÃ¡ginas diarias y un periodo de vida Ãºtil de 600.000 a 800.000 pÃ¡ginas. Los escÃ¡neres Bell &amp; Howell y Fujitsu cuestan entre 10.000 y 50.000 dÃ³lares y gozan de un periodo de vida Ãºtil de muchos millones de pÃ¡ginas.</Text>
+<Text id="72">Los escÃ¡neres para microfichas cuestan entre 15.000 (por una unidad semimanual) y 80.000 dÃ³lares (por un escÃ¡ner completamente automÃ¡tico).</Text>
+</Content>
+</Subsection>
+<Subsection id="scanning_programs">
+<Title>
+<Text id="73">Programas de escaneado</Text>
+</Title>
+<Content>
+<Text id="74">Cada escÃ¡ner viene acompaÃ±ado de su propio programa informÃ¡tico, que es necesario instalar en la computadora desde la que vaya a controlarse el escaneado. Algunos traen consigo una tarjeta controladora que se instala en la computadora para acelerar la digitalizaciÃ³n.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="preparing_the_documents">
+<Title>
+<Text id="75">PreparaciÃ³n de los documentos</Text>
+</Title>
+<Content>
+<Text id="76">Antes de escanear los documentos hay que prepararlos adecuadamente, eliminando posibles motas de polvo, secÃ¡ndolos si estÃ¡n hÃºmedos, extrayendo clips y grapas y alisando las pÃ¡ginas dobladas o arrugadas.</Text>
+<Text id="77">Es preciso desmontar el lomo de los libros, cortÃ¡ndolo en lÃ­nea recta y desprendiÃ©ndolo con precisiÃ³n. A menudo habrÃ¡n de encuadernarse de nuevo los libros procedentes de bibliotecas, en cuyo caso conviene extremar las precauciones al desmontar el lomo para facilitar la posterior encuadernaciÃ³n.</Text>
+<Text id="78">Cuando se trabaje con pocos documentos se puede retirar el lomo manualmente, con ayuda de una regla y una cuchilla. Â¡Pero cuidado con los dedos! Para un mayor nÃºmero de documentos merece la pena recurrir a guillotinas manuales especiales</Text>
+<Text id="79">Para grandes volÃºmenes, por ejemplo mÃ¡s de 20 documentos, recomendamos pedir permiso a una imprenta o copisterÃ­a para utilizar su guillotina profesional. RecuÃ©rdese que es preciso extraer los clips y las grapas para no daÃ±ar las cuchillas.</Text>
+</Content>
+</Section>
+<Section id="the_scanning_process">
+<Title>
+<Text id="80">El proceso de escaneado</Text>
+</Title>
+<Content>
+<Text id="81">Con el programa informÃ¡tico suministrado con el escÃ¡ner se genera a partir de cada pÃ¡gina una imagen electrÃ³nica, que se transforma en una imagen Bitmap o TIFF y se memoriza acto seguido en el disco duro, asignando a cada archivo un nombre normalizado. Una vez escaneados todos o una parte de los documentos de un lote empieza el proceso de OCR, del que puede ocuparse el operador del escÃ¡ner o cualquier otra persona.</Text>
+<Text id="82">En general se necesita una resoluciÃ³n de 300 ppp, aunque a veces tambiÃ©n resulte aceptable un valor de 200 ppp.</Text>
+<Subsection id="quality_control">
+<Title>
+<Text id="83">Control de calidad</Text>
+</Title>
+<Content>
+<Text id="84">La digitalizaciÃ³n sirve para obtener una versiÃ³n perfecta de las publicaciones en formato de texto o HTML mediante el proceso de OCR, o bien para crear archivos grÃ¡ficos mejorados como los PDF. En ambos casos es de suma importancia que la imagen sea de buena calidad. En caso contrario los archivos grÃ¡ficos resultan poco nÃ­tidos y consumen mÃ¡s memoria. La calidad influye sobremanera en el proceso de OCR: con imÃ¡genes de calidad mediocre la productividad puede caer hasta en un 40%. Sabiendo que el OCR suele representar mÃ¡s del 90% del costo total, se deduce que la calidad del escaneado es determinante para el costo final del proceso.</Text>
+<Text id="85">Es posible mejorar la calidad de un archivo TIFF adaptando el proceso de escaneado a cada tipo de papel mediante las opciones de ajuste que ofrece el programa del escÃ¡ner. Un tipo de papel relativamente transparente requerirÃ¡ parÃ¡metros mÃ¡s claros, el contraste deberÃ¡ ajustarse en funciÃ³n de la calidad de la impresiÃ³n, etc.</Text>
+<Text id="86">Ante todo conviene dividir el material en lotes de documentos que presenten similar calidad de papel e impresiÃ³n, y despuÃ©s realizar pruebas de OCR con una muestra del primer lote para determinar los parÃ¡metros de ajuste idÃ³neos. A continuaciÃ³n se escanearÃ¡n todos los documentos de ese primer lote antes de continuar con el siguiente.</Text>
+</Content>
+</Subsection>
+<Subsection id="filename_conventions">
+<Title>
+<Text id="87">Convenciones para designar los archivos</Text>
+</Title>
+<Content>
+<Text id="88">Es preciso asignar a cada libro o documento un nÃºmero de trabajo o cÃ³digo Ãºnico, que a su vez darÃ¡ nombre a la carpeta en la que se archiven todas las imÃ¡genes TIFF correspondientes a ese documento. SegÃºn el sistema operativo del que se trate (DOS, Windows, UNIX, LINUX, etc.), el nombre de un archivo puede comprender entre 8 y 128 caracteres, aunque es aconsejable limitarse a un mÃ¡ximo de 16 caracteres. Si se utilizan 8 caracteres, los cinco primeros servirÃ­an para identificar el documento, el siguiente serÃ­a una letra indicativa del cÃ³digo de idioma y los dos restantes caracteres indicarÃ­an el nÃºmero de pÃ¡gina. Por ejemplo: el identificadorÂ <i>u7548e12.tif</i>Â corresponderÃ­a a la imagen TIFF de la pÃ¡gina 12 de un libro escrito en inglÃ©s que tuviera por cÃ³digoÂ <i>u7548e.</i>
+</Text>
+<Text id="89">Conviene asignar un directorio del disco duro a los trabajos de escaneado (por ejemplo con el nombre deÂ <i>scanjobs</i>). DespuÃ©s se puede crear un subdirectorio para cada uno de los trabajos, en cuyo interior se crearÃ¡ un nuevo subdirectorio para cada publicaciÃ³n (en el ejemplo anterior,Â <i>u7548e</i>), donde se guardan todas las imÃ¡genes TIFF correspondientes a esa publicaciÃ³n, incluidas las imÃ¡genes en color.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="productivity_and_resources">
+<Title>
+<Text id="90">Productividad y recursos necesarios</Text>
+</Title>
+<Content>
+<Text id="91">No hay que subestimar la carga de trabajo que suponen los procesos de escaneado y, sobre todo, de OCR. Es preferible considerar que ambos procesos son completamente independientes y elegir el procedimiento idÃ³neo (desde el punto de vista econÃ³mico y tambiÃ©n prÃ¡ctico) para cada uno de ellos por separado.</Text>
+<Text id="92">Entre los aspectos que conviene tener en cuenta cabe seÃ±alar: la inversiÃ³n necesaria en escÃ¡neres y computadoras, la existencia de los recursos humanos y el espacio necesarios, la formaciÃ³n del personal, los gastos salariales, el nÃºmero inicial y total de pÃ¡ginas por escanear, los plazos en que ha de realizarse el trabajo y la posibilidad de subcontratarlo a terceros.</Text>
+<Subsection id="scanning_costs">
+<Title>
+<Text id="93">Costos del proceso de escaneado</Text>
+</Title>
+<Content>
+<Text id="94">Es importante decidir si se ha de invertir en un equipo de escaneado y asumir internamente esa labor o bien subcontratarla a una empresa especializada. Las principales consideraciones que deben tenerse en cuenta son:</Text>
+<BulletList>
+<Bullet>
+<Text id="95">los plazos en que ha de realizarse el trabajo;</Text>
+</Bullet>
+<Bullet>
+<Text id="96">el nÃºmero total de pÃ¡ginas;</Text>
+</Bullet>
+<Bullet>
+<Text id="97">los costos salariales correspondientes a las personas encargadas del escaneado.</Text>
+</Bullet>
+</BulletList>
+<Text id="98">Las personas a quienes se encomiende el escaneado deben estar muy motivadas y preparadas tÃ©cnicamente, y tener muy clara la importancia de cumplir los criterios de calidad.</Text>
+<Text id="99">Una empresa especializada suele cobrar 0,06 dÃ³lares por pÃ¡gina, a lo que hay que aÃ±adir los gastos de envÃ­o, que pueden ser de hasta 0,03 dÃ³lares por pÃ¡gina cuando se remite el material de un paÃ­s en desarrollo a un paÃ­s desarrollado y de 0,015 dÃ³lares por pÃ¡gina cuando se trata de un envÃ­o nacional.</Text>
+<Text id="100">En el Cuadro <CrossRef target="Table" ref="table_scanning_cost"/> se ofrecen estimaciones de los costos de escaneado por cuenta propia segÃºn el tipo de escÃ¡ner que se utilice. Conviene tener en cuenta que estas cifras son aproximadas y corresponden mÃ¡s bien a Ã³rdenes generales de magnitud, basados en la experiencia de los autores. En las tres primeras columnas se presentan los costos laborales. En la primera se indica la productividad (en pÃ¡ginas mensuales) suponiendo que se trabaje a jornada completa. Dividiendo las horas mensuales de trabajo por la productividad en pÃ¡ginas/mes se obtienen los recursos necesarios en tÃ©rminos de horas de trabajo/pÃ¡gina, guarismo que figura en la segunda columna (suponiendo que se trabajen 180 horas al mes).</Text>
+<Table id="table_scanning_cost">
+<Title>
+<Text id="101">Costos del proceso de escaneado</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="90"/>
+<th width="71">
+<Text id="102">Rendimiento (pÃ¡ginas/mes)</Text>
+</th>
+<th width="75">
+<Text id="103">Horas/pÃ¡gina (180 horas/mes)</Text>
+</th>
+<th width="83">
+<Text id="104">Costo/pÃ¡gina (suponiendo 4 dÃ³lares/hora)</Text>
+</th>
+<th width="60">
+<Text id="105">AdquisiciÃ³n del escÃ¡ner (dÃ³lares)</Text>
+</th>
+<th width="66">
+<Text id="106">Vida Ãºtil del escÃ¡ner (pÃ¡ginas)</Text>
+</th>
+<th width="85">
+<Text id="107">PÃ¡ginas que se podrÃ­an subcontratar por el precio del escÃ¡ner (a 0,06 dÃ³lares c/u)</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="108">EscÃ¡ner plano</Text>
+</th>
+<th width="71">
+<Text id="109">2.500</Text>
+</th>
+<th width="75">
+<Text id="110">0,072</Text>
+</th>
+<th width="83">
+<Text id="111">0,288</Text>
+</th>
+<th width="60">
+<Text id="112">300</Text>
+</th>
+<th width="66">
+<Text id="113">7.000</Text>
+</th>
+<th width="85">
+<Text id="114">5.000</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="115">EscÃ¡ner con alimentador de papel</Text>
+</th>
+<th width="71">
+<Text id="116">8.000</Text>
+</th>
+<th width="75">
+<Text id="117">0,0225</Text>
+</th>
+<th width="83">
+<Text id="118">0,09</Text>
+</th>
+<th width="60">
+<Text id="119">800</Text>
+</th>
+<th width="66">
+<Text id="120">30.000 </Text>
+</th>
+<th width="85">
+<Text id="121">13.000</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="122">Profesional: dÃºplex de gama baja</Text>
+</th>
+<th width="71">
+<Text id="123">40.000</Text>
+</th>
+<th width="75">
+<Text id="124">0,0045</Text>
+</th>
+<th width="83">
+<Text id="125">0,018</Text>
+</th>
+<th width="60">
+<Text id="126">6.000</Text>
+</th>
+<th width="66">
+<Text id="127">600.000</Text>
+</th>
+<th width="85">
+<Text id="128">100.000</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="129">Profesional: dÃºplex de gama alta</Text>
+</th>
+<th width="71">
+<Text id="130">150.000</Text>
+</th>
+<th width="75">
+<Text id="131">0,0012</Text>
+</th>
+<th width="83">
+<Text id="132">0,0048</Text>
+</th>
+<th width="60">
+<Text id="133">50.000</Text>
+</th>
+<th width="66">
+<Text id="134">8.000.000</Text>
+</th>
+<th width="85">
+<Text id="135">833.000</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="136">Para determinar el precio por pÃ¡gina se multiplican los costos salariales por hora totales (que dependerÃ¡n de cada caso) por la segunda columna del Cuadro <CrossRef target="Table" ref="table_scanning_cost"/>. En la tercera columna se indica, a tÃ­tulo de ejemplo, el precio de escanear por cuenta propia suponiendo que se pague un sueldo de 4 dÃ³lares/hora, excluidos los gastos de inversiÃ³n.</Text>
+<Text id="137">Estos cÃ¡lculos presuponen que se procesa un nÃºmero de pÃ¡ginas suficiente para justificar la adquisiciÃ³n de un escÃ¡ner. En las tres Ãºltimas columnas del Cuadro <CrossRef target="Table" ref="table_scanning_cost"/> se ofrece informaciÃ³n sobre los costos derivados del propio escÃ¡ner. En la primera de ellas se indica el precio de adquisiciÃ³n de la mÃ¡quina, en la siguiente el tiempo de vida Ãºtil que se le supone y en la Ãºltima el nÃºmero de pÃ¡ginas que podrÃ­an subcontratarse por el precio del escÃ¡ner, contando una tarifa de 0,06 dÃ³lares/pÃ¡gina.</Text>
+<Text id="138">Hay, desde luego, muchos otros factores que influyen en la decisiÃ³n de adquirir o no un escÃ¡ner: la disponibilidad de fondos suficientes, la necesidad de reducir al mÃ­nimo la dependencia para con terceras partes, el deseo de crear capacidades a escala local, la obligaciÃ³n que imponen las bibliotecas de escanear los libros en la propia localidad y no transportarlos, etc.</Text>
+<Text id="139">Las cifras del Cuadro 1 dan una idea aproximada del nÃºmero de pÃ¡ginas necesario para justificar distintos niveles de inversiÃ³n. No es frecuente que una instituciÃ³n u otra entidad necesite escanear 800.000 pÃ¡ginas. Con tales niveles de trabajo se plantean cuestiones mÃ¡s complejas que no vamos a tratar en estas lÃ­neas, como el mantenimiento del equipo o la posibilidad de recuperar gastos ofreciendo a terceros el servicio de escaneado.</Text>
+<Text id="140">Es tentador contemplar el desarrollo de la capacidad de escaneado como una actividad comercial, sobre todo en los paÃ­ses en desarrollo. Pero conviene tener muy en cuenta que no se trata de un proceso repetitivo. Una vez escaneado un documento, el cliente nunca cursarÃ¡ un nuevo pedido para repetir la operaciÃ³n, por muy buena que haya sido su relaciÃ³n de trabajo con la empresa. Desde un punto de vista comercial, se requiere un enorme trabajo de publicidad y comercializaciÃ³n. Desaconsejamos a cualquier ONG u otras organizaciones sin fines de lucro que se aventuren en este terreno sin haber procedido a ensayos exhaustivos y elaborado un minucioso plan comercial.</Text>
+<Text id="141">En conclusiÃ³n, para escanear entre 10.000 y 50.000 pÃ¡ginas conviene plantearse la posibilidad de subcontratar el trabajo. Los cerca de 6.000 dÃ³lares que cuesta un escÃ¡ner profesional de gama baja sÃ³lo se amortizan a partir de un volumen superior a las 100.000 pÃ¡ginas. Otra posible soluciÃ³n consiste en asociarse con otras instituciones (ONG o bibliotecas, por ejemplo) para adquirir colectivamente un escÃ¡ner de ese tipo.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="ocr">
+<Title>
+<Text id="142">OCR: reconocimiento Ã³ptico de caracteres</Text>
+</Title>
+<Content>
+<Text id="143">Los sistemas de reconocimiento Ã³ptico de caracteres (OCR) transforman en texto una imagen escaneada. El punto de partida es una imagen digitalizada en formato TIFF o Bitmap, de la mayor nitidez y calidad posibles, y el resultado final un archivo de texto (generalmente en formato RTF o Word) o para la Web (formato HTML). </Text>
+<Text id="144">El proceso de conversiÃ³n de un documento impreso en un archivo informÃ¡tico comprende las siguientes etapas:</Text>
+<BulletList>
+<Bullet>
+<Text id="145">escaneado;</Text>
+</Bullet>
+<Bullet>
+<Text id="146">anÃ¡lisis de la compaginaciÃ³n;</Text>
+</Bullet>
+<Bullet>
+<Text id="147">reconocimiento Ã³ptico de caracteres;</Text>
+</Bullet>
+<Bullet>
+<Text id="148">escaneado de ilustraciones y cuadros.</Text>
+</Bullet>
+</BulletList>
+<Text id="149">A lo largo del proceso se efectÃºan controles de calidad de los archivos resultantes y se memorizan Ã©stos en el formato apropiado.</Text>
+<Text id="150">El mercado ofrece muchos y buenos programas de OCR, con precios que oscilan entre los 100 y los 400 dÃ³lares<FootnoteRef id="2"/>. Entre muchos otros ejemplos cabe citar los siguientes:</Text>
+<BulletList>
+<Bullet>
+<Text id="151"><i>Read-Iris</i>Â (http://www.readiris.com/)</Text>
+</Bullet>
+<Bullet>
+<Text id="152"><i>Omnipage</i>Â (http://www.omnipage.com/)</Text>
+</Bullet>
+<Bullet>
+<Text id="153"><i>Fine-Reader</i>Â (http://www.finereader.com/)</Text>
+</Bullet>
+</BulletList>
+<Text id="154">En los sitios Web de los fabricantes se ofrece toda la informaciÃ³n necesaria, comprendida la lista de distribuidores locales. Los autores, de acuerdo con su experiencia,Â  consideran que los programas de mÃ¡s fÃ¡cil manejo son Fine-Reader y Omnipage. El primero, que cuesta unos 100 dÃ³lares, es el mÃ¡s barato y ofrece no sÃ³lo gran flexibilidad sino tambiÃ©n el mayor repertorio de idiomas.</Text>
+<Text id="155">Es necesario decidir si se efectÃºan los procesos de escaneado y OCR internamente o se subcontratan a una empresa especializada. Hacerlo por cuenta propia exige disponer de un escÃ¡ner, de un programa de OCR, de conocimientos tÃ©cnicos en la materia y de personal muy motivado y atento a los requisitos de calidad.</Text>
+<Section id="the_ocr_process">
+<Title>
+<Text id="156">El proceso de OCR</Text>
+</Title>
+<Content>
+<Text id="157">El proceso de OCR difiere segÃºn se utilice uno u otro programa de OCR, y cada uno de ellos exige un tiempo considerable de aprendizaje. En el manual de cada programa se exponen todos los detalles relativos al proceso. Hay cuatro aspectos que merecen especial atenciÃ³n: el control de calidad, los cuadros, las ilustraciones y los textos especiales como fÃ³rmulas, caracteres extranjeros, etc.</Text>
+<Subsection id="quality_control_1">
+<Title>
+<Text id="158">Control de calidad</Text>
+</Title>
+<Content>
+<Text id="159">Es preciso insistir en la importancia del control de calidad. Lo ideal es que esos controles estÃ©n a cargo de personas cuya lengua materna sea el idioma en que estÃ¡ escrito el documento o de gente con un excelente dominio del mismo. El perfil idÃ³neo es el de alguien con estudios universitarios o secundarios. Conviene saber ademÃ¡s que en este tipo de tarea los jÃ³venes suelen mantener un nivel de concentraciÃ³n superior.</Text>
+<Text id="160">Normalmente hay cuatro controles de calidad.</Text>
+<Text id="161">El primero se efectÃºa al mismo tiempo que el proceso de OCR. Cada programa tiene un verificador ortogrÃ¡fico incorporado que seÃ±ala todas las posibles letras errÃ³neas y muestra la imagen de la palabra entera para facilitar la comprobaciÃ³n y eventual correcciÃ³n del error.</Text>
+<Text id="162">El segundo es un control general del texto una vez finalizado el proceso de OCR. Uno de los errores mÃ¡s frecuentes es la omisiÃ³n de una pÃ¡gina, un pÃ¡rrafo, los tÃ­tulos de un capÃ­tulo, etc. Debe llevarse a cabo un repaso general para comprobar que no falta ninguna pÃ¡gina. Es esencial asimismo comprobar los tÃ­tulos, los encabezamientos de capÃ­tulo, los pÃ¡rrafos y los cuadros.</Text>
+<Text id="163">El tercer control es el ortogrÃ¡fico, para el que en general se utiliza Word de Microsoft porque su diccionario suele ser mÃ¡s completo que el de los programas de OCR. Importando el libro a un archivo Word y realizando un control ortogrÃ¡fico con este programa se puede detectar y corregir un mayor nÃºmero de errores. Es indispensable aÃ±adir al verificador ortogrÃ¡fico cualquier palabra especialmente difÃ­cil o susceptible de generar una seÃ±al de error, asÃ­ como los tÃ©rminos cientÃ­ficos y tÃ©cnicos que abunden en el tipo de publicaciÃ³n con que se estÃ© trabajando. </Text>
+<Text id="164">Finalmente, otra persona debe efectuar un Ãºltimo control del documento finalizado, tomando al azar fragmentos del libro completo y cerciorÃ¡ndose de que no haya errores o problemas con los cuadros, las ilustraciones, las leyendas o el aspecto general del documento. SÃ³lo despuÃ©s de este Ãºltimo control puede considerarse que el libro estÃ¡ listo para su difusiÃ³n electrÃ³nica.</Text>
+</Content>
+</Subsection>
+<Subsection id="tables">
+<Title>
+<Text id="165">Cuadros</Text>
+</Title>
+<Content>
+<Text id="166">Los cuadros suelen plantear dificultades a los programas de OCR. Controlar su contenido es ademÃ¡s una labor ardua: contienen muchos dÃ­gitos, a veces con puntos y comas, y es fÃ¡cil que las cifras acaben colocadas en la casilla equivocada. Es una tarea que exige concentraciÃ³n, dedicaciÃ³n, un intenso trabajo de relectura, comprobaciones minuciosas y un buen control de calidad. Hay bÃ¡sicamente tres formas distintas de proceder.</Text>
+<Text id="167">La primera consiste simplemente en escanear los cuadros como si fueran imÃ¡genes en blanco y negro e insertarlos con este formato en el lugar correspondiente del documento. Esta es la soluciÃ³n mÃ¡s sencilla, pues no genera errores y no exige mÃ¡s tiempo que el necesario para crear la imagen. Pero consume mÃ¡s memoria que las dos restantes, y ademÃ¡s la resoluciÃ³n obtenida no siempre basta para trabajar en la computadora con cuadros de gran tamaÃ±o: si se reduce todo el cuadro a los lÃ­mites de la pantalla, la resoluciÃ³n es demasiado pequeÃ±a; si por el contrario el cuadro desborda la pantalla, el usuario debe desplazarse para ver todas las columnas y filas, con lo que pierde visiÃ³n de conjunto.</Text>
+<Text id="168">El segundo mÃ©todo es la copia manual: crear un nuevo cuadro con el mismo nÃºmero de filas y columnas y copiar los valores correspondientes a cada casilla, carÃ¡cter por carÃ¡cter.</Text>
+<Text id="169">La tercera soluciÃ³n consiste en someter el cuadro al proceso de OCR. Aunque este procedimiento ahorra tiempo en comparaciÃ³n con el manual, la probabilidad de error es mÃ¡s alta. A veces las columnas quedan fusionadas, o el programa es incapaz de reconocer los puntos y comas.</Text>
+</Content>
+</Subsection>
+<Subsection id="images">
+<Title>
+<Text id="170">Ilustraciones</Text>
+</Title>
+<Content>
+<Text id="171">Las ilustraciones contenidas en una publicaciÃ³n corresponden en general a tres grandes tipos de imagen:</Text>
+<BulletList>
+<Bullet>
+<Text id="172">ilustraciones en blanco y negro, sin tonos intermedios;</Text>
+</Bullet>
+<Bullet>
+<Text id="173">fotografÃ­as en blanco y negro;</Text>
+</Bullet>
+<Bullet>
+<Text id="174">fotografÃ­as en color.</Text>
+</Bullet>
+</BulletList>
+<Text id="175">Las ilustraciones en blanco y negro deben escanearse en modo âdibujos de lÃ­neas simplesâ y guardarse en formato GIF o PNG. Para las fotografÃ­as en blanco y negro conviene utilizar el modo âescala de grisesâ y guardar el resultado en archivos GIF o JPEG. En cuanto a las fotografÃ­as en color, es preciso escanearlas en modo âcolorâ y guardarlas en archivos JPEG. En tÃ©rminos generales, el formato JPEG de calidad media ofrece una resoluciÃ³n suficiente.</Text>
+<Text id="176">Las ilustraciones suelen consumir gran parte del espacio que ocupa una colecciÃ³n en el disco duro o el CD-ROM. De ahÃ­ la importancia de lograr para cada imagen la mayor claridad y visibilidad junto con el menor tamaÃ±o posible. Para ahorrar espacio cabe la posibilidad de prescindir de algunas imÃ¡genes o de todas ellas cuando no sean necesarias para entender el texto.</Text>
+<Text id="177">Las ilustraciones deben escanearse por separado, una por una. Para denominar los archivos grÃ¡ficos recomendamos un nombre compuesto por los cinco o seis primeros caracteres utilizados para designar el documento seguidos del nÃºmero de la pÃ¡gina en que se encuentre la ilustraciÃ³n. Una alternativa, suponiendo que haya un directorio para cada documento, consiste simplemente en utilizar la letraÂ <i>p</i>Â [Â <i>picture</i>Â ] seguida del nÃºmero de la pÃ¡gina. Cuando en una misma pÃ¡gina haya varias ilustraciones, bastarÃ¡ con aÃ±adir una letraÂ <i>a, b, c ...</i>Â al nombre del archivo. Por ejemplo, a una imagen JPEG que aparezca en la pÃ¡gina 36 de la antedicha publicaciÃ³nÂ <i>u7548e</i>Â corresponderÃ¡ un archivo llamadoÂ <i>u7548e36.jpg</i>Â oÂ <i>p36.jpg.</i></Text>
+<Text id="178">Una vez escaneadas las imÃ¡genes, se pueden aplicar programas de procesamiento por lotes para modificar las dimensiones o mejorar la definiciÃ³n de todas las imÃ¡genes a la vez.</Text>
+</Content>
+</Subsection>
+<Subsection id="specialized_material">
+<Title>
+<Text id="179">Textos con caracterÃ­sticas especiales</Text>
+</Title>
+<Content>
+<Text id="180">Muchos documentos contienen elementos que conviene tratar aparte (caracteres especiales, fÃ³rmulas, pÃ¡ginas especialmente dificultosas, etc.). Los caracteres especiales suelen provenir de idiomas distintos u ostentar marcas diacrÃ­ticas. En tal caso hay que seleccionar el idioma del que se trate en la opciÃ³n âidiomaâ del programa OCR. Las fÃ³rmulas deberÃ¡n reproducirse manualmente, lo que a veces es imposible con un programa de OCR, en cuyo caso hay que recurrir a un procesador de texto como Word de Microsoft. Las pÃ¡ginas de las que no pueda obtenerse una imagen nÃ­tida, ya sea por la complejidad del texto o por el mal estado en que se encuentren, deberÃ¡n ser reproducidas manualmente.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="productivity_and_resources_1">
+<Title>
+<Text id="181">Productividad y recursos necesarios</Text>
+</Title>
+<Content>
+<Text id="182">Como hemos dicho, no hay que subestimar la dificultad del proceso de OCR. Aunque conviene estudiar separadamente las alternativas econÃ³micas y prÃ¡cticas del proceso de escaneado y del de OCR, ambos plantean interrogantes parecidos: la inversiÃ³n necesaria en computadoras, la disponibilidad de personal y de capacidad de gestiÃ³n, la formaciÃ³n del personal, los costos salariales, el nÃºmero total de pÃ¡ginas que deben tratarse y las posibilidades de subcontratar el trabajo a terceros.</Text>
+<Text id="183">Esta secciÃ³n se basa en la experiencia de los autores en el trabajo de OCR en BÃ©lgica, Rumania y la India. Todos los ejemplos, cÃ¡lculos y cifras que aquÃ­ se exponen corresponden a una situaciÃ³n ordinaria: documentos de dificultad normal (con cuadros e ilustraciones) como los que pueden encontrarse en la mayorÃ­a de los archivos o bibliotecas, resultados de muy buena calidad y trabajo a medio o largo plazo.</Text>
+<Subsection id="intensive_ocr">
+<Title>
+<Text id="184">Trabajo intensivo de OCR</Text>
+</Title>
+<Content>
+<Text id="185">El OCR es un proceso difÃ­cil, que exige gran concentraciÃ³n y destreza. Antes de alcanzar un nivel Ã³ptimo de rendimiento y calidad, el operador necesita un periodo de aprendizaje de unas seis semanas.</Text>
+<Text id="186">Los mejores resultados y la productividad mÃ¡s alta se consiguen por lo general durante las primeras horas de trabajo. Al cabo de tres horas la productividad baja con rapidez, quizÃ¡ hasta un 50% del nivel inicial. Al cabo de seis horas, la mayorÃ­a de la gente se encuentra muy cansada.</Text>
+<Text id="187">Algo parecido ocurre durante las primeras semanas de trabajo, en las que todo el mundo alcanza una productividad bastante elevada. Posteriormente, sin embargo, hasta dos tercios de los operadores de OCR empiezan a sentirse aburridos y descontentos. A la larga esas personas acaban abandonando el trabajo o rindiendo poco en tÃ©rminos de calidad y productividad. Incluso los que superan el periodo crÃ­tico de tres a cinco semanas y se integran en el equipo de trabajo suelen renunciar y partir en busca de una mejor ocupaciÃ³n al cabo de 6 a 12 meses.</Text>
+<Text id="188">Las observaciones sobre el personal que formulamos en la secciÃ³n <CrossRef target="Section" ref="the_ocr_process"/>  son especialmente aplicables al trabajo intensivo de OCR. Los controles de calidad resultan mejores cuando corren a cargo de hablantes nativos o profundos conocedores del idioma en cuestiÃ³n. En general los jÃ³venes pueden mantener un nivel de concentraciÃ³n superior al de las personas mayores en las labores de OCR. La experiencia demuestra que las personas de entre 18 y 23 aÃ±os de edad tienden a adaptarse mejor a ese cometido que las mayores de 25 aÃ±os.</Text>
+<Text id="189">Por Ãºltimo, considerando lo aburrido que puede resultar el trabajo de OCR, la motivaciÃ³n y un constante prurito de calidad son elementos de excepcional importancia.</Text>
+<Text id="190">De todo lo dicho se desprenden las siguientes directrices generales sobre el proceso de OCR:</Text>
+<BulletList>
+<Bullet>
+<Text id="191">Los jÃ³venes de entre 18 y 25 aÃ±os de edad son los mÃ¡s aptos para este tipo de trabajo. </Text>
+</Bullet>
+<Bullet>
+<Text id="192">Dado que las primeras horas son siempre las mÃ¡s productivas, conviene organizar turnos de trabajo a tiempo parcial o, en su defecto, encomendar la labor a jornada completa a las personas mÃ¡s motivadas y con mayor capacidad de concentraciÃ³n.</Text>
+</Bullet>
+<Bullet>
+<Text id="193">DespuÃ©s de tres a cinco semanas de actividad, dos tercios de los operadores tienden a renunciar o a sentirse hastiados. Ello se traduce en un descenso de la calidad y la productividad en las Ãºltimas semanas.</Text>
+</Bullet>
+<Bullet>
+<Text id="194">Es preciso un suministro periÃ³dico de trabajo para justificar la necesaria formaciÃ³n del personal, mantener la concentraciÃ³n y conservar alta la moral del equipo.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="achievable_productivity">
+<Title>
+<Text id="195">Objetivos asequibles de productividad</Text>
+</Title>
+<Content>
+<Table id="table_ocr_productivity">
+<Title>
+<Text id="196">Productividad en el proceso de OCR</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="161"/>
+<th width="142">
+<Text id="197">Horas de trabajo/dÃ­a</Text>
+</th>
+<th width="123">
+<Text id="198">PÃ¡ginas/dÃ­a</Text>
+</th>
+<th width="104">
+<Text id="199">PÃ¡ginas/mes</Text>
+</th>
+</tr>
+<tr>
+<th width="161">
+<Text id="200">FormaciÃ³n inicialÂ (seis semanas)</Text>
+</th>
+<th width="142">
+<Text id="201">3</Text>
+</th>
+<th width="123">
+<Text id="202">6</Text>
+</th>
+<th width="104">
+<Text id="203">120</Text>
+</th>
+</tr>
+<tr>
+<th width="161">
+<Text id="204">Nivel Ã³ptimo de productividad</Text>
+</th>
+<th width="142">
+<Text id="205">3</Text>
+</th>
+<th width="123">
+<Text id="206">9</Text>
+</th>
+<th width="104">
+<Text id="207">150 a 200</Text>
+</th>
+</tr>
+<tr>
+<th width="161">Â </th>
+<th width="142">
+<Text id="208">7</Text>
+</th>
+<th width="123">
+<Text id="209">28</Text>
+</th>
+<th width="104">
+<Text id="210">500 a 600</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="211">En el Cuadro <CrossRef target="Table" ref="table_ocr_productivity"/> se presentan las cifras mÃ¡s frecuentes de productividad en el trabajo de OCR. Teniendo en cuenta que puede tratarse de documentos de todos los tamaÃ±os y niveles de calidad, estas cifras parten del supuesto de que el conjunto de documentos contiene un nÃºmero promedio de ilustraciones y cuadros (por ejemplo una ilustraciÃ³n y un cuadro de 5x5 cada ocho pÃ¡ginas), que las ilustraciones son de calidad entre media y alta (recordemos que ello depende de la calidad del escaneado) y que los operadores de OCR dominan el idioma en que estÃ¡ escrito el documento.</Text>
+<Text id="212">En el Cuadro <CrossRef target="Table" ref="table_ocr_productivity"/> se distingue entre las estadÃ­sticas de personas en periodo de formaciÃ³n y las de quienes han alcanzado su nivel Ã³ptimo de productividad. Si un miembro del personal administrativo dedicara tres horas diarias al trabajo de OCR, su rendimiento serÃ­a de entre 180 y 200 pÃ¡ginas al mes. Un operador a jornada completa bien formado, con gran capacidad de concentraciÃ³n y escrupulosa atenciÃ³n a los criterios de calidad, en cambio, podrÃ­a alcanzar una productividad de entre 500 y 600 pÃ¡ginas al mes.</Text>
+<Text id="213">Sin embargo, con pÃ¡ginas de especial dificultad y escasa calidad, con abundantes cuadros o columnas, se obtienen cifras muy inferiores (quizÃ¡ de 300 a 400 pÃ¡ginas mensuales a jornada completa).</Text>
+<Text id="214">Supongamos que el costo salarial de un operador a jornada completa muy aplicado y motivado asciende a 400 dÃ³lares mensuales, y que los gastos generales (gastos de gestiÃ³n, computadoras, espacio de oficina, instalaciones, etc.) suponen otros 300 a 400 dÃ³lares mensuales por persona. En tal caso, el costo del proceso de OCR viene a ser de 1,2 a 1,6 dÃ³lares por pÃ¡gina. Si ademÃ¡s se toma en cuenta el periodo de formaciÃ³n, el volumen total, el lapso de tiempo considerado y los eventuales costes de la suspensiÃ³n de las operaciones cuando falte el trabajo, el costo asciende a un valor entre 1,5 y 2,5 dÃ³lares por pÃ¡gina.</Text>
+<Text id="215">Conviene comparar los costos del proceso de OCR efectuado por cuenta propia con los de la subcontrataciÃ³n a una empresa especializada. Estas empresas suelen cobrar entre 1,5 y 4 dÃ³lares por pÃ¡gina, incluyendo las ilustraciones y los cuadros. Human Info/Simple Word, que posee una unidad de este tipo en Rumania, aplica tarifas especiales para las organizaciones humanitarias sin fines de lucro (entre 1,2 y 2 dÃ³lares por pÃ¡gina). Puede solicitarse informaciÃ³n o asesoramiento escribiÃ©ndonos a la direcciÃ³n:scanning@humaninfo.org.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="alternatives_to_ocr">
+<Title>
+<Text id="216">Alternativas al proceso de OCR</Text>
+</Title>
+<Content>
+<Text id="217">En las siguientes lÃ­neas exponemos dos posibles alternativas al OCR.</Text>
+<Subsection id="manual_retyping">
+<Title>
+<Text id="218">Mecanografiado manual</Text>
+</Title>
+<Content>
+<Text id="219">La primera posibilidad, que ademÃ¡s elimina buena parte del escaneado, consiste en mecanografiar de nuevo los documentos con un programa de tratamiento de texto. Utilizando este procedimiento hay que escanear Ãºnicamente las ilustraciones y la cubierta (y no las restantes pÃ¡ginas), lo que hace innecesario disponer de un escÃ¡ner y un programa de OCR potentes. </Text>
+<Text id="220">No es preciso que los operadores entiendan el texto. SÃ³lo tienen que ser buenos mecanÃ³grafos y reproducir exactamente lo que ven. Dado que este proceso suele generar errores, a menudo se utiliza el doble mecanografiado para detectarlos y corregirlos. Este mÃ©todo requiere que dos personas mecanografÃ­en independientemente el mismo documento, despuÃ©s de lo cual un operador provisto del texto original compara ambas versiones electrÃ³nicas palabra por palabra, con ayuda de un programa informÃ¡tico especial. Se parte de la premisa de que si una misma palabra ha sido escrita dos veces por separado de la misma manera, serÃ¡ correcta. Pero ello no siempre es asÃ­, y cuando se quiere trabajar con la mÃ¡xima fiabilidad se recurre al triple mecanografiado.</Text>
+<Text id="221">Teniendo en cuenta que el uso de un programa de OCR entraÃ±a el de computadoras de gran potencia, la ventaja bÃ¡sica de este mÃ©todo es que prescinde del OCR y por lo tanto permite utilizar computadoras mÃ¡s antiguas, sencillas o de segunda mano, lo que supone un ahorro considerable. AdemÃ¡s, esta labor requiere trabajadores menos especializados. En cuanto a sus inconvenientes, Ã©stos residen en el periodo de formaciÃ³n (de al menos dos meses) que se necesita y en la abundancia de errores que suelen darse con un proceso de mecanografiado Ãºnico, lo que obliga a trabajar por duplicado o triplicado.</Text>
+<Text id="222">Los costos de este procedimiento dependen exclusivamente del nivel salarial. Los mecanÃ³grafos de paÃ­ses en desarrollo suelen cobrar unos 150 dÃ³lares mensuales. Su productividad oscila entre 20 y 30 pÃ¡ginas diarias, lo que equivale a 400 pÃ¡ginas mensuales, comprendidas las ilustraciones. Suponiendo que se trabaje por duplicado, los costos salariales suman en total 300 dÃ³lares al mes, sin contar los gastos generales.</Text>
+</Content>
+</Subsection>
+<Subsection id="image_files">
+<Title>
+<Text id="223">Archivos grÃ¡ficos</Text>
+</Title>
+<Content>
+<Text id="224">Una alternativa sumamente barata al proceso de OCR consiste en utilizar simplemente una versiÃ³n grÃ¡fica en PDF de las pÃ¡ginas del documento, lo que reduce los costos a unos 0,1 dÃ³lares por pÃ¡gina (una pequeÃ±a fracciÃ³n de lo que costarÃ­a un proceso de OCR).</Text>
+<Text id="225">Una vez concluido el escaneado y creados los archivos TIFF, se utiliza un convertidor automÃ¡tico (en general Acrobat o Photoshop de Adobe) para convertir en formato PDF todos los archivos TIFF correspondientes a las pÃ¡ginas del libro.</Text>
+<Text id="226">El problema es que en esos archivos no se pueden efectuar bÃºsquedas y que ademÃ¡s son bastante pesados (por lo general 50 Kb por pÃ¡gina, con un margen de variaciÃ³n del 20% segÃºn la calidad del archivo TIFF original).</Text>
+<Text id="227">La descarga de un archivo grÃ¡fico PDF es un proceso lento, a veces imposible o de precio prohibitivo en los paÃ­ses en desarrollo. Esos archivos caben rara vez en un disquete y no admiten operaciones de manipulaciÃ³n del texto como la de âcortar y pegarâ.</Text>
+<Text id="228">SÃ³lo se optarÃ¡ por esta soluciÃ³n cuando se carezca del presupuesto necesario para un proceso de OCR o cuando se trate de documentos destinados a un pÃºblico poco numeroso y provisto de una conexiÃ³n a Internet de bajo costo y alta velocidad.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="combining_scanning_and_ocr">
+<Title>
+<Text id="229">CombinaciÃ³n de escaneado y OCR</Text>
+</Title>
+<Content>
+<Text id="230">La mayorÃ­a de los programas de OCR pueden escanear una pÃ¡gina y efectuar inmediatamente el reconocimiento Ã³ptico, a condiciÃ³n de que el escÃ¡ner estÃ© conectado directamente a la computadora que ejecuta el programa. Aunque escanear y efectuar el OCR pÃ¡gina a pÃ¡gina es un mÃ©todo razonable cuando se trabaja con pocos documentos, resulta muy largo para trabajos mÃ¡s voluminosos y continuos.</Text>
+<Text id="231">Esta soluciÃ³n es adecuada para cantidades entre 100 a 150 pÃ¡gina al mes. Para tratar volÃºmenes superiores, en cambio, es mÃ¡s rÃ¡pido y eficaz escanear en primer lugar el documento y aplicar despuÃ©s el proceso de OCR a todas las pÃ¡ginas de una sola vez.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="three_examples">
+<Title>
+<Text id="232">De 1.000 a 100.000 pÃ¡ginas en tres ejemplos</Text>
+</Title>
+<Content>
+<Section id="typical_small_collection">
+<Title>
+<Text id="233">Una colecciÃ³n de pequeÃ±as dimensiones: de 500 a 1.000 pÃ¡ginas</Text>
+</Title>
+<Content>
+<Text id="234">La mayorÃ­a de las ONG tienen un volumen de 500 a 1.000 pÃ¡ginas por escanear. Si disponen de voluntarios motivados pueden asumir por cuenta propia el proceso de OCR.</Text>
+<Part id="scanning">
+<Title>
+<Text id="235">Escaneado</Text>
+</Title>
+<Content>
+<Text id="236">El primer paso consiste en escanear las publicaciones para generar un archivo TIFF de alta calidad para cada pÃ¡gina y una imagen bitmap independiente (ya sea de dibujo de lÃ­neas simples, escala de grises o color) para cada ilustraciÃ³n. Suponiendo que deban escanearse 1.000 pÃ¡ginas, ello puede equivaler a cerca de un mes de trabajo a tiempo parcial (sÃ³lo para el escaneado). Los archivos TIFF ocuparÃ­an entre 60 y 80 Mb de espacio en el disco duro, por lo que es aconsejable utilizar un CD-ROM para dar cabida a esos archivos. Un escÃ¡ner plano de precio reducido (entre 100 y 300 dÃ³lares) basta para realizar ese trabajo, del que puede ocuparse un voluntario despuÃ©s de la jornada laboral o durante los fines de semana, ya sea en la oficina o en casa.</Text>
+</Content>
+</Part>
+<Part id="ocr">
+<Title>
+<Text id="237">OCR</Text>
+</Title>
+<Content>
+<Text id="238">La segunda etapa es la del proceso de OCR, que se encomendarÃ¡ a otro voluntario, o equipo de voluntarios, con buenos conocimientos lingÃŒÃ­sticos y de correcciÃ³n ortogrÃ¡fica. Cabe la posibilidad de repartir los archivos TIFF entre varias computadoras o bien de utilizar una sola mÃ¡quina para la totalidad del trabajo. Por lo general se requieren entre cinco y seis meses de trabajo a tiempo parcial (a razÃ³n de 20 horas semanales, por ejemplo) para convertir 1.000 pÃ¡ginas en documentos impecables en formato Word o HTML.</Text>
+</Content>
+</Part>
+<Part id="outsourcing">
+<Title>
+<Text id="239">SubcontrataciÃ³n</Text>
+</Title>
+<Content>
+<Text id="240">Una posibilidad alternativa es la de subcontratar los procesos de escaneado y OCR. La conversiÃ³n de todos los documentos en archivos Word y HTML impecables costarÃ­a probablemente entre 1.500 y 2.000 dÃ³lares.</Text>
+</Content>
+</Part>
+</Content>
+</Section>
+<Section id="all_publications_from_an_organization">
+<Title>
+<Text id="241">Todas las publicaciones de una organizaciÃ³n: 5.000 pÃ¡ginas</Text>
+</Title>
+<Content>
+<Text id="242">Los archivos de muchas organizaciones de mayor tamaÃ±o pueden contener unas 5.000 pÃ¡ginas de libros (en catÃ¡logo o agotados), revistas, boletines, documentos, etc.</Text>
+<Part id="scanning_1">
+<Title>
+<Text id="243">Escaneado</Text>
+</Title>
+<Content>
+<Text id="244">Se trata de un volumen excesivo para un escÃ¡ner plano, lo que deja dos opciones: subcontratar el trabajo (contando unos 400 dÃ³lares por 5.000 pÃ¡ginas) o adquirir un escÃ¡ner con alimentador de papel (aproximadamente 900 dÃ³lares). Otra alternativa es que varias instituciones u ONG adquieran conjuntamente un escÃ¡ner mÃ¡s caro (6.000 dÃ³lares, divididos por el nÃºmero de participantes). Las 5.000 pÃ¡ginas en formato TIFF ocuparÃ­an entre 300 y 400 Mb en el disco duro. SeÃ±alemos de nuevo la conveniencia de utilizar un CD-ROM para guardar esos archivos.</Text>
+</Content>
+</Part>
+<Part id="ocr_1">
+<Title>
+<Text id="245">OCR</Text>
+</Title>
+<Content>
+<Text id="246">A continuaciÃ³n hay que ocuparse del proceso de OCR, que puede encargarse a otro voluntario, o equipo de voluntarios, diestro en tÃ©cnicas de OCR y correcciÃ³n ortogrÃ¡fica. Como en el caso anterior, es posible utilizar varias computadoras o una sola para esta tarea. La conversiÃ³n de 5.000 pÃ¡ginas en archivos Word o HTML impecables exigirÃ­a entre 25 y 30 meses de trabajo a tiempo parcial (a razÃ³n de 20 horas semanales), lo que en la prÃ¡ctica descarta el empleo exclusivo de voluntarios porque lleva demasiado tiempo y requiere un uso excesivo de la computadora. Para concluir el trabajo en un plazo razonable y con un buen nivel de calidad habrÃ­a que pagar a los voluntarios, supervisar su rendimiento y la calidad de su labor, proporcionarles espacio adecuado, etc.</Text>
+<Text id="247">Una posibilidad alternativa es la de crear archivos grÃ¡ficos PDF, que ocuparÃ­an entre 300 y 400 Mb de memoria y resultarÃ­an mÃ¡s difÃ­ciles de descargar de Internet.</Text>
+</Content>
+</Part>
+<Part id="outsourcing_1">
+<Title>
+<Text id="248">SubcontrataciÃ³n</Text>
+</Title>
+<Content>
+<Text id="249">Otra alternativa es la de subcontratar los procesos de escaneado y OCR, lo que costarÃ­a probablemente entre 7.500 y 10.000 dÃ³lares.</Text>
+</Content>
+</Part>
+</Content>
+</Section>
+<Section id="a_small_library">
+<Title>
+<Text id="250">Una pequeÃ±a biblioteca: 100.000 pÃ¡ginas</Text>
+</Title>
+<Content>
+<Text id="251">Otras entidades de mayor envergadura, universidades, gobiernos o bibliotecas especializadas podrÃ­an tener una biblioteca entera por digitalizar, algo asÃ­ como unas 100.000 pÃ¡ginas. Lo primero que se debe tener en cuenta es la situaciÃ³n de las publicaciones en materia de derecho de autor: bien estÃ¡n incluidas en el dominio pÃºblico o bien hay que obtener permiso explÃ­cito de los titulares de los derechos para poder digitalizarlas. Conviene cerciorarse asimismo de que los documentos no existen ya en formato electrÃ³nico.</Text>
+<Part id="scanning_2">
+<Title>
+<Text id="252">Escaneado</Text>
+</Title>
+<Content>
+<Text id="253">100.000 pÃ¡ginas son demasiadas para un escÃ¡ner con alimentador de papel, por lo que caben dos opciones: subcontratar el trabajo (a unos 8.000 dÃ³lares las 100.000 pÃ¡ginas) o adquirir, conjuntamente con otras instituciones u ONG, un equipo de mayor calidad y precio (6.000 dÃ³lares, divididos entre los participantes). 100.000 pÃ¡ginas en formato TIFF ocuparÃ¡n entre 6 y 8 Gb en el disco duro. Lo ideal es crear copias de esos archivos en discos CD-ROM.</Text>
+</Content>
+</Part>
+<Part id="ocr_2">
+<Title>
+<Text id="254">OCR</Text>
+</Title>
+<Content>
+<Text id="255">La segunda etapa es el proceso de OCR (en el caso de documentos menos utilizados, tambiÃ©n cabe la posibilidad de crear archivos PDF). Convertir 100.000 pÃ¡ginas en archivos Word o HTML impecables llevarÃ­a entre 500 y 700 meses de trabajo a tiempo parcial, lo que a todas luces descarta el uso de voluntarios para esta tarea, mÃ¡s propia de profesionales.</Text>
+<Text id="256">Para ahorrar costos se pueden convertir en PDF algunas de las pÃ¡ginas menos utilizadas (digamos el 80%, u 80.000 pÃ¡ginas), reservando los formatos Word o HTML para las 20.000 pÃ¡ginas restantes. Los archivos PDF ocuparÃ­an entre 4 y 6 Gb de espacio y no serÃ­a fÃ¡cil descargarlos de Internet, pero en cambio saldrÃ­an baratos si los creara una empresa especializada (sÃ³lo 0,2 dÃ³lares por pÃ¡gina, lo que supone un costo total de 16.000 dÃ³lares). Utilizando voluntarios para crear 80.000 archivos PDF a partir de archivos TIFF mediante programas de conversiÃ³n como Acrobat de Adobe se precisarÃ­an 10 a 20 meses de trabajo a tiempo parcial con una computadora de gran potencia.</Text>
+</Content>
+</Part>
+<Part id="outsourcing_2">
+<Title>
+<Text id="257">SubcontrataciÃ³n</Text>
+</Title>
+<Content>
+<Text id="258">Una posible alternativa es la de subcontratar el trabajo. Suponiendo que se mantuviera la mencionada proporciÃ³n del 80% en PDF y el 20% en HTML, los archivos PDF costarÃ­an unos 16.000 dÃ³lares y los archivos HTML entre 30.000 y 40.000 dÃ³lares, con lo que el presupuesto total ascenderÃ­a a unos 50.000 dÃ³lares. Si se sometieran todos los documentos a un proceso de OCR, convertir toda la colecciÃ³n en archivos Word y HTML impecables costarÃ­a entre 150.000 y 200.000 dÃ³lares.</Text>
+</Content>
+</Part>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="creating_an_electronic_collection">
+<Title>
+<Text id="259">CreaciÃ³n de una colecciÃ³n digital</Text>
+</Title>
+<Content>
+<Text id="260">Hay tres aspectos importantes que conviene tener en cuenta a la hora de crear una colecciÃ³n digital. En primer lugar es preciso organizarla. A mayor volumen de contenido, mayor necesidad hay de Ã­ndices y sistemas potentes de bÃºsqueda, indispensables cuando la colecciÃ³n supera las 3.000 a 5.000 pÃ¡ginas. En segundo lugar, deben prevalecer las necesidades del usuario final. Es preciso identificar los grupos que usarÃ¡n la colecciÃ³n y establecer un proceso de consulta periÃ³dica con ellos. En tercer lugar, el presupuesto disponible determinarÃ¡ quÃ© tanto se puede hacer.</Text>
+<Section id="methods_of_collection_building">
+<Title>
+<Text id="261">MÃ©todos para crear colecciones</Text>
+</Title>
+<Content>
+<Text id="262">Abundan los ejemplos de excelentes CD-ROM elaborados siguiendo el modelo de una pÃ¡gina Web, en la que por medio de hipervÃ­nculos se insertan y enlazan entre sÃ­ documentos en formato HTML, PDF o Word. El uso de hipervÃ­nculos, marcos y grupos estructurados, palabras clave, Ã­ndices y demÃ¡s elementos de este tipo hace fÃ¡cil y atractiva la navegaciÃ³n. Estos sistemas funcionan bien con volÃºmenes de unos cuantos miles de pÃ¡ginas, pero a partir de 3.000 a 5.000 pÃ¡ginas es importante que la colecciÃ³n estÃ© bien organizada y ofrezca un dispositivo de bÃºsqueda potente. AhÃ­ es donde el programa Greenstone puede resultar de utilidad.</Text>
+<Text id="263">El programa Greenstone crea una biblioteca digital estructurada y provista de un poderoso buscador y un mecanismo de recuperaciÃ³n. Es posible indexar hasta 150,000 pÃ¡ginas en un solo CD-ROM, que ademÃ¡s puede funcionar como servidor de Internet. Greenstone es un software de cÃ³digo fuente abierto y por lo tanto puede obtenerse gratuitamente bajo las condiciones estipuladas en la Licencia PÃºblica General de GNU.</Text>
+<Text id="264">En los manuales de consulta que acompaÃ±an al programa se explica cÃ³mo crear colecciones Greenstone. BÃ¡sicamente existen tres formas de hacerlo.</Text>
+<BulletList>
+<Bullet>
+<Text id="265">Con la interfaz de bibliotecario</Text>
+</Bullet>
+<Bullet>
+<Text id="266">Con el programa de recopilaciÃ³n, tambiÃ©n conocido como Colector</Text>
+</Bullet>
+<Bullet>
+<Text id="267">Crearlas desde la lÃ­nea de comandos.</Text>
+</Bullet>
+</BulletList>
+<Text id="268">El primer mÃ©todo corresponde a la interfaz de bibliotecario descrita laÂ <i>GuÃ­a del Usuario de la Biblioteca Digital Greenstone</i>Â (CapÃ­tulo 3, âCreando colecciones Greenstoneâ). Ãsta es una herramienta interactiva para la creaciÃ³n de colecciones que permite reunir grupos de documentos, importar o asignar metadatos e integrarlos a una colecciÃ³n. El segundo mÃ©todo es el subsistema de recopilaciÃ³n descrito en el CapÃ­tulo 4 de laÂ <i>GuÃ­a del Usuario</i>Â llamado âColectorâ. Se trata de una herramienta que aparece en versiones anteriores y ofrece una alternativa para la creaciÃ³n de colecciones de pÃ¡ginas web u otros documentos, guiÃ¡ndolo a travÃ©s de una secuencia de pÃ¡ginas Web interactivas que solicitan la informaciÃ³n conforme vaya siendo necesaria. No obstante, no proporciona ninguna forma de agregar metadatos a los documentos y, debido a su interfaz Web, no es realmente adecuada para colecciones cuya construcciÃ³n requiera mÃ¡s de unos cuantos minutos. El tercer mÃ©todo es ejecutar los programas que permiten construir la colecciÃ³n directamente desde la lÃ­nea de comandos que se encuentra en el CapÃ­tulo 1 de laÂ <i>GuÃ­a del Programador de la Biblioteca Digital Greenstone</i>. Este mÃ©todo le ofrece una mayor flexibilidad para ejecutar los programas de manera individual y le ahorra los pasos intermedios que quizÃ¡ fueran deseables para colecciones que requirieran de muchas horas en su construcciÃ³n. TambiÃ©n necesitarÃ¡ leer el CapÃ­tulo 2 con el fin de aprovechar todo el poder que le ofrece Greenstone para la creaciÃ³n de colecciones avanzadas.</Text>
+<Text id="269">Existe una cuarta herramienta para crear y editar el material asociado a una colecciÃ³n llamada Organizador. Sin embargo, sus funciones han sido sustituidas por las de la interfaz de bibliotecario mencionada arriba. Este mÃ©todo se describe en el documento tituladoÂ <i>Uso del Organizador.</i>
+</Text>
+</Content>
+</Section>
+<Section id="getting_started_in_seven_steps_and_15_minutes">
+<Title>
+<Text id="270">Aprendiendo a usar la interfaz en siete pasos y 15 minutos</Text>
+</Title>
+<Content>
+<Text id="271">La mejor forma de conocer las caracterÃ­sticas y el funcionamiento de la interfaz de bibliotecario Â es crear una pequeÃ±a biblioteca de prueba. Si dispone de 15 minutos, por favor siga los pasos que se indican a continuaciÃ³n y asÃ­ usted obtendrÃ¡ una mejor comprensiÃ³n de este programa.</Text>
+<Text id="272">Antes de empezar lo primero que deberÃ¡ hacer es instalar Greenstone (vea laÂ <i>GuÃ­a de InstalaciÃ³n</i>), el cual incluye una colecciÃ³n de muestra en formato DLS y sus archivos fuente.Â <b>Recuerde, si desea aÃ±adir a su colecciÃ³n cualquiera de los 140 documentos de la colecciÃ³n DLS completa (en vez de sÃ³lo los 11 de esta colecciÃ³n de muestra) tambiÃ©n deberÃ¡ instalar la DLS como una de las bibliotecas Greenstone de muestra.</b>Â Las colecciones de muestra y DLS se instalarÃ¡n enÂ <i>C:\Program Files\gsdl\collect</i>, en los subdirectoriosÂ <i>demo</i>Â yÂ <i>dls</i>Â respectivamente. Si anteriormente usted ya instalÃ³ Greenstone sin la colecciÃ³n DLS y desea instalarla ahora, sÃ³lo tiene que insertar nuevamente el CD-ROM Greenstone y aÃ±adir la colecciÃ³n. No es necesario desinstalar Greenstone primero.</Text>
+<Text id="273">Le sugerimos que imprima las instrucciones que aparecen a continuaciÃ³n y las siga paso a pasoÂ :</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="274">Para iniciar la interfaz bajo Windows seleccioneÂ <i>Biblioteca Digital Greenstone</i>Â en la secciÃ³n deÂ <i>Programas</i>Â del menÃº deÂ <i>Inicio</i>Â y elijaÂ <i>Interfaz de Bibliotecario</i>Si en vez de Windows usted estÃ¡ usando UNIX escriba:</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<CodeLine>cd gli</CodeLine>
+<CodeLine>./gli.sh</CodeLine>
+<Text id="275">dondeÂ <i>~/gsdl</i>Â es el directorio que contiene su sistema Greenstone.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="276">SeleccioneÂ <i>Nueva</i>Â en el menÃº Archivo que se encuentra en la barra horizontal en la parte superior de la ventana. Dele un tÃ­tulo, por ejemplo âMi primera colecciÃ³nâ y escriba su direcciÃ³n de correo electrÃ³nico y una breve descripciÃ³n de la colecciÃ³n. En el menÃº âBasar esta colecciÃ³n enâ elija âcolecciÃ³n de muestra Greenstoneâ o âSubconjunto de la Biblioteca para el Desarrolloâ (DLS por sus siglas en inglÃ©s). El efecto es el mismo, ya que ambas colecciones tienen la misma estructura.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="277">AÃ±ada algunos documentos de la colecciÃ³n de muestra (o de la colecciÃ³n DLS si estÃ¡ instalada) a su nueva colecciÃ³n. Para ello haga doble click en la carpeta deÂ <i>Colecciones Greenstone</i>Â en el cuadro izquierdo y a continuaciÃ³n haga doble click en la colecciÃ³n que prefiera. Los documentos que hay en ella aparecerÃ¡n en pantalla. Seleccione uno, arrÃ¡strelo y colÃ³quelo en el cuadro derecho. Este panel representa la colecciÃ³n que estÃ¡ construyendo. Elija varios documentos y arrÃ¡strelos uno por uno o seleccione y arrastre varios de ellos al mismo tiempo de la manera normal.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="278">Agregue algunos de sus propios documentos que no estÃ©n en la colecciÃ³n de muestra o en la DLS. Cierre la carpeta deÂ <i>Colecciones Greenstone</i>Â en el cuadro izquierdo y haga doble click en la carpetaÂ <i>Local Filespace (Espacio de archivo local)</i>Vaya a un directorio que contenga algunos documentos (p. ej. pequeÃ±os archivos de Word o HTML) y arrastre unos cuantos de ellos al cuadro derecho para incluirlos en su colecciÃ³n.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="279">AÃ±ada metadatos a los documentos de su colecciÃ³n. Hasta este momento usted ha estado operando en el panel indicado por medio de la pestaÃ±aÂ <i>Gather (Reunir)</i>Â que se encuentra debajo de la barra de menÃºs horizontal en la parte superior de la ventana. Haga click en la pestaÃ±aÂ <i>Enrich (Enriquecer)</i>Â que se encuentra a un lado. Los documentos de su colecciÃ³n aparecerÃ¡n ahora en el cuadro del lado izquierdo. Haga click en uno y examine los metadatos asociados a Ã©l que se muestran en la tablaÂ <i>âElement ... Valueâ (Elemento ... Valor)</i>Â en la parte superior derecha. Use el cuadro que estÃ¡ debajo para cambiar los valores individuales seleccionando el elemento que desee y escogiendo un valor existente de la lista o escribiendo un nuevo valor en el recuadro que se encuentra cerca de la parte inferior. AÃ±ada los metadatosÂ <i>TÃ­tulo</i>,Â <i>OrganizaciÃ³n</i>Â yÂ <i>Palabra clave</i>Â para cada uno de sus documentos que quiera poner en la colecciÃ³n. DespuÃ©s de escribir cada valor usted necesitarÃ¡ hacer click enÂ <i>âAppendâ (Agregar)</i>Â para guardar dicho valor.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="280">Haga click en la pestaÃ±aÂ <i>Create (Crear)</i>Â para salir del modoÂ <i>Enriquecer</i>Â y crear su nueva colecciÃ³n. Haga click en el botÃ³nÂ <i>Build Collection (Construir la colecciÃ³n)</i>Â que se encuentra en la parte inferior. Conforme la computadora va construyendo la colecciÃ³n usted recibirÃ¡ informaciÃ³n sobre lo que estÃ¡ haciendo.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="281">Una vez que haya terminado haga click en la pestaÃ±aÂ <i>Preview (Vista previa)</i>Â para ver la colecciÃ³n desde el interior de la interfaz de bibliotecario. Revise las listas deÂ <i>tÃ­tulos de la âaâ la âzâ</i>,Â <i>organizaciones</i>Â yÂ <i>cÃ³mo hacer</i>Â para asegurarse de que sus documentos han sido incluidos en la colecciÃ³n. Asimismo cuando visite su pÃ¡gina principal de Greenstone usted encontrarÃ¡ que la colecciÃ³n ha sido instalada como una de las colecciones regulares.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="282">Todos los importes indicados en este documento se expresan en dÃ³lares estadounidenses y corresponden a las tarifas vigentes en 2001.</Text>
+</Footnote>
+<Footnote id="2">
+<Text id="283">Recordemos que todos los importes estÃ¡n expresados en dÃ³lares estadounidenses de 2001 y corresponden a las tarifas vigentes en 2001.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/es/User_es.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/es/User_es.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/es/User_es.xml	(revision 13632)
@@ -0,0 +1,2504 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">BIBLIOTECA DIGITAL GREENSTONE</Text>
+</Heading>
+<Title>
+<Text id="2">GUÃA DEL USUARIO</Text>
+</Title>
+<Author>
+<Text id="3">Ian H. Witten, Stefan Boddie y John Thompson</Text>
+</Author>
+<Affiliation>
+<Text id="4">Departamento de InformÃ¡ticaÂ <br/>Universidad de Waikato, Nueva Zelanda</Text>
+<Text id="5">Greenstone es un conjunto de programas y aplicaciones de software especialmente diseÃ±ados para la creaciÃ³n y difusiÃ³n de colecciones documentales digitales, el cual le ofrece una nueva forma de organizar la informaciÃ³n y publicarla en Internet o CD-ROM. Greenstone ha sido elaborado como parte del proyecto de Biblioteca Digital de Nueva Zelanda de la Universidad de Waikato y actualmente es desarrollado y distribuido en colaboraciÃ³n con la UNESCO y la ONG Human Info. Es un software de cÃ³digo abierto disponible enÂ <i>http://greenstone.org</i>Â bajo los tÃ©rminos y condiciones de la Licencia PÃºblica General de GNU.</Text>
+</Affiliation>
+<Comment>
+<Text id="6">Queremos estar seguros que este software trabaje bien para usted. Por favor comunÃ­quenos cualquier problema que tenga con Ã©l a la siguiente direcciÃ³n: <i> greenstone@cs.waikato.ac.nz</i></Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.70</Text>
+</Version>
+<Date>
+<Text id="8">Marzo de 2006</Text>
+</Date>
+<Section id="acknowledgements">
+<Title>
+<Text id="9">Acerca de este manual</Text>
+</Title>
+<Content>
+<Text id="10">Este manual ofrece una descripciÃ³n completa de la manera de utilizar el programa Greenstone para crear y tener acceso a colecciones de bibliotecas digitales.</Text>
+<Text id="11">En la SecciÃ³n <CrossRef target="Chapter" ref="overview_of_greenstone"/> se da una visiÃ³n general de las posibilidades del programa. En la SecciÃ³n <CrossRef target="Chapter" ref="using_greenstone_collections"/> se explica cÃ³mo utilizar las colecciones de Greenstone. La interfaz es lo suficientemente explÃ­cita y la mejor manera de aprender es utilizÃ¡ndola; esta secciÃ³n comprende la informaciÃ³n de ayuda en lÃ­nea para una colecciÃ³n tÃ­pica. En la SecciÃ³n <CrossRef target="Chapter" ref="making_greenstone_collections"/> se explica la forma de crear su propia colecciÃ³n bibliogrÃ¡fica utilizando la Interfaz de Bibliotecario de Greenstone. En la SecciÃ³n <CrossRef target="Chapter" ref="administration"/> se presenta la utilerÃ­a de administraciÃ³n, que le permite al administrador del sistema seguir de cerca el proceso y controlar las autorizaciones para la creaciÃ³n de colecciones.</Text>
+<Text id="12">En los apÃ©ndices se enumeran las caracterÃ­sticas del programa Greenstone y se presenta un glosario de los tÃ©rminos utilizados en la documentaciÃ³n de Greenstone.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="13">Conjunto de documentos</Text>
+</Title>
+<Content>
+<Text id="14">La serie completa de documentos comprende cuatro volÃºmenes:</Text>
+<BulletList>
+<Bullet>
+<Text id="15">La GuÃ­a de InstalaciÃ³n de la Biblioteca Digital Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">La GuÃ­a del Usuario de la Biblioteca Digital Greenstone (<i>el presente documento</i>)</Text>
+</Bullet>
+<Bullet>
+<Text id="17">La GuÃ­a del Programador de la Biblioteca Digital Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="18">La Biblioteca Digital Greenstone: del Papel a la ColecciÃ³n</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">Agradecimientos</Text>
+</Title>
+<Content>
+<Text id="20">El programa Greenstone es fruto de la colaboraciÃ³n de muchas personas. Rodger McNab y Stefan Boddie son los principales arquitectos y programadores. TambiÃ©n han contribuido David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson y Stuart Yeates. Otros miembros del proyecto Biblioteca Digital de Nueva Zelanda que proporcionaron asesorÃ­a y valiosas ideas para la concepciÃ³n del sistema son: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols y Lloyd Smith. TambiÃ©n queremos dar las gracias a todos aquellos que contribuyeron a los paquetes de programas con licencias GNU incluidos en esta distribuciÃ³n: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE y XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="overview_of_greenstone">
+<Title>
+<Text id="21">VISIÃN GENERAL DE GREENSTONE</Text>
+</Title>
+<Content>
+<Text id="22">Greenstone es un sistema completo de creaciÃ³n y presentaciÃ³n de colecciones compuestas de miles o millones de documentos, que incluyen texto, imÃ¡genes, sonido y vÃ­deo.</Text>
+<Section id="collections">
+<Title>
+<Text id="23">Las colecciones</Text>
+</Title>
+<Content>
+<Text id="24">Una biblioteca digital tÃ­pica creada con Greenstone contendrÃ¡ muchas colecciones, organizadas individualmente, pero muy parecidas entre sÃ­. De fÃ¡cil mantenimiento, las colecciones pueden aumentarse y reorganizarse automÃ¡ticamente.</Text>
+<Text id="25">En la mayorÃ­a de las colecciones Greenstone hay varias maneras de encontrar informaciÃ³n. Por ejemplo, se puedenÂ <i>buscar palabras especÃ­ficas</i>Â que aparecen en un texto o en una secciÃ³n de un documento. Se puedenÂ <i>consultar documentos por tÃ­tulo</i>Â ; basta con hacer clic en un libro para poder leerlo. Se puedenÂ <i>consultar documentos por tema</i>. Los temas estÃ¡n representados por estantes; basta con hacer clic en un estante para ver los libros. Cuando procede, los documentos vienen acompaÃ±ados de un Ã­ndice: se puede entonces hacer clic en un capÃ­tulo o una subsecciÃ³n para abrirlo, visualizar el Ã­ndice completo o presentar el documento Ã­ntegro en la ventana de su navegador (lo cual es Ãºtil para la impresiÃ³n). El sitio Web de la Biblioteca Digital de Nueva Zelanda (Â <i>nzdl.org</i>) ofrece numerosos ejemplos de colecciones.</Text>
+<Text id="26">En la primera plana de cada colecciÃ³n se indica su objetivo y cobertura, y se explica su organizaciÃ³n. Se puede tener acceso a la mayorÃ­a de las colecciones mediante las funciones deÂ <i>bÃºsqueda</i>Â yÂ <i>consulta</i>. En la bÃºsqueda, el programa Greenstone examina el texto completo de todos los documentos incluidos en la colecciÃ³n (esto se denomina âbÃºsqueda en texto completoâ). En la mayorÃ­a de las colecciones los usuarios pueden escoger entre los Ã­ndices creados sobre la base de diferentes partes de los documentos. Algunas colecciones disponen de un Ã­ndice de documentos completos, un Ã­ndice de los pÃ¡rrafos y un Ã­ndice de los tÃ­tulos, en los que se pueden buscar determinadas palabras o frases. De este modo, se pueden encontrar todos los documentos que contienen un conjunto especÃ­fico de palabras (las palabras pueden estar dispersas en todo el documento), o todos los pÃ¡rrafos que contienen ese conjunto de palabras (que deben aparecer todas en el mismo pÃ¡rrafo), o todos los documentos cuyo tÃ­tulo contiene las palabras buscadas (todas las palabras deben aparecer en el tÃ­tulo del documento). Puede haber otros Ã­ndices, por ejemplo un Ã­ndice de secciones y un Ã­ndice de encabezados de secciones. Durante el proceso de consulta el usuario examina unas listas: listas de autores, listas de tÃ­tulos, listas de fechas, estructuras de clasificaciÃ³n jerÃ¡rquica, etc. Las diferentes colecciones ofrecen diferentes posibilidades de consulta.</Text>
+</Content>
+</Section>
+<Section id="finding_information">
+<Title>
+<Text id="27">BÃºsqueda de informaciÃ³n</Text>
+</Title>
+<Content>
+<Text id="28">Greenstone crea Ã­ndices de texto completo a partir del texto del documento, es decir, Ã­ndices que permiten buscar cualquier palabra en el texto completo del documento. Se pueden buscar en los Ã­ndices determinadas palabras, combinaciones de palabras, o frases, y los resultados se ordenan segÃºn su pertinencia con respecto a la consulta formulada.</Text>
+<Text id="29">En la mayorÃ­a de las colecciones, los datos descriptivos, como el autor, el tÃ­tulo, la fecha, las palabras clave, etc., se asocian a cada documento. Esta informaciÃ³n se denominaÂ <i>metadatos</i>. Muchas colecciones tambiÃ©n contienen Ã­ndices de texto completo de algunos tipos de metadatos. Por ejemplo, muchas colecciones tienen un Ã­ndice de tÃ­tulos de documentos que permite la bÃºsqueda.</Text>
+<Text id="30">Los usuarios pueden consultar de forma interactiva las listas y estructuras jerÃ¡rquicas que se generan a partir de los metadatos asociados con cada documento de la colecciÃ³n. Los metadatos forman la materia prima para la consulta. Se los debe suministrar explÃ­citamente o deben poder derivarse automÃ¡ticamente de los propios documentos. Cada colecciÃ³n ofrece distintas funciones de bÃºsqueda y de consulta. Los Ã­ndices para la bÃºsqueda y la consulta se constituyen durante un proceso de âcreaciÃ³nâ, con arreglo a la informaciÃ³n que figura en el archivo de configuraciÃ³n de la colecciÃ³n.</Text>
+<Text id="31">Greenstone crea todas las estructuras de Ã­ndices automÃ¡ticamente a partir de los documentos y los archivos conexos; nada se hace manualmente. Si se aÃ±aden nuevos documentos con el mismo formato, se los puede incorporar a la colecciÃ³n automÃ¡ticamente. En efecto, en muchas colecciones esto se lleva a cabo mediante procesos que se ponen en marcha periÃ³dicamente, localizan el material nuevo y reconstituyen los Ã­ndices, todo ello sin ninguna intervenciÃ³n manual.</Text>
+</Content>
+</Section>
+<Section id="document_formats">
+<Title>
+<Text id="32">Formatos de documentos</Text>
+</Title>
+<Content>
+<Text id="33">Los documentos de origen se presentan en diversos formatos y se convierten a un formato normalizado xml para la indexaciÃ³n mediante plugins. Los plugins distribuidos con Greenstone tratan documentos en texto sin formato, HTML, word y pdf, y los mensajes Usenet y de correo electrÃ³nico. Pueden escribirse nuevos plugins para distintos tipos de documentos (para ello es necesario consultar laÂ <i>GuÃ­a del Programador de la Biblioteca Digital Greenstone</i>). Para crear estructuras de consulta a partir de metadatos, se utiliza un sistema anÃ¡logo de âclasificadoresâ. Ãstos crean Ã­ndices de consulta de diversos tipos: listas desplegables, selectores alfabÃ©ticos, fechas y jerarquÃ­as arbitrarias. Una vez mÃ¡s, los programadores Greenstone pueden crear nuevas estructuras de consulta.</Text>
+</Content>
+</Section>
+<Section id="multimedia_and_multilingual_documents">
+<Title>
+<Text id="34">Documentos multimedia y plurilingÃŒes</Text>
+</Title>
+<Content>
+<Text id="35">Las colecciones pueden contener texto, imÃ¡genes, sonido y vÃ­deo. Los contenidos no textuales se enlazan con los documentos textuales o se acompaÃ±an de descripciones textuales (como las leyendas de las figuras) para poder buscar y consultar en modo de texto completo.</Text>
+<Text id="36">Greenstone utiliza constantemente Unicode, un sistema normalizado para la representaciÃ³n de los conjuntos de caracteres empleados en los idiomas del mundo. Ello permite tratar y presentar cualquier idioma de manera uniforme. Se han creado colecciones que contienen textos en Ã¡rabe, chino, inglÃ©s, francÃ©s, maorÃ­ y espaÃ±ol. Las colecciones plurilingÃŒes disponen de una funciÃ³n de reconocimiento automÃ¡tico de idioma y la interfaz estÃ¡ disponible en todos los idiomas antes mencionados (entre otros).</Text>
+</Content>
+</Section>
+<Section id="distributing_greenstone">
+<Title>
+<Text id="37">DistribuciÃ³n de Greenstone</Text>
+</Title>
+<Content>
+<Text id="38">Las colecciones pueden consultarse en Internet o estÃ¡n publicadas, en forma idÃ©ntica, en un CD-ROM que se instala automÃ¡ticamente en computadoras equipadas con Windows. El texto y los Ã­ndices estÃ¡n compactados y un protocolo Corba permite administrar las colecciones distribuidas y las interfaces de consultas grÃ¡ficas.</Text>
+<Text id="39">La Biblioteca Digital de Nueva Zelanda (<i>nzdl.org</i>) ofrece muchos ejemplos de colecciones, entre ellas de documentos histÃ³ricos, informaciÃ³n humanitaria y sobre desarrollo, informes tÃ©cnicos y bibliografÃ­as, obras literarias y publicaciones periÃ³dicas. </Text>
+<Text id="40">Por ser un programa de cÃ³digo fuente abierto, Greenstone puede ampliarse fÃ¡cilmente e incorporar mÃ³dulos sujetos a la Licencia PÃºblica General de GNU para la recuperaciÃ³n de informaciÃ³n en texto completo, la gestiÃ³n de bases de datos y la extracciÃ³n de texto a partir de formatos de documentos patentados. SÃ³lo mediante una cooperaciÃ³n internacional se lograrÃ¡ que los programas de biblioteca digital sean lo suficientemente completos para responder a las necesidades mundiales con la riqueza y la flexibilidad que los usuarios merecen.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="using_greenstone_collections">
+<Title>
+<Text id="41">UtilizaciÃ³n de las colecciones Greenstone</Text>
+</Title>
+<Content>
+<Text id="42">El programa Greenstone se concibiÃ³ para utilizarse con facilidad. Las interfaces de las colecciones son idÃ©nticas, tanto en la Web como en los CD-ROM. Es muy fÃ¡cil instalar Greenstone a partir de un CD-ROM en cualquier computadora equipada de Windows o Linux; se utiliza un programa de instalaciÃ³n normalizado y unos binarios precompilados. Una colecciÃ³n puede consultarse a partir de la computadora local en que estÃ¡ instalada; por otra parte, si la computadora estÃ¡ conectada a una red, el programa permite de forma automÃ¡tica y transparente el acceso a esa misma colecciÃ³n desde todas las demÃ¡s computadoras de la red.</Text>
+<Text id="43">En la siguiente secciÃ³n se explica cÃ³mo instalar un CD-ROM de Greenstone. A continuaciÃ³n, veremos las funciones de bÃºsqueda y consulta que ofrece una colecciÃ³n Greenstone representativa: la colecciÃ³n de âdemostraciÃ³nâ que viene con el programa Greenstone. Las demÃ¡s colecciones ofrecen las mismas funciones: saber utilizar una es saber utilizarlas todas. En la Ãºltima secciÃ³n se explica de quÃ© manera adaptar la interfaz a las necesidades propias, utilizando la pÃ¡gina de Preferencias.</Text>
+<Section id="using_a_greenstone_cd-rom">
+<Title>
+<Text id="44">UtilizaciÃ³n de un CD-ROM de Greenstone</Text>
+</Title>
+<Content>
+<Text id="45">El programa de Biblioteca Digital Greenstone propiamente dicho viene en un CD-ROM, y usted o el administrador de sistemas probablemente ya lo habrÃ¡ instalado en su sistema, siguiendo las instrucciones de laÂ <i>GuÃ­a de InstalaciÃ³n de la Biblioteca Digital Greenstone</i>. Si Greenstone ya estÃ¡ instalado en su computadora, no necesita leer el resto de esta secciÃ³n y puede pasar directamente a la siguiente.</Text>
+<Text id="46">Algunas colecciones Greenstone vienen en un CD-ROM Greenstone autÃ³nomo, que contiene los archivos de programa suficientes para utilizar Ãºnicamente esa colecciÃ³n. Basta sencillamente con insertar el CD-ROM en el lector correspondiente de una computadora con un sistema Windows. Es muy probable (si la computadora admite la funciÃ³n âejecuciÃ³n automÃ¡ticaâ), que aparezca una ventana en que se le invita a instalar el programa Greenstone. De no ser asÃ­, localice el lector de CD-ROM (en los sistemas Windows actuales puede encontrarlo haciendo clic en el icono âMi PCâ sobre el Escritorio), haga clic dos veces en Ã©l y despuÃ©s en el archivoÂ <i>Setup.exe</i>Â que se encuentra dentro. Se activarÃ¡ asÃ­ el programaÂ <i>Setup</i>Â de Greenstone, que lo guiarÃ¡ durante el proceso de instalaciÃ³n. En la mayorÃ­a de los casos, los usuarios responden âsÃ­â a todas las preguntas.</Text>
+<Text id="47">Al final del procedimiento de instalaciÃ³n, encontrarÃ¡ la biblioteca en el submenÃºÂ <i>Programas</i>Â del menÃºÂ <i>Inicio</i>Â de Windows, con el nombre de la colecciÃ³n (por ejemplo, âBiblioteca para el desarrolloâ o âUniversidad de las Naciones Unidasâ).</Text>
+<Text id="48">Una vez instalado el programa, se entrarÃ¡ automÃ¡ticamente en la biblioteca cada vez que vuelva a insertar el CD-ROM, siempre que estÃ© activada la funciÃ³n de ejecuciÃ³n automÃ¡tica.</Text>
+</Content>
+</Section>
+<Section id="finding_information_1">
+<Title>
+<Text id="49">BÃºsqueda de informaciÃ³n</Text>
+</Title>
+<Content>
+<Text id="50">La manera mÃ¡s fÃ¡cil de aprender a utilizar una colecciÃ³n de Greenstone es ejercitÃ¡ndose. No se preocupe, no va a romper nada. Pulse libremente: se puede hacer clic en la mayorÃ­a de las imÃ¡genes que aparecen en la pantalla. Si se mantiene el cursor quieto sobre una imagen, en la mayorÃ­a de los navegadores aparece un mensaje en que se explica lo que sucederÃ¡ si se hace clic.</Text>
+<Text id="51">Â¡Experimente! Busque palabras comunes como âtheâ (el) y âandâ (y) para obtener con certeza respuestas, y no tema, que nada se va a romper.</Text>
+<Text id="52">Los sistemas de bibliotecas digitales Greenstone suelen comprender varias colecciones independientes: por ejemplo, informes tÃ©cnicos de informÃ¡tica, obras literarias, preguntas mÃ¡s frecuentes en Internet, publicaciones periÃ³dicas. El sistema de biblioteca digital dispondrÃ¡ de una pÃ¡gina principal que le permitirÃ¡ tener acceso a cualquier colecciÃ³n puesta a disposiciÃ³n del pÃºblico; ademÃ¡s, cada colecciÃ³n tiene su propia pÃ¡gina âAcerca deâ que le darÃ¡ informaciÃ³n sobre la organizaciÃ³n de la colecciÃ³n y los principios por los que se rige su contenido. Para volver a la pÃ¡gina âAcerca deâ en cualquier momento, basta con hacer clic en el icono âColecciÃ³nâ que aparece en la parte superior izquierda de todas las pÃ¡ginas de bÃºsqueda y consulta.</Text>
+<Text id="53">En la Figura 1 se muestra una imagen de pantalla de la colecciÃ³n de demostraciÃ³n que viene con el programa Greenstone, y que representa un subconjunto muy pequeÃ±o de la colecciÃ³n de bibliotecas para el desarrollo; utilizaremos este documento como ejemplo para explicar las diferentes formas de encontrar informaciÃ³n. Si no puede encontrar la colecciÃ³n de demostraciÃ³n, use en su lugar el Subconjunto de biblioteca para el desarrollo, su aspecto es el mismo. En primer lugar, se puede hacer clic en casi todos los iconos. Varios iconos aparecen en la parte superior de, prÃ¡cticamente, todas las pÃ¡ginas. En el Cuadro 1 se explica su significado.</Text>
+<Figure id="using_the_demo_collection">
+<Title>
+<Text id="54">UtilizaciÃ³n de la colecciÃ³n de demostraciÃ³n</Text>
+</Title>
+<File width="529" height="227" url="images/User_Fig_1.png"/>
+</Figure>
+<Table id="what_the_icons_at_the_top_of_each_page_mean">
+<Title>
+<Text id="55">Significado de los iconos en la parte superior de cada pÃ¡gina</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<File width="144" height="66" url="images/User_Icon_1.gif"/>
+</th>
+<th width="397">
+<Text id="56">Esto lo lleva a la pÃ¡gina âacerca deâ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<File width="65" height="20" url="images/User_Icon_2.gif"/>
+</th>
+<th width="397">
+<Text id="57">Esto le lleva a la pÃ¡gina principal de la biblioteca digital, a partir de la cual se puede seleccionar otra colecciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<File width="46" height="20" url="images/User_Icon_3.gif"/>
+</th>
+<th width="397">
+<Text id="58">Esto le ofrece un texto de ayuda semejante al que estÃ¡ leyendo en este momento</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<File width="87" height="20" url="images/User_Icon_4.gif"/>
+</th>
+<th width="397">
+<Text id="59">Esto le permite seleccionar algunas opciones de interfaz de usuario y de bÃºsqueda que se utilizarÃ¡n en adelante</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="60">La barra horizontal âÂ <i>buscar ... temas ... tÃ­tulos a-z ... organizaciones ... cÃ³mo</i>Â â da acceso a las funciones de bÃºsqueda y consulta. El botÃ³n a la izquierda sirve para la bÃºsqueda y los que estÃ¡n a su derecha (que en esta colecciÃ³n son cuatro) indican diferentes funciones de consulta. Estos Ãºltimos cuatro botones pueden ser diferentes de una colecciÃ³n a otra.</Text>
+<Subsection id="how_to_find_information">
+<Title>
+<Text id="61">CÃ³mo encontrar informaciÃ³n</Text>
+</Title>
+<Content>
+<Text id="62">En el cuadro 2 se muestran las cinco maneras de encontrar informaciÃ³n en la colecciÃ³n de demostraciÃ³n.</Text>
+<Table id="table_icons_on_the_search_browse_bar">
+<Title>
+<Text id="63">Significado de los iconos en la barra bÃºsqueda/consulta</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="123">
+<File width="87" height="17" url="images/User_Icon_5.gif"/>
+</th>
+<th width="407">
+<Text id="64">BÃºsqueda de determinadas palabras </Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="87" height="17" url="images/User_Icon_6.gif"/>
+</th>
+<th width="407">
+<Text id="65">Acceso a las publicaciones por tema</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="87" height="17" url="images/User_Icon_7.gif"/>
+</th>
+<th width="407">
+<Text id="66">Acceso a las publicaciones por tÃ­tulo</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="127" height="17" url="images/User_Icon_8.gif"/>
+</th>
+<th width="407">
+<Text id="67">Acceso a las publicaciones por organizaciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="87" height="17" url="images/User_Icon_9.gif"/>
+</th>
+<th width="407">
+<Text id="68">Acceso a las publicaciones por lista de âÃ­ndicesâ</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="69">A partir de la pÃ¡gina âbuscarâ puedeÂ <i>buscar palabras especÃ­ficas</i>Â que aparecen en el texto (esta pÃ¡gina es similar a la pÃ¡gina âacerca deâ que se muestra en la Figura 1, salvo que no contiene el texto âAcerca de esta colecciÃ³nâ). Se puede llegar a la pÃ¡gina de bÃºsqueda a partir de otras pÃ¡ginas pulsando el botÃ³nÂ <i>buscar</i>. Se puede tener acceso a las publicaciones por tema pulsando el botÃ³nÂ <i>temas</i>. Esto hace aparecer una lista de temas, representados por estantes que pueden desplegarse haciendo clic en ellos. Puede acceder a lasÂ <i>publicaciones por tÃ­tulo</i>Â pulsando el botÃ³nÂ <i>tÃ­tulos a-z</i>. Aparece entonces una lista de libros, por orden alfabÃ©tico. Se puede acceder a lasÂ <i>publicaciones por organizaciÃ³n</i>Â pulsando el botÃ³nÂ <i>organizaciones</i>. Aparece entonces una lista de organizaciones. Se puede acceder a lasÂ <i>publicaciones por lista de âÃ­ndicesâ</i>Â pulsando el botÃ³nÂ <i>cÃ³mo</i>. Aparece entonces una lista de âÃ­ndicesâ. Todos estos botones estÃ¡n representados en la Figura 1.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_to_read_the_documents">
+<Title>
+<Text id="70">CÃ³mo leer los documentos</Text>
+</Title>
+<Content>
+<Text id="71">En la colecciÃ³n de demostraciÃ³n, se puede saber cuando se ha llegado a un libro determinado porque aparecerÃ¡ una fotografÃ­a de su portada (Figura 2). AdemÃ¡s de la foto, habrÃ¡ un Ã­ndice; el renglÃ³n en negritas le indica dÃ³nde estÃ¡, en este caso,Â <i>IntroducciÃ³n y resumen</i>Â â SecciÃ³n <CrossRef target="Chapter" ref="overview_of_greenstone"/> del libro en cuestiÃ³n. Este Ã­ndice puede desplegarse; para abrir o cerrar las carpetas, haga clic en ellas. Para cerrar el libro abierto que figura en la parte superior, haga clic en el icono correspondiente.</Text>
+<Text id="72">Debajo estÃ¡ el texto con la secciÃ³n abierta (âÂ <i>The international demand for tropical butterflies</i>...â en el ejemplo, que comienza en la parte inferior de la ilustraciÃ³n). Al final de la lectura, se pueden pulsar unas flechas para pasar a la secciÃ³n siguiente o volver a la anterior.</Text>
+<Text id="73">Debajo de la fotografÃ­a hay cuatro botones; haga clic enÂ <i>separar</i>, para abrir una nueva ventana de consulta para este libro (es Ãºtil para comparar libros, o leer varios a la vez). Si ha llegado a este libro mediante una operaciÃ³n de bÃºsqueda, los tÃ©rminos de la bÃºsqueda aparecerÃ¡n resaltados; esta funciÃ³n se puede cancelar con el botÃ³nÂ <i>no resaltar</i>. Haga clic enÂ <i>texto completo</i>Â para ampliar el texto completo de la secciÃ³n o el libro que se estÃ¡ consultando. Haga clic enÂ <i>expandir Ã­ndice</i>Â para ampliar todo el Ã­ndice, a fin de poder ver los tÃ­tulos de todos los capÃ­tulos y subsecciones.</Text>
+<Text id="74">En algunas colecciones, los documentos no tienen este tipo de estructura jerÃ¡rquica. En este caso, no aparece ningÃºn Ã­ndice cuando se entra en un documento: sÃ³lo figura el texto del documento. A veces, los documentos estÃ¡n divididos en pÃ¡ginas, y se pueden leer secuencialmente, o saltar de una pÃ¡gina a otra.</Text>
+<Figure id="a_book_in_the_demo_collection">
+<Title>
+<Text id="75">Un libro en la colecciÃ³n de demostraciÃ³n</Text>
+</Title>
+<File width="532" height="526" url="images/User_Fig_2.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="what_the_icons_mean">
+<Title>
+<Text id="76">Significado de los iconos</Text>
+</Title>
+<Content>
+<Text id="77">Cuando usted consulte la colecciÃ³n, encontrarÃ¡ las funciones que aparecen en el Cuadro 3.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_to_search_for_particular_words">
+<Title>
+<Text id="78">BÃºsqueda de determinadas palabras</Text>
+</Title>
+<Content>
+<Text id="79">A partir de la pÃ¡gina de bÃºsqueda, siga estos pasos sencillos para hacer una consulta:</Text>
+<BulletList>
+<Bullet>
+<Text id="80">Especifique en quÃ© unidades desea buscar: en la colecciÃ³n de demostraciÃ³n puede buscarÂ  en los tÃ­tulos de secciones o en el texto completo de los libros.</Text>
+</Bullet>
+<Bullet>
+<Text id="81">Indique si desea buscar todas las palabras o sÃ³lo algunas de ellas.</Text>
+</Bullet>
+<Bullet>
+<Text id="82">Escriba las palabras que desea buscar en la casilla de consulta.</Text>
+</Bullet>
+<Bullet>
+<Text id="83">Haga clic en el botÃ³nÂ <i>Iniciar la bÃºsqueda</i></Text>
+</Bullet>
+</BulletList>
+<Text id="84">Al efectuar una consulta, aparecerÃ¡n los tÃ­tulos de hasta 20 documentos pertinentes. Si pulsa el botÃ³n del final, aparecerÃ¡n los prÃ³ximos 20. A partir de allÃ­ encontrarÃ¡ botones que le mostrarÃ¡n nuevamente otros 20, o que le permitirÃ¡n volver a los primeros 20, etc. Sin embargo, por razones de eficacia se impone un mÃ¡ximo de 100 documentos encontrados por cada consulta. PodrÃ¡ cambiar ese nÃºmero haciendo clic en el botÃ³nÂ <i>preferencias</i>, en la parte superior de la pÃ¡gina.</Text>
+<Table id="table_icons_that_you_will_encounter_when_browsing">
+<Title>
+<Text id="85">Iconos que encontrarÃ¡ durante la consulta</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="123">
+<File width="18" height="11" url="images/User_Icon_10.png"/>
+</th>
+<th width="407">
+<Text id="86">Haga clic en el icono de un libro para leer el libro correspondiente</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="20" height="16" url="images/User_Icon_11.png"/>
+</th>
+<th width="407">
+<Text id="87">Haga clic en el icono de un estante para buscar libros sobre el tema</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="23" height="15" url="images/User_Icon_12.png"/>
+</th>
+<th width="407">
+<Text id="88">Visualizar este documento</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="23" height="15" url="images/User_Icon_13.png"/>
+</th>
+<th width="407">
+<Text id="89">Abrir esta carpeta y visualizar su contenido</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="28" height="23" url="images/User_Icon_14.png"/>
+</th>
+<th width="407">
+<Text id="90">Haga clic en este icono para cerrar el libro</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="23" height="15" url="images/User_Icon_15.png"/>
+</th>
+<th width="407">
+<Text id="91">Haga clic en este icono para cerrar la carpeta</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="30" height="16" url="images/User_Icon_16.png"/>
+</th>
+<th width="407">
+<Text id="92">Haga clic en la flecha para pasar a la secciÃ³n siguiente ...</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="30" height="16" url="images/User_Icon_17.png"/>
+</th>
+<th width="407">
+<Text id="93">... o volver a la secciÃ³n anterior</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="65" height="30" url="images/User_Icon_18.gif"/>
+</th>
+<th width="407">
+<Text id="94">Abrir esta pÃ¡gina en una nueva ventana</Text>
+</th>
+</tr>
+<tr>
+<th>
+<File width="65" height="30" url="images/User_Icon_19.gif"/>
+</th>
+<th>
+<Text id="95">Ampliar el Ã­ndice</Text>
+</th>
+</tr>
+<tr>
+<th>
+<File width="65" height="30" url="images/User_Icon_20.gif"/>
+</th>
+<th>
+<Text id="96">Mostrar todo el texto</Text>
+</th>
+</tr>
+<tr>
+<th>
+<File width="65" height="30" url="images/User_Icon_21.gif"/>
+</th>
+<th>
+<Text id="97">Resaltar los tÃ©rminos de la bÃºsqueda </Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="98">Para abrir un documento, haga clic en el tÃ­tulo o en el pequeÃ±o icono que estÃ¡ al lado. El icono puede representar un documento, o una carpeta, o una pÃ¡gina: si su bÃºsqueda es en libros, el icono serÃ¡ un libro; en los demÃ¡s casos, si su bÃºsqueda es en secciones, el icono serÃ¡ una carpeta o una pÃ¡gina, segÃºn que en la secciÃ³n haya subsecciones o no.</Text>
+<Part id="search_terms">
+<Title>
+<Text id="99">TÃ©rminos de la bÃºsqueda </Text>
+</Title>
+<Content>
+<Text id="100">Todo lo que escriba en la casilla de consulta se interpretarÃ¡ como una lista de palabras llamada âtÃ©rminos de la bÃºsquedaâ. Cada tÃ©rmino de la bÃºsqueda contiene solamente caracteres alfabÃ©ticos y dÃ­gitos. Los tÃ©rminos estÃ¡n separados por un espacio en blanco. Si aparecen otros tipos de caracteres, por ejemplo signos de puntuaciÃ³n, estos sirven para separar los tÃ©rminos como si fueran espacios y se harÃ¡ caso omiso de ellos. No se puede efectuar una bÃºsqueda con palabras que incluyan signos de puntuaciÃ³n.</Text>
+<Text id="101">Por ejemplo, la consulta:</Text>
+<Text id="102">Agro-forestry in the Pacific Islands: Systems for Sustainability (1993)</Text>
+<Text id="103">se tratarÃ¡ de la misma manera que:</Text>
+<Text id="104">Agro forestry in the Pacific Islands Systems for Sustainability 1993</Text>
+</Content>
+</Part>
+<Part id="query_type">
+<Title>
+<Text id="105">Tipos de consulta</Text>
+</Title>
+<Content>
+<Text id="106">Hay dos tipos diferentes de consultas.</Text>
+<BulletList>
+<Bullet>
+<Text id="107">Consultas basadas en todas las palabras. En este caso se buscan los documentos (o capÃ­tulos, o tÃ­tulos) que contengan todas la palabras que se han especificado. Aparecen los documentos que responden a la consulta.</Text>
+</Bullet>
+<Bullet>
+<Text id="108">Consulta basada en algunas palabras. Indica sÃ³lo algunos tÃ©rminos que probablemente aparezcan en los documentos en que se estÃ¡ buscando. Los documentos se presentan en el orden de pertinencia con respecto a la consulta. Para determinar el grado de correspondencia, se tendrÃ¡ en cuenta que:</Text>
+</Bullet>
+<Bullet>
+<Text id="109">cuanto mÃ¡s tÃ©rminos de bÃºsqueda contenga el documento, mayor serÃ¡ la correspondencia;</Text>
+</Bullet>
+<Bullet>
+<Text id="110">los tÃ©rminos poco frecuentes son mÃ¡s importantes que los comunes;</Text>
+</Bullet>
+<Bullet>
+<Text id="111">los documentos cortos se adaptan mejor a la bÃºsqueda que los largos.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Part>
+<Text id="112">Utilice todos los tÃ©rminos de bÃºsqueda que desee, es decir, una oraciÃ³n completa o incluso un pÃ¡rrafo entero. Si especifica Ãºnicamente un tÃ©rmino, no importarÃ¡ si utiliza la consulta de todas las palabras o de sÃ³lo algunas, salvo que en el segundo caso los resultados estarÃ¡n clasificados por la frecuencia de apariciÃ³n del tÃ©rmino de la bÃºsqueda.</Text>
+</Content>
+</Subsection>
+<Subsection id="scope_of_queries">
+<Title>
+<Text id="113">Alcance de las consultas</Text>
+</Title>
+<Content>
+<Text id="114">En la mayorÃ­a de las colecciones se puede escoger entre diversos Ã­ndices de bÃºsqueda, por ejemplo, Ã­ndices de autores o de tÃ­tulos. TambiÃ©n pueden ser Ã­ndices de capÃ­tulos o pÃ¡rrafos. En general, el documento que corresponde plenamente a la consulta aparece con independencia del Ã­ndice de bÃºsqueda utilizado.</Text>
+<Text id="115">Si los documentos son libros, se abrirÃ¡n en el lugar apropiado.</Text>
+</Content>
+</Subsection>
+<Subsection id="advanced_search_features">
+<Title>
+<Text id="116">Funciones de bÃºsqueda avanzada</Text>
+</Title>
+<Content>
+<Text id="117">Si bien los pasos antes indicados son suficientes para responder a la mayorÃ­a de las necesidades de bÃºsqueda, Greenstone propone funciones de bÃºsqueda mÃ¡s avanzada. Estas se activan a partir de la pÃ¡gina deÂ <i>preferencias</i>, a la que se llega haciendo clic en el botÃ³n deÂ <i>preferencias</i>Â en la parte superior de la pÃ¡gina. Si cambia usted sus preferencias, no haga clic en el botÃ³nÂ <i>AtrÃ¡s</i>Â de su navegador, ya que ello anularÃ­a los cambios. En cambio, haga clic en cualquiera de los botones de la barra de bÃºsqueda/consulta.</Text>
+<Part id="case_sensitivity_and_stemming">
+<Title>
+<Text id="118">Reconocimiento de mayÃºsculas y minÃºsculas y truncamiento de tÃ©rminos</Text>
+</Title>
+<Content>
+<Text id="119">Cuando especifique los tÃ©rminos de bÃºsqueda, puede usted optar por que las mayÃºsculas y minÃºsculas que aparecen en la consulta correspondan a las del documento; esto se llama âreconocimiento de mayÃºsculas y minÃºsculasâ. TambiÃ©n puede optar por hacer caso omiso o no del final de la palabra: esto se llama âtruncamientoâ.</Text>
+<Text id="120">En las Preferencias de bÃºsqueda de la pÃ¡gina de preferencias, encontrarÃ¡ un par de botones con la etiqueta ignorar diferencias entre mayÃºsculas y minÃºsculas y deben corresponder mayÃºsculas y minÃºsculas; de esta manera se controla el reconocimiento de mayÃºsculas y minÃºsculas en sus consultas. Debajo hay otros dos botones con la etiqueta ignorar las terminaciones de las palabras y debe corresponder la palabra completa; de esta manera se controla el truncamiento o no del tÃ©rmino.</Text>
+<Text id="121">Por ejemplo, si se seleccionan los botones ignorar diferencias entre mayÃºsculas y minÃºsculas e ignorar las terminaciones de las palabras, la consulta:</Text>
+<Text id="122">African building</Text>
+<Text id="123">se tratarÃ¡ de la misma manera que:</Text>
+<Text id="124">africa builds</Text>
+<Text id="125">ya que la mayÃºscula de âAfricanâ pasarÃ¡ a ser minÃºscula, y se harÃ¡ caso omiso de los sufijos ânâ e âingâ de las palabras âAfricanâ y âbuildingâ respectivamente (tampoco se tendrÃ¡ en cuenta la âsâ de âbuildsâ).</Text>
+<Text id="126">Se recomienda en general no tener en cuenta la distinciÃ³n entre mayÃºsculas y minÃºsculas y la desinencia de la palabra, a menos que se estÃ© buscando un nombre o una sigla en particular.</Text>
+</Content>
+</Part>
+<Part id="phrase_searching">
+<Title>
+<Text id="127">BÃºsqueda de frases</Text>
+</Title>
+<Content>
+<Text id="128">Si en su consulta incluye una frase entre comillas, sÃ³lo aparecerÃ¡n los documentos que contengan esa frase, exactamente como se la escribiÃ³.</Text>
+<Text id="129">Si desea utilizar la funciÃ³n de bÃºsqueda de frases, deberÃ¡ aprender un poco sobre su funcionamiento. LasÂ frases se procesan mediante un examen posterior a la recuperaciÃ³n (<i>post-retrieval scan</i>). La consulta se efectÃºa primero de modo normal, es decir, todas las palabras contenidas en las frases se incluyen como tÃ©rminos de la bÃºsqueda, y luego los documentos presentados son filtrados para eliminar aquÃ©llos en que no aparece esa frase.</Text>
+<Text id="130">Durante el examen posterior a la recuperaciÃ³n, se buscan las frases exactas, incluido cualquier signo de puntuaciÃ³n. Por ejemplo, en la consulta:</Text>
+<Text id="131">whatâs a âpost-retrieval scan?â</Text>
+<Text id="132">encontraremos en primer lugar todos los documentos que contienen las palabras:</Text>
+<CodeLine>what s a post retrieval scan</CodeLine>
+<Text id="133">y a continuaciÃ³n en los documentos presentados se buscarÃ¡ la frase:</Text>
+<Text id="134">post-retrieval scan?</Text>
+<Text id="135">Si se selecciona la opciÃ³nÂ <i>ignorar diferencias entre mayÃºsculas y minÃºsculas</i>Â en la pÃ¡gina deÂ <i>preferencias</i>, la correspondencia encontrada para la frase harÃ¡ caso omiso de la distinciÃ³n entre mayÃºsculas y minÃºsculas.</Text>
+</Content>
+</Part>
+<Part id="advanced_query_mode">
+<Title>
+<Text id="136">Modo de consulta avanzada</Text>
+</Title>
+<Content>
+<Text id="137">En el modo de consulta avanzada, que se puede seleccionar en la pÃ¡gina deÂ <i>preferencias</i>, las bÃºsquedas deÂ <i>todas</i>Â las palabras son en realidad consultas con operadores booleanos. Se trata de una lista de tÃ©rminos enlazados por los operadores lÃ³gicos â&amp;â (y), â |â (o) y â!â (no). La ausencia de operadores entre los tÃ©rminos de bÃºsquedas se interpreta como un â&amp;â (y); de esta manera, una consulta sin operadores remite a documentos en que aparecenÂ <i>todos</i>Â los tÃ©rminos.</Text>
+<Text id="138">Si en su consulta aparecen las palabras AND, OR y NOT (respectivamente, âyâ, âoâ y ânoâ en inglÃ©s), se las trata como tÃ©rminos de bÃºsqueda ordinaria, y no como operadores. Para que se consideren operadores, se deben utilizar los signos â&amp;â, â |â y â!â. AdemÃ¡s, se pueden utilizar parÃ©ntesis para agrupar.</Text>
+</Content>
+</Part>
+<Part id="using_search_history">
+<Title>
+<Text id="139">UtilizaciÃ³n del historial de bÃºsqueda</Text>
+</Title>
+<Content>
+<Text id="140">Cuando se acciona la propiedadÂ <i>historial de bÃºsquedas</i>Â en la pÃ¡gina deÂ <i>preferencias</i>, aparecerÃ¡n sus Ãºltimas bÃºsquedas junto con el nÃºmero de resultados obtenidos. Haga clic en el botÃ³n que estÃ¡ al lado de una de las bÃºsquedas anteriores para copiar el texto correspondiente en la casilla de bÃºsqueda. De esta manera resulta mÃ¡s fÃ¡cil repetir versiones ligeramente modificadas de consultas anteriores.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="changing_the_preferences">
+<Title>
+<Text id="141">Cambio de preferencias</Text>
+</Title>
+<Content>
+<Figure id="the_preferences_page">
+<Title>
+<Text id="142">La pÃ¡gina de Preferencias</Text>
+</Title>
+<File width="529" height="524" url="images/User_Fig_3.png"/>
+</Figure>
+<Text id="143">Si pulsa usted el botÃ³nÂ <i>preferencias</i>Â en la parte superior de la pÃ¡gina, podrÃ¡ cambiar algunas caracterÃ­sticas de la interfaz para que se adapte a sus necesidades. Las preferencias dependen de la colecciÃ³n; en la Figura 3 se muestra un ejemplo. Para ajustar sus preferencias de bÃºsqueda, pulse el botÃ³nÂ <i>fijar preferencias</i>Â que aparece en la Figura 3. Tras seleccionar las preferencias, no utilice el botÃ³nÂ <i>AtrÃ¡s</i>Â de su navegador, ya que anularÃ­a la operaciÃ³n. En lugar de ello, haga clic en uno de los botones de la barra de acceso, cerca de la parte superior de la pÃ¡gina.</Text>
+<Subsection id="collection_preferences">
+<Title>
+<Text id="144">Preferencias de colecciones</Text>
+</Title>
+<Content>
+<Text id="145">Algunas colecciones contienen varias subcolecciones, en las que pueden hacerse bÃºsquedas independientemente o en conjunto, como si constituyeran una unidad. En ese caso, puede usted elegir en la pÃ¡gina deÂ <i>preferencias</i>Â quÃ© subcolecciones han de incluirse en sus bÃºsquedas.</Text>
+</Content>
+</Subsection>
+<Subsection id="language_preferences">
+<Title>
+<Text id="146">Preferencias de idiomas</Text>
+</Title>
+<Content>
+<Text id="147">Cada colecciÃ³n tiene un idioma de presentaciÃ³n por defecto, pero que se puede sustituir por otro idioma, si lo desea. TambiÃ©n puede usted modificar el sistema de codificaciÃ³n utilizado por Greenstone para manejar el navegador: el programa elige las opciones por defecto razonables, pero con algunos navegadores pueden obtenerse mejores resultados visuales pasando a un sistema de codificaciÃ³n diferente. Todas las colecciones permiten pasar del formato estÃ¡ndar de interfaz grÃ¡fica a uno textual. Esto es particularmente Ãºtil para los usuarios con deficiencias visuales, que utilizan en su computadora caracteres de pantalla de gran tamaÃ±o o sintetizadores vocales.</Text>
+</Content>
+</Subsection>
+<Subsection id="presentation_preferences">
+<Title>
+<Text id="148">Preferencias de presentaciÃ³n</Text>
+</Title>
+<Content>
+<Text id="149">SegÃºn la colecciÃ³n, puede usted seleccionar otras opciones para controlar la presentaciÃ³n. Las colecciones de pÃ¡ginas Web le permiten suprimir la barra de navegaciÃ³n Greenstone en la parte superior de cada pÃ¡gina del documento, de modo que una vez que haya hecho una bÃºsqueda llegue a la pÃ¡gina Web exacta que coincide con su consulta, sin ningÃºn encabezado Greenstone. Para efectuar otra bÃºsqueda deberÃ¡ pulsar el botÃ³nÂ <i>AtrÃ¡s</i>Â de su navegador. Estas colecciones tambiÃ©n le permiten suprimir el mensaje de alerta de Greenstone que aparece cuando usted pulsa un enlace que lo saca de la biblioteca digital y lo lleva a la Web propiamente dicha. AdemÃ¡s, en algunas colecciones Web se puede determinar si los enlaces sobre la pÃ¡ginaÂ <i>resultados de la bÃºsqueda</i>Â lo llevan directamente a la URL en cuestiÃ³n o a la copia de la pÃ¡gina en la biblioteca digital.</Text>
+</Content>
+</Subsection>
+<Subsection id="search_preferences">
+<Title>
+<Text id="150">Preferencias de bÃºsqueda</Text>
+</Title>
+<Content>
+<Text id="151">En la funciÃ³nÂ <i>Preferencias de bÃºsqueda</i>Â que se muestra en la Figura 3, los dos primeros botones permiten obtener una casilla de consulta de gran tamaÃ±o, en la que se puede efectuar fÃ¡cilmente una bÃºsqueda del tamaÃ±o de un pÃ¡rrafo. En Greenstone, la bÃºsqueda de porciones de texto muy extensas es sorprendentemente rÃ¡pida. Los dos pares de botones siguientes controlan el tipo de texto encontrado mediante las bÃºsquedas efectuadas. El primer grupo (denominado âÂ <i>Reconocimiento de mayÃºsculas y minÃºsculas</i>Â â) controla la distinciÃ³n entre mayÃºsculas y minÃºsculas. El segundo (âÂ <i>Terminaciones de las palabras</i>Â â) controla si se toma en cuenta o no la desinencia de las palabras.</Text>
+<Text id="152">Con el siguiente par de botones se puede pasar al modo de consulta âavanzadaâ antes mencionado, que le permite especificar consultas mÃ¡s precisas, mediante la combinaciÃ³n de tÃ©rminos que utilizan âyâ (&amp;), âoâ (|) y ânoâ (!). Se puede activar o desactivar la funciÃ³n de historial de bÃºsqueda antes mencionada. Por Ãºltimo, gracias al Ãºltimo renglÃ³n que aparece en la Figura 3, usted puede controlar el nÃºmero de resultados obtenidos y el nÃºmero de resultados presentado en cada pantalla.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="making_greenstone_collections">
+<Title>
+<Text id="153">CREACIÃN DE COLECCIONES GREENSTONE</Text>
+</Title>
+<Content>
+<Text id="154">La forma mÃ¡s sencilla de crear nuevas colecciones es por medio de la Interfaz de Bibliotecario de Greenstone (GLI por sus siglas en inglÃ©s), la cual permite reunir conjuntos de documentos, importarlos o asignarles metadatos y construir con ellos una colecciÃ³n Greenstone. La Interfaz de Bibliotecario de Greenstone cuenta con soporte para cinco actividades bÃ¡sicas, las cuales pueden intercalarse, aunque nominalmente se toman en el siguiente orden:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="155">Copiar documentos desde el espacio de archivos de la computadora, incluyendo colecciones existentes, e incluirlos en una nueva colecciÃ³n. Los documentos âconservanâ los metadatos anteriores y tambiÃ©n pueden bajarse de Internet a travÃ©s de un programa de espejeo integrado.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="156">Enriquecer los documentos aÃ±adiendo mÃ¡s metadatos a los documentos individuales o a grupos de documentos.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="157">Designar la colecciÃ³n determinando su apariencia y los programas de acceso que a los que darÃ¡ soporte.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="158">Construir la colecciÃ³n por medio de Greenstone.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="159">Tener una vista previa de la colecciÃ³n que se acaba de crear, la cual se habrÃ¡ instalado en su pÃ¡gina principal Greenstone como una de las colecciones regulares.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="160">La interfaz de bibliotecario le permite aÃ±adir lo que la gente llama metadatos âexternosâ a los documentos, es decir, metadatos que pertenecen al documento como un todo. Pero los documentos a menudo necesitan estar estructurados en secciones y subsecciones, con lo que tambiÃ©n puede haber metadatos âinternosâ asociados a cada parte. En Greenstone los documentos de origen pueden estar etiquetados con esta informaciÃ³n, tal como se explica en la SecciÃ³n 3.3.</Text>
+<Text id="161">Finalmente, tambiÃ©n se cuenta con una forma alternativa para crear colecciones a travÃ©s del Colector, que le ayuda a crear nuevas colecciones, modificar o aÃ±adir colecciones existentes o eliminarlas. Aunque este programa de recopilaciÃ³n antecede a la interfaz de bibliotecario, para fines prÃ¡cticos se recomienda usar esta Ãºltima en lugar del Colector. El Colector se describe en la SecciÃ³n 3.4</Text>
+<Text id="162">Para poder aprovechar todo el poder que le ofrece Greenstone para construir colecciones avanzadas, usted tambiÃ©n necesitarÃ¡ leer el CapÃ­tulo 2 de la GuÃ­a del Programador.</Text>
+<Section id="the_librarian_interface">
+<Title>
+<Text id="163">La Interfaz de Bibliotecario</Text>
+</Title>
+<Content>
+<Text id="164">Para explicar el funcionamiento de la interfaz de bibliotecario de Greenstone nos gustarÃ­a hacerlo a travÃ©s de un sencillo ejemplo. Las figuras de la 4 a la 15 son imÃ¡genes en pantalla de los diferentes momentos de la acciÃ³n. Este ejemplo utiliza documentos delÂ <i>Subconjunto de la Biblioteca para el Desarrollo</i>Â (DLS por sus siglas en inglÃ©s), la cual se distribuye junto con Greenstone. Para los fines de esta exposiciÃ³n, la explicaciÃ³n toma la forma de un sencillo paseo por los pasos mencionados arriba. No obstante, una patrÃ³n de uso mÃ¡s realista es ir de atrÃ¡s para adelante a travÃ©s de las diferentes etapas conforme la tarea avanza.</Text>
+<Text id="165">La interfaz del bibliotecario puede iniciarse en uno de cuatro posibles modos: Asistente de biblioteca, Bibliotecario, Especialista de sistemas de biblioteca, y Avanzado. Estos modos controlan el nivel de detalle dentro de cada interfaz, y pueden cambiarse usando la opciÃ³n de "Preferencias" en el menÃº de "Archivo". El recorrido en esta secciÃ³n supone que la interfaz de bibliotecario se encuentra operando en el modo Bibliotecario.</Text>
+<Subsection id="getting_started">
+<Title>
+<Text id="166">Para empezar</Text>
+</Title>
+<Content>
+<Text id="167">Si cuenta con Windows inicie la interfaz de bibliotecario de seleccionandoÂ <i>Biblioteca Digital Greenstone</i>Â en la secciÃ³n deÂ <i>Programas</i>Â del menÃº deÂ <i>Inicio</i>Â y eligiendoÂ <i>Interfaz de Bibliotecario</i>. Si estÃ¡ usando UNIX, entonces escriba:</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<CodeLine>cd gli</CodeLine>
+<CodeLine>./gli.sh</CodeLine>
+<Text id="168">dondeÂ <i>~/gsdl</i>Â es el directorio que contiene el sistema Greenstone. Para empezar usted debe abrir una colecciÃ³n existente o iniciar una nueva. La figura 4 muestra al usuario en el proceso de iniciar una nueva colecciÃ³n, seleccionandoÂ <i>New [Nuevo]</i>Â en el menÃº de archivos y llenando la informaciÃ³n general acerca de la colecciÃ³n: tÃ­tulo, direcciÃ³n de correo electrÃ³nico del responsable de la colecciÃ³n y una breve descripciÃ³n de su contenido. El tÃ­tulo de la colecciÃ³n es una frase corta que se utilizarÃ¡ aÂ  lo largo de toda la biblioteca digital para identificar su contenido. Las colecciones existentes tienen nombres comoÂ <i>Biblioteca de la AlimentaciÃ³n y la NutriciÃ³n</i>,Â <i>BibliotecaÂ  Mundial del Medio Ambiente</i>, etc. Cuando se escribe el tÃ­tulo el sistema le asigna un identificador mnemotÃ©cnico Ãºnico, que equivale al ânombreâ de la colecciÃ³n para uso interno (usted puede cambiarlo si asÃ­ lo desea). La direcciÃ³n de correo electrÃ³nico corresponde al primer punto de contacto para cualquier problema que se tenga con la colecciÃ³n.</Text>
+<Text id="169">La descripciÃ³n es una breve relaciÃ³n de los principios que rigen la selecciÃ³n de los materiales que van a formar parte de la colecciÃ³n. Aparece bajo el encabezadoÂ <i>About this collection [Acerca de esta colecciÃ³n]</i>Â en la pÃ¡gina inicial.</Text>
+<Figure id="starting_a_new_collection">
+<Title>
+<Text id="170">Iniciando una nueva colecciÃ³n</Text>
+</Title>
+<File width="380" height="297" url="images/User_Fig_4.png"/>
+</Figure>
+<Figure id="exploring_the_local_file_space">
+<Title>
+<Text id="171">Explorando el espacio de archivos</Text>
+</Title>
+<File width="380" height="297" url="images/User_Fig_5.png"/>
+</Figure>
+<Text id="172">En este punto el usuario decide si desea que la nueva colecciÃ³n se base en la misma estructura que una colecciÃ³n existente o construir un tipo de colecciÃ³n totalmente nuevo. En la figura 4 el usuario decidiÃ³ basarla en elÂ <i>Subconjunto de la Biblioteca para el Desarrollo</i>Â (DLS por sus siglas en inglÃ©s). Esto implica que el conjunto de metadatos âDLSâ que se utiliza en esta colecciÃ³n se usarÃ¡ para la nueva colecciÃ³n. (De hecho, este conjunto de metadatos se ha usado para crear varias colecciones Greenstone que comparten una misma estructura y organizaciÃ³n, pero con diferentes contenidos, incluyendo las colecciones deÂ <i>Muestra</i>Â y la delÂ <i>Subconjunto de la Biblioteca para el Desarrollo</i>Â que se incluyen como ejemplos junto con Greenstone.)</Text>
+<Text id="173">El conjunto de metadatos DLS contiene los siguientes elementos:</Text>
+<BulletList>
+<Bullet>
+<Text id="174">TÃ­tulo</Text>
+</Bullet>
+<Bullet>
+<Text id="175">Tema</Text>
+</Bullet>
+<Bullet>
+<Text id="176">Idioma</Text>
+</Bullet>
+<Bullet>
+<Text id="177">OrganizaciÃ³n</Text>
+</Bullet>
+<Bullet>
+<Text id="178">Palabra clave (es decir, âCÃ³moâ).</Text>
+</Bullet>
+</BulletList>
+<Text id="179">(Existe ademÃ¡s un elemento de metadato llamadoÂ <i>AZList</i>Â que se utiliza para determinar quÃ© compartimento de la lista alfabÃ©tica contiene el tÃ­tulo del documento, con valores como âA-Bâ o âC-D-Eâ. Esto se utiliza para lograr un control preciso sobre las divisiones de la lista. En la mayorÃ­a de las otras colecciones estos compartimentos estÃ¡n ausentes y Greenstone los asigna por sÃ­ mismo.)</Text>
+<Text id="180">Si en cambio el usuario eligiÃ³ âNueva ColecciÃ³nâ, se le pedirÃ¡ que seleccione los conjuntos de metadatos que se van a usar en la nueva colecciÃ³n. Se ofrecen tres conjuntos estÃ¡ndar: Dublin Core, el conjunto de metadatos DLS mencionado arriba y un conjunto que comprende elementos de metadatos extraÃ­dos automÃ¡ticamente por Greenstone de los documentos de la colecciÃ³n. El usuario tambiÃ©n puede crear nuevos conjuntos de metadatos por medio de una pantalla que se activa a travÃ©s del menÃº âmetadatosâ.</Text>
+<Text id="181">Varios conjuntos de metadatos diferentes se pueden asociar a la misma colecciÃ³n, ya que el sistema los mantiene separados (de tal manera que los documentos, por ejemplo, pueden tener unÂ <i>TÃ­tulo</i>Â en Dublin Core y uno en DLS). Estos conjuntos se mantienen claramente diferenciados en la interfaz. Entre bastidores los conjuntos de metadatos se representan en XML.</Text>
+</Content>
+</Subsection>
+<Subsection id="assembling_the_source_material">
+<Title>
+<Text id="182">Reuniendo el material</Text>
+</Title>
+<Content>
+<Text id="183">DespuÃ©s de hacer click en el botÃ³nÂ <i>Aceptar</i>Â las partes restantes de la interfaz que habÃ­an permanecido sombreadas hasta este momento se activarÃ¡n. La pantallaÂ <i>Reunir</i>, seleccionado por medio de la pestaÃ±a del mismo nombre que se encuentra cerca de la parte superior de la figura 4, aparecerÃ¡ en pantalla. Esto le permitirÃ¡ al usuario explorar el espacio de archivos y las colecciones existentes en su computadora, y reunir los documentos seleccionados para la nueva colecciÃ³n. La pantalla se divide en dos secciones: la izquierda para explorar las estructuras existentes y la derecha para los documentos que integrarÃ¡n la colecciÃ³n.</Text>
+<Text id="184">Las operaciones disponibles en esta etapa incluyen:</Text>
+<BulletList>
+<Bullet>
+<Text id="185">Navegar de manera normal por las jerarquÃ­as de la estructura de archivos existente y por la que se estÃ¡ creando.</Text>
+</Bullet>
+<Bullet>
+<Text id="186">Arrastrar y colocar archivos en la nueva colecciÃ³n.</Text>
+</Bullet>
+<Bullet>
+<Text id="187">Seleccionar varios archivos a la vez.</Text>
+</Bullet>
+<Bullet>
+<Text id="188">Arrastrar y colocar subjerarquÃ­as completas.</Text>
+</Bullet>
+<Bullet>
+<Text id="189">Eliminar documentos de la naciente colecciÃ³n.</Text>
+</Bullet>
+<Bullet>
+<Text id="190">Crear nuevas subjerarquÃ­as dentro de la colecciÃ³n.</Text>
+</Bullet>
+<Bullet>
+<Text id="191">Filtrar los archivos que son visibles, tanto en el sistema local de archivos como en la colecciÃ³n, con base en grupos predeterminados o en tÃ©rminos de correspondencia de archivos estÃ¡ndar.</Text>
+</Bullet>
+<Bullet>
+<Text id="192">Llamar al programa apropiado para que muestre en pantalla los contenidos de un archivo seleccionado haciendo doble click en Ã©l.</Text>
+</Bullet>
+</BulletList>
+<Text id="193">Se ha tenido especial cuidado en evitar los conflictos entre nombres cuando archivos con el mismo nombre en diferentes partes de la estructura de directorios de la computadora se copian en la misma carpeta de la colecciÃ³n.</Text>
+<Text id="194">En la figura 5 el usuario estÃ¡ utilizando la pantalla interactiva del Ã¡rbol de archivos para explorar el sistema de archivos local. En esta etapa la colecciÃ³n a la derecha estÃ¡ vacÃ­a. El usuario la llena arrastrando y colocando los archivos correspondientes de la parte izquierda a la parte derecha de la pantalla. Estos archivos se âcopianâ en vez de âmoverseâ, de tal manera que el sistema original de archivos no resulta afectado. Las tÃ©cnicas usuales para seleccionar varios archivos, arrastrarlos y colocarlos, estructurar la nueva colecciÃ³n creando subdirectorios (âcarpetasâ) y eliminar archivos de ella moviÃ©ndolos al basurero o a la papelera de reciclaje estÃ¡n todas ellas disponibles.</Text>
+<Text id="195">Las colecciones existentes se representan por medio de un subdirectorio a la izquierda llamado âColecciones Greenstoneâ, el cual puede abrirse y explorarse como cualquier otro directorio. Sin embargo, los documentos que se encuentran ahÃ­ difieren de los archivos comunes debido a que ya tienen metadatos adjuntos y estos se conservan cuando pasan a formar parte de la nueva colecciÃ³n. Los conflictos podrÃ­an surgir debido a que sus metadatos tal vez les fueron asignados usando un conjunto diferente de metadatos del que se usa para la nueva colecciÃ³n, por lo que el usuario deberÃ¡ resolver esto. En la figura 6 el usuario ha seleccionado algunos documentos de la colecciÃ³n existente y los ha arrastrado a la nueva colecciÃ³n. La ventana que aparece explica que el elemento de metadatoÂ <i>Organization [OrganizaciÃ³n]</i>Â no se pudo importar automÃ¡ticamente y le pide al usuario que seleccione un conjunto de metadatos y presioneÂ <i>A Ã±adir</i>Â para aÃ±adir el elemento de metadato a dicho conjunto,<FootnoteRef id="1"/>o que elija un conjunto de metadatos, luego un elemento y presioneÂ <i>Combinar</i>Â para nombrar nuevamente el antiguo elemento de metadato de acuerdo al nuevo y combinarlos. Los metadatos de los siguientes documentos de la misma colecciÃ³n serÃ¡n tratados automÃ¡ticamente de la misma manera.</Text>
+<Text id="196">Cuando se seleccionen, arrastren y coloquen grandes conjuntos de archivos en la nueva colecciÃ³n, la operaciÃ³n de copiado puede llevar algÃºn tiempo, particularmente si esto incluye la conversiÃ³n de metadatos. Para indicar el grado de avance la interfaz muestra el archivo que se estÃ¡ copiando y el porcentaje de archivos que se han procesado.</Text>
+<Text id="197">TambiÃ©n se cuenta con programas especiales para tratar con grandes conjuntos de archivos. Por ejemplo, el usuario puede filtrar los directorios y subdirectorios para mostrar Ãºnicamente ciertos archivos por medio de un menÃº de tipos de archivos que se encuentra debajo. En la figura 7 Ãºnicamente se muestran los archivos HTM y HTML y sÃ³lo se copiarÃ¡n estos archivos al momento de arrastrarlos y colocarlos en la nueva colecciÃ³n.</Text>
+</Content>
+</Subsection>
+<Subsection id="enriching_the_documents">
+<Title>
+<Text id="198">Enriqueciendo los documentos</Text>
+</Title>
+<Content>
+<Text id="199">La siguiente fase es enriquecer los documentos aÃ±adiendo los metadatos. La pestaÃ±aÂ <i>Enriquecer</i>Â despliega una nueva pantalla de informaciÃ³n (figura 8), la cual muestra los directorios y subdirectorios de la colecciÃ³n a la izquierda y a la derecha permite aÃ±adir los metadatos a los documentos individuales o a los grupos de documentos.</Text>
+<Text id="200">Los documentos que se copiaron durante el primer paso incluyen todos los metadatos que se les hayan asociado. Si un documento es parte de una colecciÃ³n Greenstone, los metadatos definidos previamente pasan a formar parte de la nueva colecciÃ³n. Ciertamente, es posible que esta nueva colecciÃ³n tenga un conjunto diferente de metadatos, o quizÃ¡ sÃ³lo un subconjunto de los metadatos definidos y Ãºnicamente se conserven los metadatos que pertenecen al conjunto de la nueva colecciÃ³n. La soluciÃ³n de este tipo de conflictos tal vez requiera la intervenciÃ³n del usuario por medio de un diÃ¡logo suplementario (figura 6). Cualquier selecciÃ³n que se haga se recordarÃ¡ para la copia de los siguientes archivos.</Text>
+<Text id="201">La pantallaÂ <i>Enriquecer</i>Â permite asignar los valores de los metadatos a los documentos de la colecciÃ³n Por ejemplo, se pueden agregar nuevos valores al conjunto de los valores existentes para un elemento. Si los valores del elemento tienen una estructura jerÃ¡rquica, la jerarquÃ­a se puede extender de la misma forma.</Text>
+<Figure id="importing_existing_metadata">
+<Title>
+<Text id="202">Importando metadatos existentes</Text>
+</Title>
+<File width="380" height="296" url="images/User_Fig_6.png"/>
+</Figure>
+<Figure id="filtering_the_file_trees.">
+<Title>
+<Text id="203">Filtrando los Ã¡rboles de archivos.</Text>
+</Title>
+<File width="380" height="297" url="images/User_Fig_7.png"/>
+</Figure>
+<Figure id="assigning_metadata_using_enrich_view">
+<Title>
+<Text id="204">Asignando metadatos por medio de la pantallaÂ <i>Enriquecer</i>.</Text>
+</Title>
+<File width="376" height="294" url="images/User_Fig_8.png"/>
+</Figure>
+<Figure id="viewing_all_metadata_for_selected_files">
+<Title>
+<Text id="205">Viendo todos los metadatos de los archivos seleccionados.</Text>
+</Title>
+<File width="376" height="294" url="images/User_Fig_9.png"/>
+</Figure>
+<Text id="206">Los valores de los metadatos tambiÃ©n pueden asignarse a carpetas justo de la misma manera. Los documentos que se encuentran en estas carpetas y para los cuales no se hayan especificado estos metadatos heredan sus valores. Sin embargo, estos pueden sustituirse posteriormente proporcionando valores diferentes para cada documento.</Text>
+<Text id="207">Las operaciones en esta etapa del proceso incluyen:</Text>
+<BulletList>
+<Bullet>
+<Text id="208">Asignar valores de metadatos nuevos y existentes a los documentos.</Text>
+</Bullet>
+<Bullet>
+<Text id="209">Asignar metadatos a un documento individual.</Text>
+</Bullet>
+<Bullet>
+<Text id="210">Asignar metadatos a una carpeta (estos son heredados por todos los documentos de la carpeta, incluyendo los que se encuentran en las carpetas anidadas).</Text>
+</Bullet>
+<Bullet>
+<Text id="211">Asignar metadatos jerÃ¡rquicos, cuya estructura pueda actualizarse dinÃ¡micamente en caso necesario.</Text>
+</Bullet>
+<Bullet>
+<Text id="212">Editar o actualizar metadatos.</Text>
+</Bullet>
+<Bullet>
+<Text id="213">Revisar los metadatos asignados a una selecciÃ³n de archivos y directorios.</Text>
+</Bullet>
+</BulletList>
+<Text id="214">Siguiendo con nuestro ejemplo, en la figura 8 el usuario ha seleccionado la carpetaÂ <i>ec121e</i>Â y le ha asignado el valor âEC Courierâ como metadato de laÂ <i>OrganizaciÃ³n</i>. Los botones para actualizar y eliminar el metadato se activan, dependiendo de las selecciones que se hayan hecho.</Text>
+<Text id="215">Durante la fase de enriquecimiento e inclusive en cualquier otro momento el usuario puede ver todos los metadatos que se le han asignado a los documentos de la colecciÃ³n. Esto se hace seleccionando el conjunto de documentos y eligiendoÂ <i>Metadatos Asignados</i>Â en el menÃº de conjuntos de metadato, el cual despliega una ventana como la que se puede ver en la figura 9. Esta ventana muestra los metadatos en forma de hoja de cÃ¡lculo. Para grandes colecciones resulta de gran utilidad poder ver solamente los metadatos asociados a ciertos tipos de documentos y si el usuario ha especificado un filtro de archivos tal como se menciona arriba, Ãºnicamente se mostrarÃ¡n los documentos seleccionados en la pantalla de metadatos.</Text>
+<Text id="216">La pantalla en la figura 10 le permite al usuario editar los conjuntos de metadatos. AquÃ­ el usuario estÃ¡ viendo el elementoÂ <i>Subject [Tema]</i>Â del conjunto DLS. Los valores de este elemento forman una jerarquÃ­a y el usuario estÃ¡ examinando y tal vez cambiando la lista de valores asignados. La misma pantalla tambiÃ©n le permite cambiar el âperfilâ para mapear los elementos de un conjunto de metadatos a otro. Este perfil se crea al momento de importar documentos de colecciones que tienen metadatos asignados previamente.</Text>
+<Figure id="editing_the_metadata_set">
+<Title>
+<Text id="217">Editando el conjunto de metadatos.</Text>
+</Title>
+<File width="376" height="294" url="images/User_Fig_10.png"/>
+</Figure>
+<Figure id="designing_the_collection">
+<Title>
+<Text id="218">DiseÃ±ando la colecciÃ³n</Text>
+</Title>
+<File width="376" height="294" url="images/User_Fig_11.png"/>
+</Figure>
+<Figure id="specifying_which_plug-ins_to_use">
+<Title>
+<Text id="219">Especificando los plugins que se van a usar.</Text>
+</Title>
+<File width="376" height="294" url="images/User_Fig_12.png"/>
+</Figure>
+<Figure id="configuring_arguments_to_a_plug-in">
+<Title>
+<Text id="220">Configurando los argumentos de los plugins.</Text>
+</Title>
+<File width="376" height="294" url="images/User_Fig_13.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="designing_the_collection_1">
+<Title>
+<Text id="221">DiseÃ±ando la colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="222">La pantallaÂ <i>DiseÃ±o</i>Â (figuras 11â13) le permite a uno especificar la estructura, organizaciÃ³n y presentaciÃ³n de la colecciÃ³n que se estÃ¡ creando. Tal como se mencionÃ³ antes, el resultado de este proceso se registra en un âarchivo de configuraciÃ³n de la colecciÃ³nâ, que es la forma que tiene Greenstone de expresar las funciones y programas que requiere una colecciÃ³n. Este paso incluye una serie de pantallas separadas, cada una de las cuales trata un aspecto relativo al diseÃ±o de la colecciÃ³n y sirve, en efecto, como un equivalente grÃ¡fico al proceso normal de editar manualmente el archivo de configuraciÃ³n.</Text>
+<Text id="223">Las operaciones incluyen:</Text>
+<BulletList>
+<Bullet>
+<Text id="224">Revisar y editar los metadatos a nivel de colecciÃ³n, como el tÃ­tulo, autor y disponibilidad de la colecciÃ³n.</Text>
+</Bullet>
+<Bullet>
+<Text id="225">Definir quÃ© Ã­ndices de texto completo se van a crear.</Text>
+</Bullet>
+<Bullet>
+<Text id="226">Crear subcolecciones y armar los Ã­ndices de las mismas. </Text>
+</Bullet>
+<Bullet>
+<Text id="227">AÃ±adir o eliminar el soporte de la interfaz para idiomas predefinidos.</Text>
+</Bullet>
+<Bullet>
+<Text id="228">Construir una lista de los plugins que se usarÃ¡n junto con sus argumentos. </Text>
+</Bullet>
+<Bullet>
+<Text id="229">Presentar la lista al usuario para que la revise y modifique.</Text>
+</Bullet>
+<Bullet>
+<Text id="230">Configurar plugins individuales.</Text>
+</Bullet>
+<Bullet>
+<Text id="231">Construir una lista de âclasificadoresâ, sus argumentos, asignaciÃ³n y configuraciÃ³n.</Text>
+</Bullet>
+<Bullet>
+<Text id="232">Asignar cadenas de formato a varios controles dentro de la colecciÃ³n, alterando asÃ­ su apariencia.</Text>
+</Bullet>
+<Bullet>
+<Text id="233">Revisar los conjuntos de metadatos usados en la colecciÃ³n junto con sus elementos.</Text>
+</Bullet>
+</BulletList>
+<Text id="234">En la figura 11 el usuario ha hecho click en la pestaÃ±aÂ <i>DiseÃ±o</i> y estÃ¡ revisando la informaciÃ³n general acerca de la colecciÃ³n, ingresada al momento de crearla. A la izquierda aparece una lista de las diferentes facetas que el usuario puede configurar: general, plugins de documento, tipos de bÃºsqueda, Ã­ndices de bÃºsqueda, Ã­ndices de particiÃ³n, bÃºsqueda cruzada a travÃ©s de varias colecciones, clasificadores de exploraciÃ³n, caracterÃ­sticas del formato, traducciÃ³n de texto y conjuntos de metadatos. La apariencia y funcionalidad varÃ­a entre ellas. Por ejemplo, al hacer click en el botÃ³nÂ <i>Plugins de documento</i>Â aparece la pantalla que se muestra en la figura 12, la cual le permite aÃ±adir, eliminar o configurar los plugins, asÃ­ como cambiar el orden en el que se aplican a los documentos.</Text>
+<Text id="235">Los plugins y clasificadores tienen varios argumentos u âopcionesâ diferentes que el usuario puede proporcionar. El cuadro de diÃ¡logo que aparece en la figura 13 muestra los argumentos que el usuario ha especificado para algunos de los plugins. Los campos sombreados se activan cuando el usuario aÃ±ade la opciÃ³n haciendo click en el recuadro que se encuentra a su lado. Debido a que Greenstone es un sistema abierto en constante crecimiento, el nÃºmero de opciones tiende a aumentar conforme los programadores aÃ±aden nuevos programas y funciones. Para arreglÃ¡rselas con esto, Greenstone tiene un programa de âinformaciÃ³n de pluginsâÂ  que muestra una lista de las opciones disponibles para cada plugin y la interfaz de bibliotecario recurre automÃ¡ticamente a esta lista para determinar las opciones que debe mostrar. Esto le permite a la interfaz del usuario mantener automÃ¡ticamente el ritmo de los desarrollos del programa de software.</Text>
+<Figure id="getting_ready_to_create_new_collection.">
+<Title>
+<Text id="236">PreparÃ¡ndose para crear una nueva colecciÃ³n.</Text>
+</Title>
+<File width="380" height="297" url="images/User_Fig_14.png"/>
+</Figure>
+<Figure id="previewing_the_newly_built_collection">
+<Title>
+<Text id="237">Vista previa de la nueva colecciÃ³n.</Text>
+</Title>
+<File width="380" height="272" url="images/User_Fig_15.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="building_the_collection">
+<Title>
+<Text id="238">Creando la colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="239">La pantallaÂ <i>Crear</i>Â (figura 14) se utiliza para construir una colecciÃ³n basada en los documentos y metadatos asignados. El peso de este trabajo lo lleva el cÃ³digo Greenstone. El usuario controla el proceso externo a travÃ©s de una serie de pantallas separadas, cada una de las cuales trata con los argumentos proporcionados durante las diferentes etapas del proceso de creaciÃ³n.</Text>
+<Text id="240">El usuario observa el proceso de construcciÃ³n a travÃ©s de una ventana que muestra no sÃ³lo los textos generados por los guiones de importaciÃ³n y creaciÃ³n de Ã­ndices de Greenstone, sino tambiÃ©n las barras de progreso que indican el grado general de avance de cada guiÃ³n.</Text>
+<Text id="241">La figura 14 muestra la pantallaÂ <i>Crear</i>. En la parte superior se muestran algunas opciones que pueden aplicarse durante el proceso de creaciÃ³n. El usuario selecciona los valores apropiados para cada opciÃ³n. Esta figura muestra asimismo un cuadro de ârecomendacionesâ que estÃ¡ disponible a travÃ©s de toda la interfaz para explicar la funciÃ³n de cada argumento.</Text>
+<Text id="242">Una vez que el usuario estÃ© satisfecho con los argumentos, deberÃ¡ hacer clickÂ en <i>Build Collection [Crear ColecciÃ³n]</i>Â . Greenstone imprime continuamente el texto que indica el grado de avance y Ã©ste se acompaÃ±a de una barra de progreso que muestra de forma aÃºn mÃ¡s clara esta informaciÃ³n.</Text>
+</Content>
+</Subsection>
+<Subsection id="previewing">
+<Title>
+<Text id="243">PresentaciÃ³n preliminar de la colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="244">El botÃ³n de Vista Previa de la colecciÃ³n (figura 14) se utiliza para ver la imagen de la colecciÃ³n que se acaba de crear. Al oprimir este botÃ³n se inicia un navegador de web que muestra la pÃ¡gina inicial de la colecciÃ³n (Figura 15). En la prÃ¡ctica la vista previa a menudo muestra las deficiencias en el diseÃ±o de la colecciÃ³n o en los valores de los metadatos individuales, por lo que con frecuencia el usuario debe regresar a etapas anteriores para poder corregirlas. Este botÃ³n se activa una vez que la colecciÃ³n se ha creado. La nueva colecciÃ³n tambiÃ©n se habrÃ¡ instalado en su pÃ¡gina principal Greenstone como una de las colecciones regulares.</Text>
+</Content>
+</Subsection>
+<Subsection id="help">
+<Title>
+<Text id="245">Ayuda</Text>
+</Title>
+<Content>
+<Text id="246">La ayuda en lÃ­nea siempre estÃ¡ disponible y se puede acudir a ella usando el elementoÂ <i>Ayuda</i>Â que se encuentra a la derecha de la barra principal de menÃºs en la parte superior de cada pantalla. Ãste abre un archivo estructurado jerÃ¡rquicamente con texto de ayuda, el cual toma en cuenta el contexto actual del usuario para destacar la secciÃ³n correspondiente a dicha etapa del proceso. MÃ¡s aÃºn, como se mencionÃ³ arriba cada vez que el cursor se mantenga sobre un objeto interactivo aparecerÃ¡ una pequeÃ±a ventana con ârecomendacionesâ, como se puede ver en la parte inferior de la figura 14.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="librarian_interface_user_guide">
+<Title>
+<Text id="247">Guia del Usuario de la Interfaz de Bibliotecario</Text>
+</Title>
+<Content>
+<Subsection id="starting_off">
+<Title>
+<Text id="248">Para empezar</Text>
+</Title>
+<Content>
+<Text id="249">Esta secciÃ³n explica cÃ³mo crear, cargar, guardar y borrar colecciones.</Text>
+<Part id="creating_a_new_collection">
+<Title>
+<Text id="250">Creando una nueva colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="251">Para crear una nueva colecciÃ³n abra el menÃº "Archivo" y elija la opciÃ³n "Nueva". DeberÃ¡n llenarse varios campos, aunque en caso de que lo requiera usted podrÃ¡ cambiar despuÃ©s sus valores en la pantalla de diseÃ±o.</Text>
+<Text id="252">El "TÃ­tulo de la colecciÃ³n" es el texto que aparece en la parte superior de la pÃ¡gina principal de su colecciÃ³n. Puede tener la longitud que usted quiera.</Text>
+<Text id="253">La "DescripciÃ³n del contenido" deberÃ¡ describir tan detalladamente como sea posible de lo que se trata la colecciÃ³n. Utilice la tecla [Enter] o [Intro] para dividirla en pÃ¡rrafos.</Text>
+<Text id="254">Finalmente deberÃ¡ especificar si desea que la nueva colecciÃ³n tenga la misma apariencia y conjunto de metadatos que una colecciÃ³n existente o si desea iniciar una "Nueva ColecciÃ³n" por omisiÃ³n. </Text>
+<Text id="255">Haga click en "Aceptar" para crear la colecciÃ³n. Si usted escogiÃ³ "Nueva ColecciÃ³n" se le pedirÃ¡ que elija el conjunto de metadatos que usarÃ¡ en ella. Puede elegir mÃ¡s de uno y tambiÃ©n puede aÃ±adir otros mÃ¡s adelante.</Text>
+<Text id="256">Si hace click en "Cancelar" regresarÃ¡ inmediatamente a la pantalla principal.</Text>
+</Content>
+</Part>
+<Part id="saving_the_collection">
+<Title>
+<Text id="257">Guardar la colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="258">Guarde su trabajo regularmente abriendo el menÃº "Archivo" y seleccionando "Guardar". Tome en cuenta que guardar una colecciÃ³n no es lo mismo que prepararla para que se pueda usar en Greenstone (vea la secciÃ³n Produciendo una colecciÃ³n).</Text>
+<Text id="259">La Interfaz de Bibliotecario protege su trabajo guardÃ¡ndolo cada vez que salga del programa o cargue otra colecciÃ³n.</Text>
+<Text id="260">Las colecciones se guardan en un archivo que lleva el nombre de la colecciÃ³n y la extensiÃ³n ".col", ubicado en una carpeta del mismo nombre dentro de la carpeta "colecciones" del programa Greenstone.</Text>
+</Content>
+</Part>
+<Part id="opening_an_existing_collection">
+<Title>
+<Text id="261">Abriendo una colecciÃ³n existente</Text>
+</Title>
+<Content>
+<Text id="262">Para abrir una colecciÃ³n existente elija la opciÃ³n "Abrir" en el menÃº "Archivo". Con esto aparecerÃ¡ una lista de sus colecciones Greenstone. Seleccione una para ver su descripciÃ³n y haga click en "Abrir" para cargarla. Si busca una colecciÃ³n que resida fuera de la carpeta de "colecciones" de Greenstone, entonces haga click en "Explorar" para que aparezca un cuadro de diÃ¡logo que le permita buscar en el sistema de archivos.</Text>
+<Text id="263">En caso de que mÃ¡s de una Interfaz de Bibliotecario de Greenstone estÃ© corriendo al mismo tiempo, los directorios pertinentes se "bloquean" para evitar interferencias. Al abrir una colecciÃ³n se crea un pequeÃ±o archivo de bloqueo temporal en la carpeta. Antes de abrir una colecciÃ³n la Interfaz de Bibliotecario revisa que no haya un archivo de bloqueo en ella. Se puede saber si la colecciÃ³n estÃ¡ bloqueada por el color de su icono: verde para una colecciÃ³n normal, rojo para una colecciÃ³n bloqueada. Sin embargo, cuando se sale prematuramente de la Interfaz de Bibliotecario el archivo de bloqueo a veces permanece en la carpeta. Cuando posteriormente se abre esta colecciÃ³n, la Biblioteca Digital le pregunta si quiere tomar el control. Por favor, nunca le quite el control de una colecciÃ³n a alguien que este trabajando en ese momento con ella.</Text>
+<Text id="264">Cuando usted abra una colecciÃ³n que no haya sido creada por medio de la Interfaz de Bibliotecario de Greenstone se le pedirÃ¡ que seleccione uno o mÃ¡s conjuntos de metadatos. Si no selecciona ninguno, entonces los metadatos existentes se ignorarÃ¡n. De otra manera los metadatos se importarÃ¡n tal como son cuando usted arrastre los archivos. El proceso se describe en el documento llamado Importando Metadatos Previamente Asignados.</Text>
+</Content>
+</Part>
+<Part id="deleting_collections">
+<Title>
+<Text id="265">Borrando colecciones</Text>
+</Title>
+<Content>
+<Text id="266">Para borrar definitivamente colecciones de su instalaciÃ³n de Greenstone, elija "BorrarâŠ" del menÃº "Archivo". Aparece una lista de sus colecciones. Seleccione una para ver su descripciÃ³n, marque la casilla situada en la parte inferior del diÃ¡logo, y pulse "Borrar" para borrar la colecciÃ³n. Esta acciÃ³n es irreversible, por lo que debe comprobar cuidadosamente que no necesita la colecciÃ³n antes de proceder.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="downloading_files_from_the_internet">
+<Title>
+<Text id="267">Descargando archivos de Internet</Text>
+</Title>
+<Content>
+<Text id="268">La vista "Bajar" le ayuda a descargar recursos de internet. Esta secciÃ³n explica el interfaz del mecanismo de puesta en espejo del Bibliotecario.</Text>
+<Part id="the_download_view">
+<Title>
+<Text id="269">La vista en Bajar</Text>
+</Title>
+<Content>
+<Text id="270">Esta secciÃ³n describe como configurar una tarea de descarga y como controlar el proceso de descargue. Active la vista "Bajar" haciendo clic en su pestaÃ±a. La mitad superior de la pantalla contiene los controles para realizar descargas. La mitad inferior estÃ¡ vacÃ­a inicialmente, pero despuÃ©s va a mostrar una lista de tareas pendientes y terminadas.</Text>
+<Text id="271">Los archivos se descargan en una carpeta del espacio de trabajo denominada "Archivos Descargados", y pueden utilizarse en todas las colecciones construidas con el interfaz del Bibliotecario. En esta Ã¡rea los archivos se designan con su URL completo. Para cada "host" se crea una nueva carpeta, seguida por otras para cada parte del "path". De esta manera se asegura que todos los archivos son distintos.</Text>
+<Text id="272">Utilice el primero de los controles de configuraciÃ³n de la descarga, "URL OrÃ­gen", para capturar el URL de un recurso deseado. Utilice el control "Profundidad de la Descarga" para limitar el nÃºmero de hiper-vÃ­nculos que se deben seguir al descargar: PÃ³ngalo en 0 para descargar una sola pÃ¡gina; pÃ³ngalo en 1 para descargar una pÃ¡gina y todas las pÃ¡ginas a las que apunta. El lÃ­mite de profundidad se ignora al descargar medios diferentes de pÃ¡ginas html. AdemÃ¡s, hay varios controles de chequeo que se pueden prender para activar determinadas capacidades durante una descarga especÃ­fica. Una vez se ha establecido la configuraciÃ³n, haga clic en "Descargar" para iniciar un nuevo proceso de descargue. Hay otros dos controles en forma de botones: "Preferencias", que enlaza con la secciÃ³n de conexiÃ³n de las Preferencias, en la cual se pueden editar las caracterÃ­sticas del "proxy"; y "Borrar CachÃ©", que borra todos los archivos descargados previamente.</Text>
+<Text id="273">La lista de descargas tiene una entrada por cada pÃ¡gina web descargada. Cada entrada tiene un Ã¡rea de texto que da detalles acerca de la tarea, junto con una barra que indica el avance de la actividad en ejecuciÃ³n. A la izquierda de cada entrada aparecen tres botones. "Pausa" se utiliza para detener temporalmente la descarga que se estÃ¡ ejecutando. "Ver BitÃ¡cora" abre una ventana que muestra el archivo de bitÃ¡cora de las descargas. "Cerrar" termina la descarga y quita de la lista la tarea correspondiente.</Text>
+<Text id="274">La secciÃ³n Preferencias describe como establecer una conexiÃ³n Internet por medio de un "proxy". Si se necesita autenticaciÃ³n, el servidor "proxy" pide la identificaciÃ³n y la palabra clave. El interfaz del Bibliotecario no almacena palabras claves entre sesiones.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="collecting_files_for_your_collection">
+<Title>
+<Text id="275">Reuniendo archivos para su colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="276">Una vez que usted tiene una nueva colecciÃ³n necesita meter algunos archivos en ella. Estos pueden venir desde la estructura de archivos de su computadora o de otras colecciones Greenstone. Algunos incluso ya pueden tener metadatos. Esta secciÃ³n describe la forma de importar archivos.</Text>
+<Part id="the_gather_view">
+<Title>
+<Text id="277">La pantalla de selecciÃ³n de documentos</Text>
+</Title>
+<Content>
+<Text id="278">Esta secciÃ³n describe el funcionamiento de la pantalla "Reunir" que se utiliza para seleccionar los archivos que se van a incluir en la colecciÃ³n que se estÃ¡ construyendo. La Interfaz de Bibliotecario inicia con la pantalla "Reunir". Si despuÃ©s usted desea regresar a esta pantalla haga click en la pestaÃ±a del mismo nombre que se encuentra directamente debajo de la barra de menÃºs.</Text>
+<Text id="279">Dos grandes Ã¡reas tituladas "Area de trabajo" y "ColecciÃ³n" se utilizan para transferir los archivos a su colecciÃ³n. Cada una contiene "Ã¡rboles de archivos", los cuales son representaciones grÃ¡ficas de la estructura de directorios y subdirectorios de sus archivos y carpetas.</Text>
+<Text id="280">Seleccione un elemento del Ã¡rbol haciendo click en Ã©l. (TambiÃ©n existen otras formas; vÃ©ase mÃ¡s adelante.) Haga click en el signo que se encuentra junto a una carpeta o doble click en ella para expandir (o contraer) sus contenidos. Haga doble click en un archivo para abrirlo usando un programa de aplicaciÃ³n asociado (vea la secciÃ³n AsociaciÃ³n de archivos).</Text>
+<Text id="281">El Ã¡rbol de archivos del Ã¡rea de trabajo muestra los orÃ­genes de la informaciÃ³n disponible al interfaz del Bibliotecario -- el sistema local de archivos (incluyendo unidades de disco y CD-ROM), los contenidos de las colecciones existentes de Greenstone, y el cachÃ© de archivos descargados. Usted puede copiar y consultar estos archivos pero no puede moverlos, eliminarlos o editarlos, con la excepciÃ³n de los archivos descargados, los cuales pueden ser eliminados. Navegue por este espacio para buscar los archivos que desee incluir en la colecciÃ³n.</Text>
+<Text id="282">La estructura de directorios y subdirectorios de la colecciÃ³n muestra sus contenidos. Inicialmente estÃ¡ vacÃ­a.</Text>
+<Text id="283">Se puede cambiar el tamaÃ±o de las Ã¡reas oprimiendo el botÃ³n del mouse sobre la barra gris que separa las estructuras de directorios y subdirectorios (la forma del cursor cambia) y arrastrÃ¡ndola.</Text>
+<Text id="284">En la parte inferior de la ventana se muestra un Ã¡rea de estado que informa del progreso de las acciones sobre archivos (copiando, moviendo y borrando). Puede tardar un tiempo en terminar. El botÃ³n "Detener" interrumpe cualquier acciÃ³n que se estÃ© ejecutando en ese momento.</Text>
+<Text id="285">Dos grandes botones ocupan la esquina inferior derecha de la pantalla: "Nueva carpeta", con la imagen de una carpeta, crea nuevas carpetas (vea la secciÃ³n Creando carpetas), en tanto que "Eliminar", con la imagen de un bote de basura, descarta los archivos. Al hacer click en el botÃ³n "Eliminar" se suprimirÃ¡n los archivos seleccionados de la estructura de directorios y subdirectorios de la colecciÃ³n. Asimismo, los archivos pueden eliminarse arrastrÃ¡ndolos hacia este botÃ³n.</Text>
+<Text id="286">Para seleccionar varios elementos consecutivos, seleccione el primero y a continuaciÃ³n manteniendo oprimida la tecla de mayÃºsculas o [Shift] haga click en el Ãºltimo: la selecciÃ³n incluirÃ¡ todos los elementos que se encuentran en medio. Para seleccionar varios archivos que no sean consecutivos mantenga oprimida la tecla de control o [Ctrl] mientras hace click en ellos. Utilice alternativamente estos dos mÃ©todos para seleccionar grupos de elementos que no estÃ©n juntos.</Text>
+<Text id="287">En ocasiones algunas carpetas, como la que contiene sus propias pÃ¡ginas Web, tienen un significado especial. La Interfaz de Bibliotecario puede asignar dichas carpetas al primer nivel de la estructura de directorios y subdirectorios. Para hacerlo haga click con el botÃ³n derecho del mouse sobre la carpeta deseada. Seleccione "Crear un acceso directo" y dÃ©le un nombre a la carpeta. Para quitar un elemento haga click con el botÃ³n derecho del mouse sobre la carpeta mapeada y seleccione "Eliminar acceso directo".</Text>
+</Content>
+</Part>
+<Part id="creating_folders">
+<Title>
+<Text id="288">Creando carpetas</Text>
+</Title>
+<Content>
+<Text id="289">Utilice las carpetas que se encuentran en la estructura de directorios y subdirectorios de la colecciÃ³n para agrupar archivos y hacer que sean mÃ¡s fÃ¡ciles de encontrar. Las carpetas pueden contener a su vez otras subcarpetas. No hay prÃ¡cticamente ningÃºn lÃ­mite en cuanto al nÃºmero de carpetas que se pueden tener o quÃ© tan profundamente anidadas puedan estar.</Text>
+<Text id="290">Para crear una nueva carpeta, una opciÃ³n es seleccionar una carpeta existente en la estructura de directorios y subdirectorios de la colecciÃ³n y hacer click en el botÃ³n "Nueva carpeta". La nueva carpeta aparecerÃ¡ dentro de la que se seleccionÃ³ primero o en el nivel superior si no se seleccionÃ³ ninguna. Se le pedirÃ¡ que le dÃ© un nombre a la carpeta (el valor por omisiÃ³n es "Nueva carpeta").</Text>
+<Text id="291">TambiÃ©n se pueden crear nuevas carpetas haciendo click sobre una carpeta con el botÃ³n derecho del mouse, eligiendo la opciÃ³n "Nueva carpeta" y continuando tal como se describe arriba.</Text>
+</Content>
+</Part>
+<Part id="adding_files">
+<Title>
+<Text id="292">AÃ±adiendo archivos</Text>
+</Title>
+<Content>
+<Text id="293">Los archivos se pueden copiar arrastrÃ¡ndolos y colocÃ¡ndolos en una colecciÃ³n. El cursor se convierte en un fantasma del elemento seleccionado (o, si se ha seleccionado mÃ¡s de uno, del nÃºmero de ellos). Coloque la selecciÃ³n en la estructura de directorios y subdirectorios de la colecciÃ³n para copiar ahÃ­ los archivos (si la fuente son los archivos del Ã¡rea de trabajo) o muÃ©valos de lugar dentro de la misma colecciÃ³n (si la fuente son los archivos de la colecciÃ³n).</Text>
+<Text id="294">Cuando se copien varios archivos en una carpeta todos estarÃ¡n al mismo nivel, sin importar la estructura de las carpetas en las que se encontraban originalmente. Cuando se copie un segundo archivo con el mismo nombre en la misma carpeta se le preguntarÃ¡ si desea reemplazar el archivo existente. Si la respuesta es "No" entonces el archivo no se copiarÃ¡, pero los demÃ¡s sÃ­. Para cancelar las acciones restantes de copiado haga click en el botÃ³n "Detener".</Text>
+<Text id="295">Ãnicamente se moverÃ¡n los elementos "de mÃ¡s alto nivel" en una selecciÃ³n. Una carpeta estÃ¡ a un nivel mÃ¡s alto que los elementos que se encuentran en su interior, por lo que no se podrÃ¡n seleccionar los archivos de una carpeta y la carpeta al mismo tiempo. </Text>
+<Text id="296">Cuando se aÃ±ada un archivo, la Interfaz de Bibliotecario buscarÃ¡ a travÃ©s de las carpetas fuente los archivos auxiliares que contienen los metadatos asignados previamente a dicho archivo y, si encuentra alguno, empezarÃ¡ a importar estos metadatos. Conforme la operaciÃ³n siga adelante se le pedirÃ¡ (quizÃ¡ varias veces) que proporcione informaciÃ³n adicional para conciliar los metadatos importados con los conjuntos de metadatos de su colecciÃ³n. Este proceso incluye muchos avisos diferentes, los cuales se describen en la secciÃ³n Importando metadatos previamente asignados. Para obtener una explicaciÃ³n mÃ¡s detallada sobre la forma de asociar metadatos a los archivos lea el CapÃ­tulo 2 de la GuÃ­a del Programador de Greenstone: Obteniendo el mÃ¡ximo beneficio de sus documentos.</Text>
+</Content>
+</Part>
+<Part id="removing_files">
+<Title>
+<Text id="297">Eliminando archivos</Text>
+</Title>
+<Content>
+<Text id="298">Existen varios mÃ©todos para eliminar archivos y carpetas. Primero se deben indicar los elementos que se desea eliminar seleccionando los archivos y carpetas tal como se describe en la secciÃ³n de selecciÃ³n de documentos para la colecciÃ³n.</Text>
+<Text id="299">Una vez que se han seleccionado los archivos, haga click en el botÃ³n "Eliminar" o presione la tecla [Del], [Supr] o [Suprimir], dependiendo del teclado de su computadora, o arrÃ¡strelos desde la colecciÃ³n hasta el botÃ³n "Eliminar" y suÃ©ltelos ahÃ­.</Text>
+</Content>
+</Part>
+<Part id="filtering_the_tree">
+<Title>
+<Text id="300">Filtrando la estructura de directorios y subdirectorios</Text>
+</Title>
+<Content>
+<Text id="301">"Filtrar" la estructura de directorios y subdirectorios de la colecciÃ³n limita la bÃºsqueda a determinados tipos de archivos.</Text>
+<Text id="302">El menÃº "Mostrar archivos" debajo de cada estructura de directorios y subdirectorios muestra una lista de filtros definidos previamente, como por ejemplo el de "ImÃ¡genes". Al elegir uno se ocultan temporalmente todos los demÃ¡s archivos. Para restaurarlos, cambie el filtro a "Todos los archivos". Estas operaciones no alteran la colecciÃ³n ni afectan las carpetas en la estructura de archivos.</Text>
+<Text id="303">Se puede especificar un filtro en particular escribiendo un patrÃ³n que corresponda con los tipos de archivos que se desea filtrar (SÃ³lo en los modos Especialista de Sistemas Bibliotecarios y Experto). Utilice las abreviaturas estÃ¡ndar del sistema como "*.*" o "*.doc" ("*" equivale a cualquier caracter).</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="enriching_the_collection_with_metadata">
+<Title>
+<Text id="304">Enriqueciendo la colecciÃ³n con metadatos</Text>
+</Title>
+<Content>
+<Text id="305">DespuÃ©s de haber juntado varios archivos en una colecciÃ³n, enriquÃ©zcalos con informaciÃ³n adicional. Esta secciÃ³n explica la forma en que se crean, editan, asignan y recuperan los metadatos, y la forma de usar fuentes externas de metadatos (vÃ©ase tambiÃ©n el CapÃ­tulo 2 de la GuÃ­a del Programador de Greenstone: Obteniendo el mÃ¡ximo beneficio de sus documentos).</Text>
+<Part id="the_enrich_view">
+<Title>
+<Text id="306">La pantalla de asignaciÃ³n de metadatos</Text>
+</Title>
+<Content>
+<Text id="307">Utilice la pantalla "Enriquecer" para asignar metadatos a los documentos de la colecciÃ³n. Los metadatos son datos acerca de los datos: tÃ­tulo, autor, fecha de creaciÃ³n, etc. Cada metadato tiene dos partes: el "elemento" dice el tipo de metadato que es (como por ejemplo el autor) y el "valor" da la informaciÃ³n de ese elemento (como por ejemplo el nombre del autor).</Text>
+<Text id="308">En la parte izquierda de la pantalla "Enriquecer" se encuentra la estructura de directorios y subdirectorios de la colecciÃ³n. A la derecha estÃ¡ la Tabla de Metadatos, la cual muestra los metadatos de los archivos y carpetas seleccionados. Los nombres de las columnas estÃ¡n en gris en la parte superior y se pueden cambiar de tamaÃ±o arrastrando la lÃ­nea que las separa. Si se seleccionan varios archivos, el texto en negro indica que el valor es comÃºn a todos ellos, mientras que el texto sombreado indica que no. Los valores en negro se pueden actualizar o eliminar, mientras que los que estÃ¡n sombreados se pueden eliminar de los que los tienen o agregarse a los demÃ¡s.</Text>
+<Text id="309">Un icono en forma de carpeta puede aparecer junto a algunas entradas de metadatos. Esto indica que los valores se heredan de la carpeta en la que se encuentra el archivo. Los metadatos heredados no se pueden editar o eliminar, sino Ãºnicamente agregarse o sobreescribirse. Haga click en el icono de la carpeta para ir inmediatamente a la carpeta en la que se asignaron los metadatos.</Text>
+<Text id="310">Pulsando sobre el elemento de matadato en la tabla se mostrarÃ¡n los valores existentes para ese elemento en el Ã¡rea "Valores existentes para..." situada debajo de la tabla. La estructura de valores se puede expandir y contraer. Normalmente es una lista que muestra todos los valores ingresados previamente para un elemento seleccionado. Al hacer click en una entrada Ã©sta aparece automÃ¡ticamente en el campo de valores. Y a la inversa, al escribir en el campo se selecciona la entrada de la estructura de valores que empieza con los caracteres ingresados. Al oprimir [Tab] se completa automÃ¡ticamente el valor seleccionado.</Text>
+<Text id="311">Los valores de los metadatos se pueden organizar jerÃ¡rquicamente. Esto se muestra en la estructura de valores por medio de carpetas para los niveles internos. Los valores jerÃ¡rquicos pueden ingresarse utilizando el carÃ¡cter "|" para separar los niveles. Por ejemplo, se puede usar "Cartas|Rojo|Diamantes|Siete" en una jerarquÃ­a que representa un mazo de cartas. Esto permite agrupar los valores, en tanto que los grupos tambiÃ©n pueden asignarse en forma de metadatos a los archivos.</Text>
+<Text id="312">Greenstone extrae automÃ¡ticamente los metadatos de los documentos para formar un conjunto de metadatos cuyos elementos llevan el prefijo "ex.". Ãste no tiene estructura de valores y no puede editarse.</Text>
+</Content>
+</Part>
+<Part id="selecting_metadata_sets">
+<Title>
+<Text id="313">Seleccionando conjuntos de metadatos</Text>
+</Title>
+<Content>
+<Text id="314">Los grupos de elementos de metadatos definidos previamente son conocidos como "conjuntos de metadatos". Un ejemplo es el conjunto de metadatos de Dublin Core. Cuando se aÃ±ade un conjunto de metadatos a una colecciÃ³n, sus elementos se vuelven elegibles para que el usuario los pueda seleccionar. TambiÃ©n se puede tener mÃ¡s de un conjunto. Para evitar conflictos de nombre, un identificador que describe al conjunto de metadatos se agrega como prefijo al nombre del elemento. Por ejemplo, el elemento Creator de Dublin Core se convierte en "dc.Creator". Los conjuntos de metadatos se guardan en la carpeta de metadatos de la Interfaz de Bibliotecario y llevan el sufijo ".mds".</Text>
+<Text id="315">Para controlar los conjuntos de metadatos usados en una colecciÃ³n, utilice la opciÃ³n "Conjuntos de metadatos" en la vista DiseÃ±o.</Text>
+</Content>
+</Part>
+<Part id="appending_new_metadata">
+<Title>
+<Text id="316">Agregando nuevos metadatos</Text>
+</Title>
+<Content>
+<Text id="317">Ahora aÃ±adiremos un Ã­tem de metadato -- tanto un elemento como un valor -- a un archivo. Primero, seleccione el archivo en la estructura de directorios y subdirectorios de la colecciÃ³n que se encuentra a la izquierda. Esto hace que cualquier metadato asignado previamente a este archivo aparezca en la tabla de la derecha.</Text>
+<Text id="318">A continuaciÃ³n, seleccione el elemento de metadato que desea aÃ±adir haciendo click en la fila correspondiente de la tabla.</Text>
+<Text id="319">Escriba el valor en el campo de valores. Use el carÃ¡cter "|" para aÃ±adir estructura, tal y como se explica en Vista para Enriquecer. Pulsando las teclas de flecha [Arriba] o [Abajo] se guardarÃ¡n los metadatos y se moverÃ¡ la selecciÃ³n adecuadamente. Pulsando [Retorno] se guardarÃ¡n los metadatos y se crearÃ¡ una nueva entrada vacÃ­a para un elemento de metadato, permitiendo asignar varios valores al mismo.</Text>
+<Text id="320">TambiÃ©n se pueden aÃ±adir metadatos a una carpeta o a varios archivos seleccionados al mismo tiempo. Estos metadatos se aÃ±adirÃ¡ a todos los archivos que forman parte de la carpeta o de la selecciÃ³n, asÃ­ como a las subcarpetas. Recuerde que si usted asigna metadatos a una carpeta, todos los archivos nuevos que se encuentren en ella heredarÃ¡n automÃ¡ticamente los valores de la carpeta.</Text>
+</Content>
+</Part>
+<Part id="adding_previously_defined_metadata">
+<Title>
+<Text id="321">AÃ±adiendo Metadatos Previamente Definidos</Text>
+</Title>
+<Content>
+<Text id="322">Para aÃ±adir metadatos con un valor existente, seleccione primero el archivo y a continuaciÃ³n el valor requerido de la estructura de valores, expandiendo las carpetas tanto como sea necesario. El valor de la entrada seleccionada aparecerÃ¡ automÃ¡ticamente en el campo de texto (otra alternativa es utilizar las funciones de selecciÃ³n automÃ¡tica y completamiento automÃ¡tico de la estructura de valores).</Text>
+<Text id="323">El proceso de aÃ±adir metadatos con valores existentes a carpetas o a varios archivos juntos es exactamente igual.</Text>
+</Content>
+</Part>
+<Part id="editing_or_removing_metadata">
+<Title>
+<Text id="324">Editar o Borrar Metadatos</Text>
+</Title>
+<Content>
+<Text id="325">Para editar o borrar elementos de metadato, primero seleccione el campo apropiado, y luego el valor de metadato de la tabla. Edite el campo del valor, y borre todo el texto si quiere borrar el metadato.</Text>
+<Text id="326">El proceso es el mismo cuando se actualiza un directorio que contiene subdirectorios o mÃºltiples archivos, pero sÃ³lo se pueden actualizar metadatos que sean comunes a todos los archivos y carpetas seleccionados. </Text>
+<Text id="327">El arbol de valores muestra todos los valores asignados actualmente, asÃ­ como todos los valores previos de la sesiÃ³n activa, por lo que los valores modificados o borrados permanecerÃ¡n en el Ã¡rbol. Si cierra y vuelve a abrir la colecciÃ³n, se borrarÃ¡n los valores que ya no estÃ¡n asignados.</Text>
+</Content>
+</Part>
+<Part id="reviewing_assigned_metadata">
+<Title>
+<Text id="328">Revisando los metadatos asignados</Text>
+</Title>
+<Content>
+<Text id="329">En ocasiones es necesario ver los metadatos asignados a varios o a todos los archivos al mismo tiempo, por ejemplo, para determinar la forma en que quedan muchos archivos para trabajar en ellos o para tener una idea de la diferencia de tiempo entre las fechas.</Text>
+<Text id="330">Seleccione los archivos que desea examinar, pulse el botÃ³n derecho del ratÃ³n y elija "Metadatos AsignadosâŠ". Con lo que aparecerÃ¡ una ventana llamada "Todos los metadatos", ocupada en su mayor parte por una tabla de varias columnas. La primera columna muestra los nombres de los archivos, mientras que las filas muestran todos los valores asignados a dichos archivos.</Text>
+<Text id="331">Si se seleccionaron muchos archivos es posible que transcurra algÃºn tiempo antes de que se abra la ventana. Mientras tanto usted puede seguir usando la Interfaz de Bibliotecario.</Text>
+<Text id="332">Cuando la tabla sea demasiado grande se puede refinar aplicando los filtros a las columnas. Conforme se aÃ±adan nuevos filtros, Ãºnicamente aquellas filas que concuerden con ellos seguirÃ¡n siendo visibles. Para establecer, modificar o borrar un filtro haga click en el icono con forma de embudo que se encuentra en la parte superior de la columna. Se le indicarÃ¡ que proporcione informaciÃ³n sobre el filtro. Una vez que un filtro se ha aplicado, el encabezado de la columna cambia de color.</Text>
+<Text id="333">El aviso tiene una pestaÃ±a "Sencilla" y una "Avanzada". La versiÃ³n sencilla filtra las columnas de tal manera que sÃ³lo muestren las filas que contienen un determinado valor ("*" corresponde a todos los valores). Los valores de los metadatos se pueden seleccionar de la lista. La versiÃ³n avanzada permite diferentes operaciones de concordancia: "debe empezar con", "no contiene", "alfabÃ©ticamente menos que" y "es igual a". El valor se puede editar con cualquier cadena de caracteres (incluyendo "*") y se puede elegir que la concordancia no tome en cuenta el caso. Finalmente, se puede especificar una segunda condiciÃ³n de concordancia que se puede usar para especificar un rango de valores (seleccionando "Y") o valores alternativos (seleccionando "O"). Debajo de esta Ã¡rea hay un cuadro que le permite cambiar el orden de clasificaciÃ³n (ascendente o descendente). Una vez que haya terminado, haga click en "Filtrar" para aplicar el nuevo filtro a la columna. Para quitar el filtro haga click en "Borrar filtro". Recuerde que los detalles del filtro se conservan incluso cuando el filtro se borra.</Text>
+<Text id="334">Por ejemplo, para ordenar la tabla elija una columna, seleccione el filtro por omisiÃ³n (un filtro Sencillo en "*") y escoja el orden ascendente o descendente.</Text>
+</Content>
+</Part>
+<Part id="importing_previously_assigned_metadata">
+<Title>
+<Text id="335">Importando metadatos previamente asignados</Text>
+</Title>
+<Content>
+<Text id="336">Esta secciÃ³n describe cÃ³mo importar metadtos previamente asignados, es decir, metadatos asignados a los documentos antes de que fuesen aÃ±adidos a la colecciÃ³n.</Text>
+<Text id="337">Si se han asignado previamente metadatos en una forma reconocible por la Interfaz de Bibliotecario, por ejemplo, cuando se seleccionan documentos de una colecciÃ³n Greenstone existente, entonces Ã©stos se importarÃ¡n automÃ¡ticamente cuando usted aÃ±ada el archivo. Para poder hacer esto los metadatos deben mapearse hacia el conjunto de metadatos disponible en la colecciÃ³n. </Text>
+<Text id="338">La Interfaz de Bibliotecario enviarÃ¡ un mensaje solicitando la informaciÃ³n necesaria. El mensaje incluirÃ¡ breves instrucciones y a continuaciÃ³n mostrarÃ¡ el nombre del elemento de metadato que se estÃ¡ importando, tal como aparece en el archivo fuente. Este campo no se podrÃ¡ editar o cambiar. A continuaciÃ³n elija el conjunto de metadatos hacia el que el nuevo elemento deberÃ¡ mapearse y el correspondiente elemento de metadato en ese conjunto. El sistema selecciona automÃ¡ticamente la correspondencia mÃ¡s cercana en tÃ©rminos de conjunto y elemento para el nuevo metadato.</Text>
+<Text id="339">DespuÃ©s de revisar el mapeo, usted puede elegir "AÃ±adir" para aÃ±adir el nuevo elemento de metadato al conjunto de metadatos que se haya seleccionado. (Esto sÃ³lo es posible si no hay un elemento del mismo nombre dentro del conjunto seleccionado.) "Combinar" mapea el nuevo elemento hacia el que el usuario haya elegido. Finalmente, "Ignorar" no importa ningÃºn metadato con este nombre de elemento. Una vez que usted haya especificado la forma de importar una parte del metadato, la informaciÃ³n del proceso se conserva durante todo el tiempo de vida de la colecciÃ³n.</Text>
+<Text id="340">Para mayor informaciÃ³n sobre los archivos metadata.xml que Greenstone utiliza para guardar metadatos, vea el CapÃ­tulo 2 de la GuÃ­a del Programador de Greenstone: Obteniendo el mÃ¡ximo beneficio de sus documentos.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="designing_your_collection_appearance">
+<Title>
+<Text id="341">DiseÃ±ando la apariencia de su colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="342">Una vez que los archivos estÃ¡n marcados con metadatos, a continuaciÃ³n se debe decidir la forma en que aparecerÃ¡n ante los usuarios como parte de una colecciÃ³n Greenstone. Â¿QuÃ© tipo de informaciÃ³n se podrÃ¡ buscar? Â¿De quÃ© medios se dispone para navegar por los documentos? Â¿En quÃ© idiomas? Â¿DÃ³nde aparecerÃ¡n los botones en la pÃ¡gina? Todas estas cosas se pueden personalizar. Esta secciÃ³n describe la forma de hacerlo.</Text>
+<Part id="the_design_view">
+<Title>
+<Text id="343">La pantalla de diseÃ±o</Text>
+</Title>
+<Content>
+<Text id="344">Esta secciÃ³n le presenta la pantalla de DiseÃ±o y le explica la forma de navegar entre las diferentes opciones de este conjunto.</Text>
+<Text id="345">Con la Interfaz de Bibliotecario usted puede configurar la forma en que la colecciÃ³n aparecerÃ¡ frente al usuario. Las opciones se dividen en diferentes secciones, cada una relacionada con una etapa particular de navegaciÃ³n o presentaciÃ³n.</Text>
+<Text id="346">A la izquierda se encuentra una lista de las diferentes pantallas, en tanto que a la derecha estÃ¡n los controles asociados a la pantalla que estÃ¡ activa en ese momento. Para cambiar a una pantalla diferente haga click en la lista.</Text>
+<Text id="347">Para entender las etapas y los tÃ©rminos usados en el diseÃ±o de una colecciÃ³n, lea primero los CapÃ­tulos 1 y 2 de la GuÃ­a del Programador de Greenstone.</Text>
+</Content>
+</Part>
+<Part id="general">
+<Title>
+<Text id="348">General</Text>
+</Title>
+<Content>
+<Text id="349">Esta secciÃ³n explica la forma de revisar y modificar los ajustes generales asociados a una colecciÃ³n. Primero que nada, en la parte de "Secciones de diseÃ±o" haga click en "General".</Text>
+<Text id="350">AquÃ­ pueden modificarse los valores proporcionados durante la fase de creaciÃ³n de la colecciÃ³n.</Text>
+<Text id="351">Primero se encuentran las direcciones de correo electrÃ³nico del creador y del administrador de la colecciÃ³n. El siguiente campo le permite cambiar el tÃ­tulo de la colecciÃ³n. El directorio en el que se almacena la colecciÃ³n se muestra al lado, pero no puede editarse. El que sigue especifica (en forma de URL) el icono que aparecerÃ¡ en el Ã¡ngulo superior izquierdo de la pÃ¡gina "Acerca de" y el siguiente es el icono usado en la pÃ¡gina de la biblioteca digital Greenstone para conectarse a la colecciÃ³n. Entonces, una casilla controla que la colecciÃ³n sea o no accesible pÃºblicamente. Finalmente viene el Ã¡rea de texto que permite dar una "DescripciÃ³n de la ColecciÃ³n", tal como se explica en la secciÃ³n Creando una nueva colecciÃ³n.</Text>
+</Content>
+</Part>
+<Part id="document_plugins">
+<Title>
+<Text id="352">Plugins</Text>
+</Title>
+<Content>
+<Text id="353">Esta secciÃ³n describe la forma de configurar los plugins que la colecciÃ³n utiliza. Explica el modo de especificar los plugins que se utilizarÃ¡n, los parÃ¡metros que emplearÃ¡n y el orden en el que se aplicarÃ¡n. En la parte de "Secciones de diseÃ±o" haga click en "Plugins de documento".</Text>
+<Text id="354">Para aÃ±adir un plugin, escÃ³jalo de la lista "Seleccione el plugin que se va a aÃ±adir" que se encuentra en la parte inferior de la pantalla y haga click en "AÃ±adir plugin". AparecerÃ¡ una ventana titulada "Argumentos de configuraciÃ³n", la cual se explica mÃ¡s adelante. Una vez que usted haya configurado el nuevo plugin, este se aÃ±adirÃ¡ al final de la lista de "Plugins asignados actualmente". Note que, excepto para UnknownPlug, cada plugin sÃ³lo puede aparecer una vez en la lista.</Text>
+<Text id="355">Para quitar un plugin de la lista, selecciÃ³nelo y haga click en "Eliminar plugin".</Text>
+<Text id="356">Los plugins se configuran por medio de argumentos. Para modificarlos, seleccione un plugin de la lista y haga click en "Configurar plugin" (o doble click en el plugin). Aparece un diÃ¡logo "Configurando Argumentos" con varios controles para especificar argumentos.</Text>
+<Text id="357">Existen diferentes tipos de controles. Algunos son recuadros y al hacer click en ellos se aÃ±ade la opciÃ³n correspondiente al plugin. Otros son cadenas de texto con un recuadro y un campo de texto. Haga click en el cuadro para habilitarlo y escriba el argumento (expresiÃ³n regular, ruta de archivo, etc.). Otros son menÃºs descendentes desde los que se puede seleccionar un conjunto dado de valores. Para saber lo que hace un argumento, coloque el cursor del mouse encima de su nombre y la descripciÃ³n aparecerÃ¡.</Text>
+<Text id="358">Una vez que usted haya cambiado la configuraciÃ³n, haga click en "Aceptar" para guardar los cambios y cerrar el cuadro de diÃ¡logo o en "Cancelar" para cerrar el cuadro de diÃ¡logo sin cambiar ningÃºn argumento. </Text>
+<Text id="359">Los plugins de la lista se ejecutan en orden y en ocasiones Ã©ste es importante. El orden de los plugins sÃ³lo se puede cambiar en los modos Especialista de Sistemas Bibliotecarios y Experto (vea la secciÃ³n Preferencias). </Text>
+</Content>
+</Part>
+<Part id="search_types">
+<Title>
+<Text id="360">Tipos de bÃºsqueda</Text>
+</Title>
+<Content>
+<Text id="361">Esta secciÃ³n explica la forma de modificar una nueva funciÃ³n de diseÃ±o de Greenstone llamada "Tipos de bÃºsqueda", que permite la bÃºsqueda por campos. Los tipos de bÃºsqueda especifican el tipo de bÃºsqueda con el que contarÃ¡n las interfaces: formas, bÃºsqueda por campos y/o bÃºsqueda de sÃ³lo texto. En la parte de "Secciones de diseÃ±o" haga click en "Tipos de diseÃ±o".</Text>
+<Text id="362">Cuando ingrese a la pantalla de tipos de bÃºsqueda marque primero el recuadro "Permitir bÃºsquedas avanzadas", lo cual activa todos los demÃ¡s controles. Esto cambia la colecciÃ³n de forma que usa un mecanismo de indexado que permite la bÃºsqueda por campos. La especificaciÃ³n de Ã­ndices es ligeramente diferente en este modo. (Cuando se cambia entre bÃºsqueda estÃ¡ndar y avanzada, GLI intenta hacer correctamente el cambio de Ã­ndices, pero no lo hace de forma perfecta).</Text>
+<Text id="363">Para aÃ±adir un tipo de bÃºsqueda, selecciÃ³nelo de la lista "Tipos de bÃºsqueda" y haga click en "AÃ±adir tipo de bÃºsqueda". Cada tipo puede aparecer en la lista solamente una vez. El primer tipo de bÃºsqueda serÃ¡ el predefinido, y aparecerÃ¡ en la pÃ¡gina de bÃºsqueda de la colecciÃ³n construida. Los otros podrÃ¡n seleccionarse desde la pÃ¡gina de preferencias.</Text>
+<Text id="364">Para quitar un tipo de bÃºsqueda, selecciÃ³nelo de la lista "Tipos de bÃºsqueda asignados actualmente" y haga click en "Eliminar tipo de bÃºsqueda". La lista deberÃ¡ contener al menos uno.</Text>
+</Content>
+</Part>
+<Part id="search_indexes">
+<Title>
+<Text id="365">Ãndices de bÃºsqueda</Text>
+</Title>
+<Content>
+<Text id="366">Los Ã­ndices especifican las partes de la colecciÃ³n que se pueden buscar. Esta secciÃ³n explica la forma de aÃ±adir y eliminar Ã­ndices, asÃ­ como predeterminar un Ã­ndice por omisiÃ³n. En la parte correspondiente a "Secciones de diseÃ±o" haga click en "Ãndices de bÃºsqueda".</Text>
+<Text id="367">Para aÃ±adir un Ã­ndice escriba el nombre que le quiera dar en el campo "Nombre del Ã­ndice". Seleccione las fuentes de informaciÃ³n que se van a indexar haciendo click en los recuadros que se encuentran a un lado. La lista mostrarÃ¡ todos los elementos de metadatos asignados, asÃ­ como el texto completo. DespuÃ©s de seleccionar las fuentes de datos, elija la granularidad del Ã­ndice usando el menÃº de "Nivel". Una vez que se han completado estos detalles, la opciÃ³n "AÃ±adir Ã­ndice" se activa (a menos que haya un Ã­ndice con los mismos parÃ¡metros). Haga click en ella para aÃ±adir el nuevo Ã­ndice.</Text>
+<Text id="368">Para editar un Ã­ndice, selecciÃ³nelo, cambie los detalles del Ã­ndice, y pulse "Reemplazar Ãndice".</Text>
+<Text id="369">Para quitar un Ã­ndice de la lista de Ã­ndices asignados, selecciÃ³nelo y haga click en "Eliminar Ã­ndice".</Text>
+<Text id="370">Para crear un Ã­ndice que cubra todo el texto y todos los metadatos, pulse sobre "AÃ±adir todos".</Text>
+<Text id="371">El Ã­ndice predeterminado es el que se usa en la pÃ¡gina de bÃºsqueda de la colecciÃ³n y lleva la etiqueta "[Indice por omisiÃ³n]" en la lista de "Ãndices asignados". Para establecer un Ã­ndice por omisiÃ³n, selecciÃ³nelo de la lista y haga click en "Predeterminar".</Text>
+<Text id="372">Si la opciÃ³n de bÃºsqueda avanzada estÃ¡ activa (a travÃ©s de la pantalla de tipos de bÃºsqueda) los controles de indexaciÃ³n serÃ¡n diferentes. Hay una nueva fuente de pseudodatos llamada "allfields" (todos los campos) que permite buscar a travÃ©s de todos los Ã­ndices especificados al mismo tiempo. Los niveles no se asignan a un Ã­ndice en particular, sino que se aplican a todos los Ã­ndices. De esta manera los Ã­ndices y niveles se aÃ±aden por separado. "AÃ±adir todos" crea un Ã­ndice independiente para cada metadato en este modo.</Text>
+<Text id="373">El nombre de cada Ã­ndice serÃ¡ el de la fuente por omisiÃ³n. Para cambiar el nombre, seleccione un Ã­ndice, cambie sus detalles y haga click en "Reemplazar Ã­ndice".</Text>
+</Content>
+</Part>
+<Part id="partition_indexes">
+<Title>
+<Text id="374">Particiones</Text>
+</Title>
+<Content>
+<Text id="375">Los Ã­ndices se construyen sobre fuentes de metadatos o textos especÃ­ficos, por lo que el espacio de bÃºsqueda se puede controlar aÃºn mÃ¡s particionando el Ã­ndice, ya sea por idioma o por medio de un filtro determinado previamente. Esta secciÃ³n describe la forma de hacerlo. En la parte de "Secciones de diseÃ±o" haga click en "Particionar Ã­ndices".</Text>
+<Text id="376">La pantalla "Particionar Ã­ndices" tiene tres pestaÃ±as: "Definir filtros", "Asignar particiones" y "Asignar idiomas". Para saber mÃ¡s acerca de las particiones lea la secciÃ³n correspondiente a subcolecciones y subÃ­ndices en el CapÃ­tulo 2 de la GuÃ­a del Programador de Greenstone.</Text>
+<Text id="377">La pantalla de ParticiÃ³n de Ãndices sÃ³lo se activa en los modos Especialista de Sistemas Bibliotecarios y Experto (vea la secciÃ³n Preferencias). Recuerde que el nÃºmero total de particiones generadas es una combinaciÃ³n de todos los Ã­ndices, filtros de subcolecciÃ³n e idiomas seleccionados. De esta manera, dos Ã­ndices con dos filtros de subcolecciÃ³n en dos idiomas producirÃ¡n ocho particiones.</Text>
+</Content>
+</Part>
+<Part id="define_filters">
+<Title>
+<Text id="378">Definir filtros</Text>
+</Title>
+<Content>
+<Text id="379">Los filtros le permiten agrupar en una subcolecciÃ³n todos los documentos de un Ã­ndice para los cuales un valor de metadato sigue un patrÃ³n definido.</Text>
+<Text id="380">Para crear un filtro haga click en la pestaÃ±a "Definir filtros" y escriba el nombre del nuevo filtro en el campo titulado "Nombre del filtro de la subcolecciÃ³n". A continuaciÃ³n elija un atributo del documento con el cual se va a contrastar, ya sea un elemento de metadato o el nombre del archivo en cuestiÃ³n. Ingrese una expresiÃ³n regular que se utilizarÃ¡ durante la contrastaciÃ³n. Usted puede variar libremente entre "Incluir" documentos que concuerden con el filtro o "Excluirlos". Por Ãºltimo, usted tambiÃ©n puede especificar cualquiera de los indicadores estÃ¡ndar de expresiones regulares PERL para usarlos al momento de contrastar (p. ej. "i" para concordancias que no tomen en cuenta el caso). Haga click en "AÃ±adir filtro" para aÃ±adir el filtro a la lista de "Filtros definidos para la subcolecciÃ³n".</Text>
+<Text id="381">Para quitar un filtro de la lista, selecciÃ³nelo y haga click en "Eliminar filtro".</Text>
+<Text id="382">Para modificar un filtro, selecciÃ³nelo de la lista, cambie cualquiera de los valores que aparecen en los controles de ediciÃ³n y haga click en "Reemplazar filtro" para guardar los cambios.</Text>
+</Content>
+</Part>
+<Part id="assign_partitions">
+<Title>
+<Text id="383">Asignar particiones</Text>
+</Title>
+<Content>
+<Text id="384">Una vez que haya definido el filtro de una subcolecciÃ³n, utilice la pestaÃ±a "Asignar particiones" para construir los Ã­ndices del filtro (o de un grupo de filtros). Seleccione el filtro o los filtros que desee de la lista "Filtros definidos para la subcolecciÃ³n", ingrese un nombre para la particiÃ³n en el campo "Nombre de la particiÃ³n" y haga click en "AÃ±adir particiÃ³n".</Text>
+<Text id="385">Para quitar una particiÃ³n de la lista, selecciÃ³nela y haga click en "Eliminar particiÃ³n".</Text>
+<Text id="386">Para hacer que una particiÃ³n determinada sea el valor por omisiÃ³n, selecciÃ³nela de la lista y haga click en "Predeterminar".</Text>
+</Content>
+</Part>
+<Part id="assign_languages">
+<Title>
+<Text id="387">Asignar idiomas</Text>
+</Title>
+<Content>
+<Text id="388">Esta secciÃ³n describe la forma de limitar los Ã­ndices de bÃºsqueda a ciertos idiomas. Esto se hace generando una particiÃ³n por medio de la pestaÃ±a "Asignar idiomas" que se encuentra en la pantalla "Particionar Ã­ndices".</Text>
+<Text id="389">Para aÃ±adir un nuevo idioma use la pestaÃ±a "Asignar idiomas" a fin de construirle un Ã­ndice. Seleccione el idioma en la lista descendente "Idioma que se va a aÃ±adir" y haga click en "AÃ±adir idioma".</Text>
+<Text id="390">Para quitar un idioma, escÃ³jalo de la lista "SelecciÃ³n de idiomas" y haga click en "Eliminar idioma".</Text>
+<Text id="391">Para establecer un idioma por omisiÃ³n, selecciÃ³nelo de la lista y haga click en "Predeterminar".</Text>
+</Content>
+</Part>
+<Part id="cross-collection_search">
+<Title>
+<Text id="392">BÃºsqueda cruzada a travÃ©s de varias colecciones</Text>
+</Title>
+<Content>
+<Text id="393">Greenstone puede buscar a travÃ©s de varias colecciones distintas como si fueran una sola. Esto se hace especificando una lista de otras colecciones que puedan ser buscadas junto con la actual. En la parte de "Secciones de diseÃ±o" haga click en "BÃºsqueda cruzada".</Text>
+<Text id="394">La pantalla de bÃºsqueda cruzada muestra una lista de las colecciones disponibles. La colecciÃ³n actual estÃ¡ marcada y no se puede quitar de la selecciÃ³n. Para aÃ±adir otra colecciÃ³n en la cual buscar de forma paralela, haga click en ella (o haga click en ella nuevamente para quitarla de la selecciÃ³n). Si sÃ³lo se seleccionÃ³ una colecciÃ³n, entonces no habrÃ¡ bÃºsqueda cruzada.</Text>
+<Text id="395">Si las colecciones no tienen los mismos Ã­ndices (incluyendo particiones en subcolecciones e idiomas) la bÃºsqueda cruzada no funcionarÃ¡ correctamente. El usuario Ãºnicamente serÃ¡ capaz de buscar usando Ã­ndices comunes a todas las colecciones.</Text>
+<Text id="396">Para mayor informaciÃ³n vea el CapÃ­tulo 1 de la GuÃ­a del Programador de Greenstone.</Text>
+</Content>
+</Part>
+<Part id="browsing_classifiers">
+<Title>
+<Text id="397">Clasificadores de exploraciÃ³n</Text>
+</Title>
+<Content>
+<Text id="398">Esta secciÃ³n explica la forma de asignar "clasificadores" a una colecciÃ³n, los cuales se usan para navegar y buscar en ella. En la parte de "Secciones de diseÃ±o" haga click en "Clasificadores de exploraciÃ³n".</Text>
+<Text id="399">Para aÃ±adir un clasificador, escÃ³jalo por medio de la lista descendente "Seleccione el clasificador que se va a aÃ±adir" en la parte inferior de la pantalla y haga click en "AÃ±adir clasificador". Con esto aparecerÃ¡ una ventana titulada "Argumentos de configuraciÃ³n". Las instrucciones para este cuadro de diÃ¡logo son exactamente las mismas que para los plugins (vea la secciÃ³n Plugins). Una vez que haya configurado el nuevo clasificador, Ã©ste se aÃ±adirÃ¡ al final de la lista de "Clasificadores asignados actualmente".</Text>
+<Text id="400">Para quitar un clasificador de la lista, selecciÃ³nelo y haga click en "Eliminar clasificador".</Text>
+<Text id="401">Para cambiar los argumentos de un clasificador, selecciÃ³nelo de la lista y haga click en "Configurar clasificador" o doble click en el nombre del clasificador.</Text>
+<Text id="402">El orden de los clasificadores en la barra de navegaciÃ³n de la colecciÃ³n se refleja aquÃ­. Para cambiarlo, seleccione el clasificador que desea mover y haga click en "Mover arriba" o "Mover abajo".</Text>
+<Text id="403">Para mayor informaciÃ³n sobre los clasificadores, lea el CapÃ­tulo 2 de la GuÃ­a del Programador de Greenstone: Obteniendo el mÃ¡ximo beneficio de sus documentos.</Text>
+</Content>
+</Part>
+<Part id="format_features">
+<Title>
+<Text id="404">Formatos</Text>
+</Title>
+<Content>
+<Text id="405">Las pÃ¡ginas Web que usted ve cuando utiliza Greenstone no han sido guardadas previamente sino que se generan âal vueloâ conforme se van necesitando. Los comandos de formato se utilizan para cambiar la apariencia de las pÃ¡ginas generadas. Afectan aspectos como el lugar donde aparecerÃ¡n los botones cuando se muestra un documento y quÃ© vÃ­nculos despliega el clasificador DateList en pantalla. Los comandos de formato no son fÃ¡ciles de desarrollar, por lo que le recomendamos que lea el CapÃ­tulo 2 de la GuÃ­a del Programador de Greenstone. La presente secciÃ³n describe los controles de los distintos formatos y la forma en que la Interfaz de Bibliotecario le da acceso a ellos. En la parte de "Secciones de diseÃ±o" haga click en "Formatos".</Text>
+<Text id="406">Se puede aplicar un comando de formato a cualquier cosa que se encuentre en la lista llamada "Elegir funciÃ³n", la cual incluye cada clasificador y una lista de funciones determinadas previamente. Cuando se selecciona una funciÃ³n existen dos tipos de controles. Algunas funciones simplemente se activan o se desactivan por medio de un recuadro. Otras requieren que se especifique una cadena de formato, para las cuales hay una lista descendente (llamada "Componente afectado") que permite seleccionar la parte de la funciÃ³n a la que se aplica la cadena (en caso necesario), un Ã¡rea de texto (llamada "cadena de formato HTML") para ingresar la cadena y una selecciÃ³n de "variables" definidas previamente. Para insertar una variable en su posiciÃ³n actual dentro de la cadena de formato, selecciÃ³nela de la lista descendente y haga click en "Insertar".</Text>
+<Text id="407">TambiÃ©n se puede especificar un formato predeterminado para un componente en particular seleccionando la funciÃ³n que estÃ¡ en blanco. Este formato se aplicarÃ¡ a todas las funciones aplicables a menos que se especifique lo contrario.</Text>
+<Text id="408">Para aÃ±adir un nuevo formato de comando llene la informaciÃ³n tal como se describe arriba y haga click en "AÃ±adir formato". El nuevo comando de formato aparecerÃ¡ en la lista de "Comandos de formato asignados actualmente". Solamente se podrÃ¡ asignar un comando de formato a cada combinaciÃ³n de funciÃ³n/componente.</Text>
+<Text id="409">Para quitar un comando de formato de la lista, selecciÃ³nelo y haga click en "Eliminar formato".</Text>
+<Text id="410">Para cambiar un comando de formato, selecciÃ³nelo de la lista, modifique sus parÃ¡metros y haga click en "Reemplazar formato".</Text>
+<Text id="411">Para mayor informaciÃ³n acerca de las variables y los componentes de las funciones lea el CapÃ­tulo 2 de la GuÃ­a del Programador de Greenstone.</Text>
+<Text id="412">Si se marca el recuadro "Permitir opciones avanzadas" se activarÃ¡n algunas opciones de formateo avanzado. La lista de funciones que se pueden formatear cambia ligeramente y mÃ¡s variables estÃ¡n disponibles para usarlas en los comandos de formato, proporcionando asÃ­ un mayor control sobre el diseÃ±o de la pÃ¡gina.</Text>
+</Content>
+</Part>
+<Part id="translate_text">
+<Title>
+<Text id="413">TraducciÃ³n de textos</Text>
+</Title>
+<Content>
+<Text id="414">Esta secciÃ³n describe la pantalla de traducciÃ³n, donde se pueden definir fragmentos de texto en un idioma especÃ­fico para partes de la interfaz de la colecciÃ³n. En la parte de "Secciones de diseÃ±o" haga click en "Traducir texto".</Text>
+<Text id="415">Primero elija una entrada de la lista de "funciones". Las cadenas de texto asociadas a esta funciÃ³n aparecerÃ¡n abajo. Utilice la lista "Idioma de la traducciÃ³n" para seleccionar el idioma al que se va a traducir y escriba el texto traducido en el Ã¡rea de texto, haciendo referencia al "fragmento de texto inicial" en caso necesario. Una vez que haya terminado haga click en "AÃ±adir traducciÃ³n".</Text>
+<Text id="416">Para quitar una traducciÃ³n existente, selecciÃ³nela de la tabla "Traducciones asignadas" y haga click en "Eliminar traducciÃ³n".</Text>
+<Text id="417">Para actualizar una traducciÃ³n, selecciÃ³nela, edÃ­tela en el Ã¡rea de texto titulada "Texto traducido" y haga click en "Reemplazar traducciÃ³n".</Text>
+</Content>
+</Part>
+<Part id="metadata_sets">
+<Title>
+<Text id="418">Conjuntos de metadatos</Text>
+</Title>
+<Content>
+<Text id="419">Esta secciÃ³n describe la pantalla de revisiÃ³n del conjunto de metadatos. En la parte de "Secciones de diseÃ±o" haga click en "Conjuntos de metadatos".</Text>
+<Text id="420">Esta pantalla se usa para revisar los conjuntos de metadatos que utiliza la colecciÃ³n, asÃ­ como los elementos que estÃ¡n disponibles dentro de cada conjunto. Elija uno de la lista de "Conjuntos de Metadatos Disponibles" para ver los detalles de sus elementos.</Text>
+<Text id="421">Para usar otro conjunto de metadatos con la colecciÃ³n cargada, pulse "AÃ±adir Conjunto de Metadatos", y seleccione el archivo de conjunto de metadatos (.mds) para el nuevo conjunto de metadatos.</Text>
+<Text id="422">La edicion de conjuntos de metadatos se hace con el Editor Greenstone para Conjuntos de Metadatos (GEMS). Pulsando el botÃ³n "Editar Conjunto de metadatos" obtendrÃ¡ informaciÃ³n sobre cÃ³mo utilizar GEMS.</Text>
+<Text id="423">Si ya no necesita mÃ¡s un conjunto de metadatos, selecciÃ³nelo y pulse "Borrar Conjunto de Metadatos" para eliminarlo. Si habÃ­a asignado metadatos a cualquier elemento del conjunto borrado, se le preguntarÃ¡ cÃ³mo actuar con estos metadatos cuando vuelva a abrir la colecciÃ³n.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="producing_your_collection">
+<Title>
+<Text id="424">Produciendo una colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="425">Una vez que se han reunido los documentos para la colecciÃ³n, que se han enriquecido con metadatos y que se ha diseÃ±ado la forma en que la colecciÃ³n aparecerÃ¡, usted ya puede empezar a producir la colecciÃ³n. Esta secciÃ³n le explica cÃ³mo.</Text>
+<Part id="the_create_view">
+<Title>
+<Text id="426">La pantalla de creaciÃ³n de la colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="427">La pantalla "Crear" se utiliza para producir la colecciÃ³n ejecutando los guiones de los programas Greenstone con base en la informaciÃ³n que usted ha proporcionado. Al hacer click en el botÃ³n "Crear colecciÃ³n" se inicia el proceso de construcciÃ³n de la colecciÃ³n. El tiempo que se lleve dependerÃ¡ del tamaÃ±o de la colecciÃ³n y del nÃºmero de Ã­ndices que se estÃ©n creando (para colecciones de gran tamaÃ±o pueden ser horas). Una barra de progreso indica cuÃ¡nto se ha completado del proceso. Para cancelar el proceso en cualquier momento haga click en el botÃ³n "Cancelar la construcciÃ³n".</Text>
+<Text id="428">Una vez que la colecciÃ³n se ha construido exitosamente, al seleccionar "Vista previa de la colecciÃ³n" se iniciarÃ¡ un navegador de web que mostrarÃ¡ la pÃ¡gina inicial de la colecciÃ³n.</Text>
+<Text id="429">En modo Experto, puede usar las entradas del "Registro de mensajes" a la izquierda, para revisar intentos previos de construcciÃ³n de la colecciÃ³n, hayan tenido Ã©xito o no. Seleccione el registro que desee haciendo click en la fecha correspondiente en la lista "Historial de registro".</Text>
+</Content>
+</Part>
+<Part id="import_and_build_settings">
+<Title>
+<Text id="430">Controles de importaciÃ³n y construcciÃ³n </Text>
+</Title>
+<Content>
+<Text id="431">Esta secciÃ³n explica la forma de tener acceso a los diferentes controles de importaciÃ³n y construcciÃ³n. Para mayor informaciÃ³n lea el CapÃ­tulo 1 de la GuÃ­a del Programador de Greenstone: Comprendiendo el proceso de creaciÃ³n de una colecciÃ³n.</Text>
+<Text id="432">La forma de controlar los diferentes ajustes es similar a la de la ventana "Argumentos de configuraciÃ³n" que se describe en la secciÃ³n de Plugins. Algunos campos requerirÃ¡n argumentos numÃ©ricos y usted puede escribirlos directamente en el campo o usar las flechas que se encuentran a un lado para aumentar o disminuir el nÃºmero (en algunos casos la interfaz limita el rango). Otros se activan (y desactivan) haciendo click en los recuadros correspondientes.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="miscellaneous">
+<Title>
+<Text id="433">MiscelÃ¡nea</Text>
+</Title>
+<Content>
+<Text id="434">Esta secciÃ³n describe funciones y caracterÃ­sticas de la Interfaz de Bibliotecario que no estÃ¡n asociadas a ninguna pantalla en particular.</Text>
+<Part id="preferences">
+<Title>
+<Text id="435">Preferencias</Text>
+</Title>
+<Content>
+<Text id="436">Esta secciÃ³n explica el cuadro de preferencias, al cual se tiene acceso por medio de la opciÃ³n "Preferencias" en el menÃº "Archivo".</Text>
+<Text id="437">La primera opciÃ³n "General" es un campo de texto para introducir su direcciÃ³n de correo electrÃ³nico. SerÃ¡ usada para los elementos de metadatos "creador" y "administrador" de la colecciÃ³n. La siguiente opciÃ³n es un menÃº desplegable de los lenguajes en los cuales se puede presentar la Interfaz de Bibliotecario. Si usted cambia el diccionario eligiendo un idioma de la lista, entonces deberÃ¡ reinicar la Interfaz de Bibliotecario para poder cargar las cadenas de texto en el nuevo idioma.</Text>
+<Text id="438">Si se marcÃ³ el recuadro "Ver metadatos extraÃ­dos", los diferentes controles que trabajan con metadatos siempre mostrarÃ¡n todos los metadatos que se han extraÃ­do automÃ¡ticamente de los documentos. Al quitar la marca del recuadro se ocultarÃ¡n estos metadatos (aunque la opciÃ³n seguirÃ¡ disponible durante el diseÃ±o de la colecciÃ³n y en la colecciÃ³n final). Si se marcÃ³ el recuadro "Mostrar el tamaÃ±o de los archivos" el tamaÃ±o del archivo aparecerÃ¡ junto a cada uno en las estructuras de archivos del Ã¡rea de trabajo y de la colecciÃ³n que se encuentran en las pantallas "Reunir" y "Enriquecer".</Text>
+<Text id="439">La pantalla de "Modo" se utiliza para controlar el nivel de detalle dentro de la interfaz. En su nivel mÃ¡s bÃ¡sico, "Asistente de Biblioteca", la pantalla de diseÃ±o estÃ¡ inhabilitada, los argumentos que requieren expresiones regulares estÃ¡n ocultos y el proceso de construcciÃ³n de la colecciÃ³n registra un mÃ­nimo de eventos. En comparaciÃ³n, el nivel mÃ¡s alto, "Avanzado", le da acceso a todas las funciones de diseÃ±o, incluyendo la posiciÃ³n de los plugins y argumentos con expresiones regulares, ademÃ¡s de permitir un registro completo del proceso de construcciÃ³n de la colecciÃ³n. Para cambiar o revisar los modos, haga click en el botÃ³n que se encuentra junto al modo en el que usted estÃ© interesado. De esta manera usted puede revisar rÃ¡pidamente el modo en el que estÃ¡ viendo la barra de tÃ­tulo de la Interfaz de Bibliotecario.</Text>
+<Text id="440">La Interfaz de Bibliotecario puede soportar diferentes flujos de trabajo determinando cuÃ¡les de las pestaÃ±as de las diferentes pantallas estarÃ¡n visibles. Utilice la pestaÃ±a "Flujo de trabajo" para determinar quÃ© pantallas estarÃ¡n disponibles marcando los recuadros que estÃ¡n junto al nombre de cada una de ellas. De forma alternativa utilice la lista descendente que se encuentra en la parte inferior para seleccionar las configuraciones predeterminadas. Al cerrar el cuadro de preferencias se aplicarÃ¡n los ajustes. Estos se guardan junto con la colecciÃ³n, no en el archivo de configuraciÃ³n de la Interfaz de Bibliotecario.</Text>
+<Text id="441">La pestaÃ±a de "ConexiÃ³n" le permite cambiar la ruta que lo conecta al servidor local de la biblioteca digital Greenstone, el cual se utiliza durante la presentaciÃ³n preliminar de la colecciÃ³n. TambiÃ©n le permite establecer la informaciÃ³n de proxy para conectarse a Internet (ejemplo: al descargar archivos; ver la secciÃ³n Descargando Archivos del Internet para mÃ¡s detalles). Marque la casilla para permitir la conexiÃ³n por proxy y suministre los detalles de la direcciÃ³n y el nÃºmero de puerto del host que sirve de proxy. La conexiÃ³n con el proxy se establece cuando cierre el diÃ¡logo de Preferencias.</Text>
+<Text id="442">En el curso de una sesiÃ³n la Interfaz de Bibliotecario podrÃ¡ enviarle mensajes de advertencia que le avisarÃ¡n sobre las posibles consecuencias no previstas de una acciÃ³n. Usted puede desactivar los mensajes marcando el recuadro "No mostrar este mensaje otra vez". Para reactivarlos utilice la pestaÃ±a "Mensajes de advertencia" y marque los recuadros de los mensajes que desea volver a ver.</Text>
+</Content>
+</Part>
+<Part id="file_associations">
+<Title>
+<Text id="443">AsociaciÃ³n de archivos</Text>
+</Title>
+<Content>
+<Text id="444">La Interfaz de Bibliotecario utiliza diferentes programas de aplicaciÃ³n para abrir tipos particulares de archivos. Para modificar la asociaciÃ³n de archivos abra el menÃº "Archivo" y haga click en "AsociaciÃ³n de archivos".</Text>
+<Text id="445">Para establecer una asociaciÃ³n seleccione la extensiÃ³n del archivo de la lista descendente o escriba una nueva extensiÃ³n (no incluya "."). A continuaciÃ³n escriba en el campo correspondiente el comando que da inicio a la aplicaciÃ³n deseada o elija la aplicaciÃ³n en el cuadro "Explorar". "%1" se puede utilizar en el comando de inicio para insertar el nombre del archivo que se estÃ¡ abriendo. Una vez que se han llenado estos campos, el botÃ³n "AÃ±adir" se activarÃ¡, con lo que ya se puede hacer click en Ã©l para establecer la asociaciÃ³n.</Text>
+<Text id="446">Para editar una asociaciÃ³n, seleccione una extensiÃ³n de archivo existente. El comando asociado aparecerÃ¡ en el campo correspondiente a comando de inicio. EdÃ­telo y a continuaciÃ³n haga click en "Reemplazar".</Text>
+<Text id="447">Para eliminar una asociaciÃ³n, seleccione la extensiÃ³n del archivo y haga click en "Eliminar". La extensiÃ³n del archivo permanecerÃ¡ en una lista llamada "Para archivos que terminan en...".</Text>
+<Text id="448">Las asociaciones de archivos se guardan en la carpeta principal de la Interfaz de Bibliotecario en un archivo llamado "associations.xml".</Text>
+</Content>
+</Part>
+<Part id="exporting_collections_to_cddvd">
+<Title>
+<Text id="449">Exportando colecciones a un CD/DVD</Text>
+</Title>
+<Content>
+<Text id="450">Greenstone puede exportar una o mÃ¡s colecciones a un CD/DVD para Windows que se podrÃ¡ instalar automÃ¡ticamente. Para ello es indispensable que el paquete "Exportar a un CD-ROM" estÃ© instalado. Esto no se incluye por omisiÃ³n, por lo que serÃ¡ necesario modificar la instalaciÃ³n para incluirlo.</Text>
+<Text id="451">Para exportar una colecciÃ³n abra el menÃº "Archivo" y seleccione la opciÃ³n "Exportar a un CD-ROM/DVD...". Con esto aparecerÃ¡ una lista de colecciones Greenstone. Haga click en una para ver su descripciÃ³n. Marque los recuadros de las colecciones que desea exportar. Usted tambiÃ©n puede ingresar el nombre de CD/DVD en el cuadro correspondiente, el cual aparecerÃ¡ en el menÃº de Inicio una vez que el CD/DVD se haya instalado. A continuaciÃ³n haga click en "Exportar". El proceso incluye la copia de varios archivos y requerirÃ¡ de unos cuantos minutos.</Text>
+<Text id="452">Una vez que haya terminado Greenstone mostrarÃ¡ el nombre de una carpeta en la que se encontrarÃ¡n las colecciones que se han exportado. Utilice una quemadora de CD/DVDs para copiar sus contenidos en un CD/DVD en blanco.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="tagging_document_files">
+<Title>
+<Text id="453">Etiquetado de los Archivos de Documento</Text>
+</Title>
+<Content>
+<Text id="454">Muy a menudo es necesario estructurar los documentos de origen (<i>source documents</i>) en secciones y subsecciones y se necesita comunicar esta informaciÃ³n a Greenstone para que preserve la estructura jerÃ¡rquica. AdemÃ¡s, se pueden asociar metadatos, generalmente el tÃ­tulo, a cada secciÃ³n y subsecciÃ³n.</Text>
+<Text id="455">Los documentos de origen obtenidos mediante un proceso de OCR suelen ser una serie de archivos de tratamiento de texto con sus ilustraciones. Cuando se trate de archivos en formato Word de Microsoft, podrÃ¡ utilizarse elÂ <i>plugin</i>Â Word para introducirlos en Greenstone. De otra forma, cabe la posibilidad de convertirlos en archivos HTML e incorporarlos a Greenstone mediante el plugin HTML.</Text>
+<Text id="456">En cualquiera de los dos casos es preciso indicar la estructura jerÃ¡rquica de un documento insertando etiquetas en el texto, como sigue:</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<Text id="457">Â Â Â Â Â  &lt;Metadata name=âTitleâ&gt; Realizing human rights for poor people: Strategies for achieving the international development targets &lt;/Metadata&gt;</Text>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="458"><i>(el texto de la secciÃ³n va aquÃ­)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="459">Se utilizan los marcadores &lt;!-- y --&gt; porque indican que se trata de comentarios en HTML, y de esta forma las etiquetas de una secciÃ³n no influirÃ¡n en el formato del documento. Debe incluir estos marcadores alrededor de sus etiquetas de secciÃ³n, aÃºn cuando el documento que estÃ© trabajando no sea HTML (por ejemplo si es un archivo Word de Microsoft).</Text>
+<Text id="460">En la parte correspondiente a la descripciÃ³n (entre las etiquetas &lt;Description&gt; y &lt;/Description&gt;) pueden especificarse otros tipos de metadatos, aunque no se haga para colecciones como las aquÃ­ descritas.</Text>
+<Text id="461">Es importante recordar que cuando inserta etiquetas de secciÃ³n, estÃ¡ creando una tabla de contenidos jerÃ¡rquica. Esto significa que las secciones pueden estar anidadas dentro de otras secciones. De hecho, todas las secciones deben estar anidadas dentro de una Ãºnica secciÃ³n que abarca a todo el documento.</Text>
+<Text id="462">El siguiente ejemplo muestra un documento con dos capÃ­tulos, el segundo de los cuales contiene dos subsecciones. Para ver ejemplos reales de documentos de origen etiquetados de esta manera, vea los documentos de origen para las colecciones Demo y DLS.</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>Â  &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Metadata name="TÃ­tulo"&gt;Mi Documento&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>Â  &lt;Section&gt; </CodeLine>
+<CodeLine>Â Â Â  &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;Metadata name="TÃ­tulo"&gt;CapÃ­tulo 1&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="463"><i>(el texto del capÃ­tulo 1 va aquÃ­)</i></Text>
+<CodeLine>&lt;!â</CodeLine>
+<CodeLine>Â  &lt;/Section&gt;</CodeLine>
+<CodeLine>Â  &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;Metadata name="TÃ­tulo"&gt;CapÃ­tulo 2&lt;/Metadata&gt; </CodeLine>
+<CodeLine>Â Â Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â  &lt;Metadata name="TÃ­tulo"&gt;SubsecciÃ³n 1&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="464"><i>(el texto de la subsecciÃ³n 1Â  va aquÃ­)</i></Text>
+<CodeLine>&lt;!â</CodeLine>
+<CodeLine>Â Â Â  &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â  &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;Description&gt; </CodeLine>
+<CodeLine>Â Â Â Â Â Â Â  &lt;Metadata name="TÃ­tulo"&gt;SubsecciÃ³n 2&lt;/Metadata&gt; </CodeLine>
+<CodeLine>Â Â Â Â Â  &lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="465"><i>(el texto de la subsecciÃ³n 2Â  va aquÃ­)</i></Text>
+<CodeLine>&lt;!â</CodeLine>
+<CodeLine>Â Â Â  &lt;/Section&gt;</CodeLine>
+<CodeLine>Â  &lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="466">Recuerde que el metadato asignado desde adentro de una etiqueta de secciÃ³n en un documento de origen tiene prioridad sobre aquel que le fue asignado al documento como un todo. Esto significa que usted no deberÃ¡ especificar explÃ­citamente el metadato TÃ­tulo para la secciÃ³n de nivel superior dentro de un documento de origen a menos que quiera que sustituya el tÃ­tulo que le dio al momento de especificar el metadato. En el ejemplo de arriba, a menos que usted quiera sustituir el tÃ­tulo existente del documento deberÃ¡ omitir la lÃ­nea que dice:</Text>
+<CodeLine>&lt;Metadata name="TÃ­tulo"&gt;Mi Documento&lt;/Metadata&gt;</CodeLine>
+</Content>
+</Section>
+<Section id="the_collector">
+<Title>
+<Text id="467">El Colector</Text>
+</Title>
+<Content>
+<Text id="468">El Colector es una funciÃ³n que le ayuda a crear nuevas colecciones y modificar, aÃ±adir o suprimir colecciones. Para hacerlo, serÃ¡ guiado por una secuencia de pÃ¡ginas Web en que se le pedirÃ¡ la informaciÃ³n necesaria. La secuencia es muy fÃ¡cil de seguir y en esta secciÃ³n se le proporcionarÃ¡n las explicaciones necesarias. En lugar de utilizar el Colector, tambiÃ©n se pueden crear colecciones a partir de la lÃ­nea de comandos; en las primeras pÃ¡ginas de laÂ <i>GuÃ­a del Programador</i>Â se explica en detalle cÃ³mo hacerlo.</Text>
+<Text id="469">Antes de crear y distribuir colecciones de informaciÃ³n, hay que reflexionar sobre las consecuencias y las responsabilidades que ello entraÃ±a. Hay cuestiones jurÃ­dicas de derecho de autor: poder tener acceso a documentos no significa necesariamente poder comunicarlos a terceros. Hay tambiÃ©n cuestiones de tipo social: en el manejo de las colecciones se deben respetar los usos y costumbres de la comunidad de la que proceden los documentos. Y hay tambiÃ©n cuestiones Ã©ticas: algunos documentos no deben ponerse a disposiciÃ³n de nadie. Â¡La pluma es mÃ¡s poderosa que la espada! Sea consciente del poder de la informaciÃ³n y utilÃ­celo con prudencia.</Text>
+<Text id="470">Para acceder al Colector, haga clic en el enlace correspondiente en la pÃ¡gina principal de la biblioteca digital.</Text>
+<Text id="471">En Greenstone, la estructura de una colecciÃ³n en particular se determina en el momento de su creaciÃ³n. Ello incluye el formato de los documentos de origen, la manera de mostrarlos en la pantalla, la fuente de los metadatos, las funciones de consulta que deben suministrarse, los Ã­ndices de bÃºsqueda en texto completo que deben proporcionarse, y la manera en que deben mostrarse los resultados de las bÃºsquedas. Una vez creada la colecciÃ³n, es fÃ¡cil aÃ±adirle nuevos documentos, siempre que tengan el mismo formato que los documentos existentes y se suministre el mismo tipo de metadatos, exactamente de la misma manera.</Text>
+<Text id="472">El Colector tiene las funciones bÃ¡sicas siguientes:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="473">Crear una nueva colecciÃ³n con la misma estructura que una existente.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="474">Crear una nueva colecciÃ³n con una estructura diferente de las existentes.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="475">AÃ±adir nuevo material a una colecciÃ³n existente.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="476">Modificar la estructura de una colecciÃ³n existente.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="477">Suprimir una colecciÃ³n. </Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="478">Grabar una colecciÃ³n existente en un CD-ROM autÃ³nomo y de instalaciÃ³n automÃ¡tica.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="479">En la Figura 16 se muestra la utilizaciÃ³n del Colector para la creaciÃ³n de una nueva colecciÃ³n, en este caso a partir de un conjunto de archivos HTML almacenados localmente. Se debe decidir en primer lugar si se ha de trabajar con una colecciÃ³n existente o crear una nueva. En el primer caso se presentan las opciones 1 y 2 arriba mencionadas; en el segundo, las opciones 3 a 6. En la Figura 16a, el usuario opta por crear una nueva colecciÃ³n.</Text>
+<Figure id="using_the_collector_to_build_a_new_collection">
+<Title>
+<Text id="480">UtilizaciÃ³n del Colector para crear una nueva colecciÃ³nÂ (continuaciÃ³n en las pÃ¡ginas siguientes)</Text>
+<SubTitle>
+<Text id="481">(a)</Text>
+</SubTitle>
+</Title>
+<File width="484" height="628" url="images/User_Fig_16a.png"/>
+</Figure>
+<Subsection id="logging_in">
+<Title>
+<Text id="482">Inicio de sesiÃ³n</Text>
+</Title>
+<Content>
+<Text id="483">En cualquier caso, es necesario en primer lugar iniciar la sesiÃ³n. Por lo general los usuarios utilizan su navegador Web para acceder a la funciÃ³n de creaciÃ³n de colecciÃ³n en una computadora remota y crear la colecciÃ³n en ese servidor. Obviamente, no podemos permitir que cualquier persona cree colecciones (aunque sÃ³lo sea por motivos de derechos), por lo cual Greenstone contiene un sistema de seguridad que obliga a las personas que desean crear colecciones iniciar en primer lugar la sesiÃ³n. Esto permite a un sistema central ofrecer un servicio a quienes desean crear colecciones de informaciÃ³n y utilizar ese servidor para ponerlas a disposiciÃ³n de otros. Por otra parte, si utiliza Greenstone en su propia computadora, puede crear colecciones localmente, pero sigue siendo necesario iniciar la sesiÃ³n, ya que otras personas que utilicen el sistema Greenstone en la misma computadora no estarÃ¡n habilitadas a crear colecciones sin una autorizaciÃ³n previa.</Text>
+</Content>
+</Subsection>
+<Subsection id="dialog_structure">
+<Title>
+<Text id="484">Estructura de diÃ¡logo</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_1">
+<Title>
+<Text id="485">UtilizaciÃ³n del Colector para crear una nueva colecciÃ³nÂ (continuaciÃ³n)</Text>
+<SubTitle>
+<Text id="486">(b)</Text>
+</SubTitle>
+</Title>
+<File width="484" height="628" url="images/User_Fig_16b.png"/>
+</Figure>
+<Text id="487">Una vez iniciada la sesiÃ³n, aparece la pÃ¡gina presentada en la Figura 16b. En Ã©sta se muestra la secuencia de pasos que supone la creaciÃ³n de una colecciÃ³n. Estos pasos son:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="488">Informaciones sobre la colecciÃ³n</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="489">Datos fuente</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="490">Configurar la colecciÃ³n</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="491">Crear la colecciÃ³n</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="492">Visualizar la colecciÃ³n</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="493">El primer paso consiste en especificar el nombre de la colecciÃ³n y la informaciÃ³n conexa. El segundo, en indicar la procedencia de los datos de origen. El tercero consiste en ajustar las opciones de configuraciÃ³n, etapa que resulta mÃ¡s Ãºtil a medida que usted adquiere experiencia con Greenstone. En el cuarto paso es donde la computadora efectÃºa toda su labor. Durante el proceso de âcreaciÃ³nâ el sistema elabora todos los Ã­ndices y reÃºne todas las demÃ¡s informaciones necesarias para el buen funcionamiento de la colecciÃ³n. El quinto paso consiste en visualizar la colecciÃ³n que se ha creado.</Text>
+<Text id="494">Estos cinco pasos se muestran como una secuencia lineal de botones grises en la parte inferior de la pantalla de la Figura 16b, y en la parte inferior de todas las demÃ¡s pÃ¡ginas generadas por el Colector. Esta pantalla ayuda a los usuarios a ubicarse en el proceso. El botÃ³n que se debe pulsar para continuar la secuencia aparece en verde (<i>informaciones sobre la colecciÃ³n</i>Â en la Figura 16b). Los botones grises (todos los demÃ¡s de la Figura 16b) estÃ¡n desactivados. Los botones cambian a color amarillo a medida que se avanza en la secuencia, y el usuario puede volver a cualquier paso anterior haciendo clic en el botÃ³n amarillo correspondiente. Esta pantalla sigue el modelo de los âasistentesâ que se utilizan ampliamente en los programas comerciales para guiar a los usuarios a travÃ©s de las diferentes etapas necesarias para la instalaciÃ³n de un nuevo programa.</Text>
+</Content>
+</Subsection>
+<Subsection id="collection_information">
+<Title>
+<Text id="495">Informaciones sobre la colecciÃ³n</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_2">
+<Title>
+<Text id="496">UtilizaciÃ³n del Colector para crear una nueva colecciÃ³nÂ (continuaciÃ³n)</Text>
+<SubTitle>
+<Text id="497">(c)</Text>
+</SubTitle>
+</Title>
+<File width="484" height="557" url="images/User_Fig_16c.png"/>
+</Figure>
+<Text id="498">En la Figura 16c se muestra el prÃ³ximo paso en la secuencia: las informaciones sobre la colecciÃ³n. Cuando se crea una nueva colecciÃ³n es necesario proporcionar algunas informaciones al respecto:</Text>
+<BulletList>
+<Bullet>
+<Text id="499">el tÃ­tulo</Text>
+</Bullet>
+<Bullet>
+<Text id="500">la direcciÃ³n de correo electrÃ³nico de contacto, y</Text>
+</Bullet>
+<Bullet>
+<Text id="501">una descripciÃ³n breve.</Text>
+</Bullet>
+</BulletList>
+<Text id="502">El tÃ­tulo de la colecciÃ³n es una frase breve que se utiliza constantemente en la biblioteca digital para identificar el contenido de la colecciÃ³n. Como ejemplos de tÃ­tulos pueden mencionarseÂ <i>Biblioteca de la alimentaciÃ³n y la nutriciÃ³n, Biblioteca sobre el medio ambiente mundial, Biblioteca para el desarrollo</i>, etc. La direcciÃ³n de correo electrÃ³nico especifica el primer punto de contacto para cualquier problema que se plantee con la colecciÃ³n. Si el programa Greenstone detecta un problema, puede enviarse un informe de diagnÃ³stico a esta direcciÃ³n. Por Ãºltimo, la descripciÃ³n breve consiste en una oraciÃ³n en que se enuncian los principios por los que se rige el contenido de la colecciÃ³n. Aparece en la primera pÃ¡gina, debajo del encabezadoÂ <i>acerca de esta colecciÃ³n</i>, cuando se presenta la colecciÃ³n.</Text>
+<Text id="503">La etapa en que se encuentra el usuario en la secuencia de creaciÃ³n de una colecciÃ³n estÃ¡ indicada por una flecha que aparece en la parte inferior de la pantalla, en este caso concreto, como muestra la Figura 16c, nos encontramos en la etapa de lasÂ <i>informaciones sobre la colecciÃ³n</i>. El usuario sigue a la Figura 16d pulsando el botÃ³n verdeÂ <i>datos fuente</i>.</Text>
+</Content>
+</Subsection>
+<Subsection id="source_data">
+<Title>
+<Text id="504">Datos fuente</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_3">
+<Title>
+<Text id="505">UtilizaciÃ³n del Colector para crear una nueva colecciÃ³nÂ (continuaciÃ³n)</Text>
+<SubTitle>
+<Text id="506">(d)</Text>
+</SubTitle>
+</Title>
+<File width="484" height="613" url="images/User_Fig_16d.png"/>
+</Figure>
+<Text id="507">La Figura 16d ilustra el momento en que el usuario especifica el texto de origen que corresponde a la colecciÃ³n. Puede usted basar su colecciÃ³n en una de las estructuras por defecto suministradas, o en la estructura de una colecciÃ³n existente.</Text>
+<Text id="508">Si opta por la estructura por defecto, la nueva colecciÃ³n podrÃ¡ contener documentos HTML (archivos que terminan enÂ <i>.htm</i>Â oÂ <i>.html</i>), documentos de texto sin formato (archivos que terminan enÂ <i>.txt</i>Â oÂ <i>.text</i>), documentos en formato Microsoft Word (archivos que terminan enÂ <i>.doc</i>), documentos pdf (archivos que terminan enÂ <i>.pdf</i>) o documentos de correo electrÃ³nico (archivos que terminan enÂ <i>.email</i>). En la secciÃ³n 3.9 se da mÃ¡s informaciÃ³n sobre los diferentes formatos de documento que pueden incluirse.</Text>
+<Text id="509">Si basa su nueva colecciÃ³n en una existente, los archivos de la nueva colecciÃ³n deben ser exactamente del mismo tipo que los utilizados para la creaciÃ³n de la colecciÃ³n existente. Conviene observar que algunas colecciones utilizan formatos de archivos de entrada no normalizados, mientras que otras utilizan metadatos especificados en archivos auxiliares. Si sus nuevos datos carecen de esta informaciÃ³n, algunas funciones de consulta pueden no funcionar correctamente. Por ejemplo, si usted clona la colecciÃ³n de demostraciÃ³n, podrÃ¡ percatarse de que los botonesÂ <i>temas, organizaciones</i>Â eÂ <i>Ã­ndices</i>Â no pueden activarse.</Text>
+<Text id="510">En la pÃ¡gina Web aparecen casillas para indicar la localizaciÃ³n de los documentos de origen: como se indica en la Figura 16d, se pueden especificar hasta tres fuentes distintas. Si necesita mÃ¡s, basta con hacer clic en el botÃ³n marcadoÂ <i>more sources</i>Â (mÃ¡s fuentes).</Text>
+<Text id="511">Hay tres tipos de especificaciones:</Text>
+<BulletList>
+<Bullet>
+<Text id="512">un nombre de directorio en el sistema del servidor Greenstone (que comienza con âfile://â)</Text>
+</Bullet>
+<Bullet>
+<Text id="513">una direcciÃ³n que comienza por âhttp://â para los archivos que han de descargarse de la Web</Text>
+</Bullet>
+<Bullet>
+<Text id="514">una direcciÃ³n que comienza por âftp://â para los archivos que han de descargarse utilizando un FTP anÃ³nimo.</Text>
+</Bullet>
+</BulletList>
+<Text id="515">Si utilizaÂ <i>file://</i>Â oÂ <i>ftp://</i>Â para especificar un archivo, se descargarÃ¡ ese archivo.</Text>
+<Text id="516">Si utilizaÂ <i>http://</i>, todo depende si la URL correspondiente hace aparecer en su navegador una pÃ¡gina Web normal o una lista de archivos. Si se trata de una pÃ¡gina, Ã©sta se descargarÃ¡, asÃ­ como todas las pÃ¡ginas con las que tiene un enlace y las pÃ¡ginas con las que Ã©stas tienen enlace, etc., siempre que residan en el mismo sitio, bajo esa URL.</Text>
+<Text id="517">Si utilizaÂ <i>file://</i>Â oÂ <i>ftp://</i>Â para especificar una carpeta o un directorio, o emplea una URLhttp://que lleva a una lista de archivos, todo lo que se encuentre en la carpeta y todas sus subcarpetas se incluirÃ¡n en la colecciÃ³n.</Text>
+<Text id="518">Puede usted especificar fuentes de varios tipos.</Text>
+<Text id="519">En este caso (Figura 16d) la nueva colecciÃ³n contendrÃ¡ documentos tomados de un sistema de archivos local asÃ­ como de un sitio Web remoto, que se copiarÃ¡ durante el proceso de creaciÃ³n de la colecciÃ³n.</Text>
+<Text id="520">Si se pulsa el botÃ³nÂ <i>configurar la colecciÃ³n</i>Â para pasar a la siguiente etapa de la creaciÃ³n, el Colector verificarÃ¡ que se puede llegar a todas las fuentes de datos que usted ha especificado. Esto puede tomar algunos segundos, o incluso algunos minutos si ha especificado varias fuentes. Si una o varias de las fuentes de datos que usted ha especificado no estÃ¡n disponibles, aparecerÃ¡ una pÃ¡gina como la de la Figura 16e, en que se marcan las fuentes no disponibles (en este caso, las dos).</Text>
+<Figure id="using_the_collector_to_build_a_new_collection_4">
+<Title>
+<Text id="521">UtilizaciÃ³n del Colector para crear una nueva colecciÃ³nÂ (continuaciÃ³n)</Text>
+<SubTitle>
+<Text id="522">(e)</Text>
+</SubTitle>
+</Title>
+<File width="484" height="613" url="images/User_Fig_16e.png"/>
+</Figure>
+<Text id="523">Las fuentes pueden no estar disponibles porque: </Text>
+<BulletList>
+<Bullet>
+<Text id="524">el archivo, el sitio FTP o la URL no existen;</Text>
+</Bullet>
+<Bullet>
+<Text id="525">necesita conectarse primero con su proveedor de servicios Internet; </Text>
+</Bullet>
+<Bullet>
+<Text id="526">estÃ¡ tratando de tener acceso a una URL protegida por un cortafuegos (<i>firewall</i>).</Text>
+</Bullet>
+</BulletList>
+<Text id="527">El Ãºltimo caso es posiblemente el mÃ¡s misterioso. Normalmente se produce si tiene que suministrar un nombre de usuario y una contraseÃ±a para tener acceso a Internet. A veces, si se introduce la URL, es posible ver la pÃ¡gina desde su navegador Web, aunque el Colector anuncia que no estÃ¡ disponible. La explicaciÃ³n es que la pÃ¡gina en su navegador puede venir de una copia almacenada localmente (<i>cache</i>). Por desgracia, las copias almacenadas localmente en la memoriaÂ <i>cache</i>Â son invisibles para el Colector. En este caso, recomendamos que descargue las pÃ¡ginas utilizando primero su navegador.</Text>
+</Content>
+</Subsection>
+<Subsection id="configuring_the_collection">
+<Title>
+<Text id="528">ConfiguraciÃ³n de la colecciÃ³n</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_5">
+<Title>
+<Text id="529">UtilizaciÃ³n del Colector para crear una nueva colecciÃ³nÂ (continuaciÃ³n)</Text>
+<SubTitle>
+<Text id="530">(f)</Text>
+</SubTitle>
+</Title>
+<File width="484" height="446" url="images/User_Fig_16f.png"/>
+</Figure>
+<Text id="531">En la Figura 16f se muestra la siguiente etapa. La creaciÃ³n y presentaciÃ³n de todas las colecciones se controlan mediante especificaciones registradas en un archivo especial de configuraciÃ³n de colecciÃ³n (vÃ©ase mÃ¡s abajo). Los usuarios experimentados podrÃ¡n utilizar esta pÃ¡gina para modificar los parÃ¡metros de configuraciÃ³n, pero la mayorÃ­a pasarÃ¡ directamente a la etapa final. En efecto, en la Figura 16d los botonesÂ <i>configurar la colecciÃ³n</i>Â yÂ <i>crear la colecciÃ³n</i>Â aparecen en color verde, lo cual significa que se puede obviar por completo el paso 3.</Text>
+<Text id="532">En nuestro ejemplo, el usuario ha introducido una pequeÃ±a modificaciÃ³n en el archivo de configuraciÃ³n por defecto, incluyendo el indicadorÂ <i>file_is_url</i>Â mediante el plugin HTML. El efecto de este indicador es que se insertan el metadato de URL en cada documento, basÃ¡ndose en la convenciÃ³n de nombre de archivo adoptada por el programa que crea la copia. Estos metadatos se utilizan en la colecciÃ³n para que los lectores puedan remitirse a la versiÃ³n original del documento y no a una copia local.</Text>
+</Content>
+</Subsection>
+<Subsection id="building_the_collection_1">
+<Title>
+<Text id="533">CreaciÃ³n de la colecciÃ³n</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_6">
+<Title>
+<Text id="534">UtilizaciÃ³n del Colector para crear una nueva colecciÃ³nÂ (continuaciÃ³n)</Text>
+<SubTitle>
+<Text id="535">(g)</Text>
+</SubTitle>
+</Title>
+<File width="484" height="445" url="images/User_Fig_16g.png"/>
+</Figure>
+<Text id="536">En la Figura 16g se muestra la etapa de âcreaciÃ³nâ. Hasta ahora, las respuestas al diÃ¡logo de la interfaz se han registrado meramente en un archivo temporal. La etapa de creaciÃ³n es aquÃ©lla en que se efectÃºa todo el trabajo.</Text>
+<Text id="537">Durante la creaciÃ³n de la colecciÃ³n se elaboran los Ã­ndices de consulta y de bÃºsqueda, siguiendo las instrucciones del archivo de configuraciÃ³n de la colecciÃ³n. El proceso de creaciÃ³n lleva entre varios minutos y varias horas, segÃºn el tamaÃ±o de la colecciÃ³n y la potencia de su computadora. En algunas colecciones muy voluminosas, la creaciÃ³n puede llevar mÃ¡s de un dÃ­a.</Text>
+<Text id="538">Al llegar a esta etapa, en la parte inferior de la pÃ¡gina Web aparece una lÃ­nea de estado que le informa cÃ³mo estÃ¡ progresando la operaciÃ³n, con una actualizaciÃ³n cada cinco segundos. El mensaje visible en la Figura 16f indica que cuando se tomÃ³ la instantÃ¡nea de la pantalla, se estaba convirtiendo un archivo de entrada.</Text>
+<Text id="539">Aparecen mensajes de alerta si se piden archivos de entrada o URL que no existen, o que existen pero no se dispone de un plugin para procesarlos, o el plugin no puede encontrar un archivo asociado, como un archivo de imagen incorporada en un documento HTML. La intenciÃ³n es que usted siga de cerca los progresos manteniendo esta ventana abierta en su navegador. Si algunos errores provocan el final prematuro del proceso, Ã©stos quedan registrados en esta zona de estado.</Text>
+<Text id="540">Puede detener el proceso de creaciÃ³n en cualquier momento haciendo clic en el botÃ³nÂ <i>Interrumpir la creaciÃ³n</i>Â que se muestra en la Figura 16g. Si sale de la pÃ¡gina Web (y no ha cancelado el proceso de creaciÃ³n con el botÃ³nÂ <i>Interrumpir la creaciÃ³n</i>), la operaciÃ³n de creaciÃ³n continuarÃ¡ y la nueva colecciÃ³n se instalarÃ¡ al final de la operaciÃ³n.</Text>
+</Content>
+</Subsection>
+<Subsection id="viewing_the_collection">
+<Title>
+<Text id="541">VisualizaciÃ³n de la colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="542">Cuando la colecciÃ³n estÃ¡ creada e instalada, aparece en la parte inferior de la Figura 16g la secuencia de botones visibles en la parte inferior de las Figuras 4b a 4f, con el botÃ³nÂ <i>visualizar la colecciÃ³n</i>Â activado. Al pulsar este botÃ³n, el usuario llega directamente a la colecciÃ³n reciÃ©n creada.</Text>
+<Text id="543">Por Ãºltimo, existe una funciÃ³n de correo electrÃ³nico para enviar un mensaje a la direcciÃ³n digital de contacto de la colecciÃ³n, asÃ­ como al administrador del sistema, cada vez que se crea (o se modifica) una colecciÃ³n. Esto permite que esos responsables se enteren de todos los cambios que se producen y sigan de cerca lo que sucede en el sistema. Esta funciÃ³n estÃ¡ desactivada por defecto, pero puede reactivarse modificando el archivo de configuraciÃ³nÂ <i>main.cfg</i>Â (vÃ©ase a este respecto la SecciÃ³n <CrossRef target="Chapter" external="Develop" lang="es" ref="configuring_your_greenstone_site"/> de laÂ <i>GuÃ­a del Programador de la Biblioteca Digital Greenstone</i>).</Text>
+</Content>
+</Subsection>
+<Subsection id="working_with_existing_collections">
+<Title>
+<Text id="544">Trabajar con colecciones existentes</Text>
+</Title>
+<Content>
+<Text id="545">Cuando comience a utilizar el Colector debe especificar si desea crear una colecciÃ³n totalmente nueva o trabajar con una existente, aÃ±adiÃ©ndole datos o suprimiÃ©ndolos. Como Greenstone crea automÃ¡ticamente todas las estructuras de bÃºsqueda y consulta a partir de los propios documentos, eso facilita la adiciÃ³n de nuevas informaciones a las colecciones existentes. Puesto que no se insertan enlaces manualmente, se pueden incorporar automÃ¡ticamente a la colecciÃ³n los nuevos documentos disponibles en el mismo formato.</Text>
+<Text id="546">Para trabajar con una colecciÃ³n existente, hay que seleccionar primero la colecciÃ³n a partir de una lista propuesta por el programa. Algunas colecciones estÃ¡n âprotegidas contra escrituraâ y no pueden ser alteradas: Ã©stas no aparecen en la lista de selecciÃ³n. Una vez escogida la colecciÃ³n, usted puede:</Text>
+<BulletList>
+<Bullet>
+<Text id="547">AÃ±adir nuevos datos y reconstituir la colecciÃ³n</Text>
+</Bullet>
+<Bullet>
+<Text id="548">Modificar el archivo de configuraciÃ³n de la colecciÃ³n</Text>
+</Bullet>
+<Bullet>
+<Text id="549">Suprimir completamente la colecciÃ³n</Text>
+</Bullet>
+<Bullet>
+<Text id="550">Exportar la colecciÃ³n a un CD-ROM</Text>
+</Bullet>
+</BulletList>
+<Part id="add_new_data">
+<Title>
+<Text id="551">AÃ±adir nuevos datos</Text>
+</Title>
+<Content>
+<Text id="552">Se aÃ±adirÃ¡n a la colecciÃ³n los archivos que usted especifique. CerciÃ³rese de no volver a especificar archivos que ya existen en la colecciÃ³n, pues de otro modo habrÃ¡ dos ejemplares. Los archivos se identifican por su ruta de acceso completa y las pÃ¡ginas Web por su direcciÃ³n Web absoluta. Se deben especificar los directorios y archivos del mismo modo que cuando se crea una nueva colecciÃ³n.</Text>
+<Text id="553">Si desea usted aÃ±adir datos a una colecciÃ³n y por algÃºn motivo el proceso de creaciÃ³n se interrumpe, la antigua versiÃ³n de la colecciÃ³n permanecerÃ¡ inalterada.</Text>
+</Content>
+</Part>
+<Part id="edit_configuration_file">
+<Title>
+<Text id="554">Modificar el archivo de configuraciÃ³n</Text>
+</Title>
+<Content>
+<Text id="555">Los usuarios experimentados pueden modificar el archivo de configuraciÃ³n de la colecciÃ³n, del mismo modo que cuando se crea una nueva colecciÃ³n. En la SecciÃ³n <CrossRef target="Chapter" ref="administration"/>Â <i>infra</i>Â se explican los parÃ¡metros de configuraciÃ³n.</Text>
+</Content>
+</Part>
+<Part id="delete_the_collection">
+<Title>
+<Text id="556">Suprimir la colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="557">Se le pedirÃ¡ que confirme si realmente desea suprimir la colecciÃ³n. Â¡Una vez suprimida, Greenstone no podrÃ¡ recuperarla!</Text>
+</Content>
+</Part>
+<Part id="export_the_collection">
+<Title>
+<Text id="558">Exportar la colecciÃ³n</Text>
+</Title>
+<Content>
+<Text id="559">Puede usted exportar la colecciÃ³n en una forma que permita grabarla en un CD-ROM Greenstone para Windows autÃ³nomo y de instalaciÃ³n automÃ¡tica. Como los programas comerciales que crean discos CD-ROM de instalaciÃ³n automÃ¡tica son onerosos, esta funciÃ³n incluye un mÃ³dulo de instalaciÃ³n propio del sistema.</Text>
+<Text id="560">Al exportar la colecciÃ³n, el cuadro de diÃ¡logo le informa del nombre del directorio en que se ha colocado el resultado. El contenido Ã­ntegro del directorio se grabarÃ¡ en el CD-ROM utilizando un programa estÃ¡ndar de grabaciÃ³n de CD.</Text>
+<Text id="561">La inmensa variedad de las diferentes configuraciones Windows posibles nos ha impedido probar y depurar el instalador de Greenstone en todas las condiciones posibles. Aunque produce discos CD-ROM que funcionan en la mayorÃ­a de los sistemas Windows, el instalador estÃ¡ aÃºn en proceso de elaboraciÃ³n. Si surgen problemas y dispone usted de un paquete de instalaciÃ³n comercial (por ejemplo, InstallShield), lo puede utilizar para crear discos CD-ROM a partir de la informaciÃ³n suministrada por Greenstone. El directorio de exportaciÃ³n antes mencionado contiene cuatro archivos relativos al proceso de instalaciÃ³n, y tres subdirectorios que contienen la colecciÃ³n y el programa informÃ¡tico completos. Quite los cuatro archivos y use InstallShield para obtener una imagen de CD-ROM que instalarÃ¡ esos directorios y crearÃ¡ un acceso directo al programaÂ <i>gsdl\server.exe</i>.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="document_formats_1">
+<Title>
+<Text id="562">Formatos de documentos</Text>
+</Title>
+<Content>
+<Text id="563">Cuando se crea una colecciÃ³n, Greenstone procesa cada diferente formato o documento de origen buscando un plugin que admita ese formato en particular. Los plugins estÃ¡n especificados en el archivo de configuraciÃ³n de la colecciÃ³n. Greenstone suele utilizar el nombre de archivo para determinar los formatos de documentos, por ejemplo,Â <i>foo.txt</i>Â se procesa como un archivo de texto,Â <i>foo.html</i>, como un archivo HTML yÂ <i>foo.doc</i>Â como un archivo Word.</Text>
+<Text id="564">Se ofrece a continuaciÃ³n un resumen de los plugins que estÃ¡n disponibles para los formatos de documento mÃ¡s utilizados. En laÂ <i>GuÃ­a del Programador de la Biblioteca Digital Greenstone</i>Â pueden consultarse mÃ¡s detalles sobre estos plugins y los plugins adicionales para formatos utilizados con menos frecuencia.</Text>
+<Part id="textplug">
+<Title>
+<Text id="565">TEXTPlug (*.txt,*.text)</Text>
+</Title>
+<Content>
+<Text id="566">TEXPlug interpreta un archivo de texto sin formato como un documento sencillo. AÃ±ade los metadatosÂ <i>tÃ­tulo</i>Â basÃ¡ndose en la primera lÃ­nea del archivo.</Text>
+</Content>
+</Part>
+<Part id="htmlplug">
+<Title>
+<Text id="567">htmlPlug (*.htm,*.html; tambiÃ©n .shtml, .shm, .asp, .php, .cgi)</Text>
+</Title>
+<Content>
+<Text id="568">htmlPlug procesa los archivos HTML. Extrae los metadatos deÂ <i>tÃ­tulo</i>Â basÃ¡ndose en la etiqueta &lt;title&gt;; tambiÃ©n puede extraer otros datos expresados utilizando una sintaxis de la âmetaetiquetaâ HTML. Este plugin ofrece muchas opciones que se presentan en laÂ <i>GuÃ­a del Programador de la Biblioteca Digital Greenstone</i>.</Text>
+</Content>
+</Part>
+<Part id="wordplug">
+<Title>
+<Text id="569">WORDPlug (*.doc)</Text>
+</Title>
+<Content>
+<Text id="570">WORDPlug importa documentos de formato Microsoft Word. Hay muchas variantes diferentes en el formato Word, e incluso los programas Microsoft cometen con frecuencia errores de conversiÃ³n. Greenstone utiliza programas independientes para convertir los archivos Word en HTML. En el caso de algunos formatos Word mÃ¡s antiguos, el sistema recurre a un algoritmo sencillo de extracciÃ³n que encuentra todas las porciones de texto en el archivo de entrada.</Text>
+</Content>
+</Part>
+<Part id="pdfplug">
+<Title>
+<Text id="571">PDFPlug (*.pdf)</Text>
+</Title>
+<Content>
+<Text id="572">PDFPlug importa documentos de formato Pdf de Adobe (âformato de documento portableâ). Al igual que WORDPlug, utiliza un programa independiente, en este casoÂ <i>pdftohtml</i>, para convertir los archivos PDF en HTML.</Text>
+<Text id="573">A semejanza de WORDPlug, las colecciones por defecto mostrarÃ¡n el equivalente HTML del archivo cuando el usuario haga clic en el iconoÂ <i>documento</i>Â ; sin embargo, es posible ajustar las cadenas de formato en el archivo de configuraciÃ³n de la colecciÃ³n para dar al usuario acceso al archivo PDF original, y le recomendamos que proceda asÃ­. Una vez mÃ¡s, basta con sustituir las etiquetas &lt;link&gt;...&lt;/link&gt; por &lt;srclink&gt;...&lt;/srclink&gt;.</Text>
+<Text id="574">El programaÂ <i>pdftohtml</i>Â no funciona con algunos archivos PDF. Lo que sucede es que el proceso de conversiÃ³n lleva un tiempo excepcionalmente prolongado y con frecuencia aparece en la pantalla un mensaje de error relativo a dicho proceso. Si ello ocurre, la Ãºnica soluciÃ³n que podemos ofrecerle es retirar de la colecciÃ³n el documento causante del error. PDFPlug tampoco puede tratar archivos PDF codificados.</Text>
+</Content>
+</Part>
+<Part id="psplug">
+<Title>
+<Text id="575">PSPlug (*.ps)</Text>
+</Title>
+<Content>
+<Text id="576">PSPlug importa documentos de formato PostScript. Funciona mejor si ya estÃ¡ instalado en su computadora un programa Linux estÃ¡ndar llamadoÂ <i>ps2ascii</i>. Este estÃ¡ disponible en la mayorÃ­a de las instalaciones Linux, pero no en Windows. Si el programa no estÃ¡ disponible, PSPlug se limita a un simple algoritmo de extracciÃ³n de texto.</Text>
+</Content>
+</Part>
+<Part id="emailplug">
+<Title>
+<Text id="577">EMAILPlug (*.email)</Text>
+</Title>
+<Content>
+<Text id="578">EMAILPlug importa los archivos que contienen mensajes de correo electrÃ³nico y puede funcionar con los formatos de correo electrÃ³nico comunes, como los utilizados por los usuarios de correo electrÃ³nico de Netscape, Eudora y Unix. Cada documento de origen se examina para determinar si contiene uno o varios mensajes de correo electrÃ³nico unidos en un archivo Ãºnico, y en ese caso se procesa el contenido. El plugin extrae los metadatosÂ <i>Subject (âAsuntoâ), To (âDestinatarioâ, âAâ), From (âRemitenteâ, âDeâ)</i>Â yÂ <i>Date (âFechaâ)</i>. Sin embargo, este plugin no puede todavÃ­a procesar correctamente los mensajes codificados de formato MIME, que aunque son legibles, tienen con frecuencia un aspecto extraÃ±o.</Text>
+</Content>
+</Part>
+<Part id="zipplug">
+<Title>
+<Text id="579">ZIPPlug (.gz, .z, .tgz, .taz, .bz, .zip, .tar)</Text>
+</Title>
+<Content>
+<Text id="580">El plugin ZIPPlug trata los siguientes formatos de entrada comprimidos y/o archivados: gzip (<i>.gz, .z, .tgz, .taz),</i>Â bzipÂ <i>(.bz,)</i>, zip (Â <i>.zip .jar)</i>Â y tarÂ <i>(.tar)</i>. Se basa en los programasÂ <i>gunzip, bunzip, unzip</i>Â yÂ <i>tar</i>, que son programas utilitarios Linux estÃ¡ndar. ZIPPlug estÃ¡ desactivado en las computadoras equipadas con Windows.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="administration">
+<Title>
+<Text id="581">AdministraciÃ³n</Text>
+</Title>
+<Content>
+<Text id="582">En toda instalaciÃ³n Greenstone estÃ¡ incluida una funciÃ³n âadministrativaâ. Para acceder a esta funciÃ³n, haga clic en el enlace correspondiente en la pÃ¡gina principal.</Text>
+<Text id="583">La pÃ¡gina principal, que se muestra en la Figura 17, proporciona informaciÃ³n sobre cada una de las colecciones que ofrece el sistema. Conviene observar que estÃ¡n incluidasÂ <i>todas</i>Â las colecciones, pues puede haber algunas âprivadasâ que no aparecen en la pÃ¡gina principal Greenstone. Para cada una se suministra su nombre abreviado, su nombre completo, se indica si estÃ¡ a disposiciÃ³n del pÃºblico y si estÃ¡ o no en funcionamiento. Si se hace clic en la abreviatura de una colecciÃ³n en particular (la primera columna de los enlaces en la Figura 17), se obtiene informaciÃ³n sobre esa colecciÃ³n, recopilada a partir del archivo de configuraciÃ³n de la colecciÃ³n y de otras estructuras internas creadas para esa colecciÃ³n. Si la colecciÃ³n es pÃºblica y estÃ¡ en funcionamiento, al hacer clic en el nombre completo de la colecciÃ³n (el segundo enlace) se visualizarÃ¡ la colecciÃ³n propiamente dicha.</Text>
+<Text id="584">La colecciÃ³n que hemos creado en las secciones 3.2 a 3.6 se llamaÂ <i>wohiex</i>, abreviatura deÂ <i>Womenâs History Excerpt</i>Â (Extractos de la Historia de las Mujeres), y estÃ¡ visible cerca de la parte inferior de la Figura 17. En la Figura 18 se muestra la informaciÃ³n que aparece cuando se hace clic en este enlace. En la primera secciÃ³n se dan algunas informaciones sobre el archivo de configuraciÃ³n y el tamaÃ±o de la colecciÃ³n (unos 1.000 documentos, cerca de 1 millÃ³n de palabras, mÃ¡s de 6 Mb). Las secciones siguientes contienen informaciÃ³n interna relacionada con el protocolo de comunicaciÃ³n utilizado para acceder a las colecciones. Por ejemplo, las opciones de filtro para âQueryFilterâ muestran las opciones y los valores posibles que pueden utilizarse cuando se consultan las colecciones.</Text>
+<Text id="585">La funciÃ³n administrativa presenta tambiÃ©n informaciÃ³n de configuraciÃ³n acerca de la instalaciÃ³n y permite modificarla. Facilita el examen de los registros de errores que dejan constancia de los errores internos, y de los registros de usuarios que dejan constancia de la utilizaciÃ³n de la colecciÃ³n. Permite que un usuario (o varios usuarios) especÃ­fico(s) autorice(n) a otros a crear colecciones y aÃ±adir nuevo material al existente. Se puede acceder a todas estas funciones de forma interactiva, a partir de los elementos de menÃº que se muestran en la parte izquierda de la Figura 17.</Text>
+<Figure id="greenstone_administration_facility">
+<Text id="586">FunciÃ³n de AdministraciÃ³n en Greenstone</Text>
+<File width="529" height="408" url="images/User_Fig_17.png"/>
+</Figure>
+<Figure id="information_about_the_womens_history_excerpt_collection">
+<Text id="587">InformaciÃ³n sobre la colecciÃ³nÂ <b><i>Womenâs History Excerpt</i></b></Text>
+<File width="529" height="355" url="images/User_Fig_18a.png"/>
+<File width="529" height="355" url="images/User_Fig_18b.png"/>
+</Figure>
+<Section id="configuration_files">
+<Title>
+<Text id="588">Archivos de configuraciÃ³n</Text>
+</Title>
+<Content>
+<Text id="589">Hay dos archivos de configuraciÃ³n que controlan el funcionamiento de Greenstone: el archivo de configuraciÃ³n de sitioÂ <i>gsdlsite.cfg</i>Â y el archivo de configuraciÃ³n principalÂ <i>main.cfg.</i></Text>
+<Text id="590">El archivoÂ <i>gsdlsite.cfg</i>Â Â  se utiliza para configurar el programa Greenstone para el sitio en que estÃ¡ instalado. EstÃ¡ concebido para registrar las opciones de configuraciÃ³n propias de un sitio determinado como, por ejemplo, el nombre del directorio en que se guarda el programa Greenstone, la direcciÃ³n HTTP del sistema Greenstone, y si se estÃ¡ utilizando o no la funciÃ³nÂ <i>fastcgi</i>. En laÂ <i>GuÃ­a de InstalaciÃ³n de la Biblioteca Digital Greenstone</i>Â se describen los elementos que contiene este archivo.</Text>
+<Text id="591">El archivoÂ <i>main.cfg</i>Â contiene informaciÃ³n comÃºn a la interfaz de todas las colecciones presentadas en el sitio Greenstone. Incluye la direcciÃ³n de correo electrÃ³nico del encargado del mantenimiento del sistema, indica si las pÃ¡ginas de estado y del Colector estÃ¡n activadas o no, si se llevan o no los registros de las actividades de los usuarios y si se utilizan o no âÂ <i>cookies</i>Â â para identificar a los usuarios.</Text>
+</Content>
+</Section>
+<Section id="logs">
+<Title>
+<Text id="592">Registros</Text>
+</Title>
+<Content>
+<Text id="593">Se pueden examinar tres tipos de registros: registros de uso, registros de errores y registros de inicializaciÃ³n. Los dos Ãºltimos sÃ³lo interesan de hecho a las personas encargadas del mantenimiento del programa.</Text>
+<Text id="594">Todas las actividades del usuario, es decir, cada pÃ¡gina que el usuario visita, pueden quedar registradas en el programa Greenstone, aunque en los registros no se almacena informaciÃ³n nominativa. La tenedurÃ­a de registros (<i>logging</i>), desactivada por defecto, se activa incluyendo las lÃ­neas siguientes:</Text>
+<CodeLine>logcgiargsÂ Â Â Â  true</CodeLine>
+<CodeLine>usecookiesÂ Â Â Â  true</CodeLine>
+<Text id="595">en el archivo principal de configuraciÃ³n del sistema. Ambas opciones tienen por defecto el valorÂ <i>false</i>, por lo que es necesario asignarles el valorÂ <i>true</i>Â para activar la tenedurÃ­a de registros. La lÃ­neaÂ <i>logcgiargs</i>Â es la que activa o desactiva esta funciÃ³n. ActivandoÂ <i>usecookies</i>Â se asigna a cada usuario un cÃ³digo de identificaciÃ³n Ãºnico que permite seguir en el archivo de registro las interacciones de cada usuario.</Text>
+<Text id="596">Cada lÃ­nea del registro de usuarios corresponde a una pÃ¡gina visitada, Â¡aun las pÃ¡ginas generadas para la consulta de los archivos de registro! Comprende: a) la direcciÃ³n IP de la computadora del usuario, b) la marca de fecha y hora entre corchetes, c) los argumentos CGI entre parÃ©ntesis y d) el nombre del navegador del usuario (Netscape Navigator se denomina âMozillaâ). A continuaciÃ³n se presenta una lÃ­nea de muestra, dividida y anotada para facilitar su lectura:</Text>
+<CodeLine>Â Â Â  /fast-cgi-bin/niupepalibrary</CodeLine>
+<CodeLine>a)Â Â  its-wwwl.massey.ac.nz</CodeLine>
+<CodeLine>b)Â Â  [Thu Dec 07 23:47:00 NZDT 2000]</CodeLine>
+<CodeLine>c)Â Â  (a=p, b=0, bcp=, beu=, c=niupepa, cc=, ccp=0, ccs=0, cl=, cm=, cq2=, d=, e=, er=, f=0, fc=1, gc=0, gg=text, gt=0, h=, h2=, hl=1, hp=, il=1, j=, j2=, k=1, ky=, l=en, m=50, n=, n2=, o=20, p=home, pw=, q=, q2=, r=1, s=0, sp=frameset, t=1, ua=, uan=, ug=, uma=listusers, umc=, umnpwl=, umnpw2=, impw=, umug=, umun=, umus=, un=, us=invalid, v=0, w=w, x=0, z=130.123.128.4-950647871)</CodeLine>
+<CodeLine>d)Â Â  âMozilla/4.08 [en]Â  (Win95; I; Nav)â</CodeLine>
+<Text id="597">El Ãºltimo argumento CGI, âzâ, es un cÃ³digo de identificaciÃ³n o âÂ <i>cookie</i>Â â generado por el navegador del usuario; comprende el nÃºmero IP del usuario, seguido por la marca de fecha y hora de su primera visita a la biblioteca digital.</Text>
+<Text id="598">El archivo de registroÂ <i>usage.txt</i>Â se sitÃºa en el directorioÂ <i>etc.</i>, en la estructura de archivos de Greenstone (vÃ©ase laÂ <i>GuÃ­a del Programador de la Biblioteca Digital Greenstone</i>). Cuando se activa la funciÃ³n de tenedurÃ­a de registros, se consigna cada acciÃ³n de cada usuario. Sin embargo, el enlaceÂ <i>Registro de uso</i>Â que aparece en la Figura 17 sÃ³lo muestra las Ãºltimas 100 anotaciones en el archivo de registro.</Text>
+</Content>
+</Section>
+<Section id="user_management">
+<Title>
+<Text id="599">GestiÃ³n de los usuarios</Text>
+</Title>
+<Content>
+<Text id="600">Greenstone incorpora un sistema de autenticaciÃ³n que puede utilizarse para controlar el acceso a determinadas funciones. Por el momento el sistema se utiliza Ãºnicamente para restringir el nÃºmero de personas que estÃ¡n autorizadas a utilizar el Colector y algunas funciones de administraciÃ³n. Si, en el caso de una colecciÃ³n en particular, fuera necesario autentificar a los usuarios antes de hacerles llegar la informaciÃ³n, ello tambiÃ©n es posible. Se podrÃ­a, por ejemplo, proteger determinados documentos a fin de que sÃ³lo los usuarios registrados puedan tener acceso a ellos tecleando una contraseÃ±a. Ahora bien, ninguna de las colecciones utiliza actualmente esta funciÃ³n. La autenticaciÃ³n se efectÃºa pidiendo un nombre de usuario y una contraseÃ±a, tal como se ilustra en la Figura 16a.</Text>
+<Text id="601">A partir de la pÃ¡gina de administraciÃ³n, se puede hacer una lista de los usuarios, aÃ±adir nuevos usuarios y suprimir antiguos. Obviamente, la capacidad para hacerlo tambiÃ©n estÃ¡ protegida: sÃ³lo los usuarios que disponen de privilegios administrativos pueden aÃ±adir nuevos usuarios. Es tambiÃ©n posible que cada usuario pertenezca a âgruposâ diferentes. Por el momento, los Ãºnicos existentes son âÂ <i>administrator</i>Â â (administrador) y âÂ <i>colbuilder</i>Â â (creador de colecciÃ³n). Los miembros del primer grupo pueden aÃ±adir y suprimir usuarios y modificar sus grupos. Los miembros del segundo pueden acceder a las funciones antes descritas para crear nuevas colecciones y modificar (o suprimir) colecciones existentes.</Text>
+<Text id="602">Cuando se instala Greenstone, hay un solo usuario llamadoÂ <i>admin</i>Â que pertenece a ambos grupos. Su contraseÃ±a se establece durante el proceso de instalaciÃ³n. Este usuario puede crear nuevos nombres y contraseÃ±as Ãºnicamente para los usuarios pertenecientes al grupoÂ <i>colbuilder</i>, modo recomendado de brindar a otros usuarios la posibilidad de crear colecciones. La informaciÃ³n de usuario se registra en dos bases de datos situadas en la estructura de archivos de Greenstone (vÃ©ase laÂ <i>GuÃ­a del Programador de la Biblioteca Digital Greenstone</i>).</Text>
+</Content>
+</Section>
+<Section id="technical_information">
+<Title>
+<Text id="603">Informaciones tÃ©cnicas</Text>
+</Title>
+<Content>
+<Text id="604">Los enlaces situados debajo del encabezadoÂ <i>Informaciones tÃ©cnicas</i>Â proporcionan informaciÃ³n suplementaria sobre la instalaciÃ³n. El enlaceÂ <i>general</i>Â da acceso a la informaciÃ³n tÃ©cnica, incluidos los directorios de almacenamiento. El elemento de menÃºÂ <i>protocolos</i>Â proporciona, para cada tipo posible de protocolo, informaciones sobre cada una de las colecciones accesibles por ese protocolo.</Text>
+<Text id="605">Por Ãºltimo, el cÃ³digo de la interfaz de usuario (llamado el ârecepcionistaâ) utilizaÂ <i>acciones</i>Â para comunicar al sistema los deseos del usuario. Estas acciones corresponden al argumento CGI etiquetado âÂ <i>a</i>Â â. Por ejemplo, siÂ <i>a=status</i>, el recepcionista activa la acciÃ³nÂ <i>status</i>Â (que muestra la pÃ¡gina de estados). Un elemento de menÃº da acceso a la lista de todas las acciones propuestas por el sistema y otro lleva a los argumentos aceptados por esas acciones.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_a_software_features">
+<Title>
+<Text id="606">ApÃ©ndice A: CaracterÃ­sticas del programa</Text>
+</Title>
+<Content>
+<Table class="hidden" id="table_appendixa">
+<Title/>
+<TableContent>
+<tr>
+<th>
+<Text id="607"><i>Accesible mediante un navegador Web</i></Text>
+</th>
+<th>
+<Text id="608">Se accede a las colecciones mediante un navegador Web estÃ¡ndar (Netscape o Internet Explorer), con una combinaciÃ³n de funciones de consulta sencillas y una poderosa capacidad de bÃºsqueda.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="609"><i>BÃºsqueda en texto completo y por campos</i></Text>
+</th>
+<th>
+<Text id="610">El usuario puede efectuar bÃºsquedas en el texto completo de los documentos, o elegir entre los diversos Ã­ndices constituidos a partir de diferentes porciones de los documentos. Por ejemplo, algunas colecciones tienen un Ã­ndice de los documentos completos, un Ã­ndice de las secciones, un Ã­ndice de los tÃ­tulos y un Ã­ndice de los autores, y en cada uno de ellos se pueden efectuar bÃºsquedas de determinadas palabras o frases. Los resultados pueden ordenarse por pertinencia o clasificarse mediante un metadato.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="611"><i>Flexibilidad de la consulta</i></Text>
+</th>
+<th>
+<Text id="612">El usuario puede consultar listas de autores, listas de tÃ­tulos, listas de fechas, estructuras de clasificaciÃ³n, etc. Las diferentes colecciones pueden ofrecer distintas funciones de consulta, e incluso dentro de una colecciÃ³n se dispondrÃ¡ de una amplia variedad de interfaces de consulta. Las interfaces de consulta y de bÃºsqueda se elaboran durante el proceso de creaciÃ³n, con arreglo a la informaciÃ³n de configuraciÃ³n de la colecciÃ³n.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="613"><i>CreaciÃ³n automÃ¡tica de estructuras de acceso</i></Text>
+</th>
+<th>
+<Text id="614">El programa Greenstone crea colecciones de informaciÃ³n cuyo mantenimiento es muy fÃ¡cil. Todas las estructuras de bÃºsqueda y consulta se elaboran directamente a partir de los propios documentos. No se inserta manualmente ningÃºn enlace, sino que se mantienen los enlaces existentes en los originales. Gracias a esta caracterÃ­stica, los nuevos documentos en el mismo formato pueden incorporarse automÃ¡ticamente a la colecciÃ³n. En algunas colecciones, esto se hace mediante procesos que se ponen en marcha periÃ³dicamente, localizan el material nuevo y reconstituyen los Ã­ndices, todo ello sin intervenciÃ³n manual.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="615"><i>UtilizaciÃ³n de los metadatos disponibles</i></Text>
+</th>
+<th>
+<Text id="616">Los metadatos, es decir, las informaciones descriptivas tales como el autor, el tÃ­tulo, la fecha, las palabras clave, etc., pueden asociarse a cada documento o a cada secciÃ³n de documento. Los metadatos constituyen la materia prima de los Ã­ndices de consulta. Se los debe suministrar explÃ­citamente o deben poder extraerse automÃ¡ticamente de los documentos de origen. Para la mayorÃ­a de los documentos electrÃ³nicos se utiliza el sistema de metadatos Dublin Core, aunque se contempla la posibilidad de utilizar otros sistemas.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="617"><i>Los plugins amplÃ­an las capacidades del sistema</i></Text>
+</th>
+<th>
+<Text id="618">Para poder utilizar varios tipos de documentos de origen, el programa estÃ¡ organizado de manera que puedan escribirse plugins para nuevos tipos de documentos. En la actualidad existen plugins para textos sin formato, HTML, Word, PDF, PostScript, correo electrÃ³nico, algunos formatos patentados, asÃ­ como para la exploraciÃ³n recursivaÂ  de estructuras de directorio y archivos comprimidos que contienen tales documentos. Una colecciÃ³n puede tener documentos de origen de diferentes formas. Para elaborar los Ã­ndices de consulta a partir de los metadatos se utiliza un sistema anÃ¡logo de âclasificadoresâ que crean Ã­ndices de consulta de diversos tipos, basados en los metadatos.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="619"><i>Programa diseÃ±ado para colecciones de varios gigabytes</i></Text>
+</th>
+<th>
+<Text id="620">Las colecciones pueden contener millones de documentos, por lo cual el sistema Greenstone puede manejar colecciones de hasta varios gigabytes.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="621"><i>Los documentos pueden estar en cualquier idioma</i></Text>
+</th>
+<th>
+<Text id="622">En todo el programa se utiliza Unicode, sistema que permite procesar cualquier idioma de forma sistemÃ¡tica. Hasta la fecha, se han creado colecciones que contienen documentos en francÃ©s, espaÃ±ol, maorÃ­, chino, Ã¡rabe e inglÃ©s. Se utiliza una conversiÃ³n âal vueloâ (on-the-fly) para convertir el formato Unicode en un alfabeto reconocido por el navegador Web del usuario.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="623"><i>La interfaz de usuario estÃ¡ disponible en numerosos idiomas</i></Text>
+</th>
+<th>
+<Text id="624">La interfaz puede presentarse en numerosos idiomas. Actualmente esa interfaz estÃ¡ disponible en alemÃ¡n, Ã¡rabe, chino, espaÃ±ol, inglÃ©s, maorÃ­, neerlandÃ©s y portuguÃ©s. Pueden aÃ±adirse fÃ¡cilmente nuevos idiomas.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="625"><i>Las colecciones pueden contener texto, imagen, sonido y vÃ­deo</i></Text>
+</th>
+<th>
+<Text id="626">Las colecciones Greenstone pueden contener texto, imÃ¡genes, sonidos y videoclips. La mayor parte del material no textual estÃ¡ enlazado a los documentos textuales o va acompaÃ±ado de descripciones textuales (por ejemplo, las leyendas de las figuras) para permitir la bÃºsqueda y consulta en texto completo. Sin embargo, la arquitectura del programa permite la utilizaciÃ³n de plugins y clasificadores aun para datos no textuales.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="627"><i>UtilizaciÃ³n de tÃ©cnicas de compresiÃ³n avanzadas</i></Text>
+</th>
+<th>
+<Text id="628">Se utilizan tÃ©cnicas de compresiÃ³n para reducir el tamaÃ±o de los Ã­ndices y el texto. La reducciÃ³n del tamaÃ±o de los Ã­ndices mediante la compresiÃ³n tiene la ventaja adicional de aumentar la velocidad de recuperaciÃ³n de la informaciÃ³n textual.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="629"><i>Suministro de una funciÃ³n de administraciÃ³n</i></Text>
+</th>
+<th>
+<Text id="630">Una funciÃ³n âde administraciÃ³nâ permite que usuarios especificados autoricen a nuevos usuarios a crear colecciones, posibilita la protecciÃ³n de los documentos de talÂ  modo que sÃ³lo los usuarios registrados puedan tener acceso a ellos tecleando una contraseÃ±a, permite examinar la composiciÃ³n de todas las colecciones, etc. Gracias a los registros de actividades de los usuarios, se puede tener constancia de todas las consultas hechas a todas las colecciones de Greenstone.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="631"><i>PresentaciÃ³n dinÃ¡mica de las nuevas colecciones</i></Text>
+</th>
+<th>
+<Text id="632">Se pueden actualizar las colecciones y proponer nuevas colecciones en todo momento, sin apagar el sistema; el proceso encargado de la interfaz de usuario tomarÃ¡ nota (mediante sondeos periÃ³dicos) de las nuevas colecciones que aparezcan y las aÃ±adirÃ¡ a la lista presentada al usuario.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="633"><i>Las colecciones pueden publicarse en Internet o en CD-ROM</i></Text>
+</th>
+<th>
+<Text id="634">Se puede utilizar el programa para difundir colecciones por Internet. Las colecciones de Greenstone se pueden tambiÃ©n distribuir, en exactamente la misma forma, en CD-ROM. La interfaz de usuario funciona mediante un navegador Web estÃ¡ndar (Netscape viene en cada disco) y la interacciÃ³n es la misma que por la Web, con la salvedad de que los tiempos de respuesta son mÃ¡s previsibles. Los CD-ROM funcionan con todas las versiones del sistema operativo Windows.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="635"><i>Las colecciones pueden distribuirse entre diferentes computadoras</i></Text>
+</th>
+<th>
+<Text id="636">Una estructura de proceso flexible permite la distribuciÃ³n de diferentes colecciones por diferentes computadoras, aunque todas se presentan al usuario de la misma manera, en la misma pÃ¡gina Web y como parte de la misma biblioteca digital.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="637"><i>Funcionamiento con Windows y Unix</i></Text>
+</th>
+<th>
+<Text id="638">Greenstone funciona con los sistemas Windows (3.1/3.11, 95/98/Me, NT/2000) y Unix (Linux y SunOS). Cualquiera de estos sistemas puede utilizarse como servidor Web. Las colecciones no pueden crearse con versiones antiguas de Windows (3.1/3.11), pero pueden transferirse a esos sistemas colecciones previamente creadas.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="639"><i>Ventajas de Greenstone</i></Text>
+</th>
+<th>
+<Text id="640">La Biblioteca Digital Greenstone es un programa de cÃ³digo fuente abierto, disponible en el sitio Web de la Biblioteca Digital de Nueva Zelanda (nzdl.org), segÃºn las condiciones estipuladas en la Licencia PÃºblica General de GNU. El programa incluye todo lo que se ha mencionado mÃ¡s arriba: la funciÃ³n de servidor Web, la creaciÃ³n de discos CD-ROM, la creaciÃ³n de colecciones, posibilidades plurilingÃŒes, plugins y clasificadores para diversos tipos de documentos de origen. Comprende una funciÃ³n de autoinstalaciÃ³n que permite instalar fÃ¡cilmente el programa en Windows y Unix. Con arreglo al principio de los programas de cÃ³digo fuente abierto, se alienta a los usuarios a aportar modificaciones y mejoras.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<Chapter id="appendix_b_glossary_of_terms">
+<Title>
+<Text id="641">APÃNDICE B: GLOSARIO DE TÃRMINOS</Text>
+</Title>
+<Content>
+<Table id="appendixb" class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th>
+<Text id="642"><b>TÃ©rmino</b></Text>
+</th>
+<th>
+<Text id="643"><b>Significado</b></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="644"><i>autoconf</i></Text>
+</th>
+<th>
+<Text id="645">Programa Unix utilizado para configurar el paquete de instalaciÃ³n del programa Greenstone a fin que se adapte a su sistema</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="646"><i>Autorun</i></Text>
+</th>
+<th>
+<Text id="647">FunciÃ³n de Windows que arranca automÃ¡ticamente un programa cada vez que se inserta un CD-ROM</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="648">Consulta booleana</Text>
+</th>
+<th>
+<Text id="649">Consulta en un sistema de recuperaciÃ³n de informaciÃ³n que puede contener Y, O y NO booleanos</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="650">Consulta</Text>
+</th>
+<th>
+<Text id="651">Acceso a una colecciÃ³n recorriendo una lista organizada de valores de metadatos asociados a los documentos (tales como el autor, el tÃ­tulo, la fecha, palabras claves)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="652"><i>Buildcol.pl</i></Text>
+</th>
+<th>
+<Text id="653">Programa de Greenstone utilizado para crear colecciones</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="654">CreaciÃ³n</Text>
+</th>
+<th>
+<Text id="655">Proceso de constituciÃ³n de las estructuras de indexaciÃ³n y consulta que se utilizan para tener acceso a una colecciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="656">C++</Text>
+</th>
+<th>
+<Text id="657">Lenguaje de programaciÃ³n en que estÃ¡ escrita la mayor parte del programa Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="658">Ignorar las diferencias entre mayÃºsculas y minÃºsculas</Text>
+</th>
+<th>
+<Text id="659">FunciÃ³n cuyo objeto es que en las operaciones de bÃºsqueda no se distinga entre las palabras en mayÃºsculas y minÃºsculas</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="660">CGI</Text>
+</th>
+<th>
+<Text id="661"><i>Common Gateway Interface</i>Â (interfaz comÃºn de pasarela). Sistema que permite que los usuarios puedan activar programas en la computadora central (o servidor), haciendo clic en pÃ¡ginas Web</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="662">GuiÃ³n CGI</Text>
+</th>
+<th>
+<Text id="663">CÃ³digo asociado a un botÃ³n, un menÃº, o un enlace en una pÃ¡gina Web, que especifica lo que ha de hacer la computadora central cuando se hace clic en ese objeto</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="664"><i>cgi-bin</i></Text>
+</th>
+<th>
+<Text id="665">Directorio en que estÃ¡n almacenados los guiones cgi</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="666">Clasificador</Text>
+</th>
+<th>
+<Text id="667">MÃ³dulo de cÃ³digo de Greenstone que examina los metadatos del documento para elaborar un Ã­ndice de consulta</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="668">ColecciÃ³n</Text>
+</th>
+<th>
+<Text id="669">Conjunto de documentos agrupados en una interfaz de bÃºsqueda y consulta homogÃ©nea</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="670">Archivo de configuraciÃ³n de colecciÃ³n</Text>
+</th>
+<th>
+<Text id="671">Archivo que especifica de quÃ© manera ha de importarse y crearse la colecciÃ³n, quÃ© Ã­ndices e interfaces de idiomas han de suministrarse, etc.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="672">Servidor de colecciÃ³n</Text>
+</th>
+<th>
+<Text id="673">Programa que da acceso a una colecciÃ³n en curso de utilizaciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="674">Archivo de configuraciÃ³n</Text>
+</th>
+<th>
+<Text id="675">VÃ©ase âArchivo de configuraciÃ³n de colecciÃ³nâ, âArchivo de configuraciÃ³n principalâ, âArchivo de configuraciÃ³n de sitioâ</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="676">CVS</Text>
+</th>
+<th>
+<Text id="677">Concurrent Versioning System (sistema de versiones concurrentes). Sistema que permite mantener el cÃ³digo fuente utilizado en el programa Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="678"><i>db2txt</i></Text>
+</th>
+<th>
+<Text id="679">Herramienta Greenstone que permite visualizar en forma textual una base de datos GDBM (vÃ©ase âGDBMâ)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="680">ColecciÃ³n de demostraciÃ³n</Text>
+</th>
+<th>
+<Text id="681">Un subconjunto de la biblioteca para el desarrollo, distribuido con el programa Greenstone y utilizado para ilustrar esta guÃ­a didÃ¡ctica</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="682">Biblioteca digital</Text>
+</th>
+<th>
+<Text id="683">ColecciÃ³n de objetos digitales (texto, sonido, vÃ­deo), junto con mÃ©todos de acceso y recuperaciÃ³n de informaciÃ³n, asÃ­ como de selecciÃ³n, organizaciÃ³n y mantenimiento</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="684">DLS</Text>
+</th>
+<th>
+<Text id="685">Subconjunto de biblioteca para el desarrollo. Una colecciÃ³n Greenstone de informaciÃ³n humanitaria para los paÃ­ses en desarrollo</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="686">Documento</Text>
+</th>
+<th>
+<Text id="687">Unidad bÃ¡sica a partir de la cual se crean las colecciones de biblioteca digital; puede incluir texto, grÃ¡ficos, sonido, vÃ­deo, etc.</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="688">Dublin Core</Text>
+</th>
+<th>
+<Text id="689">Forma estÃ¡ndar de describir los metadatos</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="690">Fast-CGI</Text>
+</th>
+<th>
+<Text id="691">FunciÃ³n que permite que los guiones CGI permanezcan continuamente en funcionamiento, a fin de que no sea necesario reiniciarlos desde cero cada vez que se los activa</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="692">Programa de filtro</Text>
+</th>
+<th>
+<Text id="693">Parte del servidor de colecciones Greenstone que ejecuta las operaciones de bÃºsqueda y consulta</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="694">Cadena de formato</Text>
+</th>
+<th>
+<Text id="695">Cadena que especifica cÃ³mo visualizar en Greenstone los documentos y otras listas</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="696">CodificaciÃ³n GB</Text>
+</th>
+<th>
+<Text id="697">Forma estÃ¡ndar de codificar el idioma chino</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="698">GDBM</Text>
+</th>
+<th>
+<Text id="699"><i>GNU DataBase Manager</i>Â (administrador de base de datos de GNU). Programa utilizado por Greenstone para almacenar los metadatos de cada documento</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="700">GIMP</Text>
+</th>
+<th>
+<Text id="701"><i>GNU Image-Manipulation Program</i>Â (programa de manipulaciÃ³n de imÃ¡genes de GNU). Programa utilizado (en Unix) para crear iconos en Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="702">GML</Text>
+</th>
+<th>
+<Text id="703"><i>Greenstone Markup Language</i>Â (lenguaje de marcado Greenstone). Formato compatible con XML utilizado para almacenar documentos internamente</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="704">Licencia PÃºblica General GNU </Text>
+</th>
+<th>
+<Text id="705">Licencia de programas informÃ¡ticos que permite a los usuarios copiar y distribuir gratuitamente programas informÃ¡ticos y modificarlos, siempre que todas las modificaciones publicadas se pongan a disposiciÃ³n del pÃºblico en forma de cÃ³digo fuente</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="706">Greenstone</Text>
+</th>
+<th>
+<Text id="707">Nombre de este programa de biblioteca digital</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="708">GSDL </Text>
+</th>
+<th>
+<Text id="709">Abreviatura deÂ <i>Greenstone Digital Library</i>Â (Biblioteca Digital Greenstone)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="710"><i>%GSDLHOME%</i></Text>
+</th>
+<th>
+<Text id="711">Variable del sistema operativo Windows que representa el directorio principal en que se almacenan todos los programas y colecciones de Greenstone (<i>$GSDLHOME</i>Â en los sistema Unix)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="712"><i>%GSDLOS%</i></Text>
+</th>
+<th>
+<Text id="713">Variable del sistema operativo Windows que representa el sistema operativo en curso de utilizaciÃ³n (<i>$GSDLOS</i>Â en los sistemas Unix)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="714"><i>hashfile</i></Text>
+</th>
+<th>
+<Text id="715">Programa Greenstone utilizado en el momento de la importaciÃ³n o creaciÃ³n de colecciones para generar el identificador de objeto (OID) de cada documento</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="716">HTML</Text>
+</th>
+<th>
+<Text id="717"><i>HyperText Markup Language</i>Â (lenguaje de marcado de hipertexto). Lenguaje en que estÃ¡n escritos los documentos Web</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="718"><i>Â import.pl</i></Text>
+</th>
+<th>
+<Text id="719">Programa Greenstone utilizado para importar documentos</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="720">ImportaciÃ³n</Text>
+</th>
+<th>
+<Text id="721">Proceso de incorporaciÃ³n de colecciones de documentos al sistema Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="722">Ãndice</Text>
+</th>
+<th>
+<Text id="723">Estructura de informaciÃ³n utilizada para la bÃºsqueda o consulta en una colecciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="724">InstallShield</Text>
+</th>
+<th>
+<Text id="725">Programa Windows, utilizado para los CD-ROM Greenstone, que permite instalar un sistema a partir de un CD-ROM</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="726">Archivo de configuraciÃ³n principal</Text>
+</th>
+<th>
+<Text id="727">Archivo que contiene las especificaciones comunes a todas las colecciones que se ofrecen en este sitio</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="728">Metadatos</Text>
+</th>
+<th>
+<Text id="729">Datos descriptivos, tales como el autor, el tÃ­tulo, la fecha, palabras clave, etc., asociados a un documento (o colecciÃ³n de documentos)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="730">MG</Text>
+</th>
+<th>
+<Text id="731"><i>Managing Gigabytes</i>Â (gestiÃ³n de gigabytes). Programa utilizado en el sistema Greenstone para la indexaciÃ³n en texto completo, que incorpora tÃ©cnicas de compresiÃ³n (vÃ©ase al respecto Witten, I.H; Mofft, A. y Bell, TÂ <i>Managing Gigabytes: compressing and indexing documents and images</i>Â (GestiÃ³n de gigabytes: compresiÃ³n e indexaciÃ³n de documentos e imÃ¡genes), Morgan Kaufmann, segunda ediciÃ³n, 1999)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="732"><i>mgbuild</i></Text>
+</th>
+<th>
+<Text id="733">Programa MG para la constituciÃ³n de un Ã­ndice comprimido de texto completo</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="734"><i>mgquery</i></Text>
+</th>
+<th>
+<Text id="735">Programa MG para efectuar bÃºsquedas en un Ã­ndice comprimido de texto completo</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="736"><i>mkcol.pl</i></Text>
+</th>
+<th>
+<Text id="737">Programa Greenstone que crea e inicializa la estructura de directorio de una nueva colecciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="738">Proyecto de BibliotecaÂ  Digital de Nueva Zelanda</Text>
+</th>
+<th>
+<Text id="739">Proyecto de investigaciÃ³n del Departamento de InformÃ¡tica de la Universidad de Waikato, Nueva Zelanda, que creÃ³ el programa Greenstone (<i>nzdl.org)</i></Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="740">OID</Text>
+</th>
+<th>
+<Text id="741"><i>Object Identifier</i>Â (identificador de objeto). CÃ³digo de identificaciÃ³n Ãºnico asociado a un documento</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="742">Perl</Text>
+</th>
+<th>
+<Text id="743">Lenguaje de programaciÃ³n utilizado para una gran parte de las operaciones de tratamiento de texto durante el proceso de creaciÃ³n de una colecciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="744">Ping</Text>
+</th>
+<th>
+<Text id="745">Mensaje enviado a un sistema para determinar si estÃ¡ en funcionamiento o no</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="746">plugin</Text>
+</th>
+<th>
+<Text id="747">MÃ³dulo de cÃ³digo que administra los documentos de diferentes formatos, utilizado durante los procesos de importaciÃ³n y creaciÃ³n de colecciones</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="748">Protocolo</Text>
+</th>
+<th>
+<Text id="749">Conjunto de convenciones mediante las cuales el ârecepcionistaâ de Greenstone se comunica con un servidor de colecciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="750">Consulta ordenada</Text>
+</th>
+<th>
+<Text id="751">Consulta en lenguaje natural de un sistema de recuperaciÃ³n de informaciÃ³n, en virtud del cual los documentos que corresponden a la consulta solicitada se ordenan por orden de pertinencia</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="752">Recepcionista</Text>
+</th>
+<th>
+<Text id="753">Programa que organiza la interfaz de usuario de Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="754">RTF</Text>
+</th>
+<th>
+<Text id="755"><i>Rich Text Format</i>Â (formato de texto enriquecido). Formato estÃ¡ndar para el intercambio de documentos textuales</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="756">BÃºsqueda</Text>
+</th>
+<th>
+<Text id="757">Acceso a una colecciÃ³n a travÃ©s de una bÃºsqueda en texto completo de su contenido (o de una parte de su contenido, por ejemplo, los tÃ­tulos de secciones)</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="758">Servidor</Text>
+</th>
+<th>
+<Text id="759">VÃ©ase âServidor de colecciÃ³nâ y âServidor Webâ</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="760"><i>Â setup.bat, setup.sh, setup.csh</i></Text>
+</th>
+<th>
+<Text id="761">GuiÃ³n utilizado para instalar el entorno necesario para el reconocimiento del programa Greenstone</Text>
+</th>
+</tr> 
+<tr>
+<th>
+<Text id="762">Archivo de configuraciÃ³n de sitio</Text>
+</th>
+<th>
+<Text id="763">Archivo que contiene las especificaciones utilizadas para configurar el programa Greenstone para el sitio en que estÃ¡ instalado</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="764">Â Truncamiento</Text>
+</th>
+<th>
+<Text id="765">Corte del final de un tÃ©rmino de consulta para hacerlo mÃ¡s genÃ©rico</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="766">Â STL</Text>
+</th>
+<th>
+<Text id="767"><i>Standard Template Library</i>Â (biblioteca estÃ¡ndar de plantillas). Biblioteca de cÃ³digos C++ muy difundida, elaborada por Silicon Graphics</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="768"><i>Â txt2db</i></Text>
+</th>
+<th>
+<Text id="769">Programa Greenstone utilizado en el momento de la creaciÃ³n para constituir la base de datos GDBM</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="770">Â Unicode</Text>
+</th>
+<th>
+<Text id="771">Sistema estÃ¡ndar de representaciÃ³n de los conjuntos de caracteres utilizados en los idiomas del mundo</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="772">UNU</Text>
+</th>
+<th>
+<Text id="773">Universidad de las Naciones Unidas; esta sigla se utiliza tambiÃ©n para referirse a una colecciÃ³n Greenstone creada para esa organizaciÃ³n</Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="774">Servidor Web</Text>
+</th>
+<th>
+<Text id="775">Programa estÃ¡ndar que utilizan las computadoras para difundir informaciÃ³n por Internet </Text>
+</th>
+</tr>
+<tr>
+<th>
+<Text id="776">XML</Text>
+</th>
+<th>
+<Text id="777">Formato estÃ¡ndar para los documentos y datos estructurados en la Web (el lenguaje de marcado Greenstone es un formato compatible con XML)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="778">Esta opciÃ³n se inhabilita si ya existe un elemento con el mismo nombre.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/fr/Develop_fr.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/fr/Develop_fr.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/fr/Develop_fr.xml	(revision 13632)
@@ -0,0 +1,5218 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1"/>
+</Heading>
+<Title>
+<Text id="2">Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Title>
+<Author>
+<Text id="3">David Bainbridge, Dana McKay et Ian H. Witten</Text>
+</Author>
+<Affiliation>
+<Text id="4">DÃ©partement d'informatique,<br/>UniversitÃ© de Waikato, Nouvelle-ZÃ©lande</Text>
+</Affiliation>
+<Text id="5">Greenstone est une suite logicielle destinÃ©e Ã  la construction et Ã  la distribution de collections de bibliothÃšques numÃ©riques. Cette suite fournit une nouvelle maniÃšre d'organiser l'information et de la publier sur l'Internet ou sur un cÃ©dÃ©rom. Greenstone est produit par le projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande (dÃ©pendant de l'universitÃ© de Waikato), et distribuÃ© en coopÃ©ration avec l'UNESCO et le projet de bibliothÃšques pour l'humanitÃ©. C'est un logiciel Open Source, qu'on peut obtenir Ã  l'URLhttp://greenstone.org, et qui est diffusÃ© selon les termes de la licence publique gÃ©nÃ©rale de GNU.</Text>
+<Comment>
+<Text id="6">Nous souhaitons nous assurer que ce logiciel fonctionne bien pour vous.<br/>Faites-nous part, en anglais, de tout problÃšme Ã  l'adresse Ã©lectronique<br/>.</Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">Mars 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">Ã propos de ce manuel</Text>
+</Title>
+<Content>
+<Text id="10">Ce manuel explique le fonctionnement de Greenstone. Il vise ceux qui souhaitent personnaliser des collections et dÃ©velopper ou maintenir le logiciel.</Text>
+<Text id="11">La sectionÂ <CrossRef target="Chapter" ref="understanding_the_collection-building_process"/> expose le processus de construction de collection vu de l'intÃ©rieur, comprenant la structure de rÃ©pertoire, le format de document interne, et le fichier de configuration qui gouverne la structure de chaque collection. La section <CrossRef target="Chapter" ref="getting_the_most_out_of_your_documents"/> dÃ©crit les parties de Greenstone qui traitent les documents source (et leurs mÃ©ta-donnÃ©es) et dictent la maniÃšre dont on accÃšde Ã  l'information depuis l'interface utilisateur. Elle dÃ©crit Ã©galement des composants logiciels Â«externesÂ», distribuÃ©s avec Greenstone. La sectionÂ <CrossRef target="Chapter" ref="the_greenstone_runtime_system"/> explique la structure du systÃšme d'exÃ©cution de Greenstone, et donne aussi des dÃ©tails du logiciel pour aider Ã  comprendre son fonctionnement et comment le modifier pour correspondre Ã  des besoins particuliers. La sectionÂ <CrossRef target="Chapter" ref="configuring_your_greenstone_site"/> dÃ©crit les fichiers de configuration de Greenstone, et une annexe propose une introduction Ã  la bibliothÃšque standard de patrons (templates) pour C++.</Text>
+<Text id="12">Lors de votre travail avec le logiciel Greenstone, vous trouverez peut-Ãªtre des rÃ©fÃ©rences Ã  des fonctionnalitÃ©s qui ne sont pas dÃ©crites dans le prÃ©sent manuel, car Greenstone est en perpÃ©tuel dÃ©veloppement. Pour en savoir plus sur les travaux en cours, rejoignez la liste de diffusion de Greenstone (vous trouverez les instructions pour cela sur le site webgreenstone.org).</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="13">Documents d'accompagnement</Text>
+</Title>
+<Content>
+<Text id="14">L'ensemble des documents de Greenstone comprend cinq volumes:</Text>
+<BulletList>
+<Bullet>
+<Text id="15">Guide d'installation de la bibliothÃšque numÃ©rique Greenstone </Text>
+</Bullet>
+<Bullet>
+<Text id="16">Guide de l'utilisateur de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="17">Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone (<i>ce document-ci</i>)</Text>
+</Bullet>
+<Bullet>
+<Text id="18">BibliothÃšque numÃ©rique Greenstone: du papier Ã  la collection</Text>
+</Bullet>
+<Bullet>
+<Text id="19">BibliothÃšque numÃ©rique Greenstone: Utilisation de "L'organizer"</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="20">Remerciements</Text>
+</Title>
+<Content>
+<Text id="21">Le logiciel Greenstone a vu le jour grÃ¢ce Ã  un effort de collaboration entre de nombreuses personnes. Rodger McNab et Stefan Boddie en sont les principaux architectes et dÃ©veloppeurs. Des contributions ont Ã©tÃ© faites par David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, et Stuart Yeates. D'autres membres du Projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande ont Ã©galement donnÃ© des conseils et inspirÃ© les concepteurs du systÃšme: Mark Apperley, Sally Jo Cunningham, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, et Lloyd Smith. Nous remercions aussi tous ceux qui ont contribuÃ© au dÃ©veloppement des modules sous licence GNU GPL qui font partie de cette distribution: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE, XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="understanding_the_collection-building_process">
+<Title>
+<Text id="22">Comprendre le processus de construction d'une collection</Text>
+</Title>
+<Content>
+<Text id="23">Les utilisateurs finals de Greenstone peuvent construire des collections Ã  l'aide du Collector, dÃ©crit dans la section 3 du Guide de l'utilisateur de la bibliothÃšque numÃ©rique Greenstone. Il facilite beaucoup la construction de collections sur le modÃšle de collections existantes, mais avec des contenus nouveaux. Cependant, il n'est pas rÃ©ellement possible d'utiliser le Collector pour crÃ©er des collections avec des structures complÃštement nouvelles. Le Collector vous invite bien Ã  Ã©diter le fichier de configuration de la collection, qui gouverne cette structure de collection, mais il faut trÃšs bien connaÃ®tre Greenstone pour pouvoir y effectuer des modifications radicales et efficaces. La prÃ©sente section vous explique ce qu'il faut savoir pour opÃ©rer ainsi. Elle dÃ©crit Ã©galement la structure de rÃ©pertoire de Greenstone et le format interne de stockage des documents.</Text>
+<Text id="24">Tout au long de ce manuel nous supposerons que vous avez installÃ© Greenstone sur votre ordinateur, que ce dernier fonctionne sous Windows ou sous Unix. Si tel n'est pas encore le cas vous devriez consulter le Guide d'installation de la bibliothÃšque numÃ©rique Greenstone. Le nom GSDLHOME reprÃ©sentera le rÃ©pertoire racine de Greenstone, qui s'appelle %GSDLHOME% sur des systÃšmes Windows et $GSDLHOME sur des systÃšmes Unix. On dÃ©termine ce rÃ©pertoire pendant la procÃ©dure d'installation.</Text>
+<Section id="building_collections_from_the_command_line">
+<Title>
+<Text id="25">Construire des collections depuis la ligne de commande</Text>
+</Title>
+<Content>
+<Text id="26">CommenÃ§ons par dÃ©crire pas Ã  pas les opÃ©rations nÃ©cessaires pour construire une collection depuis la ligne de commande, ce qui facilitera la comprÃ©hension du processus. Bien sÃ»r, c'est le Collector qu'il faut plutÃŽt utiliser pour construire des collections de maniÃšre plus agrÃ©able. La collection que nous prenons en exemple est l'une des collections distribuÃ©es sur le cÃ©dÃ©rom du logiciel Greenstone, et elle contient les pages web personnelles de nombreux contributeurs au projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande et au logiciel Greenstone.</Text>
+<Text id="27">Les sections suivantes dÃ©taillent la construction sous Windows et sous Unix. En rÃ©alitÃ©, les deux se ressemblent presque complÃštementÂ --Â ne lisez que celle qui concerne votre systÃšme. Lorsque vous suivrez ces Ã©tapes, vous penserez peut-Ãªtre que certaines opÃ©rations sont mystÃ©rieuses ou des arcanes, mais ne les en suivez pas moins fidÃšlementÂ --Â elles prendront tout leur sens plus tard. Suivra un bref rÃ©sumÃ© des diffÃ©rences entre les processus de construction sous les deux systÃšmes.</Text>
+<Subsection id="collection_building_under_windows">
+<Title>
+<Text id="28">Construire des collections sous Windows</Text>
+</Title>
+<Content>
+<Text id="29">Le premier dÃ©fi lors de la construction d'une collection Ã  la ligne de commande sous Windows, c'est de parvenir Ã  l'Â«interprÃ©teur de commandesÂ», qui est l'endroit oÃ¹ l'on tape les commandes. Dans le menu DÃ©marrer ou le sous-menu Programmes, recherchez une ligne Invite MS-DOS, Invite DOS, ou InterprÃ©teur de commandes. Si vous ne trouvez rien de tel, invoquez l'entrÃ©e ExÃ©cuter et tentez de taper command (ou cmd) dans la boÃ®te de dialogue qui va apparaÃ®tre. Si rien de tout ceci ne fonctionne, faites-vous assister par une personne qui s'y connaÃ®t, telle que votre administrateur systÃšme.</Text>
+<Text id="30">Rendez-vous dans le rÃ©pertoire d'installation de Greenstone. En supposant que Greenstone a Ã©tÃ© installÃ© dans l'emplacement standard, vous vous y rendrez en tapant:</Text>
+<CodeLine>cd "C:\Program Files\gsdl "</CodeLine>
+<Text id="31">Les apostrophes doubles sont nÃ©cessaires Ã  cause de l'espace dans Program Files. Tapez ensuite Ã  l'invite:</Text>
+<CodeLine>setup.bat</CodeLine>
+<Text id="32">Ce fichier de commandes (que vous pouvez lire si vous en avez la curiositÃ©) explique au systÃšme oÃ¹ trouver les programmes de Greenstone<FootnoteRef id="1"/>. Si lors de votre session Ã  l'invite de commandes DOS, vous souhaitez revenir au rÃ©pertoire racine de Greenstone, vous pourrez toujours ce faire en tapant cd "%GSDLHOME%" (ici encore, les apostrophes doubles sont nÃ©cessaires: elles sont dues Ã  la prÃ©sence d'espaces dans le nom de fichier). Si vous fermez votre fenÃªtre DOS et en ouvrez une autre, il faudra de nouveau invoquer le fichier setup.bat.</Text>
+<Text id="33">Vous avez maintenant la possibilitÃ© de compiler, construire, et construire Ã  nouveau des collections. Le premier programme que vous allons examiner est le programme Perl mkcol.pl, dont le nom signifie Â«make a collectionÂ» (compiler une collection). Commencez par exÃ©cuter le programme en tapant perl -S mkcol.pl pour obtenir Ã  l'Ã©cran une description de la syntaxe et une liste des arguments possiblesÂ --Â si votre environnement Windows est configurÃ© de maniÃšre Ã  associer l'application Perl aux fichiers se terminant en .pl, il vous suffira de taper mkcol.pl pour obtenir ce rÃ©sultat. Comme vous pourrez le lire dans le message qui apparaÃ®t, l'unique argument obligatoire est creator, qui sert Ã  spÃ©cifier qui a construit la collection.</Text>
+<Text id="34">Utilisons cette commande pour crÃ©er les fichiers et sous-rÃ©pertoires initiaux nÃ©cessaires Ã  notre collection des pages personnelles des membres du projet de bibliothÃšque numÃ©rique Greenstone. Pour affecter Ã  la collection le nom dlpeople (Â«gens de la bibliothÃšque numÃ©riqueÂ» en anglais et en abrÃ©gÃ©), j'ai tapÃ©:</Text>
+<CodeLine>perl âS mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<Text id="35">(on peut se contenter de taper<i>mkcol.pl -creator me@cs.waikato.ac.nz dlpeople</i>si Perl est associÃ© aux extensions de fichiers en<i>.pl</i>). N'oubliez pas de remplacer mon adresse Ã©lectronique par la vÃŽtre!</Text>
+<Text id="36">Pour visualiser les fichiers nouvellement crÃ©Ã©s, on se dÃ©place dans le rÃ©pertoire de la collection en tapant:</Text>
+<CodeLine>cd "%GSDLHOME%\collect\dlpeople "</CodeLine>
+<Figure id="collection_configuration_file_created_by_mkcol">
+<Title>
+<Text id="37">Fichier de configuration de collection crÃ©Ã© par mkcol.pl</Text>
+</Title>
+<CodeLine>creatorÂ Â Â Â Â Â Â Â Â Â Â Â Â me@cs.waikato.ac.nz</CodeLine>
+<CodeLine>maintainerÂ Â Â Â Â Â Â Â Â Â me@cs.waikato.ac.nz</CodeLine>
+<CodeLine>publicÂ Â Â Â Â Â Â Â Â Â Â Â Â Â true</CodeLine>
+<CodeLine>betaÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â true</CodeLine>
+<CodeLine>indexesÂ Â Â Â Â Â Â Â Â Â Â Â Â document:text</CodeLine>
+<CodeLine>defaultindexÂ Â Â Â Â Â Â Â document:text</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â ZIPPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â GAPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â TEXTPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â HTMLPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â EMAILPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â ArcPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â RecPlug</CodeLine>
+<CodeLine>classifyÂ Â Â Â Â Â Â Â Â Â Â Â AZList -metadata "Title"</CodeLine>
+<CodeLine>collectionmetaÂ collectionnameÂ Â Â Â "dlpeople"</CodeLine>
+<CodeLine>collectionmetaÂ iconcollectionÂ Â Â Â ""</CodeLine>
+<CodeLine>collectionmetaÂ collectionextraÂ Â Â ""</CodeLine>
+<CodeLine>collectionmetaÂ .document:textÂ Â Â Â "documents "</CodeLine>
+</Figure>
+<Text id="38">On peut alors lister le contenu du rÃ©pertoire en tapant dir. Il devrait s'y trouver sept sous-rÃ©pertoires: archives, building, etc, images, import, index, et perllib.</Text>
+<Text id="39">Il faut maintenant peupler la collection d'Ã©chantillons de documents. Les documents source de la collection dlpeople se trouvent sur le cÃ©dÃ©rom de la distribution Greenstone dans le rÃ©pertoire collectdlpeople. InsÃ©rez d'abord le cÃ©dÃ©rom dans le lecteur (par exemple, sous D). Copiez ensuite le contenu du rÃ©pertoire Dcollectdlpeople dans le rÃ©pertoire import de la collection dlpeople. Vous pouvez procÃ©der comme suit:</Text>
+<Indented>
+<Text id="40">sÃ©lectionner le contenu du rÃ©pertoire dlpeople, et le faire glisser dans le rÃ©pertoire import de la collection dlpeople.</Text>
+</Indented>
+<Text id="41">Vous pouvez aussi taper la commande:</Text>
+<CodeLine>xcopy /s d:\collect\dlpeople\* import</CodeLine>
+<Text id="42">Dans le rÃ©pertoire etc de la collection, on trouve un fichier appelÃ© collect.cfg. Ouvrez-le dans votre Ã©diteur de texte prÃ©fÃ©rÃ©Â --Â edit est basique mais communÃ©ment disponible. Il devrait ressembler Ã  ce que prÃ©sente la figureÂ <CrossRef target="Figure" ref="collection_configuration_file_created_by_mkcol"/>, qui montre le fichier de configuration de collection crÃ©Ã© par la commande:</Text>
+<Text id="43">Nous sommes dÃ©sormais disposÃ©s Ã  Â«importerÂ» la collection. Il s'agit du processus qui apporte les documents dans le systÃšme Greenstone, en normalisant le format des documents, la maniÃšre dont les mÃ©ta-donnÃ©es sont spÃ©cifiÃ©es, et la structure de fichiers de stockage des documents. Tapez perl -S import.pl Ã  l'invite pour obtenir une liste de toutes les options du programme d'import. L'option -removeold s'assure que tout document prÃ©alablement importÃ© est effacÃ© dans un premier temps.</Text>
+<CodeLine>perl âS import.pl -removeold dlpeople</CodeLine>
+<Text id="44">Ne vous inquiÃ©tez pas du texte qui dÃ©file: il s'agit d'un compte-rendu de la progression de l'import. Sachez que l'import de cette collection prend environ cinq minutes sur une machine Ã  1Â GHz, et d'autant plus longtemps sur des machines plus lentes. Vous remarquerez qu'il n'est pas besoin de se trouver dans les rÃ©pertoires collect ou dlpeople lors de la saisie de cette commande: la variable GSDLHOME Ã©tant dÃ©jÃ  positionnÃ©e, le logiciel Greenstone peut trouver tous les fichiers nÃ©cessaires.</Text>
+<Text id="45">Modifions dÃ©sormais quelque peu le fichier de configuration de la collection pour en personnaliser la reprÃ©sentation. Donnons d'abord un nom Ã  la collection. Il sera utilisÃ© par les navigateurs web en tant que page de titre pour la premiÃšre page de la collection, et servira d'icone de collection si aucune image n'est fournie. Remplacez la ligne<i>collectionmeta collectionname "dlpeople"</i>par quelque chose comme<i>collectionmeta collectionname "Les membres du projet NZDL"</i>(NZDL est l'acronyme anglais du projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande: New Zealand Digital Library Project).</Text>
+<Text id="46">Ajoutez une description de votre collection entre les apostrophes doubles de la ligne collectionmeta collectionextra "". Elle servira de texte pour le paragraphe Ã  propos sur la page d'accueil de la collection. J'ai personnellement ajoutÃ©: "Cette collection comprend les pages personnelles de certains membres du projet NZDL.". Il est important de saisir cette description sous la forme d'une seule ligne dans l'Ã©diteurÂ --Â ne soyez pas tentÃ© de revenir Ã  la ligne si vous arrivez sur le bord droit de la fenÃªtre, mais continuez simplement Ã  taper!Â --Â sans quoi le fichier de configuration ne pourra pas Ãªtre correctement analysÃ©. Si vous souhaitez que votre collection puisse Ãªtre utilisÃ©e avec diffÃ©rentes interfaces de langues, il est possible de faire en sorte que cette description dÃ©pende de la langue choisie: ce procÃ©dÃ© est dÃ©crit dans la sectionÂ <CrossRef target="Section" ref="configuration_file"/>, plus bas.</Text>
+<Text id="47">On peut retenir toute image utilisable dans un navigateur web en tant qu'icone de collectionÂ --Â l'image que j'ai crÃ©Ã©e est prÃ©sentÃ©e figure <CrossRef target="Figure" ref="collection_icon"/>. Tapez l'emplacement de l'image entre les apostrophes doubles de la ligne<i>collectionmeta iconcollection ""</i>du fichier de configuration. On peut utiliser le raccourci _httpprefix_ pour remplacer le dÃ©but d'une URL qui pointe vers une image situÃ©e dans la zone de fichiers de Greenstone. Cela rend Ã©galement les configurations plus portables. Vous pouvez par exemple taper:<i>_httpprefix_/collect/dlpeople/images/icon.gif</i>si vous avez placÃ© une image convenable dans le rÃ©pertoire images de la collection (collectdlpeopleimages dans l'exemple qui nous intÃ©resse).</Text>
+<Text id="48">Sauvegardez le fichier de configuration de la collection et refermez-leÂ --Â vous n'en aurez plus besoin au cours de ce didacticiel.</Text>
+<Text id="49">La prochain Ã©tape consiste Ã  Â«construireÂ» la collection, ce qui crÃ©e tous les index et fichiers qui lui permettront de fonctionner. Tapez perl -S buildcol.pl Ã  l'invite pour obtenir la liste des options de construction de collection. Ces options sont prÃ©sentÃ©es plus en dÃ©tails dans la section section <CrossRef target="Section" ref="import_and_build_processes"/>. Pour l'instant, nous nous contenterons des valeurs par dÃ©faut en tapant:</Text>
+<CodeLine>perl âS buildcol.pl dlpeople</CodeLine>
+<Text id="50">Ã  l'invite. Ici non plus, ne vous inquiÃ©tez pas en voyant dÃ©filer le compte-rendu de progression.</Text>
+<Text id="51">Â«ActivezÂ» la collection comme suit:</Text>
+<Text id="52">sÃ©lectionnez le contenu du rÃ©pertoire building de la collection dlpeople, et faites-le glisser dans le rÃ©pertoire index.</Text>
+<Text id="53">Vous pouvez aussi effacer le rÃ©pertoire index (et tout ce qu'il contient) en tapant la commande:</Text>
+<CodeLine>rd /s index                 # on Windows NT/2000</CodeLine>
+<CodeLine>deltree /Y index       # on Windows 95/98</CodeLine>
+<Text id="54">et rebaptiser ensuite le rÃ©pertoire building en index avec:</Text>
+<CodeLine>ren building index</CodeLine>
+<Text id="55">Enfin, tapez:</Text>
+<CodeLine>mkdir building</CodeLine>
+<Text id="56">en vue de futures reconstructions. Il est important de taper ces commandes dans le bon rÃ©pertoire (Ã  la diffÃ©rence des commandes mkcol.pl, import.pl et buildcol.pl de Greenstone). Si le rÃ©pertoire actuel n'est pas dlpeople, tapez:<i>cd "%GSDLHOME%\collect\dlpeople"</i>avant de procÃ©der Ã  la sÃ©quence rd, ren, et mkdir donnÃ©e ci-dessus.</Text>
+<Text id="57">Vous devriez pouvoir accÃ©der Ã  la collection nouvellement construite depuis la page d'accueil de Greenstone. Il vous faudra rÃ©actualiser ou recharger cette page si elle Ã©tait dÃ©jÃ  ouverte dans votre navigateur, voire fermer le navigateur et le redÃ©marrer (pour Ã©viter les problÃšmes de tampon ou cache). Il se peut aussi, dans le cas oÃ¹ vous utilisez la version Â«BibliothÃšque localeÂ» de Greenstone, que vous deviez redÃ©marrer le programme library. Pour visualiser la nouvelle collection, cliquez sur l'image. Le resultat devrait alors ressembler Ã  la figureÂ <CrossRef target="Figure" ref="about_page_for_the_new_collection"/>.</Text>
+<Figure id="collection_icon">
+<Title>
+<Text id="58">Icone de collection </Text>
+</Title>
+<File width="156" height="120" url="images/Dev_Fig_2.png"/>
+</Figure>
+<Text id="59">Si nous nous rÃ©sumons, l'ensemble des commandes tapÃ©es pour produire la collection dlpeople sont:</Text>
+<CodeLine>cd "C:\Program Files\gsdl " # assuming default location</CodeLine>
+<CodeLine>setup.bat</CodeLine>
+<CodeLine>perl âS mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<CodeLine>cd "%GSDLHOME%\collect\dlpeople "</CodeLine>
+<CodeLine>xcopy   /s   d:\collect\dlpeople\*   import # assuming D drive</CodeLine>
+<CodeLine>perl âS import.pl dlpeople</CodeLine>
+<CodeLine>perl âS buildcol.pl dlpeople</CodeLine>
+<CodeLine>rd /s index           # on Windows NT/2000</CodeLine>
+<CodeLine>deltree /Y index # on Windows 95/98</CodeLine>
+<CodeLine>ren building index</CodeLine>
+<CodeLine>mkdir building</CodeLine>
+</Content>
+</Subsection>
+<Subsection id="collection_building_under_unix">
+<Title>
+<Text id="60">Construire des collections sous Unix</Text>
+</Title>
+<Content>
+<Text id="61">Commencez par vous rendre dans le rÃ©pertoire d'installation de Greenstone. Si par exemple Greenstone a Ã©tÃ© installÃ© dans l'emplacement standard, dans votre rÃ©pertoire personnel, vous vous y rendrez en tapant:</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<Text id="62">Tapez ensuite Ã  l'invite:</Text>
+<CodeLine>source setup.bash     # if you're running the BASH shell</CodeLine>
+<CodeLine>source setup.csh       # if you're running the C shell</CodeLine>
+<Text id="63">Ces fichiers de commandes (que vous pouvez lire si vous en avez la curiositÃ©) expliquent au systÃšme oÃ¹ trouver les programmes de Greenstone. Si lors de votre session Ã  l'interprÃ©teur de commandes, vous souhaitez revenir au rÃ©pertoire racine de Greenstone, vous pourrez toujours ce faire en tapant cd $GSDLHOME.</Text>
+<Text id="64">Si vous ignorez le type d'interprÃ©teur de commandes que vous utilisez, tapez echo $0 Ã  l'inviteÂ --Â cela affichera l'information recherchÃ©e. Si vous utilisez un autre interprÃ©teur de commandes, demandez conseil Ã  votre administrateur systÃšme.</Text>
+<Text id="65">AprÃšs avoir chargÃ© le bon fichier de rÃ©glages, vous avez maintenant la possibilitÃ© de compiler, construire, et construire Ã  nouveau des collections. Le premier programme que vous allons examiner est le programme Perl mkcol.pl, dont le nom signifie Â«make a collectionÂ» (compiler une collection). Commencez par exÃ©cuter le programme en tapant simplement mkcol.pl pour obtenir Ã  l'Ã©cran une description de la syntaxe et une liste des arguments possibles. Comme vous pourrez le lire dans le message qui apparaÃ®t, l'unique argument obligatoire est creator, qui sert Ã  spÃ©cifier qui a construit la collection.</Text>
+<Figure id="about_page_for_the_new_collection">
+<Title>
+<Text id="66">Page Â«Ã  proposÂ» de la nouvelle collection</Text>
+</Title>
+<File width="389" height="409" url="images/Dev_Fig_3.png"/>
+</Figure>
+<Text id="67">Utilisons cette commande pour crÃ©er les fichiers et sous-rÃ©pertoires initiaux nÃ©cessaires Ã  notre collection des pages personnelles des membres du projet de bibliothÃšque numÃ©rique Greenstone. Pour affecter Ã  la collection le nom dlpeople (Â«gens de la bibliothÃšque numÃ©riqueÂ» en anglais et en abrÃ©gÃ©), j'ai tapÃ©:</Text>
+<CodeLine>mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<Text id="68">N'oubliez pas de remplacer mon adresse Ã©lectronique par la vÃŽtre!</Text>
+<Text id="69">Pour visualiser les fichiers nouvellement crÃ©Ã©s, on se dÃ©place dans le rÃ©pertoire de la collection en tapant:</Text>
+<CodeLine>cd $GSDLHOME/collect/dlpeople</CodeLine>
+<Text id="70">On peut alors lister le contenu du rÃ©pertoire en tapant ls. Il devrait s'y trouver sept sous-rÃ©pertoires: archives, building, etc, images, import, index, et perllib.</Text>
+<Text id="71">Il faut maintenant peupler la collection d'Ã©chantillons de documents. Les documents source de la collection dlpeople se trouvent sur le cÃ©dÃ©rom de la distribution Greenstone dans le rÃ©pertoire collect/dlpeople. Pour lire des informations sur un cÃ©dÃ©rom depuis Linux, insÃ©rez le disque dans le lecteur et tapez</Text>
+<CodeLine>mount /cdrom</CodeLine>
+<Text id="72">Ã  l'invite (cette commande peut varier d'un systÃšme Ã  l'autre). Une fois montÃ©, le cÃ©dÃ©rom peut s'utiliser comme tout autre rÃ©pertoire; vous pouvez donc taper ls /cdrom/collect. VoilÃ  qui devrait rÃ©vÃ©ler un rÃ©pertoire dlpeople sur le cÃ©dÃ©rom.</Text>
+<Text id="73">Copiez ensuite le contenu du rÃ©pertoire /cdrom/collect/dlpeople dans le rÃ©pertoire GSDLHOME/collect/dlpeople/import. Pour ce faire, tapez la commande:</Text>
+<CodeLine>cp âr /cdrom/collect/dlpeople/*   import/</CodeLine>
+<Text id="74">puis tapez</Text>
+<CodeLine>umount /cdrom</CodeLine>
+<Text id="75">pour fermer le lecteur de cÃ©dÃ©rom. </Text>
+<Text id="76">Dans le rÃ©pertoire etc de la collection, on trouve un fichier appelÃ© collect.cfg. Ouvrez-le dans votre Ã©diteur de texte prÃ©fÃ©rÃ©Â --Â emacs est un Ã©diteur populaire sous Linux.Il devrait ressembler Ã  ce que prÃ©sente la figureÂ 1, qui montre le fichier de configuration de collection crÃ©Ã© par la commande:<i>mkcol.pl -creator me@cs.waikato.ac.nz dlpeople</i></Text>
+<Text id="77">Nous sommes dÃ©sormais disposÃ©s Ã  Â«importerÂ» la collection. Il s'agit du processus qui apporte les documents dans le systÃšme Greenstone, en normalisant le format des documents, la maniÃšre dont les mÃ©ta-donnÃ©es sont spÃ©cifiÃ©es, et la structure de fichiers de stockage des documents. Tapez import.pl Ã  l'invite pour obtenir une liste de toutes les options du programme d'import. L'option -removeold s'assure que tout document prÃ©alablement importÃ© est effacÃ© dans un premier temps.</Text>
+<CodeLine>import.pl âremoveold dlpeople</CodeLine>
+<Text id="78">Ne vous inquiÃ©tez pas du texte qui dÃ©file: il s'agit d'un compte-rendu de la progression de l'import. Sachez que l'import de cette collection prend environ cinq minutes sur une machine Ã  1Â GHz, et d'autant plus longtemps sur des machines plus lentes. Vous remarquerez qu'il n'est pas besoin de se trouver dans les rÃ©pertoires collect ou dlpeople lors de la saisie de cette commande: la variable GSDLHOME Ã©tant dÃ©jÃ  positionnÃ©e, le logiciel Greenstone peut trouver tous les fichiers nÃ©cessaires.</Text>
+<Text id="79">Modifions dÃ©sormais quelque peu le fichier de configuration de la collection pour en personnaliser la reprÃ©sentation. Donnons d'abord un nom Ã  la collection. Il sera utilisÃ© par les navigateurs web en tant que page de titre pour la premiÃšre page de la collection, et servira d'icone de collection si aucune image n'est fournie. Remplacez la ligne<i>collectionmeta collectionname "dlpeople"</i>par quelque chose comme<i>collectionmeta collectionname "Les membres du projet NZDL"</i>(NZDL est l'acronyme anglais du projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande: New Zealand Digital Library Project).</Text>
+<Text id="80">Ajoutez une description de votre collection entre les apostrophes doubles de la ligne collectionmeta collectionextra "". Elle servira de texte pour le paragraphe Â«Ã  proposÂ» sur la page d'accueil de la collection. J'ai personnellement ajoutÃ©: "Cette collection comprend les pages personnelles de certains contributeurs au projet NZDL.". Il est important de saisir cette description sous la forme d'une seule ligne dans l'Ã©diteurÂ --Â ne soyez pas tentÃ© de revenir Ã  la ligne si vous arrivez sur le bord droit de la fenÃªtre, mais continuez simplement Ã  taper!Â --Â sans quoi le fichier de configuration ne pourra pas Ãªtre correctement analysÃ©. Si vous souhaitez que votre collection puisse Ãªtre utilisÃ©e avec diffÃ©rentes interfaces de langues, il est possible de faire en sorte que cette description dÃ©pende de la langue choisie: ce procÃ©dÃ© est dÃ©crit dans la sectionÂ <CrossRef target="Section" ref="configuration_file"/>, ci-dessous.</Text>
+<Text id="81">On peut retenir toute image utilisable dans un navigateur web en tant qu'icone de collectionÂ --Â l'image que j'ai crÃ©Ã©e est prÃ©sentÃ©e figureÂ <CrossRef target="Figure" ref="collection_icon"/>. Tapez l'emplacement de l'image entre les apostrophes doubles de la ligne<i>collectionmeta iconcollection ""</i>du fichier de configuration. On peut utiliser le raccourci _httpprefix_ pour remplacer le dÃ©but d'une URL qui pointe vers une image situÃ©e dans la zone de fichiers de Greenstone. Cela rend Ã©galement les configurations plus portables. Vous pouvez par exemple taper:<i>_httpprefix_/collect/dlpeople/images/icon.gif</i>si vous avez placÃ© une image convenable dans le rÃ©pertoire images de la collection (collect/dlpeople/images dans l'exemple qui nous intÃ©resse).</Text>
+<Text id="82">Sauvegardez le fichier de configuration de la collection et refermez-leÂ --Â vous n'en aurez plus besoin au cours de ce didacticiel.</Text>
+<Text id="83">La prochain Ã©tape consiste Ã  Â«construireÂ» la collection, ce qui crÃ©e tous les index et fichiers qui lui permettront de fonctionner. Tapez buildcol.pl Ã  l'invite pour obtenir la liste des options de construction de collection. Ces options sont prÃ©sentÃ©es plus en dÃ©tails dans la section section <CrossRef target="Section" ref="import_and_build_processes"/>. Pour l'instant, nous nous contenterons des valeurs par dÃ©faut en tapant:</Text>
+<CodeLine>buildcol.pl dlpeople</CodeLine>
+<Text id="84">Ã  l'invite. Ici non plus, ne vous inquiÃ©tez pas en voyant dÃ©filer le compte-rendu de progression.</Text>
+<Text id="85">Â«ActivezÂ» la collection en dÃ©plaÃ§ant toutes les donnÃ©es qui viennent d'Ãªtre placÃ©es dans le rÃ©pertoire building vers le rÃ©pertoire index. Si vous avez dÃ©jÃ  construit cette collection de par le passÃ©, commencez d'abord par enlever l'ancien rÃ©pertoire index avec la commande:</Text>
+<CodeLine>rm âr index/*</CodeLine>
+<Text id="86">(en supposant que vous vous trouvez alors dans le rÃ©pertoire dlpeople). Puis tapez</Text>
+<CodeLine>mv building/* index/</CodeLine>
+<Table id="collection-building_differences_between_windows_and_linux">
+<Title>
+<Text id="87">DiffÃ©rences entre Windows et Linux pour la construction de collections</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="265">
+<Text id="88"><b>Windows</b></Text>
+</th>
+<th width="265">
+<Text id="89"><b>Linux</b></Text>
+</th>
+</tr>
+<tr>
+<th width="265">
+<Text id="90">ExÃ©cuter<i>setup.bat</i>pour rendre disponibles les programmes de Greenstone </Text>
+</th>
+<th width="265">
+<Text id="91">Charger<i>setup.bash</i>ou<i>setup.csh</i>pour rendre les programmes disponibles</Text>
+</th>
+</tr>
+<tr>
+<th width="265">
+<Text id="92">Copier les fichiers depuis le cÃ©dÃ©rom en utilisant le gestionnaire de fichiers graphique ou des commandes DOS</Text>
+</th>
+<th width="265">
+<Text id="93">Copier les fichiers depuis le cÃ©dÃ©rom en utilisant<i>mount</i>et d'autres commandes Unix</Text>
+</th>
+</tr>
+<tr>
+<th width="265">
+<Text id="94">L'ancien index de collection est remplacÃ© en tapant<i>rd /s index</i>puis<i>ren building index</i>suivis de<i>mkdir building</i>, ou en utilisant le gestionnaire de fichiers graphique</Text>
+</th>
+<th width="265">
+<Text id="95">L'ancien index de collection est remplacÃ© en tapant<i>rm âr index/*</i>puis<i>mv building/* index</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="96">Vous devriez pouvoir accÃ©der Ã  la collection nouvellement construite depuis la page d'accueil de Greenstone. Il vous faudra rÃ©actualiser ou recharger cette page si elle Ã©tait dÃ©jÃ  ouverte dans votre navigateur, voire fermer le navigateur et le redÃ©marrer (pour Ã©viter les problÃšmes de tampon ou cache). Pour visualiser la nouvelle collection, cliquez sur l'image. Le resultat devrait alors ressembler Ã  la figureÂ <CrossRef target="Figure" ref="about_page_for_the_new_collection"/>.</Text>
+<Text id="97">Si nous nous rÃ©sumons, l'ensemble des commandes tapÃ©es pour produire la collection dlpeople sont:</Text>
+<CodeLine>cd ~/gsdl # assuming default Greenstone in home directory</CodeLine>
+<CodeLine>source setup.bash     # if you're running the BASH shell</CodeLine>
+<CodeLine>source setup.csh       # if you're running the C shell</CodeLine>
+<CodeLine>mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<CodeLine>cd $GSDLHOME/collect/dlpeople</CodeLine>
+<CodeLine>mount /cdrom # assuming this is where CD-ROM is mapped to</CodeLine>
+<CodeLine>cp âr /cdrom/collect/dlpeople/* import/</CodeLine>
+<CodeLine>umount /cdrom</CodeLine>
+<CodeLine>import.pl dlpeople</CodeLine>
+<CodeLine>buildcol.pl dlpeople</CodeLine>
+<CodeLine>rm -r index/*</CodeLine>
+<CodeLine>mv building/* index</CodeLine>
+</Content>
+</Subsection>
+<Subsection id="differences_between_windows_and_unix">
+<Title>
+<Text id="98">DiffÃ©rences entre Windows et Unix</Text>
+</Title>
+<Content>
+<Text id="99">Les processus de construction de collection sont trÃšs similaires sous Unix et sous Windows, mais quelques petites diffÃ©rences demeurent, diffÃ©rences que nous avons rÃ©sumÃ©es dans la tableÂ <CrossRef target="Table" ref="collection-building_differences_between_windows_and_linux"/>.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="greenstone_directories">
+<Title>
+<Text id="100">Les rÃ©pertoires de Greenstone</Text>
+</Title>
+<Content>
+<Text id="101">La figureÂ <CrossRef target="Figure" ref="structure_of_the_gsdlhome_directory"/> montre la structure du rÃ©pertoire GSDLHOME. La tableÂ <CrossRef target="Table" ref="where_to_find_information_about_directories"/> donne une brÃšve description du contenu de chacun des rÃ©pertoires reprÃ©sentÃ©s dans le diagramme. Certains rÃ©pertoires seront plus dÃ©taillÃ©s plus loin dans le manuelÂ --Â utilisez le guide des sections de la tableÂ <CrossRef target="Table" ref="where_to_find_information_about_directories"/> pour savoir oÃ¹ aller chercher des informations supplÃ©mentaires.</Text>
+<Figure id="structure_of_the_gsdlhome_directory">
+<Title>
+<Text id="102">Structure du rÃ©pertoire GSDLHOME</Text>
+</Title>
+<File width="415" height="143" url="images/Dev_Fig_4.png"/>
+</Figure>
+<Table id="where_to_find_information_about_directories">
+<Title>
+<Text id="103">OÃ¹ trouver de l'information Ã  propos des rÃ©pertoires</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="331">
+<Text id="104"><b>Contenu</b></Text>
+</th>
+<th width="66">
+<Text id="105">Section</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="106"><i>bin</i></Text>
+</th>
+<th width="331">
+<Text id="107">Code exÃ©cutable, comprenant des binaires dans le rÃ©pertoire portant le nom de votre systÃšme d'exploitation.</Text>
+</th>
+<th width="66">
+<Text id="108">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="109"><i>bin/script</i></Text>
+</th>
+<th width="331">
+<Text id="110">Scripts Perl utilisÃ©s pour la crÃ©ation et la construction de collections (tels que<i>import.pl</i>et<i>buildcol.pl</i>). Pour obtenir une description de ces programmes, tapez leur nom Ã  l'invite de commandes.</Text>
+</th>
+<th width="66">
+<Text id="111">1.3</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="112"><i>perllib</i></Text>
+</th>
+<th width="331">
+<Text id="113">Modules Perl utilisÃ©s au moment de l'import et de la construction (tels que les greffons, ou<i>plugins</i>)</Text>
+</th>
+<th width="66">
+<Text id="114">2.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="115"><i>perllib/plugins</i></Text>
+</th>
+<th width="331">
+<Text id="116">Code Perl pour les greffons (<i>plugins</i>) de traitement de documents. </Text>
+</th>
+<th width="66">
+<Text id="117">2.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="118"><i>perllib/classify</i></Text>
+</th>
+<th width="331">
+<Text id="119">Code Perl pour les classificateurs (tels que le code AZList, qui crÃ©e une liste de documents en se basant sur l'ordre alphabÃ©tique d'un attribut.)</Text>
+</th>
+<th width="66">
+<Text id="120">2.2</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="121"><i>cgi-bin</i></Text>
+</th>
+<th width="331">
+<Text id="122">Tous les scripts CGI de Greenstone, qui seront dÃ©placÃ©s vers le rÃ©pertoire<i>cgi-bin</i>du systÃšme.</Text>
+</th>
+<th width="66">
+<Text id="123">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="124"><i>tmp</i></Text>
+</th>
+<th width="331">
+<Text id="125">RÃ©pertoire utilisÃ© par Greenstone pour le stockage des fichiers temporaires.</Text>
+</th>
+<th width="66">
+<Text id="126">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="127"><i>etc</i></Text>
+</th>
+<th width="331">
+<Text id="128">Fichiers de configuration, journaux d'initialisation et d'erreur, bases de donnÃ©es d'autorisation des utilisateurs.</Text>
+</th>
+<th width="66">
+<Text id="129">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="130"><i>src</i></Text>
+</th>
+<th width="331">
+<Text id="131">Code C++ utilisÃ© pour servir des collections sur un serveur web.</Text>
+</th>
+<th width="66">
+<Text id="132">3</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="133"><i>src/colservr</i></Text>
+</th>
+<th width="331">
+<Text id="134">Code C++ pour servir des collectionsâpour rÃ©pondre aux requÃªtes et ce genre de choses.</Text>
+</th>
+<th width="66">
+<Text id="135"><CrossRef target="Section" ref="protocol"/></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="136"><i>src/recpt</i></Text>
+</th>
+<th width="331">
+<Text id="137">Code C++ pour obtenir des requÃªtes depuis l'interface utilisateur et mettre en forme les rÃ©ponses aux requÃªtes pour cette interface.</Text>
+</th>
+<th width="66">
+<Text id="138">3.9</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="139"><i>packages</i></Text>
+</th>
+<th width="331">
+<Text id="140">Code source des paquetages logiciels externes Ã  Greenstone mais utilisÃ©s par ce dernier.</Text>
+</th>
+<th width="66">
+<Text id="141">2.5</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="142"><i>packages/mg</i></Text>
+</th>
+<th width="331">
+<Text id="143">Code source de MG, logiciel de compression et d'indexation utilisÃ© par Greenstone.</Text>
+</th>
+<th width="66">
+<Text id="144">2.5</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="145"><i>mappings</i></Text>
+</th>
+<th width="331">
+<Text id="146">Tables de correspondance Unicode (comme par exemple pour le jeu de caractÃšres chinois GB).</Text>
+</th>
+<th width="66">
+<Text id="147">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="148"><i>macros</i></Text>
+</th>
+<th width="331">
+<Text id="149">Les fichiers de macros utilisÃ©s pour l'interface utilisateur.</Text>
+</th>
+<th width="66">
+<Text id="150">2.4</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="151"><i>collect</i></Text>
+</th>
+<th width="331">
+<Text id="152">Collections servies par cette copie de Greenstone.</Text>
+</th>
+<th width="66">
+<Text id="153">1.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="154"><i>lib</i></Text>
+</th>
+<th width="331">
+<Text id="155">Code C++ utilisÃ© Ã  la fois par le serveur de collection et par le rÃ©ceptionniste.</Text>
+</th>
+<th width="66">
+<Text id="156">3.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="157"><i>images</i></Text>
+</th>
+<th width="331">
+<Text id="158">Images utilisÃ©es dans l'interface utilisateur.</Text>
+</th>
+<th width="66">
+<Text id="159">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="160"><i>docs</i></Text>
+</th>
+<th width="331">
+<Text id="161">Documentation.</Text>
+</th>
+<th width="66">
+<Text id="162">â</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Section>
+<Section id="import_and_build_processes">
+<Title>
+<Text id="163">Les processus d'import et de construction</Text>
+</Title>
+<Content>
+<Text id="164">Dans le processus de construction de collection dÃ©crit Ã  la sectionÂ <CrossRef target="Section" ref="building_collections_from_the_command_line"/>, on utilise une commande pour importer des documents (import.pl) et une autre commande pour construire la collection (buildcol.pl). Nous dÃ©taillons dans la prÃ©sente section ce que ces programmes font et les options qu'ils acceptent. Nous utiliserons la variable nom_col pour nous rÃ©fÃ©rer Ã  la collection en cours de construction ou d'import.</Text>
+<Text id="165">Les processus d'import et de construction sont trÃšs similaires, ce qui explique le nombre d'options communes qu'ils comptent, options dÃ©crites dans la tableÂ <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/> (souvenez-vous que pour obtenir la liste des options acceptÃ©es par tout script Greenstone, il suffit de taper son nom seul, sans argument, Ã  l'invite de commandes).</Text>
+<Table id="options_for_the_import_and_build_processes">
+<Title>
+<Text id="166">Options des processus d'import et de construction</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="104">
+<Text id="167"><b>Argument</b></Text>
+</th>
+<th width="293">
+<Text id="168"><b>Fonction</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="169"><i>-verbosity</i></Text>
+</th>
+<th width="104">
+<Text id="170">Nombre de 0 Ã  3</Text>
+</th>
+<th width="293">
+<Text id="171">ContrÃŽle la quantitÃ© d'informations sur le processus qui sont affichÃ©es sur la sortie d'erreur standard: Â«0Â» en donne un peu, Â«3Â» en donne beaucoup.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="172"><i>-archivedir</i></Text>
+</th>
+<th width="104">
+<Text id="173">Nom de rÃ©pertoire</Text>
+</th>
+<th width="293">
+<Text id="174">SpÃ©cifie oÃ¹ les fichiers d'archives de Greenstone sont stockÃ©s, c'est-Ã -dire oÃ¹<i>import.pl</i>les enregistre et oÃ¹<i>buildcol.pl</i>les trouve. La valeur par dÃ©faut est<i>GSDLHOME/collect/nom_col/archives</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="175"><i>-maxdocs</i></Text>
+</th>
+<th width="104">
+<Text id="176">Nombre &gt;0</Text>
+</th>
+<th width="293">
+<Text id="177">Nombre maximal de documents Ã  importer ou Ã  construire. Option utile lors de tests de fichiers de configuration d'une nouvelle collection, ou de nouveaux greffons<i>plugins</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="178"><i>-collectdir</i></Text>
+</th>
+<th width="104">
+<Text id="179">Nom de rÃ©pertoire</Text>
+</th>
+<th width="293">
+<Text id="180">SpÃ©cifie oÃ¹ la collection se trouve. La valeur par dÃ©faut est<i>GSDLHOME/collect</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="181"><i>-out</i></Text>
+</th>
+<th width="104">
+<Text id="182">Nom de fichier</Text>
+</th>
+<th width="293">
+<Text id="183">SpÃ©cifie un fichier oÃ¹ Ã©crire tous les messages produits, le comportement par dÃ©faut Ã©tant de les afficher sur la sortie d'erreur standard (c'est-Ã -dire l'Ã©cran). Option utile lorsque l'on travaille avec des niveaux de dÃ©bogage.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="184"><i>-keepold</i></Text>
+</th>
+<th width="104">
+<Text id="185">Aucun</Text>
+</th>
+<th width="293">
+<Text id="186">N'efface pas le rÃ©sultat de l'ancienne opÃ©ration d'import ou de construction. Dans le cas de l'import, ceci signifie que l'on n'efface pas le contenu du rÃ©pertoire<i>archives</i>; dans le cas de la construction, ceci signifie que l'on n'efface pas le contenu du rÃ©pertoire<i>building</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="187"><i>âdebug</i></Text>
+</th>
+<th width="104">
+<Text id="188">Aucun</Text>
+</th>
+<th width="293">
+<Text id="189">Affiche la sortie du greffon<i>plugin</i>sur la sortie standard.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Subsection id="the_import_process">
+<Title>
+<Text id="190">Le processus d'import</Text>
+</Title>
+<Content>
+<Text id="191">Le processus d'import a pour but principal de convertir les documents depuis leur format d'origine vers le format d'archivage de Greenstone utilisÃ© de maniÃšre interne par Greenstone, et d'Ã©crire un fichier de compte-rendu (archives.inf) qui sera utilisÃ© lors de la construction de la collection. Le programme import.pl a besoin de connaÃ®tre les greffons (plugins) Ã  utiliser, et de savoir oÃ¹ trouver les fichiers des documents originaux. La tableÂ <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/> montre les options communes aux processus d'import et de construction; la tableÂ <CrossRef target="Table" ref="additional_options_for_the_import_process"/> montre les options propres au processus d'import. L'option OIDtype mÃ©rite quelques explications. Chaque document dispose d'un identifiant d'objet associÃ©, ou OID (Object IDentifier). La meilleure faÃ§on de calculer un tel identifiant est de calculer une somme de contrÃŽle (Â«hacherÂ») le contenu du document (c'est la mÃ©thode hash). Cependant, cette mÃ©thode Ã©tant lente, il est possible de choisir une solution plus simple, incrÃ©mentale, qui se contente de numÃ©roter les documents sÃ©quentiellement dans leur ordre de fourniture (c'est la mÃ©thode incremental). Vous pouvez utiliser la mÃ©thode incremental pour aller plus vite, mais utilisez la mÃ©thode hash si vous avez l'intention d'ajouter des documents Ã  votre collection plus tard, sans recommencer tout le processus d'import.</Text>
+<Table id="additional_options_for_the_import_process">
+<Title>
+<Text id="192">Options propres au processus d'import</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="104">
+<Text id="193"><b>Argument</b></Text>
+</th>
+<th width="293">
+<Text id="194"><b>Fonction</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="195"><i>-importdir</i></Text>
+</th>
+<th width="104">
+<Text id="196">Nom de rÃ©pertoire</Text>
+</th>
+<th width="293">
+<Text id="197">SpÃ©cifie oÃ¹ trouver les contenus Ã  importer. La valeur par dÃ©faut est Defaults to<i>GSDLHOME/collect/nom_col/import</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="198"><i>-removeold</i></Text>
+</th>
+<th width="104">
+<Text id="199">Aucun</Text>
+</th>
+<th width="293">
+<Text id="200">Efface le contenu du rÃ©pertoire <i>archives</i>avant l'import.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="201"><i>-gzip</i></Text>
+</th>
+<th width="104">
+<Text id="202">Aucun</Text>
+</th>
+<th width="293">
+<Text id="203">Compresse l'archive de documents Greenstone produite par<i>import</i>(<i>ZIPPlug</i>doit faire partie de la liste des plugins greffons, et le programme<i>gzip</i>doit Ãªtre installÃ© sur votre machine).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="204"><i>-groupsize</i></Text>
+</th>
+<th width="104">
+<Text id="205">Nombre &gt;0</Text>
+</th>
+<th width="293">
+<Text id="206">Nombre de documents Ã  rassembler dans un fichier d'archive de Greenstone. La valeur par dÃ©faut est 1 (c'est-Ã -dire que chaque fichier ne renferme qu'un document).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="207"><i>âsortmeta</i></Text>
+</th>
+<th width="104">
+<Text id="208">Nom de balise de mÃ©ta-donnÃ©es</Text>
+</th>
+<th width="293">
+<Text id="209">Trie les documents par ordre alphabÃ©tique selon le contenu de la balise de mÃ©ta-donnÃ©es. Cette fonctionnalitÃ© est dÃ©sactivÃ©e si la collection compte plus d'un groupe (c'est-Ã -dire que<i>groupsize</i>&gt;1).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="210"><i>-OIDtype</i></Text>
+</th>
+<th width="104">
+<Text id="211"><i>hash</i>ou<br/>
+<i>incremental</i></Text>
+</th>
+<th width="293">
+<Text id="212">MÃ©thode de crÃ©ation des <i>OIDs</i>pour les documents:<i>hash</i>calcule une somme de contrÃŽle du contenu mais est lente;<i>incremental</i>se contente d'affecter des numÃ©ros de documents de maniÃšre sÃ©quentielle, elle est donc plus rapide.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Figure id="steps_in_the_import_process">
+<Title>
+<Text id="213">Ãtapes du processus d'import</Text>
+</Title>
+<File width="402" height="379" url="images/Dev_Fig_5.png"/>
+</Figure>
+<Text id="214">La figureÂ <CrossRef target="Figure" ref="steps_in_the_import_process"/> reprÃ©sente le processus d'import tel qu'implÃ©mentÃ© par le programme import.pl. Chaque ovale reprÃ©sente un module utilisÃ© pour mener Ã  bien les tÃ¢ches relatives Ã  une partie spÃ©cifique du systÃšme Greenstone. On peut trouver tous ces modules dans le rÃ©pertoire GSDLHOME/perllib.</Text>
+<Text id="215">Pour l'Ã©tape 3, remarquez que des variables d'import telles que importdir et archivedir peuvent Ãªtre positionnÃ©es dans le fichier de configuration de la collection ou depuis la ligne de commande. Si elles sont positionnÃ©es dans la ligne de commande, toute valeur spÃ©cifiÃ©e dans le fichier de configuration sera ignorÃ©e.</Text>
+<Text id="216">L'Ã©tape 6 voit la crÃ©ation du fichier d'information d'archives (archives.inf).</Text>
+<Text id="217">L'Ã©tape 7 crÃ©e un objet qui saura oÃ¹ sauvegarder les documents, et qui suivra toute instruction particuliÃšre de sauvegarde (telle que sortmeta, qui trie les documents selon une balise de mÃ©ta-donnÃ©es spÃ©cifiÃ©e).</Text>
+<Text id="218">La plupart du travail effectuÃ© par le processus d'import est en fait accompli par les greffons (plugins), qui sont appelÃ©s par le module plugin. Ce module met en place un pipe-line des greffons spÃ©cifiÃ©s dans le fichier de configuration de collection. Il gÃšre aussi l'Ã©criture des documents d'archive de Greenstone (en utilisant un objet document).</Text>
+</Content>
+</Subsection>
+<Subsection id="the_build_process">
+<Title>
+<Text id="219">Le processus de construction</Text>
+</Title>
+<Content>
+<Text id="220">Lors du processus de construction le texte est compactÃ©, et les index de corps du texte spÃ©cifiÃ©s dans le fichier de configuration de collection sont crÃ©Ã©s. De plus, les informations relatives Ã  la collection qui apparaÃ®tront sur le web sont prÃ©-calculÃ©es et incorporÃ©es dans la collectionÂ --Â il s'agit par exemple des informations relatives aux icones et aux titres, ainsi que des informations produites par des classificateurs. Le programme buildcol.pl partage de nombreuses options avec import.pl; elles sont dÃ©taillÃ©es dans la tableÂ <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/>. La tableÂ <CrossRef target="Table" ref="additional_options_for_the_build_process"/> prÃ©sente les options qui lui sont propres.</Text>
+<Table id="additional_options_for_the_build_process">
+<Title>
+<Text id="221">Options propres au processus de construction</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="104">
+<Text id="222"><b>Argument</b></Text>
+</th>
+<th width="293">
+<Text id="223"><b>Fonction</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="224"><i>-builddir</i></Text>
+</th>
+<th width="104">
+<Text id="225">Nom de rÃ©pertoire</Text>
+</th>
+<th width="293">
+<Text id="226">SpÃ©cifie oÃ¹ trouver le rÃ©sultat de la construction (la valeur par dÃ©faut est<i>GSDLHOME/collect/nom_col/building</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="227"><i>-index</i></Text>
+</th>
+<th width="104">
+<Text id="228">Nom d'index (ex.<br/>
+<i>section:Title</i>)</Text>
+</th>
+<th width="293">
+<Text id="229">SpÃ©cifie quels index construire. La valeur par dÃ©faut est l'ensemble des index indiquÃ©s dans le fichier de configuration de la collection.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="230"><i>-allclassifications</i></Text>
+</th>
+<th width="104">
+<Text id="231">Aucun</Text>
+</th>
+<th width="293">
+<Text id="232">EmpÃªche le processus de construction d'effacer les classifications qui ne contiennent aucun document (comme par exemple la classification Â«XÂ» dans les titres si aucun document n'a un titre commenÃ§ant par la lettre Â«XÂ»).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="233"><i>-create_images</i></Text>
+</th>
+<th width="104">
+<Text id="234">Aucun</Text>
+</th>
+<th width="293">
+<Text id="235">CrÃ©e automatiquement les icones de collection (pour utiliser ceci, il faut avoir installÃ© GIMP et le module Perl Gimp).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="236"><i>-mode</i></Text>
+</th>
+<th width="104">
+<Text id="237"><i>all</i>,<br/>
+<i>compress_text</i>,<br/>
+<i>infodb</i>, or<br/>
+<i>build_index</i></Text>
+</th>
+<th width="293">
+<Text id="238">DÃ©termine ce que le processus de construction doit faire (la valeur par dÃ©faut est<i>all</i>). Le mode<i>All</i>effectue une construction complÃšte,<i>compress_text</i>se contente de compacter le texte du document,<i>infodb</i>crÃ©e une base de donnÃ©es des informations relatives Ã  la collectionânom, fichiers, fichiers associÃ©s, informations de classification etc.âet<i>build_index</i>construit les index spÃ©cifiÃ©s dans le fichier de configuration de collection ou Ã  la ligne de commande.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="239"><i>âno_text</i></Text>
+</th>
+<th width="104"/>
+<th width="293">
+<Text id="240">Ne stocke pas de texte compactÃ©. Cette option est utile pour minimiser la taille des index construits si l'on souhaite toujours afficher les documents originaux au moment de l'exÃ©cution.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Figure id="steps_in_the_build_process">
+<Title>
+<Text id="241">Ãtapes du processus de construction</Text>
+</Title>
+<File width="308" height="234" url="images/Dev_Fig_6.png"/>
+</Figure>
+<Text id="242">Le diagramme de la figureÂ <CrossRef target="Figure" ref="steps_in_the_build_process"/> reprÃ©sente l'exÃ©cution du programme buildcol.pl. De nombreuses Ã©tapes sont communes avec le processus d'import. La premiÃšre Ã©tape qui diffÃšre est l'Ã©tape 4 (Ã  gauche sur la figure). Cette Ã©tape n'est effectuÃ©e que si l'option create_images a Ã©tÃ© activÃ©e. Les images sont alors crÃ©Ã©es et consignÃ©es dans le fichier de configuration de collection Ã  l'aide d'une fonction du script buildcol.pl. Pour que ceci fonctionne correctement, il faut avoir installÃ© et configurÃ© convenablement GIMP (GNU Image-Manipulation Program, programme de manipulation d'images de GNU) et le module Perl Gimp. Il faut aussi disposer d'un accÃšs en Ã©criture (et en lecture) sur le fichier de configuration de collection.</Text>
+<Text id="243">L'Ã©tape 5 contrÃŽle d'abord l'existence ou non d'une procÃ©dure de construction propre Ã  la collection. Certaines collections impliquent des traitements particuliers au moment de la construction, auquel cas il faut Ã©crire un constructeur propre Ã  la collection et le placer dans son rÃ©pertoire perllib, sous le nom de la collection auquel on aura concatÃ©nÃ© la chaÃ®ne Â«builderÂ» (constructeur). Les constructeurs propres aux collections hÃ©ritent de mgbuilder. Dans l'Ã©tape 5 le constructeur (qu'il s'agisse du constructeur par dÃ©faut ou d'un constructeur propre Ã  la collection) est initialisÃ© avec des informations telles que le nombre de documents Ã  inclure, s'il faut ou non garder l'ancienne version de la collection, et oÃ¹ les rÃ©pertoires building et archive sont localisÃ©s.</Text>
+<Text id="244">L'Ã©tape 6 est l'Ã©tape de construction, au cours de laquelle le texte des documents est compactÃ© et indexÃ©, les titres et les icones de collection sont stockÃ©s dans la base de donnÃ©es d'informations de la collection, et les structures de donnÃ©es sont construites pour supporter les classificateurs appelÃ©s par les greffons (plugins) de la collection. Toutes ces Ã©tapes sont menÃ©es Ã  bien par mgbuilder (ou un constructeur propre Ã  la collection), qui lui-mÃªme utilise MG (Managing Gigabytes (gÃ©rer les giga-octets), voir Witten<i>et al.</i>, 1999), logiciel de compression et d'indexation.</Text>
+<Text id="245">L'option mode permet de spÃ©cifier les portions de collection Ã  construire, mais par dÃ©faut tout est construit: texte compactÃ©, index, et base de donnÃ©es d'informations de la collection.</Text>
+<Text id="246">Pour publier une collection sur le web aprÃšs construction, il faut la dÃ©placer du rÃ©pertoire building vers le rÃ©pertoire index. Les collections ne sont pas construites directement dans le rÃ©pertoire index car des collections volumineuses peuvent prendre plusieurs heures ou jours Ã  construire. Il est important que le processus de construction n'affecte pas une copie existante de la collection tant qu'il n'est pas terminÃ©.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="greenstone_archive_documents">
+<Title>
+<Text id="247">Documents d'archives de Greenstone</Text>
+</Title>
+<Content>
+<Text id="248">Tous les documents source sont importÃ©s dans le systÃšme Greenstone aprÃšs conversion dans le format d'archivage de Greenstone. C'est un style XML qui divise les documents en sections, et qui peut renfermer des mÃ©ta-donnÃ©es au niveau du document ou de chaque section. Vous ne devriez pas avoir Ã  crÃ©er des fichiers d'archives de Greenstone manuellementÂ --Â c'est le travail des greffons (plugins) de traitement de documents dÃ©crits dans le chapitre suivant. Il est cependant utile de comprendre le format des fichiers Greenstone, et c'est pourquoi nous le dÃ©crivons ici.</Text>
+<Text id="249">En XML, les mots-clefs sont entourÃ©s de chevrons pour le balisage. Le format d'archivage de Greenstone encode des documents dÃ©jÃ  en HTML, et tout caractÃšre &lt;, &gt;, ou " compris dans le texte original est Ã©chappÃ© grÃ¢ce Ã  la convention standard &amp;lt;, &amp;gt;, et &amp;quot;.</Text>
+<Figure id="greenstone_archive_format">
+<Title>
+<Text id="250">Format d'archivage de Greenstone: (a) dÃ©finition de type de document (DTD); (b) document d'exemple</Text>
+<SubTitle>
+<Text id="251">(a)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;!DOCTYPE GreenstoneArchive [</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Section (Description,Content,Section*)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Description (Metadata*)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Content (#PCDATA)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Metadata (#PCDATA)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;ATTLIST Metadata name CDATA #REQUIRED&gt;</CodeLine>
+<CodeLine>]&gt;</CodeLine>
+</Figure>
+<Figure id="greenstone_archive_format_1">
+<Title>
+<Text id="252"/>
+<SubTitle>
+<Text id="253">(b)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;?xml version="1.0"?&gt;</CodeLine>
+<CodeLine>&lt;!DOCTYPE GreenstoneArchive SYSTEM</CodeLine>
+<CodeLine>"http://greenstone.org/dtd/GreenstoneArchive/1.0/GreenstoneArchive.dtd" &gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "gsdlsourcefilename"&gt;ec158e.txt&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Freshwater Resources in Arid Lands&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "Identifier"&gt;HASH0158f56086efffe592636058&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "gsdlassocfile"&gt;cover.jpg:image/jpeg:&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "gsdlassocfile"&gt;p07a.png:image/png:&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Preface&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>This is the text of the preface</i>
+</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;First and only chapter&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Part 1&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>This is the first part of the first and only chapter</i>
+</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Part 2&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>This is the second part of the first and only chapter</i>
+</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+</Figure>
+<Text id="254">La premiÃšre partie de la figureÂ <CrossRef target="Figure" ref="greenstone_archive_format"/> donne la dÃ©finition de type de document (DTD) pour le format d'archivage de Greenstone. Pour simplifier, un document est divisÃ© en Ã©lÃ©ments Section, et les sections peuvent Ãªtre imbriquÃ©es. Chaque Section renferme une Description qui comprend zÃ©ro ou plusieurs Ã©lÃ©ments Metadata (mÃ©ta-donnÃ©es), et un Ã©lÃ©ment Content (contenu), qui peut Ãªtre vide, et qui renferme les donnÃ©es du document Ã  proprement parler. Ã chaque Ã©lÃ©ment Metadata on associe un attribut de nom (dont le nom est libre), et des donnÃ©es textuelles. En XML, PCDATA signifie Â«parsed character dataÂ» (donnÃ©es de type caractÃšre analysÃ©es), c'est-Ã -dire du texte, tout simplement.</Text>
+<Text id="255">La deuxiÃšme partie de la figureÂ <CrossRef target="Figure" ref="greenstone_archive_format_1"/> montre un document simple Ã©crit dans ce format, qui est un petit livre avec deux images associÃ©es. Le livre consiste en deux sections appelÃ©es respectivement PrÃ©face et Premier et unique chapitre, la deuxiÃšme section se divisant en deux sous-sections. Remarquez qu'il n'existe aucune notion de Â«chapitreÂ» en tant que tel: un chapitre est simplement reprÃ©sentÃ© comme une section de premier niveau.</Text>
+<Table id="greenstone_archive_format_values">
+<Title>
+<Text id="256">Format d'archivage de Greenstone: valeurs pour l'attribut<i>name</i>de la balise<i>Metadata</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="130">
+<Text id="257"><i>gsdlsourcefilename</i></Text>
+</th>
+<th width="400">
+<Text id="258">Fichier original Ã  partir duquel on a gÃ©nÃ©rÃ© le fichier d'archive de Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="130">
+<Text id="259"><i>gsdlassocfile</i></Text>
+</th>
+<th width="400">
+<Text id="260">Fichier associÃ© au document (un fichier d'image par exemple)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="261">La balise &lt;Section&gt; dÃ©note le dÃ©but de chaque section de document, et la balise fermante correspondante (&lt;/Section&gt;) marque la fin de cette section. Ã la suite de chaque balise &lt;Section&gt; on trouve un Ã©lÃ©ment &lt;Description&gt;. S'y trouve un nombre quelconque d'Ã©lÃ©ments &lt;Metadata&gt;. On peut ainsi associer diffÃ©rentes mÃ©ta-donnÃ©es Ã  diffÃ©rentes sections du document. La plupart de ces mÃ©ta-donnÃ©es sont des types particuliers de mÃ©ta-donnÃ©es tels que &lt;Title&gt; (titre). Les deux valeurs de l'attribut name (nom) montrÃ©es dans la tableÂ <CrossRef target="Table" ref="greenstone_archive_format_values"/> reÃ§oivent de Greenstone un traitement particulier; toutes les autres sont considÃ©rÃ©es comme des mÃ©ta-donnÃ©es attachÃ©es Ã  cette section.</Text>
+<Text id="262">Dans certaines collections les documents dont divisÃ©s en pages. Ces derniÃšres sont alors traitÃ©es comme des sections. Un livre peut par exemple disposer de sections de premier niveau qui correspondent Ã  des chapitres, au sein desquels on trouvera un certain nombre de Â«sectionsÂ» qui correspondront en rÃ©alitÃ© aux diffÃ©rentes pages du chapitre.</Text>
+<Subsection id="document_metadata">
+<Title>
+<Text id="263">MÃ©ta-donnÃ©es de document</Text>
+</Title>
+<Content>
+<Text id="264">Les mÃ©ta-donnÃ©es sont des informations de description associÃ©es Ã  un document telles que l'auteur, le titre, la date, des mots-clefs, etc. Nous avons dÃ©jÃ  signalÃ© que les mÃ©ta-donnÃ©es Ã©taient stockÃ©es avec les documents. En observant la figureÂ <CrossRef target="Figure" ref="greenstone_archive_format"/>, on remarque que les balises &lt;Metadata&gt; spÃ©cifient le nom du type de mÃ©ta-donnÃ©es, et lui donnent une valeur. On a par exemple la ligne &lt;Metadata name="Title"&gt;Premier et unique chapitre&lt;/Metadata&gt; dans la deuxiÃšme partie de la figureÂ <CrossRef target="Figure" ref="greenstone_archive_format_1"/>Â --Â le titre d'un document est une mÃ©ta-donnÃ©e qui lui est associÃ©e. On utilise le standard de mÃ©ta-donnÃ©es Dublin Core pour dÃ©finir des types de mÃ©ta-donnÃ©es (Dublin Core, 2001; Weibel, 1999; Thiele, 1997).</Text>
+<Text id="265">La tableÂ <CrossRef target="Table" ref="dublin_core_metadata_standard"/> montre les types disponibles dans le standard, les Ã©toiles signalant les entrÃ©es disponibles Ã  ce jour sur le site web de la bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande. Si aucun type ne dÃ©crit correctement un certain type de mÃ©ta-donnÃ©es, on peut aussi utiliser des types de mÃ©ta-donnÃ©es absentes du standard Dublin Core. La collection Â«DemoÂ» contient par exemple les mÃ©ta-donnÃ©es how to (comment faire) et Magazine.</Text>
+<Table id="dublin_core_metadata_standard">
+<Title>
+<Text id="266">Standard de mÃ©ta-donnÃ©es</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="133">
+<Text id="267"><b>Nom</b></Text>
+</th>
+<th width="94">
+<Text id="268"><b>Balise de mÃ©ta-donnÃ©es</b></Text>
+</th>
+<th width="305">
+<Text id="269"><b>DÃ©finition</b></Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="270">*Title</Text>
+</th>
+<th width="94">
+<Text id="271">Title</Text>
+</th>
+<th width="305">
+<Text id="272">Nom donnÃ© Ã  la ressource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="273">*CrÃ©ateur</Text>
+</th>
+<th width="94">
+<Text id="274"><i>Creator</i></Text>
+</th>
+<th width="305">
+<Text id="275">EntitÃ© principalement responsable de la fabrication du contenu de la ressource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="276">*ThÃšme et mots-clefs</Text>
+</th>
+<th width="94">
+<Text id="277"><i>Subject</i></Text>
+</th>
+<th width="305">
+<Text id="278">ThÃšme du contenu de la ressource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="279">*Description</Text>
+</th>
+<th width="94">
+<Text id="280"><i>Description</i></Text>
+</th>
+<th width="305">
+<Text id="281">Compte-rendu du contenu de la ressource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="282">*Ãditeur</Text>
+</th>
+<th width="94">
+<Text id="283"><i>Publisher</i></Text>
+</th>
+<th width="305">
+<Text id="284">EntitÃ© responsable de la publication de la ressource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="285">Contributeur</Text>
+</th>
+<th width="94">
+<Text id="286"><i>Contributor</i></Text>
+</th>
+<th width="305">
+<Text id="287">EntitÃ© responsable de contributions au contenu de la ressource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="288">*Date</Text>
+</th>
+<th width="94">
+<Text id="289"><i>Date</i></Text>
+</th>
+<th width="305">
+<Text id="290">Date de publication de la ressource ou toute autre date importante associÃ©e Ã  la ressource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="291">Type de ressource</Text>
+</th>
+<th width="94">
+<Text id="292"><i>Type</i></Text>
+</th>
+<th width="305">
+<Text id="293">Nature ou genre du contenu de la ressource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="294">Format</Text>
+</th>
+<th width="94">
+<Text id="295"><i>Format</i></Text>
+</th>
+<th width="305">
+<Text id="296">ReprÃ©sentation physique ou numÃ©rique de la ressource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="297">*Identificateur de resource</Text>
+</th>
+<th width="94">
+<Text id="298"><i>Identifier</i></Text>
+</th>
+<th width="305">
+<Text id="299">RÃ©fÃ©rence univoque Ã  la ressource dans un contexte donnÃ©: il s'agit de l'identifiant d'objet, ou<i>OID</i></Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="300">*Source</Text>
+</th>
+<th width="94">
+<Text id="301"><i>Source</i></Text>
+</th>
+<th width="305">
+<Text id="302">RÃ©fÃ©rence Ã  une ressource d'oÃ¹ la prÃ©sente ressource est tirÃ©e</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="303">*Langue</Text>
+</th>
+<th width="94">
+<Text id="304"><i>Language</i></Text>
+</th>
+<th width="305">
+<Text id="305">Langue du contenu intellectuel de la ressource </Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="306">Relation</Text>
+</th>
+<th width="94">
+<Text id="307"><i>Relation</i></Text>
+</th>
+<th width="305">
+<Text id="308">RÃ©fÃ©rence Ã  une ressource liÃ©e</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="309">*Couverture</Text>
+</th>
+<th width="94">
+<Text id="310"><i>Coverage</i></Text>
+</th>
+<th width="305">
+<Text id="311">PortÃ©e ou Ã©tendue du contenu de la ressource</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="312">Gestion des droits</Text>
+</th>
+<th width="94">
+<Text id="313"><i>Rights</i></Text>
+</th>
+<th width="305">
+<Text id="314">Informations sur les droits attachÃ©s Ã  la ressource ou dans celle-ci</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="inside_greenstone_archive_documents">
+<Title>
+<Text id="315">Au coeur des documents d'archive de Greenstone</Text>
+</Title>
+<Content>
+<Text id="316">Le format d'archivage de Greenstone impose peu de structure aux documents individuels. Les document sont divisÃ©s en paragraphes. Ils peuvent Ãªtre divisÃ©s hiÃ©rarchiquement en sections et en sous-sections, que l'on peut imbriquer jusqu'Ã  une profondeur arbitraire. Ã chaque document est associÃ© un identifiant de document ou OIDÂ --Â ces derniers servant aussi Ã  identifier les sections et les sous-sections par l'ajout de numÃ©ros de sections et de sous-sections, sÃ©parÃ©s par des points, Ã  l'OID du document. On se rÃ©fÃ©rera par exemple Ã  la sous-section 3 de la section 2 du document HASHa7 sous la forme HASHa7.2.3.</Text>
+<Text id="317">Quand on lit un livre dans une collection de Greenstone, la hiÃ©rarchie des sections est reportÃ©e dans la table des matiÃšres du livre. Les livres de la collection Â«DemoÂ», par exemple, disposent d'une table des matiÃšres hiÃ©rarchique qui montre des chapitres, des sections, et des sous-sections, comme l'illustre la figureÂ <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection"/>. Les documents de la collection Computer Science Technical Reports (rapports techniques en informatique) ne disposent pas d'une structure hiÃ©rarchique de sections, mais chaque document est divisÃ© en pages et on peut naviguer parmi les pages d'un document rapatriÃ©. Les chapitres, les sections, les sous-sections, et les pages sont tous simplement implÃ©mentÃ©s en tant que Â«sectionsÂ» au sein du document.</Text>
+<Figure id="hierarchical_structure_in_the_demo_collection">
+<Title>
+<Text id="318">Structure hiÃ©rarchique de la collection Â«DemoÂ»</Text>
+<SubTitle>
+<Text id="318a">(a)</Text>
+</SubTitle>
+</Title>
+<File width="373" height="251" url="images/Dev_Fig_8a.png"/>
+</Figure>
+<Figure id="hierarchical_structure_in_the_demo_collection_1">
+<Title>
+<Text id="318b">Structure hiÃ©rarchique de la collection Â«DemoÂ»</Text>
+<SubTitle>
+<Text id="318c">(b)</Text>
+</SubTitle>
+</Title>
+<File width="373" height="251" url="images/Dev_Fig_8b.png"/>
+</Figure>
+<Text id="319">La structure de document sert aussi aux index de recherche. Il existe trois niveaux possibles d'index:<i>document</i>,<i>section</i>, et<i>paragraphe</i>, bien que la plupart des collections ne les utilisent pas tous trois. Un index de<i>document</i>contient tout le documentÂ --Â on peut l'utiliser pour trouver tous les documents contenant un ensemble particulier de mots (qui peuvent alors Ãªtre Ã©parpillÃ©s tout au long du document, loin les uns des autres). Lors de la crÃ©ation d'un index de<i>section</i>, toute portion de texte indexÃ©e s'Ã©tend d'une balise ouvrante &lt;Section&gt; Ã  la prochaine balise &lt;Section&gt;Â --Â un chapitre qui dÃ©bute immÃ©diatement par une autre section crÃ©era donc un document vide dans l'index. Les sections et les sous-sections sont traitÃ©es de la mÃªme maniÃšre: la structure hiÃ©rarchique de document est aplatie dans le but de crÃ©er des index de recherche. Les index de<i>paragraphe</i>considÃšrent chaque paragraphe comme un document Ã  part entiÃšre, et sont utiles pour mener des recherches plus ciblÃ©es.</Text>
+<Text id="320">Le menu dÃ©roulant de la figureÂ <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection_1"/> montre les index de recherche de la collection Â«DemoÂ». Les chapitres et les titres des sections sont des index au niveau de la section. alors que les livres entiers reprÃ©sentent des index au niveau des documents. Ã l'instar des index de texte, on peut crÃ©er des index pour tout type de mÃ©ta-donnÃ©es. Certaines collections proposent par exemple des exemples des titres de sections, comme illustrÃ© sur la figureÂ <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection_1"/>.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="configuration_file">
+<Title>
+<Text id="321">Fichier de configuration de la collection</Text>
+</Title>
+<Content>
+<Text id="322">Le fichier de configuration de la collection gouverne la structure de la collection telle qu'elle est vue par l'utilisateur, ce qui permet d'en personnaliser l'apparence et l'ergonomie, ainsi que la maniÃšre dont ses documents sont traitÃ©s et prÃ©sentÃ©s. Le programme mkcol.pl crÃ©e un fichier de configuration de collection simple, en enregistrant votre adresse de courrier Ã©lectronique en tant que crÃ©ateur et mainteneur. Nous avons vu lors de l'exploration pas Ã  pas du processus en ligne de commande que le crÃ©ateur est un argument obligatoire, et il sera Ã©galement enregistrÃ© en tant que mainteneur sauf si on fournit cette information sÃ©parÃ©ment.</Text>
+<Table id="items_in_the_collection_configuration_file">
+<Title>
+<Text id="323">ÃlÃ©ments du fichier de configuration de la collection</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<CodeLine>creator</CodeLine>
+</th>
+<th width="397">
+<Text id="324">Adresse de courrier Ã©lectronique du crÃ©ateur de la collection</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>maintainer</i></CodeLine>
+</th>
+<th width="397">
+<Text id="325">Adresse de courrier Ã©lectronique du mainteneur de la collection</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>public</i></CodeLine>
+</th>
+<th width="397">
+<Text id="326">La collection doit-elle Ãªtre rendue publique ou non?</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>beta</i></CodeLine>
+</th>
+<th width="397">
+<Text id="327">La collection est-elle une version bÃªta ou non? </Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>indexes</i></CodeLine>
+</th>
+<th width="397">
+<Text id="328">Liste des index Ã  construire</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>defaultindex</i></CodeLine>
+</th>
+<th width="397">
+<Text id="329">Index par dÃ©faut</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>subcollection</i></CodeLine>
+</th>
+<th width="397">
+<Text id="330">DÃ©finit une sous-collection fondÃ©e sur des mÃ©ta-donnÃ©es </Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>indexsubcollections</i></CodeLine>
+</th>
+<th width="397">
+<Text id="331">SpÃ©cifie quelles sous-collections indexer</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>defaultsubcollection</i></CodeLine>
+</th>
+<th width="397">
+<Text id="332">L'<i>indexsubcollection</i>par dÃ©faut</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>languages</i></CodeLine>
+</th>
+<th width="397">
+<Text id="333">Liste des langues dans lesquelles construire des index</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>defaultlanguage</i></CodeLine>
+</th>
+<th width="397">
+<Text id="334">Index de langue par dÃ©faut</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>collectionmeta</i></CodeLine>
+</th>
+<th width="397">
+<Text id="335">DÃ©finit des mÃ©ta-donnÃ©es au niveau de la collection</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>plugin</i></CodeLine>
+</th>
+<th width="397">
+<Text id="336">SpÃ©cifie un greffon (\lang{plugin}) Ã  utiliser au moment de la construction </Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>format</i></CodeLine>
+</th>
+<th width="397">
+<Text id="337">ChaÃ®ne de formatage (notion expliquÃ©e ci-dessous) </Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>classify</i></CodeLine>
+</th>
+<th width="397">
+<Text id="338">SpÃ©cifie un classificateur Ã  utiliser au moment de la construction</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="339">Chaque ligne du fichier de configuration de collection est sur le modÃšle de la paire Â«attribut, valeurÂ». Chaque attribut donne une information sur la collection qui affecte la maniÃšre dont elle sera reprÃ©sentÃ©e ou dont les documents seront traitÃ©s. La tableÂ <CrossRef target="Table" ref="items_in_the_collection_configuration_file"/> montre les Ã©lÃ©ments que l'on peut inclure dans un fichier de configuration de collection, et Ã  quoi sert chaque Ã©lÃ©ment. En plus de ceux-ci, on peut aussi spÃ©cifier toutes les options de ligne de commande des programmes import.pl et buildcol.pl dans un fichier de configuration de collection. Par exemple, une ligne disant no_text true (true signifie Â«vraiÂ» ou Â«activÃ©Â» dans ce contexte) positionnera l'option no_text du programme buildcol.pl.</Text>
+<Text id="340">Le fichier de configuration de collection crÃ©Ã© par le script mkcol.pl et prÃ©sentÃ© tableÂ <CrossRef target="Table" ref="collection_configuration_file_created_by_mkcd"/>, est trÃšs simple et ne contient que le strict minimum d'informations. Les lignes 1 et 2 proviennent de la valeur de creator fournie au programme mkcol.pl, et renferment les adresses de courrier Ã©lectronique des responsables de la crÃ©ation et de la maintenance de la collection (qui peuvent Ãªtre distincts).</Text>
+<Table id="collection_configuration_file_created_by_mkcd">
+<Title>
+<Text id="341">Fichier de configuration de collection crÃ©Ã© par<i>mkcd.pl</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="342"><b>Attribute</b></Text>
+</th>
+<th width="265">
+<Text id="343"><b>Valeur</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>1</CodeLine>
+</th>
+<th width="132">
+<CodeLine>creator</CodeLine>
+</th>
+<th width="265">
+<Text id="344">utilisateur@email.com</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>2</CodeLine>
+</th>
+<th width="132">
+<CodeLine>maintainer</CodeLine>
+</th>
+<th width="265">
+<Text id="345">utilisateur@email.com</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>3</CodeLine>
+</th>
+<th width="132">
+<CodeLine>public</CodeLine>
+</th>
+<th width="265">
+<Text id="346">True</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>4</CodeLine>
+</th>
+<th width="132">
+<CodeLine>beta</CodeLine>
+</th>
+<th width="265">
+<Text id="347">True</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>5</CodeLine>
+</th>
+<th width="132">
+<CodeLine>indexes</CodeLine>
+</th>
+<th width="265">
+<Text id="348">document:text</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>6</CodeLine>
+</th>
+<th width="132">
+<CodeLine>defaultindex</CodeLine>
+</th>
+<th width="265">
+<Text id="349">document:text</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>7</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="350">ZIPPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>8</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="351">GAPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>9</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="352">TextPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>10</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="353">HTMLPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>11</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="354">EMAILPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>12</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="355">ArcPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>13</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="356">RecPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>14</CodeLine>
+</th>
+<th width="132">
+<CodeLine>classify</CodeLine>
+</th>
+<th width="265">
+<Text id="357">AZList metadata Title</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>15</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="358">collectionname "collection d'exemple"</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>16</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="359">iconcollection ""</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>17</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="360">collectionextra ""</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>18</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="361">.document:text "documents"</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="362">La ligne 3 indique si la collection sera accessible au public aprÃšs construction, et peut prendre les valeurs true (valeur par dÃ©faut, qui signifie que la collection sera publiquement disponible), ou false (qui signifie que cela ne sera pas le cas). C'est utile lorsque l'on construit des collections pour tester le logiciel, ou pour usage personnel. La ligne 4 indique si la collection est une version bÃªta ou non (la valeur par dÃ©faut ici aussi est true, ce qui signifie que la collection est une version bÃªta).</Text>
+<Text id="363">La ligne 5 dÃ©termine les index de collection Ã  crÃ©er au moment de la construction: dans cet exemple, seul le texte du document sera indexÃ©. Il existe trois niveaux possibles d'index:<i>document</i>,<i>section</i>, et<i>paragraphe</i>(paragraph en anglais). Ils peuvent contenir les donnÃ©es au format texte (text) ou dans toute mÃ©ta-donnÃ©eÂ --Â la plus commune est le titre (Title). On spÃ©cifie un index en prÃ©cisant niveaudonnÃ©es. Par exemple, pour inclure Ã©galement un index des titres de sections, il faudrait remplacer la ligne 5 par indexes documenttext sectionTitle. On inclut plusieurs types de donnÃ©es dans le mÃªme index en les sÃ©parant par des virgules. Pour crÃ©er par exemple un index au niveau de la section de titres, de texte et de dates, il faudrait avoir en ligne 5 indexes sectiontext,Title,Date. Le defaultindex dÃ©fini en ligne 6 est l'index Ã  utiliser par dÃ©faut sur la page de recherche de la collection.</Text>
+<Text id="364">Les lignes 7 Ã  13 spÃ©cifient les greffons (plugins) Ã  utiliser lors de la conversion de documents vers le format d'archivage de Greenstone et lors de la construction de collections depuis des fichiers d'archives. La sectionÂ <CrossRef target="Section" ref="plugins"/> dÃ©taille les greffons disponibles. L'ordre dans lequel les greffons sont listÃ©s est l'ordre dans lequel ils sont appliquÃ©s sur chaque document. DÃšs qu'un greffon a Ã©tÃ© capable de traiter un document, les suivants de la liste ne sont pas appelÃ©s.</Text>
+<Text id="365">La ligne 14 spÃ©cifie qu'il faudra crÃ©er une liste alphabÃ©tique des titres Ã  des fins de navigation. Les structures de navigation sont construites par des Â«classificateursÂ». La sectionÂ <CrossRef target="Section" ref="classifiers"/> dÃ©taille les classificateurs et leurs possibilitÃ©s.</Text>
+<Text id="366">Les lignes 15 Ã  18 servent Ã  spÃ©cifier les mÃ©ta-donnÃ©es au niveau de la collection. L'attribut collectionname dÃ©finit la forme longue du nom de la collection, qui sera utilisÃ©e en tant que Â«titreÂ» pour le navigateur web. L'attribut collectionicon donne l'URL de l'icone de la collection. Si comme ligne 18 on spÃ©cifie un index, la chaÃ®ne suivante sera affichÃ©e comme le nom de cet index sur la page de recherche de la collection. Une mÃ©ta-donnÃ©e au niveau de la collection particuliÃšrement importante est collectionextra, qui fournit un texte, entourÃ© d'apostrophes doubles, dÃ©crivant la collection. Il servira de texte pour le paragraphe Â«Ã  proposÂ». On peut fournir diffÃ©rentes versions de l'attribut collectionextra pour diffÃ©rentes langues d'interface en ajoutant une spÃ©cification de langue entre crochets. Par exemple, </Text>
+<Indented>
+<Text id="367">collectionmeta collectionextra "collection description"</Text>
+</Indented>
+<Indented>
+<Text id="368">collectionmeta collectionextra [l=fr] "description en franÃ§ais"</Text>
+</Indented>
+<Indented>
+<Text id="369">collectionmeta collectionextra [l=mi] "description en maori"</Text>
+</Indented>
+<Text id="370">Si la langue d'interface est positionnÃ©e Ã  Â«frÂ» ou Â«miÂ», la version appropriÃ©e de la description sera affichÃ©e. Pour d'autres langues c'est la version par dÃ©faut qui apparaÃ®tra. </Text>
+<Text id="371">Ce fichier de configuration de collection simple ne fournit aucun exemple de chaÃ®ne de formatage, ni des possibilitÃ©s de sous-collection et de langue proposÃ©es par le fichier de configuration. Les chaÃ®nes de format seront couvertes plus en dÃ©tail dans la sectionÂ <CrossRef target="Section" ref="formatting_greenstone_output"/>, mais nous traiterons des sous-collections et des langues ici-mÃªme.</Text>
+<Subsection id="subcollections">
+<Title>
+<Text id="372">Sous-collections</Text>
+</Title>
+<Content>
+<Text id="373">Greenstone permet de dÃ©finir des sous-collections et de construire des index sÃ©parÃ©s pour chacune d'entre elles. Une collection comprend par exemple un sous-ensemble important de documents appelÃ© Food and Nutrition Bulletin (bulletin de la nourriture et de la nutrition). Nous l'utiliserons en tant qu'exemple.</Text>
+<Text id="374">Cette collection compte trois index, tous trois au niveau de la section: le premier pour toute la collection, le deuxiÃšme pour le Food and Nutrition Bulletin, et le troisiÃšme pour les documents restants. On peut lire ci-aprÃšs les lignes concernÃ©es du fichier de configuration de collection:</Text>
+<CodeLine>indexes                           section:text</CodeLine>
+<CodeLine>subcollection               fn "Title/^Food and Nutrition Bulletin/i "</CodeLine>
+<CodeLine>subcollection               other "!Title/^Food and Nutrition Bulletin/i "</CodeLine>
+<CodeLine>indexsubcollections fn   other   fn,other</CodeLine>
+<Text id="375">Les lignes deux et trois dÃ©finissent des sous-collections appelÃ©es fn, qui contiendra les documents du Food and Nutrition Bulletin, et other, qui contiendra les documents restants. Le troisiÃšme champ de ces dÃ©finitions est une expression rationnelle de Perl qui identifie ces sous-ensembles en utilisant la mÃ©ta-donnÃ©e Title: on recherche des titres qui commencent par Food and Nutrition Bulletin dans le premier cas, et les titres qui ne commencent pas ainsi dans le second (remarquez le "!" de nÃ©gation). L'i final rend la reconnaissance de motif indÃ©pendante de la casse: majuscules et minuscules seront confondues. Le champ de mÃ©ta-donnÃ©es, qui dans le cas prÃ©sent est Title, peut Ãªtre n'importe quel champ valide, ou Filename (nom de fichier) pour reconnaÃ®tre le nom de fichier original du document. La quatriÃšme ligne, indexsubcollections, spÃ©cifie trois index: un pour la collection fn, un pour la sous-collection other, et le troisiÃšme pour les deux sous-collections (c'est-Ã -dire pour tous les documents). Remarquez que si deux entrÃ©es avaient Ã©tÃ© spÃ©cifiÃ©es sur la premiÃšre ligne, indexes, le nombre total d'index gÃ©nÃ©rÃ©s aurait Ã©tÃ© de six et non pas de trois.</Text>
+<Text id="376">Si une collection contient des documents dans des langues diffÃ©rentes, on peut construire des index sÃ©parÃ©s pour chaque langue. La langue est une mÃ©ta-donnÃ©e; les valeurs sont spÃ©cifiÃ©es Ã  l'aide des codes en deux lettres du standard ISOÂ 639 reprÃ©sentant les noms des languesÂ --Â par exemple, en est l'anglais, fr le franÃ§ais, zh le chinois, et mi le maori. Ãtant donnÃ© que l'on peut spÃ©cifier des valeurs de mÃ©ta-donnÃ©es au niveau de la section, on peut avoir certaines portions de documents dans des langues diffÃ©rentes.</Text>
+<Text id="377">Si par exemple le fichier de configuration contenait</Text>
+<CodeLine>indexes section:text section:Title document:text paragraph:text</CodeLine>
+<CodeLine>languages en zh mi</CodeLine>
+<Text id="378">les index de texte de sections, de titres de sections, de texte de document et de texte de paragraphe seraient crÃ©Ã©s en anglais, en chinois, et en maoriÂ --Â pour un total de douze index. Si on ajoute quelques sous-collections, voilÃ  qui augmente d'autant le nombre d'index, et d'une multiplication! Il faut prendre garde Ã  la surenchÃšre des index.</Text>
+<Text id="379">(On pourrait obtenir une telle spÃ©cification d'index avec subcollection plutÃŽt qu'avec la fonctionnalitÃ© languages. Mais la syntaxe excluant la crÃ©ation de sous-collections de sous-collections, il serait alors impossible d'indexer chaque langue sÃ©parÃ©ment dans chaque sous-collection.)</Text>
+</Content>
+</Subsection>
+<Subsection id="cross-collection_searching">
+<Title>
+<Text id="380">Recherche inter-collections</Text>
+</Title>
+<Content>
+<Text id="381">Greenstone propose une fonctionnalitÃ© de recherche transverse aux collections, qui permet d'effectuer une recherche parmi plusieurs collections Ã  la fois, et de combiner les rÃ©sultats en coulisses de maniÃšre Ã  donner Ã  l'utilisateur l'impression qu'il a menÃ© sa recherche dans une unique collection unifiÃ©e. On peut rechercher tout sous-ensemble de collections: la page de PrÃ©fÃ©rences laisse choisir quelles collections inclure dans les recherches.</Text>
+<Text id="382">On active la recherche inter-collections par une ligne</Text>
+<CodeLine>supercollection col _1 col _2 âŠ.</CodeLine>
+<Text id="383">oÃ¹ les collections impliquÃ©es sont appelÃ©es col_1, col_2, ... La mÃªme ligne devrait apparaÃ®tre dans les fichiers de configuration de toutes les collections impliquÃ©es.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="getting_the_most_out_of_your_documents">
+<Title>
+<Text id="384">Exploitez vos documents au maximum</Text>
+</Title>
+<Content>
+<Text id="385">On peut individualiser les collections pour rendre accessibles les informations qu'elles contiennent de diverses maniÃšres. Le prÃ©sent chapitre dÃ©crit la maniÃšre dont Greenstone extrait l'information des documents et la prÃ©sente Ã  l'utilisateur: le traitement des documents (sectionÂ <CrossRef target="Section" ref="plugins"/>), les structures de classification (sectionÂ <CrossRef target="Section" ref="classifiers"/>), et les outils d'interface utilisateur (sectionsÂ <CrossRef target="Section" ref="formatting_greenstone_output"/> etÂ <CrossRef target="Section" ref="controlling_the_greenstone_user_interface"/>).</Text>
+<Section id="plugins">
+<Title>
+<Text id="386">Greffons (plugins)</Text>
+</Title>
+<Content>
+<Text id="387">Les greffons analysent les documents importÃ©s et en extraient les mÃ©ta-donnÃ©es. Par exemple, le greffon HTML convertit des pages HTML en format d'archivage de Greenstone et extrait les mÃ©ta-donnÃ©es explicites dans le format de documentÂ --Â telles que les titres, entourÃ©s de balises &lt;title&gt;&lt;/title&gt;. </Text>
+<Text id="388">Les greffons sont Ã©crits en Perl. Ils sont tous inspirÃ©s d'un greffon de base appelÃ© BasPlug, qui effectue les opÃ©rations partout nÃ©cessaires, telles que crÃ©er un nouveau document d'archive de Greenstone avec lequel travailler, affecter un identifiant d'objet (OID), et gÃ©rer les sections d'un document. Les greffons se trouvent dans le rÃ©pertoire perllib/plugins.</Text>
+<Text id="389">Pour en savoir plus sur un greffon particulier, tapez<i>pluginfo.pl nom-de-greffon</i>Ã  l'invite de commandes (il vous faudra d'abord invoquer le script de rÃ©glages appropriÃ© si vous ne l'avez pas encore fait, et sous Windows il vous faudra taper perl -S pluginfo.pl plugin-name si votre environnement n'est pas rÃ©glÃ© pour associer les fichiers se terminant en .pl Ã  l'interprÃ©teur Perl). Ceci affichera des informations relatives au greffon Ã  l'Ã©cranÂ --Â les options spÃ©cifiques qu'il accepte, et quelles options gÃ©nÃ©rales sont autorisÃ©es.</Text>
+<Text id="390">On peut facilement Ã©crire de nouveaux greffons qui traitent des formats de documents non couverts par les greffons existants, mettent les documents en forme d'une maniÃšre particuliÃšre, ou extraient un nouveau type de mÃ©ta-donnÃ©es.</Text>
+<Subsection id="general_options">
+<Title>
+<Text id="391">Options gÃ©nÃ©rales</Text>
+</Title>
+<Content>
+<Text id="392">La tableÂ <CrossRef target="Table" ref="options_applicable_to_all_plugins"/> montre les options acceptÃ©es par tout greffon hÃ©ritant de BasPlug.</Text>
+<Table id="options_applicable_to_all_plugins">
+<Title>
+<Text id="393">Options valables pour tous les greffons</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<CodeLine><i>input_encoding</i></CodeLine>
+</th>
+<th width="397">
+<Text id="394">Encodage de caractÃšres utilisÃ© dans les documents source. Par dÃ©faut Greenstone devine automatiquement l'encodage utilisÃ© dans chaque document. Il est parfois utile cependant de positionner cette valeur: si par exemple vous savez que tous vos documents sont en ASCII brut, positionner l'encodage en entrÃ©e Ã  la valeur<i>ascii</i>augmentera considÃ©rablement la vitesse d'import et de construction de votre collection. Il existe de nombreuses valeurs possibles; tapez<i>pluginfo.pl BasPlug</i>pour en obtenir la liste complÃšte.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>default_encoding</i></CodeLine>
+</th>
+<th width="397">
+<Text id="395">L'encodage utilisÃ© si<i>input_encoding</i>vaut<i>auto</i>et que la dÃ©tection automatique d'encodage Ã©choue.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>process_exp</i></CodeLine>
+</th>
+<th width="397">
+<Text id="396">Une expression rationnelle de Perl Ã  utiliser sur les noms de fichier (pour localiser par exemple un certain type d'extension de fichier). Ceci dicte les fichiers qu'un greffon doit traiter. Chaque greffon dispose d'une valeur par dÃ©faut (la valeur par dÃ©faut de<i>HTMLPlug</i>est<i>(?i).html?</i>âc'est-Ã -dire tout fichier d'extension<i>.htm</i>ou<i>.html</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>block_exp</i></CodeLine>
+</th>
+<th width="397">
+<Text id="397">Une expression rationnelle de Perl Ã  utiliser sur les noms de fichier qui ne doivent pas Ãªtre passÃ©s aux greffons suivants. Ceci peut Ã©viter l'apparition d'ennuyeux messages d'erreur qui ne vous intÃ©ressent pas. Certains greffons disposent d'expressions de blocage par dÃ©fautâpar exemple, le greffon<i>HTMLPlug</i>bloque les fichiers d'extensions<i>.gif</i>,<i>.jpg</i>,<i>.jpeg</i>,<i>.png</i>,<i>.rtf</i>and<i>.css</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>cover_image</i></CodeLine>
+</th>
+<th width="397">
+<Text id="398">Recherche un fichier<i>.jpg</i>(portant le mÃªme nom que le fichier en cours de traitement) et l'associe au document en tant qu'image de couverture.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_acronyms</i></CodeLine>
+</th>
+<th width="397">
+<Text id="399">Extrait les acronymes des documents et les ajoute en tant que mÃ©ta-donnÃ©es aux documents d'archive de Greenstone correspondants.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>markup_acronyms</i></CodeLine>
+</th>
+<th width="397">
+<Text id="400">Ajoute des informations sur les acronymes dans le texte du document.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_language</i></CodeLine>
+</th>
+<th width="397">
+<Text id="401">Identifie la langue de chaque document et l'associe en tant que mÃ©ta-donnÃ©e. Ceci est automatique si l'option <i>input_encoding</i>a la valeur<i>auto</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>default_language</i></CodeLine>
+</th>
+<th width="397">
+<Text id="402">Si l'extraction automatique de la langue Ã©choue, la mÃ©ta-donnÃ©e de langue est positionnÃ©e Ã  cette valeur.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>first</i></CodeLine>
+</th>
+<th width="397">
+<Text id="403">Extrait une liste sÃ©parÃ©e par des virgules de la premiÃšre portion de texte et l'ajoute en tant que mÃ©ta-donnÃ©e <i>FirstNNN</i>(souvent utilisÃ© en remplacement de<i>Title</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_email</i></CodeLine>
+</th>
+<th width="397">
+<Text id="404">Extrait les adresses de courrier Ã©lectronique et les ajoute aux mÃ©ta-donnÃ©es du document.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_date</i></CodeLine>
+</th>
+<th width="397">
+<Text id="405">Extrait les dates relatives au contenu de documents historiques et les ajoute en tant que mÃ©ta-donnÃ©es de type<i>Coverage</i>.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="document_processing_plugins">
+<Title>
+<Text id="406">Greffons de traitement de documents</Text>
+</Title>
+<Content>
+<Table id="greenstone_plugins">
+<Title>
+<Text id="407">Greffons (<i>plugins</i>) de Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="60"/>
+<th width="72"/>
+<th width="236">
+<Text id="408"><b>Purpose</b></Text>
+</th>
+<th width="85">
+<Text id="409"><b>File types</b></Text>
+</th>
+<th width="76">
+<Text id="410"><b>Ignores files</b></Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="411"><b>GÃ©nÃ©raux</b></Text>
+</th>
+<th width="72">
+<Text id="412"><i>ArcPlug</i></Text>
+</th>
+<th width="236">
+<Text id="413">Traite les fichiers mentionnÃ©s dans le fichier<i>archives.inf</i>, qui est utilisÃ© comme vecteur de communication entre les processus d'import et de construction. Doit Ãªtre inclus (sauf si<i>import.pl</i>n'est pas utilisÃ©).</Text>
+</th>
+<th width="85">
+<Text id="414"><i>â</i></Text>
+</th>
+<th width="76">
+<Text id="415"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="416"><i>RecPlug</i></Text>
+</th>
+<th width="236">
+<Text id="417">Explore rÃ©cursivement une structure arborescente de rÃ©pertoire en regardant si les fichiers sont des rÃ©pertoires et si c'est le cas, en insÃ©rant tous les fichiers du rÃ©pertoire dans le pipe-line des greffons. Affecte les mÃ©ta-donnÃ©es si l'option<i>âuse_metadata_files</i>est positionnÃ©e et si des fichiers<i>metadata.xml</i>sont prÃ©sents.</Text>
+</th>
+<th width="85">
+<Text id="418"><i>â</i></Text>
+</th>
+<th width="76">
+<Text id="419"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="420"><i>GAPlug</i></Text>
+</th>
+<th width="236">
+<Text id="421">Traite les fichiers d'archive de Greenstone gÃ©nÃ©rÃ©s par le programme<i>import.pl.</i>Doit Ãªtre inclus (sauf si <i>import.pl</i>n'est pas utilisÃ©).</Text>
+</th>
+<th width="85">
+<Text id="422"><i>.xml</i></Text>
+</th>
+<th width="76">
+<Text id="423"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="424">TEXTPlug</Text>
+</th>
+<th width="236">
+<Text id="425">Traite le texte brut en le plaÃ§ant entre balises<i>&lt;pre&gt; &lt;/pre&gt;</i>(et en le traitant comme s'il Ã©tait prÃ©-formatÃ©).</Text>
+</th>
+<th width="85">
+<Text id="426"><i>.txt, .text</i></Text>
+</th>
+<th width="76">
+<Text id="427"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="428"><i>HTMLPlug</i></Text>
+</th>
+<th width="236">
+<Text id="429">Traite le HTML en remplaÃ§ant les liens hypertexte de maniÃšre appropriÃ©e. Si le document cible d'un lien n'est pas dans la collection, une page intermÃ©diaire est insÃ©rÃ©e, avertissant l'utilisateur qu'il quitte la collection. Extrait les mÃ©ta-donnÃ©es dÃ©jÃ  disponibles telles que<i>Title</i>.</Text>
+</th>
+<th width="85">
+<Text id="430"><i>.htm, .html, .cgi, .php, .asp, .shm, .shtml</i></Text>
+</th>
+<th width="76">
+<Text id="431"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="432"><i>WordPlug</i></Text>
+</th>
+<th width="236">
+<Text id="433">Traite les fichiers au format Microsoft Word, en extrayant l'auteur et le titre s'ils sont disponibles, et en laissant les diagrammes et les images aux endroits appropriÃ©s. Les outils de conversion utilisÃ©s par ce greffon produisent parfois du HTML mal mis en forme, et nous recommandons que vous fournissiez les documents originaux Ã  des fins de visualisation lors de la construction de collections de fichiers Word. Le texte extrait est cependant convenable Ã  des fins de recherche et d'indexation.</Text>
+</th>
+<th width="85">
+<Text id="434"><i>.doc</i></Text>
+</th>
+<th width="76">
+<Text id="435"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="436"><i>PDFPlug</i></Text>
+</th>
+<th width="236">
+<Text id="437">Traite les documents PDF, en extrayant la premiÃšre ligne de texte en tant que titre. Le programme<i>pdftohtml</i>ne parvient pas Ã  traiter certains fichiers PDF. Le processus de conversion prend un temps exponentiellement long, et on voit souvent apparaÃ®tre Ã  l'Ã©cran un message traitant de ce processus. Si cela se produit, la seule solution que nous puissions proposer est d'ÃŽter le document concernÃ© de la collection et de recommencer le processus d'import.</Text>
+</th>
+<th width="85">
+<Text id="438"><i>.pdf</i></Text>
+</th>
+<th width="76">
+<Text id="439"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="440"><i>PSPlug</i></Text>
+</th>
+<th width="236">
+<Text id="441">Traite les documents PostScript, en extrayant optionnellement les mÃ©ta-donnÃ©es de date, de titre, et de numÃ©ro de page.</Text>
+</th>
+<th width="85">
+<Text id="442"><i>.ps</i></Text>
+</th>
+<th width="76">
+<Text id="443"><i>.eps</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="444"><i>EMAILPlug</i></Text>
+</th>
+<th width="236">
+<Text id="445">Traite les messages de courrier Ã©lectronique, en reconnaissant l'auteur, le thÃšme, la date, etc. Ce greffon ne traite pas encore correctement les courriers Ã©lectroniques encodÃ©s au format MIMEâbien que lisibles, ils ont souvent un aspect Ã©trange.</Text>
+</th>
+<th width="85">
+<Text id="446">Doit se terminer par des chiffres ou des chiffres suivis de<i>.Email</i></Text>
+</th>
+<th width="76">
+<Text id="447"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="448"><i>BibTexPlug</i></Text>
+</th>
+<th width="236">
+<Text id="449">Traite les fichiers de bibliographie au format<i>BibTex</i>.</Text>
+</th>
+<th width="85">
+<Text id="450"><i>.bib</i></Text>
+</th>
+<th width="76">
+<Text id="451"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="452"><i>ReferPlug</i></Text>
+</th>
+<th width="236">
+<Text id="453">Traite les fichiers de bibliographie au format<i>refer</i>.</Text>
+</th>
+<th width="85">
+<Text id="454"><i>.bib</i></Text>
+</th>
+<th width="76">
+<Text id="455"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="456"><i>SRCPlug</i></Text>
+</th>
+<th width="236">
+<Text id="457">Traite les fichiers de code source</Text>
+</th>
+<th width="85">
+<Text id="458"><i>Makefile, Readme, .c, .cc, .cpp, .h, .hpp, .pl, .pm, .sh</i></Text>
+</th>
+<th width="76">
+<Text id="459"><i>.o, .obj, .a, .so, .dll</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="460"><i>ImagePlug</i></Text>
+</th>
+<th width="236">
+<Text id="461">Traite les fichiers d'images pour crÃ©er une bibliothÃšque d'images. Ne fonctionne que sous Unix.</Text>
+</th>
+<th width="85">
+<Text id="462"><i>.jpeg, .jpg, .gif, .png, .bmp, .xbm, .tif, .tiff</i></Text>
+</th>
+<th width="76">
+<Text id="463"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="464"><i>SplitPlug</i></Text>
+</th>
+<th width="236">
+<Text id="465">Ã l'instar de BasPlug et de ConvertToPlug, il ne faut pas appelÃ© ce greffon directement; il faut plutÃŽt que des greffons qui ont besoin de traiter des fichiers contenant plusieurs documents en hÃ©ritent.</Text>
+</th>
+<th width="85">
+<Text id="466"><i>â</i></Text>
+</th>
+<th width="76">
+<Text id="467"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="468"><i>FOXPlug</i></Text>
+</th>
+<th width="236">
+<Text id="469">Traite les fichiers dbt de FoxBASE</Text>
+</th>
+<th width="85">
+<Text id="470"><i>.dbt, .dbf</i></Text>
+</th>
+<th width="76">
+<Text id="471"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="472"><i>ZIPPlug</i></Text>
+</th>
+<th width="236">
+<Text id="473">DÃ©compacte les fichiers<i>gzip</i>,<i>bzip</i>,<i>zip</i>, et<i>tar</i>files, pour peu que les outils GNU appropriÃ©s soient disponibles.</Text>
+</th>
+<th width="85">
+<Text id="474"><i>.gzip, .bzip, .zip, .tar, .gz, .bz, .tgz, .taz</i></Text>
+</th>
+<th width="76">
+<Text id="475"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="476"><b>Propres Ã  une collection</b></Text>
+</th>
+<th width="72">
+<Text id="477"><i>PrePlug</i></Text>
+</th>
+<th width="236">
+<Text id="478">Traite la sortie HTML en utilisant PRESCRIPT, divisant les documents en pages pour la collection <i>Computer Science Technical Reports</i>.</Text>
+</th>
+<th width="85">
+<Text id="479"><i>.html, .html.gz</i></Text>
+</th>
+<th width="76">
+<Text id="480"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="481"><i>GBPlug</i></Text>
+</th>
+<th width="236">
+<Text id="482">Traite le texte Ã©lectronique du projet Gutenbergâqui comprend des informations de titre saisies manuellement.</Text>
+</th>
+<th width="85">
+<Text id="483"><i>.txt.gz, .html, .htm</i></Text>
+</th>
+<th width="76">
+<Text id="484"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="485"><i>TCCPlug</i></Text>
+</th>
+<th width="236">
+<Text id="486">Traite les documents de courrier Ã©lectronique de la collection<i>Computists' Weekly</i>(l'hebdomadaire des informaticiens) </Text>
+</th>
+<th width="85">
+<Text id="487">Doit commencer par<i>tcc</i>ou<i>cw</i></Text>
+</th>
+<th width="76">
+<Text id="488"><i>â</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="489">Les greffons de traitement de documents sont utilisÃ©s par le logiciel de construction de collection pour analyser chaque document source d'une maniÃšre qui dÃ©pend de son format. Le fichier de configuration d'une collection liste tous les greffons utilisÃ©s lors de sa construction. Lors de l'opÃ©ration d'import, chaque fichier ou chaque rÃ©pertoire est passÃ© tour Ã  tour Ã  tous les greffons jusqu'Ã  ce qu'un greffon soit trouvÃ© qui puisse traiter l'objetÂ --Â c'est pourquoi les premiers greffons listÃ©s ont la prioritÃ© sur des greffons apparaissant plus tard dans la liste. Si aucun greffon ne peut traiter le fichier, un avertissement est affichÃ© (sur la sortie d'erreur standard) et le traitement passe au fichier suivant (c'est pourquoi l'option block_exp peut Ãªtre utileÂ --Â pour Ã©viter ces messages d'erreur dans le cas de fichiers qui sont peut-Ãªtre prÃ©sents mais n'ont pas besoin d'Ãªtre traitÃ©s). Lors de la construction, on utilise la mÃªme procÃ©dure, mais c'est le rÃ©pertoire archives qui est traitÃ© en lieu et place du rÃ©pertoire import.</Text>
+<Text id="490">Les greffons standard de Greenstone sont listÃ©s tableÂ <CrossRef target="Table" ref="greenstone_plugins"/>. Il est nÃ©cessaire d'utiliser un processus rÃ©cursif pour traverser des hiÃ©rarchies de rÃ©pertoires. Bien que les programmes d'import et de construction n'effectuent pas de rÃ©cursion explicite, certains greffons provoquent une rÃ©cursion indirecte en passant des noms de fichiers ou de rÃ©pertoires dans le pipe-line des greffons. Par exemple, la maniÃšre habituelle d'opÃ©rer rÃ©cursivement Ã  travers une hiÃ©rarchie de rÃ©pertoire est de spÃ©cifier RecPlug, qui travaille exactement ainsi. S'il est prÃ©sent, il devrait Ãªtre en derniÃšre position dans le pipe-line. Seuls les deux premiers greffons de la tableÂ <CrossRef target="Table" ref="greenstone_plugins"/> provoquent une rÃ©cursion indirecte.</Text>
+<Text id="491">Certains greffons sont Ã©crits pour des collections spÃ©cifiques, avec un format de document que l'on ne trouve nulle part ailleurs, tel que le texte Ã©lectronique utilisÃ© dans la collection Gutenberg<FootnoteRef id="2"/>. Ces greffons spÃ©cifiques Ã  une collection se trouvent dans le rÃ©pertoire perllib/plugins de la collection. On peut utiliser des greffons spÃ©cifiques Ã  une collection pour remplacer des greffons gÃ©nÃ©raux portant le mÃªme nom, qui ne seront alors pas appelÃ©s.</Text>
+<Text id="492">Certains greffons de traitement de documents utilisent des programmes externes qui analysent des formats de fichiers propriÃ©taires spÃ©cifiquesÂ --Â tel que par exemple Microsoft WordÂ --Â et les transforment en texte brut ou en HTML. Un greffon gÃ©nÃ©ral appelÃ© ConvertToPlug invoque le programme de conversion appropriÃ© et en passe le rÃ©sultat aux greffons TEXTPlug ou HTMLPlug. Nous dÃ©crirons cette opÃ©ration plus en dÃ©tail sous peu.</Text>
+<Text id="493">Certains greffons disposent d'options individuelles, qui les contrÃŽlent de maniÃšre plus fine que ce que permettent les options gÃ©nÃ©rales. C'est la tableÂ <CrossRef target="Table" ref="plugin-specific_options"/> qui dÃ©crit ces options individuelles.</Text>
+<Table id="plugin-specific_options">
+<Title>
+<Text id="494">Options propres aux greffons</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="495"><b>Option</b></Text>
+</th>
+<th width="265">
+<Text id="496"><b>But</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="497"><i>HTMLPlug</i></Text>
+</th>
+<th width="132">
+<Text id="498"><i>nolinks</i></Text>
+</th>
+<th width="265">
+<Text id="499">Ne piÃšge pas de liens dans la collection. Ceci accÃ©lÃšre les processus d'import et de construction, mais tout lien contenu dans la collection sera cassÃ©.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="500"><i>description_tags</i></Text>
+</th>
+<th width="265">
+<Text id="501">InterprÃšte les fichiers de documents balisÃ©s comme dans la sous-section 2.1.5.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="502"><i>keep_head</i></Text>
+</th>
+<th width="265">
+<Text id="503">N'enlÃšve pas les en-tÃªtes HTML.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="504"><i>no_metadata</i></Text>
+</th>
+<th width="265">
+<Text id="505">Ne recherche aucune mÃ©ta-donnÃ©e (ceci peut accÃ©lÃ©rer les processus d'import et de construction).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="506"><i>metadata_fields</i></Text>
+</th>
+<th width="265">
+<Text id="507">Prend une liste sÃ©parÃ©e par des virgules de types de mÃ©ta-donnÃ©es Ã  extraire (dont la valeur par dÃ©faut est<i>Title</i>).Pour changer le nom des mÃ©ta-donnÃ©es dans le fichier d'archive de Greenstone, utilisez<i>balise&lt;nouveaunom&gt;</i>oÃ¹<i>balise</i>est la balise HTML recherchÃ©e et<i>nouveaunom</i>son nouveau nom.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="508"><i>hunt_creator_metadata</i></Text>
+</th>
+<th width="265">
+<Text id="509">Trouve autant de mÃ©ta-donnÃ©es que possible relatives Ã  la paternitÃ© du document et les consigne dans le document d'archive de Greenstone sous la forme de mÃ©ta-donnÃ©es<i>Creator</i>. Il faut aussi inclure<i>Creator</i>avec l'option<i>metadata_fields</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="510"><i>file_is_url</i></Text>
+</th>
+<th width="265">
+<Text id="511">Utilisez cette option si un programme de miroir web a Ã©tÃ© utilisÃ© pour crÃ©er la structure des documents Ã  importer.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="512"><i>assoc_files</i></Text>
+</th>
+<th width="265">
+<Text id="513">Donne une expression rationnelle de Perl qui dÃ©crit les types de fichiers Ã  traiter comme des fichiers associÃ©s. Les types par dÃ©faut sont<i>.jpg</i>,<i>.jpeg</i>,<i>.gif</i>,<i>.png</i>,<i>.css</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="514"><i>rename_assoc_files</i></Text>
+</th>
+<th width="265">
+<Text id="515">Change le nom des fichiers associÃ©s aux documents. Lors de ce processus la structure de rÃ©pertoire de tout fichier associÃ© rÃ©trÃ©cira beaucoup (ce qui est utile s'il faut stocker la collection dans un espace disque limitÃ©).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="516"><i>HTMLPlug</i>et<br/>
+<i>TEXTPlug</i></Text>
+</th>
+<th width="132">
+<Text id="517"><i>title_sub</i></Text>
+</th>
+<th width="265">
+<Text id="518">Expression de substitution Perl pour modifier les titres.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="519"><i>PSPlug</i></Text>
+</th>
+<th width="132">
+<Text id="520"><i>extract_date</i></Text>
+</th>
+<th width="265">
+<Text id="521">Extrait la date de crÃ©ation de l'en-tÃªte PostScript et la stocke en tant que mÃ©ta-donnÃ©e.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="522"><i>extract_title</i></Text>
+</th>
+<th width="265">
+<Text id="523">Extrait le titre du document de l'en-tÃªte PostScript et le stocke en tant que mÃ©ta-donnÃ©e de titre.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="524"><i>extract_pages</i></Text>
+</th>
+<th width="265">
+<Text id="525">Extrait les numÃ©ros de pages du document PostScript et les ajoute aux sections appropriÃ©es en tant que mÃ©ta-donnÃ©es sous la balise<i>Pages</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="526"><i>RecPlug</i></Text>
+</th>
+<th width="132">
+<Text id="527"><i>use_metadata_files</i></Text>
+</th>
+<th width="265">
+<Text id="528">Affecte des mÃ©ta-donnÃ©es Ã  partir d'un fichier tel que dÃ©crit dans la sous-section 2.1.4.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="529"><i>ImagePlug</i></Text>
+</th>
+<th width="132">
+<Text id="530">Diverses options</Text>
+</th>
+<th width="265">
+<Text id="531">Voir<i>ImagePlug.pm.</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="532"><i>SRCPlug</i></Text>
+</th>
+<th width="132">
+<Text id="533"><i>remove_prefix</i></Text>
+</th>
+<th width="265">
+<Text id="534">Donne une expression rationnelle de Perl d'un motif Ã  chercher en tÃªte et qu'il faut ÃŽter du nom de fichier. Le comportement par dÃ©faut est d'ÃŽter tout le chemin.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="plugins_to_import_proprietary_formats">
+<Title>
+<Text id="535">Greffons d'import de formats propriÃ©taires</Text>
+</Title>
+<Content>
+<Text id="536">Les formats propriÃ©taires posent des problÃšmes difficiles pour tout systÃšme de bibliothÃšque numÃ©rique. Bien qu'ils soient parfois documentÃ©s, ils sont susceptibles de changer sans prÃ©avis, et il est difficile de suivre le rythme des changements. Greenstone a fait le choix d'utiliser des outils de conversion publiÃ©s selon les termes de la GPL (licence publique gÃ©nÃ©rale de GNU) par des gens focalisÃ©s sur telle ou telle tÃ¢che de conversion. Les outils pour convertir les formats Word et PDF sont inclus dans le rÃ©pertoire packages. Tous convertissent des documents au format texte ou au format HTML. Les greffons HTMLPlug et TEXTPlug prennent ensuite la relÃšve et convertissent ce rÃ©sultat intermÃ©diaire au format d'archivage de Greenstone. C'est ConvertToPlug qui est utilisÃ© pour inclure les outils de conversion. BasPlug n'est jamais appelÃ© directement, mais les greffons traitant des formats particuliers en hÃ©ritent, comme illustrÃ© figureÂ <CrossRef target="Figure" ref="plugin_inheritance_hierarchy"/>. ConvertToPlug utilise le systÃšme d'hÃ©ritage dynamique de Perl pour hÃ©riter soit de TEXTPlug soit de HTMLPlug, selon le format dans lequel le document source a Ã©tÃ© converti.</Text>
+<Figure id="plugin_inheritance_hierarchy">
+<Title>
+<Text id="537">HiÃ©rarchie d'hÃ©ritage des greffons (plugins)</Text>
+</Title>
+<File width="229" height="193" url="images/Dev_Fig_9.png"/>
+</Figure>
+<Text id="538">Quand ConvertToPlug reÃ§oit un document, il appelle gsConvert.pl (qui se trouve dans le rÃ©pertoire GSDLHOME/bin/script) pour invoquer l'outil de conversion appropriÃ©. AprÃšs conversion, le document est renvoyÃ© vers le greffon ConvertToPlug, qui invoque ensuite le greffon texte ou HTML, selon les cas. Tout greffon hÃ©ritant de ConvertToPlug dispose d'une option convert_to (convertit vers), dont l'argument est soit text (texte) soit html, pour spÃ©cifier le format intermÃ©diaire prÃ©fÃ©rÃ©. Le format texte est plus rapide, mais le format HTML rend mieux en gÃ©nÃ©ral, et comprend des images.</Text>
+<Text id="539">Il existe parfois plusieurs outils de conversion pour traiter un format particulier, et le programme gsConvert peut en essayer plusieurs sur un document donnÃ©. Par exemple, l'outil habituel de conversion du format Work, wvWare, ne traite pas les formats antÃ©rieurs Ã  Word 6, et c'est un programme appelÃ© AnyToHTML, qui se contente d'extraire toutes les chaÃ®nes de texte qu'il peut trouver, qui est appelÃ© pour convertir les documents au format Word 5.</Text>
+<Text id="540">Voici les Ã©tapes nÃ©cessaires pour ajouter un nouvel outil externe de conversion de document:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="541">Installez le nouvel outil de conversion de maniÃšre qu'il soit accessible Ã  Greenstone (placez-le dans le rÃ©pertoire packages).</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="542">Modifiez gsConvert.pl pour utiliser le nouvel outil de conversion. Il s'agit d'ajouter une nouvelle clause Ã  l'instruction if de la fonction main, et d'ajouter une fonction qui appelle l'outil de conversion.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="543">Ãcrivez un greffon de premier niveau qui hÃ©rite de ConvertToPlug pour intercepter le format et le passer Ã  la suite de la chaÃ®ne.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Subsection>
+<Subsection id="assigning_metadata_from_a_file">
+<Title>
+<Text id="544">Affecter des mÃ©ta-donnÃ©es Ã  partir d'un fichier</Text>
+</Title>
+<Content>
+<Text id="545">Le greffon standard RecPlug incorpore Ã©galement une mÃ©thode pour positionner des mÃ©ta-donnÃ©es dans les documents de maniÃšre manuelle (ou automatique) Ã  partir de fichiers XML crÃ©Ã©s manuellement (ou automatiquement). Nous dÃ©taillons quelque peu ceci, de maniÃšre que vous puissiez crÃ©er des fichiers de mÃ©ta-donnÃ©es dans le format appropriÃ©. Si l'option use_metadata_files est prÃ©cisÃ©e, RecPlug utilise un fichier de mÃ©ta-donnÃ©es auxiliaire, metadata.xml. La premiÃšre partie de la figureÂ <CrossRef target="Figure" ref="xml_format"/> illustre la dÃ©finition de type de document (DTD) XML pour le format du fichier de mÃ©ta-donnÃ©es, et la deuxiÃšme partie de la figureÂ <CrossRef target="Figure" ref="xml_format_1"/> montre un exemple de fichier metadata.xml.</Text>
+<Figure id="xml_format">
+<Title>
+<Text id="546">Format XML: (a) DÃ©finition de type de document (DTD); (b) Fichier de mÃ©ta-donnÃ©es d'exemple</Text>
+<SubTitle>
+<Text id="547">(a)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;!DOCTYPE GreenstoneDirectoryMetadata [</CodeLine>
+<CodeLine>   &lt;!ELEMENT DirectoryMetadata (FileSet*)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT FileSet (FileName+,Description)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT FileName (#PCDATA)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT Description (Metadata*)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT Metadata (#PCDATA)&gt;</CodeLine>
+<CodeLine>   &lt;ATTLIST Metadata name CDATA #REQUIRED&gt;</CodeLine>
+<CodeLine>   &lt;ATTLIST Metadata mode (accumulate|override) "override"&gt;</CodeLine>
+<CodeLine>]&gt;</CodeLine>
+</Figure>
+<Figure id="xml_format_1">
+<Title>
+<Text id="548"/>
+<SubTitle>
+<Text id="549">(b)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;?xml version="1.0" ?&gt;</CodeLine>
+<CodeLine>&lt;!DOCTYPE GreenstoneDirectoryMetadata SYSTEM</CodeLine>
+<CodeLine>"http://greenstone.org/dtd/GreenstoneDirectoryMetadata/<br/>1.0/GreenstoneDirectoryMetadata.dtd"&gt;</CodeLine>
+<CodeLine>&lt;DirectoryMetadata&gt;</CodeLine>
+<CodeLine>   &lt;FileSet&gt;</CodeLine>
+<CodeLine>       &lt;FileName&gt;nugget.*&lt;/FileName&gt;</CodeLine>
+<CodeLine>       &lt;Description&gt;</CodeLine>
+<CodeLine>       &lt;Metadata name="Title"&gt;Nugget Point Lighthouse&lt;/Metadata&gt;</CodeLine>
+<CodeLine>           &lt;Metadata name="Place" mode="accumulate"&gt;Nugget Point&lt;/Metadata&gt;</CodeLine>
+<CodeLine>       &lt;/Description&gt;</CodeLine>
+<CodeLine>   &lt;/FileSet&gt;</CodeLine>
+<CodeLine>   &lt;FileSet&gt;</CodeLine>
+<CodeLine>       &lt;FileName&gt;nugget-point-1.jpg&lt;/FileName&gt;</CodeLine>
+<CodeLine>       &lt;Description&gt;</CodeLine>
+<CodeLine>           &lt;Metadata name="Title"&gt;Nugget Point Lighthouse , The Catlins &lt;/Metadata&gt;</CodeLine>
+<CodeLine>           &lt;Metadata name="Subject"&gt;Lighthouse&lt;/Metadata&gt;</CodeLine>
+<CodeLine>       &lt;/Description&gt;</CodeLine>
+<CodeLine>   &lt;/FileSet&gt;</CodeLine>
+<CodeLine>&lt;/DirectoryMetadata&gt;</CodeLine>
+</Figure>
+<Text id="550">Le fichier d'exemple contient deux structures de mÃ©ta-donnÃ©es. Dans chacune, l'Ã©lÃ©ment filename dÃ©crit les fichiers auxquels les mÃ©ta-donnÃ©es s'appliquent, sous la forme d'une expression rationnelle. &lt;FileName&gt;nugget.*&lt;/FileName&gt; indique ainsi que le premier enregistrement de mÃ©ta-donnÃ©es s'applique Ã  tous les fichiers dont le nom commence par Â«nuggetÂ»<FootnoteRef id="3"/>. Pour ces fichiers, la mÃ©ta-donnÃ©e Title vaudra Â«Phare de Nugget PointÂ».</Text>
+<Text id="551">Les Ã©lÃ©ments de mÃ©ta-donnÃ©es sont traitÃ©s dans l'ordre dans lequel ils apparaissent. La deuxiÃšme structure de la figureÂ 10 positionne la mÃ©ta-donnÃ©e Title pour le fichier nugget-point-1.jpg Ã  la valeur Â«Phare de Nugget Point, CatlinsÂ», en Ã©crasant la spÃ©cification prÃ©cÃ©dente. Elle ajoute Ã©galement un champ Subject dans les mÃ©ta-donnÃ©es.</Text>
+<Text id="552">Parfois, les mÃ©ta-donnÃ©es sont multi-valuÃ©es et les nouvelles valeurs devraient s'accumuler au lieu d'Ã©craser les prÃ©cÃ©dentes. L'attribut mode=accumulate a cet effet. Il est appliquÃ© Ã  la mÃ©ta-donnÃ©e Place (lieu) dans la premiÃšre spÃ©cification de la figureÂ 10, cette mÃ©ta-donnÃ©e sera donc multi-valuÃ©e. Pour revenir Ã  une mÃ©ta-donnÃ©e simple, Ã©crivez<i>&lt;Metadata name="Place" mode="override"&gt;Nouvelle-ZÃ©lande&lt;/Metadata&gt;</i>En fait, on peut nÃ©gliger de prÃ©ciser cette spÃ©cification de mode puisque tout Ã©lÃ©ment Ã©crase le prÃ©cÃ©dent par dÃ©faut, sauf indication contraire. Pour accumuler les mÃ©ta-donnÃ©es dans un champ particulier, il faut prÃ©ciser mode=accumulate Ã  chaque occurrence.</Text>
+<Text id="553">Quand son option use_metadata_files est activÃ©e, le greffon RecPlug recherche dans chaque rÃ©pertoire en entrÃ©e un fichier XML appelÃ© metadata.xml et applique son contenu Ã  tous les fichiers et sous-rÃ©pertoires du rÃ©pertoire courant.</Text>
+<Text id="554">Le mÃ©canisme metadata.xml instanciÃ© dans le greffon RecPlug n'est qu'une maniÃšre de spÃ©cifier des mÃ©ta-donnÃ©es pour des documents. Il est facile d'Ã©crire des greffons diffÃ©rents qui accepteront des spÃ©cifications de mÃ©ta-donnÃ©es dans des formats complÃštement diffÃ©rents.</Text>
+</Content>
+</Subsection>
+<Subsection id="tagging_document_files">
+<Title>
+<Text id="555">Baliser les fichiers de documents</Text>
+</Title>
+<Content>
+<Text id="556">Il faut souvent structurer les documents source en sections et sous-sections, et donc communiquer cette information Ã  Greenstone de maniÃšre qu'il puisse reproduire la structure hiÃ©rarchique du document. On peut aussi associer Ã  chaque section et sous-section des mÃ©ta-donnÃ©es, et en particulier un titre.</Text>
+<Text id="557">La maniÃšre la plus simple de procÃ©der est souvent d'Ã©diter les fichiers source, tout simplement. Le greffon HTML dispose d'un option description_tags qui traite les balises dans le texte comme suit:</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>   &lt;Description&gt;</CodeLine>
+<CodeLine>       &lt;Metadata name="Title"&gt; Realizing human rights for poor people: Strategies for achieving the international development targets&lt;/Metadata&gt;</CodeLine>
+<CodeLine>   &lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="558"><i>(texte de la section)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="559">On utilise les marqueurs<i>&lt;!-- ... --&gt;</i>car ils dÃ©notent des commentaires en HTML; ces balises de section n'auront donc aucun impact sur la mise en forme du document. On peut spÃ©cifier d'autres types de mÃ©ta-donnÃ©es dans la portion Description, mais ce n'est pas le cas du style de collection dÃ©crit ici. On peut aussi imbriquer des balises, de telle sorte que la ligne<i>(texte de la section)</i>ci-dessus peut elle-mÃªme inclure des sous-sections, telles que</Text>
+<Text id="560"><i>(texte de la premiÃšre partie de la section)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>   &lt;Description&gt;</CodeLine>
+<CodeLine>       &lt;Metadata name="Title"&gt; The international development targets&lt;/Metadata&gt;</CodeLine>
+<CodeLine>   &lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="561"><i>(texte de la sous-section)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="562"><i>(texte de la derniÃšre partie de la section)</i></Text>
+<Text id="563">Cette fonctionnalitÃ© est hÃ©ritÃ©e par tout greffon utilisant HTMLPlug. En particulier, le greffon Word convertit les donnÃ©es qu'il reÃ§oit au format HTML: on peut donc procÃ©der exactement de la mÃªme maniÃšre pour spÃ©cifier des mÃ©ta-donnÃ©es dans les fichiers Word (et RTF). Ceci implique un peu de travail en coulisses, puisque lors de la conversion de documents Word vers HTML, le programme prend soin, normalement, de neutraliser les caractÃšres significatifs pour HTML, tels que<i>&lt;</i>et<i>&gt;</i>; nous nous sommes arrangÃ©s pour contourner cette neutralisation dans le cas des spÃ©cifications mentionnÃ©es ci-dessus. Il faut alors utiliser exactement le mÃªme format, mÃªme dans des fichiers Word, et ne pas oublier les<i>&lt;!--</i>et<i>--&gt;</i>qui entourent les mÃ©ta-donnÃ©es. Le choix des polices et l'espacement n'ont aucune importance.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="classifiers">
+<Title>
+<Text id="564">Classificateurs</Text>
+</Title>
+<Content>
+<Text id="565">Les classificateurs servent Ã  crÃ©er les index de navigation d'une collection, comme par exemple l'index titres A-Z de la collection dlpeople, et les index thÃšme, comment faire, organisation et titres A-Z dans la bibliothÃšque de dÃ©veloppement pour l'humanitÃ©, dont la collection Â«DemoÂ» est un sous-ensemble. La barre de navigation situÃ©e au sommet des copies d'Ã©cran dans les figuresÂ 3 etÂ 8a inclut la fonction Rechercher, qui est toujours disponible, suivie par autant de boutons que de classificateurs dÃ©finis. Les informations servant Ã  la navigation sont stockÃ©es dans la base de donnÃ©es d'informations de la collection, et y sont placÃ©es par des classificateurs lors de la phase finale du programme buildcol.pl.</Text>
+<Figure id="azlist_classifier">
+<Title>
+<Text id="566">Classificateur<i>AZList</i></Text>
+</Title>
+<File width="390" height="182" url="images/Dev_Fig_11.png"/>
+</Figure>
+<Text id="567">Les classificateurs, Ã  l'instar des greffons, sont spÃ©cifiÃ©s dans le fichier de configuration de la collection. Ã chacun correspond une ligne dÃ©butant par le mot-clef classify et suivie du nom du classificateur et des options qu'il accepte. Le fichier de configuration de collection simple Ã©tudiÃ© dans la sectionÂ <CrossRef target="Section" ref="configuration_file"/> comprend la ligne classify AZList -metadata Title, qui crÃ©e une liste alphabÃ©tique des titres en prenant tous les documents pourvus d'un champ de mÃ©ta-donnÃ©es Title, en triant ces derniers et en les ventilant en intervalles alphabÃ©tiques. On trouvera un exemple dans la figureÂ <CrossRef target="Figure" ref="azlist_classifier"/>.</Text>
+<Figure id="list_classifier">
+<Title>
+<Text id="568">Classificateur<i>List</i></Text>
+</Title>
+<File width="394" height="143" url="images/Dev_Fig_12.png"/>
+</Figure>
+<Text id="569">Un classificateur plus simple, appelÃ© List, et illustrÃ© dans la figureÂ <CrossRef target="Figure" ref="list_classifier"/>, crÃ©e une liste triÃ©e d'une mÃ©ta-donnÃ©e spÃ©cifiÃ©e et l'affiche sans crÃ©er de tranches alphabÃ©tiques. Un exemple est la mÃ©ta-donnÃ©e how to de la collection Â«DemoÂ», qui est produite par la ligne classify List -metadata Howto dans le fichier de configuration de la collection<FootnoteRef id="4"/>. Un autre classificateur de liste gÃ©nÃ©rique est DateList, illustrÃ© dans la figureÂ <CrossRef target="Figure" ref="datelist_classifier"/>, qui engendre une liste de sÃ©lection d'intervalles de dates (le classificateur DateList est Ã©galement utilisÃ© dans la collection Â«ArchivesÂ» de Greenstone).</Text>
+<Figure id="datelist_classifier">
+<Title>
+<Text id="570">Classificateur<i>DateList</i></Text>
+</Title>
+<File width="390" height="159" url="images/Dev_Fig_13.png"/>
+</Figure>
+<Text id="571">D'autres classifications engendrent des structures de navigation qui sont explicitement hiÃ©rarchiques. Les classifications hiÃ©rarchiques sont utiles pour des classifications et sous-classifications de thÃšmes, et les hiÃ©rarchies organisationnelles. Le fichier de configuration de la collection Â«DemoÂ» contient la ligne classify Hierarchy -hfile sub.txt -metadata Subject -sort Title, et la figureÂ <CrossRef target="Figure" ref="hierarchy_classifier"/> ontre la hiÃ©rarchie de thÃšmes que cette ligne produit. L'Ã©tagÃšre portant un titre en gras et l'Ã©tagÃšre actuellement utilisÃ©e; la classification de thÃšme Ã  laquelle elle appartient la surplombe. Dans cet exemple la hiÃ©rarchie utilisÃ©e pour la classification est stockÃ©e dans un simple fichier texte, sous le nom sub.txt.</Text>
+<Figure id="hierarchy_classifier">
+<Title>
+<Text id="572">Classificateur<i>Hierarchy</i></Text>
+</Title>
+<File width="394" height="198" url="images/Dev_Fig_14.png"/>
+</Figure>
+<Text id="573">Tous les classificateurs gÃ©nÃšrent une structure hiÃ©rarchique qui est utilisÃ©e pour afficher un index de navigateur. Les niveaux les plus bas de la hiÃ©rarchie (les feuilles) sont gÃ©nÃ©ralement les documents, mais dans certains classificateurs ce sont les sections. Les noeuds internes de la hiÃ©rarchie sont Vlist, Hlist, ou Datelist. Un noeud Vlist est une liste d'objets affichÃ©s verticalement et descendant la page, telle que l'index Â«comment faireÂ» de la collection Â«DemoÂ» (figureÂ <CrossRef target="Figure" ref="list_classifier"/>). Un noeud Hlist est affichÃ© horizontalement; par exemple l'affichage AZList de la figureÂ <CrossRef target="Figure" ref="azlist_classifier"/> est une hiÃ©rarchie Ã  deux niveaux de noeuds internes consistant en un noeud Hlist (donnant le sÃ©lecteur A-Z) et dont les enfants sont des noeuds VlistÂ --Â parents, Ã  leur tour, de documents. Un noeud Datelist (figureÂ <CrossRef target="Figure" ref="datelist_classifier"/>) est un cas particulier de noeud Vlist qui permet d'effectuer des sÃ©lections par annÃ©e et par mois.</Text>
+<Text id="574">Les lignes spÃ©cifiant des classificateurs dans les fichiers de configuration de collection contiennent un argument metadata qui identifie les mÃ©ta-donnÃ©es selon lesquelles classifier et trier les documents. Tout document de la collection ne disposant pas de cette mÃ©ta-donnÃ©e sera omis par le classificateur (mais il sera quand mÃªme indexÃ©, et les recherches le prendront donc en compte). En l'absence de spÃ©cification d'argument metadata, tous les documents sont inclus dans le classificateur, dans l'ordre dans lequel le processus de construction les a trouvÃ©s. C'est utile si vous souhaitez obtenir une liste de tous les documents de votre collection.</Text>
+<Table id="greenstone_classifiers">
+<Title>
+<Text id="575">Classificateurs de Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="576"><b>Argument</b></Text>
+</th>
+<th width="305">
+<Text id="577"><b>But</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="578"><i>Hierarchy</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="579">Classification hiÃ©rarchique</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="580"><i>hfile</i></Text>
+</th>
+<th width="305">
+<Text id="581">Fichier de classification</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="582"><i>metadata</i></Text>
+</th>
+<th width="305">
+<Text id="583">ÃlÃ©ment de mÃ©ta-donnÃ©e Ã  confronter Ã  l'identifiant<i>hfile</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="584"><i>sort</i></Text>
+</th>
+<th width="305">
+<Text id="585">ÃlÃ©ment de mÃ©ta-donnÃ©e utilisÃ© pour trier les documents au sein des feuilles (valeur par dÃ©faut:<i>Title</i>)</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="586"><i>buttonname</i></Text>
+</th>
+<th width="305">
+<Text id="587">Nom du bouton utilisÃ© pour accÃ©der Ã  ce classificateur (valeur par dÃ©faut: valeur de l'argument<i>metadata</i>)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="588"><i>List</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="589">Liste alphabÃ©tique des documents</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="590"><i>metadata</i></Text>
+</th>
+<th width="305">
+<Text id="591">Inclut les documents contenant cet Ã©lÃ©ment de mÃ©ta-donnÃ©e</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="592"><i>buttonname</i></Text>
+</th>
+<th width="305">
+<Text id="593">Nom du bouton utilisÃ© pour accÃ©der Ã  ce classificateur (valeur par dÃ©faut: valeur de l'argument<i>metadata</i>)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="594"><i>SectionList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="595">Liste des sections dans les documents</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="596"><i>AZList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="597">Liste des documents ventilÃ©s en intervalles alphabÃ©tiques</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="598"><i>metadata</i></Text>
+</th>
+<th width="305">
+<Text id="599">Inclut les documents contenant cet Ã©lÃ©ment de mÃ©ta-donnÃ©e</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="600"><i>buttonname</i></Text>
+</th>
+<th width="305">
+<Text id="601">Nom du bouton utilisÃ© pour accÃ©der Ã  ce classificateur (valeur par dÃ©faut: valeur de l'argument<i>metadata</i>)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="602"><i>AZSectionList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="603">Comme<i>AZList</i>mais inclut chaque section du document</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="604"><i>DateList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="605">Similaire Ã <i>AZList</i>mais en triant par date</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="606">Les classificateurs actuellement disponibles sont listÃ©s dans la table <CrossRef target="Table" ref="greenstone_classifiers"/>. De mÃªme que l'on peut utiliser le programme pluginfo.pl pour en savoir plus sur un greffon quelconque, on peut utiliser le programme classinfo.pl pour en savoir plus sur un classificateur et sur les options qu'il propose.</Text>
+<Text id="607">Tous les classificateurs acceptent l'argument buttonname, qui dÃ©finit ce qui est Ã©crit sur le bouton de navigation de Greenstone qui invoque le classificateur (sa valeur par dÃ©faut est le nom de l'argument metadata). Des boutons sont fournis pour chacun des types de mÃ©ta-donnÃ©es du systÃšme Dublin Core, ainsi que pour quelques autres types de mÃ©ta-donnÃ©es.</Text>
+<Text id="608">Chaque classificateur reÃ§oit un nom implicite en fonction de sa position dans le fichier de configuration. Par exemple, le troisiÃšme classificateur spÃ©cifiÃ© dans le fichier s'appellera CL3. Ces noms sont utilisÃ©s dans les champs de la base de donnÃ©es d'informations de la collection, qui dÃ©finit la hiÃ©rarchie des classificateurs.</Text>
+<Text id="609">On peut Ã©crire des classificateurs propres Ã  une collection; ils sont alors stockÃ©s dans son rÃ©pertoire perllib/classify. La bibliothÃšque de dÃ©veloppement pour l'humanitÃ© dispose d'un classificateur propre de collection qui s'appelle HDLList, et qui est une variante mineure d'AZList.</Text>
+<Subsection id="list_classifiers">
+<Title>
+<Text id="610">Classificateurs de listes</Text>
+</Title>
+<Content>
+<Text id="611">Voici les diffÃ©rentes possibilitÃ©s de classificateurs de listes:</Text>
+<BulletList>
+<Bullet>
+<Text id="612">SectionListÂ --Â comme List mais les feuilles sont des sections et non pas des documents. Toutes les sections du document sont incluses Ã  l'exception des sections de premier niveau. Cela sert Ã  crÃ©er des listes de sections (ou d'articles, de chapitres, ou ...) cVoici les diffÃ©rentes omme dans la collection Computists' Weekly (l'hebdomadaire des informaticiens), disponible depuis le site webnzdl.org, dont chaque numÃ©ro est un unique document qui comprend plusieurs dÃ©pÃªches indÃ©pendantes, chacune Ã©tant placÃ©e dans sa propre section.</Text>
+</Bullet>
+<Bullet>
+<Text id="613">AZListÂ --Â gÃ©nÃšre une hiÃ©rarchie Ã  deux niveaux comprenant un noeud HList dont les enfants sont des noeuds VList, parents Ã  leur tour de documents. Le noeud HList est un sÃ©lecteur A-Z qui divise les documents en intervalles alphabÃ©tiques. Les documents sont triÃ©s alphabÃ©tiquement selon des mÃ©ta-donnÃ©es, et la liste rÃ©sultante est ventilÃ©e en intervalles.</Text>
+</Bullet>
+<Bullet>
+<Text id="614">AZSectionListÂ --Â comme AZList, mais les feuilles sont des sections, et non pas des documents.</Text>
+</Bullet>
+<Bullet>
+<Text id="615">DateListÂ --Â comme AZList Ã  ceci prÃšs que le noeud HList de premier niveau permet des sÃ©lections par annÃ©e et que ses enfants sont des noeuds de type DateList et non pas de type VList. La valeur par dÃ©faut de l'argument metadata est Date.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="the_hierarchy_classifier">
+<Title>
+<Text id="616">Le classificateur hierarchy</Text>
+</Title>
+<Content>
+<Text id="617">Tous les classificateurs sont hiÃ©rarchiques. Cependant, les classificateurs de la sectionÂ 2.1.1 disposent d'un nombre fixÃ© de niveaux, alors que le classificateur hierarchy dÃ©crit dans la prÃ©sente section peut crÃ©er un nombre de niveaux arbitraire: il est plus complexe Ã  spÃ©cifier que les classificateurs de listes.</Text>
+<Figure id="part_of_the_file_sub">
+<Title>
+<Text id="618">Portion du fichier sub.txt</Text>
+</Title>
+<CodeLine>1           1       "General reference"</CodeLine>
+<CodeLine>1.2       1.2       "Dictionaries, glossaries, language courses, terminology</CodeLine>
+<CodeLine>2           2       "Sustainable Development, International cooperation, Pro</CodeLine>
+<CodeLine>2.1       2.1       "Development policy and theory, international cooperatio</CodeLine>
+<CodeLine>2.2       2.2       "Development, national planning, national plans"</CodeLine>
+<CodeLine>2.3       2.3       "Project planning and evaluation (incl. project managem</CodeLine>
+<CodeLine>2.4       2.4       "Regional development and planning incl. regional profil</CodeLine>
+<CodeLine>2.5       2.5       "Nongovernmental organisations (NGOs) in general, self-</CodeLine>
+<CodeLine>2.6       2.6       "Organisations, institutions, United Nations (general, d</CodeLine>
+<CodeLine>2.6.1   2.6.1       "United Nations"</CodeLine>
+<CodeLine>2.6.2   2.6.2       "International organisations"</CodeLine>
+<CodeLine>2.6.3   2.6.3       "Regional organisations"</CodeLine>
+<CodeLine>2.6.5   2.6.5       "European Community - European Union"</CodeLine>
+<CodeLine>2.7       2.7       "Sustainable Development, Development models and example</CodeLine>
+<CodeLine>2.8       2.8       "Basic Human Needs"</CodeLine>
+<CodeLine>2.9       2.9       "Hunger and Poverty Alleviation"</CodeLine>
+</Figure>
+<Text id="619">L'argumentÂ hfile donne le nom d'un fichier, tel que celui de la figureÂ <CrossRef target="Figure" ref="part_of_the_file_sub"/>, qui dÃ©finit la hiÃ©rarchie de mÃ©ta-donnÃ©es. Chaque ligne dÃ©crit une classification, et les descriptions comptent trois parties:</Text>
+<BulletList>
+<Bullet>
+<Text id="620">Un identifiant, qui fait correspondre la valeur de la mÃ©ta-donnÃ©e (donnÃ©e par l'argument metadata) Ã  la classification.</Text>
+</Bullet>
+<Bullet>
+<Text id="621">Un marqueur de position dans la hiÃ©rarchie, sous forme numÃ©rique en plusieurs parties, comme par exemple 2, 2.12, 2.12.6.</Text>
+</Bullet>
+<Bullet>
+<Text id="622">Le nom de la classification (s'il contient des espaces, il faut le placer entre apostrophes doubles).</Text>
+</Bullet>
+</BulletList>
+<Text id="623">La figureÂ <CrossRef target="Figure" ref="part_of_the_file_sub"/> est une portion du fichier sub.txt, utilisÃ© pour crÃ©er la hiÃ©rarchie de thÃšmes dans la bibliothÃšque de dÃ©veloppement pour l'HumanitÃ© (et dans la collection Â«DemoÂ»). Cet exemple n'est pas trÃšs clair puisque le nombre reprÃ©sentant la hiÃ©rarchie apparaÃ®t deux fois sur chaque ligne. Le type de mÃ©ta-donnÃ©e Hierarchy est reprÃ©sentÃ© dans les documents avec des valeurs sous forme numÃ©rique hiÃ©rarchique, ce qui correspond Ã  la premiÃšre occurrence. C'est la deuxiÃšme occurrence qui est utilisÃ©e pour dÃ©terminer la hiÃ©rarchie implÃ©mentÃ©e dans la hiÃ©rarchie de navigation.</Text>
+<Text id="624">Le classificateur hierarchy dispose d'un argument facultatif, sort, qui dÃ©termine la maniÃšre dont les documents sont ordonnÃ©s au niveau des feuilles. On peut spÃ©cifier n'importe quelle mÃ©ta-donnÃ©e comme clef de tri. Le comportement par dÃ©faut est de produire la liste dans l'ordre dans lequel le processus de construction rencontre les documents. Au niveau des noeuds internes, l'ordre est dÃ©terminÃ© par celui des spÃ©cifications dans l'argument hfile.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_classifiers_work">
+<Title>
+<Text id="625">Fonctionnement des classificateurs</Text>
+</Title>
+<Content>
+<Text id="626">Les classificateurs sont des objets Perl, hÃ©ritant de BasClas.pm, et stockÃ©s dans le rÃ©pertoire perllib/classify. Ils sont utilisÃ©s lors de la construction de la collection. Leur exÃ©cution se fait en quatre Ã©tapes:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="627">La mÃ©thode new crÃ©e l'objet classificateur.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="628">La mÃ©thode init initialise l'objet avec des paramÃštres tels que le type de mÃ©ta-donnÃ©e, le nom du bouton, et le critÃšre de tri.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="629">La mÃ©thode classify est invoquÃ©e une fois par document, et stocke les informations de la classification effectuÃ©e dans l'objet classificateur. </Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="630">La mÃ©thode get_classify_info renvoie la classification stockÃ©e localement vers le processus de construction, qui l'Ã©crit Ã  son tour dans la base de donnÃ©es d'informations de la collection Ã  des fins d'utilisation lors de l'affichage de la collection, au moment de l'exÃ©cution.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="631">La mÃ©thode classify rapatrie l'OID de chaque document, la valeur de mÃ©ta-donnÃ©e selon laquelle classifier le document, et, si nÃ©cessaire, la valeur de mÃ©ta-donnÃ©e selon laquelle trier les documents. La mÃ©thode get_classify_info s'occupe du tri et de tout traitement propre au classificateur. Dans le cas du classificateur AZList par exemple, elle ventile la liste en intervalles.</Text>
+<Text id="632">Le processus de construction initialise les classificateurs dÃšs que l'objet builder est construit. Les classifications sont crÃ©Ã©es pendant la phase de construction, lors de la crÃ©ation de la base de donnÃ©es d'informations, par classify.pm, qui rÃ©side dans le rÃ©pertoire perllib de Greenstone.</Text>
+<Table id="items_appearing_in_format_strings">
+<Title>
+<Text id="633">Objets apparaissant dans les chaÃ®nes de formatage</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="634"><i>[Text]</i></Text>
+</th>
+<th width="397">
+<Text id="635">Texte du document</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="636"><i>[link] âŠ [/link]</i></Text>
+</th>
+<th width="397">
+<Text id="637">Portion de HTML Ã  relier au document lui-mÃªme</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="638"><i>[icon]</i></Text>
+</th>
+<th width="397">
+<Text id="639">Une icone appropriÃ©e (telle que la petite icone de texte dans une chaÃ®ne<i>RÃ©sultats de la recherche</i>)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="640"><i>[num]</i></Text>
+</th>
+<th width="397">
+<Text id="641">NumÃ©ro du document (utile pour dÃ©boguer)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="642"><i>[metadata-name]</i></Text>
+</th>
+<th width="397">
+<Text id="643">Valeur de cet Ã©lÃ©ment de mÃ©ta-donnÃ©e pour le document, tel que<i>[Title]</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="formatting_greenstone_output">
+<Title>
+<Text id="644">Mettre en forme la sortie de Greenstone</Text>
+</Title>
+<Content>
+<Text id="645">Les pages web que vous pouvez voir lorsque vous utilisez Greenstone ne sont stockÃ©es nulle part; elles sont gÃ©nÃ©rÃ©es Â«Ã  la volÃ©eÂ» en fonction des besoins. L'apparence de nombreux aspects de ces pages est contrÃŽlÃ©e Ã  l'aide de Â«chaÃ®nes de formatageÂ» (dans le sens de Â«mise en formeÂ», et pas de Â«remise Ã  zÃ©roÂ»). Les chaÃ®nes de formatage se trouvent dans le fichier de configuration de la collection, introduites par le mot-clef format lui-mÃªme suivi du nom de l'Ã©lÃ©ment concernÃ© par la mise en forme. Il existe deux types d'Ã©lÃ©ments de page contrÃŽlÃ©s par des chaÃ®nes de formatage. Le premier comprend les Ã©lÃ©ments de la page qui affichent des documents ou des portions de documents. Le second comprend les listes produites par les classificateurs et les recherches. Toutes les chaÃ®nes de formatage sont interprÃ©tÃ©es au moment de l'affichage des pages. Elles prennent donc effet dÃšs que le fichier collect.cfg est modifiÃ© et sauvegardÃ©; il est par consÃ©quent rapide et facile de faire des expÃ©riences avec les chaÃ®nes de formatage.</Text>
+<Text id="646">La tableÂ <CrossRef target="Table" ref="items_appearing_in_format_strings"/> montre les instructions qui affectent la reprÃ©sentation des documents. L'option DocumentButtons contrÃŽle les boutons qui sont affichÃ©s sur une page de document. Ici, chaÃ®ne est une liste de boutons (sÃ©parÃ©s par<i>|</i>), dont les valeurs possibles sont Detach (dÃ©tacher), Highlight (mettre en valeur), Expand Text (dÃ©velopper le texte), et Expand Contents (dÃ©velopper la table des matiÃšres). Modifier l'ordre de la liste a le mÃªme effet sur les boutons.</Text>
+<Table id="the_format_options">
+<Title>
+<Text id="647">Les options du mot-clef<i>format</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="246">
+<Text id="648"><i>format DocumentImages true/false</i></Text>
+</th>
+<th width="283">
+<Text id="649">Si la valeur est<i>true</i>, affiche une image de couverture en haut Ã  gauche de la page du document (la valeur par dÃ©faut est<i>false</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="650"><i>format DocumentHeading chaÃ®ne_de_formatage</i></Text>
+</th>
+<th width="283">
+<Text id="651">Si l'option<i>DocumentImages</i>a la valeur<i>false</i>, la chaÃ®ne de formatage contrÃŽle la reprÃ©sentation de l'en-tÃªte de document apparaissant en haut Ã  gauche de la page du document (la valeur par dÃ©faut est<i>[Title]</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="652"><i>format DocumentContents true/false</i></Text>
+</th>
+<th width="283">
+<Text id="653">Affiche la table des matiÃšres (si le document a une structure hiÃ©rarchique), ou des flÃšches pour se rendre Ã  la section prÃ©cÃ©dente ou suivante et le texte Â«page k sur nÂ» (dans le cas contraire).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="654"><i>format DocumentButtons chaÃ®ne</i></Text>
+</th>
+<th width="283">
+<Text id="655">ContrÃŽle les boutons affichÃ©s sur une page de document (la valeur par dÃ©faut est<i>Detach|Highlight</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="656"><i>format DocumentText chaÃ®ne_de_formatage</i></Text>
+</th>
+<th width="283">
+<Text id="657">Format du texte Ã  afficher sur une page de document; la valeur par dÃ©faut est</Text>
+<CodeLine>Â Â Â Â <i>&lt;center&gt;&lt;table width=537&gt;</i></CodeLine>
+<CodeLine><i>Â Â Â Â Â Â &lt;tr&gt;&lt;td&gt;[Text]&lt;/td&gt;&lt;/tr&gt;</i></CodeLine>
+<CodeLine><i>Â Â Â Â Â Â &lt;/table&gt;&lt;/center&gt;</i></CodeLine>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="658"><i>format DocumentArrowsBottom true/false</i></Text>
+</th>
+<th width="283">
+<Text id="659">Affiche des flÃšches pour se rendre Ã  la section prÃ©cÃ©dente ou suivante au pied de la page du document (la valeur par dÃ©faut est<i>true</i>, qui active ce comportement).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="660"><i>format DocumentUseHTML true/false</i></Text>
+</th>
+<th width="283">
+<Text id="661">Si la valeur est<i>true</i>, chaque document sera affichÃ© dans un cadre<i>frame</i>diffÃ©rent. La page de<i>PrÃ©fÃ©rences</i>changera un peu Ã©galement, et proposera de nouvelles options pour les documents HTML, telles que la possibilitÃ© de se rendre directement sur le document source original (partout sur le web) plutÃŽt que sur la copie faite par Greenstone.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Subsection id="formatting_greenstone_lists">
+<Title>
+<Text id="662">Formatage des listes de Greenstone</Text>
+</Title>
+<Content>
+<Text id="663">Les chaÃ®nes de formatage qui contrÃŽlent l'apparence des listes peuvent s'appliquer Ã  divers niveaux de la structure d'affichage. Elles peuvent altÃ©rer toutes les listes d'un certain type au sein d'une collection (comme par exemple DateList), toutes les parties d'une liste (comme par exemple toutes les entrÃ©es de la liste Rechercher), ou des portions spÃ©cifiques d'une liste particuliÃšre (comme par exemple la portion verticale de la liste du classificateur AZList appliquÃ© sur des titres).</Text>
+<Text id="664">Le mot-clef format prÃ©cÃšde un mot-clef en deux parties, dont une seule est obligatoire. La premiÃšre partie identifie la liste oÃ¹ s'applique le format. La liste gÃ©nÃ©rÃ©e par une recherche s'appelle Search (rechercher), tandis que les listes gÃ©nÃ©rÃ©es par des classificateurs sont appelÃ©es CL1, CL2, CL3,... pour respectivement le premier, le deuxiÃšme, le troisiÃšme... classificateur spÃ©cifiÃ© dans le fichier collect.cfg. La deuxiÃšme partie du mot-clef est la portion de la liste Ã  laquelle appliquer la mise en formeÂ --Â soit HList (pour une liste horizontale, telle que le sÃ©lecteur dans un noeud AZList), VList (pour une liste verticale, telle que la liste des tous les titres sous un noeud de type AZList), ou DateList. Par exemple:</Text>
+<Indented>
+<Text id="665">format CL4VList ... s'applique Ã  tous les VList de CL4</Text>
+</Indented>
+<Indented>
+<Text id="666">format CL2HList ... s'applique Ã  tous les HList de CL2</Text>
+</Indented>
+<Indented>
+<Text id="667">format CL1DateList ... s'applique Ã  tous les DateList de CL1</Text>
+</Indented>
+<Indented>
+<Text id="668">format SearchVList ... s'applique Ã  la liste de RÃ©sultats de la recherche</Text>
+</Indented>
+<Indented>
+<Text id="669">format CL3 ... s'applique Ã  tous les noeuds de CL3, sauf indication contraire</Text>
+</Indented>
+<Indented>
+<Text id="670">format VList ... s'applique Ã  tous les VList de tous les classificateurs, sauf indication contraire</Text>
+</Indented>
+<Text id="671">Les<i>"..."</i>de ces exemples reprÃ©sentent des spÃ©cifications de formatage HTML qui contrÃŽlent l'information et sa reprÃ©sentation, apparaissant sur des pages web reprÃ©sentant le classificateur. Comme pour les spÃ©cifications HTML, toute mÃ©ta-donnÃ©e peut apparaÃ®tre entre crochets: sa valeur est interpolÃ©e Ã  l'endroit indiquÃ©. Tout Ã©lÃ©ment de la tableÂ <CrossRef target="Table" ref="the_format_options"/> peut Ã©galement apparaÃ®tre dans des chaÃ®nes de formatage. La syntaxe des chaÃ®nes prÃ©voit Ã©galement une instruction conditionnelle, qui est illustrÃ©e plus bas.</Text>
+<Text id="672">Rappelez-vous que tous les classificateurs produisent des hiÃ©rarchies. Chaque niveau de la hiÃ©rarchie est affichÃ© de l'une de quatre maniÃšres possibles. Nous avons dÃ©jÃ  mentionnÃ© HList, VList, et DateList. Il existe Ã©galement Invisible, qui est la maniÃšre dont les tous premiers niveaux des hiÃ©rarchies sont reprÃ©sentÃ©sÂ --Â le nom du classificateur apparaÃ®t dÃ©jÃ  sÃ©parÃ©ment, en effet, sur la barre de navigation de Greenstone.</Text>
+</Content>
+</Subsection>
+<Subsection id="examples_of_classifiers_and_format_strings">
+<Title>
+<Text id="673">Exemples de classificateurs et de chaÃ®nes de formatage</Text>
+</Title>
+<Content>
+<Figure id="excerpt_from_the_demo_collection_collect" class="withLineNumber">
+<Title>
+<Text id="674">Extrait du fichier collect.cfg de la collection Â«DemoÂ»</Text>
+</Title>
+<CodeLine>classify Hierarchy -hfile sub.txt -metadata Subject -sort Title</CodeLine>
+<CodeLine>classify AZList       -metadata Title</CodeLine>
+<CodeLine>classify Hierarchy -hfile org.txt -metadata Organisation -sort Title</CodeLine>
+<CodeLine>classify List           -metadata Howto</CodeLine>
+<CodeLine>format SearchVList " &lt;td valign=top [link][icon][/link]&lt;/td&gt;&lt;td&gt;{If}</CodeLine>
+<CodeLine>                                       {[parent(All':'):Title],[parent(All':'):Title]:}</CodeLine>
+<CodeLine>                                       [link][Title][/link]&lt;/td&gt; "</CodeLine>
+<CodeLine>format CL4Vlist                 "&lt;br&gt;[link][Howto][/link] "</CodeLine>
+<CodeLine>format DocumentImages   true</CodeLine>
+<CodeLine>format DocumentText       "&lt;h3&gt;[Title]&lt;/h3&gt;\\n\\n&lt;p&gt;[Text]"</CodeLine>
+<CodeLine>format DocumentButtons " Expand Text|Expand contents|Detach|Highlight"</CodeLine>
+</Figure>
+<Text id="675">La figureÂ <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/> reprÃ©sente une portion du fichier de configuration de la collection Â«DemoÂ». Nous l'utilisons comme exemple, car il comprend plusieurs classificateurs avec un formatage riche. Remarquez que les instructions des fichiers de configuration ne peuvent pas contenir de retour Ã  la ligne, et que dans la figure, nous avons scindÃ© les lignes les plus longues pour des raisons de lisibilitÃ©.</Text>
+<Text id="676">La ligne 4 spÃ©cifie le classificateur How To (comment faire) de la collection Â«DemoÂ». C'est le quatriÃšme classificateur du fichier de configuration de la collection; on s'y rÃ©fÃšre donc sous le nom CL4. L'instruction de formatage correspondante est la ligne 7 de la figureÂ <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>. Cette information d'Â«indiceÂ» est engendrÃ©e par le classificateur List, et sa structure est la liste brute des titres affichÃ©s figureÂ <CrossRef target="Figure" ref="list_classifier"/>. Les titres sont reliÃ©s aux documents eux-mÃªmes: cliquer sur un titre affiche le document correspondant. Les enfants du premier niveau de la hiÃ©rarchie sont affichÃ©s sous la forme d'une VList (liste verticale), qui liste les sections verticalement. Comme l'indique l'instruction format associÃ©e, chaque Ã©lÃ©ment de la liste apparaÃ®t sur une nouvelle ligne ("&lt;br&gt;") et contient le texte de Howto, lui-mÃªme reliÃ© par lien hypertexte au document lui-mÃªme.</Text>
+<Text id="677">La ligne 1 spÃ©cifie la classification Subject (ThÃšme) de la collection Â«DemoÂ», Ã  laquelle on se rÃ©fÃ©rera sous le nom CL1 (puisqu'elle est la premiÃšre du fichier de configuration), et la ligne 3 spÃ©cifie la classification Organisation CL3. Toutes deux sont gÃ©nÃ©rÃ©es par le classificateur Hierarchy et comprennent donc une structure hiÃ©rarchique d'objets VList.</Text>
+<Text id="678">La ligne 2 spÃ©cifie la derniÃšre classification de la collection Â«DemoÂ», titres A-Z (CL2). Remarquez qu'il n'existe pas de chaÃ®nes de formatage associÃ©es aux classificateurs CL1 Ã  CL3. Greenstone dispose de valeurs par dÃ©faut pour chaque type de chaÃ®ne de formatage; il n'est donc pas nÃ©cessaire de positionner une chaÃ®ne de formatage quand on ne souhaite pas obtenir un comportement diffÃ©rent du comportement par dÃ©faut.</Text>
+<Figure id="formatting_the_document">
+<Title>
+<Text id="679">Mise en forme du document</Text>
+</Title>
+<File width="394" height="277" url="images/Dev_Fig_17.png"/>
+</Figure>
+<Text id="680">VoilÃ  pour les quatre lignes classify de la figureÂ <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>. On y trouve aussi quatre lignes format. Nous avons dÃ©jÃ  expliquÃ© la ligne CL4Vlist. Les trois lignes restantes sont du premier type de chaÃ®ne de formatage, documentÃ© dans la tableÂ <CrossRef target="Table" ref="items_appearing_in_format_strings"/>. Par exemple, la ligne 8 place l'image de couverture en haut Ã  gauche de chaque page de document. La ligne 9 formate le texte du document Ã  proprement parler, et place le titre du chapitre ou de la section concernÃ©e juste avant le texte. Tous ces effets sont illustrÃ©s dans la figureÂ <CrossRef target="Figure" ref="formatting_the_document"/>.</Text>
+<Figure id="formatting_the_search_results">
+<Title>
+<Text id="681">Mise en forme des rÃ©sultats de la recherche</Text>
+</Title>
+<File width="396" height="243" url="images/Dev_Fig_18.png"/>
+</Figure>
+<Text id="682">La ligne 5 de la figureÂ <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/> est une spÃ©cification quelque peu complexe qui formate la liste de rÃ©sultats Ã  une requÃªte renvoyÃ©e par une recherche, dont les portions sont illustrÃ©es Ã  la figureÂ <CrossRef target="Figure" ref="formatting_the_search_results"/>. Voici une version simplifiÃ©e de la chaÃ®ne de formatage:</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;</CodeLine>
+<CodeLine>&lt;td&gt;[link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="683">Ceci est conÃ§u pour apparaÃ®tre comme une ligne dans un tableau, ce qui est la maniÃšre dont la liste de rÃ©sultats Ã  une requÃªte est mise en forme. Comme d'habitude, on obtient une petite icone cliquable qui mÃšne au texte, et le titre du document, ancre d'un lien hypertexte qui mÃšne au document Ã  proprement parler.</Text>
+<Text id="684">Dans cette collection, les documents sont hiÃ©rarchiques. En fait, l'ancre de lien hypertexte ci-dessus se transforme en le titre de la section renvoyÃ©e par le requÃªte. Il serait nÃ©anmoins prÃ©fÃ©rable de lui adjoindre Ã©galement le titre de la section qui la contient, du chapitre qui contient cette derniÃšre, et du livre oÃ¹ ce chapitre apparaÃ®t. Il existe un objet de mÃ©ta-donnÃ©e particulier, parent, qui n'est pas stockÃ© dans les documents mais qui est implicite dans tout document hiÃ©rarchique, qui produit une telle liste. Elle renvoie soit le document parent ou, si elle est utilisÃ©e avec le qualificateur All (tout), la liste de tous les ancÃªtres au sens hiÃ©rarchique, sÃ©parÃ©s par une chaÃ®ne de caractÃšres que l'on peut prÃ©ciser aprÃšs le qualificateur All. Ainsi:</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt; <br/>&lt;td&gt;{[parent(All': '):Title]: }[link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="685">a pour effet de produire une liste contenant le titre du livre, le titre du chapitre, etc., qui entourent la section cible; titres sÃ©parÃ©s par des caractÃšres deux points, et un dernier caractÃšre deux points est suivi d'un lien hypertexte menant au titre de la section cible.</Text>
+<Text id="686">Malheureusement, dans le cas oÃ¹ la cible est un livre, elle n'aura aucun parent et on verra donc apparaÃ®tre une chaÃ®ne vide suivie d'un caractÃšre deux points. Pour Ã©viter de tels problÃšmes, on peut utiliser dans une chaÃ®ne de formatage des instructions conditionnelles if and or ... else (si et ou ... sinon):</Text>
+<CodeLine>{If}{[metadata], action-if-non-null, action-if-null}</CodeLine>
+<CodeLine>{Or}{action, else another-action, else another-action, etc}</CodeLine>
+<Text id="687">Dans chaque cas les accolades signalent que les instructions doivent Ãªtre interprÃ©tÃ©es, et non pas simplement affichÃ©es comme du texte. L'instruction If teste si la mÃ©ta-donnÃ©e est vide, et prend la premiÃšre clause si ce n'est pas le cas, et la deuxiÃšme clause si c'est le cas (et si une deuxiÃšme clause est fournie). On peut utiliser tout Ã©lÃ©ment de mÃ©ta-donnÃ©es, y compris la mÃ©ta-donnÃ©e spÃ©ciale parent. L'instruction Or Ã©value chaque action tour Ã  tour jusqu'au moment oÃ¹ elle en rencontre une qui n'est pas vide. Cette action est alors renvoyÃ©e en sortie et le reste de la ligne est ignorÃ©.</Text>
+<Text id="688">Si l'on revient Ã  la ligne 5 de la figureÂ <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>, la chaÃ®ne de formatage complÃšte est:</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;</CodeLine>
+<CodeLine>&lt;td&gt;{If}{[parent(All': '):Title],</CodeLine>
+<CodeLine>           [parent(All': '):Title]:}</CodeLine>    
+<CodeLine>      [link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="689">Ceci fait prÃ©cÃ©der la spÃ©cification parent d'un test qui examine si le rÃ©sultat est vide et n'affiche la chaÃ®ne du parent que lorsque ce dernier est prÃ©sent. On peut aussi qualifier parent par Top (sommet) au lieu de All (tout), ce qui donne le nom de document de niveau le plus Ã©levÃ© qui entoure une sectionÂ --Â dans le cas prÃ©sent, le nom du livre. Nul besoin, avec Top, de chaÃ®ne de sÃ©paration.</Text>
+<Text id="690">Voici quelques derniers exemples pour illustrer d'autres fonctionnalitÃ©s. Le classificateur DateList, dans la figureÂ <CrossRef target="Figure" ref="datelist_classifier"/>, est utilisÃ© dans la classification Dates de la collection Computists' Weekly (l'hebdomadaire des informaticiens), et il se trouve qu'il en est le deuxiÃšme classificateur, soit CL2. Le classificateur et les spÃ©cifications de formatage sont indiquÃ©s ci-dessous. Le classificateur DateList diffÃšre d'AZList en ce sens qu'il trie toujours selon la mÃ©ta-donnÃ©e Date, et que les branches situÃ©es au pied de la hiÃ©rarchie de navigation utilisent DateList au lieu de VList, ce qui ajoute Ã  gauche des listes de documents, l'annÃ©e et le mois.</Text>
+<CodeLine>classify AZSectionList metadata=Creator</CodeLine>
+<CodeLine>format CL2Vlist "&lt;td&gt;[link][icon][/link]&lt;/td&gt; <br/>&lt;td&gt;[Creator]&lt;/td&gt; <br/>&lt;td&gt;&amp;nbsp;&amp;nbsp;[Title]&lt;/td&gt; <br/>&lt;td&gt;[parent(Top):Date]&lt;/td&gt; "</CodeLine>
+<Text id="691">La spÃ©cification de formatage affiche ces VLists de maniÃšre appropriÃ©e.</Text>
+<Text id="692">Le mÃ©canisme de chaÃ®ne de formatage est souple mais difficile Ã  apprendre. La meilleure maniÃšre de procÃ©der est d'Ã©tudier des fichiers de configuration de collections existantes.</Text>
+</Content>
+</Subsection>
+<Subsection id="linking_to_different_document_versions">
+<Title>
+<Text id="693">Tirer des liens vers diffÃ©rentes versions d'un document</Text>
+</Title>
+<Content>
+<Text id="694">Utiliser le mÃ©canisme<i>[link] ... [/link]</i>dans une chaÃ®ne de formatage a pour effet d'insÃ©rer un lien hypertexte menant au texte du document, en version HTML. Il est utile dans certaines collections de pouvoir afficher d'autres versions du document. Dans une collection de documents au format Microsoft Word, par exemple, il est bon d'Ãªtre capable d'afficher la version Word de chaque document plutÃŽt que le HTML qui en fut extrait; de mÃªme pour des documents PDF.</Text>
+<Text id="695">Pour pouvoir afficher diffÃ©rentes versions d'un document, la clef est d'embarquer les informations nÃ©cessaires (c'est-Ã -dire oÃ¹ se trouvent les autres versions du document) dans le format d'archivage de Greenstone du document. On reprÃ©sente cette information sous la forme de mÃ©ta-donnÃ©es. Souvenez-vous qu'en plaÃ§ant</Text>
+<CodeLine>[link][Title][/link]</CodeLine>
+<Text id="696">dans une chaÃ®ne de formatage, on crÃ©e un lien vers la version HTML du document, lien dont l'ancre est le titre du document. Les greffons Word et PDF gÃ©nÃ©rent tous deux la mÃ©ta-donnÃ©e srclink de telle sorte qu'Ã©crire</Text>
+<CodeLine>[srclink][Title][/srclink]</CodeLine>
+<Text id="697">dans une chaÃ®ne de formatage crÃ©era un lien vers la version Word ou PDF du document; lien dont l'ancre sera dans cet exemple aussi, le titre du document. Pour permettre d'afficher l'icone appropriÃ©e pour les documents Word et PDF, ces greffons gÃ©nÃ©rent aussi la mÃ©ta-donnÃ©e srcicon de telle sorte que</Text>
+<CodeLine>[srclink][srcicon][/srclink]</CodeLine>
+<Text id="698">crÃ©era un lien Ã©tiquetÃ© par l'icone standard pour le format Word ou PDF (selon le cas), et non pas par le titre du document.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="controlling_the_greenstone_user_interface">
+<Title>
+<Text id="699">ContrÃŽler l'interface utilisateur de Greenstone</Text>
+</Title>
+<Content>
+<Text id="700">L'interface utilisateur de Greenstone est entiÃšrement contrÃŽlÃ©e par des macros placÃ©es dans le rÃ©pertoire GSDLHOME/macros. Elles sont Ã©crites dans un langage conÃ§u spÃ©cialement pour Greenstone, et sont utilisÃ©es au moment de l'exÃ©cution pour engendrer des pages web. La traduction du langage de macros en HTML est la derniÃšre Ã©tape de l'affichage d'une page. Ainsi, toute modification Ã  un fichier de macros affecte immÃ©diatement l'affichage, il est donc rapide et facile de faire des expÃ©riences avec les macros. Tous les fichiers de macros utilisÃ©s par Greenstone sont listÃ©s dans le fichier GSDLHOME/etc/main.cfg et sont chargÃ©s Ã  chaque dÃ©marrage. Signalons l'exception de la version Â«BibliothÃšque localeÂ» sous Windows; dans ce cas il est nÃ©cessaire de redÃ©marrer le processus.</Text>
+<Text id="701">Les pages web sont gÃ©nÃ©rÃ©es Ã  la volÃ©e pour de nombreuses raisons, et le systÃšme de macros est la maniÃšre dont Greenstone implÃ©mente la souplesse nÃ©cessaire. On peut prÃ©senter des pages dans de nombreuses langues diffÃ©rentes, et on utilise un fichier de macros diffÃ©rent pour stocker tout le texte de l'interface dans chaque langue. Quand Greenstone affiche une page l'interprÃ©teur de macros consulte une variable de langue et charge la page dans la langue appropriÃ©e (ce systÃšme ne va pas, malheureusement, jusqu'Ã  traduire le contenu du document). De mÃªme, les valeurs de certaines variables d'affichage, telles que le nombre de documents trouvÃ©s par une recherche, ne sont pas connues Ã  l'avance: elles sont interpolÃ©es dans le texte de la page Ã  l'aide de macros.</Text>
+<Subsection id="the_macro_file_format">
+<Title>
+<Text id="702">Le format des fichiers de macros</Text>
+</Title>
+<Content>
+<Text id="703">Les fichiers de macros ont pour extension .dm. Chaque fichier dÃ©finit un ou plusieurs paquetages, et chaque paquetage dÃ©finit une sÃ©rie de macros utilisÃ©es dans un but prÃ©cis et unique. Ã l'instar des classificateurs et des greffons, il existe une base Ã  partir de laquelle construire des macros, appelÃ©e base.dm; ce fichier dÃ©finit le contenu de base d'une page.</Text>
+<Text id="704">Les macros portent des noms qui commencent et finissent par un caractÃšre de soulignement, et leur contenu est dÃ©fini Ã  l'aide d'accolades. Leur contenu peut consister en du texte brut, du HTML (y compris de liens vers des appliquettes (applets) Java ou du JavaScript), des noms de macros, ou toute combinaison de ces Ã©lÃ©ments. La macro suivante, extraite du fichier base.dm, dÃ©finit le contenu d'une page en l'absence de toute macro de remplacement:</Text>
+<CodeLine>_content_ {&lt;p&gt;&lt;h2&gt;Oops&lt;/h2&gt;_textdefaultcontent_}</CodeLine>
+<Text id="705">Cette page affichera Â«OopsÂ» Ã  son sommet, suivi du contenu de la macro d'erreur correspondante, _textdefaultcontent_ qui est en anglais dÃ©finie comme suit: Global:textdefaultcontentThe requested page could not be found. Please use your browsers 'back' button or the above home button to return to the Greenstone Digital Library.; dans d'autres langues, elle affichera une traduction appropriÃ©e de cette phrase. En franÃ§ais, on obtiendra par exemple Global:textdefaultcontentLa page demandÃ©e n'a pu Ãªtre trouvÃ©e. Utilisez s'il-vous-plaÃ®t le bouton Â«retourÂ» de votre navigateur, ou le bouton Â«accueilÂ» pour retourner Ã  la BibliothÃšque NumÃ©rique Greenstone.</Text>
+<Text id="706">Les deux macros _textdefaultcontent_ (contenu textuel par dÃ©faut) et _content_ (contenu) se trouvent dans le paquetage global car elles sont requises dans toutes les portions de l'interface utilisateur. Les macros peuvent utiliser des macros d'autres paquetages en tant que contenu, mais il faut alors qu'elles en prÃ©fixent les noms par le nom du paquetage. Exemple:</Text>
+<CodeLine>_collectionextra_ {This collection contains _about:numdocs_ documents. It was last built _about:builddate_ days ago.)</CodeLine>
+<Text id="707">provient du fichier french.dm (macros pour le franÃ§ais), et elle est utilisÃ©e comme description par dÃ©faut d'une collection. Elle fait partie du paquetage intitulÃ© global, mais les macros _numdocs_ et _builddate_ se trouvent toutes deux dans le paquetage about (Ã  propos de...)Â --Â d'oÃ¹ le about qui prÃ©fixe leurs noms.</Text>
+<Text id="708">Les macros renferment souvent des conditionnelles, qui ressemblent aux conditonnelles de chaÃ®nes de formatage dÃ©crites plus haut, Ã  ceci prÃšs que leur apparence est un peu diffÃ©rente. Le format de base est _If_(x,y,z), oÃ¹ x est une condition, y est le contenu de macro Ã  utiliser si cette condition est vÃ©rifiÃ©e, z le contenu Ã  utiliser dans le cas contraire. Les opÃ©rateurs de comparaison sont les mÃªmes que les opÃ©rateurs simples utilisÃ©s dans Perl (moins que, plus que, Ã©gale, diffÃ©rent de). L'exemple suivant, extrait du fichier base.dm, sert Ã  dÃ©terminer comment afficher le sommet de la page Ã propos de cette collection d'une collection:</Text>
+<CodeLine>_imagecollection_ {</CodeLine>
+<CodeLine>       _If_( "_iconcollection_ " ne "",</CodeLine>
+<CodeLine>                 &lt;a href = "_httppageabout_ "&gt; </CodeLine>
+<CodeLine>                         &lt;img src = "_iconcollection_ " border = 0&gt;</CodeLine>
+<CodeLine>                         &lt;/a&gt;,</CodeLine>
+<CodeLine>                 _imagecollectionv_)</CodeLine>
+<CodeLine>}</CodeLine>
+<Text id="709">VoilÃ  qui peut sembler abscons. La macro _iconcollection_ vaut la chaÃ®ne vide si la collection ne dispose pas d'une icone, ou le nom de l'image dans le cas contraire. Pour paraphraser le code ci-dessus en franÃ§ais: s'il existe une image de collection, afficher l'en-tÃªte de page Ã  propos (Ã  laquelle on se rÃ©fÃšre par _httppageabout_) et puis cette image; sinon afficher la solution de secours _imagecollectionv_.</Text>
+<Text id="710">Les macros peuvent prendre des arguments. Voici une autre dÃ©finition de la macro _imagecollection_, suivant immÃ©diatement la dÃ©finition donnÃ©e plus haut, dans le fichier base.dm:</Text>
+<CodeLine>_imagecollection_[v=1]{_imagecollectionv_}</CodeLine>
+<Text id="711">L'argument [v=1] spÃ©cifie qu'il faut utiliser cette deuxiÃšme dÃ©finition quand Greenstone fonctionne en mode texte seul. Les macros de langue fonctionnent de maniÃšre similaireÂ --Â Ã  l'exception du fichier english.dm, qui est le fichier utilisÃ© par dÃ©faut, toutes les macros de langue spÃ©cifient leur langue en argument. Par exemple:</Text>
+<CodeLine>_textimagehome_ {Home Page}</CodeLine>
+<Text id="712">apparaÃ®t dans le fichier de macros pour la langue anglaise, alors que la version allemande est:</Text>
+<CodeLine>_textimagehome_ [l=de] {Hauptaseite}</CodeLine>
+<Text id="713">Les versions anglaise et allemande se trouvent dans le mÃªme paquetage, bien qu'elles soient stockÃ©es dans des fichiers sÃ©parÃ©s (les dÃ©finitions de paquetages peuvent occuper plusieurs fichiers). Greenstone utilise son argument l au moment de l'exÃ©cution pour dÃ©cider quelle langue afficher.</Text>
+<Figure id="part_of_the_aboutdm_macro_file">
+<Title>
+<Text id="714">Portion du fichier de macro about.dm</Text>
+</Title>
+<CodeLine>package about</CodeLine>
+<CodeLine>##############################################</CodeLine>
+<CodeLine># about page content</CodeLine>
+<CodeLine>###############################################</CodeLine>
+<CodeLine>_pagetitle_ {_collectionname_}</CodeLine>
+<CodeLine>_content_ {</CodeLine>
+<CodeLine>&lt;center&gt;</CodeLine>
+<CodeLine>_navigationbar_</CodeLine>
+<CodeLine>&lt;/center&gt;</CodeLine>
+<CodeLine>_query:queryform_</CodeLine>
+<CodeLine>&lt;p&gt;_iconblankbar_</CodeLine>
+<CodeLine>&lt;p&gt;_textabout_</CodeLine>
+<CodeLine>_textsubcollections_</CodeLine>
+<CodeLine>&lt;h3&gt;_help:textsimplehelpheading_&lt;/h3&gt;</CodeLine>
+<CodeLine>_help:simplehelp_</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine>_textabout_ {</CodeLine>
+<CodeLine>&lt;h3&gt;_textabcol_&lt;/h3&gt;</CodeLine>
+<CodeLine>_Global:collectionextra_</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="715">Comme dernier exemple, la figureÂ <CrossRef target="Figure" ref="part_of_the_aboutdm_macro_file"/> montre un extrait du fichier de macros about.dm, utilisÃ© pour gÃ©nÃ©rer la page Ã  propos de chaque collection. Elle montre la dÃ©finition de trois macros, _pagetitle_ (titre de page), _content_ (contenu), et _textabout_ (texte Â«Ã  propos de...Â»).</Text>
+</Content>
+</Subsection>
+<Subsection id="using_macros">
+<Title>
+<Text id="716">Utiliser les macros</Text>
+</Title>
+<Content>
+<Text id="717">Les macros sont puissantes, et peuvent sembler un peu obscures. Mais avec une bonne connaissance de HTML et un peu de pratique elles deviennent une maniÃšre rapide et facile de personnaliser votre site Greenstone.</Text>
+<Text id="718">Supposons par exemple que vous souhaitiez crÃ©er une page statique qui ressemble Ã  votre site Greenstone actuel. Vous pouvez crÃ©er un nouveau paquetage, que vous appellerez static par exemple, dans un nouveau fichier, et y redÃ©finir la macro _content_. Ajoutez ce nom de fichier dans GSDLHOME/etc/main.cfg, que Greenstone charge Ã  chaque fois qu'il est invoquÃ©. Vous accÃ©derez Ã  la nouvelle page en utilisant votre URL habituelle pour Greenstone et en lui ajoutant les arguments ?a=p&amp;p=static (on obtiendra par exemple l'URL complÃšte suivante:http://serveur/cgi-bin/library?a=p&amp;p=static).</Text>
+<Text id="719">Pour modifier l'apparence et l'ergonomie de Greenstone vous pouvez Ã©diter les paquetages base et style. Pour modifier la page d'accueil de Greenstone, Ã©ditez le paquetage home (ceci est dÃ©crit dans le Guide d'installation de la bibliothÃšque numÃ©rique Greenstone). Pour modifier la page de requÃªtes, Ã©ditez le fichier query.dm.</Text>
+<Text id="720">ExpÃ©rimentez sans crainte avec les macros. Les modifications apparaissent instantanÃ©ment, puisque les macros sont interprÃ©tÃ©es lors de l'affichage des pages. Le langage de macros est un outil puissant que vous pouvez utiliser pour vous approprier vraiment votre site Greenstone.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="the_packages_directory">
+<Title>
+<Text id="721">Le rÃ©pertoire packages</Text>
+</Title>
+<Content>
+<Table id="the_packages_directory_1">
+<Title>
+<Text id="722">Le rÃ©pertoire<i>packages</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="217">
+<Text id="723"><b>Paquetage</b></Text>
+</th>
+<th width="180">
+<Text id="724"><b>URL</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="725"><i>mg</i></Text>
+</th>
+<th width="217">
+<Text id="726">MG, abrÃ©viation de âManaging Gigabytesâ (gÃ©rer les giga-octets). Logiciel de compression, d'indexation et de recherche utilisÃ© pour gÃ©rer les donnÃ©es textuelles dans les collections de Greenstone.</Text>
+</th>
+<th width="180">
+<Text id="727"><i>www.citri.edu.au/mg</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="728"><i>wget</i></Text>
+</th>
+<th width="217">
+<Text id="729">Logiciel de miroir web utilisÃ© par Greenstone. Ãcrit en C++.</Text>
+</th>
+<th width="180">
+<Text id="730"><i>www.tuwien.ac.at/~prikryl/ wget.html</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="731"><i>w3mir</i></Text>
+</th>
+<th width="217">
+<Text id="732">Logiciel de miroir web Ã©crit en Perl. Ce n'est pas le programme de miroir web prÃ©fÃ©rÃ© par Greenstone car il repose sur une version spÃ©cifique mais dÃ©passÃ©e d'un certain module Perl (qui est distribuÃ© dans le rÃ©pertoire<i>w3mir</i>).</Text>
+</th>
+<th width="180">
+<Text id="733"><i>www.math.uio.no/~janl/w3mir</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="734"><i>windows</i></Text>
+</th>
+<th width="217">
+<Text id="735">Paquetages utilisÃ©s lors de l'exÃ©cution sous Windows.</Text>
+</th>
+<th width="180">
+<Text id="736"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="737"><i>windows/gdbm</i></Text>
+</th>
+<th width="217">
+<Text id="738">Version du gestionnaire de bases de donnÃ©es de GNU crÃ©Ã©e pour Windows. GDBM est fourni en standard sous Linux.</Text>
+</th>
+<th width="180">
+<Text id="739"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="740"><i>windows/crypt</i></Text>
+</th>
+<th width="217">
+<Text id="741">Programme de chiffrement utilisÃ© pour les mots de passe des fonctions administratives de Greenstone.</Text>
+</th>
+<th width="180">
+<Text id="742"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="743"><i>windows/stlport</i></Text>
+</th>
+<th width="217">
+<Text id="744">bibliothÃšque standard de patrons (<i>templates</i>), utilisÃ©e lors de la compilation de Greenstone avec certains compilateurs pour Windows.</Text>
+</th>
+<th width="180">
+<Text id="745"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="746"><i>wv</i></Text>
+</th>
+<th width="217">
+<Text id="747">Convertisseur du format Microsoft Word (pour construire des collections Ã  partir de documents Word), allÃ©gÃ©e pour Greenstone.</Text>
+</th>
+<th width="180">
+<Text id="748"><i>sourceforge.net/projects/wvware</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="749"><i>pdftohtml</i></Text>
+</th>
+<th width="217">
+<Text id="750">Convertisseur du format PDF utilisÃ© pour construire des collections Ã  partir de documents PDF.</Text>
+</th>
+<th width="180">
+<Text id="751"><i>www.ra.informatik.uni-stutt gart.de/~gosho/pdftohtml</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="752"><i>yaz</i></Text>
+</th>
+<th width="217">
+<Text id="753">Programme client Z39.50 utilisÃ© lors des expÃ©rimentations de recherche pour rendre Greenstone compatible Z39.50. Le fichier<i>README.gsdl</i>rend compte des progrÃšs Ã  ce sujet.</Text>
+</th>
+<th width="180">
+<Text id="754"><i>www.indexdata.dk</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="755">Le rÃ©pertoire packages (paquetages), dont le contenu est reprÃ©sentÃ© dans la tableÂ <CrossRef target="Table" ref="the_packages_directory_1"/>, est l'endroit de stockage de tout le code utilisÃ© par Greenstone mais Ã©crit par des tiers ou d'autres Ã©quipes de recherche. Tout le logiciel distribuÃ© avec Greenstone a Ã©tÃ© publiÃ© sous la licence publique gÃ©nÃ©rale de GNU (GPL). Les exÃ©cutables produits par ces paquetages sont placÃ©s dans le rÃ©pertoire bin de Greenstone. Chaque paquetage est stockÃ© dans son propre rÃ©pertoire. Les diffÃ©rents paquetages ont des fonctions trÃšs diverses, allant de l'indexation et de la compression Ã  la conversion de documents du format Microsoft Word en HTML. Chaque paquetage dispose d'un fichier README (lisez-moi) qui fournit des informations complÃ©mentaires le concernant.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="the_greenstone_runtime_system">
+<Title>
+<Text id="756">Le systÃšme d'exÃ©cution de Greenstone</Text>
+</Title>
+<Content>
+<Text id="757">Le prÃ©sent chapitre dÃ©crit le systÃšme d'exÃ©cution de Greenstone pour que vous puissiez comprendre, augmenter et Ã©tendre ses fonctionnalitÃ©s. Le logiciel est Ã©crit en C++ est utilise intensivement l'hÃ©ritage virtuel. Si vous ne connaissez pas bien ce langage il est prÃ©fÃ©rable que vous l'appreniez avant de continuer la lecture. Deitel et Deitel (1994) proposent un didacticiel complet, mais la rÃ©fÃ©rence incontournable est le Stroustrup (1997).</Text>
+<Text id="758">Nous commenÃ§ons par expliquer la philosophie de la conception qui a sous-tendu le systÃšme d'exÃ©cution car elle a des consÃ©quences importantes sur l'implÃ©mentation. Nous fournissons ensuite les dÃ©tails d'implÃ©mentation, qui forment la partie principale de ce chapitre. La version de Greenstone dÃ©crite ici est la version CGI (ou version BibliothÃšque Web pour les utilisateurs de Windows). La version BibliothÃšque locale utilise le mÃªme code source mais dispose en frontal d'un serveur web intÃ©grÃ©. C'est Ã©galement un processus persistent.</Text>
+<Section id="process_structure">
+<Title>
+<Text id="759">Structure des processus</Text>
+</Title>
+<Content>
+<Figure id="overview_of_a_general_greenstone_system">
+<Title>
+<Text id="760">Vue d'ensemble d'un systÃšme Greenstone gÃ©nÃ©rique</Text>
+</Title>
+<File width="382" height="335" url="images/Dev_Fig_20.png"/>
+</Figure>
+<Text id="761">La figureÂ <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/> montre plusieurs utilisateurs, reprÃ©sentÃ©s par des terminaux informatiques en haut du diagramme, en train d'accÃ©der Ã  trois collections Greenstone. Avant d'Ãªtre mises en ligne, ces collections subissent les processus d'import et de construction dÃ©crits dans les chapitres prÃ©cÃ©dents. Tout d'abord, les documents, reprÃ©sentÃ©s en bas de la figure, sont importÃ©s dans le format d'archivage de Greenstone, qui est compatible XML. Les fichiers d'archives servent ensuite Ã  la construction de plusieurs index de recherche et d'une base de donnÃ©es d'informations de la collection comprenant les structures hiÃ©rarchiques permettant la navigation. La collection est alors prÃªte Ã  Ãªtre mise en ligne et Ã  rÃ©pondre Ã  des requÃªtes d'informations.</Text>
+<Text id="762">Deux composants sont centraux dans la conception du systÃšme d'exÃ©cution: les Â«rÃ©ceptionnistesÂ» et les Â«serveurs de collectionÂ». Du point de vue de l'utilisateur, un rÃ©ceptionniste est le point de contact avec la bibliothÃšque numÃ©rique. Il accepte les donnÃ©es fournies par l'utilisateur, gÃ©nÃ©ralement sous la forme de saisies au clavier et de clics de souris; il les analyse; et il Ã©met ensuite une requÃªte au(x) serveur(s) de collection appropriÃ©s. Ce dernier localise l'information recherchÃ©e et la renvoie au rÃ©ceptionniste pour que ce dernier la prÃ©sente Ã  l'utilisateur. Les serveurs de collection se comportent comme un mÃ©canisme abstrait qui gÃšre le contenu de la collection, alors que les rÃ©ceptionnistes gÃšrent l'interface utilisateur.</Text>
+<Figure id="greenstone_system_using_the_null_protocol">
+<Title>
+<Text id="763">SystÃšme Greenstone utilisant le Â«protocole videÂ»</Text>
+</Title>
+<File width="329" height="424" url="images/Dev_Fig_21.png"/>
+</Figure>
+<Text id="764">Comme illustrÃ© dans la figureÂ <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/>, les rÃ©ceptionnistes communiquent avec les serveurs de collection en utilisant un protocole dÃ©fini. L'implÃ©mentation de ce protocole dÃ©pend de l'ordinateur et de la configuration du systÃšme de bibliothÃšque numÃ©rique. Le cas le plus frÃ©quent et le plus simple est celui d'un rÃ©ceptionniste et d'un serveur de collection, fonctionnant tous deux sur le mÃªme ordinateur. C'est ce qui est produit par l'installation par dÃ©faut de Greenstone. Les deux processus sont alors combinÃ©s dans un unique exÃ©cutable (appelÃ© library), et le protocole se rÃ©duit par consÃ©quent Ã  des appels de fonctions. C'est ce que nous appelons le<i>protocole vide</i>(null protocol). C'est la base des systÃšmes de bibliothÃšque numÃ©rique Greenstone clef en main. Cette configuration simplifiÃ©e est illustrÃ©e figureÂ <CrossRef target="Figure" ref="greenstone_system_using_the_null_protocol"/>, oÃ¹ le rÃ©ceptionniste, le protocole et le serveur de collection sont regroupÃ©s sous la forme d'une unique entitÃ©, le programme library. Le prÃ©sent chapitre a pour but d'expliquer son fonctionnement.</Text>
+<Text id="765">Un Â«serveurÂ» est habituellement un processus persistent qui, une fois dÃ©marrÃ©, fonctionne indÃ©finiment, en rÃ©pondant aux requÃªtes entrantes. MalgrÃ© son nom, cependant, le serveur de collection dans la configuration du protocole vide n'est pas un serveur au sens habituel. En fait, Ã  chaque requÃªte d'une page web de Greenstone, le programme library est dÃ©marrÃ© (par le mÃ©canisme CGI), rÃ©pond Ã  la requÃªte, et quitte. Nous n'appelons le serveur de collection Â«serveurÂ» que parce qu'il est Ã©galement conÃ§u pour fonctionner dans la configuration plus gÃ©nÃ©rale de la figureÂ <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/>.</Text>
+<Text id="766">De maniÃšre surprenante, ce cycle de dÃ©marrage, traitement, et fin d'exÃ©cution n'est pas aussi lent qu'on pourrait le craindre, et le service fourni est parfaitement utilisable. Il est clair cependant que ce systÃšme est inefficace. Un mÃ©canisme appelÃ© Fast-CGI (www.fastcgi.com) fournit un compromis. Si on l'utilise, le programme library demeure en mÃ©moire aprÃšs la premiÃšre exÃ©cution, et les lots suivants d'arguments CGI lui sont communiquÃ©s, ce qui Ã©vite les surcharges d'initialisation, et ressemble beaucoup Ã  un serveur au sens classique. Fast-CGI est une option dans Greenstone, que l'on active en recompilant le code source de Greenstone avec les bibliothÃšques appropriÃ©es.</Text>
+<Text id="767">Pour fournir un autre choix que le protocole vide, nous avons Ã©galement dÃ©veloppÃ© le protocole Greenstone en utilisant le cÃ©lÃšbre systÃšme CORBA (Slama<i>et al.</i>, 1999). Il utilise un paradigme orientÃ© objet unifiÃ© pour activer diffÃ©rents processus, fonctionnant sur diffÃ©rentes plates-formes, et implÃ©mentÃ©s en diffÃ©rents langages de programmation, pour accÃ©der au mÃªme ensemble d'objets distribuÃ©s sur l'Internet (ou tout autre rÃ©seau). Des scÃ©narios comme celui de la figureÂ <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/> peuvent ensuite Ãªtre entiÃšrement implÃ©mentÃ©s, avec des rÃ©ceptionnistes et des serveurs de collection fonctionnant sur des ordinateurs diffÃ©rents.</Text>
+<Figure id="graphical_query_interface_to_greenstone">
+<Title>
+<Text id="768">Interface graphique de requÃªtes de Greenstone</Text>
+</Title>
+<File width="397" height="348" url="images/Dev_Fig_22.png"/>
+</Figure>
+<Text id="769">Ceci permet la mise en place d'interfaces bien plus sophistiquÃ©es pour mettre en place exactement les mÃªmes collections de bibliothÃšques numÃ©riques. Un exemple parmi tant d'autres, la figureÂ <CrossRef target="Figure" ref="graphical_query_interface_to_greenstone"/> reprÃ©sente une interface graphique de requÃªtes, fondÃ©e sur des diagrammes de Venn, qui permet aux utilisateurs de manipuler directement des requÃªtes boolÃ©ennes. Ãcrite en Java, cette interface fonctionne localement, sur l'ordinateur de l'utilisateur. Utilisant CORBA, elle accÃšde Ã  un serveur de collection Greenstone distant, Ã©crit en C++.</Text>
+<Text id="770">Ce protocole distribuÃ© faisant toujours l'objet de recherches en raffinement et utilisabilitÃ©, le prÃ©sent manuel ne le dÃ©taillera pas davantage (voir Bainbridge<i>et al.</i>, 2001, pour des informations complÃ©mentaires Ã  ce sujet). </Text>
+</Content>
+</Section>
+<Section id="conceptual_framework">
+<Title>
+<Text id="771">Cadre conceptuel</Text>
+</Title>
+<Content>
+<Figure id="generating_the_about_this_collection_page">
+<Title>
+<Text id="772">GÃ©nÃ©ration de la page Â«Ã  proposÂ»</Text>
+</Title>
+<File width="398" height="354" url="images/Dev_Fig_23.png"/>
+</Figure>
+<Text id="773">La figureÂ <CrossRef target="Figure" ref="generating_the_about_this_collection_page"/> reprÃ©sente la page Â«Ã  proposÂ» d'une collection Greenstone particuliÃšre (la collection du projet Gutenberg). Examinez l'URL au sommet de la figure: cette page est gÃ©nÃ©rÃ©e par l'exÃ©cution du programme CGI library, qui est l'exÃ©cutable mentionnÃ© plus haut, comprenant Ã  la fois le rÃ©ceptionniste et le serveur de collection, reliÃ©s entre eux par le protocole vide. Les arguments passÃ©s au programme library sont c=gberg, a=p, et p=about. On peut les interprÃ©ter comme suit:</Text>
+<Indented>
+<Text id="774"><i>Pour la collection du projet Gutenberg (c=gberg), l'action est de gÃ©nÃ©rer une page (a=p), et la page Ã  gÃ©nÃ©rer s'appelle aboutÂ --Â Ã  propos de ...Â --Â (p=about).</i></Text>
+</Indented>
+<Figure id="greenstone_runtime_system">
+<Title>
+<Text id="775">SystÃšme d'exÃ©cution de Greenstone</Text>
+</Title>
+<File width="534" height="345" url="images/Dev_Fig_24.png"/>
+</Figure>
+<Text id="776">La figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/> illustre les portions principales du systÃšme d'exÃ©cution de Greenstone. Au sommet, le rÃ©ceptionniste initialise d'abord ses composants, puis analyse les arguments CGI pour savoir quelle action appeler. Lors de l'exÃ©cution de l'action (ce qui comprend d'autres traitements des arguments CGI), le logiciel utilise le protocole pour accÃ©der au contenu de la collection. La rÃ©ponse est utilisÃ©e pour gÃ©nÃ©rer une page web, avec l'aide du composant de mise en forme et du langage de macros.</Text>
+<Text id="777">Le langage de macros, que nous avons rencontrÃ© sectionÂ <CrossRef target="Section" ref="controlling_the_greenstone_user_interface"/>, fournit un systÃšme de bibliothÃšque numÃ©rique Greenstone d'un style consistant, et permet de crÃ©er des interfaces dans diffÃ©rentes langues. L'interaction avec la bibliothÃšque fournit les squelettes des pages web; les macros du rÃ©pertoire GSDLHOME/macros leur donnent chair.</Text>
+<Text id="778">L'objet de langage de macros reprÃ©sentÃ© figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/> a pour rÃŽle de lire ces fichiers et de stocker le rÃ©sultat de l'analyse en mÃ©moire. Toute action peut utiliser cet objet pour dÃ©velopper une macro. On peut mÃªme crÃ©er de nouvelles dÃ©finitions de macros pour en Ã©craser d'anciennes, ce qui ajoute une dimension dynamique Ã  l'utilisation des macros.</Text>
+<Text id="779">La reprÃ©sentation de la page Â«Ã  proposÂ» (figureÂ <CrossRef target="Figure" ref="generating_the_about_this_collection_page"/>) est connue avant l'exÃ©cution, et consignÃ©e dans le fichier de macros about.dm. Les en-tÃªtes, les pieds, et l'image de fond n'y sont mÃªme pas mentionnÃ©s car ils se trouvent dans le paquetage de macros global. Cependant, le texte spÃ©cifique d'Â«Ã  proposÂ» d'une collection particuliÃšre n'est pas connu d'avance; il est stockÃ© dans la base de donnÃ©es d'informations de la collection lors du processus de construction. Cette information, rapatriÃ©e Ã  l'aide du protocole, est stockÃ©e sous _collectionextra_ dans le paquetage de macros global. Vous remarquerez que ce nom de macro ressemble presque exactement au nom utilisÃ© pour exprimer cette information dans le fichier de configuration de collection dÃ©crit sectionÂ <CrossRef target="Section" ref="configuration_file"/>. Pour gÃ©nÃ©rer le contenu de la page, la macro _content_ (contenu) du paquetage about (prÃ©sentÃ© figureÂ <CrossRef target="Figure" ref="part_of_the_aboutdm_macro_file"/>) est dÃ©veloppÃ©e, ce qui Ã  son tour dÃ©veloppe _textabout_ (texte d'Ã  propos), qui accÃšde Ã  la macro _collectionextra_, qui venait d'Ãªtre placÃ©e lÃ  de faÃ§on dynamique.</Text>
+<Text id="780">Un autre ingrÃ©dient important est l'objet de mise en forme, ou formatage. Les instructions de mise en forme du fichier de configuration de collection affectent la prÃ©sentation de portions particuliÃšres de la collection, comme nous l'avons expliquÃ© sectionÂ <CrossRef target="Section" ref="formatting_greenstone_output"/>. Elles sont gÃ©rÃ©es par l'objet de mise en forme reprÃ©sentÃ© figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/>. La tÃ¢che principale de cet objet est d'analyser et d'Ã©valuer des instructions telles que les chaÃ®nes de formatage de la figureÂ <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>. Comme nous l'avons vu en sectionÂ <CrossRef target="Section" ref="formatting_greenstone_output"/>, de telles chaÃ®nes peuvent comprendre des rÃ©fÃ©rences Ã  des mÃ©ta-donnÃ©es entre crochets (comme par exemple [Title] pour le titre), qu'il faut ensuite rapatrier du serveur de collection. Les objets de mise en forme et de langage de macros interagissent, car les instructions de formatage peuvent comprendre des macros qui, une fois dÃ©veloppÃ©es, incluent des mÃ©ta-donnÃ©es, qui une fois dÃ©veloppÃ©es incluent des macros, etc.</Text>
+<Text id="781">Le serveur de collection, au bas de la figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/>, connaÃ®t lui aussi une phase d'initialisation, prÃ©parant les objets filtre et source pour rÃ©pondre Ã  des requÃªtes entrantes fournies selon le protocole, et un objet de recherche pour les assister dans cette tÃ¢che. Les objets de recherche accÃšdent en fin de chaÃ®ne aux index et Ã  la base de donnÃ©es d'informations de la collection, tous crÃ©Ã©s lors de la construction de la collection.</Text>
+<Text id="782">Si on ne compte pas les lignes vides, le rÃ©ceptionniste contient 15Â 000 lignes de code. Le serveur de collection en compte 5Â 000, dont les trois quarts correspondent Ã  des fichiers d'en-tÃªtes. Le serveur de collection est plus compact car le rapatriement de donnÃ©es se fait Ã  travers deux programmes prÃ©-compilÃ©s. MG, un systÃšme de rapatriement dans le corps du texte, sert Ã  la recherche, et GDBM, un systÃšme de gestion de bases de donnÃ©es, renferme la base de donnÃ©es d'informations de la collection.</Text>
+<Text id="783">Pour encourager extensibilitÃ© et souplesse, Greenstone utilise largement l'hÃ©ritageÂ --Â en particulier dans les objets d'action, de filtre, de source, et de recherche. Pour une simple bibliothÃšque numÃ©rique ne contenant que des collections textuelles, ceci signifie qu'il vous faudra en apprendre un peu plus pour programmer le systÃšme. Mais cela signifie aussi qu'on pourrait facilement remplacer MG et GDBM si le besoin devait un jour s'en faire sentir. De plus, l'architecture du logiciel est assez riche pour accepter toutes les fonctionnalitÃ©s multimÃ©dia, telles que le contrÃŽle de l'interface par des systÃšmes de reconnaissance vocale, ou la soumission de requÃªtes sous la forme d'images dessinÃ©es.</Text>
+</Content>
+</Section>
+<Section id="how_the_conceptual_framework_fits_together">
+<Title>
+<Text id="784">Agencement du cadre conceptuel</Text>
+</Title>
+<Content>
+<Text id="785">Les sectionsÂ <CrossRef target="Section" ref="collection_server"/> etÂ <CrossRef target="Section" ref="receptionist"/> dÃ©taillent le fonctionnement du serveur de collection et du rÃ©ceptionniste, en passant plus de temps sur chacun des modules de la figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/> et en dÃ©crivant leur implÃ©mentation. Il est utile de commencer par travailler sur des exemples d'interaction utilisateur avec Greenstone et de dÃ©crire ce qui se passe en coulisses. Nous supposerons pour le moment que tous les objects sont correctement initialisÃ©s. L'initialisation est une procÃ©dure assez compliquÃ©e, que nous revisiterons dans la sectionÂ <CrossRef target="Section" ref="initialisation"/>.</Text>
+<Subsection id="performing_a_search">
+<Title>
+<Text id="786">Effectuer une recherche</Text>
+</Title>
+<Content>
+<Figure id="searching_gutenberg_for_darcy">
+<Title>
+<Text id="787">Recherche de Â«DarcyÂ» dans le projet Gutenberg</Text>
+</Title>
+<File width="396" height="353" url="images/Dev_Fig_25.png"/>
+</Figure>
+<Text id="788">Quand un utilisateur effectue une requÃªte en pressant le boutton DÃ©marrer la recherche sur la page de recherche, une nouvelle action de Greenstone est invoquÃ©e, qui aboutit Ã  la gÃ©nÃ©ration d'une nouvelle page HTML Ã  l'aide du langage de macros. La figureÂ <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/> montre le rÃ©sultat de la recherche dans la collection du projet Gutenberg du nom Darcy. La page de recherche comprenait originellement l'instruction a=q cachÃ©e dans le HTML. Cette instruction est activÃ©e lorsque le bouton de recherche est enfoncÃ©, et appelle l'action queryaction. L'exÃ©cution de queryaction effectue un appel Ã  l'objet de filtre de la collection (c=gberg) Ã  travers le protocole.</Text>
+<Text id="789">Les filtres sont une fonction de base importante des serveurs de collection. AdaptÃ©s aux activitÃ©s de recherche et de navigation, ils fournissent une maniÃšre de sÃ©lectionner un sous-ensemble d'informations dans la collection. Dans le cas prÃ©sent, queryaction met en place une requÃªte de filtre en:</Text>
+<BulletList>
+<Bullet>
+<Text id="790">plaÃ§ant le type de requÃªte de filtre Ã  QueryFilter (filtre de requÃªte; la sectionÂ <CrossRef target="Section" ref="collection_server"/> dÃ©crit les diffÃ©rents types de filtres);</Text>
+</Bullet>
+<Bullet>
+<Text id="791">stockant les prÃ©fÃ©rences de recherche de l'utilisateurÂ --Â sensibilitÃ© Ã  la casse, troncature et autresÂ --Â dans la requÃªte de filtre;</Text>
+</Bullet>
+<Bullet>
+<Text id="792">appelant la fonction filter() (filtre) Ã  travers le protocole vide.</Text>
+</Bullet>
+</BulletList>
+<Text id="793">Les appels du protocole sont synchrones: le rÃ©ceptionniste est effectivement bloquÃ© tant que la requÃªte de filtre n'a pas Ã©tÃ© traitÃ©e par le serveur de collection et que les donnÃ©es gÃ©nÃ©rÃ©es n'ont pas Ã©tÃ© renvoyÃ©es.</Text>
+<Text id="794">Lors d'un appel de protocole de type QueryFilter, l'objet de filtre (de la figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/>) dÃ©code les options et effectue un appel Ã  l'objet de recherche, qui utilise MG pour la recherche proprement dite. L'objet de recherche a pour rÃŽle de fournir une interface abstraite de programme qui permet la recherche, indÃ©pendamment de l'outil de recherche utilisÃ© de faÃ§on sous-jacente. Le format utilisÃ© pour le renvoi des rÃ©sultats utilise lui aussi l'abstraction, ce qui oblige l'objet de recherche Ã  traduire les donnÃ©es gÃ©nÃ©rÃ©es par l'outil de recherche sous une forme standard.</Text>
+<Text id="795">Lorsque les rÃ©sultats de la recherche ont Ã©tÃ© renvoyÃ©s au rÃ©ceptionniste, la suite des Ã©vÃ©nements consiste Ã  mettre en forme les rÃ©sultats pour les afficher, en utilisant les objets de mise en forme et de langage de macros. Comme le montre la figureÂ <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/>, ceci suppose de gÃ©nÃ©rer l'en-tÃªte, le pied de page, la barre de navigation et le fond de page standard de Greenstone; de rÃ©pÃ©ter la partie principale de la page de requÃªtes juste en dessous de la barre de navigation; et d'afficher une icone de livre ainsi que le titre et l'auteur pour chacun des rÃ©sultats de la recherche. La mise en forme de cette derniÃšre partie est dictÃ©e par l'instruction format SearchVList du fichier de configuration de collection. Avant qu'on puisse afficher les mÃ©ta-donnÃ©es de titre et d'auteur, il faut les rapatrier depuis le serveur de collection, ce qui suppose des appels supplÃ©mentaires Ã  travers le protocole, en utilisant cette fois BrowseFilter (filtre de navigation).</Text>
+</Content>
+</Subsection>
+<Subsection id="retrieving_a_document">
+<Title>
+<Text id="796">Rapatrier un document</Text>
+</Title>
+<Content>
+<Text id="797">Ã la suite de la requÃªte prÃ©cÃ©dente pour Darcy, voyons ce qui se passe lors de l'affichage d'un document. La figureÂ <CrossRef target="Figure" ref="the_golf_course_mystery"/> montre ce qui se passe quand on clique sur l'icone jouxtant le titre The Golf Course Mystery (le mystÃšre du parcours de golf) dans la figureÂ <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/>.</Text>
+<Figure id="the_golf_course_mystery">
+<Title>
+<Text id="798">The Golf Course Mystery (le mystÃšre du parcours de golf)</Text>
+</Title>
+<File width="393" height="349" url="images/Dev_Fig_26.png"/>
+</Figure>
+<Text id="799">Le texte source de la collection Gutenberg consiste en un long fichier par livre. Au moment de la construction, ces fichiers sont ventilÃ©s sous forme de pages diffÃ©rentes environ toutes les 200 lignes, et les informations relatives Ã  chaque page sont stockÃ©es dans les index et la base de donnÃ©es d'informations de la collection. Au sommet de la figureÂ <CrossRef target="Figure" ref="the_golf_course_mystery"/> on constate que ce livre comprend 104 pages engendrÃ©es automatiquement, et on remarque juste en dessous le dÃ©but de la premiÃšre page: le copiste, le titre, l'auteur, et le dÃ©but d'une table des matiÃšres (qui fait partie du texte source de Gutenberg; elle n'a pas Ã©tÃ© engendrÃ©e par Greenstone). En haut Ã  gauche on trouve des boutons qui contrÃŽlent la mise en forme du document: une seule page ou tout le document; s'il faut mettre en valeur le terme de la requÃªte ou non; et s'il faut que le livre soit ou non affichÃ© dans sa propre fenÃªtre, dÃ©tachÃ©e des activitÃ©s principales de recherche et de navigation. En haut Ã  droite on trouve une aide Ã  la navigation qui propose un accÃšs direct Ã  n'importe quelle page du livre: il suffit de taper le numÃ©ro de la page et d'enfoncer le bouton Â«aller Ã  la pageÂ». On peut aussi se rendre aux pages prÃ©cÃ©dente ou suivante en cliquant sur les icones de flÃšches aux cÃŽtÃ©s de l'outil de sÃ©lection de page.</Text>
+<Text id="800">L'action de rapatriement des documents, documentaction, est spÃ©cifiÃ©e par a=d et elle accepte quelques arguments supplÃ©mentaires. Le plus important est le document Ã  rapatrier: il est spÃ©cifiÃ© par la variable d. Dans la figureÂ <CrossRef target="Figure" ref="the_golf_course_mystery"/>, il a la valeur<i>d=HASH51e598821ed6cbbdf0942b.1</i>pour rapatrier la premiÃšre page du document d'identifiant<i>HASH51e598821ed6cbbdf0942b</i>qui s'appelle aussi, de maniÃšre plus agrÃ©able, The Golf Course Mystery (le mystÃšre du parcours de golf). Il existe d'autres variables, spÃ©cifiant s'il faut ou non mettre en valeur le terme de la requÃªte (hl, pour highlighting) et quelle page du livre afficher (gt). Ces variables permettent de proposer les fonctionnalitÃ©s offertes par les boutons prÃ©sentÃ©s sur la page web de la figureÂ <CrossRef target="Figure" ref="the_golf_course_mystery"/>, et dÃ©crits ci-dessus. Si l'une de ces variables manque Ã  l'appel, c'est le comportement par dÃ©faut correspondant qui sera utilisÃ©.</Text>
+<Text id="801">Cette action suit une procÃ©dure similaire Ã  celle de queryaction: Ã©valuation des arguments CGI, accÃšs au serveur de collection en utilisant le protocole, et utilisation du rÃ©sultat pour engendrer une page web. Les options relatives au document sont dÃ©codÃ©es Ã  partir des arguments CGI et stockÃ©es dans l'objet pour plus tard. Pour rapatrier le document depuis le serveur de collection, on n'a besoin que de l'identifiant de document pour effectuer l'appel de protocole Ã  get_document() (obtenir le document). AprÃšs l'envoi du texte, un travail considÃ©rable de remise en forme est nÃ©cessaire. Pour ce faire, le code de documentaction accÃšde aux arguments stockÃ©s dans l'objet et utilise les objets de mise en forme et de langage de macros.</Text>
+</Content>
+</Subsection>
+<Subsection id="browsing_a_hierarchical_classifier">
+<Title>
+<Text id="802">Navigation dans un classificateur hiÃ©rarchique</Text>
+</Title>
+<Content>
+<Text id="803">La figureÂ <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/> montre un exemple de navigation, oÃ¹ l'utilisateur a choisi titres A-Z et choisi le lien hypertexte de la lettre K. C'est Ã©galement documentaction qui gÃšre cela, ce qu'on constate en observant l'argument CGI a=d, comme prÃ©cÃ©demment. Cependant, alors qu'auparavant la requÃªte CGI comprenait une variable d, il n'y en a aucune cette fois-ci. Ã la place, le noeud Ã  afficher pour navigation dans la hiÃ©rarchie de classification est spÃ©cifiÃ© dans la variable cl. Dans notre cas, ceci reprÃ©sente les titres groupÃ©s sous la lettre K. Cette liste a Ã©tÃ© formÃ©e au moment de la construction et fut stockÃ©e dans la base de donnÃ©es d'informations de la collection.</Text>
+<Figure id="browsing_titles_in_the_gutenberg_collection">
+<Title>
+<Text id="804">Navigation dans les titres de la collection Gutenberg</Text>
+</Title>
+<File width="394" height="351" url="images/Dev_Fig_27.png"/>
+</Figure>
+<Text id="805">Les enregistrements reprÃ©sentant des noeuds de classificateur dans la base de donnÃ©es utilisent le prÃ©fixe CL, suivi de nombres sÃ©parÃ©s par des points (.) pour dÃ©signer oÃ¹ ils rÃ©sident au sein de la structure rÃ©cursive. Si on ignore le bouton de recherche, situÃ© tout Ã  gauche de la barre de navigation, les classificateurs sont numÃ©rotÃ©s sÃ©quentiellement et par ordre croissant, de gauche Ã  droite, en commenÃ§ant Ã  1. Ainsi, le noeud de classificateur de premier niveau pour les titres dans notre exemple est CL1 et la page recherchÃ©e est engendrÃ©e en positionnant cl=CL1.11. On peut observer cela dans l'URL au sommet de la figureÂ <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/>.</Text>
+<Text id="806">Lors du traitement d'une requÃªte de document de type cl, l'objet de filtre est utilisÃ© pour rapatrier le noeud Ã  travers le protocole. Selon les donnÃ©es renvoyÃ©es, d'autres appels de protocole sont effectuÃ©s pour rapatrier les mÃ©ta-donnÃ©es des documents. Dans le cas prÃ©sent, ce sont les titres des livres qui sont rapatriÃ©s. Mais si le noeud avait Ã©tÃ© un noeud interne dont les fils avaient eux-mÃªmes Ã©tÃ© des noeuds, les titres des noeuds fils auraient eux aussi Ã©tÃ© rapatriÃ©s. Du point de vue du code cela revient Ã  la mÃªme chose, et c'est gÃ©rÃ© par le mÃªme mÃ©canisme.</Text>
+<Text id="807">Enfin, toutes les informations rapatriÃ©es sont reliÃ©es les unes aux autres Ã  l'aide du langage de macros, pour produire la page web reprÃ©sentÃ©e figureÂ <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/>.</Text>
+</Content>
+</Subsection>
+<Subsection id="generating_the_home_page">
+<Title>
+<Text id="808">GÃ©nÃ©ration de la page d'accueil</Text>
+</Title>
+<Content>
+<Figure id="greenstone_home_page">
+<Title>
+<Text id="809">Page d'accueil de Greenstone</Text>
+</Title>
+<File width="397" height="393" url="images/Dev_Fig_28.png"/>
+</Figure>
+<Text id="810">Comme dernier exemple, examinons le cas de la gÃ©nÃ©ration de la page d'accueil de Greenstone. La figureÂ <CrossRef target="Figure" ref="greenstone_home_page"/> montreÂ --Â dans le cas de l'installation par dÃ©faut de GreenstoneÂ --Â la page d'accueil aprÃšs l'installation de certaines collections de test. Son URL, qu'on peut voir au sommet de la capture d'Ã©cran, comprend les arguments a=p et p=home. Ainsi, Ã  l'instar de la page Â«Ã  proposÂ», elle a Ã©tÃ© engendrÃ©e par pageaction (a=p), mais dans le cas prÃ©sent la page Ã  produire est la page homeÂ --Â accueilÂ --Â (p=home). Le langage de macros accÃšde par consÃ©quent au fichier home.dm. Nul besoin de spÃ©cifier une collection (Ã  l'aide de la variable c) dans le cas prÃ©sent.</Text>
+<Text id="811">La page d'accueil a pour but de prÃ©senter les collections disponibles. Cliquer sur une icone emmÃšne l'utilisateur sur la page Ã  propos de la collection choisie. Le menu des collections est gÃ©nÃ©rÃ© automatiquement Ã  chaque chargement de la page, en se fondant sur les collections prÃ©sentes dans le systÃšme de fichiers Ã  ce moment-lÃ . Quand une nouvelle collection est mise en ligne, elle apparaÃ®t automatiquement sur la page d'accueil lorsque cette page est rechargÃ©e ou rÃ©actualisÃ©e, pour peu que cette collection ait Ã©tÃ© spÃ©cifiÃ©e comme Â«publiqueÂ».</Text>
+<Text id="812">Pour ce faire, le rÃ©ceptionniste utilise, Ã©videmment, le protocole. Dans le cadre de l'Ã©valuation des arguments CGI, pageaction est programmÃ© pour dÃ©tecter le cas particulier p=home. L'action utilise alors get_collection_list() (obtenir la liste des collections), appel de protocole servant Ã  Ã©tablir l'ensemble actuel de collections mises en ligne. Pour chacune de ces collections il appelle get_collectinfo() (obtenir les informations de collection) pour recevoir les informations la concernant. Ces informations prÃ©cisent si la collection est publiquement disponible, quelle est l'URL menant Ã  l'icone de la collection (si une telle icone existe), et le nom complet de la collection, et elles sont utilisÃ©es pour gÃ©nÃ©rer l'entrÃ©e appropriÃ©e sur la page d'accueil de la collection.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="source_code">
+<Title>
+<Text id="813">Code source</Text>
+</Title>
+<Content>
+<Table id="standalone_programs_included_in_greenstone">
+<Title>
+<Text id="814">Programmes indÃ©pendants inclus dans Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="815"><i>setpasswd/</i></Text>
+</th>
+<th width="397">
+<Text id="816">Support des mots de passe sous Windows.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="817"><i>getpw/</i></Text>
+</th>
+<th width="397">
+<Text id="818">Support des mots de passe sous Unix.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="819"><i>txt2db/</i></Text>
+</th>
+<th width="397">
+<Text id="820">Convertit un format de texte ASCII Ã  la XML en le format de la base de donnÃ©es de GNU.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="821"><i>db2txt/</i></Text>
+</th>
+<th width="397">
+<Text id="822">Convertit le format de la base de donnÃ©es de GNU en un format de texte ASCII Ã  la XML.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="823"><i>phind/</i></Text>
+</th>
+<th width="397">
+<Text id="824">Outil de navigation hiÃ©rarchique dans les groupes de mots.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="825"><i>hashfile/</i></Text>
+</th>
+<th width="397">
+<Text id="826">Calcule un identifiant de document unique, fondÃ© sur le contenu du fichier.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="827"><i>mgpp/</i></Text>
+</th>
+<th width="397">
+<Text id="828">Version rÃ©-Ã©crite et mise Ã  jour du paquetage<i>Managing Gigabytes</i>(gÃ©rer les giga-octets), en C++.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="829"><i>w32server/</i></Text>
+</th>
+<th width="397">
+<Text id="830">Serveur de bibliothÃšque locale pour Windows.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="831"><i>checkis/</i></Text>
+</th>
+<th width="397">
+<Text id="832">Support spÃ©cifique pour l'installation de Greenstone sous Windows. </Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="833">Le code source du systÃšme d'exÃ©cution se trouve dans GSDLHOME/src. Il occupe deux sous-rÃ©pertoires, recpt pour le code du rÃ©ceptionniste, et colservr pour celui du serveur de collection. Greenstone fonctionne sur les systÃšmes Windows Ã  partir de la version 3.1, qui impose malheureusement une limite de huit caractÃšres sur les noms de fichiers et de rÃ©pertoires; c'est ce qui explique l'utilisation d'abrÃ©viations cryptiques telles que recpt et colservr. Les sous-rÃ©pertoires restants comprennent des outils indÃ©pendants, principalement utilisÃ©s en renfort du processus de construction. Ils sont listÃ©s dans la tableÂ <CrossRef target="Table" ref="standalone_programs_included_in_greenstone"/>.</Text>
+<Text id="834">Un autre rÃ©pertoire, GSDLHOME/lib, inclut des objets de bas niveau utilisÃ©s Ã  la fois par le rÃ©ceptionniste et par le serveur de collection. Ce code est dÃ©crit dans la sectionÂ <CrossRef target="Section" ref="common_greenstone_types"/>.</Text>
+<Text id="835">Greenstone utilise Ã©normÃ©ment la bibliothÃšque standard de patrons (STL), une bibliothÃšque bibliothÃšque trÃšs rÃ©pandue de code C++, dÃ©veloppÃ©e par Silicon Graphics (www.sgi.com), et qui est l'aboutissement de nombreuses annÃ©es de conception et de dÃ©veloppement. Ã l'instar de toutes les bibliothÃšques de programmation, il faut un certain temps pour l'apprendre. L'annexeÂ AppendixA donne un bref aperÃ§u de ses principales portions utilisÃ©es tout au long du code de Greenstone. Pour une description plus dÃ©taillÃ©e, consultez le manuel de rÃ©fÃ©rence officiel de STL, disponible en ligne sur le site webwww.sgi.com, ou l'un des nombreux manuels traitant de STL, tel que celui de Josuttis (1999).</Text>
+</Content>
+</Section>
+<Section id="common_greenstone_types">
+<Title>
+<Text id="836">Types de base de Greenstone</Text>
+</Title>
+<Content>
+<Text id="837">Les objets dÃ©finis dans le rÃ©pertoire GSDLHOME/lib sont des objets de bas niveau de Greenstone, construits par-dessus STL, et qui sont utilisÃ©s tout au long du code source. Nous dÃ©taillons tout d'abord text_t, un objet utilisÃ© pour reprÃ©senter du texte Unicode. Nous rÃ©sumerons ensuite le but de chacun des fichiers de bibliothÃšque.</Text>
+<Subsection id="the_text_t_object">
+<Title>
+<Text id="838">L'objet text_t</Text>
+</Title>
+<Content>
+<Text id="839">Greenstone fonctionne avec de nombreuses langues, tant pour le contenu d'une collection que pour l'interface utilisateur. Pour gÃ©rer cela, nous avons utilisÃ© Unicode tout au long du code source, et l'objet sous-jacent qui rÃ©alise une chaÃ®ne Unicode s'appelle text_t.</Text>
+<Figure id="the_text_t_api" class="withLineNumber">
+<Title>
+<Text id="840">API de text_t (abrÃ©gÃ©e)</Text>
+</Title>
+<CodeLine>typedef vector&lt;unsigned short&gt; usvector;</CodeLine>
+<CodeLine/>
+<CodeLine>class text_t {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>usvector text;</CodeLine>
+<CodeLine>unsigned short encoding; // 0 = unicode, 1 = other</CodeLine>
+<CodeLine/>
+<CodeLine>public:</CodeLine>
+<CodeLine>   // constructors</CodeLine>
+<CodeLine>   text_t ();</CodeLine>
+<CodeLine>   text_t (int i);</CodeLine>
+<CodeLine>   text_t (char *s); // assumed to be a normal c string</CodeLine>
+<CodeLine/>
+<CodeLine>   void setencoding (unsigned short theencoding);</CodeLine>
+<CodeLine>   unsigned short getencoding ();</CodeLine>
+<CodeLine/>
+<CodeLine>   // STL container support</CodeLine>
+<CodeLine>   iterator begin ();</CodeLine>
+<CodeLine>   iterator end ();</CodeLine>
+<CodeLine/>
+<CodeLine>   void erase(iterator pos);</CodeLine>
+<CodeLine>   void push_back(unsigned short c);</CodeLine>
+<CodeLine>   void pop_back();</CodeLine>
+<CodeLine/>
+<CodeLine>   void reserve (size_type n);</CodeLine>
+<CodeLine/>
+<CodeLine>   bool empty () const {return text.empty();}</CodeLine>
+<CodeLine>   size_type size() const {return text.size();}</CodeLine>
+<CodeLine/>
+<CodeLine>   // added functionality</CodeLine>
+<CodeLine>   void clear ();</CodeLine>
+<CodeLine>   void append (const text_t &amp;t);</CodeLine>
+<CodeLine/>
+<CodeLine>   // support for integers</CodeLine>
+<CodeLine>   void appendint (int i);</CodeLine>
+<CodeLine>   void setint (int i);</CodeLine>
+<CodeLine>   int getint () const;</CodeLine>
+<CodeLine/>
+<CodeLine>   // support for arrays of chars</CodeLine>
+<CodeLine>   void appendcarr (char *s, size_type len);</CodeLine>
+<CodeLine>   void setcarr (char *s, size_type len);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="841">Unicode stocke chaque caractÃšre sur deux octets. La figureÂ <CrossRef target="Figure" ref="the_text_t_api"/> montre les fonctionnalitÃ©s principales de l'interface de programmation (API, pour Application Program Interface) de text_t. Les deux octets sont assurÃ©s par l'utilisation du type standard C++ short, dÃ©fini comme Ã©tant un entier sur deux octets. Le type de donnÃ©es central de l'objet text_t est un tableau dynamique de short non signÃ©s, construit par la dÃ©claration STL vector&lt;unsigned short&gt;, et baptisÃ© usvector (pour unsigned short vector).</Text>
+<Text id="842">Les fonctions de construction (lignes 10-12) gÃšrent explicitement trois formes d'initialisation: construction sans paramÃštres, qui engendre une chaÃ®ne Unicode vide; construction avec un paramÃštre entier, qui engendre une version texte Unicode de la valeur numÃ©rique fournie; et construction avec un paramÃštre char*, qui traite l'argument comme une chaÃ®ne C++ terminÃ©e par un caractÃšre nul et en gÃ©nÃšre une version Unicode.</Text>
+<Text id="843">Ensuite, la plus grande partie du code (lignes 17-28) s'occupe de maintenir un conteneur de type vecteur STL: begin() (dÃ©but), end() (fin), push_back() (remettre), empty() (vide), etc. On peut aussi effacer des chaÃ®nes, concatÃ©ner des chaÃ®nes, ainsi que convertir une valeur entiÃšre dans une chaÃ®ne de texte Unicode et renvoyer la valeur entiÃšre correspondant Ã  un texte qui reprÃ©sente un nombre.</Text>
+<Figure id="overloaded_operators_to_text_t" class="withLineNumber">
+<Title>
+<Text id="844">OpÃ©rateurs surchargÃ©s pour text_t</Text>
+</Title>
+<CodeLine>class text_t {</CodeLine>
+<CodeLine>   // ...</CodeLine>
+<CodeLine>   public:</CodeLine>
+<CodeLine>   text_t &amp;operator=(const text_t &amp;x);</CodeLine>
+<CodeLine>   text_t &amp;operator+= (const text_t &amp;t);</CodeLine>
+<CodeLine>   reference operator[](size_type n);</CodeLine>
+<CodeLine/>
+<CodeLine>   text_t &amp;operator=(int i);</CodeLine>
+<CodeLine>   text_t &amp;operator+= (int i);^ \\</CodeLine>
+<CodeLine>   text_t &amp;operator= (char *s);</CodeLine>
+<CodeLine>   text_t &amp;operator+= (char *s);</CodeLine>
+<CodeLine/>
+<CodeLine>   friend inline bool operator!=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator==(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&lt; (const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&gt; (const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&gt;=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&lt;=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   // ...</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="845">De nombreux opÃ©rateurs surchargÃ©s n'apparaissent pas dans la figureÂ <CrossRef target="Figure" ref="the_text_t_api"/>. Ils sont montrÃ©s dans la figureÂ <CrossRef target="Figure" ref="overloaded_operators_to_text_t"/> pour donner un avant-goÃ»t des opÃ©rations possibles. La ligne 4 permet l'affectation d'un objet text_t Ã  un autre, et la ligne 5 surcharge l'opÃ©rateur +=, pour fournir une maniÃšre plus naturelle de concatÃ©ner un objet text_t Ã  la fin d'un autre. Il est Ã©galement possible, Ã  travers la ligne 6, d'accÃ©der Ã  un caractÃšre Unicode particulier (reprÃ©sentÃ© sous la forme d'un short) en utilisant des indices de tableaux [ ]. On fournit aussi des opÃ©rateurs d'affectation et de concatÃ©nation pour les entiers et les chaÃ®nes C++. Les lignes 12-18 fournissent des opÃ©rateurs boolÃ©ens de comparaison de deux objets text_t: Ã©gale, diffÃ©rent de, prÃ©cÃšde alphanumÃ©riquement, etc.</Text>
+<Text id="846">Il existe aussi des fonctions membre qui prennent des arguments de type const au lieu d'arguments de type non-const, mais elles ne sont pas reprÃ©sentÃ©es ici. Une telle rÃ©pÃ©tition est habituelle dans des objets C++, ce qui augmente le code de l'API mais ne la rend pas plus grosse conceptuellement. En fait, de nombreuses fonctions sont implÃ©mentÃ©es sous la forme d'instructions tenant sur une ligne. Pour plus de dÃ©tails, reportez-vous au fichier source GSDLHOME/lib/text_t.h.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_greenstone_library_code">
+<Title>
+<Text id="847">Le code des bibliothÃšques Greenstone</Text>
+</Title>
+<Content>
+<Text id="848">Les fichiers d'en-tÃªtes du rÃ©pertoire GSDLHOME/lib comprennent un mÃ©lange de fonctions et d'objets qui fournissent un support utile au systÃšme d'exÃ©cution de Greenstone. LÃ  oÃ¹ l'efficacitÃ© prime, les fonctions et les fonctions membre sont dÃ©clarÃ©es inline. Dans la majoritÃ© des cas, les dÃ©tails d'implÃ©mentation sont contenus dans le fichier .cpp correspondant au fichier d'en-tÃªtes.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="100">
+<Text id="849">cfgread.h</Text>
+</th>
+<th width="450">
+<Text id="850">Fonctions de lecture et d'Ã©crite de fichiers de configuration. Par exemple, la fonction read_cfg_line() (lit une ligne de configuration) prend comme arguments le flux Ã  utiliser en entrÃ©e et le tableau text_tarray (raccourci pour vector &lt;text_t&gt;) Ã  remplir avec les donnÃ©es lues.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="851">display.h</Text>
+</th>
+<th width="450">
+<Text id="852">Objet sophistiquÃ© utilisÃ© par le rÃ©ceptionniste pour positionner, stocker et dÃ©velopper les macros, et gÃ©rer les types, La sectionÂ <CrossRef target="Section" ref="receptionist"/> le dÃ©taille.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="853">fileutil.h</Text>
+</th>
+<th width="450">
+<Text id="854">Support fonctionnel pour des fonctionnalitÃ©s de gestion de fichiers indÃ©pendantes du systÃšme d'exploitation. Par exemple, la fonction de nom filename_cat() (affiche nom-de-fichier) accepte jusqu'Ã  arguments text_t et renvoie un text_t qui est le rÃ©sultat de la concatÃ©nation des Ã©lÃ©ments en utilisant le sÃ©parateur de rÃ©pertoires appropriÃ© pour le systÃšme d'exploitation en cours d'utilisation.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="855">gsdlconf.h</Text>
+</th>
+<th width="450">
+<Text id="856">Fonctions propres au systÃšme qui rÃ©pondent Ã  des questions telles que: le systÃšme d'exploitation a-t-il besoin d'accÃ©der au fichier strings.h aussi bien qu'au fichier string.h? Toutes les valeurs appropriÃ©s pour le verrouillage de fichier sont-elles correctement positionnÃ©es?</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="857">gsdltimes.h</Text>
+</th>
+<th width="450">
+<Text id="858">Support fonctionnel pour la date et l'heure. Par exemple, la fonction time2text() (temps vers texte) prend l'heure de l'ordinateur, exprimÃ©e en nombre de secondes Ã©coulÃ©es depuis le premier janvier 1970, et la convertit sous la forme AAAA/MM/JJ hhmmss, qu'elle renvoie comme un objet text_t.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="859">gsdltools.h</Text>
+</th>
+<th width="450">
+<Text id="860">Support variÃ© pour le systÃšme d'exÃ©cution de Greenstone: clarifie le cÃŽtÃ© petit boutien (littleEndian) ou grand boutien (bigEndian); vÃ©rifie si Perl est disponible; exÃ©cute une commande systÃšme (avec quelques gadgets); et Ã©chappe les caractÃšres spÃ©ciaux de macros dans une chaÃ®ne text_t.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="861">gsdlunicode.h</Text>
+</th>
+<th width="450">
+<Text id="862">SÃ©rie d'objets hÃ©ritÃ©s qui gÃšrent le traitement de chaÃ®nes Unicode text_t Ã  travers des flux en entrÃ©e et en sortie, comme par exemple les conversions Unicode vers UTF-8 et vice versa; et la destruction des espaces de largeur nulle. GÃšre Ã©galement les fichiers de correspondance Ã  travers l'objet mapconvert, et les tables de correspondance sont chargÃ©es dans le rÃ©pertoire GSDLHOME/mappings.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="863">text_t.h</Text>
+</th>
+<th width="450">
+<Text id="864">Principalement, l'objet de texte Unicode dÃ©crit ci-dessus. Fournit Ã©galement deux classes de conversion de flux: inconvertclass (classe de conversion en entrÃ©e) et outconvertclass (classe de conversion en sortie). Ce sont les classes de base utilisÃ©es dans le fichier gsdlunicode.h.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="collection_server">
+<Title>
+<Text id="865">Serveur de collection</Text>
+</Title>
+<Content>
+<Text id="866">Nous allons maintenant expliquer systÃ©matiquement tous les objets apparaissant dans le cadre conceptuel de la figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/>. Nous commenÃ§ons au bas du diagrammeÂ --Â c'est-Ã -dire aux fondations du systÃšmeÂ --Â avec les objets de recherche, source, et de filtre, et remonterons les couches du protocole vers les composants centraux du rÃ©ceptionniste: actions, mise en forme, et langage de macros. Nous nous concentrerons ensuite sur l'initialisation des objets, puisque cette derniÃšre est plus facile Ã  comprendre quand on connaÃ®t le rÃŽle des diffÃ©rents objets.</Text>
+<Text id="867">La plupart des classes centrales du cadre conceptuel sont exprimÃ©es Ã  l'aide d'hÃ©ritage virtuel pour favoriser l'extensibilitÃ©. Avec l'hÃ©ritage virtuel, les objets hÃ©ritÃ©s peuvent Ãªtre passÃ©s en tant que leur classe de base, mais tout appel de fonction invoque la version dÃ©finie dans l'objet hÃ©ritÃ©. En assurant que le code source de Greenstone utilise partout la classe de base, sauf aux endroits oÃ¹ s'effectue la construction des objets Ã  proprement parler, nous garantissons donc que diffÃ©rentes implÃ©mentationsÂ --Â utilisant peut-Ãªtre des technologies sous-jacentes radicalement diffÃ©rentesÂ --Â peuvent facilement Ãªtre mises en place.</Text>
+<Text id="868">Supposons par exemple qu'une classe de base nommÃ©e BaseCalc (calculs de base) fournisse l'arithmÃ©tique classique: additions, soustractions, multiplications et divisions. Si toutes ses fonctions sont dÃ©clarÃ©es virtuelles, et que tous les arguments et types renvoyÃ©s sont dÃ©clarÃ©s comme des chaÃ®nes, on peut facilement implÃ©menter des versions hÃ©ritÃ©es de l'objet. L'une, FixedPrecisionCalc (calcul en prÃ©cision finie), pourrait utiliser les fonctions de la bibliothÃšque C pour faire les conversions entre chaÃ®nes et entiers, et implÃ©menter les calculs en utilisant les opÃ©rateurs arithmÃ©tiques standard: +, -, *, et /. Une autre, appelÃ©e InfinitePrecisionCalc (calcul en prÃ©cision infinie), pourrait accÃ©der aux arguments des chaÃ®nes caractÃšre par caractÃšre, en implÃ©mentant les opÃ©rations arithmÃ©tiques qui sont en principe d'une prÃ©cision infinie. En Ã©crivant un programme qui utilise partout BaseCalc, l'implÃ©mentation peut passer de la prÃ©cision finie Ã  la prÃ©cision infinie ou inversement en modifiant une seule ligne: l'endroit oÃ¹ l'objet de calcul est construit.</Text>
+<Subsection id="the_search_object">
+<Title>
+<Text id="869">L'objet de recherche</Text>
+</Title>
+<Content>
+<Figure id="search_base_class_api">
+<Title>
+<Text id="870">API de la classe de base de recherche Search</Text>
+</Title>
+<CodeLine>class searchclass {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   searchclass ();</CodeLine>
+<CodeLine>   virtual ~searchclass ();</CodeLine>
+<CodeLine>   // the index directory must be set before any searching</CodeLine>
+<CodeLine>   // is done</CodeLine>
+<CodeLine>   virtual void setcollectdir (const text_t &amp;thecollectdir);</CodeLine>
+<CodeLine>   // the search results are returned in queryresults</CodeLine>
+<CodeLine>   // search returns 'true' if it was able to do a search</CodeLine>
+<CodeLine>   virtual bool search(const queryparamclass &amp;queryparams,</CodeLine>
+<CodeLine>                         queryresultsclass &amp;queryresults)=0;</CodeLine>
+<CodeLine>   // the document text for 'docnum' is placed in 'output'</CodeLine>
+<CodeLine>   // docTargetDocument returns 'true' if it was able to</CodeLine>
+<CodeLine>   // try to get a document</CodeLine>
+<CodeLine>   // collection is needed to see if an index from the</CodeLine>
+<CodeLine>   // collection is loaded. If no index has been loaded</CodeLine>
+<CodeLine>   // defaultindex is needed to load one</CodeLine>
+<CodeLine>   virtual bool docTargetDocument(const text_t &amp;defaultindex,</CodeLine>
+<CodeLine>                                               const text_t &amp;defaultsubcollection,</CodeLine>
+<CodeLine>                                               const text_t &amp;defaultlanguage,</CodeLine>
+<CodeLine>                                               const text_t &amp;collection,</CodeLine>
+<CodeLine>                                               int docnum,</CodeLine>
+<CodeLine>                                               text_t &amp;output)=0;</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   querycache *cache;</CodeLine>
+<CodeLine>   text_t collectdir; // the collection directory</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="871">La figureÂ <CrossRef target="Figure" ref="search_base_class_api"/> montre l'API de la classe de base de l'objet de recherche prÃ©sentÃ© dans la figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/>. Elle dÃ©finit deux fonctions membre virtuelles: search() (recherche) et docTargetDocument() (doc document-cible). Comme le signifie le =0 qui suit la dÃ©claration des arguments, il s'agit de fonctions puresÂ --Â ce qui signifie qu'une classe qui hÃ©rite de cet objet devra implÃ©menter ces deux fonctions, faute de quoi le compilateur se plaindra.</Text>
+<Text id="872">La classe comprend Ã©galement deux champs de donnÃ©es protÃ©gÃ©s: collectdir (rÃ©pertoire de collection) et cache (tampon). Un objet de recherche est instanciÃ© pour une collection particuliÃšre, et le champ collectdir sert Ã  stocker l'endroit du systÃšme de fichiers oÃ¹ la collection (et en particulier ses fichiers d'index) se trouve. Le champ cache retient les rÃ©sultats d'une requÃªte. Il sert Ã  accÃ©lÃ©rer des requÃªtes ultÃ©rieures qui rÃ©pÃ©teraient la mÃªme requÃªte (et ses paramÃštres). Il peut sembler improbable qu'on effectue des requÃªtes identiques, mais dans la pratique c'est un phÃ©nomÃšne frÃ©quent. Le protocole de Greenstone est sans Ã©tat. Pour gÃ©nÃ©rer une page de rÃ©sultats semblable Ã  la figureÂ <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/> mais en prÃ©sentant les rÃ©sultats 11-20 de la mÃªme requÃªte, la recherche est Ã  nouveau transmise, en spÃ©cifiant cette fois-ci qu'il faut renvoyer les documents 11-20. L'utilisation de tampon rend ceci efficace, car le fait que cette recherche a dÃ©jÃ  eu lieu est dÃ©tectÃ© et les rÃ©sultats sont obtenus directement depuis le tampon.</Text>
+<Text id="873">Ces deux champs de donnÃ©es s'appliquent Ã  tout objet hÃ©ritÃ© qui implÃ©mente un mÃ©canisme de recherche. C'est pourquoi ils apparaissent dans la classe de base, et ils sont dÃ©clarÃ©s dans une section protÃ©gÃ©e de la classe de maniÃšre que les classes hÃ©ritÃ©es puissent y accÃ©der directement.</Text>
+</Content>
+</Subsection>
+<Subsection id="search_and_retrieval_with_mg">
+<Title>
+<Text id="874">Recherche et rapatriement avec MG</Text>
+</Title>
+<Content>
+<Text id="875">Greenstone utilise MG (abrÃ©viation de Â«Managing GigabytesÂ»Â --Â gÃ©rer les giga-octets; voir Witten<i>et al.</i>, 1999) pour indexer et rapatrier les documents, et son code source est inclus dans le rÃ©pertoire GSDLHOME/packages. MG utilise des techniques de compression pour optimiser l'utilisation de l'espace disque sans impacter la vitesse d'exÃ©cution. Pour une collection de documents Ã©crits en anglais, le texte compactÃ© et les index de corps du texte occupent en tout, en moyenne, un tiers de l'espace disque requis par le texte original, non compactÃ©. La recherche et le rapatriement sont souvent plus rapides que les opÃ©rations Ã©quivalentes sur la version non compactÃ©e car elles impliquent moins d'opÃ©rations sur le disque dur. </Text>
+<Figure id="api_for_direct_access_to_mg">
+<Title>
+<Text id="876">API pour accÃ©der directement Ã  MG (abrÃ©gÃ©e)</Text>
+</Title>
+<CodeLine>enum result_kinds {</CodeLine>
+<CodeLine>   result_docs,           // Return the documents found in last search</CodeLine>
+<CodeLine>   result_docnums,     // Return document id numbers and weights</CodeLine>
+<CodeLine>   result_termfreqs, // Return terms and frequencies</CodeLine>
+<CodeLine>   result_terms           // Return matching query terms</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>int mgq_ask(char *line);</CodeLine>
+<CodeLine>int mgq_results(enum result_kinds kind, int skip, int howmany,</CodeLine>
+<CodeLine>                               int (*sender)(char *, int, int, float, void *),</CodeLine>
+<CodeLine>                               void *ptr);</CodeLine>
+<CodeLine>int mgq_numdocs(void);</CodeLine>
+<CodeLine>int mgq_numterms(void);</CodeLine>
+<CodeLine>int mgq_equivterms(unsigned char *wordstem,</CodeLine>
+<CodeLine>                           int (*sender)(char *, int, int, float, void *),</CodeLine>
+<CodeLine>                           void *ptr);</CodeLine>
+<CodeLine>int mgq_docsretrieved (int *total_retrieved, int *is_approx);</CodeLine>
+<CodeLine>int mgq_getmaxstemlen ();</CodeLine>
+<CodeLine>void mgq_stemword (unsigned char *word);</CodeLine>
+</Figure>
+<Text id="877">L'utilisation normale de MG se fait interactivement, en tapant des commandes Ã  l'invite, et une maniÃšre d'implÃ©menter la classe mgsearchclass serait d'utiliser l'appel system() de la bibliothÃšque C au sein de l'objet pour exÃ©cuter les commandes MG appropriÃ©es. Mais une approche plus efficace consiste Ã  taper directement dans le code de MG avec des appels de fonctions. Bien que ceci nÃ©cessite une meilleure comprÃ©hension du code de MG, on peut masquer une grande partie de la complexitÃ© derriÃšre une nouvelle API qui deviendra le point de contact pour l'objet mgsearchclass. C'est le rÃŽle du fichier colserver/mgq.c, dont l'API est prÃ©sentÃ©e figureÂ <CrossRef target="Figure" ref="api_for_direct_access_to_mg"/>.</Text>
+<Text id="878">On fournit des paramÃštres Ã  MG Ã  travers la fonction mgq_ask() (demande mgq), qui prend des options de texte dans un format identique Ã  celui utilisÃ© Ã  la ligne de commande, tel que:</Text>
+<CodeLine>mgq_ask( ".set casefold off ");</CodeLine>
+<Text id="879">Il sert aussi Ã  invoquer une requÃªte. On accÃšde Ã  ses rÃ©sultats Ã  travers la fonction mgq_results (rÃ©sultats de mgq), qui prend un pointeur vers une fonction comme quatriÃšme paramÃštre. Ceci fournit une maniÃšre souple de convertir l'information renvoyÃ©e dans les structures de donnÃ©es de MG en le format requis par mgsearchclass. Des appels tels que mgq_numdocs() (mgq-numÃ©ros de documents), mgq_numterms() et mgq_docsretrieved() (respectivement, mgq-numÃ©ros de termes et mgq-documents rapatriÃ©s) renvoient Ã©galement des informations, qui sont cette fois plus prÃ©cisÃ©ment prescrites. Les deux derniÃšres fonctions gÃšrent la troncature.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_source_object">
+<Title>
+<Text id="880">L'objet source</Text>
+</Title>
+<Content>
+<Figure id="source_base_class_api">
+<Title>
+<Text id="881">API de la classe de base source</Text>
+</Title>
+<CodeLine>class sourceclass {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   sourceclass ();</CodeLine>
+<CodeLine>   virtual ~sourceclass ();</CodeLine>
+<CodeLine>   // configure should be called once for each configuration line</CodeLine>
+<CodeLine>   virtual void configure (const text_t &amp;key, const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   // init should be called after all the configuration is done but</CodeLine>
+<CodeLine>   // before any other methods are called</CodeLine>
+<CodeLine>   virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   // translate_OID translates OIDs using " .pr " , . " fc " etc.</CodeLine>
+<CodeLine>   virtual bool translate_OID (const text_t &amp;OIDin, text_t &amp;OIDout, comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   // get_metadata fills out the metadata if possible, if it is not</CodeLine>
+<CodeLine>   // responsible for the given OID then it return s false.</CodeLine>
+<CodeLine>   virtual bool get_metadata (const text_t &amp;requestParams, const text_t &amp;refParams,</CodeLine>
+<CodeLine>                           bool getParents, const text_tset &amp;fields, const text_t &amp;OID,</CodeLine>
+<CodeLine>                           MetadataInfo_tmap &amp;metadata, comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool get_document (const text_t &amp;OID, text_t &amp;doc, </CodeLine>
+<CodeLine>                           comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="882">Le rÃŽle de l'objet source dans la figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/> est d'accÃ©der aux mÃ©ta-donnÃ©es et au texte du document, et l'API de sa classe de base est prÃ©sentÃ©e figureÂ <CrossRef target="Figure" ref="source_base_class_api"/>. Une fonction membre associe Ã  chaque tÃ¢che les fonctions get_metadata() (obtient les mÃ©ta-donnÃ©es) et get_document() (obtient le document) , respectivement. Toutes deux sont dÃ©clarÃ©es virtual, la version fournie par une implÃ©mentation particuliÃšre de la classe de base n'est donc appelÃ©e qu'au moment de l'exÃ©cution. Une version hÃ©ritÃ©e de cet objet utilise GDBM pour implÃ©menter get_metadata() et MG pour implÃ©menter get_document(): nous dÃ©taillons cette version ci-dessous. </Text>
+<Text id="883">On trouve d'autres fonctions membre dans la figureÂ <CrossRef target="Figure" ref="source_base_class_api"/>, telles que configure(), init(), et translate_OID() (traduire l'identifiant d'objet). Les deux premiÃšres sont liÃ©es au processus d'initialisation dÃ©crit sectionÂ <CrossRef target="Section" ref="initialisation"/>.</Text>
+<Text id="884">La derniÃšre, translate_OID(), gÃšre la syntaxe pour exprimer les identifiants de documents. Nous avons vu figureÂ <CrossRef target="Figure" ref="the_golf_course_mystery"/> comment on pouvait ajouter un numÃ©ro de page Ã  un identifiant de document pour ne rapatrier que la page correspondante. Ceci est possible car les pages ont Ã©tÃ© stockÃ©es en tant que Â«sectionsÂ» lors de la construction de la collection. Ajouter Â«.1Â» Ã  un OID rapatrie la premiÃšre section du document correspondant. Les sections peuvent Ãªtre imbriquÃ©es; on y accÃšde alors on concatÃ©nant les numÃ©ros de sections et en sÃ©parant les numÃ©ros par des points.</Text>
+<Text id="885">En plus des numÃ©ros hiÃ©rarchiques de sections, la syntaxe de l'identifiant de document permet des accÃšs relatifs. Par rapport Ã  la section actuelle du document il est possible d'accÃ©der au<i>premier fils</i>(<i>first child</i>) en ajoutant .fc, au<i>dernier fils</i>(<i>last child</i>) en ajoutant .lc, au<i>parent</i>en ajoutant .pr, au<i>frÃšre suivant</i>(<i>next sibling</i>) en ajoutant .ns, et au<i>frÃšre prÃ©cÃ©dent</i>(<i>previous sibling</i>) en ajoutant .ps.</Text>
+<Text id="886">La fonction translate_OID() utilise les paramÃštres OIDin (OID en entrÃ©e) et OIDout (OID en sortie) pour renfermer la source et le rÃ©sultat de la conversion. Elle prend aussi deux autres paramÃštres, err (erreur) et logout (journal en sortie). Ils communiquent tout Ã©tat d'erreur qui peut se produire lors de l'opÃ©ration de traduction, et dÃ©terminent oÃ¹ envoyer les informations de journalisation. Ces paramÃštres dÃ©pendent Ã©troitement du protocole, comme nous le verrons dans la sectionÂ <CrossRef target="Section" ref="protocol"/>.</Text>
+<Part id="database_retrieval_with_gdbm">
+<Title>
+<Text id="887">Rapatriement de base de donnÃ©es avec gdbm</Text>
+</Title>
+<Content>
+<Text id="888">GDBM est le gestionnaire de bases de donnÃ©es de GNU (www.gnu.org). Il implÃ©mente une structure d'enregistrements plats de couples clef/donnÃ©es, et il est compatible en arriÃšre avec DBM et NDBM. Les opÃ©rations fournies comprennent le stockage, le rapatriement, et la destruction d'enregistrements par clef, et un parcours non ordonnÃ© de toutes les clefs.</Text>
+<Figure id="gdbm_database_for_the_gutenberg_collection">
+<Title>
+<Text id="889">Base de donnÃ©es GDBM pour la collection (extrait)</Text>
+</Title>
+<CodeLine>[HASH01d7b30d4827b51282919e9b]</CodeLine>
+<CodeLine>&lt;doctype&gt;         doc</CodeLine>
+<CodeLine>&lt;hastxt&gt;           0</CodeLine>
+<CodeLine>&lt;Title&gt;             The Winter's Tale</CodeLine>
+<CodeLine>&lt;Creator&gt;         William Shakespeare</CodeLine>
+<CodeLine>&lt;archivedir&gt;   HASH01d7/b30d4827.dir</CodeLine>
+<CodeLine>&lt;thistype&gt;       Invisible</CodeLine>
+<CodeLine>&lt;childtype&gt;     Paged</CodeLine>
+<CodeLine>&lt;contains&gt;        " .1; " .2; " .3; " .4; " .5; " .6; " .7; " .8; " .9; " .10; " .11; " .12;            \ <br/>                           " .13; " .14; " .15; " .16; " .17; " .18; " .19; " .20; " .21; " .22;            \ <br/>                           " .23; " .24; " .25; " .26; " .27; " .28; " .29; " .30; " .31; " .32;            \ <br/>                           " .33; " .34; " .35</CodeLine>
+<CodeLine>&lt;docnum&gt;           168483</CodeLine>
+<CodeLine>âââââââââââââââââââââââ-</CodeLine>
+<CodeLine>[CL1]</CodeLine>
+<CodeLine>&lt;doctype&gt;         classify</CodeLine>
+<CodeLine>&lt;hastxt&gt;           0</CodeLine>
+<CodeLine>&lt;childtype&gt;     HList</CodeLine>
+<CodeLine>&lt;Title&gt;             Title</CodeLine>
+<CodeLine>&lt;numleafdocs&gt; 1818</CodeLine>
+<CodeLine>&lt;thistype&gt;       Invisible</CodeLine>
+<CodeLine>&lt;contains&gt;       " .1; " .2; " .3; " .4; " .5; " .6; " .7; " .8; " .9; " .10; " .11; " .12;          \ <br/>                           " .13; " .14; " .15; " .16; " .17; " .18; " .19; " .20; " .21; " .22;          \ <br/>                            " .23; " .24</CodeLine>
+<CodeLine>âââââââââââââââââââââââ-</CodeLine>
+<CodeLine>[CL1.1]</CodeLine>
+<CodeLine>&lt;doctype&gt;         classify</CodeLine>
+<CodeLine>&lt;hastxt&gt;           0</CodeLine>
+<CodeLine>&lt;childtype&gt;     VList</CodeLine>
+<CodeLine>&lt;Title&gt;             A</CodeLine>
+<CodeLine>&lt;numleafdocs&gt; 118</CodeLine>
+<CodeLine>&lt;contains&gt;      HASH0130bc5f9f90089b3723431f;HASH9cba43bacdab5263c98545;\</CodeLine>
+<CodeLine>                          HASH12c88a01da6e8379df86a7;HASH9c86579a83e1a2e4cf9736;   \</CodeLine>
+<CodeLine>                           HASHdc2951a7ada1f36a6c3aca;HASHea4dda6bbc7cdeb4abfdee;   \</CodeLine>
+<CodeLine>                          HASHce55006513c47235ac38ba;HASH012a33acaa077c0e612b9351;\</CodeLine>
+<CodeLine>                          HASH010dd1e923a123826ae30e4b;HASHaf674616785679fed4b7ee;\</CodeLine>
+<CodeLine>                         HASH0147eef4b9d1cb135e096619;HASHe69b9dbaa83ffb045d963b;\</CodeLine>
+<CodeLine>                         HASH01abc61c646c8e7a8ce88b10;HASH5f9cd13678e21820e32f3a;\</CodeLine>
+<CodeLine>                         HASHe8cbba1594c72c98f9aa1b;HASH01292a2b7b6b60dec96298bc;\</CodeLine>
+<CodeLine>                         ...</CodeLine>
+</Figure>
+<Text id="890">La figureÂ <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> montre un extrait de la base de donnÃ©es d'informations de la collection crÃ©Ã©e lors de la construction de la collection Gutenberg. Cet extrait fut produit Ã  l'aide de l'outil Greenstone db2txt, qui convertit le format binaire de base de donnÃ©es GDBM sous forme textuelle. La figureÂ <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> contient trois enregistrements, sÃ©parÃ©s par des lignes horizontales. Le premier est une entrÃ©e de document, les deux autres sont des portions de la hiÃ©rarchie crÃ©Ã©es par le classificateur AZList pour les titres de la collection. La premiÃšre ligne de chaque enregistrement est sa clef.</Text>
+<Text id="891">L'enregistrement de document stocke le titre du livre, son auteur, et toute autre mÃ©ta-donnÃ©e fournie (ou extraite) lors de la construction de la collection. Il contient aussi des valeurs pour usage interne: oÃ¹ les fichiers associÃ©s Ã  ce document se trouvent (&lt;archivedir&gt;) et le numÃ©ro de document utilisÃ© de maniÃšre interne par MG (&lt;docnum&gt;).</Text>
+<Text id="892">Le champ &lt;contains&gt; (contient) stocke une liste d'Ã©lÃ©ments, sÃ©parÃ©s par des points-virgules, qui pointent vers des enregistrement relatifs dans la base de donnÃ©es. Pour un enregistrement de document, &lt;contains&gt; sert Ã  pointer vers les sections imbriquÃ©es. On formera des clefs d'enregistrement en concatÃ©nant la clef courante Ã  l'un des Ã©lÃ©ments fils (le sÃ©parateur Ã©tant un point).</Text>
+<Text id="893">Le deuxiÃšme enregistrement de la figureÂ <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> est le noeud principal de la hiÃ©rarchie de classification de titres A-Z. Ses enfants, auxquels on accÃšde Ã  travers le champ &lt;contains&gt;, comprennent CL1.1, CL1.2, CL1.3 etc., et correspondent aux pages individuelles pour les lettres A, B, C, etc. Il n'en existe que 24: le classificateur AZList a rassemblÃ© les lettres Q-R et Y-Z car elles ne concernaient que peu de titres.</Text>
+<Text id="894">Les enfants du champ &lt;contains&gt; du troisiÃšme enregistrement, CL1.1, sont les documents proprement dits. On peut trouver des structures plus compliquÃ©esÂ --Â le champ &lt;contains&gt; peut inclure un mÃ©lange de documents et d'autres noeuds CL. Les clefs exprimÃ©es relativement Ã  la clef courante se reconnaissent des clefs absolues car elles commencent par une apostrophe double. (").</Text>
+</Content>
+</Part>
+<Part id="using_mg_and_gdbm_to_implement_a_source_object">
+<Title>
+<Text id="895">Utiliser MG et GDBM pour implÃ©menter un objet source</Text>
+</Title>
+<Content>
+<Figure id="api_for_mg_and_gdbm_based_version_of_sourceclass">
+<Title>
+<Text id="896">API de la version de sourceclass basÃ©e sur MG et GDBM (abrÃ©gÃ©e)</Text>
+</Title>
+<CodeLine>class mggdbmsourceclass : public sourceclass {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   // Omitted, data fields that store:</CodeLine>
+<CodeLine>   //     collection specific file information</CodeLine>
+<CodeLine>   //     index substructure</CodeLine>
+<CodeLine>   //     information about parent</CodeLine>
+<CodeLine>   //     pointers to gdbm and mgsearch objects</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   mggdbmsourceclass ();</CodeLine>
+<CodeLine>   virtual ~mggdbmsourceclass ();</CodeLine>
+<CodeLine>   void set_gdbmptr (gdbmclass *thegdbmptr);</CodeLine>
+<CodeLine>   void set_mgsearchptr (searchclass *themgsearchptr);</CodeLine>
+<CodeLine>   void configure (const text_t &amp;key, const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   bool translate_OID (const text_t &amp;OIDin, text_t &amp;OIDout,</CodeLine>
+<CodeLine>                                           comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   bool get_metadata (const text_t &amp;requestParams,</CodeLine>
+<CodeLine>                                           const text_t &amp;refParams,</CodeLine>
+<CodeLine>                                         bool getParents, const text_tset &amp;fields,</CodeLine>
+<CodeLine>                                         const text_t &amp;OID, MetadataInfo_tmap &amp;metadata,</CodeLine>
+<CodeLine>                                         comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   bool get_document (const text_t &amp;OID, text_t &amp;doc,</CodeLine>
+<CodeLine>                                         comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="897">L'objet qui rassemble MG et GDBM pour rÃ©aliser une implÃ©mentation de sourceclass s'appelle mggdbmsourceclass. La figureÂ <CrossRef target="Figure" ref="api_for_mg_and_gdbm_based_version_of_sourceclass"/> prÃ©sente son API. Les deux fonctions membre set_gdbmptr() et set_mgsearchptr() (respectivement, positionne le pointeur gdbm et recherche le pointeur mg) stockent des pointeurs vers leurs objets respectifs, de sorte que les implÃ©mentations de get_metadata() (obtient les mÃ©ta-donnÃ©es) et get_document() (obtient le document) puissent accÃ©der aux outils appropriÃ©s pour mener leur tÃ¢che Ã  bien.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="the_filter_object">
+<Title>
+<Text id="898">L'objet de filtre</Text>
+</Title>
+<Content>
+<Figure id="api_for_the_filter_base_class">
+<Title>
+<Text id="899">API de la classe de base de filtre</Text>
+</Title>
+<CodeLine>class filterclass {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   text_t gsdlhome;</CodeLine>
+<CodeLine>   text_t collection;</CodeLine>
+<CodeLine>   text_t collectdir;</CodeLine>
+<CodeLine>   FilterOption_tmap filterOptions;</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   filterclass ();</CodeLine>
+<CodeLine>   virtual ~filterclass ();</CodeLine>
+<CodeLine>   virtual void configure (const text_t &amp;key,Â const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   // returns the name of this filter</CodeLine>
+<CodeLine>   virtual text_t get_filter_name ();</CodeLine>
+<CodeLine>   // returns the current filter options</CodeLine>
+<CodeLine>   virtual void get_filteroptions (InfoFilterOptionsResponse_t &amp;response,</CodeLine>
+<CodeLine>                                 comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void filter (const FilterRequest_t &amp;request,</CodeLine>
+<CodeLine>                         FilterResponse_t &amp;response,</CodeLine>
+<CodeLine>                         comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="900">L'API de la classe de base de l'objet de filtre de la figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/> est prÃ©sentÃ©e dans la figureÂ <CrossRef target="Figure" ref="api_for_the_filter_base_class"/>. Elle commence par les champs de donnÃ©es protÃ©gÃ©s gsdlhome, collection, et collectdir, frÃ©quents dans les classes qui ont besoin d'accÃ©der Ã  des fichiers propres Ã  des collections.</Text>
+<BulletList>
+<Bullet>
+<Text id="901">gsdlhome est la mÃªme chose que GSDLHOME, de sorte que l'objet puisse localiser les fichiers de Greenstone.</Text>
+</Bullet>
+<Bullet>
+<Text id="902">collection est le nom du rÃ©pertoire correspondant Ã  la collection.</Text>
+</Bullet>
+<Bullet>
+<Text id="903">collectdir est le chemin complet du rÃ©pertoire de collection (ceci est nÃ©cessaire car une collection ne se trouve pas toujours dans la zone GSDLHOME).</Text>
+</Bullet>
+</BulletList>
+<Text id="904">mggdbsourceclass est une autre classe qui inclut ces trois champs de donnÃ©es.</Text>
+<Text id="905">Les fonctions membre configure() et init() (d'abord vues dans la fonction sourceclass) sont utilisÃ©es par le processus d'initialisation. L'objet lui-mÃªme est intimement alignÃ© avec la portion de filtre lui correspondant dans le protocole; en particulier les fonctions get_filteroptions() et filter() correspondent exactement. </Text>
+<Figure id="how_a_filter_option_is_stored">
+<Title>
+<Text id="906">ManiÃšre de stocker une option de filtre</Text>
+</Title>
+<CodeLine>struct FilterOption_t {</CodeLine>
+<CodeLine>   void clear (); \   void check_defaultValue ();</CodeLine>
+<CodeLine>   FilterOption_t () {clear();}</CodeLine>
+<CodeLine>   text_t name;</CodeLine>
+<CodeLine>   enum type_t {booleant=0, integert=1, enumeratedt=2, stringt=3};</CodeLine>
+<CodeLine>   type_t type;</CodeLine>
+<CodeLine>   enum repeatable_t {onePerQuery=0, onePerTerm=1, nPerTerm=2};</CodeLine>
+<CodeLine>   repeatable_t repeatable;</CodeLine>
+<CodeLine>   text_t defaultValue;</CodeLine>
+<CodeLine>   text_tarray validValues;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>struct OptionValue_t {</CodeLine>
+<CodeLine>   void clear ();</CodeLine>
+<CodeLine>   text_t name;</CodeLine>
+<CodeLine>   text_t value;</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="907">Les deux classes prÃ©sentÃ©es dans la figureÂ <CrossRef target="Figure" ref="how_a_filter_option_is_stored"/> sont centrales pour les options de filtre. FilterOption_t (filtre d'option) stocke le nom de l'option, son type, et si elle peut ou non Ãªtre rÃ©pÃ©tÃ©e (repeatable). validValues est interprÃ©tÃ© selon le type de l'option. Pour un type boolÃ©en, la premiÃšre valeur est la valeur fausse false, la deuxiÃšme valeur est la valeur vraie true. Pour un type entier, la premiÃšre valeur est la valeur minimale, la deuxiÃšme valeur est la valeur maximale. Pour un type Ã©numÃ©rÃ© toutes les valeurs sont listÃ©es. Pour un type de chaÃ®ne la valeur est ignorÃ©e. Pour des situations plus simples, on utilise OptionValue_t (valeur d'option), qui enregistre sous forme de text_t le nom de l'option et sa valeur.</Text>
+<Text id="908">Les objets de requÃªte et de rÃ©ponse passÃ©s en paramÃštres Ã  filterclass sont construits Ã  partir de ces deux classes, en utilisant des tableaux associatifs pour stocker un ensemble d'options telles que les options nÃ©cessaires Ã  la fonction InfoFilterOptionsResponse_t. On peut trouver des dÃ©tails complÃ©mentaires dans le fichier GSDLHOME/src/recpt/comtypes.h.</Text>
+</Content>
+</Subsection>
+<Subsection id="inherited_filter_objects">
+<Title>
+<Text id="909">Objets de filtre hÃ©ritÃ©s</Text>
+</Title>
+<Content>
+<Figure id="inheritance_hierarchy_for_filter">
+<Title>
+<Text id="910">HiÃ©rarchie d'hÃ©ritage pour l'objet de filtre</Text>
+</Title>
+<File width="337" height="245" url="images/Dev_Fig_38.png"/>
+</Figure>
+<Text id="911">Les filtres utilisent deux niveaux d'hÃ©ritage, comme illustrÃ© dans la figureÂ <CrossRef target="Figure" ref="inheritance_hierarchy_for_filter"/>. Tout d'abord on distingue les filtres de requÃªte et de navigation, et il existe pour les premiers une implÃ©mentation spÃ©cifique, fondÃ©e sur MG. Pour fonctionner correctement, mgqueryfilterclass doit accÃ©der Ã  MG Ã  travers mgsearchclass et Ã  GDBM Ã  travers gdbmclass. browsefilterclass n'a besoin que d'accÃ©der Ã  GDBM. Les pointeurs vers ces objets sont stockÃ©s sous la forme de champs de donnÃ©es protÃ©gÃ©s au sein des classes respectives.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_collection_server_code">
+<Title>
+<Text id="912">Code du serveur de collection</Text>
+</Title>
+<Content>
+<Text id="913">Voici les fichiers d'en-tÃªtes du rÃ©pertoire GSDLHOME/src/colservr, suivis de leur description. Le nom de fichier correspond gÃ©nÃ©ralement au nom de l'objet qu'il renferme.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="120">
+<Text id="914">browsefilter.h</Text>
+</th>
+<th width="420">
+<Text id="915">(filtre de navigation) HÃ©ritÃ© de filterclass (classe de filtre), cet objet fournit un accÃšs Ã  GDBM (dÃ©crit plus haut).</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="916">collectserver.h</Text>
+</th>
+<th width="420">
+<Text id="917">(serveur de collection) Cet objet relie les objets de filtre et source d'une collection, pour former l'objet de collection reprÃ©sentÃ© figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="918">colservrconfig.h</Text>
+</th>
+<th width="420">
+<Text id="919">(configuration du serveur de collection) Support fonctionnel pour la lecture des fichiers propres Ã  une collection etc/collect.cfg et index/build.cfg. Le premier est le fichier de configuration de la collection; le deuxiÃšme est un fichier gÃ©nÃ©rÃ© par le processus de construction qui enregistre le moment de la derniÃšre construction menÃ©e Ã  bien, une liste des correspondances d'index, combien de documents ont Ã©tÃ© indexÃ©s, et leur taille (non compactÃ©e) en octets.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="920">filter.h</Text>
+</th>
+<th width="420">
+<Text id="921">(filtre) La classe de base de l'objet filtre filterclass dÃ©crit ci-dessus.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="922">maptools.h</Text>
+</th>
+<th width="420">
+<Text id="923">DÃ©finit une classe stringmap (correspondance de chaÃ®ne) qui fournit une correspondance se rappelant l'ordre original d'une correspondance text_t, mais qui est d'une consultation rapide. mggdbmsourceclass ainsi que queryfilterclass s'en servent.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="924">mggdbmsource.h</Text>
+</th>
+<th width="420">
+<Text id="925">HÃ©ritÃ© de sourceclass, cet objet donne accÃšs Ã  MG et GDBM (dÃ©crit plus haut).</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="926">mgppqueryfilter.h</Text>
+</th>
+<th width="420">
+<Text id="927">HÃ©ritÃ© de queryfilterclass, cet objet fournit une implÃ©mentation de QueryFilter fondÃ©e sur MG++, version amÃ©liorÃ©e de MG Ã©crite en C++. Remarquez que Greenstone est par dÃ©faut configurÃ© pour utiliser MG, puisque MG++ est toujours en cours de dÃ©veloppement.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="928">mgppsearch.h</Text>
+</th>
+<th width="420">
+<Text id="929">HÃ©ritÃ© de searchclass, cet objet fournit une implÃ©mentation de l'objet de recherche avec MG++. Comme mgppqueryfilterclass, ceci n'est pas utilisÃ© par dÃ©faut.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="930">mgq.h</Text>
+</th>
+<th width="420">
+<Text id="931">Interface fonctionnelle au paquetage MG. Ses fonctions principales sont mg_ask() et mg_results().</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="932">mgqueryfilter.h</Text>
+</th>
+<th width="420">
+<Text id="933">HÃ©ritÃ© de queryfilterclass, cet objet fournit une implÃ©mentation de QueryFilter fondÃ©e sur MG.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="934">mgsearch.h</Text>
+</th>
+<th width="420">
+<Text id="935">HÃ©ritÃ© de searchclass, cet objet fournit une implÃ©mentation de l'objet de recherche qui utilise MG (dÃ©crit plus haut).</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="936">phrasequeryfilter.h</Text>
+</th>
+<th width="420">
+<Text id="937">HÃ©ritÃ© de mgqueryclass, cet objet fournit une classe de requÃªte fondÃ©e sur les groupes de mots. Il n'est pas utilisÃ© dans l'installation par dÃ©faut. C'est mgqueryfilterclass qui fournit cette fonctionnalitÃ© Ã  travers un support fonctionnel depuis phrasesearch.h.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="938">phrasesearch.h</Text>
+</th>
+<th width="420">
+<Text id="939">Support fonctionnel pour rechercher des groupes de mots comme une opÃ©ration post-traitement.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="940">querycache.h</Text>
+</th>
+<th width="420">
+<Text id="941">UtilisÃ© par searchclass et les classes qui en hÃ©ritent pour garder dans un tampon les rÃ©sultats d'une requÃªte, afin de gÃ©nÃ©rer plus efficacement la gÃ©nÃ©ration des pages de rÃ©sultats suivantes (dÃ©crit plus haut).</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="942">queryfilter.h</Text>
+</th>
+<th width="420">
+<Text id="943">HÃ©ritÃ© de la classe de base de filtre filterclass, cet objet Ã©tablit une classe de base pour les objets de filtre de requÃªte (dÃ©crit plus haut).</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="944">queryinfo.h</Text>
+</th>
+<th width="420">
+<Text id="945">Support pour la recherche: structures de donnÃ©es et objets pour contenir les paramÃštres des requÃªtes, les documents rÃ©sultats et les frÃ©quences des termes.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="946">search.h</Text>
+</th>
+<th width="420">
+<Text id="947">La classe de base de l'objet de recherche searchclass (dÃ©crite plus haut).</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="948">source.h</Text>
+</th>
+<th width="420">
+<Text id="949">La classe de base de l'objet source sourceclass (dÃ©crite plus haut).</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="protocol">
+<Title>
+<Text id="950">Le protocole</Text>
+</Title>
+<Content>
+<Table id="list_of_protocol_calls">
+<Title>
+<Text id="951">Liste des appels de protocole</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="952"><i>get_protocol_name()</i></Text>
+</th>
+<th width="397">
+<Text id="953">Renvoie le nom de ce protocole. Les valeurs possibles comprennent<i>nullproto</i>(protocole vide),<i>corbaproto</i>(protocole CORBA), et<i>z3950proto</i>. UtilisÃ© par des portions du systÃšme d'exÃ©cution qui dÃ©pendent du protocole pour dÃ©cider quel code exÃ©cuter.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="954"><i>get_collection_list()</i></Text>
+</th>
+<th width="397">
+<Text id="955">Renvoie la liste des collections que ce protocole connaÃ®t.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="956"><i>has_collection()</i></Text>
+</th>
+<th width="397">
+<Text id="957">Renvoie la valeur vraie<i>true</i>si le protocole peut communiquer avec la collection nommÃ©e, c'est-Ã -dire si cette collection fait partie de sa liste de collections.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="958"><i>ping()</i></Text>
+</th>
+<th width="397">
+<Text id="959">Renvoie la valeur vraie<i>true</i>si on a pu Ã©tablir une connexion Ã  la collection nommÃ©e. Dans le cas du protocole vide l'implÃ©mentation est la mÃªme que celle de<i>has_collection().</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="960"><i>get_collectinfo()</i></Text>
+</th>
+<th width="397">
+<Text id="961">Obtient des informations gÃ©nÃ©riques relatives Ã  la collection nommÃ©e: date de derniÃšre construction, nombre de documents qu'elle contient, etc. Inclut aussi des mÃ©ta-donnÃ©es du fichier de configuration de la collection: le texte Â«\menu{Ã  propos}Â»; l'icone de collection Ã  utiliser, etc.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="962"><i>get_filterinfo()</i></Text>
+</th>
+<th width="397">
+<Text id="963">Obtient une liste de tous les objets de filtre pour la collection nommÃ©e.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="964"><i>get_filteroptions()</i></Text>
+</th>
+<th width="397">
+<Text id="965">Obtient toutes les options pour un objet de filtre particulier au sein de la collection nommÃ©e.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="966"><i>filter()</i></Text>
+</th>
+<th width="397">
+<Text id="967">Permet la recherche et la navigation. Pour un type de filtre donnÃ© et des rÃ©glages d'options, accÃšde au contenu de la collection nommÃ©e pour produire un ensemble rÃ©sultat qui est filtrÃ© selon les rÃ©glages d'options. Les champs de donnÃ©es renvoyÃ©s dÃ©pendent Ã©galement des rÃ©glages d'options, comme par exemple la frÃ©quence des termes de requÃªte et les mÃ©ta-donnÃ©es de document.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="968"><i>get_document()</i></Text>
+</th>
+<th width="397">
+<Text id="969">Obtient un document ou une section d'un document.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="970">La tableÂ <CrossRef target="Table" ref="list_of_protocol_calls"/> liste les appels de fonction au protocole, en rÃ©sumant chaque entrÃ©e. Les exemples donnÃ©s sectionÂ <CrossRef target="Section" ref="how_the_conceptual_framework_fits_together"/> ont couvert la plupart de ces appels. Les fonctions non mentionnÃ©es prÃ©cÃ©demment sont les fonctions has_collection(), ping(), get_protocol_name() et get_filteroptions(). Les deux premiÃšres rÃ©pondent par oui ou par non aux questions Â«la collection existe-t-elle sur ce serveur?Â» et Â«est-elle en cours de fonctionnement?Â», respectivement. Le but des deux autres est de supporter des protocoles multiples au sein d'une architecture distribuÃ©e sur des ordinateurs diffÃ©rents, et non pas le simple exÃ©cutable fondÃ© sur le protocole vide et dÃ©crit ici. L'une d'entre elles fait une distinction selon le protocole en cours d'utilisation. L'autre permet Ã  un rÃ©ceptionniste d'interroger un serveur de collection pour trouver les options supportÃ©es, afin de s'auto-configurer dynamiquement pour profiter des services offerts par un serveur particulier.</Text>
+<Figure id="null_protocol_api">
+<Title>
+<Text id="971">API du protocole vide (abrÃ©gÃ©e)</Text>
+</Title>
+<CodeLine>class nullproto : public recptproto {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   virtual text_t get_protocol_name ();</CodeLine>
+<CodeLine>   virtual void get_collection_list (text_tarray &amp;collist,</CodeLine>
+<CodeLine>                comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void has_collection (const text_t &amp;collection,</CodeLine>
+<CodeLine>                bool &amp;hascollection,</CodeLine>
+<CodeLine>                comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void ping (const text_t &amp;collection,</CodeLine>
+<CodeLine>                  bool &amp;wassuccess,</CodeLine>
+<CodeLine>                  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_collectinfo (const text_t &amp;collection,</CodeLine>
+<CodeLine>                  ColInfoResponse_t &amp;collectinfo,</CodeLine>
+<CodeLine>                  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_filterinfo (const text_t &amp;collection,</CodeLine>
+<CodeLine>                   InfoFiltersResponse_t &amp;response,</CodeLine>
+<CodeLine>                   comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_filteroptions (const text_t &amp;collection,</CodeLine>
+<CodeLine>                   const InfoFilterOptionsRequest_t &amp;request,</CodeLine>
+<CodeLine>                   InfoFilterOptionsResponse_t &amp;response,</CodeLine>
+<CodeLine>                   comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void filter (const text_t &amp;collection,</CodeLine>
+<CodeLine>                   FilterRequest_t &amp;request,</CodeLine>
+<CodeLine>                   FilterResponse_t &amp;response,</CodeLine>
+<CodeLine>                   comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_document (const text_t &amp;collection,</CodeLine>
+<CodeLine>                  const DocumentRequest_t &amp;request,</CodeLine>
+<CodeLine>                  DocumentResponse_t &amp;response,</CodeLine>
+<CodeLine>                  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="972">La figureÂ <CrossRef target="Figure" ref="null_protocol_api"/> montre l'API pour le protocole vide. Les commentaires, ainsi que certains dÃ©tails de bas niveau, ont Ã©tÃ© omis (consultez le fichier source, c'est-Ã -dire recpt/nullproto.h, pour avoir tous les dÃ©tails).</Text>
+<Text id="973">Ce protocole hÃ©rite de la classe de base recptproto. On utilise l'hÃ©ritage virtuel de telle sorte que plus d'un type de protocoleÂ --Â y compris des protocoles pas encore conÃ§usÂ --Â puisse Ãªtre facilement supportÃ© dans le reste du code source. Ceci est possible car l'objet de classe de base recptproto est utilisÃ© tout au long du code source, Ã  l'exception de l'endroit de la construction. Nous spÃ©cifions ici la vÃ©ritable variÃ©tÃ© de protocole que nous souhaitons utiliserÂ --Â dans ce cas-ci, le protocole vide.</Text>
+<Text id="974">Ã l'exception de get_protocol_name(), qui ne prend aucun paramÃštre et renvoie le nom du protocole sous la forme d'une chaÃ®ne au format Unicode, toutes les fonctions du protocole incluent un paramÃštre d'erreur et un flux de sortie en tant que leurs deux derniers arguments. Le paramÃštre d'erreur enregistre toute erreur qui se produit pendant l'exÃ©cution de l'appel de protocole, et le flux de sortie est utilisÃ© Ã  des fins de journalisation. Les fonctions sont de type void--elles ne renvoient pas explicitement des informations dans leur derniÃšre instruction, mais renvoient plutÃŽt des donnÃ©es Ã  travers des paramÃštres dÃ©signÃ©s tels que le paramÃštre d'erreur (dont on vient de parler). Dans certains langages de programmation, de tels sous-programmes s'appelleraient Â«procÃ©duresÂ» et non Â«fonctionsÂ», mais le C++ n'opÃšre pas de telle distinction syntaxique.</Text>
+<Text id="975">La plupart des fonctions prennent le nom de la collection en argument. Trois des fonctions membre (les fonctions get_filteroptions(), filter(), et get_document()) suivent le schÃ©ma de fournir un paramÃštre de requÃªte et de recevoir les rÃ©sultats dans un paramÃštre de rÃ©ponse.</Text>
+</Content>
+</Section>
+<Section id="receptionist">
+<Title>
+<Text id="976">Le rÃ©ceptionniste</Text>
+</Title>
+<Content>
+<Text id="977">C'est la derniÃšre couche du modÃšle conceptuel. AprÃšs analyse des arguments du CGI, l'activitÃ© principale est l'exÃ©cution d'une action, assistÃ©e par les objets de mise en forme et de langage de macros. Ces derniers sont dÃ©crits plus bas. Bien qu'ils soient reprÃ©sentÃ©s comme des objets dans le cadre conceptuel, les objets de mise en forme et de langage de macros ne sont pas strictement des objets au sens du C++. En fait, l'objet de mise en forme est une collection de structures de donnÃ©es et un ensemble de fonction qui opÃšre sur ces derniÃšres, et l'objet de langage de macros est construit autour de displayclass, dÃ©finie dans lib/display.h, avec un support de conversion de flux provenant de lib/gsdlunicode.h.</Text>
+<Subsection id="actions">
+<Title>
+<Text id="978">Les actions</Text>
+</Title>
+<Content>
+<Table id="actions_in_greenstone">
+<Title>
+<Text id="979">Les actions dans Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="980"><i>action</i></Text>
+</th>
+<th width="397">
+<Text id="981">Classe de base pour l'hÃ©ritage virtuel.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="982"><i>authenaction</i></Text>
+</th>
+<th width="397">
+<Text id="983">Support de l'authentification utilisateur: demande Ã  l'utilisateur un mot de passe si aucun n'a Ã©tÃ© saisi; vÃ©rifie sa validitÃ©; et oblige l'utilisateur Ã  se rÃ©-authentifier si trop de temps s'est Ã©coulÃ© entre deux accÃšs.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="984"><i>collectoraction</i></Text>
+</th>
+<th width="397">
+<Text id="985">GÃ©nÃšre les pages pour le Collector.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="986"><i>documentaction</i></Text>
+</th>
+<th width="397">
+<Text id="987">Rapatrie les documents, les sections de documents, les portions de la hiÃ©rarchie de classification, ou les informations de mise en forme.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="988"><i>extlinkaction</i></Text>
+</th>
+<th width="397">
+<Text id="989">EmmÃšne un utilisateur directement vers une URL externe Ã  la collection, en gÃ©nÃ©rant ou non d'abord une page d'alerte (selon les<i>PrÃ©fÃ©rences</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="990"><i>pageaction</i></Text>
+</th>
+<th width="397">
+<Text id="991">GÃ©nÃšre une page en conjonction avec le langage de macros.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="992"><i>pingaction</i></Text>
+</th>
+<th width="397">
+<Text id="993">VÃ©rifie si une collection est en ligne ou non.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="994"><i>queryaction</i></Text>
+</th>
+<th width="397">
+<Text id="995">Effectue une recherche.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="996"><i>statusaction</i></Text>
+</th>
+<th width="397">
+<Text id="997">GÃ©nÃšre les pages d'administration.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="998"><i>tipaction</i></Text>
+</th>
+<th width="397">
+<Text id="999">Affiche une astuce alÃ©atoire Ã  l'utilisateur.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1000"><i>usersaction</i></Text>
+</th>
+<th width="397">
+<Text id="1001">GÃšre l'ajout, la destruction, et la gestion des accÃšs utilisateur.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="1002">Greenstone supporte les onze actions rÃ©sumÃ©es dans la tableÂ <CrossRef target="Table" ref="actions_in_greenstone"/>.</Text>
+<Figure id="using_the_cgiargsinfoclass_from_pageactioncpp" class="withLineNumber">
+<Title>
+<Text id="1003">Utilisation de cgiargsinfoclass depuis pageaction.cpp</Text>
+</Title>
+<CodeLine>cgiarginfo arg_ainfo;</CodeLine>
+<CodeLine>arg_ainfo.shortname = " a " ;</CodeLine>
+<CodeLine>arg_ainfo.longname = " action" ;</CodeLine>
+<CodeLine>arg_ainfo.multiplechar = true;</CodeLine>
+<CodeLine>arg_ainfo.argdefault = " p" ;</CodeLine>
+<CodeLine>arg_ainfo.defaultstatus = cgiarginfo::weak;</CodeLine>
+<CodeLine>arg_ainfo.savedarginfo = cgiarginfo::must;</CodeLine>
+<CodeLine>argsinfo.addarginfo (NULL, arg_ainfo);</CodeLine>
+<CodeLine/>
+<CodeLine>arg_ainfo.shortname = " p" ;</CodeLine>
+<CodeLine>arg_ainfo.longname = " page" ;</CodeLine>
+<CodeLine>arg_ainfo.multiplechar = true;</CodeLine>
+<CodeLine>arg_ainfo.argdefault = " home" ;</CodeLine>
+<CodeLine>arg_ainfo.defaultstatus = cgiarginfo::weak;</CodeLine>
+<CodeLine>arg_ainfo.savedarginfo = cgiarginfo::must;</CodeLine>
+<CodeLine>argsinfo.addarginfo (NULL, arg_ainfo);</CodeLine>
+</Figure>
+<Text id="1004">Les arguments CGI nÃ©cessaires Ã  une action sont formellement dÃ©clarÃ©s dans sa fonction constructeur avec cgiarginfo (dÃ©finie dans recpt/cgiargs.h). La figure <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/> montre un extrait de la fonction constructeur pageaction, qui dÃ©finit la taille et les propriÃ©tÃ©s des arguments CGI a et p.</Text>
+<Text id="1005">Pour chaque argument CGI, le constructeur doit spÃ©cifier son nom court (lignes 2 et 10), qui est le nom de la variable CGI Ã  proprement parler; un nom long (lignes 3 et 11) qui est utilisÃ© pour fournir une description plus parlante de l'action; s'il reprÃ©sente une valeur de caractÃšre simple ou multiple (lignes 4 et 12); possiblement, une valeur par dÃ©faut (lignes 5 et 13); ce qui se produit quand plusieurs valeurs par dÃ©faut sont fournies (lignes 6 et 14, Ã©tant donnÃ© qu'on peut positionner des valeurs par dÃ©faut dans les fichiers de configuration); et s'il faut ou non que la valeur soit conservÃ©e Ã  la fin de cette action (lignes 7 et 15).</Text>
+<Text id="1006">Ãtant donnÃ© qu'elle est embarquÃ©e dans le code, on peut gÃ©nÃ©rer automatiquement des pages web qui dÃ©taillent cette information. L'action statusaction produit cette information, et on peut la visualiser en saisissant l'URL de la page d'administration de Greenstone.</Text>
+<Text id="1007">Les douze actions hÃ©ritÃ©es sont construites dans main(), la fonction de premier niveau de l'exÃ©cutable library, dont la dÃ©finition est donnÃ©e dans le fichier recpt/librarymain.cpp. C'est aussi lÃ  que l'objet receptionist (dÃ©fini dans recpt/receptionist.cpp) est construit. La responsabilitÃ© de toutes les actions est passÃ©e Ã  l'objet receptionist, qui les traite en maintenant, sous la forme d'un champ de donnÃ©es, un tableau associatif de la classe de base d'action, indexÃ© par les noms d'actions.</Text>
+<Figure id="action_base_class_api">
+<Title>
+<Text id="1008">API de la classe de base d'action</Text>
+</Title>
+<CodeLine>class action {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   cgiargsinfoclass argsinfo;</CodeLine>
+<CodeLine>   text_t gsdlhome;</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   action ();</CodeLine>
+<CodeLine>   virtual ~action ();</CodeLine>
+<CodeLine>   virtual void configure (const text_t &amp;key, const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual text_t get_action_name ();</CodeLine>
+<CodeLine>   cgiargsinfoclass getargsinfo ();</CodeLine>
+<CodeLine>   virtual bool check_cgiargs (cgiargsinfoclass &amp;argsinfo,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool check_external_cgiargs (cgiargsinfoclass &amp;argsinfo,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              outconvertclass &amp;outconvert,</CodeLine>
+<CodeLine>              const text_t &amp;saveconf,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_cgihead_info (cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              response_t &amp;response,</CodeLine>
+<CodeLine>              text_t &amp;response_data,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool uses_display (cgiargsclass &amp;args);</CodeLine>
+<CodeLine>   virtual void define_internal_macros (displayclass &amp;disp,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void define_external_macros (displayclass &amp;disp,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool do_action (cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              browsermapclass *browsers,</CodeLine>
+<CodeLine>              displayclass &amp;disp,</CodeLine>
+<CodeLine>              outconvertclass &amp;outconvert,</CodeLine>
+<CodeLine>              ostream &amp;textout,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1009">La figureÂ <CrossRef target="Figure" ref="action_base_class_api"/> montre l'API de la classe de base d'action. Lors de l'exÃ©cution d'une action, l'objet receptionist appelle plusieurs fonctions, en commenÃ§ant par check_cgiargs(). La plupart l'aident Ã  vÃ©rifier, positionner, et dÃ©finir des valeurs et des macros, alors que la fonction do_action() engendre pour de bon la page produite. Si un objet hÃ©ritÃ© particulier ne dispose d'aucune dÃ©finition pour une fonction membre donnÃ©e, il passe Ã  la dÃ©finition de la classe de base qui implÃ©mente un comportement par dÃ©faut appropriÃ©.</Text>
+<Text id="1010">Voici des explications des fonctions membre:</Text>
+<BulletList>
+<Bullet>
+<Text id="1011">get_action_name()renvoie la valeur de l'argument CGIa, qui spÃ©cifie cette action. Le nom devrait Ãªtre court, mais peut faire plus d'un caractÃšre.</Text>
+</Bullet>
+<Bullet>
+<Text id="1012">check_cgiargs()est appelÃ©e avant les fonctionsget_cgihead_info(),define_external_macros(), etdo_action(). En cas d'erreur un message est Ã©crit surlogout; si l'erreur est importante la fonction renvoie la valeur faussefalseet ne produit aucun contenu de page.</Text>
+</Bullet>
+<Bullet>
+<Text id="1013">check_external_cgiargs()est appelÃ©e aprÃšscheck_cgiargs()pour toutes les actions. Il n'a d'usage que d'Ã©craser certains comportements par dÃ©faut, comme par exemple produire une page de connexion quand la page demandÃ©e exige une authentification. </Text>
+</Bullet>
+<Bullet>
+<Text id="1014">get_cgihead_info()positionne les informations de l'en-tÃªte CGI. Si la variableresponsevautlocation, alorsresponse_datacontient l'adresse de redirection. Siresponsevautcontent, alorsresponse_datacontient le type de contenu.</Text>
+</Bullet>
+<Bullet>
+<Text id="1015">uses_display()renvoietruesi la classe d'affichagedisplayclassest nÃ©cessaire pour produire le contenu de la page (comportement par dÃ©faut).</Text>
+</Bullet>
+<Bullet>
+<Text id="1016">define_internal_macros()dÃ©finit toutes les macros liÃ©es aux pages gÃ©nÃ©rÃ©es par cette action.</Text>
+</Bullet>
+<Bullet>
+<Text id="1017">define_external_macros()dÃ©finit toutes les macros qui pourraient Ãªtre utilisÃ©es par d'autres actions pour produire des pages.</Text>
+</Bullet>
+<Bullet>
+<Text id="1018">do_action()gÃ©nÃšre la page produite, normalement dans un flux Ã  travers l'objet de langage de macrodisplayet l'objet de conversion de la sortietextout. Renvoie la valeur faussefalsesi une erreur a empÃªchÃ© l'action de produire quoi que ce soit.</Text>
+</Bullet>
+</BulletList>
+<Text id="1019">Au dÃ©but de la dÃ©finition de classe, argsinfo est le champ de donnÃ©es protÃ©gÃ© (utilisÃ© dans l'extrait de code reprÃ©sentÃ© dans la figureÂ <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/>) qui stoke les informations d'argument CGI spÃ©cifiÃ©es dans une fonction constructeur d'action hÃ©ritÃ©e. L'autre champ de donnÃ©es, gsdlhome, enregistre GSDLHOME pour pouvoir y accÃ©der plus facilement<FootnoteRef id="5"/>. L'objet inclut Ã©galement les fonctions configure() et init() Ã  des fins d'initialisation.</Text>
+</Content>
+</Subsection>
+<Subsection id="formatting">
+<Title>
+<Text id="1020">Mise en forme</Text>
+</Title>
+<Content>
+<Figure id="core_data_structures_in_format">
+<Title>
+<Text id="1021">Structures de donnÃ©es centrales de la classe de mise en forme</Text>
+</Title>
+<CodeLine>enum command_t {comIf, comOr, comMeta, comText, comLink, comEndLink,</CodeLine>
+<CodeLine>         comNum, comIcon, comDoc,</CodeLine>
+<CodeLine>         comHighlight, comEndHighlight};</CodeLine>
+<CodeLine>enum pcommand_t {pNone, pImmediate, pTop, pAll};</CodeLine>
+<CodeLine>enum dcommand_t {dMeta, dText};</CodeLine>
+<CodeLine>enum mcommand_t {mNone, mCgiSafe};</CodeLine>
+<CodeLine>struct metadata_t {</CodeLine>
+<CodeLine>   void clear();</CodeLine>
+<CodeLine>   metadata_t () {clear();}</CodeLine>
+<CodeLine>   text_t metaname;</CodeLine>
+<CodeLine>   mcommand_t metacommand;</CodeLine>
+<CodeLine>   pcommand_t parentcommand;</CodeLine>
+<CodeLine>   text_t parentoptions;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>// The decision component of an {If}{decision,true-text,false-text}</CodeLine>
+<CodeLine>// formatstring. The decision can be based on metadata or on text;</CodeLine>
+<CodeLine>// normally that text would be a macro like</CodeLine>
+<CodeLine>// _cgiargmode_.</CodeLine>
+<CodeLine>struct decision_t {</CodeLine>
+<CodeLine>   void clear();</CodeLine>
+<CodeLine>   decision_t () {clear();}</CodeLine>
+<CodeLine>   dcommand_t command;</CodeLine>
+<CodeLine>   metadata_t meta;</CodeLine>
+<CodeLine>   text_t text;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>struct format_t {</CodeLine>
+<CodeLine>   void clear();</CodeLine>
+<CodeLine>   format_t () {clear();}</CodeLine>
+<CodeLine>   command_t command;</CodeLine>
+<CodeLine>   decision_t decision;</CodeLine>
+<CodeLine>   text_t text;</CodeLine>
+<CodeLine>   metadata_t meta;</CodeLine>
+<CodeLine>   format_t *nextptr;</CodeLine>
+<CodeLine>   format_t *ifptr;</CodeLine>
+<CodeLine>   format_t *elseptr;</CodeLine>
+<CodeLine>   format_t *orptr;</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1022">Bien que la mise en forme soit reprÃ©sentÃ©e comme une seule entitÃ© dans la figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/>, elle constitue en rÃ©alitÃ© une collection de structures de donnÃ©es et de fonctions, rassemblÃ©es dans le fichier d'en-tÃªtes recpt/formattools.h. Les structures de donnÃ©es centrales de la classe sont reprÃ©sentÃ©es figureÂ <CrossRef target="Figure" ref="core_data_structures_in_format"/>.</Text>
+<Figure id="data_structures_built_for_sample_format_statement">
+<Title>
+<Text id="1023">Structures de donnÃ©es construites pour l'exemple d'instruction de mise en forme</Text>
+</Title>
+<File width="395" height="152" url="images/Dev_Fig_43.png"/>
+</Figure>
+<Text id="1024">L'implÃ©mentation est plus facile Ã  expliquer avec un exemple. Quand l'instruction de mise en forme</Text>
+<CodeLine>format CL1Vlist</CodeLine>
+<Text id="1025" type="code">"[link][Title]{If}{[Creator], par [Creator]}[/link]"</Text>
+<Text id="1026">est lue dans un fichier de configuration de collection, elle est analysÃ©e par les fonctions de formattools.cpp et la structure de donnÃ©es interconnectÃ©e montrÃ©e figureÂ <CrossRef target="Figure" ref="data_structures_built_for_sample_format_statement"/> est construite. Quand il faut faire Ã©valuer l'instruction de mise en forme par une action, la structure de donnÃ©es est traversÃ©e. Le chemin pris au niveau des noeuds comIf et comOr dÃ©pend des mÃ©ta-donnÃ©es renvoyÃ©es par un appel au protocole.</Text>
+<Text id="1027">Il se peut que lors du rapatriement de mÃ©ta-donnÃ©es, le rÃ©sultat contienne d'autres macros et syntaxes de mise en forme. Ceci est gÃ©rÃ© par des allers-retours entre l'analyse et l'Ã©valuation, en fonction des besoins.</Text>
+</Content>
+</Subsection>
+<Subsection id="macro_language">
+<Title>
+<Text id="1028">Le langage de macros</Text>
+</Title>
+<Content>
+<Text id="1029">L'entitÃ© de langage de macros de la figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/>, tout comme celle de mise en forme, ne correspond pas Ã  une unique classe C++. Dans ce cas-ci il existe une classe centrale, mais l'implÃ©mentation du langage de macros dÃ©pend aussi de fonctions et de classes de support.</Text>
+<Text id="1030">Ici encore, on expliquera mieux l'implÃ©mentation en utilisant un exemple. Donnons d'abord quelques dÃ©finitions d'Ã©chantillons de macros qui illustrent les prioritÃ©s entre macros, puisÂ --Â Ã  l'aide d'un diagrammeÂ --Â nous dÃ©crirons les structures de donnÃ©es de base construites pour supporter cette activitÃ©. Enfin, nous prÃ©senterons et dÃ©crirons les fonctions membre publiques de displayclass, l'objet de macro de premier niveau.</Text>
+<Figure id="illustration_of_macro_precedence">
+<Title>
+<Text id="1031">Illustration de la prioritÃ© entre les macros</Text>
+</Title>
+<CodeLine>package query</CodeLine>
+<CodeLine>_header_ []         {_querytitle_}</CodeLine>
+<CodeLine>_header_ [l=en]     {Search page}</CodeLine>
+<CodeLine>_header_ [c=demo]   {&lt;table bgcolor=green&gt;&lt;tr&gt;&lt;td&gt;_querytitle_&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;}</CodeLine>
+<CodeLine>_header_ [v=1]      {_textquery_}</CodeLine>
+<CodeLine>_header_ [l=fr,v=1,c=hdl] {HDL Page de recherche}</CodeLine>
+</Figure>
+<Text id="1032">Dans une collection Greenstone habituelle, la prioritÃ© entre les macros est normalement: c (pour la collection) passe avant v (pour une interface graphique ou textuelle), qui passe avant l (pour la langue). Ceci est mis en place par la ligne</Text>
+<CodeLine>macroprecedence c,v,l</CodeLine>
+<Text id="1033">dans le fichier de configuration principal main.cfg. Les instructions de macros de la figureÂ <CrossRef target="Figure" ref="illustration_of_macro_precedence"/> dÃ©finissent des exemples de macros pour l'en-tÃªte _header_ du paquetage de requÃªte pour diverses valeurs de c, v, et l. Si les arguments CGI donnÃ©s lors de l'invocation d'une action comprennent c=hdl, v=1, et l=en, la macro _header_[v=1] serait alors sÃ©lectionnÃ©e pour l'affichage. Elle serait sÃ©lectionnÃ©e avant _content_[l=en] car v a la prioritÃ© sur l. La macro _content_[l=fr,v=1,c=hdl] ne serait pas sÃ©lectionnÃ©e parce que le paramÃštre de page pour l est diffÃ©rent.</Text>
+<Figure id="data_structures_representing_the_default_macros">
+<Title>
+<Text id="1034">Structures de donnÃ©es reprÃ©sentant les macros par dÃ©faut</Text>
+</Title>
+<File width="382" height="194" url="images/Dev_Fig_45.png"/>
+</Figure>
+<Text id="1035">La figureÂ <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/> montre la structure de donnÃ©es principale construite lors de la lecture des fichiers de macros spÃ©cifiÃ©s dans etc/main.cfg. Il s'agit essentiellement d'un tableau associatif de tableaux associatifs de tableaux associatifs. Le niveau le plus Ã©levÃ© (Ã  gauche) indexe le paquetage dont provient la macro, et le deuxiÃšme niveau indexe le nom de la macro. Le dernier niveau indexe tous les paramÃštres spÃ©cifiÃ©s, en stockant chacun sous le type mvalue qui enregistre, en plus de la valeur de la macro, le fichier dont elle provient. Par exemple, on peut trouver le texte dÃ©fini pour _header_[l=en] dans la figureÂ <CrossRef target="Figure" ref="illustration_of_macro_precedence"/> stockÃ© dans le plus bas des deux enregistrements mvalue dans la figureÂ <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/>.</Text>
+<Figure id="displayclass_api">
+<Title>
+<Text id="1036">API de la classe d'affichage displayclass</Text>
+</Title>
+<CodeLine>class displayclass</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   displayclass ();</CodeLine>
+<CodeLine>   ~displayclass ();</CodeLine>
+<CodeLine>   int isdefaultmacro (text_t package, const text_t &amp;macroname);</CodeLine>
+<CodeLine>   int setdefaultmacro (text_t package, const text_t &amp;macroname,  </CodeLine>
+<CodeLine>         text_t params, const text_t &amp;macrovalue);</CodeLine>
+<CodeLine>   int loaddefaultmacros (text_t thisfilename);</CodeLine>
+<CodeLine>   void openpage (const text_t &amp;thispageparams,</CodeLine>
+<CodeLine>         const text_t &amp;thisprecedence);</CodeLine>
+<CodeLine>   void setpageparams (text_t thispageparams,</CodeLine>
+<CodeLine>         text_t thisprecedence);</CodeLine>
+<CodeLine>   int setmacro (const text_t &amp;macroname,</CodeLine>
+<CodeLine>         text_t package,</CodeLine>
+<CodeLine>         const text_t &amp;macrovalue);</CodeLine>
+<CodeLine>   void expandstring (const text_t &amp;inputtext, text_t &amp;outputtext);</CodeLine>
+<CodeLine>   void expandstring (text_t package, const text_t &amp;inputtext,</CodeLine>
+<CodeLine>         text_t &amp;outputtext, int recursiondepth = 0);</CodeLine>
+<CodeLine>   void setconvertclass (outconvertclass *theoutc) {outc = theoutc;}</CodeLine>
+<CodeLine>   outconvertclass *getconvertclass () {return outc;}</CodeLine>
+<CodeLine>   ostream *setlogout (ostream *thelogout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1037">L'objet central de support du langage de macros est displayclass, dÃ©fini dans lib/display.h. Ses fonctions membre publiques sont reprÃ©sentÃ©es figureÂ <CrossRef target="Figure" ref="displayclass_api"/>. La classe lit les fichiers de macros spÃ©cifiÃ©s Ã  l'aide de loaddefaultmacros(), en stockant dans une section protÃ©gÃ©e de la classe (non reprÃ©sentÃ©e), le type de la structure de donnÃ©es montrÃ©e figureÂ <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/>. Il est Ã©galement permis au systÃšme d'exÃ©cution de positionner des macros Ã  l'aide de setmacro() (dans le dernier exemple de la sectionÂ <CrossRef target="Section" ref="how_the_conceptual_framework_fits_together"/>, pageaction positionne _homeextra_ comme Ã©tant la table des collections dynamiquement gÃ©nÃ©rÃ©e en utilisant cette fonction). Ceci est supportÃ© par un ensemble de tableaux associatifs similaires Ã  ceux utilisÃ©s pour reprÃ©senter les fichiers de macros (ce n'est pas identique, car le premier n'a pas besoin d'une couche de Â«paramÃštresÂ»). Dans displayclass, Les macros lues dans le fichier s'appellent les<i>macros par dÃ©faut</i>. Les macros locales spÃ©cifiÃ©es Ã  travers setmacro() s'appellent<i>macros courantes</i>, et sont effacÃ©es de la mÃ©moire aprÃšs la gÃ©nÃ©ration de la page.</Text>
+<Text id="1038">Quand il faut produire une page, openpage() est d'abord appelÃ©e pour communiquer les rÃ©glages courants des paramÃštres de page (l=en etc.). Ensuite, le texte et les macros passent dans un flux Ã  travers la classeÂ --Â typiquement depuis une actionclassÂ --Â en utilisant du code tel que:</Text>
+<CodeLine>cout &lt;&lt; text_t2ascii &lt;&lt; display &lt;&lt; "_amacro_ "</CodeLine>
+<CodeLine>         &lt;&lt; "_anothermacro_ ";</CodeLine>
+<Text id="1039">Le rÃ©sultat est que les macros sont dÃ©veloppÃ©es selon les rÃ©glages des paramÃštres de page. Si nÃ©cessaire, ces rÃ©glages peuvent Ãªtre modifiÃ©s en cours de procÃ©dure Ã  l'aide d'une action en utilisant setpageparams(). Les fonctions membre publiques restantes fournissent le support de bas niveau.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_receptionist_code">
+<Title>
+<Text id="1040">Le code du rÃ©ceptionniste</Text>
+</Title>
+<Content>
+<Text id="1041">Nous avons maintenant dÃ©crit les objets principaux du rÃ©ceptionniste. Nous dÃ©taillons ci-dessous les classes de support, situÃ©es dans GSDLHOME/src/recpt. Ã l'exception des cas oÃ¹ l'efficacitÃ© primeÂ --Â les dÃ©finitions sont alors inlineÂ --Â les dÃ©tails d'implÃ©mentation sont contenus dans le fichier .cpp correspondant au fichier d'en-tÃªtes. Les fichiers de support comportent souvent le mot tool (outil) dans leur nom, comme par exemple OIDtools.h et formattools.h.</Text>
+<Text id="1042">Un autre ensemble de fichiers de portÃ©e lexicale comprend le prÃ©fixe z3950. Ces fichiers fournissent un accÃšs distant aux bases de donnÃ©es et aux catalogues en ligne publiquement accessibles Ã  travers le protocole Z39.50.</Text>
+<Text id="1043">Le terme browserclass est inclus dans un autre groupe important de fichiers de support. Ces fichiers sont liÃ©s Ã  travers une hiÃ©rarchie d'hÃ©ritage virtuel. En tant que groupe, ils supportent une notion abstraite de navigation: gÃ©nÃ©ration de pages en sÃ©rie comportant des contenus de documents compartimentÃ©s ou des mÃ©ta-donnÃ©es. Les possibilitÃ©s des navigation comportent la lecture de documents triÃ©s par ordre alphabÃ©tique des titres ou par ordre chronologique des dates; l'exploration des rÃ©sultats d'une requÃªte par lot de dix entrÃ©es; et l'accÃšs aux pages individuelles d'un livre en utilisant le mÃ©canisme aller Ã  la page.... Chaque possibilitÃ© de navigation hÃ©rite de la classe de base, browserclass:</Text>
+<BulletList>
+<Bullet>
+<Text id="1044">datelistbrowserclass fournit le support pour les listes chronologiques;</Text>
+</Bullet>
+<Bullet>
+<Text id="1045">hlistbrowserclass fournit le support pour les listes horizontales;</Text>
+</Bullet>
+<Bullet>
+<Text id="1046">htmlbrowserclass fournit le support pour les pages HTML;</Text>
+</Bullet>
+<Bullet>
+<Text id="1047">invbrowserclass fournit le support pour les listes invisibles;</Text>
+</Bullet>
+<Bullet>
+<Text id="1048">pagedbrowserclass fournit le support pour aller Ã  une page particuliÃšre;</Text>
+</Bullet>
+<Bullet>
+<Text id="1049">vlistbrowserclass fournit le support pour les listes verticales.</Text>
+</Bullet>
+</BulletList>
+<Text id="1050">Les actions accÃšdent aux objets browserclass Ã  travers browsetools.h.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="140">
+<Text id="1051">OIDtools.h</Text>
+</th>
+<th width="390">
+<Text id="1052">Support fonctionnel pour l'Ã©valuation des identifiants de documents sur le protocole.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1053">action.h</Text>
+</th>
+<th width="390">
+<Text id="1054">Classe de base pour l'entitÃ© d'action dÃ©crite figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1055">authenaction.h</Text>
+</th>
+<th width="390">
+<Text id="1056">Action hÃ©ritÃ©e pour la gestion de l'authentification d'un utilisateur.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1057">browserclass.h</Text>
+</th>
+<th width="390">
+<Text id="1058">Classe de base pour les activitÃ©s de navigation abstraites.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1059">browsetools.h</Text>
+</th>
+<th width="390">
+<Text id="1060">Support fonctionnel pour l'accÃšs Ã  browserclass (hiÃ©rarchie). Les fonctionnalitÃ©s comprennent le dÃ©veloppement et la contraction de contenus, l'affichage d'une table des matiÃšres, et la gÃ©nÃ©ration de contrÃŽles tels que le mÃ©canisme aller Ã  la page....</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1061">cgiargs.h</Text>
+</th>
+<th width="390">
+<Text id="1062">DÃ©finit cgiarginfo, utilisÃ© dans la figureÂ <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/>, ainsi que le support d'autres structures de donnÃ©es pour les arguments CGI.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1063">cgiutils.h</Text>
+</th>
+<th width="390">
+<Text id="1064">Support fonctionnel pour les arguments CGI utilisant les structures de donnÃ©es dÃ©finies dans le fichier cgiargs.h.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1065">cgiwrapper.h</Text>
+</th>
+<th width="390">
+<Text id="1066">Support fonctionnel qui fait tout ce qui est nÃ©cessaire pour produire une page en utilisant le protocole CGI. L'accÃšs se fait Ã  travers la fonction</Text>
+<CodeLine>void cgiwrapper (receptionist &amp;recpt, text_t collection);</CodeLine>
+<Text id="1067">qui est la seule fonction dÃ©clarÃ©e dans le fichier d'en-tÃªtes. Tout le reste du fichier .cpp correspondant a une portÃ©e lexicale locale au fichier (par l'utilisation du mot-clef C++ static). Si la fonction est employÃ©e pour une collection particuliÃšre alors il faudrait positionner collection, sinon cette chaÃ®ne doit Ãªtre la chaÃ®ne vide "". Ce code comprend du support pour Fast-CGI.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1068">collectoraction.h</Text>
+</th>
+<th width="390">
+<Text id="1069">Action hÃ©ritÃ©e qui facilite la construction de collections par l'utilisateur final Ã  travers le Collector. La page gÃ©nÃ©rÃ©e provient de collect.dm et elle est contrÃŽlÃ©e par l'argument CGI p=page.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1070">comtypes.h</Text>
+</th>
+<th width="390">
+<Text id="1071">Types centraux du protocole.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1072">converter.h</Text>
+</th>
+<th width="390">
+<Text id="1073">Support objet pour les convertisseurs de flux.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1074">datelistbrowserclass.h</Text>
+</th>
+<th width="390">
+<Text id="1075">HÃ©ritÃ© de browserclass, cet objet fournit un support de navigation pour les listes chronologiques telles que celle qu'on peut voir dans la collection Â«ArchivesÂ» de Greenstone sous Dates dans la barre de navigation.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1076">documentaction.h</Text>
+</th>
+<th width="390">
+<Text id="1077">Action hÃ©ritÃ©e utilisÃ©e pour rapatrier une document ou une portion d'une hiÃ©rarchie de classification.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1078">extlinkaction.h</Text>
+</th>
+<th width="390">
+<Text id="1079">Action hÃ©ritÃ©e qui contrÃŽle si un utilisateur se rend directement Ã  un lien externe, ou s'il doit passer par une page d'avertissement qui l'alerte du fait qu'il s'apprÃªte Ã  sortir du systÃšme de bibliothÃšque numÃ©rique.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1080">formattools.h</Text>
+</th>
+<th width="390">
+<Text id="1081">Support fonctionnel pour l'analyse et l'Ã©valuation des instructions format de configuration de collection. DÃ©taillÃ© dans la sectionÂ <CrossRef target="Subsection" ref="formatting"/>, ci-dessus.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1082">historydb.h</Text>
+</th>
+<th width="390">
+<Text id="1083">Structures de donnÃ©es et support fonctionnel pour la gestion d'une base de donnÃ©es des requÃªtes prÃ©cÃ©dentes de telle sorte qu'un utilisateur puisse faire une nouvelle requÃªte en reprenant d'anciens termes.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1084">hlistbrowserclass.h</Text>
+</th>
+<th width="390">
+<Text id="1085">HÃ©ritÃ© de browserclass, cet objet fournit le support de navigation pour les listes horizontales.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1086">htmlbrowserclass.h</Text>
+</th>
+<th width="390">
+<Text id="1087">HÃ©ritÃ© de browserclass, cet objet fournit le support de navigation pour les pages HTML.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1088">htmlgen.h</Text>
+</th>
+<th width="390">
+<Text id="1089">Support fonctionnel pour mettre en valeur les termes de requÃªte dans une chaÃ®ne text_t.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1090">htmlutils.h</Text>
+</th>
+<th width="390">
+<Text id="1091">Support fonctionnel qui convertit une chaÃ®ne text_t en le HTML Ã©quivalent. Les symboles ", &amp;, &lt;, et &gt; sont respectivement convertis en &amp;quot;, &amp;amp;, &amp;lt;, et &amp;gt;.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1092">infodbclass.h</Text>
+</th>
+<th width="390">
+<Text id="1093">DÃ©finit deux classes: gdbmclass et infodbclass. La premiÃšre fournit l'API de Greenstone pour GDBM; la deuxiÃšme est la classe objet utilisÃ©e pour stocker une entrÃ©e d'enregistrement lue dans une base de donnÃ©es GDBM, et c'est essentiellement un tableau associatif de tableaux de chaÃ®nes text_t indicÃ©es par des entiers.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1094">invbrowserclass.h</Text>
+</th>
+<th width="390">
+<Text id="1095">HÃ©ritÃ© de browserclass, cet objet fournit le support de navigation pour les listes qui ne sont pas censÃ©es Ãªtre affichÃ©es (invisibles). </Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1096">nullproto.h</Text>
+</th>
+<th width="390">
+<Text id="1097">HÃ©ritÃ©e de recptproto, cette classe rÃ©alise le protocole vide, implÃ©mentÃ© par des appels de fonctions du rÃ©ceptionniste vers le serveur de collection.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1098">pageaction.h</Text>
+</th>
+<th width="390">
+<Text id="1099">Action hÃ©ritÃ©e qui, en conjonction avec le fichier de macros nommÃ© dans l'argument p=page, gÃ©nÃšre une page web.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1100">pagedbrowserclass.h</Text>
+</th>
+<th width="390">
+<Text id="1101">HÃ©ritÃ© de browserclass, cet objet fournit le support de navigation pour le mÃ©canisme aller Ã  la page..., vu par exemple dans la collection Gutenberg.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1102">pingaction.h</Text>
+</th>
+<th width="390">
+<Text id="1103">Action hÃ©ritÃ©e qui vÃ©rifie si une collection particuliÃšre rÃ©pond aux requÃªtes.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1104">queryaction.h</Text>
+</th>
+<th width="390">
+<Text id="1105">Action hÃ©ritÃ©e qui prend la requÃªte, les rÃ©glages et les prÃ©fÃ©rences stipulÃ©s, et effectue une recherche, en gÃ©nÃ©rant comme rÃ©sultat le sous-ensemble des documents o=num correspondants, en commenÃ§ant Ã  la position r=num.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1106">querytools.h</Text>
+</th>
+<th width="390">
+<Text id="1107">Support fonctionnel pour les requÃªtes.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1108">receptionist.h</Text>
+</th>
+<th width="390">
+<Text id="1109">Objet de premier niveau du rÃ©ceptionniste. Maintient un enregistrement des informations d'arguments CGI, des instantiations de chaque action hÃ©ritÃ©e, des instantiations de chaque objet de navigation, l'objet central de langage de macros displayclass, et tous les convertisseurs possibles.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1110">recptconfig.h</Text>
+</th>
+<th width="390">
+<Text id="1111">Support fonctionnel pour la lecture des fichiers de configuration principal et de site.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1112">recptproto.h</Text>
+</th>
+<th width="390">
+<Text id="1113">Classe de base pour le protocole.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1114">statusaction.h</Text>
+</th>
+<th width="390">
+<Text id="1115">Action hÃ©ritÃ©e qui gÃ©nÃšre, en conjonction avec le fichier status.dm, les diverses pages d'administration.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1116">tipaction.h</Text>
+</th>
+<th width="390">
+<Text id="1117">Action hÃ©ritÃ©e qui produit, en conjonction avec tip.dm, une page web contenant une astuce choisie au hasard parmi la liste d'astuces stockÃ©e dans le fichier tip.dm.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1118">userdb.h</Text>
+</th>
+<th width="390">
+<Text id="1119">Structure de donnÃ©es et support fonctionnel pour maintenir une base de donnÃ©es GDBM d'utilisateurs: leur mot de passe, leurs groupes, etc.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1120">usersaction.h</Text>
+</th>
+<th width="390">
+<Text id="1121">Une action d'administration hÃ©ritÃ©e de la classe de base qui supporte l'ajout et la destruction d'utilisateurs, ainsi que la modification de la liste des groupes auxquels ils appartiennent.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1122">vlistbrowserclass.h</Text>
+</th>
+<th width="390">
+<Text id="1123">HÃ©ritÃ© de browserclass, cet objet fournit un support de navigation pour les listes verticales, point d'appui des classificateurs. Par exemple, les fils du noeud des titres commenÃ§ant par la lettre N sont stipulÃ©s comme formant une VList.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1124">z3950cfg.h</Text>
+</th>
+<th width="390">
+<Text id="1125">Support de structure de donnÃ©es pour le protocole Z39.50. UtilisÃ© par z3950proto.cpp, qui dÃ©finit la classe de protocole principale (hÃ©ritÃ©e de la classe de base recptproto) et l'analyseur de fichier de configuration zparse.y (Ã©crit en YACC).</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1126">z3950proto.h</Text>
+</th>
+<th width="390">
+<Text id="1127">HÃ©ritÃ©e de recptproto, cette classe rÃ©alise le protocole de rÃ©fÃ©rence Z39.50 de sorte que le rÃ©ceptionniste de Greenstone puisse accÃ©der Ã  des sites de bibliothÃšques distantes hÃ©bergÃ©s sur serveur Z39.50.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1128">z3950server.h</Text>
+</th>
+<th width="390">
+<Text id="1129">Support complÃ©mentaire pour le protocole Z39.50.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="initialisation">
+<Title>
+<Text id="1130">Initialisation</Text>
+</Title>
+<Content>
+<Text id="1131">Dans Greenstone, l'initialisation est une opÃ©ration compliquÃ©e qui traite les fichiers de configuration et affecte des valeurs par dÃ©faut aux champs de donnÃ©es. En plus des fonctions d'hÃ©ritage et constructeur, les objets centraux dÃ©finissent les fonctions init() et configure() pour faciliter la normalisation de la tÃ¢che. MÃªme ainsi, l'ordre d'exÃ©cution peut Ãªtre difficile Ã  suivre. La prÃ©sente section dÃ©crit ce qui se passe.</Text>
+<Text id="1132">Greenstone utilise plusieurs fichiers de configuration pour des raisons diffÃ©rentes, mais tous suivent la mÃªme syntaxe. Ã moins qu'une ligne ne contienne que des blancs ou commence par un caractÃšre diÃšse (<i>#</i>), le premier mot dÃ©finit un mot-clef et les mots suivants reprÃ©sentent une configuration particuliÃšre pour ce mot-clef.</Text>
+<Text id="1133">Les lignes des fichiers de configuration sont passÃ©es une Ã  une Ã  la fonction configure() sous la forme de deux arguments: le mot-clef et un tableau des mots restants. En se fondant sur le mot-clef, un version particuliÃšre de la fonction configure() dÃ©cide si l'information l'intÃ©resse, et dans l'affirmative, la stocke. Par exemple, collectserver (qui correspond Ã  l'objet de collection de la figureÂ <CrossRef target="Figure" ref="greenstone_runtime_system"/>) traite les instructions de mise en forme du fichier de configuration de collection. Quand la fonction configure() reÃ§oit le mot-clef format, elle dÃ©clenche une instruction if qui stocke dans l'objet une copie du deuxiÃšme argument de la fonction. </Text>
+<Text id="1134">AprÃšs le traitement du mot-clef et avant de rendre la main, certaines versions de configure() passent les donnÃ©es aux fonctions configure() d'autres objets. L'objet rÃ©ceptionniste appelle les fonctions configure() des objets d'actions, de protocoles, et de navigation. L'objet de protocole vide appelle la fonction configure() de chaque objet de collection; l'objet de collection appelle les objets de filtre et source.</Text>
+<Text id="1135">En C++, les champs de donnÃ©es sont normalement initialisÃ©s par la fonction qui construit l'objet. Cependant, dans Greenstone, certaines initialisations dÃ©pendent de valeurs lues dans des fichiers de configuration, il faut donc procÃ©der Ã  un deuxiÃšme tour d'initialisations. C'est le but des fonctions membre init(), et dans certains cas cela mÃšne Ã  d'autres appels de fonctions configure().</Text>
+<Figure id="initialising_greenstone_using_the_null_protocol">
+<Title>
+<Text id="1136">Initialisation de Greenstone avec le protocole vide</Text>
+</Title>
+<CodeLine>============</CodeLine>
+<CodeLine>Main program</CodeLine>
+<CodeLine>============</CodeLine>
+<CodeLine>Statically construct Receptionist</CodeLine>
+<CodeLine>Statically construct NullProtocol</CodeLine>
+<CodeLine>Establish the value for 'gsdlhome' by reading gsdlsite.cfg</CodeLine>
+<CodeLine>Foreach directory in GSDLHOME/collect that isn't "modelcol":</CodeLine>
+<CodeLine>   Add directory name (now treated as collection name) to NullProtocol:</CodeLine>
+<CodeLine>       Dynamically construct Collection</CodeLine>
+<CodeLine>       Dynamically construct Gdbm class</CodeLine>
+<CodeLine>       Dynamically construct the Null Filter</CodeLine>
+<CodeLine>       Dynamically construct the Browse Filter</CodeLine>
+<CodeLine>       Dynamically construct MgSearch</CodeLine>
+<CodeLine>       Dynamically construct the QueryFilter</CodeLine>
+<CodeLine>       Dynamically construct the MgGdbmSource</CodeLine>
+<CodeLine>       Configure Collection with 'collection'</CodeLine>
+<CodeLine>           Passing 'collection' value on to Filters and Sources:</CodeLine>
+<CodeLine>       Configure Receptionist with 'collectinfo':</CodeLine>
+<CodeLine>           Passing 'collectinfo' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>Add NullProtocol to Receptionist</CodeLine>
+<CodeLine>Add in UTF-8 converter</CodeLine>
+<CodeLine>Add in GB converter</CodeLine>
+<CodeLine>Add in Arabic converter</CodeLine>
+<CodeLine>Foreach Action:</CodeLine>
+<CodeLine>   Statically construct Action</CodeLine>
+<CodeLine>   Add Action to Receptionist</CodeLine>
+<CodeLine>Foreach Browsers:</CodeLine>
+<CodeLine>   Statically construct Browser</CodeLine>
+<CodeLine>   Add Browser to Receptionist</CodeLine>
+<CodeLine>Call function cgiwrapper:</CodeLine>
+<CodeLine>   =================</CodeLine>
+<CodeLine>   Configure objects</CodeLine>
+<CodeLine>   =================</CodeLine>
+<CodeLine>   Configure Receptionist with 'collection'</CodeLine>
+<CodeLine>       Passing 'collection' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>       NullProtocol not interested in 'collection'</CodeLine>
+<CodeLine>   Configure Receptionist with 'httpimg'</CodeLine>
+<CodeLine>       Passing 'httpimg' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>       NullProtocol passing 'httpimg' on to Collection</CodeLine>
+<CodeLine>       Passing 'httpimg' value on to Filters and Sources:</CodeLine>
+<CodeLine>   Configure Receptionist with 'gwcgi'</CodeLine>
+<CodeLine>       Passing 'gwcgi' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>       NullProtocol passing 'gwcgi' on to Collection</CodeLine>
+<CodeLine>           Passing 'gwcgi' value on to Filters and Sources:</CodeLine>
+<CodeLine>   Reading in site configuration file gsdlsite.cfg</CodeLine>
+<CodeLine>       Configure Recptionist with 'gsdlhome'</CodeLine>
+<CodeLine>           Passing 'gsdlhome' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>           NullProtocol passing 'gsdlhome' on to Collection</CodeLine>
+<CodeLine>               Passing 'gsdlhome' value on to Filters and Sources:</CodeLine>
+<CodeLine>       Configure Recptionist with ...</CodeLine>
+<CodeLine>       ... and so on for all entries in gsdlsite.cfg</CodeLine>
+<CodeLine>   Reading in main configuration file main.cfg</CodeLine>
+<CodeLine>       Confiugre Recptionist with ...</CodeLine>
+<CodeLine>       ... and so on for all entries in main.cfg</CodeLine>
+<CodeLine>   ====================</CodeLine>
+<CodeLine>   Initialising objects</CodeLine>
+<CodeLine>   ====================</CodeLine>
+<CodeLine>   Initialise the Receptionist</CodeLine>
+<CodeLine>       Configure Receptionist with 'collectdir'</CodeLine>
+<CodeLine>           Passing 'collectdir' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>           NullProtocol not interested in 'collectdir'</CodeLine>
+<CodeLine>       Read in Macro files</CodeLine>
+<CodeLine>       Foreach Actions</CodeLine>
+<CodeLine>           Initialise Action</CodeLine>
+<CodeLine>       Foreach Protocol</CodeLine>
+<CodeLine>           Initialise Protocol</CodeLine>
+<CodeLine>           When Protocol==NullProtocol:</CodeLine>
+<CodeLine>               Foreach Collection</CodeLine>
+<CodeLine>                   Reading Collection's build.cfg</CodeLine>
+<CodeLine>                   Reading Collection's collect.cfg</CodeLine>
+<CodeLine>                       Configure Collection with 'creator'</CodeLine>
+<CodeLine>                           Passing 'creator' value on to Filters and Sources:</CodeLine>
+<CodeLine>                       Configure Collection with 'maintainer'</CodeLine>
+<CodeLine>                           Passing 'maintainer' value on to Filters and Sources:</CodeLine>
+<CodeLine>                       ... and so on for all entries in collect.cfg</CodeLine>
+<CodeLine>       Foreach Browsers</CodeLine>
+<CodeLine>           Initialise Browser</CodeLine>
+<CodeLine>   =============</CodeLine>
+<CodeLine>   Generate page</CodeLine>
+<CodeLine>   =============</CodeLine>
+<CodeLine>   Parse CGI arguments</CodeLine>
+<CodeLine>   Execute designated Action to produce page</CodeLine>
+<CodeLine>End.</CodeLine>
+</Figure>
+<Text id="1137">Les lignesÂ <CrossRef target="Figure" ref="initialising_greenstone_using_the_null_protocol"/> prÃ©sentent les messages de diagnostics gÃ©nÃ©rÃ©s par une version de Greenstone configurÃ©e pour mettre en valeur le processus d'initialisation. Le programme dÃ©marre Ã  la fonction main() du fichier recpt/librarymain.cpp. Il construit un objet de rÃ©ceptionniste et un objet de protocole vide, puis parcourt le fichier gsdlsite.cfg (situÃ© dans le mÃªme rÃ©pertoire que l'exÃ©cutable library) Ã  la recherche de gsdlhome et stocke son rÃ©sultat dans une variable. Pour chaque collection en ligneÂ --Â liste Ã©tablie en lisant les rÃ©pertoires prÃ©sents dans GSDLHOME/collectÂ --Â le programme construit un objet de collection, Ã  travers l'objet de protocole vide, qui contient des objets de filtre, de recherche et source, ainsi que quelques appels cÃ¢blÃ©s Ã  la fonction configure().</Text>
+<Text id="1138">La fonction main() ajoute ensuite l'objet de protocole vide au rÃ©ceptionniste, qui conserve un tableau de classe de base de protocoles dans un champ de donnÃ©es protÃ©gÃ©, et positionne ensuite plusieurs convertisseurs. La fonction main() construit tous les objets d'action et de navigation utilisÃ©s dans l'exÃ©cutable et les ajoute Ã  l'objet rÃ©ceptionniste. La fonction conclut en appelant la fonction cgiwrapper() de cgiwrapper.cpp, qui comporte elle-mÃªme une certaine quantitÃ© d'initialisation d'objets.</Text>
+<Text id="1139">La fonction cgiwrapper() comprend trois parties: configuration, initialisation, et gÃ©nÃ©ration de page. Tout d'abord, quelques appels cÃ¢blÃ©s Ã  la fonction configure() sont effectuÃ©s. Le fichier gsdlsite.cfg est ensuite lu et la fonction configure() est appelÃ©e pour chacune de ses lignes. MÃªme chose pour le fichier etc/main.cfg.</Text>
+<Text id="1140">La deuxiÃšme phase de la fonction cgiwrapper() effectue des appels Ã  init(). L'objet rÃ©ceptionniste ne fait qu'un appel Ã  sa fonction, mais cette invocation appelle les fonctions init() des diffÃ©rents objets qu'il contient. Un appel cÃ¢blÃ© Ã  configure() est d'abord effectuÃ© pour positionner collectdir, puis les fichiers de macros sont lus. La fonction init() de chaque action est appelÃ©e. MÃªme chose pour chaque protocole utilisÃ© dans le rÃ©ceptionnisteÂ --Â mais dans le cas du systÃšme dÃ©crit ici, seul le protocole vide y est stockÃ©. L'appel de la fonction init() de cet objet provoque d'autres configurations: pour chaque collection du protocole vide, les fichiers propres Ã  la collection build.cfg et collect.cfg sont lus et traitÃ©s, chaque ligne provoquant un appel Ã  la fonction configure().</Text>
+<Text id="1141">La phase finale de cgiwrapper() consiste Ã  analyser les arguments CGI, et appeler ensuite l'action appropriÃ©e. Tous ces appels sont effectuÃ©s avec le support de l'objet rÃ©ceptionniste.</Text>
+<Text id="1142">Les codes de configuration, initialisation, et de gÃ©nÃ©ration de page sont sÃ©parÃ©s car Greenstone est optimisÃ© pour fonctionner en tant que serveur (avec Fast-CGI, ou le protocole CORBA, ou la version Â«BibliothÃšque localeÂ» sous Windows). Dans ce mode de fonctionnement, le code de configuration et d'initialisation n'est effectuÃ© qu'une fois, et le programme demeure ensuite en mÃ©moire et gÃ©nÃšre de nombreuses pages web en rÃ©ponse aux requÃªtes des clients, sans nÃ©cessiter de rÃ©initialisation.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="configuring_your_greenstone_site">
+<Title>
+<Text id="1143">Configurer son site Greenstone</Text>
+</Title>
+<Content>
+<Text id="1144">Dans Greenstone, deux fichiers de configuration sont utilisÃ©s pour configurer divers aspects du site Greenstone. Il s'agit du fichier de configuration Â«principalÂ» main.cfg, qui se trouve dans GSDLHOME/etc, et du fichier de configuration Â«de siteÂ» gsdlsite.cfg, qui se trouve dans GSDLHOME/cgi-bin. Ces fichiers contrÃŽlent tous deux des aspects spÃ©cifiques de la configuration du site, et tous deux peuvent Ãªtre visualisÃ©s depuis la page d'administration de Greenstone.</Text>
+<Section id="main_configuration_file">
+<Title>
+<Text id="1145">Fichier de configuration principal</Text>
+</Title>
+<Content>
+<Text id="1146">Le fichier de configuration principal main.cfg sert Ã  configurer le rÃ©ceptionnisteÂ --Â la partie de Greenstone qui prÃ©sente les requÃªtes et affiche les pages. Vous pouvez tout contrÃŽler, des langues que l'interface peut utiliser aux journaux qui seront conservÃ©s.</Text>
+<Subsection id="site_maintenance_and_logging">
+<Title>
+<Text id="1147">Maintenance du site et journalisation</Text>
+</Title>
+<Content>
+<Text id="1148">Les lignes du fichier de configuration dictent la maniÃšre dont votre site Greenstone sera maintenu, quelles fonctionnalitÃ©s il offrira, quels Ã©vÃ©nements seront journalisÃ©s, et quelles notifications seront faites au mainteneur. La tableÂ <CrossRef target="Table" ref="configuration_options_for_site_maintenance_and_logging"/> dÃ©taille certaines des options disponibles; les options restantes sont dÃ©crites dans les sections suivantes.</Text>
+<Table id="configuration_options_for_site_maintenance_and_logging">
+<Title>
+<Text id="1149">Options de configuration pour la maintenance et la journalisation</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="1150"><b>Valeur</b></Text>
+</th>
+<th width="246">
+<Text id="1151"><b>But</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1152"><i>maintainer</i></Text>
+</th>
+<th width="151">
+<Text id="1153">vide ou une adresse de courrier Ã©lectronique </Text>
+</th>
+<th width="246">
+<Text id="1154">Adresse de courrier Ã©lectronique du mainteneur de site Ã  utiliser pour certaines notifications. Si elle est vide, les Ã©vÃ©nements de courrier Ã©lectronique sont dÃ©sactivÃ©s</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1155"><i>MailServer</i></Text>
+</th>
+<th width="151">
+<Text id="1156">vide ou un nom de serveur</Text>
+</th>
+<th width="246">
+<Text id="1157">Serveur de courrier Ã©lectronique sortant pour le site. Si elle est vide, c'est<i>mail.domaine-du-mainteneur</i>qui sera utilisÃ© (si par exemple le mainteneur est<i>aide@exemple.com</i>, la valeur par dÃ©faut sera<i>mail.exemple.com</i>). Si ceci n'aboutit pas Ã  un serveur SMTP valide, les Ã©vÃ©nements de courrier Ã©lectronique ne fonctionneront pas</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1158"><i>status</i></Text>
+</th>
+<th width="151">
+<Text id="1159"><i>enabled</i>(activÃ©e) ou<i>disabled</i>(dÃ©sactivÃ©e)</Text>
+</th>
+<th width="246">
+<Text id="1160">DÃ©termine si la page de<i>Maintenance et administration</i>doit Ãªtre rendue disponible</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1161"><i>collector</i></Text>
+</th>
+<th width="151">
+<Text id="1162"><i>enabled</i>(activÃ©e) ou<i>disabled</i>(dÃ©sactivÃ©e)</Text>
+</th>
+<th width="246">
+<Text id="1163">DÃ©termine si l'outil Â«CollectorÂ» de construction de collection pour l'utilisateur final est disponible</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1164"><i>logcgiargs</i></Text>
+</th>
+<th width="151">
+<Text id="1165"><i>true</i>(vraie) ou<i>false</i>(fausse)</Text>
+</th>
+<th width="246">
+<Text id="1166">Si la valeur est<i>true</i>, , un journal d'utilisation est conservÃ© dans le fichier <i>usage.txt</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1167"><i>usecookies</i></Text>
+</th>
+<th width="151">
+<Text id="1168"><i>true</i>(vraie) ou<i>false</i>(fausse)</Text>
+</th>
+<th width="246">
+<Text id="1169">Si la valeur est<i>true</i>,des informations relatives aux utilisateurs du site sont collectÃ©es (Ã  l'aide de<i>cookies</i>) et consignÃ©es dans le journal<i>usage.txt</i>(ceci ne fonctionne que si l'option<i>logcgiargs</i>a la valeur<i>true</i>)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1170"><i>LogDateFormat</i></Text>
+</th>
+<th width="151">
+<Text id="1171"><i>LocalTime</i>(heure locale) ou<br/>
+<i>UTCTime</i>(heure du temps universelâGMT) ou<br/>
+<i>Absolute</i>(heure absolue)</Text>
+</th>
+<th width="246">
+<Text id="1172">Format dans lequel consigner les dates et les heures dans les journaux.<i>LocalTime</i>produit le format Â«Thu Dec 07 12:34 NZDT 2000Â»,<i>UTCTime</i>est le mÃªme format mais en temps universel, et<i>absolute</i>est un entier reprÃ©sentant le nombre de secondes Ã©coulÃ©es depuis Â«00:00:00 01/01/1970 GMTÂ»</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1173"><i>LogEvents</i></Text>
+</th>
+<th width="151">
+<Text id="1174"><i>AllEvents</i>(tous les Ã©vÃ©nements) ou<br/>
+<i>CollectorEvents</i>(Ã©vÃ©nements du Collector) ou<br/>
+<i>disabled</i>(dÃ©sactivÃ©e)</Text>
+</th>
+<th width="246">
+<Text id="1175">Consigne certains Ã©vÃ©nements dans le journal<i>events.txt</i>.<i>AllEvents</i>consigne tous les Ã©vÃ©nements de Greenstone,<i>CollectorEvents</i>ne consigne que les Ã©vÃ©nements liÃ©s au Collector, et<i>disabled</i>ne consigne aucun Ã©vÃ©nement</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1176"><i>EmailEvents</i></Text>
+</th>
+<th width="151">
+<Text id="1177"><i>enabled</i>(activÃ©e) ou<i>disabled</i>(dÃ©sactivÃ©e)</Text>
+</th>
+<th width="246">
+<Text id="1178">Envoie un courrier Ã©lectronique au mainteneur (s'il y en a unâvoir l'option maintainer) Ã  chaque fois qu'un Ã©vÃ©nement se produit</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1179"><i>EmailUserEvents</i></Text>
+</th>
+<th width="151">
+<Text id="1180"><i>enabled</i>(activÃ©e) ou<i>disabled</i>(dÃ©sactivÃ©e)</Text>
+</th>
+<th width="246">
+<Text id="1181">Envoie un courrier Ã©lectronique Ã  l'utilisateur lors de certains Ã©vÃ©nementsâtels que la fin de la construction d'une collection par le Collector</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1182"><i>macrofiles</i></Text>
+</th>
+<th width="151">
+<Text id="1183">liste de noms de fichiers de macros</Text>
+</th>
+<th width="246">
+<Text id="1184">DÃ©termine quelles macros sont disponibles pour le logiciel d'interface utilisateur de Greenstone</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="language_support">
+<Title>
+<Text id="1185">Support des langues</Text>
+</Title>
+<Content>
+<Text id="1186">Le fichier de configuration main.cfg contient deux types d'entrÃ©es qui affectent la gestion des diffÃ©rentes langues. Elles dÃ©terminent quelles langues et quels encodages seront disponibles dans la page de PrÃ©fÃ©rences. Les lignes encoding (encodage) spÃ©cifient les diffÃ©rents types d'encodage de caractÃšres qui peuvent Ãªtre sÃ©lectionnÃ©s. Les lignes language (langue) spÃ©cifient quelles langues on pourra sÃ©lectionner pour l'interface utilisateur (il doit bien sÃ»r exister une macro de langue pour chaque langue possible).</Text>
+<Text id="1187">La ligne encoding peut contenir quatre valeurs possibles: shortname (nom court), longname (nom long), map (correspondance), et multibyte (multi-octets). La valeur shortname est l'Ã©tiquette du jeu de caractÃšres standard, et doit Ãªtre spÃ©cifiÃ©e pour tous les encodages. La valeur longname donne le nom d'encodage spÃ©cifiÃ© sur la page de PrÃ©fÃ©rences. En son absence la valeur par dÃ©faut est celle de shortname. La valeur map est obligatoire pour tous les encodages Ã  l'exception de l'UTF-8, qui est gÃ©rÃ© de maniÃšre interne (et qui devrait toujours Ãªtre activÃ©). La valeur multibyte devrait Ãªtre positionnÃ©e pour tous les jeux de caractÃšres qui nÃ©cessitent plus d'un octet par caractÃšre. Le fichier main.cfg spÃ©cifie de nombreux encodages, dont la plupart sont dÃ©sactivÃ©s car commentÃ©s. Pour activer un encodage, ÃŽtez le caractÃšre de commentaire Â«<i>#</i>Â».</Text>
+<Text id="1188">Chaque ligne language peut contenir trois valeurs possibles: shortname (nom court), longname (nom long), et default_encoding (encodage par dÃ©faut). La valeur shortname est le symbole de langue en deux lettres ISO 639, et elle est obligatoire. La valeur longname donne le nom de la langue spÃ©cifiÃ© sur la page de PrÃ©fÃ©rences. En son absence la valeur par dÃ©faut est celle de shortname. L'option default_encoding sert Ã  spÃ©cifier l'encodage prÃ©fÃ©rÃ© pour cette langue.</Text>
+</Content>
+</Subsection>
+<Subsection id="page_parameters_and_cgi_arguments">
+<Title>
+<Text id="1189">ParamÃštres de page et arguments CGI</Text>
+</Title>
+<Content>
+<Text id="1190">On peut dÃ©finir des paramÃštres de page et des arguments CGI dans le fichier de configuration main.cfg. Rappelez-vous qu'Ã  la figureÂ <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/> la plupart des arguments CGI sont dÃ©finis au sein mÃªme du code C++ de la bibliothÃšque. Cependant, il est parfois utile de dÃ©finir de nouveaux arguments ou d'Ã©diter les arguments existants dans les fichiers de configuration, ce qui Ã©vite de recompiler la bibliothÃšque.</Text>
+<Text id="1191">Pour ce faire, vous utiliserez l'option de configuration cgiarg. Elle peut prendre jusqu'Ã  six arguments, qui sont les suivants: shortname (nom court), longname (nom long), multiplechar (caractÃšres multiples), argdefault (argument par dÃ©faut), defaultstatus (Ã©tat par dÃ©faut), et savedarginfo (informations de sauvegarde d'argument). Ces arguments correspondent aux options d'arguments CGI dÃ©crits sectionÂ <CrossRef target="Section" ref="receptionist"/>. Par exemple, dans le fichier main.cfg, par dÃ©faut, l'option de configuration cgiarg sert Ã  positionner les valeurs par dÃ©faut des arguments CGI existants a et p Ã  p et home, respectivement. </Text>
+<Text id="1192">Les paramÃštres de page sont un cas particulier d'arguments CGI qui correspondent aux paramÃštres des fichiers de macros de Greenstone. Par exemple, l'argument CGI l correspond directement au paramÃštre l= dans les fichiers de macros. On utilise l'option de configuration pageparam pour dÃ©finir un argument CGI comme Ã©tant Ã©galement un paramÃštre de page.</Text>
+<Text id="1193">La meilleure maniÃšre d'apprendre les diffÃ©rentes options de configuration possibles dans le fichier de configuration main.cfg est de faire des expÃ©riences avec ce dernier. Souvenez-vous que si vous utilisez la version Â«BibliothÃšque localeÂ» de Greenstone sous Windows, il faut redÃ©marrer le serveur pour que toute modification des fichiers de configuration soit prise en compte.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="site_configuration_file">
+<Title>
+<Text id="1194">Fichier de configuration de site</Text>
+</Title>
+<Content>
+<Table id="lines_in_gsdlsitecfg">
+<Title>
+<Text id="1195">Lignes du fichier<i>gsdlsite.cfg</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="1196"><b>Ligne</b></Text>
+</th>
+<th width="397">
+<Text id="1197"><b>Fonction</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1198"><i>gsdlhome</i></Text>
+</th>
+<th width="397">
+<Text id="1199">Un chemin vers le rÃ©pertoire<i>GSDLHOME</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1200"><i>httpprefix</i></Text>
+</th>
+<th width="397">
+<Text id="1201">L'adresse web de<i>GSDLHOME</i>. Si la racine de documents de votre serveur web a la valeur<i>GSDLHOME</i>vous n'avez pas besoin de cette ligne.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1202"><i>httpimage</i></Text>
+</th>
+<th width="397">
+<Text id="1203">L'adresse web du rÃ©pertoire contenant les images de l'interface utilisateur. Si la racine de documents de votre serveur web a la valeur<i>GSDLHOME</i>ceci vaudra<i>/images</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1204"><i>gwcgi</i></Text>
+</th>
+<th width="397">
+<Text id="1205">L'adresse web du prÃ©sent script CGI (se termine gÃ©nÃ©ralement par<i>library</i>). Ceci n'est pas nÃ©cessaire si votre serveur web positionne la variable d'environnement<i>SCRIPT_NAME</i>(nom de script).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1206"><i>maxrequests</i></Text>
+</th>
+<th width="397">
+<Text id="1207">(Ne s'applique que si l'on utilise<i>fast-cgi</i>.) Nombre de requÃªtes que Fast-CGI doit traiter avant de rendre la main. Lors du dÃ©bogage de la bibliothÃšque il faut positionner ceci Ã  une faible valeur, et Ã  une valeur Ã©levÃ©e dans le cas contraire, en production.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="1208">Le fichier de configuration de site gsdlsite.cfg positionne des variables utilisÃ©es par le logiciel de bibliothÃšque et le serveur web au moment de l'exÃ©cution, et se trouve dans le mÃªme rÃ©pertoire que le programme library. La tableÂ <CrossRef target="Table" ref="lines_in_gsdlsitecfg"/> dÃ©crit les lignes de ce fichier; elles sont expliquÃ©es dans la sectionÂ 5 du Guide d'installation de la bibliothÃšque numÃ©rique Greenstone.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_a_stl">
+<Title>
+<Text id="1209">A. La bibliothÃšque standard de patrons (templates) pour C++</Text>
+</Title>
+<Content>
+<Text id="1210">La bibliothÃšque standard de patrons (STL) est une bibliothÃšque bibliothÃšque trÃšs rÃ©pandue de code C++, dÃ©veloppÃ©e par Silicon Graphics (www.sgi.com). Cette annexe donne un bref aperÃ§u de ses fonctions principales, utilisÃ©es tout au long du code de Greenstone. Pour une description plus dÃ©taillÃ©e, consultez le manuel de rÃ©fÃ©rence officiel de STL, disponible en ligne sur le site webwww.sgi.com, ou l'un des nombreux manuels traitant de STL, tel que celui de Josuttis (1999).</Text>
+<Text id="1211">Comme le suggÃšre le mot Â«patronÂ», STL n'est pas juste une bibliothÃšque d'objets prÃªts Ã  l'emploi. CouplÃ©e avec le mÃ©canisme de patrons de C++, elle fournit aux programmeurs une solution pour dÃ©velopper leurs propres objets de maniÃšre concise, objets qui tapent dans les fonctionnalitÃ©s algorithmiques embarquÃ©es dans STL. VoilÃ  qui ajoute une couche de complexitÃ©, mais cela en vaut la peine.</Text>
+<Text id="1212">Pour aider Ã  comprendre les extraits de code Greenstone donnÃ©s dans le prÃ©sent manuel, nous donnons quelques exemples de STL Ã  des fins de didacticiel.</Text>
+<Section id="lists">
+<Title>
+<Text id="1213">A..1 Listes</Text>
+</Title>
+<Content>
+<Figure id="programming_a_list_of_integers" class="withLineNumber">
+<Title>
+<Text id="1214">Programmer une liste d'entiers</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>#define nil 0</CodeLine>
+<CodeLine/>
+<CodeLine>struct intlist {</CodeLine>
+<CodeLine>   int val;</CodeLine>
+<CodeLine>   struct intlist* next;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_list(intlist* head)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   int total = 0;</CodeLine>
+<CodeLine>   intlist* curr = head;</CodeLine>
+<CodeLine>   while (curr!=nil)</CodeLine>
+<CodeLine>   {</CodeLine>
+<CodeLine>       total += curr-&gt;val;</CodeLine>
+<CodeLine>       curr = curr-&gt;next;</CodeLine>
+<CodeLine>   }</CodeLine>
+<CodeLine/>
+<CodeLine>   return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>void main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   intlist node1 = { 5, nil };</CodeLine>
+<CodeLine>   intlist node2 = { 4, nil };</CodeLine>
+<CodeLine>   node2.next = &amp;node1;</CodeLine>
+<CodeLine/>
+<CodeLine>   int total = total_int_list(&amp;node2);</CodeLine>
+<CodeLine>  cout &lt;&lt; " List items total to: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="1215">Ãtudions tout d'abord deux programmes qui implÃ©mentent une liste d'entiers. L'un utilise des types C++ de base (la Â«bonne vieille maniÃšre de faireÂ»), tandis que l'autre utilise STL. La figureÂ <CrossRef target="Figure" ref="programming_a_list_of_integers"/> montre le code source de l'implÃ©mentation qui n'utilise<i>pas</i>STL. Les lignes 5-8 dÃ©finissent les structures de donnÃ©es de base que nous allons utiliser: le champ val stocke la valeur de l'entier, et next (prochain) pointe vers le prochain Ã©lÃ©ment de la listeÂ --Â une implÃ©mentation classique d'une liste chaÃ®nÃ©e, en somme.</Text>
+<Text id="1216">Pour illustrer l'utilisation de la structure de donnÃ©es, le programme principal (lignes 23-32) initialise une liste d'entiers avec les Ã©lÃ©ments [5, 4]. Il appelle ensuite la fonction total_int_list (total des entiers de la liste, dÃ©finie lignes 10-21), fonction qui prend pour unique argument un pointeur vers la tÃªte d'une liste et qui fait la somme de toutes les valeurs que la liste contient. La valeur renvoyÃ©e (Â«9Â», dans notre cas) est affichÃ©e Ã  l'Ã©cran.</Text>
+<Text id="1217">Le gros du travail est accompli par les lignes 12-18. On commence par un peu d'initialisation: la variable locale total est mise Ã  zÃ©ro, et curr (courant) pointe vers le dÃ©but de la liste. Une boucle while ajoute ensuite l'Ã©lÃ©ment entier courant au sous-total courant (total += curr-&gt;val;) avant de passer au prochain Ã©lÃ©ment (curr = curr-&gt;next;). La boucle while termine quand curr vaut nil (vide), ce qui signifie qu'il ne reste plus aucun Ã©lÃ©ment de la liste Ã  traiter.</Text>
+<Figure id="programming_a_list_of_integers_using_stl">
+<Title>
+<Text id="1218">Programmer une liste d'entiers en utilisant STL</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine>#include &lt;list&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_list(list&lt;int&gt;* head)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   int total = 0;</CodeLine>
+<CodeLine>   list&lt;int&gt;::iterator curr = head-&gt;begin();</CodeLine>
+<CodeLine>   while (curr!=head-&gt;end())</CodeLine>
+<CodeLine>   {</CodeLine>
+<CodeLine>       total += *curr;</CodeLine>
+<CodeLine>       curr++;</CodeLine>
+<CodeLine>   }</CodeLine>
+<CodeLine/>
+<CodeLine>   return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>void main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   list&lt;int&gt; vals;</CodeLine>
+<CodeLine>   vals.push_back(5);</CodeLine>
+<CodeLine>   vals.push_back(4);</CodeLine>
+<CodeLine/>
+<CodeLine>   int total = total_int_list(&amp;vals);</CodeLine>
+<CodeLine>   cout &lt;&lt; " List items total to: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="1219">La figureÂ <CrossRef target="Figure" ref="programming_a_list_of_integers_using_stl"/> montre un programme Ã©quivalent qui utilise STL. Il n'est plus nÃ©cessaire de dÃ©finir une structure de donnÃ©es adÃ©quate dans le code; seule la directive #include &lt;list&gt; de la ligne 2, qui inclut le patron de liste dÃ©fini dans STL, est nÃ©cessaire. L'objet est appelÃ© une Â«classe de contenanceÂ» car lors de la dÃ©claration d'une variable de ce type on spÃ©cifie aussi le type qu'on souhaite qu'elle stocke. On rÃ©alise une liste d'entiers ligne 19 avec l'instruction list&lt;int&gt; vals;. On peut ajouter des Ã©lÃ©ments Ã  l'objet en utilisant la fonction membre push_back(), comme dans les lignes 20-21.</Text>
+<Text id="1220">Le gros du travail est accompli par les lignes 6-12. On commence toujours deux initialisations et une boucle while, mais Ã  part cela la nouvelle syntaxe a fort peu en commun avec l'ancienne. Cette nouvelle maniÃšre de faire les choses gravite autour d'une variable de type iterator (itÃ©rateur, ligne 7). De nombreuses classes STL incluent des types iterator pour fournir une maniÃšre uniforme de traverser une suite d'objets de contenance. Le premier Ã©lÃ©ment est renvoyÃ© avec begin() (dÃ©but) et l'Ã©lÃ©ment qui suit le dernier Ã©lÃ©ment est renvoyÃ© avec end(). On passe Ã  l'Ã©lÃ©ment suivant par l'opÃ©ration d'incrÃ©mentation ++, qui est surchargÃ©e par la classe d'itÃ©ration pour implÃ©menter cette tÃ¢che, et on accÃšde Ã  la valeur stockÃ©e par dÃ©rÃ©fÃ©renciation (*curr, ligne), opÃ©ration elle aussi surchargÃ©e.</Text>
+<Text id="1221">L'implÃ©mentation STL de ce programme est un peu plus concise que le code conventionnel (25 lignes, Ã  comparer aux 31 originales). Les gains sont plus importants dans des projets plus volumineux, car l'objet list (liste) de STL est plus puissant que ce que cet exemple en illustre ici. C'est par exemple une liste doublement chaÃ®nÃ©e qui supporte diverses maniÃšres d'insÃ©rer et d'effacerÂ --Â et il faudrait des efforts de programmation supplÃ©mentaires pour intÃ©grer ces fonctionnalitÃ©s Ã  la version de liste d'entiers classique.</Text>
+<Text id="1222">Remarquez que le paramÃštre total_int_list de la figureÂ <CrossRef target="Figure" ref="programming_a_list_of_integers_using_stl"/> a Ã©tÃ© implÃ©mentÃ© sous la forme d'un entier, pour correspondre au pointeur utilisÃ© dans la variable total_int_list dans la figureÂ <CrossRef target="Figure" ref="programming_a_list_of_integers"/>. En STL, il est souvent plus naturel (et plus souhaitable) d'utiliser des rÃ©fÃ©rences plutÃŽt que des pointeurs. Le paramÃštre devient alors list&lt;int&gt;&amp; head, (tÃªte), et ses fonctions membre sont appelÃ©es par la syntaxe head.begin(); (dÃ©but de tÃªte) et ainsi de suite.</Text>
+</Content>
+</Section>
+<Section id="maps">
+<Title>
+<Text id="1223">A..2 Correspondances</Text>
+</Title>
+<Content>
+<Text id="1224">Lorsque l'on implÃ©mente un systÃšme de bibliothÃšque numÃ©rique, il est utile de pouvoir stocker des Ã©lÃ©ments dans un tableau indicÃ© par des chaÃ®nes de texte plutÃŽt que par des nombres. Dans Greenstone, par exemple, ceci simplifie grandement le stockage des fichiers de macros aprÃšs leur lecture; de mÃªme pour les divers fichiers de configuration. Un type de donnÃ©es qui permet un tel accÃšs s'appelle un<i>tableau associatif</i>, et les langages de programmation modernes de haut niveau en proposent souvent. On l'appelle aussi parfois<i>tableau de hachage</i>(surtout en Perl), puisque la technique habituelle d'implÃ©mentation d'un index de texte est de hacher (calculer une somme de contrÃŽle) les valeurs du tableau associatif.</Text>
+<Figure id="using_associative_arrays_in_stl" class="withLineNumber">
+<Title>
+<Text id="1225">Utiliser des tableaux associatifs en STL</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine>#include &lt;map&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_table(map&lt;char*, int&gt;&amp; table)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   int total = 0;</CodeLine>
+<CodeLine>   map&lt;char*, int&gt;::iterator curr = table.begin();</CodeLine>
+<CodeLine>   while (curr!=table.end())</CodeLine>
+<CodeLine>   {</CodeLine>
+<CodeLine>       total += (curr-&gt;second);</CodeLine>
+<CodeLine>       curr++;</CodeLine>
+<CodeLine>   }</CodeLine>
+<CodeLine/>
+<CodeLine>   return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>int main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   map&lt;char*, int&gt; table;</CodeLine>
+<CodeLine>   table["Alice"] = 31;</CodeLine>
+<CodeLine>   table["Peter"] = 24;</CodeLine>
+<CodeLine>   table["Mary"]   = 47;</CodeLine>
+<CodeLine/>
+<CodeLine>   int total = total_int_table(table);</CodeLine>
+<CodeLine>   cout &lt;&lt; " Age total: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>  }</CodeLine>
+</Figure>
+<Text id="1226">En STL, on fait des tableaux associatifs en utilisant l'objet map (carte, ou correspondance). La figureÂ <CrossRef target="Figure" ref="using_associative_arrays_in_stl"/> prÃ©sente un exemple quelque peu artificiel qui stocke l'Ã¢ge de trois personnes (Alice, Pierre, et Marie) dans un tableau associatif indicÃ© par leurs prÃ©noms (lignes 19-22). Le problÃšme est d'Ã©crire une fonction qui calcule l'Ã¢ge total de toutes les personnes prÃ©sentes, sans savoir combien elles sont ni qui elles sont. Bien sÃ»r, on pourrait rÃ©soudre ce problÃšme avec un classique tableau d'entiers indicÃ©s numÃ©riquement. L'exemple est contraint d'illustrer les fonctionnalitÃ©s de l'objet map et de mettre en valeur les similaritÃ©s de traitement avec l'objet list Ã©quipÃ© d'un iterator.</Text>
+<Text id="1227">Tout comme list, map est une classe de contenance. Cependant, lorsque l'on dÃ©clare une variable de ce type, il faut spÃ©cifier deux<FootnoteRef id="6"/>choses: le type d'index, et le type d'Ã©lÃ©ment. Comme on peut le voir ligne 19, on obtient un tableau associatif qui stocke des entiers indicÃ©s par des chaÃ®nes en Ã©crivant char* (c'est la maniÃšre de dÃ©clarer une chaÃ®ne en C++) en tant que type d'indiÃ§age suivi de int en tant que type d'Ã©lÃ©ment.</Text>
+<Text id="1228">Il existe plusieurs maniÃšres de stocker des Ã©lÃ©ments dans le tableau associatif. Dans l'exemple, on utilise lignes 20-22 l'indice de tableau [ ], qui est surchargÃ©, pour initialiser le tableau avec les Ã¢ges des trois personnes. La ressemblance entre total_int_tableÂ --Â qui effectue le calcul principal dans le programmeÂ --Â et total_int_list de la figureÂ <CrossRef target="Figure" ref="programming_a_list_of_integers"/> est frappante. Ces deux objets sont en fait presque identiques, et ce n'est pas une coÃ¯ncidence. STL utilise lourdement l'hÃ©ritage de sorte que des objets diffÃ©rents utilisent encore les mÃªmes opÃ©rations fondamentales. C'est particuliÃšrement le cas des itÃ©rateurs (iterator). Les petites diffÃ©rences entre les deux fonctions sont que l'itÃ©rateur est maintenant tirÃ© de map&lt;char*, int&gt;, et que l'accÃšs Ã  ses Ã©lÃ©ments se fait avec curr-&gt;second()Â --Â en effet la dÃ©rÃ©fÃ©renciation de la variable (*curr) est dÃ©finie comme devant renvoyer un objet de type pair. Ceci enregistre Ã  la fois le nom d'index (first, ou Â«premierÂ») et la valeur de l'Ã©lÃ©ment (second, ou Â«deuxiÃšmeÂ»), mais seul la deuxiÃšme nous intÃ©resse. Ã part cela, le code est identique. La seule diffÃ©rence restanteÂ --Â le changement de l'unique argument de la fonction d'un pointeur vers une rÃ©fÃ©renceÂ --Â est superficielle.</Text>
+<Text id="1229">Greenstone utilise largement deux autres types STL: vector (vecteur), et set (ensemble). Le premier facilite les tableaux dynamiques, et le second supporte les opÃ©rations ensemblistes mathÃ©matiques telles que l'union, l'intersection, et la diffÃ©rence ensembliste.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="bibliography">
+<Title>
+<Text id="1230">Bibliographie</Text>
+</Title>
+<Content>
+<Text id="1231">Aulds, C. (2000) Linux Apache Web Server Administration. Sybex.</Text>
+<Text id="1232">Bainbridge, D., Buchanan, G., McPherson, J., Jones, S., Mahoui, A. and Witten, I.H. (2001) Â«Greenstone: A platform for distributed digital library developmentÂ». Rapport de recherche, dÃ©partement d'informatique, universitÃ© de Waikato, Nouvelle-ZÃ©lande.</Text>
+<Text id="1233">Christiansen, T. Torkington, N. and Wall, L. (1998) Perl en action. Ãditions O'Reilly.</Text>
+<Text id="1234">Coar, K.A.L. (1998) Apache Server For Dummies. IDG Books.</Text>
+<Text id="1235">Deitel, H.M. and Deitel, P.J. (1994) C++: How to Program. Prentice Hall, Englewood Cliffs, New Jersey.</Text>
+<Text id="1236">Dublin Core (2001) Â«The Dublin Core Metadata InitiativeÂ» at http://purl.org/dc/, le 16 janvier 2001.</Text>
+<Text id="1237">Josuttis, N.M. (1999) The C++ standard library: a tutorial and reference. Addison-Wesley, 1999.</Text>
+<Text id="1238">Keller, M. and Holden, G. (1999) Apache Server for Windows Little Black Book. Coriolis Group.</Text>
+<Text id="1239">Schwartz, R.L. and Christiansen, T. (1997) Introduction Ã  Perl (2Ãšme Ã©dition). Ãditions O'Reilly.</Text>
+<Text id="1240">Slama, D., Garbis, J. and Russell, P. (1999) Enterprise CORBA. Prentice Hall, Englewood Cliffs, New Jersey.</Text>
+<Text id="1241">Stroustrup, B. (1997) The C++ Programming Language. Addison-Wesley.</Text>
+<Text id="1242">Thiele, H. (1997) Â«The Dublin Core and Warwick Framework: A Review of the Literature, March 1995-September 1997Â»<i>D-Lib Magazine</i>, janvier.&lt;http://www.dlib.org/dlib/january98/01thiele.html&gt;</Text>
+<Text id="1243">Wall, L., Christiansen, T. and Orwant, J. (2000) Programmation en Perl (3Ãšme Ã©dition). Ãditions O'Reilly.</Text>
+<Text id="1244">Weibel, S. (1999) Â«The State of the Dublin Core Metadata InitiativeÂ» <i>D-Lib Magazine</i>, Volume 5 Number 4; avril.&lt;http://www.dlib.org/dlib/april99/04weibel.html&gt;</Text>
+<Text id="1245">Witten, I.H., Moffat, A. and Bell, T.C. (1999) Managing gigabytes: compressing and indexing documents and images. Morgan Kaufmann, San Francisco.</Text>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="1246">... Greenstone Sur des systÃšmes Windows 95/98, l'exÃ©cution de setup.bat peut Ã©chouer avec le message d'erreur Hors de l'espace d'environnement. Dans ce cas, Ã©ditez le fichier config.sys de votre systÃšme (qui se trouve habituellement sous Cconfig.sys) et ajoutez-y la ligne shell=C:command.com /e:4096 /p (oÃ¹ C reprÃ©sente la lettre de votre lecteur systÃšme) pour agrandir la taille de la table d'environnement. Il vous faudra redÃ©marrer l'ordinateur pour que cette modification soit prise en compte. RÃ©pÃ©tez ensuite les Ã©tapes effectuÃ©es avant l'obtention de ce message d'erreur.</Text>
+</Footnote>
+<Footnote id="2">
+<Text id="1247">... Gutenberg N.D.T.: projet de numÃ©risation de la littÃ©rature classique en langue anglaise libre de droits, disponible sur le web.</Text>
+</Footnote>
+<Footnote id="3">
+<Text id="1248">...nuggetÂ» Attention: dans Greenstone, les expressions rationnelles sont interprÃ©tÃ©es dans le langage Perl, et les conventions diffÃšrent subtilement d'autres conventions. Par exemple, Â«*Â» correspond Ã  zÃ©ro ou plusieurs occurrences du caractÃšre qui prÃ©cÃšde, et Â«.Â» remplace n'importe quel caractÃšreÂ --Â donc Â«nugget.*Â» correspond Ã  toute chaÃ®ne commenÃ§ant par Â«nuggetÂ», que ce prÃ©fixe soit suivi d'un point ou non. Pour imposer un point Ã  cette position il faudrait Ã©chapper le point, et Ã©crire Â«nugget..*Â» Ã  la place.</Text>
+</Footnote>
+<Footnote id="4">
+<Text id="1249">... collection Remarquez que les versions les plus rÃ©centes de la collection Â«DemoÂ» utilisent un classificateur Hierarchy pour reprÃ©senter les mÃ©ta-donnÃ©es how to (comment faire). Dans de tels cas de figure, elles apparaÃ®tront un peu diffÃ©remment que dans la figureÂ <CrossRef target="Figure" ref="list_classifier"/>.</Text>
+</Footnote>
+<Footnote id="5">
+<Text id="1250">... facilement La valeur gsdlhome provient du fichier gsdlsite.cfg situÃ© dans le mÃªme rÃ©pertoire que l'exÃ©cutable CGI library, alors que GSDLHOME est positionnÃ© en exÃ©cutant le script setup qui accÃšde Ã  un fichier diffÃ©rent; il est donc techniquement possible que les deux valeurs soient diffÃ©rentes. C'est possible, mais pas dÃ©sirable, et le texte ci-dessus est Ã©crit dans l'hypothÃšse oÃ¹ ces deux valeurs sont Ã©gales.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/fr/Install_fr.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/fr/Install_fr.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/fr/Install_fr.xml	(revision 13632)
@@ -0,0 +1,1007 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">GREENSTONE DIGITAL LIBRARY</Text><Updated date="14-Dec-2006 by lh92"/>
+</Heading>
+<Title>
+<Text id="2">Guide d'installation de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Title>
+<Author>
+<Text id="3">Ian H. Witten et Stefan Boddie</Text>
+</Author>
+<Affiliation>
+<Text id="4">DÃ©partement d'informatique,<br/>UniversitÃ© de Waikato, Nouvelle-ZÃ©lande</Text>
+</Affiliation>
+<Text id="5">Greenstone est une suite logicielle destinÃ©e Ã  la construction et Ã  la distribution de collections de bibliothÃšques numÃ©riques. Cette suite fournit une nouvelle maniÃšre d'organiser l'information et de la publier sur l'Internet ou sur un cÃ©dÃ©rom. Greenstone est produit par le projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande (dÃ©pendant de l'universitÃ© de Waikato), et distribuÃ© en coopÃ©ration avec l'UNESCO et le projet de bibliothÃšques pour l'humanitÃ©. C'est un logiciel Open Source, qu'on peut obtenir Ã  l'URLhttp://greenstone.org, et qui est diffusÃ© selon les termes de la licence publique gÃ©nÃ©rale de GNU.</Text>
+<Comment>
+<Text id="6">Nous souhaitons nous assurer que ce logiciel fonctionne bien pour vous.<br/>Faites-nous part, en anglais, de tout problÃšme Ã  l'adresse Ã©lectronique<br/>.</Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">Mars 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">Ã propos de ce manuel</Text>
+</Title>
+<Content>
+<Text id="10">Ce document explique comment installer Greenstone pour pouvoir l'utiliser sur votre ordinateur. Il explique aussi comment obtenir les logiciels associÃ©s, qui sont librement disponibles: le serveur web Apache et Perl. Nous avons fait au mieux pour simplifier au maximum la procÃ©dure d'installation.</Text>
+<Text id="11">Ce logiciel fonctionne sur diffÃ©rentes plates-formes et diffÃ©rentes configurations. Par consÃ©quent, de nombreux dÃ©tails pourront impacter la procÃ©dure d'installation. La sectionÂ <CrossRef target="Chapter" ref="versions_of_greenstone"/> liste des questions qu'il faudra se poser avant d'installer Greenstone. La sectionÂ <CrossRef target="Chapter" ref="installation_procedure"/> dÃ©taille la procÃ©dure d'installation pour les diffÃ©rentes versions; ne lisez que la portion relative Ã  votre systÃšme d'exploitation. La sectionÂ <CrossRef target="Chapter" ref="greenstone_collections"/> dÃ©crit les collections de bibliothÃšques numÃ©riques de dÃ©monstration comprises dans la distribution. La sectionÂ <CrossRef target="Chapter" ref="setting_up_webserver"/> explique comment configurer des serveurs web communs, Apache et PWS/IIS de Microsoft, de maniÃšre Ã  les faire fonctionner avec Greenstone. La sectionÂ <CrossRef target="Chapter" ref="configuring_your_site"/> dÃ©crit plusieurs options de configuration de Greenstone, et la sectionÂ <CrossRef target="Chapter" ref="personalizing"/> montre comment crÃ©er une page d'accueil personnalisÃ©e pour votre installation de bibliothÃšque numÃ©rique. Enfin, une annexe <CrossRef target="Chapter" ref="appendix_associated_software"/> liste des logiciels associÃ©s et donne pour chacun la maniÃšre de l'obtenir.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="12">Documents d'accompagnement</Text>
+</Title>
+<Content>
+<Text id="13">L'ensemble des documents de Greenstone comprend cinq volumes:</Text>
+<BulletList>
+<Bullet>
+<Text id="14">Guide d'installation de la bibliothÃšque numÃ©rique Greenstone (<i>ce document-ci</i>)</Text>
+</Bullet>
+<Bullet>
+<Text id="15">Guide de l'utilisateur de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="17">BibliothÃšque numÃ©rique Greenstone: du papier Ã  la collection</Text>
+</Bullet>
+<Bullet>
+<Text id="18">BibliothÃšque numÃ©rique Greenstone: Utilisation de "L'organizer"</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">Remerciements</Text>
+</Title>
+<Content>
+<Text id="20">Le logiciel Greenstone a vu le jour grÃ¢ce Ã  un effort de collaboration entre de nombreuses personnes. Rodger McNab et Stefan Boddie en sont les principaux architectes et dÃ©veloppeurs. Des contributions ont Ã©tÃ© faites par David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, et Stuart Yeates. D'autres membres du Projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande ont Ã©galement donnÃ© des conseils et inspirÃ© les concepteurs du systÃšme: Mark Apperley, Sally Jo Cunningham, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, et Lloyd Smith. Nous remercions aussi tous ceux qui ont contribuÃ© au dÃ©veloppement des modules sous licence GNU GPL qui font partie de cette distribution: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE, XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="versions_of_greenstone">
+<Title>
+<Text id="21">Les versions de Greenstone</Text>
+</Title>
+<Content>
+<Text id="22">Greenstone fonctionne sur diffÃ©rentes plates-formes et configurations, comme rÃ©sumÃ© figureÂ <CrossRef target="Figure" ref="different_options"/>.</Text>
+<Figure id="different_options">
+<Title>
+<Text id="23"><b>Figure:</b>Les options disponibles pour Windows et Unix de Greenstone</Text>
+</Title>
+<File width="542" height="264" url="images/Install_Fig_1.png"/>
+</Figure>
+<Text id="24">La procÃ©dure d'installation dÃ©pend de nombreux paramÃštres. Avant de continuer la lecture, posez-vous les questions suivantes:</Text>
+<BulletList>
+<Bullet>
+<Text id="25">Utilisez-vous Windows ou Unix?</Text>
+</Bullet>
+<Bullet>
+<Text id="26">Si vous utilisez Windows, utilisez-vous 3.1/3.11 ou bien une version plus rÃ©cente? Bien qu'il soit possible de visualiser des collections et de servir d'autres ordinateurs sur le mÃªme rÃ©seau avec des machines pourvues de Windows 3.1/3.11, il n'est pas possible d'y construire de nouvelles collections. La version complÃšte de Greenstone fonctionne sur Windows 95/98/Me, et sur NT/2000.</Text>
+</Bullet>
+<Bullet>
+<Text id="27">Si vous utilisez Unix, s'agit-il de Linux ou d'une autre version d'Unix? Dans le cas de Linux, une version binaire du systÃšme complet, facile Ã  installer, est fournie. Pour d'autres Unix il vous faudra installer le code source et le compiler, ce qui pourra nÃ©cessiter l'installation d'autres logiciels.</Text>
+</Bullet>
+<Bullet>
+<Text id="28">Dans le cas des systÃšmes Windows NT/2000 ou Unix, pouvez-vous vous connecter en tant qu'Â«administrateurÂ» ou Â«rootÂ»? Ceci est parfois nÃ©cessaire pour configurer un serveur web de maniÃšre adÃ©quate pour qu'il puisse fonctionner avec Greenstone.</Text>
+</Bullet>
+<Bullet>
+<Text id="29">Souhaitez-vous disposer du code source? Si vous utilisez Windows ou Linux, vous pouvez vous contenter d'installer des binaires. Mais si vous souhaitez Ã©galement disposer du code source, il est dans la distribution de Greenstone.</Text>
+</Bullet>
+<Bullet>
+<Text id="30">Souhaitez-vous construire de nouvelles collections de bibliothÃšques numÃ©riques? Si tel est le cas, il vous faudra disposer de Perl, qui est librement disponible pour Windows comme pour Unix.</Text>
+</Bullet>
+<Bullet>
+<Text id="31">Votre ordinateur comprend-il un serveur web? Greenstone est fourni avec un serveur web pour Windows. Cependant, si vous disposez dÃ©jÃ  d'un serveur web, vous pouvez souhaitez continuer Ã  l'employer. Dans le cas des systÃšmes Unix, il vous faudra utiliser un serveur web.</Text>
+</Bullet>
+<Bullet>
+<Text id="32">Savez-vous comment configurer votre serveur web? Si vous n'utilisez pas le serveur web fourni avec Greenstone, il vous faudra lÃ©gÃšrement modifier la configuration de votre serveur web pour qu'il puisse reconnaÃ®tre Greenstone.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Chapter>
+<Chapter id="installation_procedure">
+<Title>
+<Text id="33">La procÃ©dure d'installation</Text>
+</Title>
+<Content>
+<Text id="34">Il existe des versions Windows et Unix de Greenstone, sous formes binaire comme de code source. L'interface utilisateur de Greenstone utilise un navigateur web: Netscape Navigator ou Internet Explorer conviennent tous deux, Ã  partir de leurs versions 4.0. Si vous ne disposez pas de navigateur web, le cÃ©dÃ©rom comprend les versions Windows de Netscape.</Text>
+<Section id="windows">
+<Title>
+<Text id="35">Windows</Text>
+</Title>
+<Content>
+<Text id="36">Si c'est Unix que vous employez, rendez-vous directement Ã  la sectionÂ 2.2. Les utilisateurs de Windows qui se contenteront d'une installation simple et immÃ©diate iront lire quant Ã  eux la procÃ©dure d'installation simplifiÃ©e, sectionÂ 2.1.1. Greenstone occupe environ 40 mÃ©ga-octets d'espace disque.</Text>
+<Text id="37">Si vous souhaitez vous Ã©carter un tant soit peu de la configuration par dÃ©faut, il vous faudra dÃ©cider d'installer le binaire ou le code source. En cas de doute, optez pour le binaire. La procÃ©dure d'installation est la mÃªme dans les deux cas, et les sections suivantes dÃ©taillent les options disponibles.</Text>
+<Text id="38">Ã la fin de l'installation, sautez Ã  la sectionÂ 3.</Text>
+<Subsection id="simple_installation">
+<Title>
+<Text id="39">Installation simplifiÃ©e</Text>
+</Title>
+<Content>
+<Text id="40">Pour installer la version Windows Ã  partir du cÃ©dÃ©rom, insÃ©rez le disque dans le lecteur (par exemple, sous D). Si aprÃšs environ 20 secondes d'attente la procÃ©dure d'installation n'a toujours pas automatiquement dÃ©marrÃ©, cliquez sur le menu DÃ©marrer, choisissez ExÃ©cuter et tapez DWindowsSetup.exe, oÃ¹ Â«DÂ» reprÃ©sente la lettre identifiant votre lecteur de cÃ©dÃ©rom. Les utilisateurs de Windows 3.1 choisiront ExÃ©cuter Ã  partir du Gestionnaire de fichiers et taperont, eux aussi, DWindowsSetup.exe.</Text>
+<Text id="41">Pour que l'installation se dÃ©roule le plus simplement possible, contentez-vous d'accepter les choix par dÃ©faut Ã  chaque Ã©tape en cliquant sur le bouton Suivant. C'est tout! Greenstone est installÃ© dans CProgram Filesgsdl.</Text>
+<Text id="42">Ã la fin de l'installation, vous dÃ©marrerez Greenstone en cliquant sur le bouton DÃ©marrer, ouvrirez le menu Programmes, et sÃ©lectionnerez BibliothÃšque NumÃ©rique Greenstone (Greenstone Digital Library). Ceci invoquera une boÃ®te de dialogue; cliquez simplement sur Entrer dans la bibliothÃšque. VoilÃ  qui dÃ©marrera automatiquement votre navigateur web et chargera la page d'accueil de la bibliothÃšque numÃ©rique Greenstone, qui devrait ressembler Ã  la figureÂ <CrossRef target="Figure" ref="your_greenstone_home_page"/>. Vous pourrez alors entrer dans la collection de dÃ©monstration de Greenstone en cliquant sur son icone.</Text>
+<Figure id="your_greenstone_home_page">
+<Title>
+<Text id="43">La page d'accueil de Greenstone</Text>
+</Title>
+<File width="395" height="327" url="images/Install_Fig_2.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="windows_binaries">
+<Title>
+<Text id="44">Binaires pour Windows</Text>
+</Title>
+<Content>
+<Text id="45">Le cÃ©dÃ©rom comprend deux binaires distincts pour Windows: la BibliothÃšque locale et la BibliothÃšque Web. L'installation par dÃ©faut dÃ©crite ci-dessus sÃ©lectionne la version Â«BibliothÃšque localeÂ», que nous vous recommandons chaudement d'utiliser. La Â«BibliothÃšque WebÂ», qui est bien plus difficile Ã  utiliser, n'est nÃ©cessaire que si vous employez dÃ©jÃ  un serveur web et rencontrez des conflits d'affectation de numÃ©ro de port en utilisant la Â«BibliothÃšque localeÂ». MalgrÃ© une appellation modeste, cette derniÃšre fournit un service web complet et autonome.</Text>
+<Text id="46">BibliothÃšque locale. Ceci permet Ã  tout ordinateur Ã©quipÃ© de Windows de servir des collections Greenstone dÃ©jÃ  construites. La collection Greenstone Â«DemoÂ» sera installÃ©e automatiquement; vous pourrez Ã©galement installer les autres collections prÃ©sentes sur le cÃ©dÃ©rom (voyez ceci en <CrossRef target="Chapter" ref="greenstone_collections"/>). Le logiciel de bibliothÃšque locale est le mÃªme que celui qui est prÃ©sent sur les cÃ©dÃ©roms produits par le systÃšme Greenstone.</Text>
+<Text id="47">La bibliothÃšque locale est destinÃ©e aux ordinateurs isolÃ©s, ou aux ordinateurs non Ã©quipÃ©s de serveur web. Elle contient un petit serveur web pour que les autres ordinateurs du mÃªme rÃ©seau puissent Ã©galement accÃ©der Ã  la bibliothÃšque (mais ce serveur web n'est pas trÃšs configurable).</Text>
+<Text id="48">Le logiciel de bibliothÃšque locale dÃ©tecte automatiquement si l'ordinateur dispose de logiciels de communication en rÃ©seau ou s'il est connectÃ© Ã  un rÃ©seau. Il fonctionnera correctement dans toutes les combinaisons possibles, mais on pourra nÃ©anmoins rencontrer deux problÃšmes. Il se peut que Greenstone:</Text>
+<BulletList>
+<Bullet>
+<Text id="49">provoque une connexion tÃ©lÃ©phonique non dÃ©sirÃ©e;</Text>
+</Bullet>
+<Bullet>
+<Text id="50">ou Ã©choue Ã  cause de la prÃ©sence de logiciels de communication en rÃ©seau mal installÃ©s.</Text>
+</Bullet>
+</BulletList>
+<Text id="51">C'est pour de telles situations qu'une version restreinte de la bibliothÃšque locale est fournie, version qui ne fonctionne qu'avec Netscape (et pas Internet Explorer). Lors de l'invocation de la version Â«BibliothÃšque localeÂ» de Greenstone, la boÃ®te de dialogue qui apparaÃ®t propose un bouton pour sÃ©lectionner cette version restreinte. Ã moins que les problÃšmes mentionnÃ©s ci-dessus ne se posent, prÃ©fÃ©rez-lui toujours la version standard.</Text>
+<Text id="52">BibliothÃšque Web. Ceci permet Ã  tout ordinateur disposant d'un serveur web de servir des collections Greenstone dÃ©jÃ  construites. Comme dans le cas de la bibliothÃšque locale mentionnÃ© ci-dessus, la collection Greenstone Â«DemoÂ» sera installÃ©e automatiquement. Vous pourrez Ã©galement installer les autres collections prÃ©sentes sur le cÃ©dÃ©rom (voyez ceci en sectionÂ <CrossRef target="Chapter" ref="greenstone_collections"/>).</Text>
+<Text id="53">La bibliothÃšque web diffÃšre de la bibliothÃšque locale en ce sens qu'elle est destinÃ©e aux ordinateurs qui disposent dÃ©jÃ  d'un serveur web.</Text>
+<Text id="54">Pour utiliser la bibliothÃšque web, vous aurez aussi besoin</Text>
+<BulletList>
+<Bullet>
+<Text id="55">d'un logiciel serveur web, comme Apache par exemple (voyez l'annexe <CrossRef target="Chapter" ref="appendix_associated_software"/> Ã  ce sujet).</Text>
+</Bullet>
+<Bullet>
+<Text id="56">Le Collector. Ce composant, inclus Ã  la fois dans la bibliothÃšque locale et dans la bibliothÃšque web, vous permet de construire des collections autour de contenus de votre choix. Pour l'utiliser, vous aurez aussi besoin de Perl. Nous recommandons ActivePerl (voyez l'annexe <CrossRef target="Chapter" ref="appendix_associated_software"/> Ã  ce sujet).</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="">
+<Title>
+<Text id="57">Configuration de serveur web pour Windows (ne concerne que la bibliothÃšque web)</Text>
+</Title>
+<Content>
+<Text id="58">La version de Greenstone en bibliothÃšque locale a cet avantage qu'elle fonctionne directement, sans nÃ©cessiter de configuration particuliÃšre. Dans le cas de la version en bibliothÃšque web, il vous faudra en revanche apporter quelques modifications aux rÃ©glages de votre serveur web.</Text>
+<Text id="59">Si vous disposez dÃ©jÃ  d'un serveur web, il faudra apporter quelques modifications Ã  sa configuration pour pouvoir utiliser votre installation de Greenstone. Le script d'installation dÃ©taille ces modifications dans le cas du serveur web ApacheÂ --Â voyez la sectionÂ <CrossRef target="Section" ref="pws_and_iis_webservers"/> pour obtenir des instructions relatives Ã  la configuration des serveurs web PWS et IIS. Vous aurez peut-Ãªtre besoin d'un administrateur systÃšme pour reconfigurer un serveur web dÃ©jÃ  installÃ©Â --Â votre administrateur systÃšme devrait comprendre les instructions fournies par le script d'installation.</Text>
+<Text id="60">Si vous ne disposez pas dÃ©jÃ  d'un serveur web, il vous faudra en installer un (voyez l'annexe <CrossRef target="Chapter" ref="appendix_associated_software"/> pour obtenir des informations sur le serveur Apache). Il vous faudra ensuite le configurer de maniÃšre appropriÃ©e. La sectionÂ <CrossRef target="Chapter" ref="setting_up_webserver"/> dÃ©taille les portions de l'installation d'un serveur web qui concernent Greenstone, et comment il faut les modifier. Tout revient Ã  ajouter une petite dizaine de lignes Ã  un fichier de configuration.</Text>
+</Content>
+</Subsection>
+<Subsection id="windows_source">
+<Title>
+<Text id="61">Code source pour Windows</Text>
+</Title>
+<Content>
+<Text id="62">Le code source de Greenstone occupe 50 mÃ©ga-octets d'espace disque, mais 90 mÃ©ga-octets seront nÃ©cessaires pour procÃ©der Ã  la compilation. Pour compiler ce code source sur Windows vous devrez Ã©galement disposer</Text>
+<BulletList>
+<Bullet>
+<Text id="63">du compilateur Microsoft Visual C++ (nous travaillons actuellement sur l'aplanissement de petits problÃšmes posÃ©s par la compilation de Greenstone avec diverses versions de GCC pour Windows).</Text>
+</Bullet>
+</BulletList>
+<Text id="64">(Vous n'aurez pas besoin de GDBM, le gestionnaire de bases de donnÃ©es de GNU, car il est inclus dans la distribution de Greenstone).</Text>
+<Text id="65">Il est peu probable que vous parveniez Ã  compiler Greenstone sur une machine fonctionnant sous un systÃšme Windows 3.1/3.11.</Text>
+<Text id="66">Au cas oÃ¹ vous recompilez Greenstone et souhaitez utiliser la version recompilÃ©e pour crÃ©er des cÃ©dÃ©roms, sachez que le code produit par les versions rÃ©centes du compilateur Microsoft Visual C++ ne fonctionne pas sous les systÃšmes Windows 3.1/3.11, mais fonctionne sans problÃšmes sous des systÃšmes ultÃ©rieurs (95, 98, Me, NT, 2000). Si vous souhaitez que vos cÃ©dÃ©roms puissent Ãªtre utilisÃ©s sur des versions anciennes de Windows, il vous faudra utiliser une autre version du compilateur. De plus, Greenstone utilise STL, la bibliothÃšque standard de patrons (templates) pour C++, et mÃªme si d'anciens compilateurs sont parfois fournis avec STL, la version fournie ne fonctionne pas toujours trÃšs bien. C'est pourquoi, pour recompiler Greenstone de telle sorte qu'il produise des cÃ©dÃ©roms qui fonctionneront sur d'anciennes versions de Windows, vous aurez besoin</Text>
+<BulletList>
+<Bullet>
+<Text id="67">du compilateur Microsoft Visual C++, version 4.0 ou 4.2.</Text>
+</Bullet>
+<Bullet>
+<Text id="68">d'une version externe de STL, la bibliothÃšque standard de patrons pour C++. STL est empaquetÃ©e avec Greenstone afin d'Ãªtre utilisÃ©e avec ces versions du compilateur.</Text>
+</Bullet>
+</BulletList>
+<Text id="69">Vous remarquerez que la procÃ©dure d'installation pour Windows ne tente pas de compiler Greenstone si vous choisissez d'installer le code source. Pour obtenir des instructions de compilation de Greenstone propres Ã  votre plate-forme et Ã  votre compilateur, voyez le fichier Install, placÃ© dans le rÃ©pertoire principal de Greenstone (CProgram Filesgsdl par dÃ©faut) pendant la procÃ©dure d'installation.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="unix">
+<Title>
+<Text id="70">Unix</Text>
+</Title>
+<Content>
+<Text id="71">La prÃ©sente section s'adresse aux utilisateurs d'Unix; les utilisateurs de Windows auront avantage Ã  consulter la sectionÂ <CrossRef target="Section" ref="how_to_find_greenstone"/>. Il vous faut choisir d'installer le binaire ou le code source: le binaire occupe 50 mÃ©ga-octets d'espace disque, et le code source a besoin de 160 mÃ©ga-octets pour compiler.</Text>
+<Subsection id="unix_binaries">
+<Title>
+<Text id="72">Binaires Unix</Text>
+</Title>
+<Content>
+<Text id="73">Le binaire est prÃ©vu pour une distribution Linux pour puce Intel de type x86, avec support pour les binaires ELF. Voici des exemples de distributions qui remplissent ces conditions:</Text>
+<BulletList>
+<Bullet>
+<Text id="74">RedHat 5.1</Text>
+</Bullet>
+<Bullet>
+<Text id="75">SuSE Linux 6.1</Text>
+</Bullet>
+<Bullet>
+<Text id="76">Debian 2.1</Text>
+</Bullet>
+<Bullet>
+<Text id="77">Slackware 4.0</Text>
+</Bullet>
+</BulletList>
+<Text id="78">Cela devrait Ã©galement Ãªtre le cas de versions plus rÃ©centes de ces distributions.</Text>
+<Text id="79">Il vous faudra un serveur web: nous recommandons Apache. Nous recommandons aussi trÃšs chaudement d'installer le serveur web avant d'installer GreenstoneÂ --Â ceci facilitera grandement la rÃ©ponse aux questions posÃ©es pendant la procÃ©dure d'installation de Greenstone. Si vous souhaitez construire de nouvelles collections de bibliothÃšques numÃ©riques, il vous faudra Ã©galement installer Perl, s'il est absent de votre systÃšme. Pour savoir si Perl est installÃ©, invoquez un terminal, tapez perl -v, et voyez si le message qui apparaÃ®t prÃ©cise, entre autres choses, un numÃ©ro de version. Perl est installÃ© par dÃ©faut dans la plupart des versions de Linux. L'annexe <CrossRef target="Chapter" ref="appendix_associated_software"/> donne des prÃ©cisions sur la maniÃšre d'obtenir Apache et Perl.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_source">
+<Title>
+<Text id="80">Code source Unix</Text>
+</Title>
+<Content>
+<Text id="81">Le code source est le mÃªme pour Windows et pour Unix. Il a Ã©tÃ© compilÃ© et testÃ© sous les systÃšmes Linux, Solaris, et Macintosh OS/X; cela devrait Ãªtre immÃ©diat de le porter vers d'autres Unix.</Text>
+<Text id="82">Pour compiler le code source de Greenstone sous Unix, il vous faut:</Text>
+<BulletList>
+<Bullet>
+<Text id="83">GCC, le compilateur C++ de GNU;</Text>
+</Bullet>
+<Bullet>
+<Text id="84">GDBM, le gestionnaire de bases de donnÃ©es de GNU.</Text>
+</Bullet>
+</BulletList>
+<Text id="85">Pour faire fonctionner Greenstone, il vous faudra Ã©galement un serveur web et le langage Perl, tel qu'expliquÃ© ci-dessus dans la sectionÂ 2.2.1.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_installation">
+<Title>
+<Text id="86">Installation sous Unix</Text>
+</Title>
+<Content>
+<Text id="87">Pour installer la version d'Unix du CD-ROM, insÃ©rer le disque dans la commande, et dactylographier</Text>
+<Table class="hidden" id="table_commands">
+<Title/>
+<TableContent>
+<tr>
+<th width="151">
+<CodeLine>mount /cdrom</CodeLine>
+</th>
+<th width="246">
+<Text id="88">monte le pÃ©riphÃ©rique de cÃ©dÃ©roms (cette commande peut changer d'un systÃšme Ã  l'autre; sous OS/X, par exemple, il suffit de se rendre, par la commande cd, dans le rÃ©pertoire /Volumes et de se rendre ensuite dans le sous-rÃ©pertoire appropriÃ© pour le cÃ©dÃ©rom)</Text>
+</th>
+</tr>
+<tr>
+<th width="151">
+<CodeLine>cd /cdrom</CodeLine>
+</th>
+<th width="246">
+<Text id="89">se dÃ©place dans le rÃ©pertoire principal du cÃ©dÃ©rom</Text>
+</th>
+</tr>
+<tr>
+<th width="151">
+<CodeLine>cd Unix</CodeLine>
+</th>
+<th width="246">
+<Text id="90">se dÃ©place dans le rÃ©pertoire abritant le script d'installation pour Unix</Text>
+</th>
+</tr>
+<tr>
+<th width="151">
+<CodeLine>sh Install.sh</CodeLine>
+</th>
+<th width="246">
+<Text id="91">exÃ©cute le processus d'installation (nous prÃ©cisons explicitement le nom de l'interprÃ©teurÂ --Â shÂ --Â car de nombreuses installations interdisent l'exÃ©cution de programmes directement depuis le cÃ©dÃ©rom)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="92">Cette derniÃšre commande entame un dialogue interactif dont le but est d'obtenir de vous les informations nÃ©cessaires Ã  l'installation de Greenstone sur votre systÃšme, et qui vous donne des informations dÃ©taillÃ©es sur les rÃ©sultats des opÃ©rations effectuÃ©es.</Text>
+<Text id="93">La procÃ©dure d'installation commence par vous demander dans quel rÃ©pertoire installer Greenstone. Le premier fichier qui y sera placÃ© sera Â«uninstallÂ», programme qui nettoiera toute installation partielle, au cas oÃ¹ vous rencontreriez des problÃšmes ou mettriez fin prÃ©maturÃ©ment Ã  la procÃ©dure d'installation. Vous choisirez ensuite si vous souhaitez installer les binaires ou le code source, puis viennent des questions relatives Ã  la configuration de votre serveur web. Vous devez disposer d'un rÃ©pertoire oÃ¹ stocker des scripts CGI exÃ©cutables (communÃ©ment appelÃ© Â«cgi-binÂ» dans les systÃšmes Unix); vous pouvez en crÃ©er un nouveau ou utiliser celui qui existe dÃ©jÃ . Si vous en crÃ©ez un nouveau, il vous faudra en informer votre serveur web par le truchement de son fichier de configuration. Dans chacun de ces deux cas de figure, il vous faudra saisir l'adresse web du rÃ©pertoire CGI. Le dialogue d'installation vous guidera au travers de tous ces choix. Il est important de mettre en place des droits d'accÃšs corrects Ã  certains rÃ©pertoires, et on vous demandera les informations nÃ©cessaires. Enfin, on vous demandera le mot de passe de l'utilisateur en charge de l'administration systÃšme de Greenstone.</Text>
+<Text id="94">Par dÃ©faut, Greenstone s'installe dans le rÃ©pertoire /usr/local/gsdl si c'est l'utilisateur root qui effectue l'installation, et dans le rÃ©pertoire /gsdl dans le cas contraire, oÃ¹ Â«Â» dÃ©note le rÃ©pertoire personnel de l'utilisateur concernÃ©.</Text>
+<Text id="95">L'installation des binaires ne prend que quelques minutes, juste assez pour vous laisser le temps de rÃ©pondre aux questions appropriÃ©es. Si vous installez le code source, le script d'installation procÃ©dera Ã  sa compilation, opÃ©ration qui peut prendre de 10 minutes Ã  une heure ou plus, en fonction de la vitesse de votre processeur.</Text>
+<Text id="96">Pour dÃ©sinstaller le logiciel, tapez:</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<Text id="97">ou /usr/local/gsdl si c'est l'utilisateur root qui a installÃ© Greenstone</Text>
+<CodeLine>sh Uni nstall.sh</CodeLine>
+<Text id="98">Pendant la procÃ©dure d'installation, on vous demandera si vous souhaitez installer des collections Greenstone. La collection Greenstone Â«DemoÂ» est installÃ©e automatiquement; les autres collections du cÃ©dÃ©rom sont dÃ©crites en sectionÂ <CrossRef target="Chapter" ref="greenstone_collections"/>.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_webserver_configuration">
+<Title>
+<Text id="99">Configuration de serveur web sous Unix</Text>
+</Title>
+<Content>
+<Text id="100">Si vous disposez dÃ©jÃ  d'un serveur web, il faudra y apporter quelques modifications pour rendre votre installation de Greenstone opÃ©rationnelle. Le script d'installation dÃ©taille ces modifications. Vous aurez peut-Ãªtre besoin d'un administrateur systÃšme pour reconfigurer le serveur webÂ --Â votre administrateur systÃšme devrait comprendre les instructions fournies par le script d'installation. Pour votre confort, la sortie du script d'installation est consignÃ©e dans un fichier appelÃ© INSTALL_RECORD et situÃ© dans le rÃ©pertoire d'installation de Greenstone.</Text>
+<Text id="101">Si vous ne disposez pas dÃ©jÃ  d'un serveur web, il vous faudra en installer un. L'annexe <CrossRef target="Chapter" ref="appendix_associated_software"/> fournit des informations relatives Ã  Apache. Il vous faudra ensuite le configurer de maniÃšre appropriÃ©e. La sectionÂ <CrossRef target="Chapter" ref="setting_up_webserver"/> dÃ©taille les portions de l'installation d'un serveur web qui concernent Greenstone, et comment il faut les modifier. Tout revient Ã  ajouter une petite dizaine de lignes Ã  un fichier de configuration.</Text>
+<Text id="102">Nul besoin d'effectuer la procÃ©dure d'installation ci-dessus dÃ©taillÃ©e sous l'identifiant Â«rootÂ». Cependant, de tels privilÃšges peuvent Ãªtre nÃ©cessaires pour modifier un serveur Apache existantÂ --Â tout dÃ©pend de sa configuration. Si vous installez Apache vous-mÃªme, vous pouvez procÃ©der en tant que simple utilisateur, sans utiliser de privilÃšges rÃ©servÃ©s Ã  Â«rootÂ». Dans le cas oÃ¹ vous avez affaire Ã  un administrateur systÃšme rÃ©ticent, vous pourrez toujours contourner la difficultÃ© en installant un deuxiÃšme serveur web Apache sur votre ordinateurÂ --Â mÃªme si un tel serveur est dÃ©jÃ  installÃ©.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="how_to_find_greenstone">
+<Title>
+<Text id="103">OÃ¹ trouver Greenstone</Text>
+</Title>
+<Content>
+<Subsection id="local_library_windows_only">
+<Title>
+<Text id="104">BibliothÃšque locale (seulement pour Windows)</Text>
+</Title>
+<Content>
+<Text id="105">Si vous utilisez la bibliothÃšque locale, il suffit d'invoquer le programme Â«GreenstoneÂ» depuis le menu DÃ©marrer. Ceci dÃ©marrera automatiquement le navigateur web et chargera la page d'accueil de la bibliothÃšque numÃ©rique Greenstone, d'oÃ¹ la collection Â«DemoÂ» de Greenstone devrait Ãªtre accessible.</Text>
+</Content>
+</Subsection>
+<Subsection id="web_library_windows_and_unix">
+<Title>
+<Text id="106">BibliothÃšque Web (Windows et Unix)</Text>
+</Title>
+<Content>
+<Text id="107">Si vous utilisez la bibliothÃšque web, utilisez l'URL suivante pour entrer sur le systÃšme Greenstone, aprÃšs avoir installÃ© le logiciel et configurÃ© le serveur web:</Text>
+<Text id="108">http://localhost/gsdl/cgi-bin/library</Text>
+<Text id="109">La collection Â«DemoÂ» de Greenstone devrait Ãªtre accessible depuis cette page.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_collector">
+<Title>
+<Text id="110">Le Collector</Text>
+</Title>
+<Content>
+<Text id="111">Un lien menant vers le Collector est fourni sur la page d'accueil de la bibliothÃšque numÃ©rique.</Text>
+</Content>
+</Subsection>
+<Subsection id="administration">
+<Title>
+<Text id="112">Administration</Text>
+</Title>
+<Content>
+<Text id="113">Un lien menant vers les pages d'administration est fourni sur la page d'accueil de la bibliothÃšque numÃ©rique. L'utilisateur en charge de l'administration s'appelle Â«adminÂ», et vous avez dÃ» spÃ©cifier son mot de passe pendant le processus d'installation. L'administrateur a le droit d'ajouter de nouveaux utilisateurs et de construire des collections.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="the_greenstone_librarian_interface_(gli)">
+<Title>
+<Text id="114">l'Interface BibliothÃ©caire de Greenstone (GLI)</Text>
+</Title>
+<Content>
+<Text id="115">Greenstone "Librarian Interface" (l'Interface BibliothÃ©caire de Greenstone) (GLI) est un outil d'assistance Ã  la mise sur pied de bibliothÃšques numÃ©riques utilisant Greenstone. Il vous donne accÃšs Ã  la fonctionnalitÃ© de crÃ©ation de collection Greenstone, Ã  partir d'une interface commode "pointer et cliquer".</Text>
+<Text id="116">GLI est installÃ© automatiquement avec toutes les distributions de Greenstone. Il est placÃ© dans le sous-rÃ©pertoire "gli" du rÃ©pertoire racine de Greenstone (CProgram Filesgsdlgli, par dÃ©faut ). Il faut noter qu'il fonctionne conjointement avec Greenstone et ne le fera correctement que s'il est placÃ© dans un sous rÃ©pertoire de votre installation Greenstone. Et ce sera le cas si on a tÃ©lÃ©chargÃ© une des distributions de Greenstone.</Text>
+<Text id="117">Pour utiliser "GLI", l'ordinateur doit disposer de l'environnement "JAVA Runtime". Si tel n'est pas le cas, l'installation propose une version incluse dans le CD-ROM. Dans Unix, on doit s'assurer que PERL est installÃ© (pour Windows, Perl est dÃ©jÃ  inclus dans le logiciel Greenstone ). PriÃšre signaler Ã  greenstone@cs.waikato.ac.nz tout problÃšme intervenu dans l'exÃ©cution ou l'utilisation du "Librarian Interface" (Interface BibliothÃ©caire).</Text>
+<Subsection id="running_under_windows">
+<Title>
+<Text id="118">ExÃ©cution sous Windows</Text>
+</Title>
+<Content>
+<Text id="119">Pour exÃ©cuter "GLI" sous Windows, parcourir le rÃ©pertoire gli dans votre installation Greenstone (par exemple en utilisant l'explorateur de Windows), et double-cliquer sur le fichier appelÃ© gli.bat. Ce fichier vÃ©rifie que Greenstone, l'environnement Java Runtime et Perl sont tous installÃ©s, et dÃ©marre "Greenstone Librarian Interface" (l'Interface BibliothÃ©caire de Greenstone).</Text>
+</Content>
+</Subsection>
+<Subsection id="running_under_unix">
+<Title>
+<Text id="120">ExÃ©cution sous Unix</Text>
+</Title>
+<Content>
+<Text id="121">Pour exÃ©cuter GLI sous Unix, passer au rÃ©pertoire gli de votre installation Greenstone, et ensuite exÃ©cuter le script gli.sh. Ce script vÃ©rifie que Greenstone, l'environnement Java Runtime et Perl sont tous installÃ©s et sont sur votre chemin de recherche, et dÃ©marre "Greenstone Librarian Interface" (l'Interface BibliothÃ©caire de Greenstone).</Text>
+</Content>
+</Subsection>
+<Subsection id="getting_help">
+<Title>
+<Text id="122">Obtenir de l'aide</Text>
+</Title>
+<Content>
+<Text id="123">"Greenstone Librarian Interface" (l'Interface BibliothÃ©caire de Greenstone) a en ligne des fonctions d'aide Ã©tendues. On peut obtenir de l'aide en cliquant sur le bouton Help situÃ© en haut Ã  droite de l'Ã©cran. Ceci ouvre le texte sur une section qui traite de ce qu'on est en train de faire, d'un des panneaux utilisÃ©s. On peut parcourir le texte d'aide et s'informer sur ce qu'on cherche. Utilisez-le.</Text>
+</Content>
+</Subsection>
+<Subsection id="compiling_gli">
+<Title>
+<Text id="124">Compiler le l'Interface BibliothÃ©caire de Greenstone</Text>
+</Title>
+<Content>
+<Text id="125">Si on a tÃ©lÃ©chargÃ© une distribution source de Greenstone, le code source Java de "Greenstone Librarian Interface" (l'Interface BibliothÃ©caire de Greenstone) est mis Ã  disposition. Pour le compiler, l'ordinateur doit avoir un kit de dÃ©veloppement Java. L'appendice <CrossRef target="Chapter" ref="appendix_associated_software"/> fournit l'information sur la maniÃšre de l'obtenir. Pour compiler le code source, exÃ©cuter les fichiers makegli.bat (Windows) ou makegli.sh (Unix). Une fois compilÃ©, vous pouvez exÃ©cuter GLI comme dÃ©crit ci-dessus.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="testing_and_troubleshooting">
+<Title>
+<Text id="126">Tests et diagnostics</Text>
+</Title>
+<Content>
+<Text id="127">Pour tester Greenstone, pointez votre navigateur web vers la page d'accueil de Greenstone afin d'explorer la collection Â«DemoÂ» ou toute autre collection installÃ©e. Pas d'inquiÃ©tudeÂ --Â vous ne pouvez rien casser. Cliquez partout et sans crainte: la plupart des images qui apparaÃ®tront sur votre Ã©cran rÃ©agissent aux clics. Si vous maintenez le pointeur de la souris au-dessus d'une image, la plupart des navigateurs afficheront un message qui vous expliquera ce qui se passera si vous cliquez. Faites l'expÃ©rience! Choisissez des mots communs tels que Â«leÂ» (the) ou Â«etÂ» (and) en tant que critÃšres de rechercheÂ --Â voilÃ  qui devrait fournir des rÃ©ponses, et vous ne pourrez rien casser. Pour plus d'informations Ã  ce sujet, consultez le Guide de l'utilisateur de la bibliothÃšque numÃ©rique Greenstone.</Text>
+<Subsection id="troubleshooting">
+<Title>
+<Text id="128">Diagnostics et remÃšdes</Text>
+</Title>
+<Content>
+<Table id="table_troubleshooting">
+<Title/>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="129"><b>ProblÃšme</b></Text>
+</th>
+<th width="246">
+<Text id="130"><b>Essayez ceci</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="131">BIBLIOTHÃQUE LOCALE (SEULEMENT POUR WINDOWS)</Text>
+</th>
+<th width="151">
+<Text id="132">Quand je dÃ©marre Greenstone, mon ordinateur me demande de me connecter Ã  mon fournisseur dâaccÃšs Internet par tÃ©lÃ©phone.</Text>
+</th>
+<th width="246">
+<Text id="133">Cliquez sur le bouton<i>Annuler</i>de la boÃ®te de dialogue. Ceci rÃ©sout gÃ©nÃ©ralement ce problÃšme.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="134">Quand je dÃ©marre Greenstone, mon ordinateur me demande<i>encore</i>de me connecter Ã  mon fournisseur dâaccÃšs Internet par tÃ©lÃ©phone.</Text>
+</th>
+<th width="246">
+<Text id="135">Choisissez la Â«version restreinteÂ» lorsque vous dÃ©marrez Greenstone. Cette version ne fonctionne quâavec Netscape.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="136">Quand je pointe mon navigateur vers la bibliothÃšque numÃ©rique, il ne trouve pas la page dâaccueil.</Text>
+</th>
+<th width="246">
+<Text id="137">VÃ©rifiez vos rÃ©glages de mandataire (<i>proxy</i>) Internet et dÃ©sactivez ces derniers (utilisez<i>Ãditer les prÃ©fÃ©rences</i>pour Netscape ou<i>Options Internet</i>pour Internet Explorer).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="138">Le Collector me semble fonctionner trÃšs lentement!</Text>
+</th>
+<th width="246">
+<Text id="139">Utilisez-vous Netscape sous Windows 2000 ? Si câest le cas, essayez plutÃŽt dâemployer Internet Explorer â sousWindows 2000 (et seulement sous ce systÃšme), il semble y avoir une incompatibilitÃ© avec Netscape.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="142">BIBLIOTHÃQUE WEB (WINDOWS ET UNIX)</Text>
+</th>
+<th width="151">
+<Text id="143">Quand je dÃ©marre Apache, il termine immÃ©diatement.</Text>
+</th>
+<th width="246">
+<Text id="144">Ajoutez une directive ServerName localhost dans le fichier de configuration dâApache (voyez Ã  ce sujet la section <CrossRef target="Section" ref="apache_web_server"/>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="145">Quand je pointe mon navigateur vers la bibliothÃšque numÃ©rique, il affiche nâimporte quoi â un fichier binaire.</Text>
+</th>
+<th width="246">
+<Text id="146">VÃ©rifiez la directive ScriptAlias dans le fichier de configuration dâApache, et assurez-vous quâelle prÃ©cÃšde la directive Alias (voyez Ã  ce sujet la section 4.1).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="147">Jâobtiens bien la page dâaccueil de Greenstone de la figureÂ <CrossRef target="Figure" ref="your_greenstone_home_page"/>, mais lâicone de la collection Â«DemoÂ» nâapparaÃ®t pas.</Text>
+</th>
+<th width="246">
+<Text id="148">ExÃ©cutez le programme library, situÃ© dans le rÃ©pertoire cgi-bin, depuis lâinterprÃ©teur de commandes de DOS ou du shell, afin dâobtenir des informations de dÃ©bogage qui vous aideront Ã  mieux localiser le problÃšme.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="149">LES DEUX VERSIONS</Text>
+</th>
+<th width="151">
+<Text id="150">Quand je pointe mon navigateur vers la bibliothÃšque numÃ©rique, il ne trouve pas la page dâaccueil.</Text>
+</th>
+<th width="246">
+<Text id="151">Essayez dâutiliser la chaÃ®ne 127.0.0.1 en lieu et place de localhost. Ce numÃ©ro IP rÃ©servÃ© correspond Ã  une Â«boucle de retourÂ» (<i>loopback</i>) vers votre ordinateur local.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<br/>
+<Text id="152">Mon navigateur se plaint de ne pas trouver le fichier main.cfg.</Text>
+</th>
+<th width="246">
+<Text id="153">VÃ©rifiez que les fichiers de Greenstone existent bien et sont lisibles par tous. Si vous utilisez la bibliothÃšque web, essayez dâexÃ©cuter le programme library depuis lâinterprÃ©teur de commandes. Sâil sâexÃ©cute sans heurts, le problÃšme est Ã  chercher du cÃŽtÃ© des permissions de fichiers (voir Ã  ce sujet la section <CrossRef target="Section" ref="file_permissions"/>). Dans le cas contraire, la variable GSDLHOME a probablement reÃ§u une valeur incorrecte dans le fichier de configuration gsdlsite.cfg (voir Ã  ce sujet la section <CrossRef target="Section" ref="gsdlsite_configuration_file"/>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="154">Jâai des soucis avec le Collector.</Text>
+</th>
+<th width="246">
+<Text id="155">Lisez le Guide de lâutilisateur de la bibliothÃšque numÃ©rique Greenstone, section <CrossRef external="User" lang="fr" target="Chapter" ref="making_greenstone_collections"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="156">Jâai ajoutÃ© un nouvel utilisateur mais il ne semble pas pouvoir se connecter.</Text>
+</th>
+<th width="246">
+<Text id="157">VÃ©rifier que le rÃ©pertoire C:\Program Files\gsdl\etc ainsi que tous les fichiers quâil contient sont inscriptibles par tous (voir Ã  ce sujet la section <CrossRef target="Section" ref="file_permissions"/>).</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="learn_more">
+<Title>
+<Text id="158">Pour en savoir plus</Text>
+</Title>
+<Content>
+<Text id="159">Pour en savoir plus sur les entrailles de votre installation de Greenstone, consultez le Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone. Il comprend, entre autres choses, les dÃ©tails de la structure arborescente de rÃ©pertoires qui a Ã©tÃ© mise en place, ainsi que des informations sur la maniÃšre de configurer votre site Greenstone.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="greenstone_collections">
+<Title>
+<Text id="160">Les collections de Greenstone</Text>
+</Title>
+<Content>
+<Text id="161">Plusieurs collections de dÃ©monstration de Greenstone sont inclus dans le CD-ROM. Si vous avez un accÃšs web, beaucoup d'autres peuvent Ãªtre tÃ©lÃ©chargÃ©s sous forme finie ou non, Ã  partir du site web de la "New Zealand Digital Library Project (nzdl.org)".</Text>
+<Text id="162">La collection de dÃ©monstration de Greenstone est un petit composant de "Humanity Development Library (HDL)", une collection bien entretenue. Elle illustre le fait que des possibilitÃ©s de navigation relativement riches peuvent Ãªtre fournies (aussi longtemps qu'une mÃ©ta-donnÃ©e appropriÃ©e est disponible). Elle est automatiquement incluse Ã  l'installation du logiciel.</Text>
+<Text id="163">Greenstone vient aussi avec quelques exemples de collections bien documentÃ©es dont la page "about" dÃ©crit la maniÃšre avec laquelle ils ont Ã©tÃ© Ã©laborÃ©s. Ils dÃ©montrent diverses possibilitÃ©s de Greenstone. La boÃ®te de dialogue "install" vous proposera de les inclure ou non dans l'installation de Greenstone; l'espace disque approximatif nÃ©cessaire Ã  chaque collection est indiquÃ© ci-dessous.</Text>
+<Table class="hidden" id="table_collections">
+<Title/>
+<TableContent>
+<tr>
+<th width="60">
+<Text id="164"><i>demo</i></Text>
+</th>
+<th width="182">
+<Text id="165">DÃ©monstration de Greenstone (7 MO)</Text>
+</th>
+<th width="294">
+<Text id="166">Une petite composante de HDL. Si vous clonez cette collection, la totalitÃ© des fonctions nâapparaÃ®tra que si vos nouveaux fichiers fournissent lâinformation mÃ©ta-donnÃ©e appropriÃ©e.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="167"><i>dls-e</i></Text>
+</th>
+<th width="182">
+<Text id="168">Sous-ensemble de la collection BibliothÃšque de DÃ©veloppement (150 MO)</Text>
+</th>
+<th width="294">
+<Text id="169">A lâinstar de "Greenstone Demo", câest une composante de HDL, mais plus grande. Elle contient 250 livres de publications, rapports et magazines dans divers domaines du dÃ©veloppement humain (la totalitÃ© de HDL contient 1230 publications). Elle a la mÃªme structure que "Greenstone Demo". Elle est assez complexe et si on est tout juste dÃ©butant, il serait peut-Ãªtre prÃ©fÃ©rable de consulter dâabord dâautres collections (Exemple : dÃ©monstration MS Word et PDF, les archives Greenstone, ou la collection "simple image").</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="170"><i>wrdpdf-e</i></Text>
+</th>
+<th width="182">
+<Text id="171">DÃ©monstration MSWord et PDF (4 MO)</Text>
+</th>
+<th width="294">
+<Text id="172">Elle contient des documents en PDF, MS Word, RTF, et des formats Postscript, qui attestent de la possibilitÃ© de former des collections Ã  partir de documents de diffÃ©rents formats. Le fichier de configuration de la collection est trÃšs simple.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="173"><i>gsarch-e</i></Text>
+</th>
+<th width="182">
+<Text id="174">Collection des Archives de Greenstone (5 MO)</Text>
+</th>
+<th width="294">
+<Text id="175">Une collection de messages e-mail Ã  partir des archives de listes dâadresses de Greenstone, elle utilise le plugin e-mail qui analyse les fichiers en formats e-mail. Le fichier de configuration de la collection est trÃšs simple.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="176"><i>cltbib-e</i></Text>
+</th>
+<th width="182">
+<Text id="177">Collection bibliographie (7 MO)</Text>
+</th>
+<th width="294">
+<Text id="178">Avec environ 4000 entrÃ©es bibliographiques, cette collection incorpore une interface de recherche basÃ©e sur un formulaire qui permet une recherche par champ. Elle est assez complexe.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="179"><i>cltext-e</i></Text>
+</th>
+<th width="182">
+<Text id="180">SupplÃ©ment bibliographie (1 MO)</Text>
+</th>
+<th width="294">
+<Text id="181">Cette petite collection de 10 entrÃ©es bibliographiques illustre la fonction "supercollection" qui recherche plusieurs collections Ã  la fois. Elle fonctionne avec la collection bibliographie et son fichier de configuration est presque le mÃªme.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="182"><i>MARC-e</i></Text>
+</th>
+<th width="182">
+<Text id="183">Exemple MARC (1 MO)</Text>
+</th>
+<th width="294">
+<Text id="184">BasÃ© sur quelques enregistrements Marc de la Librairie du CongrÃšs, câest est une collection simple (et ne permet pas une recherche basÃ©e sur formulaire).</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="185"><i>oai-e</i></Text>
+</th>
+<th width="182">
+<Text id="186">DÃ©mo OAI (18 MO)</Text>
+</th>
+<th width="294">
+<Text id="187">En utilisant la caractÃ©ristique "Open Archive Protocol" et "Import Form", elle extrait des mÃ©ta-donnÃ©es dâune archive et confectionne une collection Ã  partir des enregistrements. Dans ce cas, ce sont des images ; ainsi, aussi bien les plugins OAI que les images sont utilisÃ©s.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="188"><i>image-e</i></Text>
+</th>
+<th width="182">
+<Text id="189">Collection dâimages simple (1 MO)</Text>
+</th>
+<th width="294">
+<Text id="190">Cette collection dâimages simples standard ne contient aucun texte et aucune mÃ©tadonnÃ©e explicite, ce qui la rend plutÃŽt irrÃ©aliste. Le fichier de configuration est tout aussi simple et accessible.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="191"><i>authen-e</i></Text>
+</th>
+<th width="182">
+<Text id="192">DÃ©monstration de formatage et dâauthentification (8 MO)</Text>
+</th>
+<th width="294">
+<Text id="193">Avec le mÃªme matÃ©riel que la collection de dÃ©monstration Greenstone originale, elle affiche deux caractÃ©ristiques indÃ©pendantes : le formatage de document non-standard et lâaccÃšs contrÃŽlÃ© aux documents par le biais dâune authentification de lâutilisateur.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="194"><i>garish</i></Text>
+</th>
+<th width="182">
+<Text id="195">Version Garish de la collection de dÃ©monstration (8 MO)</Text>
+</th>
+<th width="294">
+<Text id="196">Cette collection contient aussi le mÃªme matÃ©riel que la collection de dÃ©monstration Greenstone. Sa prÃ©sentation a Ã©tÃ© altÃ©rÃ©e pour montrer comment les pages gÃ©nÃ©rÃ©es peuvent Ãªtre affichÃ©es diffÃ©remment. Elle dÃ©pend dâun fichier macro non standard qui est fourni avec Greenstone.</Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="197"><i>isis-e</i></Text>
+</th>
+<th width="182">
+<Text id="198">Exemple CDS/ISIS (1 MO)</Text>
+</th>
+<th width="294">
+<Text id="199">Cette collection est construite a partir des donnÃ©es CDS/ISIS de quelques 150 entrÃ©es bibliographiques. Elle utilize le plugin ISISPlug, qui lit les fichiers standards ISIS .mst et .fdt et les convertit en metadonnÃ©es de Greenstone.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<Chapter id="setting_up_webserver">
+<Title>
+<Text id="200">Configuration du serveur web</Text>
+</Title>
+<Content>
+<Text id="201">Nous dÃ©crivons dans cette section la maniÃšre de configurer votre serveur web pour qu'il fonctionne avec Greenstone. Toutes ces prÃ©cisions sont inutiles Ã  qui utilise la bibliothÃšque locale sous Windows, car le logiciel fonctionne alors Â«tel queÂ», sans nÃ©cessiter un serveur web.</Text>
+<Text id="202">Nous traiterons Ã  la fois le cas du serveur web Apache, qui est librement disponible pour Windows comme pour Unix (reportez-vous Ã  l'annexe <CrossRef target="Chapter" ref="appendix_associated_software"/> pour plus de dÃ©tails Ã  ce sujet), et des serveurs web Â«Personal Web Server (PWS)Â» et Â«Internet Information Services (IIS)Â» de Microsoft. PWS est le serveur web standard fourni par Microsoft pour Windows 95/98; IIS est celui des versions 2000 et XP de Windows. Windows NT peut utiliser chacun de ces deux serveurs. La description concernant Apache s'applique aussi Ã  la bibliothÃšque web, versions Windows comme Unix (bien que nous utilisions les terminologies et chemins d'accÃšs propres Ã  Windows). La section PWS/IIS ne s'applique qu'Ã  la bibliothÃšque web sous Windows.</Text>
+<Text id="203">AprÃšs avoir installÃ© le serveur web, il faut installer Greenstone. Nous supposerons que lors de la procÃ©dure d'installation, vous avez choisi l'action par dÃ©faut Ã  chaque Ã©tape, en cliquant sur le bouton Suivant. Au final, vous disposez d'un rÃ©pertoire CProgram Filesgsdl contenant le binaire de la bibliothÃšque web, ainsi que quelques fichiers complÃ©mentaires.</Text>
+<Text id="204">Tous les serveurs web utilisent l'URL spÃ©ciale Â«localhostÂ» pour reprÃ©senter l'ordinateur sur lequel le serveur fonctionne. C'est pourquoi, lors de l'installation d'un serveur web, vous pourrez accÃ©der Ã  vos documents HTML en tapant l'URLhttp://localhostdans un navigateur. Si votre ordinateur possÃšde un nom dans le DNS (ou systÃšme de noms), c'est ce nom qui sera utilisÃ© en lieu et place de Â«localhostÂ» pour identifier votre ordinateur depuis des sites distants. C'est ainsi que sur l'ordinateur de la bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande, les URLhttp://nzdl.orgethttp://localhostsont Ã©quivalentes. Si vous tapezhttp://nzdl.orgsur votre ordinateur, vous accÃ©derez au serveur web de la bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande, alors que si vous tapezhttp://localhostvous accÃ©derez au serveur web de votre propre ordinateur.</Text>
+<Section id="apache_web_server">
+<Title>
+<Text id="205">Le serveur web Apache</Text>
+</Title>
+<Content>
+<Text id="206">Le serveur web Apache est gÃ©nÃ©ralement installÃ© dans le rÃ©pertoire CProgram FilesApache GroupApache, et il est configurÃ© de sorte que son rÃ©pertoire cgi-bin soit dans le sous-rÃ©pertoire cgi-bin et que le rÃ©pertoire racine des documents corresponde au sous-rÃ©pertoire htdocs. On peut modifier sa configuration en Ã©ditant le fichier de configuration situÃ© sous CProgram FilesApache GroupApacheconfhttpd.conf. Ce fichier Ã©tant un fichier texte, il est trÃšs facile Ã  lire et de voir comment les choses sont configurÃ©es.</Text>
+<Text id="207">En fonction de la configuration des logiciels de communication en rÃ©seau de votre ordinateur, vous devrez peut-Ãªtre ajouter la ligne suivante au fichier de configuration httpd.conf de votre serveur Apache:</Text>
+<CodeLine>ServerName localhost</CodeLine>
+<Text id="208">En l'absence de cette ligne, le systÃšme tentera de dÃ©terminer le nom de votre serveur. Cependant, des bogues prÃ©sents dans certaines versions de Windows font Ã©chouer cette opÃ©ration. Dans un tel cas de figure, Apache sort immÃ©diatement lorsqu'on le dÃ©marre. Il affiche bien un message d'erreur, mais ce dernier est tout de suite effacÃ© et vous n'aurez probablement pas le temps de le lire.</Text>
+<Subsection id="setting_up_cgi-bin_directory">
+<Title>
+<Text id="209">Mettre en place le rÃ©pertoire cgi-bin de Greenstone</Text>
+</Title>
+<Content>
+<Text id="210">Le rÃ©pertoire cgi-bin est celui oÃ¹ le serveur web traite les documents en tant que programmes Ã  exÃ©cuter. On utilise la directive ScriptAlias d'Apache pour crÃ©er un rÃ©pertoire cgi-bin. Vous remarquerez que cette directive permet de transformer n'importe quel rÃ©pertoire en rÃ©pertoire d'exÃ©cutables CGIÂ --Â nul besoin pour le rÃ©pertoire de s'appeler Â«cgi-binÂ»! De mÃªme, un rÃ©pertoire appelÃ© Â«cgi-binÂ» ne joue aucun rÃŽle particulier en l'absence de directive ScriptAlias le concernant.</Text>
+<Text id="211">Une fois installÃ©, Apache possÃšde le rÃ©pertoire cgi-bin suivant: CProgram FilesApache GroupApachecgi-bin. Ceci signifie que si on lui fournit l'URLhttp://localhost/cgi-bin/bonjour, le serveur web tentera d'exÃ©cuter un fichier bonjour situÃ© dans le rÃ©pertoire prÃ©cÃ©dent.</Text>
+<Text id="212">Greenstone comprend un programme, appelÃ© Â«library.exeÂ», qui doit Ãªtre exÃ©cutÃ© par le serveur web: il lit alors un fichier appelÃ© le Â«fichier de configuration de site de GreenstoneÂ», ou Â«gsdlsite.cfgÂ», qui doit se trouver dans le mÃªme rÃ©pertoire.</Text>
+<Text id="213">La meilleure maniÃšre d'obtenir ce rÃ©sultat est d'utiliser la directive ScriptAlias d'Apache pour crÃ©er un nouveau rÃ©pertoire cgi-bin. Voici l'extrait du fichier de configuration d'Apache, httpd.conf, qui ajoute le rÃ©pertoire CProgram Filesgsdlcgi-bin Ã  la liste des rÃ©pertoires de type cgi-bin:</Text>
+<CodeLine>ScriptAlias /gsdl/cgi-bin/ "C:/Program Files/gsdl/cgi-bin/"</CodeLine>
+<CodeLine>&lt;Directory C:/Program Files/gsdl/cgi-bin&gt;</CodeLine>
+<CodeLine>  Options None</CodeLine>
+<CodeLine>  AllowOverride None</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="214">Vous remarquerez que les fichiers de configuration d'Apache utilisent des barres de division ((forward) slash) en lieu et place des barres obliques inversÃ©es (backslash), communes sous Windows.</Text>
+<Text id="215">Ceci signifie que toutes les URL de la formehttp://localhost/gsdl/cgi-bin...seront recherchÃ©es dans le rÃ©pertoire de chemin CProgram Filesgsdlcgi-bin et exÃ©cutÃ©es par le serveur web. Par exemple, si on lui demande l'URLhttp://localhost/gsdl/cgi-bin/bonjour, le serveur web tentera de lire CProgram Filesgsdlcgi-binbonjour, et de l'exÃ©cuter. Mais l'URLhttp://localhost/cgi-bin/bonjourcontinuera comme avant Ã  examiner le rÃ©pertoire cgi-bin d'Apache Ã  la recherche deCProgram FilesApache GroupApachecgi-binbonjour, pour exÃ©cuter ce fichier.</Text>
+</Content>
+</Subsection>
+<Subsection id="document_root_directory">
+<Title>
+<Text id="216">Le rÃ©pertoire racine des documents</Text>
+</Title>
+<Content>
+<Text id="217">Le rÃ©pertoire racine des documents est la racine de la structure arborescente des rÃ©pertoires de votre serveur web. Lors de son installation, Apache dispose comme racine de documents du rÃ©pertoire de chemin CProgram FilesApache GroupApachehtdocs. Cela signifie que si on lui demande l'URLhttp://localhost/bonjour.html, le serveur web tentera de lire un fichier appelÃ© bonjour.html dans le rÃ©pertoire ci-dessus.</Text>
+<Text id="218">Greenstone contient plusieurs fichiers qu'il faut que le serveur web lise. La maniÃšre la plus simple de procÃ©der est d'utiliser la directive Alias, qui ressemble Ã  ScriptAlias Ã  ceci prÃšs qu'elle s'applique aux pages web normales, et pas aux scripts CGI. InsÃ©rez les lignes suivantes dans le fichier de configuration de votre Apache, aprÃšs la directive ScriptAlias, afin d'ajouter le rÃ©pertoire CProgram Filesgsdl comme lieu de recherche de documents.</Text>
+<CodeLine>Alias /gsdl/ "C:/Program Files/gsdl/"</CodeLine>
+<CodeLine>&lt;Directory C:/Program Files/gsdl&gt;</CodeLine>
+<CodeLine> Options Indexes MultiViews FollowSymLinks</CodeLine>
+<CodeLine> AllowOverride None</CodeLine>
+<CodeLine> Order allow,deny</CodeLine>
+<CodeLine> Allow from all</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="219">Ceci signifie que toute URL correspondant au premier argument de la directive Alias (gsdl) est recherchÃ©e sous la forme de fichiers situÃ©s dans le rÃ©pertoire donnÃ© en deuxiÃšme argument. En d'autres termes, une URL de la formehttp://localhost/gsdl/...aura pour effet la recherche de fichiers dans le rÃ©pertoire CProgram Filesgsdl. Si par exemple on fournit au serveur web l'URLhttp://localhost/gsdl/bonjour.html, il tentera de rechercher le fichier CProgram Filesgsdlbonjour.html. Mais l'URLhttp://localhost/bonjour.htmlcontinuera comme avant Ã  examiner le rÃ©pertoire htdocs normal d'Apache Ã  la recherche du fichier CProgram FilesApache GroupApachehtdocsbonjour.html.</Text>
+<Text id="220">Assurez-vous d'ajouter la directive Alias aprÃšs la directive ScriptAlias. DÃ©finir auprÃšs d'Apache l'alias/gsdlavant l'alias/gsdl/cgi-binreconnaÃ®trait l'URL/gsdl/cgi-bin/libraryavec la directive Alias et non pas avec la directive ScriptAlias, et cette URL serait interprÃ©tÃ©e comme une requÃªte de document au lieu d'une requÃªte du rÃ©sultat de l'exÃ©cution d'un programme. On obtiendrait alors l'Â«affichageÂ» du fichier binaire du programme en tant que page web dans le navigateur web, sans jamais l'avoir exÃ©cutÃ©.</Text>
+</Content>
+</Subsection>
+<Subsection id="security">
+<Title>
+<Text id="221">SÃ©curitÃ©</Text>
+</Title>
+<Content>
+<Text id="222">Gardez Ã  l'esprit le fait que si la version Â«bibliothÃšque webÂ» de Greenstone est configurÃ©e en suivant les instructions donnÃ©es ci-dessus, n'importe qui aura le droit de tÃ©lÃ©charger tout fichier situÃ© dans la structure arborescente de rÃ©pertoire dÃ©marrant sous gsdl. Ceci comprend les fichiers d'indexation, les documents source de toute collection que vous construirez, la base de donnÃ©es utilisateur, les journaux d'utilisation, etc.</Text>
+<Text id="223">Si vous souhaitez Ã©viter cela, vous pouvez facilement resserrer la configuration de votre serveur web afin d'en augmenter la sÃ©curitÃ©. Dans le cas du serveur web Apache, remplacez les lignes donnÃ©es dans la section prÃ©cÃ©dente par les lignes suivantes dans le fichier de configuration:</Text>
+<CodeLine>Alias /gsdl/ "C:/Program Files/gsdl/"</CodeLine>
+<CodeLine>&lt;Directory "C:/Program Files/gsdl"&gt;</CodeLine>
+<CodeLine>   Order allow,deny</CodeLine>
+<CodeLine>   Deny from all</CodeLine>
+<CodeLine>   &lt;FilesMatch</CodeLine>
+<CodeLine>"\.(gif|jpe?g|png|css|mov|mpeg|ps|pdf|doc|rtf|jar|class)$"&gt;</CodeLine>
+<CodeLine>         Order allow,deny</CodeLine>
+<CodeLine>         Allow from all</CodeLine>
+<CodeLine>   &lt;/FilesMatch&gt;</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="224">Ceci aura pour effet de n'autoriser en tÃ©lÃ©chargement que les fichiers dont le nom vÃ©rifie l'expression rationnelle donnÃ©e dans la ligne FilesMatch (c'est-Ã -dire, dans le cas prÃ©sent, de n'autoriser qu'une liste fixÃ©e d'extensions de noms de fichiers).</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="pws_and_iis_webservers">
+<Title>
+<Text id="225">Les serveurs web PWS et IIS</Text>
+</Title>
+<Content>
+<Text id="226">Bien qu'aucun de ces deux serveurs ne soit installÃ© par dÃ©faut dans les systÃšmes Windows actuels, on peut facilement les installer Ã  l'aide du panneau de contrÃŽle Ajouter/Supprimer des programmes. Si vous ne les trouvez pas sur le cÃ©dÃ©rom de votre distribution de Windows, il vous faudra les tÃ©lÃ©charger depuis le site web de Microsoft (www.microsoft.com).</Text>
+<Text id="227">La procÃ©dure de mise en place de Greenstone est la mÃªme pour PWS et pour IIS. Invoquez le gestionnaire personnel de web et effectuez les actions suivantes:</Text>
+
+<NumberedList>
+<NumberedItem>
+<Text id="228">SÃ©lectionnez AvancÃ© pour obtenir l'Ã©cran d'Options AvancÃ©es.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="229">SÃ©lectionnez Accueil et cliquez sur Ajouter. Remplissez les champs comme suit:</Text>
+<Text id="230">Champ<i>RÃ©pertoire</i>:<i>C:\Program Files\gsdl</i></Text>
+<Text id="231">Champ<i>Alias</i>:<i>gsdl</i></Text>
+<Text id="232">Permissions dâaccÃšs:<i>Lecture</i></Text>
+<Text id="233">Permissions dâapplication:<i>Aucune</i></Text>
+<Text id="234">Cliquez sur OK.</Text>
+<Text id="235">VoilÃ  qui rendra les fichiers de Greenstone accessibles au serveur web.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="236">De retour dans l'Ã©cran d'Options avancÃ©es, sÃ©lectionnez gsdl et cliquez sur Ajouter. Remplissez les champs comme suit:</Text>
+<Text id="237">Champ<i>RÃ©pertoire</i>:<i>C:\Program Files\gsdl\cgi-bin</i></Text>
+<Text id="238">Champ<i>Alias</i>:<i>cgi-bin</i></Text>
+<Text id="239">Permissions dâaccÃšs:<i>Aucune</i></Text>
+<Text id="240">Permissions dâapplication:<i>ExÃ©cution</i></Text>
+<Text id="241">Cliquez sur OK.</Text>
+<Text id="242">VoilÃ  qui rendra le programme library.exe de Greenstone exÃ©cutable par le serveur web.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="243">Rendez-vous Ã  l'URLhttp://localhost/cgi-bin/library.exe</Text>
+<Text id="244">Remarque: avec les serveurs PWS et IIS, il vous faut prÃ©ciser l'extension de fichier .exe.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="configuring_your_site">
+<Title>
+<Text id="245">Configurer son site</Text>
+</Title>
+<Content>
+<Text id="246">Pour que Greenstone puisse fonctionner correctement, il faut mettre en place les droits d'accÃšs Ã  certains fichiers. On trouve aussi un fichier de configuration associÃ© Ã  chaque site Greenstone. La procÃ©dure d'installation crÃ©e un fichier de configuration gÃ©nÃ©rique qui repose sur les choix effectuÃ©s durant l'installation, mais son contenu peut Ãªtre adaptÃ© Ã  diffÃ©rentes situations. La prÃ©sente section dÃ©taille ces deux questions.</Text>
+<Section id="file_permissions">
+<Title>
+<Text id="247">Droits d'accÃšs aux fichiers</Text>
+</Title>
+<Content>
+<Text id="248">La prÃ©sente section ne concerne par les utilisateurs de Windows 95/98, car leurs systÃšmes d'exploitation n'identifient pas les propriÃ©taires des fichiers.</Text>
+<Text id="249">Sous Windows NT et 2000 ainsi que sous les systÃšmes Unix, les scripts CGI ne sont pas exÃ©cutÃ©s avec des droits d'utilisateurs normaux, car il n'est pas possible d'identifier les utilisateurs sur le web. Ils sont plutÃŽt exÃ©cutÃ©s au nom de l'utilisateur qui a dÃ©marrÃ© le serveur web (sur les systÃšmes de type Windows), ou au nom d'un utilisateur particulier (souvent appelÃ© nobody sur les systÃšmes Unix). C'est pourquoi tous les fichiers et rÃ©pertoires contenus dans l'arborescence CProgram Filesgsdl doivent Ãªtre lisibles par tous (ou en tout cas lisibles par l'utilisateur des scripts CGI, qui peut Ãªtre nobody). Pour tester la bonne mise en place des permissions sur les fichiers, exÃ©cutez le programme library.exe depuis l'interprÃ©teur de commandes. Si les fichiers se trouvent aux bons endroits mais que les permissions sont incorrectes, il fonctionnera correctement depuis l'interprÃ©teur de commandes. Cette situation est Ã  comparer Ã  l'exÃ©cution depuis un navigateur web, oÃ¹ il est alors exÃ©cutÃ© avec les droits de l'utilisateur nobody, situation qui devrait Ã©chouer en cas de droits incorrects. Un autre test consiste Ã  l'exÃ©cuter au nom d'un autre utilisateur aprÃšs s'Ãªtre connectÃ© en tant que tel, pour vÃ©rifier si les droits d'accÃšs aux fichiers sont spÃ©cifiques au compte utilisateur original.</Text>
+<Text id="250">Pour fonctionner depuis un navigateur web, tous les rÃ©pertoires de Greenstone doivent Ãªtre lisibles par tous. Le rÃ©pertoire CProgram Filesgsdletc et son contenu doivent de mÃªme Ãªtre inscriptibles par tous. Il s'agit du rÃ©pertoire oÃ¹ le programme library inscrira les journaux d'utilisation, d'erreur et d'initialisation, ainsi que diverses bases de donnÃ©es utilisateur. Si vous Ãªtes rÃ©ticent Ã  rendre ce rÃ©pertoire inscriptible par tous, mettez en place des permissions de sorte que seuls les fichiers errout.txt, initout.txt, key.db, users.db, history.db, et usage.txt soient inscriptibles par l'utilisateur CGI.</Text>
+<Text id="251">Si les droits d'accÃšs sous le rÃ©pertoire CProgram Filesgsdletc sont incorrects, vous remarquerez peut-Ãªtre que l'authentification des utilisateurs et la recherche dans l'historique ne fonctionneront pas, ainsi que l'absence de gÃ©nÃ©ration du journal d'utilisation (usage.txt).</Text>
+</Content>
+</Section>
+<Section id="gsdlsite_configuration_file">
+<Title>
+<Text id="252">Le fichier de configuration gsdlsite.cfg</Text>
+</Title>
+<Content>
+<Text id="253">La procÃ©dure d'installation crÃ©e un fichier de configuration de Greenstone gÃ©nÃ©rique qui repose sur les choix effectuÃ©s durant l'installation. Dans le cas de notre installation c'est CProgram Filesgsdlcgi-bingsdlsite.cfg, dont voici le contenu:</Text>
+<CodeLine># Site configuration file for Greenstone.</CodeLine>
+<CodeLine># Lines begining with</CodeLine>
+<CodeLine># are comments.</CodeLine>
+<CodeLine># This file should be placed in the same directory as your library</CodeLine>
+<CodeLine># executable file. it should be edited to suit your site.</CodeLine>
+<CodeLine># points to the GSDLHOME directory</CodeLine>
+<CodeLine>gsdlhome âC:/Program Files/gsdl â</CodeLine>
+<CodeLine># this is the http address of GSDLHOME</CodeLine>
+<CodeLine># if your webservers DocumentRoot is set to $GSDLHOME</CodeLine>
+<CodeLine># then httpprefix can be commented out</CodeLine>
+<CodeLine>httpprefix /gsdl</CodeLine>
+<CodeLine># this is the http address of the directory which</CodeLine>
+<CodeLine># contains the images for the interface.</CodeLine>
+<CodeLine>httpimg /gsdl/images</CodeLine>
+<CodeLine># should contain the http address of this cgi script. This</CodeLine>
+<CodeLine># is not needed if the http server sets the environment variable</CodeLine>
+<CodeLine># SCRIPT_NAME</CodeLine>
+<CodeLine>#gwcgi         /cgi-bin/library</CodeLine>
+<CodeLine># maxrequests is the most requests a fastcgi process</CodeLine>
+<CodeLine># will serve before it exits. This can be set to a</CodeLine>
+<CodeLine># low figure (like 1) while debugging and then set</CodeLine>
+<CodeLine># to a high figure (like 10000) when everything is</CodeLine>
+<CodeLine># working well.</CodeLine>
+<CodeLine>#maxrequests 10000</CodeLine>
+<Text id="254">Vous pouvez personnaliser votre installation en Ã©ditant ce fichier, mais il est peu probable que vous en Ã©prouviez le besoin.</Text>
+<Text id="255">La ligne gsdlhome pointe tout simplement vers le rÃ©pertoire CProgram Filesgsdl.</Text>
+<Text id="256">httpprefix est l'adresse web du rÃ©pertoire oÃ¹ Greenstone est installÃ©. Nous avons expliquÃ© plus haut comment crÃ©er un alias de maniÃšre que les URL de la formehttp://localhost/gsdl/...soient recherchÃ©es dans le rÃ©pertoire CProgram Filesgsdl. Placer la ligne httpprefix /gsdl dans le fichier de configuration gsdlsite met en place les mÃªmes conventions pour le logiciel Greenstone.</Text>
+<Text id="257">httpimg est l'adresse web de CProgram Filesgsdlimages, rÃ©pertoire qui contient toutes les images (au format GIF) utilisÃ©es par l'interface. Dans toutes les installations standard de Greenstone ce sera httpprefix/images, et vous n'interviendrez pas sur cette ligne.</Text>
+<Text id="258">gwcgi est l'adresse web du programme CGI library. La plupart des serveurs web (dont Apache) n'en ont pas besoin, et cette ligne doit alors rester commentÃ©e, donc inactive. N'ÃŽtez le commentaire que si vous Ãªtes sÃ»r de vous, car cela peut poser certains problÃšmes.</Text>
+<Text id="259">maxrequests n'est utilisÃ© que par les versions de Greenstone qui ont activÃ© l'option Â«Fast-CGIÂ» lors de la compilation. La distribution binaire standard n'inclut pas cette option, car tous les serveurs web ne sont pas configurÃ©s de maniÃšre compatible. L'option Â«Fast-CGIÂ» accÃ©lÃšre l'exÃ©cution des scripts CGI en gardant l'exÃ©cutable principal en mÃ©moire entre deux invocations du logiciel, au lieu de le charger depuis le disque dur Ã  chaque requÃªte d'une page web depuis le logiciel Greenstone. Le compromis Ã  trouver est un Ã©quilibre avec la quantitÃ© de mÃ©moire utilisÃ©e, qui peut augmenter si le programme demeure longtemps en mÃ©moire. AprÃšs la gÃ©nÃ©ration de maxrequests pages web, le programme CGI rend la main, libÃ©rant ainsi toute la mÃ©moire accumulÃ©e. Pour rÃ©pondre Ã  la prochaine requÃªte provoquÃ©e par une page web, le programme CGI est alors relu depuis le disque dur, et un nouveau cycle de requÃªtes de pages dÃ©marre. La plupart des installations utilisent le protocole standard CGI, ce qui signifie qu'on peut ignorer sans crainte le paramÃštre maxrequests.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="personalizing">
+<Title>
+<Text id="260">Personnaliser son installation</Text>
+</Title>
+<Content>
+<Text id="261">La premiÃšre chose que vous aurez probablement envie de faire aprÃšs l'installation de Greenstone et la vÃ©rification de son bon fonctionnement, c'est de personnaliser la page d'accueil. Le fichier qui engendre la page d'accueil de Greenstone s'appelle home.dm, et se situe dans le sous-rÃ©pertoire macros du rÃ©pertoire oÃ¹ vous avez installÃ© Greenstone. Pour les systÃšmes Windows, la valeur par dÃ©faut est donc CProgram Filesgsdlmacroshome.dm. C'est un fichier texte qu'il faudra Ã©diter pour crÃ©er une nouvelle page d'accueil. Au lieu de l'Ã©diter, nous recommandons de crÃ©er un nouveau fichier, disons yourhome.dm (chez moi). Ce fichier ressemblera au fichier home.dm mais dÃ©finira le Â«paquetage homeÂ»Â --Â la portion activeÂ --Â un peu diffÃ©remment.</Text>
+<Text id="262">Quand on met en place une autre page d'accueil, il faut pouvoir la relier d'une faÃ§on ou d'une autre aux pages de la bibliothÃšque numÃ©rique de maniÃšre Ã  pouvoir effectuer des recherches et naviguer dans les collections sur votre systÃšme. La solution adoptÃ©e par Greenstone est d'utiliser des Â«macrosÂ». C'est la raison pour laquelle le fichier correspondant Ã  la page d'accueil a un nom qui se termine en Â«.dmÂ» et non pas en Â«.htmlÂ»Â --Â c'est un fichier Â«de macrosÂ», et non pas un fichier HTML habituel. Pas d'inquiÃ©tude cependant: le fichier de macros ne contient que de l'HTML, entremÃªlÃ© de quelques incantations mystiques expliquÃ©es ci-dessous. Le langage de macros regorge de potentialitÃ©s puissantes, et nous n'en dÃ©crivons ici qu'une faible portion (reportez-vous au Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone pour obtenir plus d'informations Ã  son sujet).</Text>
+<Section id="example">
+<Title>
+<Text id="263">Exemple</Text>
+</Title>
+<Content>
+<Figure id="your_own_greenstone_home_page">
+<Title>
+<Text id="264">Votre propre page d'accueil de Greenstone</Text>
+</Title>
+<File width="395" height="227" url="images/Install_Fig_3.png"/>
+</Figure>
+<Text id="265">La figureÂ <CrossRef target="Figure" ref="your_own_greenstone_home_page"/> montre un exemple d'une nouvelle page d'accueil pour la bibliothÃšque numÃ©rique. Chacun des liens mentionnant Â«Cliquez iciÂ» vous emmÃšnera sur la portion correspondante de Greenstone. Cette page fut engendrÃ©e par le fichier yourhome.dm, prÃ©sentÃ© en figureÂ <CrossRef target="Figure" ref="yourhome_dm"/>.</Text>
+<Figure id="yourhome_dm">
+<Title>
+<Text id="266">Fichier yourhome.dm utilisÃ© pour crÃ©er la figureÂ <CrossRef target="Figure" ref="your_own_greenstone_home_page"/></Text>
+</Title>
+<CodeLine>package home</CodeLine>
+<CodeLine>_content_ {</CodeLine>
+<CodeLine>&lt;h2&gt;Your own Greenstone home page&lt;/h2&gt;</CodeLine>
+<CodeLine>&lt;ul&gt;</CodeLine>
+<CodeLine>&lt;table&gt;</CodeLine>
+<CodeLine>&lt;tr valign=top&gt;&lt;td&gt;Search page for the demo collection&lt;br&gt;&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httpquery_&amp;c=demo"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;"About" page for the demo collection&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppageabout_&amp;c=demo"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;Preferences page for the demo collection&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppagepref_&amp;c=demo"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;Home page&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppagehome_"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;Help page&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppagehelp_"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;Administration page&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppagestatus_"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;tr&gt;&lt;td&gt;The Collector&lt;/td&gt;</CodeLine>
+<CodeLine>      &lt;td&gt;&lt;a href="_httppagecollector_"&gt;Click here&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;</CodeLine>
+<CodeLine>&lt;/table&gt;</CodeLine>
+<CodeLine>&lt;/ul&gt;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine># if you hate the squirly green bar down the left-hand side of the</CodeLine>
+<CodeLine># page, uncomment these lines:</CodeLine>
+<CodeLine># _header_ {</CodeLine>
+<CodeLine># }</CodeLine>
+</Figure>
+<Text id="267">Vous pouvez utiliser la figureÂ <CrossRef target="Figure" ref="yourhome_dm"/> comme un patron pour crÃ©er votre propre page d'accueil de Greenstone. Pour simplifier, il dÃ©finit une macro Â«contentÂ», et les accolades renferment de l'HTML ordinaire, ainsi que toute commande de mise en forme HTML, pour inclure le contenu que vous souhaitez voir apparaÃ®tre sur la page. Le texte Ã©tant de l'HTML standard, vous pouvez si vous le souhaitez inclure des liens hypertexte et utiliser toutes les autres fonctionnalitÃ©s du HTML.</Text>
+<Text id="268">Pour relier votre nouvelle page d'accueil Ã  d'autres pages de la bibliothÃšque numÃ©rique, vous devrez utilisez une formule magique appropriÃ©e. Dans ce langage de macros, les formules magiques sont entourÃ©es de caractÃšres de soulignementÂ --Â vous pouvez en voir dans la figureÂ <CrossRef target="Figure" ref="yourhome_dm"/>. Par exemple,<i>_httppagehome_</i>vous emmÃšne sur la page d'accueil,<i>_httppagehelp_</i>vers la page d'aide, etc. Dans certains cas il vous faudra prÃ©ciser le nom d'une collection. La chaÃ®ne qui suit,<i>_httpquery_&amp;c=demo</i>, donne la page de recherche pour la collection Â«DemoÂ»; dans le cas d'autres collections vous remplacerez la chaÃ®ne Â«<i>demo</i>Â» par le nom de la collection dÃ©sirÃ©e.</Text>
+<Text id="269">La macro<i>_content_</i>contient directement du HTML. On peut placer n'importe quel code HTML dans une dÃ©finition de macro. Cependant, les caractÃšres spÃ©ciaux<i>{</i>,<i>}</i>,<i>\</i>, et<i>_</i>devront Ãªtre prÃ©cÃ©dÃ©s d'une barre oblique inversÃ©e (backslash, c'est-Ã -dire Â«Â») pour leur Ã©viter d'Ãªtre interprÃ©tÃ©s par l'interprÃ©teur du langage de macros.</Text>
+<Text id="270">Vous remarquerez que la dÃ©finition de macro<i>_content_</i>ne contient ni en-tÃªte ni pied de page HTML. Si vous souhaitez intervenir sur ces Ã©lÃ©ments dans votre page d'accueil, ce sont les macros<i>_header_</i>et/ou<i>_footer_</i>qu'il vous faudra personnaliser respectivement, en les ajoutant Ã  votre fichier yourhome.dm sous la forme</Text>
+<CodeLine>_macroname_ {</CodeLine>
+<CodeLine>...</CodeLine>
+<CodeLine>}</CodeLine>
+<Text id="271">Par exemple, la barre verte ondulante sur la gauche des pages Greenstone est dÃ©finie dans la macro<i>_header_</i>, et elle disparaÃ®tra si on dÃ©clare cette macro comme Ã©tant vide, comme indiquÃ© Ã  la fin de la figureÂ <CrossRef target="Figure" ref="yourhome_dm"/>.</Text>
+</Content>
+</Section>
+<Section id="how_to_make_it_work">
+<Title>
+<Text id="272">Mise en place</Text>
+</Title>
+<Content>
+<Text id="273">Il faut informer Greenstone de l'existence de la nouvelle page d'accueil, de nom yourhome.dm. Le systÃšme charge les fichiers de macros spÃ©cifiÃ©s dans le fichier de configuration principal main.cfg, c'est pourquoi il faut y indiquer tout nouveau fichier crÃ©Ã©. Les collisions de noms sont gÃ©rÃ©es comme on pourrait s'y attendre: les dÃ©finitions les plus rÃ©centes ont la prioritÃ©.</Text>
+<Text id="274">Ainsi, pour faire en sorte que le logiciel de bibliothÃšque numÃ©rique Greenstone utilise la page d'accueil de la figureÂ <CrossRef target="Figure" ref="your_own_greenstone_home_page"/> en lieu et place de la page par dÃ©faut, il faut commencer par placer le fichier yourhome.dm de la figureÂ <CrossRef target="Figure" ref="yourhome_dm"/> dans le rÃ©pertoire macros. Il faut ensuite Ã©diter le fichier de configuration main.cfg et y remplacer home.dm par yourhome.dm dans la liste des fichiers de macros chargÃ©s au dÃ©marrage.</Text>
+</Content>
+</Section>
+<Section id="redirecting_a_url_to_greenstone">
+<Title>
+<Text id="275">Renvoyer une URL vers Greenstone</Text>
+</Title>
+<Content>
+<Text id="276">Vous Ã©prouverez peut-Ãªtre l'envie de rediriger une URL plus pratique vers le CGI de Greenstone. Sur notre systÃšme, par exemple, l'URLhttp://nzdl.org(qui est un raccourci pourhttp://nzdl.org/index.html) est renvoyÃ©e vershttp://nzdl.org/cgi-bin/library. C'est la directive Redirect qui s'occupe de cela pour le serveur web Apache. Comme les autres directives, elle prend place dans le fichier de configuration CProgram FilesApache GroupApacheconfhttpd.conf. Pour renvoyer l'URLhttp://www.monserveur.comvershttp://www.monserveur.com/cgi-bin/library, ajoutez la ligne suivante dans le fichier httpd.conf:</Text>
+<CodeLine>Redirect /index.html http://www.yourserver.com/cgi-bin/library</CodeLine>
+<Text id="277">Vous pourrez ensuite atteindre votre systÃšme de bibliothÃšque numÃ©rique directement depuis l'URLhttp://www.monserveur.com. Si vous souhaitez plutÃŽt que ce soit l'URLhttp://www.monserveur.com/greenstonequi soit renvoyÃ©e vershttp://www.monserveur.com/cgi-bin/library, c'est la ligne suivante qu'il faudra inclure dans le fichier httpd.conf:</Text>
+<CodeLine>Redirect /greenstone http://www.yourserver.com/cgi-bin/library</CodeLine>
+<Text id="278">Si votre ordinateur ne dispose pas de nom dans le DNS (ou systÃšme de noms), tel que Â«www.monserveur.comÂ» dans l'exemple donnÃ© ci-dessus, il suffit de remplacerwww.monserveur.compar localhostdans toutes les lignes d'exemple. Tant que le navigateur et le serveur web fonctionnent sur la mÃªme machineÂ --Â ce qui est sÃ»rement le cas si votre ordinateur ne dispose pas de nom dans le DNSÂ --Â l'effet obtenu sera exactement le mÃªme.</Text>
+<Text id="279">Au lieu de placer les directives de redirection dans le fichier httpd.conf, on peut tout aussi bien les placer dans un fichier appelÃ© .htaccess, et placÃ© dans le rÃ©pertoire racine des documents du serveur web. Cette solution prÃ©sente mÃªme deux avantages sur la prÃ©cÃ©dente. D'abord, les modifications apportÃ©es au fichier .htaccess sont immÃ©diatement actives, alors qu'il faut redÃ©marrer le serveur web Apache pour observer les effets de changements apportÃ©s au fichier httpd.conf. Ensuite, il faut gÃ©nÃ©ralement Ãªtre connectÃ© en tant que l'utilisateur Â«rootÂ» sur les systÃšmes Unix pour pouvoir Ã©diter le fichier httpd.conf, mais ce n'est souvent pas le cas du fichier .htaccess.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_associated_software">
+<Title>
+<Text id="280">Logiciels associÃ©s</Text>
+</Title>
+<Content>
+<Text id="281">Voici comment obtenir les paquetages logiciels mentionnÃ©s dans ce document.</Text>
+<Section id="apache_webserver">
+<Title>
+<Text id="282">Le serveur web Apache</Text>
+</Title>
+<Content>
+<Text id="283">Toutes les versions de Greenstone, Ã  l'exception de la version bibliothÃšque locale pour Windows, requiÃšrent un serveur web externe. De nombreuses installations, et en particulier les plus volumineuses, disposeront dÃ©jÃ  d'un serveur web. Si vous utilisez Linux, Apache se trouve peut-Ãªtre sur votre cÃ©dÃ©rom sans avoir Ã©tÃ© sÃ©lectionnÃ© lors de la procÃ©dure d'installation. Le serveur web Apache, disponible Ã  l'URLwww.apache.org, est libre et facile Ã  installer.</Text>
+</Content>
+</Section>
+<Section id="perl">
+<Title>
+<Text id="284">Perl</Text>
+</Title>
+<Content>
+<Text id="285">Pour construire des collections avec Greenstone il faut disposer du langage Perl, version 5 ou ultÃ©rieure. Dans le cas des systÃšmes Windows, nous recommandons ActivePerl, disponible surwww.activestate.com. La plupart des systÃšmes Unix disposeront dÃ©jÃ  d'une installation de Perl mais dans le cas contraire, vous en trouverez le code source ainsi que des binaires pour de nombreuses plates-formes Unix, le tout librement tÃ©lÃ©chargeable, Ã  l'URLwww.perl.com.</Text>
+</Content>
+</Section>
+<Section id="gcc">
+<Title>
+<Text id="286">GCC</Text>
+</Title>
+<Content>
+<Text id="287">La version Unix de Greenstone se compile avec le compilateur C++ de GNU, GCC. Greenstone utilise intensivement la bibliothÃšque standard de patrons pour C++, STL (nous avons remarquÃ© qu'elle Ã©tait cassÃ©e sur d'anciennes versions GCC; veuillez nous signaler tout problÃšme relatif Ã  STL que vous rencontreriez). Prenez note du fait que cette version de Greenstone ne compilera pas avec la version 3.0 de GCC.</Text>
+</Content>
+</Section>
+<Section id="gdbm">
+<Title>
+<Text id="288">GDBM</Text>
+</Title>
+<Content>
+<Text id="289">Toutes les versions de Greenstone utilisent GDBM, le gestionnaire de bases de donnÃ©es de GNU. Il est fourni avec toutes les versions Windows de Greenstone et installÃ© automatiquement pendant la procÃ©dure d'installation. Les systÃšmes Linux en disposant dÃ©jÃ , nous ne le fournissons pas pour ces derniers. La plupart des autres systÃšmes Unix en disposent, mais si nÃ©cessaire vous pourrez le tÃ©lÃ©charger depuis l'URLwww.gnu.org.</Text>
+</Content>
+</Section>
+<Section id="java_runtime_environment">
+<Title>
+<Text id="290">Environnement Java Runtime</Text>
+</Title>
+<Content>
+<Text id="291">Pour utiliser "Greenstone Librarian Interface" (l'Interface BibliothÃ©caire de Greenstone), il est nÃ©cessaire de disposer d'une version appropriÃ©e de Java Runtine Environment. Si on n'en dispose pas, une version appropriÃ©e est incluse dans le CD-ROM; le cas Ã©chÃ©ant, le tÃ©lÃ©chargement de la derniÃšre version est possible Ã  partir dehttp://java.sun.com/j2se/downloads.html. La version 1.4.0 ou supÃ©rieure est requise.</Text>
+</Content>
+</Section>
+<Section id="java_compiler">
+<Title>
+<Text id="292">Compilateur Java</Text>
+</Title>
+<Content>
+<Text id="293">Pour compiler le code source de l'Interface du BibliothÃ©caire Greenstone, vous devez d'abord installer un Java Development Toolkit. Vous pouvez tÃ©lÃ©charger J2SE (Software Development Kit) de l'URL http://java.sun.com/j2se/downloads.html. La version 1.4.0 or supÃ©rieur est nÃ©cessaire.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/fr/Paper_fr.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/fr/Paper_fr.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/fr/Paper_fr.xml	(revision 13632)
@@ -0,0 +1,851 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1"/>
+</Heading>
+<Title>
+<Text id="2">BibliothÃšque numÃ©rique Greenstone: du papier Ã  la collection</Text>
+</Title>
+<Author>
+<Text id="3">Dr Michel Loots, Dan Camarzan et Ian H. Witten</Text>
+</Author>
+<Affiliation>
+<Text id="4">ONG Human Info, Belgique<br/>Simple Words, Roumanie<br/>UniversitÃ© de Waikato, Nouvelle-ZÃ©lande</Text>
+</Affiliation>
+<Comment>
+<Text id="5">Greenstone est une suite logicielle destinÃ©e Ã  la construction et Ã  la distribution de collections de bibliothÃšques numÃ©riques. Cette suite fournit une nouvelle maniÃšre d'organiser l'information et de la publier sur l'Internet ou sur un cÃ©dÃ©rom. Greenstone est produit par le projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande (dÃ©pendant de l'universitÃ© de Waikato), et dÃ©veloppÃ© et distribuÃ© en coopÃ©ration avec l'UNESCO et l'ONG Human Info.C'est un logiciel Open Source, diffusÃ© selon les termes de la licence publique gÃ©nÃ©rale de GNU, et qu'on peut obtenir Ã  l'URLhttp://greenstone.org.</Text>
+<Text id="6">Nous souhaitons nous assurer que ce logiciel fonctionne bien pour vous. Faites-nous part, en anglais, de tout problÃšme Ã  l'adresse Ã©lectronique.</Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">Mars 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">Ã propos de ce manuel</Text>
+</Title>
+<Content>
+<Text id="10">Ce document explique comment crÃ©er des collections de cÃ©dÃ©roms Ã  partir de documents papier. Il dÃ©crit en dÃ©tail les procÃ©dures et les coÃ»ts relatifs Ã  la numÃ©risation et aux processus de reconnaissance optique de caractÃšres (ROC, ou OCR), de maniÃšre Ã  obtenir des textes dans un format que Greenstone puisse accepter. Il dÃ©crit aussi comment crÃ©er et Ã©diter le matÃ©riel associÃ© Ã  une collection.</Text>
+<Text id="11">Nous nous sommes efforcÃ©s d'Ãªtre aussi clairs et complets que possible dans nos explication. Toute marque commerciale mentionnÃ©e ne l'est que dans un but d'illustration, et cela ne signifie en rien que nous conseillions, favorisions ou recommandions ce produit d'une quelconque maniÃšre.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="12">Documents d'accompagnement</Text>
+</Title>
+<Content>
+<Text id="13">L'ensemble des documents de Greenstone comprend cinq volumes:</Text>
+<BulletList>
+<Bullet>
+<Text id="14">Guide d'installation de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="15">Guide de l'utilisateur de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="17">BibliothÃšque numÃ©rique Greenstone: du papier Ã  la collection (<i>ce document-ci</i>)</Text>
+</Bullet>
+<Bullet>
+<Text id="18">BibliothÃšque numÃ©rique Greenstone: Utilisation de "L'organizer"</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">Remerciements</Text>
+</Title>
+<Content>
+<Text id="20">L'opÃ©ration de numÃ©risation, l'Organizer et tout le savoir-faire relatif Ã  la crÃ©ation de collections Ã  but non lucratif par le fruit d'un travail de collaboration furent dÃ©veloppÃ©s par Michel Loots, docteur en mÃ©decine, membre des projets Human Info NGO et HumanityCD, et par Dan Camarzan de Simple Words, ainsi que par leurs collaborateurs de Brasov, en Roumanie.</Text>
+<Text id="21">Le logiciel Greenstone a vu le jour grÃ¢ce Ã  un effort de collaboration entre de nombreuses personnes. Rodger McNab et Stefan Boddie en sont les principaux architectes et dÃ©veloppeurs. Des contributions ont Ã©tÃ© faites par David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, et Stuart Yeates. D'autres membres du Projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande ont Ã©galement donnÃ© des conseils et inspirÃ© les concepteurs du systÃšme: Mark Apperley, Sally Jo Cunningham, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, et Lloyd Smith. Nous remercions aussi tous ceux qui ont contribuÃ© au dÃ©veloppement des modules sous licence GNU GPL qui font partie de cette distribution: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE, XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="introduction">
+<Title>
+<Text id="22">Introduction</Text>
+</Title>
+<Content>
+<Text id="23">L'un des objectifs du logiciel de bibliothÃšque numÃ©rique Greenstone est de permettre Ã  des entitÃ©s telles que des universitÃ©s, des agences des Nations Unies, des organisations non gouvernementales, des associations Ã  but non lucratif, ou des gouvernements, de crÃ©er des collections variÃ©es d'informations qui pourront Ãªtre diffusÃ©es en ligne ou sur cÃ©dÃ©rom.</Text>
+<Text id="24">Les Ã©tapes Ã  suivre seront typiquement:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="25">SÃ©lection des documents Ã  inclure</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="26">S'assurer des atorisations d'utilisation de ces documents (droits d'auteurs et copyrights) dans la bibliothÃšque numÃ©rique</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="27">NumÃ©risation et ROC des documents papier non disponibles sous forme numÃ©rique de maniÃšre Ã  disposer d'un format numÃ©rique parfait</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="28">Conversion de tous les documents dans un format (comprenant texte et images) qu'il est possible d'importer dans Greenstone (de prÃ©fÃ©rence HTML ou Microsoft Word, mais d'autres formats sont Ã©galement possibles, et traitÃ©s plus ou moins prÃ©cisÃ©ment par un Â«greffonÂ» (plugin) qui leur est propre (voir Ã  ce sujet le Guide de l'utilisateur de la bibliothÃšque numÃ©rique Greenstone))</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="29">Ãtiquetage des chapitres, paragraphes et images des documents numÃ©riques</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="30">Organisation de la collection sous forme d'une bibliothÃšque numÃ©rique structurÃ©e de maniÃšre optimale</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="31">Construction de la bibliothÃšque numÃ©rique Ã  l'aide du logiciel Greenstone</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="32">Pressage et distribution de la collection sur cÃ©dÃ©rom et/ou distribution sur l'Internet</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="33">Pour crÃ©er une collection numÃ©rique, les publications doivent Ãªtre disponibles dans un format numÃ©rique. Si des livres, revues ou d'autres documents ne sont disponibles que sous forme de papier, il faudra les numÃ©riser et les traiter sous un format lisible par ordinateur (Ã©tape iii). GÃ©nÃ©ralement on procÃšde par reconnaissance optique de caractÃšres (ROC, ou OCR), mais parfois on saisit les documents Ã  nouveau, au clavier. Ce processus est dÃ©crit dans les sectionsÂ 2Ã Â 4du prÃ©sent manuel.</Text>
+<Text id="34">L'Ã©tape v active les diffÃ©rentes portions d'un document qui pourront Ãªtre sÃ©lectionnÃ©es indÃ©pendamment et affichÃ©es par les lecteurs dans la bibliothÃšque rÃ©sultante, alors que l'Ã©tape vi correspond Ã  l'affectation d'attributs Ã  des documents tels que les catÃ©gories de thÃšmes, de mots-clefs, et les donnÃ©es bibliographiques, utilisÃ©es pour le classement et la recherche dans la bibliothÃšque. Ces Ã©tapes sont traitÃ©es au chapitreÂ 5de ce manuel.</Text>
+<Text id="35">Ce manuel prÃ©sente les nombreux problÃšmes qui se posent lors du processus d'Ã©dition et de crÃ©ation d'une collection Ã  partir de documents papier. Avant de poursuivre la lecture, posez-vous les questions suivantes:</Text>
+<BulletList>
+<Bullet>
+<Text id="36">Quel but poursuit la collection?</Text>
+</Bullet>
+<Bullet>
+<Text id="37">Quel public est ciblÃ©?</Text>
+</Bullet>
+<Bullet>
+<Text id="38">Quelle couverture gÃ©ographiqueÂ --Â locale, rÃ©gionale, mondiale?</Text>
+</Bullet>
+<Bullet>
+<Text id="39">Combien de documents seront rendus disponibles?</Text>
+</Bullet>
+<Bullet>
+<Text id="40">Combien de pages?</Text>
+</Bullet>
+<Bullet>
+<Text id="41">Quelle quantitÃ© de contenus graphiques?</Text>
+</Bullet>
+<Bullet>
+<Text id="42">Le contenu se divise-t-il en portions que seul un public limitÃ© consultera et en portions Ã  dissÃ©miner plus largement?</Text>
+</Bullet>
+<Bullet>
+<Text id="43">Les documents sont-ils dÃ©jÃ  disponibles sous forme Ã©lectronique?</Text>
+</Bullet>
+<Bullet>
+<Text id="44">Si tel est le cas, sous quels formats? (remarquez au passage que des fichiers au format PDF ne sont pas toujours Ã©quivalents Ã  leur contenu textuel sous forme numÃ©rique, puisqu'ils ne contiennent souvent que des images, une par page)</Text>
+</Bullet>
+<Bullet>
+<Text id="45">Quels sont les droits qui s'appliquent aux documents?</Text>
+</Bullet>
+<Bullet>
+<Text id="46">Qui possÃšde des droits?</Text>
+</Bullet>
+<Bullet>
+<Text id="47">Existe-t-il d'autres organisations ciblant le mÃªme public?</Text>
+</Bullet>
+<Bullet>
+<Text id="48">Souhaitez-vous collaborer avec d'autres groupes?</Text>
+</Bullet>
+<Bullet>
+<Text id="49">Quel est le budget global du projet?</Text>
+</Bullet>
+<Bullet>
+<Text id="50">De quelles ressources humaines (en hommes-mois) disposez-vous pour la coordination, l'Ã©dition, la numÃ©risation et la programmation?</Text>
+</Bullet>
+<Bullet>
+<Text id="51">De combien d'ordinateurs disposez-vous pour ce projet?</Text>
+</Bullet>
+<Bullet>
+<Text id="52">Combien de cÃ©dÃ©roms souhaitez-vous distribuer? </Text>
+</Bullet>
+<Bullet>
+<Text id="53">Seront-ils gratuits ou payants? </Text>
+</Bullet>
+</BulletList>
+</Content>
+</Chapter>
+<Chapter id="scanners_and_scanning">
+<Title>
+<Text id="54">Les scanners et la numÃ©risation</Text>
+</Title>
+<Content>
+<Text id="55">La premiÃšre Ã©tape dans la conversion de documents papier en une collection pour bibliothÃšque numÃ©rique est d'obtenir des images de toutes les pages de toutes les publications sous forme numÃ©rique. L'Ã©tape suivante consiste Ã  appliquer une reconnaissance optique de caractÃšres (ROC, ou OCR), pour la rÃ©ussite de laquelle il est essentiel de disposer d'images propres et de bonne qualitÃ©. Le processus de numÃ©risation utilise un scanner qui travaille Ã  une rÃ©solution minimale de 300 dpi (points par pouce, ou dots per inch). La plupart des numÃ©risations peuvent se faire en noir et blanc, mais en prÃ©sence d'illustrations en couleurs il faut utiliser un scanner couleur. Dans la plupart des cas les couvertures des livres sont en couleurs et il faudra les numÃ©riser en tant que photographie couleur.</Text>
+<Section id="scanners">
+<Title>
+<Text id="56">Les scanners</Text>
+</Title>
+<Content>
+<Text id="57">On trouve des scanners Ã  tous les prix, de toutes tailles et de toutes formes. Ils coÃ»tent de 100$ pour les scanners Ã  plat Ã  50Â 000$ pour de gros scanners industriels de fabricants tels que Bell &amp; Howell<FootnoteRef id="1"/>. On trouve de nombreux sites web qui proposent de nombreux scanners Ã  vendre. Vous les trouverez facilement en tapant le mot-clef Â«scannerÂ» dans des moteurs de recherche tels que Google, Altavista, ou Yahoo. </Text>
+<Text id="58">Le format de sortie des scanners est un fichier informatique dont le format est souvent TIFF ou bitmap. Le meilleur format est le TIFF IV compressÃ©: une page numÃ©risÃ©e et convertie en ce format n'occupe en moyenne que 50 kilo-octets, Ã  comparer aux 2 mÃ©ga-octets qu'elle occuperait sous forme bitmap non compressÃ©e.</Text>
+<Subsection id="low-cost_flat-bed_scanner">
+<Title>
+<Text id="59">Scanners Ã  plat de bas de gamme</Text>
+</Title>
+<Content>
+<Text id="60">Les scanners Ã  plat sont les moins onÃ©reux et les plus communs. De nombreuses marques en proposent: HP, Agfa, Acer, etc. Les prix s'Ã©talent de 100 Ã  300$. On peut numÃ©riser Ã  la fois des images en noir et blanc ou en couleurs. Le faible prix permet d'Ã©quiper chaque ordinateur de son propre scanner.</Text>
+<Text id="61">Ces scanners ont pour inconvÃ©nients une qualitÃ© moyenne du rÃ©sultat, une faible vitesse de numÃ©risation, une fiabilitÃ© rÃ©duite quand la tempÃ©rature s'Ã©lÃšve, et des pannes frÃ©quentes. Il faut numÃ©riser les pages manuellement, une Ã  une. Chaque page doit Ãªtre placÃ©e avec attention sur la vitre de numÃ©risation de maniÃšre Ã  obtenir un alignement correct. Ces scanners ont une faible productivitÃ©. Bien que les fabricants prÃ©tendent qu'on peut scanner une page en moins d'une minute, il est rare dans la pratique de pouvoir scanner plus de douze pages en une heure. Le processus de numÃ©risation monopolise l'ordinateur utilisÃ©.</Text>
+<Text id="62">C'est pourquoi de tels scanners ne sont utiles que pour des petits travaux de numÃ©risation, avec de 200 Ã  400 pages par mois de maniÃšre rÃ©guliÃšre, ou de 1000 Ã  2000 pages de maniÃšre exceptionnelle.</Text>
+</Content>
+</Subsection>
+<Subsection id="low-end_scanner_with_sheet_feeder">
+<Title>
+<Text id="63">Scanners de bas de gamme avec chargeur</Text>
+</Title>
+<Content>
+<Text id="64">Ces scanners coÃ»tent de 500 Ã  1200$. On peut insÃ©rer, scanner et traiter de 10 Ã  50 pages d'un coup: l'opÃ©rateur ne doit pas rester constamment aux cÃŽtÃ©s de la machine. Cela permet d'atteindre une productivitÃ© de 150 Ã  200 pages par jour. Ces scanners sont plus robustes et tombent en panne moins souventÂ --Â ils permettent gÃ©nÃ©ralement de traiter de 30 Ã  50Â 000 pages avant de nÃ©cessiter une rÃ©paration.</Text>
+<Text id="65">Ils ont pour inconvÃ©nient de ne numÃ©riser qu'une face de chaque feuille Ã  la foisÂ --Â il faut retourner la pile de feuilles et la numÃ©riser de nouveau pour obtenir les versos. Ceci crÃ©e des problÃšmes car les chargeurs causent souvent des ennuis des bourrages papier.</Text>
+<Text id="66">Ces scanners sont utiles pour des volumes de 1500 Ã  3000 pages par mois.</Text>
+</Content>
+</Subsection>
+<Subsection id="color_scanners">
+<Title>
+<Text id="67">Scanners couleur</Text>
+</Title>
+<Content>
+<Text id="68">Toute opÃ©ration de numÃ©risation se heurte tÃŽt ou tard au problÃšme des images couleur, c'est pourquoi il faudra toujours disposer d'un scanner couleur. De maniÃšre gÃ©nÃ©rale, moins de 5% de toute publication contient des images couleur, sans compter la couverture. C'est pourquoi un scanner Ã  plat tel que dÃ©crit ci-dessus suffira. Nous conseillons de choisir un scanner capable d'une rÃ©solution de 600 dpi.</Text>
+</Content>
+</Subsection>
+<Subsection id="professional_duplex_scanners">
+<Title>
+<Text id="69">Scanners professionnels bi-faces</Text>
+</Title>
+<Content>
+<Text id="70">Les scanners professionnels sont des machines fiables et industrielles, capables de traiter un grand volumeÂ --Â de 2 Ã  10Â 000 pages par jour. Ils disposent d'un systÃšme de chargeur automatique Ã  plateau qui peut recevoir des paquets de 50 Ã  200 pages. Les meilleurs et les plus rapides sont des machines duplex qui peuvent numÃ©riser les deux faces d'une feuille d'un coup.</Text>
+<Text id="71">Les scanners professionnels duplex ont besoin d'un ordinateur puissant Ã©quipÃ© d'un disque dur de 10 Ã  20 giga-octets. Les prix s'Ã©talent de 5 Ã  50Â 000$. Par exemple, le scanner duplex Canon DR-6020 coÃ»te 5000$ et peut traiter des documents recto-verso. Il a une capacitÃ© d'environ 2000 pages par jour et une durÃ©e de vie de 600 Ã  800Â 000 pages. Les scanners Bell &amp; Howell et Fujitsu coÃ»tent de 10 Ã  50Â 000$ et ont une durÃ©e de vie de plusieurs millions de pages.</Text>
+<Text id="72">Les scanners Ã  micro-fiches coÃ»tent de 15Â 000$ pour une unitÃ© semi-automatique Ã  80Â 000$ pour une unitÃ© entiÃšrement automatisÃ©e.</Text>
+</Content>
+</Subsection>
+<Subsection id="scanning_programs">
+<Title>
+<Text id="73">Logiciels de numÃ©risation</Text>
+</Title>
+<Content>
+<Text id="74">Tous les scanners sont fournis avec leur propre logiciel, qui doit donc Ãªtre installÃ© sur l'ordinateur qui pilote le scanner. Certains scanners disposent d'une carte Ã  enficher sur l'ordinateur pour accÃ©lÃ©rer l'opÃ©ration de numÃ©risation.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="preparing_the_documents">
+<Title>
+<Text id="75">La prÃ©paration des documents</Text>
+</Title>
+<Content>
+<Text id="76">Avant d'Ãªtre numÃ©risÃ©s, les documents doivent Ãªtre correctement prÃ©parÃ©s. Il faut dÃ©poussiÃ©rer, sÃ©cher, enlever les agrafes, et aplanir les pages pliÃ©es.</Text>
+<Text id="77">Il faut ÃŽter la reliure des livres par une coupure nette, droite et prÃ©cise. Les livres des bibliothÃšques devront souvent Ãªtre reliÃ©s Ã  nouveau, auquel cas la plus grande attention est nÃ©cessaire lors de cette opÃ©ration, ce qui facilitera la mise en place de la nouvelle reliure.</Text>
+<Text id="78">Pour un nombre limitÃ© de documents, la coupe peut se faire Ã  la rÃšgle et au cutter. Faites attention Ã  vos mains! Pour des plus gros volumes, il existe des machines Ã  couper faites pour.</Text>
+<Text id="79">Pour des gros volumes (Ã  partir de 20 documents) nous recommandons de demander Ã  un imprimeur ou une boÃ®te Ã  copies l'autorisation d'utiliser leur massicot professionnel. N'oubliez pas d'ÃŽter toute agrafe ou trombone; ils pourraient endommager les lames.</Text>
+</Content>
+</Section>
+<Section id="the_scanning_process">
+<Title>
+<Text id="80">L'opÃ©ration de numÃ©risation</Text>
+</Title>
+<Content>
+<Text id="81">Quand on utilise le logiciel fourni avec le scanner, chaque page est numÃ©risÃ©e et transformÃ©e en image numÃ©rique au format TIFF ou bitmap. Ces images doivent alors Ãªtre stockÃ©es sur le disque dur sous des noms de fichiers habituels. La reconnaissance optique de caractÃšres dÃ©bute Ã  la fin de la numÃ©risation de tout ou partie d'un lot de documents.</Text>
+<Text id="82">Il faudra une rÃ©solution de 300 dpi pour la numÃ©risation, mÃªme si parfois 200 dpi peuvent suffire.</Text>
+<Subsection id="quality_control">
+<Title>
+<Text id="83">ContrÃŽle qualitÃ©</Text>
+</Title>
+<Content>
+<Text id="84">La numÃ©risation a pour but de passer les pages Ã  la ROC pour produire des versions traitement de texte ou HTML des publications, ou de produire des fichiers image de bonne qualitÃ© tels que des fichiers image PDF. Dans tous les cas, la qualitÃ© de la numÃ©risation est cruciale: une mauvaise qualitÃ© produira des images peu jolies, qui occuperont plus de mÃ©moire. La nettetÃ© des images affecte Ã©normÃ©ment le processus de ROC: la productivitÃ© peut chuter jusqu'Ã  40% si la qualitÃ© n'est pas au rendez-vous. Sachant que l'opÃ©ration de ROC reprÃ©sente plus de 90% du coÃ»t total de la transformation du papier en collection, on constate que la qualitÃ© de la numÃ©risation peut avoir des effets trÃšs marquÃ©s sur le coÃ»t global.</Text>
+<Text id="85">On peut amÃ©liorer la qualitÃ© du fichier TIFF en ajustant le processus de numÃ©risation Ã  chaque type de papier, en utilisant les rÃ©glages fournis par le logiciel de numÃ©risation. Les papiers relativement transparents requerront des rÃ©glages plus clairs; il faut ajuster le contraste en fonction de la qualitÃ© d'impression, etc.</Text>
+<Text id="86">Commencez par diviser les feuilles en lots de texture de papier et de qualitÃ© d'impression comparables. Faites des tests de ROC sur un Ã©chantillon du premier lot pour dÃ©terminer les rÃ©glages optimaux. NumÃ©risez ensuite tout ce lot avant de passer au suivant.</Text>
+</Content>
+</Subsection>
+<Subsection id="filename_conventions">
+<Title>
+<Text id="87">Conventions sur les noms de fichier</Text>
+</Title>
+<Content>
+<Text id="88">Attribuez Ã  chaque livre ou document un numÃ©ro de traitement ou un code unique, qui sera utilisÃ© en tant que nom du rÃ©pertoire contenant tous les fichiers TIFF relatifs au document. Selon votre systÃšme d'exploitation (DOS, Windows, Unix, Linux, etc.), vous pourrez utiliser de 8 Ã  128 caractÃšres pour les noms de fichiers. Nous vous recommandons de vous limiter Ã  8 ou 16 caractÃšres pour cet identifiant de document. Les 5 premiers caractÃšres pourront par exemple identifier le document, la lettre suivante pourra contenir un code de langue de rÃ©daction du document, et les caractÃšres restants pourront identifier la page. Par exemple, l'identifiant u7548f12.tif pourra reprÃ©senter l'image TIFF de la page 12 d'un livre Ã©crit en franÃ§ais, de code u7548.</Text>
+<Text id="89">RÃ©servez un rÃ©pertoire du disque dur aux opÃ©rations de numÃ©risation (appelons-le par exemple scanjobs). Puis crÃ©ez un sous-rÃ©pertoire pour chaque lot. CrÃ©ez Ã  nouveau un sous-rÃ©pertoire pour chaque publication, comme par exemple u7548f pour le document ci-dessus Ã©voquÃ©. Stockez toutes les images TIFF de la publication, y compris les images couleur, dans ce rÃ©pertoire.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="productivity_and_resources">
+<Title>
+<Text id="90">De la productivitÃ© et des ressources nÃ©cessaires</Text>
+</Title>
+<Content>
+<Text id="91">Ne sous-estimez pas l'ampleur de l'opÃ©ration de numÃ©risationÂ --Â et en particulier celle de la ROC qui la suivra. Il vaut mieux considÃ©rer la numÃ©risation et la ROC comme deux activitÃ©s complÃštement sÃ©parÃ©es. Les choix optimaux, tant Ã©conomiques que pratiques, seront faits indÃ©pendamment.</Text>
+<Text id="92">Les aspects auxquels rÃ©flÃ©chir incluent les investissements nÃ©cessaires en matÃ©riel (scanners et ordinateurs); la disponibilitÃ© d'un espace disque suffisant ainsi que d'assez de ressources humaines; la formation des agents; les coÃ»ts salariaux; les nombres de pages initial et final Ã  numÃ©riser, les dates maximales de fin de travaux; et les possibilitÃ©s de sous-traitance.</Text>
+<Subsection id="scanning_costs">
+<Title>
+<Text id="93">CoÃ»ts de numÃ©risation</Text>
+</Title>
+<Content>
+<Text id="94">Une dÃ©cision importante consiste Ã  trancher entre investir en achat d'Ã©quipement de numÃ©risation et effectuer toute la numÃ©risation soi-mÃªme, ou sous-traiter cette tÃ¢che Ã  une sociÃ©tÃ© spÃ©cialisÃ©e. Les critÃšres principaux sont:</Text>
+<BulletList>
+<Bullet>
+<Text id="95">urgence du travail de numÃ©risation;</Text>
+</Bullet>
+<Bullet>
+<Text id="96">nombre total de pages;</Text>
+</Bullet>
+<Bullet>
+<Text id="97">coÃ»ts salariaux des opÃ©rateurs de numÃ©risation.</Text>
+</Bullet>
+</BulletList>
+<Text id="98">Les opÃ©rateurs doivent Ãªtre extrÃªmement motivÃ©s, douÃ©s techniquement, et soucieux de qualitÃ©. </Text>
+<Text id="99">Une sociÃ©tÃ© spÃ©cialisÃ©e rÃ©clamera en moyenne 0.06$ par page. Il faut ajouter Ã  cela le coÃ»t du transfert des documents, qui peut s'Ã©lever Ã  0.03$ pour un envoi d'un pays en voie de dÃ©veloppement vers un pays dÃ©veloppÃ©, et 0.015$ pour un envoi entre pays dÃ©veloppÃ©s.</Text>
+<Text id="100">Le tableauÂ <CrossRef target="Table" ref="table_scanning_cost"/> donne une estimation du coÃ»t du processus de numÃ©risation s'il est effectuÃ© par vos soins, en utilisant diffÃ©rents types de scanners. Vous remarquerez que ces chiffres sont des estimations, et ne sont fournis qu'en tant que rÃ©fÃ©rence approximative en se fondant sur l'expÃ©rience des auteurs. Les trois premiÃšres colonnes traitent des coÃ»ts salariaux. La premiÃšre prÃ©sente la capacitÃ© en pages par mois, sur la base d'un temps plein. On trouve les ressources nÃ©cessaires en homme-mois par page en divisant le nombre mensuel d'heures travaillÃ©es par la capacitÃ© en pages par mois de la deuxiÃšme colonne. Il est prÃ©sentÃ© dans la troisiÃšme colonne, sur la base de 180 heures travaillÃ©es par mois.</Text>
+<Table id="table_scanning_cost">
+<Title>
+<Text id="101">CoÃ»t de la numÃ©risation</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="90"/>
+<th width="71">
+<Text id="102">CapacitÃ© (pages/mois)</Text>
+</th>
+<th width="75">
+<Text id="103">Heures/page (180 h/mois)</Text>
+</th>
+<th width="83">
+<Text id="104">CoÃ»t/page (4$/h)</Text>
+</th>
+<th width="60">
+<Text id="105">Achat du scanner</Text>
+</th>
+<th width="66">
+<Text id="106">DurÃ©e de vie du scanner (en pages)</Text>
+</th>
+<th width="85">
+<Text id="107">CoÃ»t du scanner (0.06$/p.)</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="108">Scanner Ã  plat</Text>
+</th>
+<th width="71">
+<Text id="109">2 500</Text>
+</th>
+<th width="75">
+<Text id="110">0.072</Text>
+</th>
+<th width="83">
+<Text id="111">0.288$</Text>
+</th>
+<th width="60">
+<Text id="112">300$</Text>
+</th>
+<th width="66">
+<Text id="113">7 000</Text>
+</th>
+<th width="85">
+<Text id="114">5 000</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="115">Scanner Ã  chargeur</Text>
+</th>
+<th width="71">
+<Text id="116">8 000</Text>
+</th>
+<th width="75">
+<Text id="117">0.0225</Text>
+</th>
+<th width="83">
+<Text id="118">0.09$</Text>
+</th>
+<th width="60">
+<Text id="119">800$</Text>
+</th>
+<th width="66">
+<Text id="120">30 000</Text>
+</th>
+<th width="85">
+<Text id="121">13 000</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="122">Scanner pro. bas de gamme</Text>
+</th>
+<th width="71">
+<Text id="123">40 000</Text>
+</th>
+<th width="75">
+<Text id="124">0.0045</Text>
+</th>
+<th width="83">
+<Text id="125">0.018$</Text>
+</th>
+<th width="60">
+<Text id="126">6 000$</Text>
+</th>
+<th width="66">
+<Text id="127">600 000</Text>
+</th>
+<th width="85">
+<Text id="128">100 000</Text>
+</th>
+</tr>
+<tr>
+<th width="90">
+<Text id="129">Scanner pro. haut de gamme</Text>
+</th>
+<th width="71">
+<Text id="130">150 000</Text>
+</th>
+<th width="75">
+<Text id="131">0.0012</Text>
+</th>
+<th width="83">
+<Text id="132">0.0048$</Text>
+</th>
+<th width="60">
+<Text id="133">50 000$</Text>
+</th>
+<th width="66">
+<Text id="134">8 000 000</Text>
+</th>
+<th width="85">
+<Text id="135">833 000</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<br/>
+<Text id="136">Le prix par page s'obtient en multipliant le coÃ»t salarial horaire global dans votre cas par la deuxiÃšme colonne du tableauÂ <CrossRef target="Table" ref="table_scanning_cost"/>. Nous avons donnÃ© en exemple, dans la troisiÃšme colonne, le prix d'une numÃ©risation faite sur place avec un coÃ»t salarial de 4$ par heureÂ --Â ce qui ne comprend pas le coÃ»t des investissements.</Text>
+<Text id="137">Ces calculs supposent que le scanner est utilisÃ© pour un volume suffisant, justifiant l'investissement. Les trois derniÃšres colonnes du tableau <CrossRef target="Table" ref="table_scanning_cost"/>Â fournissent plus d'informations sur le coÃ»t du scanner Ã  proprement parler. La premiÃšre montre le coÃ»t d'achat du scanner, et la deuxiÃšme fournit sa durÃ©e de vie moyenne. La derniÃšre colonne montre le nombre de pages qu'on pourrait faire numÃ©riser par un sous-traitant, au prix de 0.06$ par page, pour le prix du scanner seul.</Text>
+<Text id="138">Bien sÃ»r, de nombreux autres facteurs guident le choix du scanner: disponibilitÃ© des fonds, souhait d'indÃ©pendance, volontÃ© de dÃ©velopper un pÃŽle de compÃ©tences local, rÃšgles des bibliothÃšques imposant une numÃ©risation locale sans possibilitÃ© de transport des livres, etc.</Text>
+<Text id="139">Ces chiffres donnent une idÃ©e du volume de pages Ã  traiter pour justifier diffÃ©rents niveaux d'investissement. Un institut ou une organisation aura rarement besoin de numÃ©riser plus de 800Â 000 pages. Ã de tels niveaux, des paramÃštres plus complexes entrent en ligne de compteÂ --Â tels que la maintenance et la possibilitÃ© de rentabiliser l'investissement en revendant des services de numÃ©risationÂ --Â paramÃštres dont nous ne traiterons pas ici.</Text>
+<Text id="140">On peut Ãªtre sÃ©duit par l'idÃ©e de dÃ©velopper une activitÃ© commerciale de numÃ©risation, surtout dans les pays en voie de dÃ©veloppement. Mais gardez Ã  l'esprit que la numÃ©risation est une activitÃ© non rÃ©currente: une fois les documents numÃ©risÃ©s, les clients ne passeront jamais une autre commande pour la numÃ©risation des mÃªmes documents, mÃªme si les relations sont excellentes. D'un point de vue commercial, il faut prÃ©voir d'intenses efforts de mercatique. Nous dÃ©conseillons aux ONG et aux autres organisations Ã  but non lucratif de s'aventurer dans un tel projet sans essais liminaires trÃšs complets et un projet financier extrÃªmement rÃ©flÃ©chi.</Text>
+<Text id="141">En conclusion, on peut dire qu'il vaut mieux sous-traiter si la quantitÃ© de pages Ã  numÃ©riser s'Ã©tale de 10 Ã  50Â 000 pages. Un scanner professionnel de bas de gamme, coÃ»tant environ 6000$, ne se justifie que s'il faut numÃ©riser plus de 100Â 000 pages. On peut aussi envisager une association de plusieurs institutions (telles que des ONG ou des bibliothÃšques) pour l'achat groupÃ© d'une telle machine.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="ocr">
+<Title>
+<Text id="142">ROC: reconnaissance optique de caractÃšres</Text>
+</Title>
+<Content>
+<Text id="143">Un systÃšme de reconnaissance optique de caractÃšres, ou ROC, transforme une image numÃ©risÃ©e en texte. Il accepte en entrÃ©e une image numÃ©rique au format TIFF ou bitmap, de prÃ©fÃ©rence propre et de bonne qualitÃ©. Il fournit en sortie un fichier de traitement de texte ou pour le web, aux formats RTF, Word, ou HTML.</Text>
+<Text id="144">La conversion de documents papier sous forme Ã©lectronique est un processus en quatre Ã©tapes:</Text>
+<BulletList>
+<Bullet>
+<Text id="145">numÃ©risation; </Text>
+</Bullet>
+<Bullet>
+<Text id="146">analyse de la mise en page;</Text>
+</Bullet>
+<Bullet>
+<Text id="147">reconnaissance;</Text>
+</Bullet>
+<Bullet>
+<Text id="148">numÃ©risation des images et des tableaux.</Text>
+</Bullet>
+</BulletList>
+<Text id="149">En suivant ces Ã©tapes, il faut effectuer des contrÃŽles qualitÃ© sur les fichiers produits, et les sauvegarder dans le format appropriÃ©.</Text>
+<Text id="150">On trouve beaucoup de bons programmes de ROC sur le marchÃ©, et leurs prix varient de 100 Ã  400$<FootnoteRef id="2"/>. On trouve par exemple, entre (nombreux) autres:</Text>
+
+<BulletList>
+<Bullet>
+<Text id="151">Read-Iris (http://www.readiris.com/)</Text>
+</Bullet>
+<Bullet>
+<Text id="152">Omnipage (http://www.omnipage.com/)</Text>
+</Bullet>
+<Bullet>
+<Text id="153">Fine-Reader (http://www.finereader.com/) </Text>
+</Bullet>
+</BulletList>
+<Text id="154">Les sites web des Ã©diteurs vous fourniront toutes les informations nÃ©cessaires, y compris la liste des revendeurs dans votre rÃ©gion. L'expÃ©rience des auteurs les amÃšne Ã  recommander pour leur bonne ergonomie les programmes Fine-Reader et Omnipage. Fine-Reader est le moins cher, Ã  environ 100$. Il est trÃšs souple, et a les options de langue les plus variÃ©es.</Text>
+<Text id="155">Il faut choisir entre effectuer la numÃ©risation et la ROC sur place, ou sous-traiter ces opÃ©rations Ã  une organisation spÃ©cialisÃ©e. Un travail sur place nÃ©cessite un scanner, un logiciel de ROC, des compÃ©tences en ROC (donc des formations), et des opÃ©rateurs soucieux de qualitÃ© et extrÃªmement motivÃ©s.</Text>
+<Section id="the_ocr_process">
+<Title>
+<Text id="156">Le processus de ROC</Text>
+</Title>
+<Content>
+<Text id="157">Le processus de ROC change d'un programme Ã  l'autre, et chacun est trÃšs long Ã  apprendre et Ã  maÃ®triser. Le manuel du logiciel expliquera ce processus en dÃ©tail. Quatre aspects mÃ©ritent qu'on leur accorde une attention particuliÃšre: le contrÃŽle qualitÃ©, les tableaux, les images, et les contenus spÃ©cialisÃ©s tels que formules, caractÃšres d'autres alphabets ou langues, etc.</Text>
+<Subsection id="quality_control_1">
+<Title>
+<Text id="158">ContrÃŽle qualitÃ©</Text>
+</Title>
+<Content>
+<Text id="159">On n'insistera jamais assez sur ce point. Il vaut mieux faire mener ces contrÃŽles qualitÃ© par des locuteurs dont la langue traitÃ©e est la langue maternelle, ou des gens maÃ®trisant parfaitement cette langue. Les meilleurs candidats se recruteront Ã  l'universitÃ© ou au lycÃ©e. Remarquons que des relecteurs plus jeunes seront capables d'une concentration plus soutenue pour ce type de travail.</Text>
+<Text id="160">On compte normalement quatre contrÃŽles qualitÃ©.</Text>
+<Text id="161">Le premier est effectuÃ© au moment de la ROC. Tout programme de ROC dispose d'un vÃ©rificateur orthographique intÃ©grÃ© qui met en valeur toutes les lettres suspectes. Il affiche en mÃªme temps l'image du mot concernÃ©, ce qui facilite le travail de vÃ©rification et de correction de l'erreur.</Text>
+<Text id="162">Le deuxiÃšme est une vÃ©rification globale du texte Ã  la fin du processus de ROC. Il arrive souvent d'oublier une page, un paragraphe, un titre de chapitre, etc. Un examen global est nÃ©cessaire pour dÃ©tecter d'Ã©ventuelles pages manquantes. Il est essentiel de vÃ©rifier les titres, les en-tÃªtes de chapitres, les paragraphes, et les tableaux.</Text>
+<Text id="163">Le troisiÃšme est une vÃ©rification orthographique utilisant Microsoft Word: ce programme dispose en effet d'un dictionnaire souvent plus sophistiquÃ© que ceux qui sont embarquÃ©s dans les programmes de ROC. En important le livre dans Word et en y effectuant une vÃ©rification orthographique, on peut trouver et corriger des erreurs supplÃ©mentaires. Veillez Ã  enseigner au vÃ©rificateur orthographique tous les mots particuliÃšrement difficiles ou sujets Ã  erreurs, ou encore les termes scientifiques et techniques communs dans le type de publication considÃ©rÃ©.</Text>
+<Text id="164">Enfin, le document complet devrait Ãªtre vÃ©rifiÃ© par un relecteur indÃ©pendant, qui en extrait des Ã©chantillons et contrÃŽle l'absence d'erreurs, de problÃšmes avec les tableaux et les images, la typographie, et l'aspect gÃ©nÃ©ral du texte rÃ©sultant. Ce n'est qu'aprÃšs cette Ã©tape qu'un livre peut Ãªtre dÃ©clarÃ© apte Ã  la dissÃ©mination numÃ©rique.</Text>
+</Content>
+</Subsection>
+<Subsection id="tables">
+<Title>
+<Text id="165">Tableaux</Text>
+</Title>
+<Content>
+<Text id="166">Les programmes de ROC peinent Ã  traiter les tableaux. De plus, il est difficile de les vÃ©rifier: ils contiennent de nombreux chiffres, souvent avec des espaces, points ou virgules, et il est aisÃ© de dÃ©caler des cellules d'une ligne ou d'une colonne. Il leur faut un effort de concentration particulier et une relecture obstinÃ©e et intense, une vÃ©rification soigneuse, et un bon contrÃŽle qualitÃ©. On peut les traiter de trois maniÃšres extrÃªmement diffÃ©rentes.</Text>
+<Text id="167">D'abord, les tableaux peuvent Ãªtre traitÃ©s en tant qu'images. Cela implique de les numÃ©riser sous forme d'image noir et blanc et de les placer au bon endroit dans le document rÃ©sultant. C'est la solution la plus facile: aucun risque d'erreur, et le temps nÃ©cessaire est uniquement celui de la crÃ©ation de l'image. Cependant, cette solution est plus gourmande en mÃ©moire. Un autre problÃšme concerne la rÃ©solution, pas toujours suffisante lorsqu'il faut afficher de grands tableaux sur un Ã©cran d'ordinateur: si on affiche tout le tableau, il est illisible, et si on agrandit l'image (en la faisant sortir de l'Ã©cran) pour la rendre lisible, l'utilisateur doit s'y dÃ©placer pour pouvoir en lire toutes les lignes et colonnes, et manque d'une vue d'ensemble.</Text>
+<Text id="168">Ensuite, les tableaux peuvent Ãªtre recrÃ©Ã©s manuellement en crÃ©ant une table comptant le mÃªme nombre de lignes et de colonnes et en tapant les cellules une Ã  une, caractÃšre par caractÃšre.</Text>
+<Text id="169">Enfin, le tableau peut passer Ã  la ROC. C'est plus rapide que la saisie manuelle, mais prÃ©sente un plus grand risque d'erreurs. Les colonnes sont parfois fusionnÃ©es, et les points et les virgules ne sont pas bien reconnus.</Text>
+</Content>
+</Subsection>
+<Subsection id="images">
+<Title>
+<Text id="170">Images</Text>
+</Title>
+<Content>
+<Text id="171">Les publications contiennent trois grands types d'images diffÃ©rents:</Text>
+<BulletList>
+<Bullet>
+<Text id="172">croquis en noir et blanc;</Text>
+</Bullet>
+<Bullet>
+<Text id="173">photographies en noir et blanc;</Text>
+</Bullet>
+<Bullet>
+<Text id="174">photographies en couleurs.</Text>
+</Bullet>
+</BulletList>
+<Text id="175">Les croquis noir et blanc se numÃ©risent en mode Â«croquisÂ» et seront sauvegardÃ©s au format GIF ou PNG. Les photographies noir et blanc se numÃ©risent en mode Â«niveaux de grisÂ» et seront sauvegardÃ©es au format GIF ou JPEG. Les photographies couleur se numÃ©risent en mode Â«couleurÂ» et seront sauvegardÃ©es au format JPEG. Dans la plupart des cas, le JPEG de qualitÃ© moyenne fournit une rÃ©solution suffisante.</Text>
+<Text id="176">Pour la plupart des collections, ce sont les images qui consomment le plus de place sur le disque dur ou sur le cÃ©dÃ©rom. C'est pourquoi il est important d'optimiser chaque image du point de vue de la clartÃ© et de la lisibilitÃ©, tout en minimisant sa taille. Vous Ã©conomiserez de l'espace disque en nÃ©gligeant de reprendre tout ou partie des images, de prÃ©fÃ©rence celles qui ne sont pas pertinentes par rapport au texte.</Text>
+<Text id="177">Il faut numÃ©riser les images sÃ©parÃ©ment, une Ã  une. Nous vous recommandons de donner aux fichiers image un nom consistant en les 5 ou 6 premiers caractÃšres utilisÃ©s pour identifier le document, suivis du numÃ©ro de page oÃ¹ apparaÃ®t l'image. Une autre solution, dans l'hypothÃšse oÃ¹ chaque document dispose de son propre rÃ©pertoire, est de se contenter d'utiliser la lettre p, suivie du numÃ©ro de page de l'image. Si plusieurs images apparaissent sur la mÃªme page, on ajoutera au nom de fichier une lettre supplÃ©mentaire: a, b, c... Si par exemple une image JPEG apparaÃ®t page 36 de la publication u7548f ci-dessus Ã©voquÃ©e, elle sera placÃ©e dans un fichier appelÃ© u7548e36.jpg ou p36.jpg.</Text>
+<Text id="178">AprÃšs la numÃ©risation des images, on peut mettre au travail les programmes de traitement par lots (batch), afin de changer les tailles ou d'amÃ©liorer la qualitÃ© de toutes les images en une seule passe.</Text>
+</Content>
+</Subsection>
+<Subsection id="specialized_material">
+<Title>
+<Text id="179">Contenus spÃ©cialisÃ©s</Text>
+</Title>
+<Content>
+<Text id="180">De nombreux documents renferment des contenus spÃ©cialisÃ©s tels que des caractÃšres spÃ©ciaux, des formules, ou des pages difficiles. Les caractÃšres spÃ©ciaux sont souvent issus de langues Ã©trangÃšres ou pourvus de signes diacritiques. Il faut alors utiliser l'option de langue du programme de ROC utilisÃ© et lui indiquer la langue Ã  reconnaÃ®tre. Les formules devront Ãªtre recrÃ©Ã©es manuellement. Parfois cette opÃ©ration n'est pas possible dans le programme de ROC, et uniquement faisable dans un traitement de texte tel que Microsoft Word. Les pages difficiles, au contenu complexe ou si endommagÃ©es qu'on n'a pas pu en obtenir une image nette lors du processus de numÃ©risation, devront parfois Ãªtre retapÃ©es.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="productivity_and_resources_1">
+<Title>
+<Text id="181">De la productivitÃ© et des ressources nÃ©cessaires</Text>
+</Title>
+<Content>
+<Text id="182">Comme on l'a dÃ©jÃ  signalÃ©, il ne faut pas sous-estimer la difficultÃ© du processus de ROC. MÃªme si ses aspects Ã©conomiques et pratiques doivent Ãªtre traitÃ©s indÃ©pendamment de ceux relevant de la numÃ©risation, on trouve des points communs: le nÃ©cessaire investissement en ordinateurs; la disponibilitÃ© en ressources humaines et leur encadrement; la formation des opÃ©rateurs; les coÃ»ts salariaux; le nombre total de pages Ã  traiter; et la possibilitÃ© de sous-traiter des documents.</Text>
+<Text id="183">Dans cette section, nous faisons partager notre expÃ©rience d'opÃ©rations de ROC en Belgique, en Roumanie et en Inde. Toutes les Ã©tudes de cas, les calculs et les chiffres prÃ©sentÃ©s font les hypothÃšses implicites de situations moyennes et de documents de difficultÃ© standard (incluant images et tableaux) tels qu'on en trouve dans la plupart des archives et des bibliothÃšques, des rÃ©sultats de trÃšs bonne qualitÃ©, et une opÃ©ration Ã  moyen ou long terme.</Text>
+<Subsection id="intensive_ocr">
+<Title>
+<Text id="184">La ROC intensive</Text>
+</Title>
+<Content>
+<Text id="185">La ROC est une activitÃ© difficile, qui requiert une grande concentration et beaucoup de compÃ©tences. Avant d'atteindre une productivitÃ© et une qualitÃ© de croisiÃšre, il faut prÃ©voir une pÃ©riode d'apprentissage d'environ six semaines.</Text>
+<Text id="186">Les premiÃšres heures de chaque jour sont souvent les plus fructueuses en matiÃšre de rÃ©sultats et de productivitÃ©. AprÃšs trois heures de travail de ROC, la productivitÃ© dÃ©croÃ®t trÃšs rapidement, jusqu'Ã  50% du niveau initial. AprÃšs six heures de travail, la plupart des gens sont trÃšs fatiguÃ©s.</Text>
+<Text id="187">La mÃªme courbe se dessine au niveau supÃ©rieur, celui des semaines. Les premiÃšres semaines, tout le monde travaille vite et bien, mais vient un moment oÃ¹ les deux tiers des agents s'ennuient et deviennent frustrÃ©s. Ces personnes abandonnent le projet ou se mettent Ã  travailler de faÃ§on mÃ©diocre, en quantitÃ© comme en qualitÃ©. MÃªme ceux qui passent le cap critique des 3 ou 5 semaines de travail et intÃšgrent l'Ã©quipe, partent souvent aprÃšs 6 Ã  12 mois, Ã  la recherche d'un meilleur poste.</Text>
+<Text id="188">Les remarques de la sectionÂ Section <CrossRef target="Section" ref="the_ocr_process"/> concernant le personnel sont particuliÃšrement avÃ©rÃ©es dans le cadre d'un travail de ROC intensif. Il vaut mieux faire mener les contrÃŽles qualitÃ© par des locuteurs dont la langue traitÃ©e est la langue maternelle, ou des gens maÃ®trisant parfaitement cette langue. Des relecteurs plus jeunes seront capables d'une concentration plus soutenue pour des tÃ¢ches de ROC. Empiriquement, on a constatÃ© que des personnes Ã¢gÃ©es de 18 Ã  23 ans convenaient mieux que des personnes de plus de 25 ans.</Text>
+<Text id="189">Enfin, la ROC peut Ãªtre un travail fastidieux, ce qui donne une importance exceptionnelle aux questions de motivation et de goÃ»t du travail bien fait.</Text>
+<Text id="190">Ces remarques sur la ROC mÃšnent aux prÃ©ceptes suivants:</Text>
+<BulletList>
+<Bullet>
+<Text id="191">Les jeunes gens Ã¢gÃ©s de 18 Ã  25 ans sont les plus indiquÃ©s pour ce travail.</Text>
+</Bullet>
+<Bullet>
+<Text id="192">Les premiÃšres heures Ã©tant toujours les plus productives, il faut organiser le travail Ã  temps partiel ou ne retenir que les gens les plus motivÃ©s et concentrÃ©s pour un travail Ã  temps plein.</Text>
+</Bullet>
+<Bullet>
+<Text id="193">Les deux tiers des gens abandonnent ou s'ennuient aprÃšs trois Ã  cinq semaines, ce qui se traduit par une qualitÃ© et une productivitÃ© en baisse les derniÃšres semaines.</Text>
+</Bullet>
+<Bullet>
+<Text id="194">Il faut veiller Ã  fournir un travail rÃ©gulier pour justifier la formation nÃ©cessaire, pour maintenir la concentration, et pour que restent hauts les c3#3urs.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="achievable_productivity">
+<Title>
+<Text id="195">ProductivitÃ© possible</Text>
+</Title>
+<Content>
+<Table id="table_ocr_productivity">
+<Title>
+<Text id="196">ProductivitÃ© de l'OCR</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="161"/>
+<th width="142">
+<Text id="197">Heures travaillÃ©es par jour</Text>
+</th>
+<th width="123">
+<Text id="198">Pages par jour</Text>
+</th>
+<th width="104">
+<Text id="199">Pages par mois</Text>
+</th>
+</tr>
+<tr>
+<th width="161">
+<Text id="200">Formation initiale (6 semaines)</Text>
+</th>
+<th width="142">
+<Text id="201">3</Text>
+</th>
+<th width="123">
+<Text id="202">6</Text>
+</th>
+<th width="104">
+<Text id="203">120</Text>
+</th>
+</tr>
+<tr>
+<th width="161">
+<Text id="204">Niveau de productivitÃ© optimale</Text>
+</th>
+<th width="142">
+<Text id="205">3</Text>
+</th>
+<th width="123">
+<Text id="206">9</Text>
+</th>
+<th width="104">
+<Text id="207">150 Ã  200</Text>
+</th>
+</tr>
+<tr>
+<th width="161"/>
+<th width="142">
+<Text id="208">7</Text>
+</th>
+<th width="123">
+<Text id="209">28</Text>
+</th>
+<th width="104">
+<Text id="210">500 Ã  600</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="211">Le tableauÂ <CrossRef target="Table" ref="table_ocr_productivity"/> donne les statistiques moyennes de productivitÃ© pour la ROC. Les documents sont de toutes tailles et de toutes qualitÃ©s, et ces chiffres supposent que le lot de documents contient un nombre moyen d'images et de tableauxÂ --Â disons une image et une tableau de 5 lignes par 5 colonnes toutes les 8 pages. Ils supposent aussi que les images des pages sont de qualitÃ© moyenne Ã  bonne (comme on l'a dÃ©jÃ  signalÃ©, ceci dÃ©pend de la numÃ©risation) et que les opÃ©rateurs maÃ®trisent bien la langue.</Text>
+<Text id="212">Le tableauÂ <CrossRef target="Table" ref="table_ocr_productivity"/> distingue les cas des opÃ©rateurs en formation et celui des opÃ©rateurs ayant atteint leur niveau de productivitÃ© optimal. Si un agent administratif devait passer 3 heures par jour Ã  des activitÃ©s de ROC, il pourrait produire 180 Ã  200 pages par mois. Dans le cas de personnel employÃ© Ã  temps plein, ayant reÃ§u une formation adÃ©quate, avec une concentration Ã©levÃ©e et un goÃ»t du travail bien fait, on peut obtenir de 500 Ã  600 pages par mois.</Text>
+<Text id="213">Cependant, les taux obtenus sur des pages difficiles, de qualitÃ© mÃ©diocre, contenant beaucoup d'images ou de tableaux, sont bien plus faiblesÂ --Â peut-Ãªtre de 300 Ã  400 pages par mois pour un travail Ã  temps plein.</Text>
+<Text id="214">Supposons que les coÃ»ts salariaux d'opÃ©rateurs de ROC motivÃ©s et soucieux de qualitÃ© travaillant Ã  temps plein s'Ã©lÃšvent Ã  400$ par mois, et que les frais d'infrastructure (comprenant les coÃ»ts d'encadrement, les ordinateurs, les bureaux, les fournitures, etc.) s'Ã©lÃšvent Ã  300 Ã  400$ par personne et par mois. Alors le coÃ»t de la ROC est de 1.2$ Ã  1.6$ par page. Si on prend en compte le temps de formation, le volume total, la durÃ©e de l'opÃ©ration, et les coÃ»ts de licenciement si l'opÃ©ration devait prendre fin par manque de travail, ces coÃ»ts atteignent 1.5$ Ã  2.5$ par page.</Text>
+<Text id="215">Il faut comparer le coÃ»t d'une ROC menÃ©e sur place Ã  celui d'une ROC sous-traitÃ©e Ã  un professionnel. De telles sociÃ©tÃ©s demandent en gÃ©nÃ©ral de 1.5$ Ã  4$ par page, en comptant les images et les tableaux. L'ONG Human Info/Simple Words dispose d'une telle unitÃ© en Roumanie, et pratique un tarif spÃ©cial pour les organisations humanitaires ou Ã  but non lucratifs: de 1.2$ Ã  2$ par page. Contactez-nous Ã  l'adresse Ã©lectronique si vous souhaitez obtenir des informations ou des conseils complÃ©mentaires.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="alternatives_to_ocr">
+<Title>
+<Text id="216">Pour Ã©viter la ROC</Text>
+</Title>
+<Content>
+<Text id="217">Il existe deux solutions qui permettent d'Ã©viter la ROC, et nous les prÃ©sentons toutes deux ici.</Text>
+<Subsection id="manual_retyping">
+<Title>
+<Text id="218">Saisie manuelle</Text>
+</Title>
+<Content>
+<Text id="219">La premiÃšre, qui Ã©limine Ã©galement la plupart des opÃ©rations de numÃ©risation, consiste Ã  retaper les documents Ã  la main, en utilisant un traitement de texte. Il faut quand mÃªme numÃ©riser la couverture et les images, mais les autres pages n'ont pas besoin d'Ãªtre numÃ©risÃ©es, ce qui Ã©vite l'achat d'un scanner puissant et de logiciels de ROC.</Text>
+<Text id="220">Les opÃ©rateurs n'ont pas besoin de comprendre le texte: il leur suffit d'Ãªtre des dactylographes prÃ©cis, qui tapent exactement ce qu'ils voient. La saisie gÃ©nÃšre des erreurs, qu'on trouve et dÃ©tecte par la mÃ©thode dite de double saisie. Elle consiste Ã  demander Ã  deux personnes de saisir le mÃªme document indÃ©pendamment, suite Ã  quoi on comparer les deux versions numÃ©riques mot Ã  mot Ã  l'aide d'un logiciel spÃ©cial manipulÃ© par un opÃ©rateur disposant du document original. On suppose implicitement qu'un mot tapÃ© indÃ©pendamment deux fois de la mÃªme maniÃšre est nÃ©cessairement correct. Mais cela ne suffit pas toujours, et on peut avoir recours Ã  de la triple saisie pour obtenir une prÃ©cision extrÃªmement Ã©levÃ©e.</Text>
+<Text id="221">L'avantage de la saisie est l'Ã©conomie effectuÃ©e: nul besoin d'un programme de ROC (qui nÃ©cessite des ordinateurs puissants), aussi des ordinateurs plus anciens, ou d'occasion peuvent suffire. De plus, ce travail peut Ãªtre menÃ© par des personnes moins qualifiÃ©es. L'inconvÃ©nient est la durÃ©e de la pÃ©riode de formation (d'un minimum de deux mois). Une simple saisie induisant souvent trop d'erreurs, il faut procÃ©der Ã  une double ou Ã  une triple saisie.</Text>
+<Text id="222">Le coÃ»t dÃ©pend entiÃšrement du salaire. Les dactylos sont gÃ©nÃ©ralement payÃ©es environ 150$ par mois dans les pays en voie de dÃ©veloppement. La productivitÃ© est de 20 Ã  30 pages par jour, pour un total de 400 pages par mois, en comptant les images. Avec une double saisie, cela donne un coÃ»t de revient salarial d'environ 300$ par mois, plus les Ã  cÃŽtÃ©s.</Text>
+</Content>
+</Subsection>
+<Subsection id="image_files">
+<Title>
+<Text id="223">Fichiers image</Text>
+</Title>
+<Content>
+<Text id="224">Une solution de remplacement Ã  la ROC trÃšs peu onÃ©reuse est de se contenter d'utiliser une version image PDF des pages du document. Le coÃ»t est nÃ©gligeable devant celui de la ROCÂ --Â environ 0.1$ par page.</Text>
+<Text id="225">Ã l'issue du processus de numÃ©risation et une fois que les fichiers TIFF sont disponibles, un convertisseur automatique (on utilise en gÃ©nÃ©ral Adobe Acrobat ou Adobe Photoshop) transforme tous les fichiers TIFF des pages du livre en fichiers PDF.</Text>
+<Text id="226">Le revers de la mÃ©daille est l'impossibilitÃ© de mener des recherches textuelles dans de tels fichiers. De plus, ils sont trÃšs lourds: environ 50 kilo-octets par page, plus ou moins 20% selon la qualitÃ© du fichier TIFF original.</Text>
+<Text id="227">Les fichiers image PDF sont lents Ã  tÃ©lÃ©charger (parfois, dans les pays en voie de dÃ©veloppement, cette opÃ©ration est impossible ou a un coÃ»t prohibitif). Ils tiennent rarement sur une disquette, et il est impossible de manipuler leur texte, ne serait-ce que pour effectuer des copier-coller.</Text>
+<Text id="228">Il faut rÃ©server cette mÃ©thode aux situations oÃ¹ aucun budget ne peut Ãªtre dÃ©bloquÃ© pour la ROC, et pour les documents susceptibles d'Ãªtre utilisÃ©s par un petit nombre de personnes, disposant d'une connexion Internet Ã  haut dÃ©bit.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="combining_scanning_and_ocr">
+<Title>
+<Text id="229">Mettre bout Ã  bout numÃ©risation et ROC</Text>
+</Title>
+<Content>
+<Text id="230">Si un scanner est directement reliÃ© Ã  l'ordinateur qui hÃ©berge le logiciel de ROC, la plupart des programmes de ROC peuvent numÃ©riser une page et effectuer immÃ©diatement la reconnaissance de caractÃšres. ProcÃ©der une page Ã  la fois, en enchaÃ®nant numÃ©risation puis ROC, est une stratÃ©gie raisonnable pour des petits volumes, mais s'avÃ©rera coÃ»teux en temps pour des tÃ¢ches plus importantes et plus continues.</Text>
+<Text id="231">Cette solution peut suffire pour 100 Ã  150 pages par mois. Pour des volumes plus Ã©levÃ©s il est plus rapide et plus efficace de commencer par numÃ©riser le document, puis de dÃ©marrer en deuxiÃšme lieu une opÃ©ration de ROC sur toutes ses pages Ã  la fois.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="three_examples">
+<Title>
+<Text id="232">Trois exemples: de 1000 Ã  100 000 pages</Text>
+</Title>
+<Content>
+<Section id="typical_small_collection">
+<Title>
+<Text id="233">Cas d'une petite collection: de 500 Ã  1000 pages</Text>
+</Title>
+<Content>
+<Text id="234">La plupart des ONG ont un volume de 500 Ã  1000 pages Ã  numÃ©riser. Un tel volume peut Ãªtre traitÃ© sur place si on trouve des volontaires motivÃ©s.</Text>
+<Subsection id="scanning">
+<Title>
+<Text id="235">NumÃ©risation</Text>
+</Title>
+<Content>
+<Text id="236">La premiÃšre Ã©tape consiste Ã  numÃ©riser les publications pour produire un fichier TIFF de bonne qualitÃ© de chaque page, et une image sÃ©parÃ©e pour chaque illustration (croquis, image en niveaux de gris ou en couleurs). Si on fait l'hypothÃšse que 1000 pages doivent Ãªtre numÃ©risÃ©es, ceci peut reprÃ©senter un travail Ã  temps partiel d'environ un moisÂ --Â pour la numÃ©risation seule. Les fichiers TIFF occuperont de 60 Ã  80 mÃ©ga-octets d'espace disque, et c'est une bonne idÃ©e que de graver un cÃ©dÃ©rom rÃ©inscriptible contenant ces fichiers. Un scanner Ã  plat de bas de gamme de 100 Ã  300$ suffira Ã  mener cette tÃ¢che de numÃ©risation Ã  bien. La numÃ©risation peut Ãªtre prise en charge par un volontaire, aprÃšs les heures de bureau ou les jours non ouvrÃ©s, au bureau ou Ã  la maison.</Text>
+</Content>
+</Subsection>
+<Subsection id="ocr">
+<Title>
+<Text id="237">ROC</Text>
+</Title>
+<Content>
+<Text id="238">La ROC, menÃ©e par un autre volontaire ou par une Ã©quipe de volontaires, douÃ©s en langue et en correction, vient ensuite. Les fichiers TIFF peuvent Ãªtre partagÃ©s entre ordinateurs, ou bien on peut utiliser un seul ordinateur pour l'ensemble du travail. Il faudra en moyenne de 5 Ã  6 mois Ã  temps partiel (par exemple, environ 20 heures par semaine) pour convertir 1000 pages en bons documents Word ou HTML.</Text>
+</Content>
+</Subsection>
+<Subsection id="outsourcing">
+<Title>
+<Text id="239">Sous-traiter</Text>
+</Title>
+<Content>
+<Text id="240">On peut aussi envisager de sous-traiter les opÃ©rations de numÃ©risation et de ROC. Il en coÃ»tera probablement de 1500 Ã  2000$ pour tout convertir en bons fichiers Word ou HTML.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="all_publications_from_an_organization">
+<Title>
+<Text id="241">Toutes les publications d'une organisation: 5000 pages</Text>
+</Title>
+<Content>
+<Text id="242">De nombreuses organisations plus importantes disposent d'environ 5000 pages d'archives de livres, journaux, revues, et autres documents, actuels ou Ã©puisÃ©s.</Text>
+<Subsection id="scanning_1">
+<Title>
+<Text id="243">NumÃ©risation</Text>
+</Title>
+<Content>
+<Text id="244">VoilÃ  un volume trop important pour un scanner Ã  plat. La numÃ©risation doit donc Ãªtre sous-traitÃ©e (ce qui coÃ»tera environ 400$ pour 5000 pages) ou confiÃ©e Ã  un scanner Ã  chargeur (qui coÃ»te environ 900$). On peut aussi envisager l'achat groupÃ© d'un scanner plus performant, avec d'autres institutions ou ONG (il en coÃ»tera 6000$, Ã  diviser par le nombre de participants). Les 5000 pages converties au format TIFF occuperont 300 Ã  400 mÃ©ga-octets d'espace disque. LÃ  encore, c'est une bonne idÃ©e de graver un cÃ©dÃ©rom rÃ©inscriptible contenant ces fichiers.</Text>
+</Content>
+</Subsection>
+<Subsection id="ocr_1">
+<Title>
+<Text id="245">ROC</Text>
+</Title>
+<Content>
+<Text id="246">La ROC, menÃ©e par un volontaire ou par une Ã©quipe de volontaires, douÃ©s en langue et en correction, vient ensuite. Ici encore, les fichiers TIFF peuvent Ãªtre partagÃ©s entre ordinateurs, ou bien on peut utiliser un seul ordinateur pour l'ensemble du travail. Il faudra en moyenne de 25 Ã  30 mois Ã  temps partiel (par exemple, environ 20 heures par semaine) pour convertir 5000 pages en bons documents Word ou HTML. En pratique, c'est lÃ  une tÃ¢che trop longue et gourmande en ressources informatiques pour pouvoir fonctionner sur la base du volontariat. Il faudrait rÃ©munÃ©rer les volontaires, surveiller leurs performances et la qualitÃ© de leur travail, fournir l'espace adÃ©quat, etc., pour obtenir un travail finalisÃ© de bonne qualitÃ© dans des dÃ©lais raisonnables.</Text>
+<Text id="247">On peut aussi crÃ©er des fichiers image PDF, ce qui occupera de 300 Ã  400 mÃ©ga-octets d'espace disque, et sera plus difficile Ã  tÃ©lÃ©charger depuis l'Internet.</Text>
+</Content>
+</Subsection>
+<Subsection id="outsourcing_1">
+<Title>
+<Text id="248">Sous-traiter</Text>
+</Title>
+<Content>
+<Text id="249">On peut aussi envisager de sous-traiter les opÃ©rations de numÃ©risation et de ROC. Il en coÃ»tera probablement de 7500 Ã  10Â 000$ pour tout convertir en bons fichiers Word ou HTML.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="a_small_library">
+<Title>
+<Text id="250">Une petite bibliothÃšques: 100 000 pages</Text>
+</Title>
+<Content>
+<Text id="251">Des organisations plus importantes, des universitÃ©s, des gouvernements, et des bibliothÃšques spÃ©cialisÃ©es disposeront peut-Ãªtre de toute une bibliothÃšque Ã  numÃ©riserÂ --Â disons, 100Â 000 pages. La premiÃšre question Ã  se poser est celle des droits attachÃ©s aux publications: si elles ne sont pas placÃ©es ou tombÃ©es dans le domaine public, il faut obtenir des dÃ©tenteurs des droits l'autorisation explicite de les numÃ©riser. Pensez aussi Ã  vÃ©rifier si les fichiers ne sont pas dÃ©jÃ  disponibles sous forme numÃ©rique.</Text>
+<Subsection id="scanning_2">
+<Title>
+<Text id="252">NumÃ©risation</Text>
+</Title>
+<Content>
+<Text id="253">Le volume est trop important pour un scanner Ã  chargeur. Il faut donc sous-traiter la numÃ©risation (il en coÃ»tera 8000$ pour 100Â 000 pages) ou acheter un scanner plus performant en commun avec quelques autres institutions ou ONG (il en coÃ»tera 6000$, Ã  diviser par le nombre de participants). Les 100Â 000 pages converties au format TIFF occuperont 6 Ã  8 giga-octets d'espace disque. La meilleure idÃ©e est de graver une sÃ©rie de copies de ces fichiers sur cÃ©dÃ©rom rÃ©inscriptible.</Text>
+</Content>
+</Subsection>
+<Subsection id="ocr_2">
+<Title>
+<Text id="254">ROC</Text>
+</Title>
+<Content>
+<Text id="255">La ROC vient ensuite (on peut aussi penser Ã  crÃ©er des fichiers PDF pour des documents moins largement utilisÃ©s). Il faudra en moyenne de 500 Ã  700 mois Ã  temps partiel pour convertir 5000 pages en documents Word ou HTML. C'est une opÃ©ration impossible Ã  mener sur la base du volontariat, et il faut avoir une approche professionnelle.</Text>
+<Text id="256">On peut rÃ©duire les coÃ»ts en transformant les pages les moins frÃ©quemment utilisÃ©es (par exemple, les 80% les moins utilisÃ©s, ce qui reprÃ©sente 80Â 000 pages) en PDF, et ne transformer que les 20Â 000 pages restantes en Word et en HTML. Les fichiers PDF occuperont 6 Ã  8 giga-octets d'espace disque et seront plus difficiles Ã  tÃ©lÃ©charger sur l'Internet, mais ils ne coÃ»teront que 0.2$ par page Ã  faire produire par des professionnels (pour un coÃ»t total de 16Â 000$). S'il fallait faire crÃ©er 80Â 000 fichiers PDF Ã  partir de fichiers TIFF par des volontaires utilisant des programmes de conversion vers PDF tels qu'Adobe Acrobat, il faudrait prÃ©voir 10 Ã  20 mois de travail Ã  temps partiel sur un ordinateur puissant.</Text>
+</Content>
+</Subsection>
+<Subsection id="outsourcing_2">
+<Title>
+<Text id="257">Sous-traiter</Text>
+</Title>
+<Content>
+<Text id="258">On peut aussi envisager de sous-traiter le travail. Si on reste sur l'hypothÃšse de 80% des pages converties en PDF et les 20% les plus frÃ©quents en HTML, le coÃ»t du PDF s'Ã©lÃ©vera Ã  environ 16Â 000$ et celui du HTML de 30 Ã  40Â 000$, pour un budget global d'environ 50Â 000$. Si toutes les pages passaient Ã  la ROC, il en coÃ»terait de 150 Ã  200Â 000$ pour convertir toute la collection en fichiers Word et HTML. </Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="creating_an_electronic_collection">
+<Title>
+<Text id="259">CrÃ©er une collection Ã©lectronique</Text>
+</Title>
+<Content>
+<Text id="260">Quand on dÃ©cide de crÃ©er une collection, il faut garder Ã  l'esprit trois aspects importants. D'abord, il faut organiser la collection. Plus dense et complet sera le contenu, plus le besoin d'indexation et de systÃšmes de recherche puissants se fera sentir. De tels outils sont indispensables pour des collections de 3000 Ã  5000 pages ou plus. Ensuite, il faut donner la prioritÃ© aux besoins des utilisateurs finals. Identifiez le public ciblÃ© par la collection, et consultez-le rÃ©guliÃšrement. Enfin, le budget disponible tranchera tous les choix en matiÃšre de dÃ©veloppement ou raffinement.</Text>
+<Section id="methods_of_collection_building">
+<Title>
+<Text id="261">MÃ©thodes de construction de collections</Text>
+</Title>
+<Content>
+<Text id="262">On trouve de nombreux exemples d'excellents cÃ©dÃ©roms crÃ©Ã©s sur le modÃšle de la page web. Les documents HTML, PDF ou Word peuvent Ãªtre ajoutÃ©s et reliÃ©s au reste de la collection grÃ¢ce Ã  des liens hypertexte. La navigation est simple et attrayante grÃ¢ce aux liens hypertexte, aux cadres, aux mots-clefs, aux index, etc. De tels systÃšmes peuvent convenir pour des volumes de quelques milliers de pages, mais Ã  partir de 3000 ou 5000 pages ils atteindront leurs limites et il deviendra important de disposer d'une collection bien structurÃ©e et de fonctionnalitÃ©s de recherche puissantes. C'est lÃ  que Greenstone peut rendre service.</Text>
+<Text id="263">Le logiciel de bibliothÃšque numÃ©rique Greenstone crÃ©e une bibliothÃšque numÃ©rique structurÃ©e disposant d'un moteur de recherche trÃšs puissant. On peut indexer jusqu'Ã  150Â 000 pages sur un simple cÃ©dÃ©rom, et chaque cÃ©dÃ©rom peut se transformer en serveur web. Greenstone est un logiciel libre, disponible selon les termes de la licence publique gÃ©nÃ©rale de GNU.</Text>
+<Text id="264">Les manuels fournis dÃ©crivent la maniÃšre de confectionner des collections Greenstone. Il y a essentiellement trois faÃ§ons de crÃ©er des collections.</Text>
+
+<BulletList>
+<Bullet>
+<Text id="265">Le "Librarian Interface" (l'Interface BibliothÃ©caire)</Text>
+</Bullet>
+<Bullet>
+<Text id="266">Le "Collector" (Le collectionneur)</Text>
+</Bullet>
+<Bullet>
+<Text id="267">La crÃ©ation Ã  partir de la ligne de commande.</Text>
+</Bullet>
+</BulletList>
+<Text id="268">La premiÃšre est le "Librarian Interface" (l'Interface BibliothÃ©caire) dÃ©crit dans le "Guide de l'utilisateur de la bibliothÃšque numÃ©rique Greenstone" (Chapitre 3, "RÃ©aliser des collections Greenstone"). C'est un outil interactif fonctionnel dans la crÃ©ation des collections. Avec lui, on peut collecter des groupes de documents, importer ou assigner des mÃ©ta-donnÃ©es, et confectionner une collection Greenstone. La deuxiÃšme mÃ©thode est le sous-systÃšme "collectionneur", dÃ©crit au chapitre 4 du guide de l'utilisateur. C'est un outil plus ancien qui fournit une maniÃšre alternative de crÃ©er des collections de pages Web et autres documents. Il vous guide Ã  travers une sÃ©quence de pages Web conventionnelles qui exigent l'information requise. Il ne fournit cependant aucun moyen d'ajouter une mÃ©tadata aux documents et, parce que c'est une interface Web, il n'est vraiment pas adaptÃ© aux collections qui prennent plus que quelques minutes pour Ãªtre crÃ©Ã©es. La troisiÃšme mÃ©thode consiste Ã  exÃ©cuter directement, Ã  partir de la ligne de commande, les programmes de crÃ©ation de collections; elle figure dans le "Guide du dÃ©veloppeur de la collection Greenstone" (Chapitre 1). Elle offre plus de flexibilitÃ© dans l'exÃ©cution individuelle des programmes et dans la sauvegarde des rÃ©sultats intermÃ©diaires, hautement souhaitable pour les collections qui prennent des heures Ã  Ãªtre crÃ©Ã©es. La lecture du chapitre 2 du Developer's Guide s'avÃšre aussi nÃ©cessaire pour exploiter de faÃ§on optimale la puissance de Greenstone dans la confection des collections de pointe.</Text>
+<Text id="269">Une quatriÃšme mÃ©thode de crÃ©ation et d'Ã©dition du matÃ©riel associÃ© Ã  la collection existe; c'est un programme appelÃ© "The Collection Organizer" (Organisateur de la Collection). Cependant, sa fonctionnalitÃ© a Ã©tÃ© dÃ©passÃ©e par le "Librarian Interface" (l'Interface BibliothÃ©caire) mentionnÃ© ci-dessus. Ce document est dÃ©crit comme un leg sous le titre "Using the Organizer" (Utiliser l'organisateur).</Text>
+</Content>
+</Section>
+<Section id="getting_started_in_seven_steps_and_15_minutes">
+<Title>
+<Text id="270">Commencer en sept Ã©tapes et en 15 minutes</Text>
+</Title>
+<Content>
+<Text id="271">La meilleure faÃ§on d'apprÃ©hender et de sentir l'Interface BibliothÃ©caire est en fait de crÃ©er une bibliothÃšque par un petit test. Si vous disposez de 15 minutes on vous conseille de suivre ces Ã©tapes pour une meilleure comprÃ©hension de ces programmes.</Text>
+<Text id="272">Avant tout, vous installez Greenstone (Voir Le Guide d'installation de Greenstone) "The Greenstone intaller's Guide" qui comprend la collection de dÃ©monstration "Demo Collection" dans un format DLS et ses fichiers sources. Noter que si vous souhaitez ajouter Ã  la collection l'un quelconque des 140 documents de la collection DLS (au lieu seulement des 11 de la collection Demo de Greenstone), vous devez installer DLS comme un des modÃšles des bibliothÃšques Greenstone. Dans CProgram Filesgsdlcollect, comme d'ailleurs Demo, dans les sous-repertoires respectifs DLS et Demo. Si Greenstone avait dÃ©jÃ  Ã©tÃ© installÃ© sans la collection DLS et que vous souhaitez installer celle-ci, vous devez rÃ©insÃ©rer le Cd-rom de Greenstone et procÃ©der Ã  l'ajout de DLS. La dÃ©sinstallation de Greenstone n'est en aucun cas nÃ©cessaire.</Text>
+<Text id="273">Nous vous conseillons d'imprimer les instructions ci-dessous et de les suivre pas Ã  pas:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="274">DÃ©marrer le "Librarian Interface" (l'Interface BibliothÃ©caire) sous Windows en sÃ©lectionnant Greenstone Digital Library Ã  partir de la section Programmes du menu de DÃ©marrage et en sÃ©lectionnant "Librarian interface". Si vous utilisez Unix Ã  la place, il faut taper:</Text>
+<CodeLine>cd ~/gsdl cd gli ./gli.sh</CodeLine>
+<Text id="275">oÃ¹Â /gsdl est le rÃ©pertoire contenant votre systÃšme Greenstone.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="276">SÃ©lectionner "Nouveau" Ã  partir du menu "Fichier" dans la barre de menu horizontale placÃ©e en haut de la fenÃªtre. Lui donner un titre, par exemple "Ma premiÃšre collection" et mettre votre adresse Ã©lectronique et une description sommaire de la collection. Dans le menu "Baser cette collection sur", choisir "greenstone demo" (dÃ©monstration de greenstone) ou "Developement Library Subset" (le rÃ©sultat est le mÃªme parce que ces deux collections ont la mÃªme structure).</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="277">Ajouter des documents Ã  partir de la collection Demo (ou la collection DLS si elle est installÃ©e) Ã  votre nouvelle collection. Pour ce faire, double-cliquer sur le rÃ©pertoire des Collections Greenstone Ã  gauche du panneau, et double-cliquer sur la collection dÃ©sirÃ©e. Les documents qui s'y trouvent sont affichÃ©s en dessous. SÃ©lectionnez-en un, le faire glisser et le dÃ©poser dans le panneau de droite ("glisser-coller"). Celle-ci reprÃ©sente la collection en cours de crÃ©ation. Choisir plusieurs documents, les faire glisser un Ã  un Ã  l'intÃ©rieur, ou utiliser une sÃ©lection multiple de faÃ§on standard.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="278">Ajouter vos propres documents qui ne sont pas dans la collection Demo ou DLS. Fermer le rÃ©pertoire des collections Greenstone du panneau de gauche et double-cliquer sur le rÃ©pertoire "Local filespace". Naviguer vers le rÃ©pertoire qui contient des documents(c'est Ã  dire de petits fichiers Word et HTML). En faire glisser quelques-uns dans le panneau de droite pour les inclure dans votre collection.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="279">Ajouter des mÃ©ta-donnÃ©es aux documents de votre collection. Jusqu'Ã  prÃ©sent, l'exÃ©cution se dÃ©roulait sous le panneau "Gather", indiquÃ© par l'onglet "Gather" en-dessous de la barre de menu horizontale en haut de Windows. Cliquer sur l'onglet "Enrich" qui se trouve Ã  cÃŽtÃ©. Les documents dans votre collection apparaissent maintenant dans le panneau de gauche : cliquer sur l'un et examiner la mÃ©ta-donnÃ©e qui lui est associÃ©e dans la liste "ElÃ©ment ... Valeurs" en haut Ã  droite. Utiliser le panneau en-dessous pour changer les valeurs individuelles en sÃ©lectionnant l'Ã©lÃ©ment dÃ©sirÃ© et, soit choisir une valeur existante sur la liste, ou taper une nouvelle valeur dans la boÃ®te situÃ©e en bas. Ajouter les meta-donnÃ©es Titre, Organisation et Mot-clÃ© Ã  chacun de vos propres documents figurant sur la collection. AprÃšs la saisie de chaque valeur, il est nÃ©cessaire de cliquer sur "Ajouter" pour ajouter cette valeur Ã  la mÃ©ta-donnÃ©e.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="280">Cliquez l'onglet "CrÃ©er" pour quitter le mode "Enrich" et crÃ©er votre nouvelle collection. Cliquer sur l'onglet "CrÃ©er la Collection" en bas. Pendant que l'ordinateur Ã©labore la collection, vous recevrez en feedback un compte rendu sur ce qui est en cours d'exÃ©cution.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="281">En fin d'exÃ©cution, cliquer sur l'onglet Preview pour visualiser la collection Ã  partir du "Librarian Interface" (l'Interface BibliothÃ©caire). VÃ©rifier les titres a-z, organisations et comment lister pour vous assurer que vos documents ont Ã©tÃ© inclus dans la collection. En visitant votre page Web Greenstone, le constat est fait aussi que la collection a Ã©tÃ© installÃ©e parmi les collections de Greenstone.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="282">Tous les prix mentionnÃ©s reprÃ©sentent des dollars amÃ©ricains (USD) et sont donnÃ©s sur la base du marchÃ© en 2001.</Text>
+</Footnote>
+<Footnote id="2">
+<Text id="283">Rappel: tous les prix mentionnÃ©s reprÃ©sentent des dollars amÃ©ricains (USD) et sont donnÃ©s sur la base du marchÃ© en 2001.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/fr/User_fr.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/fr/User_fr.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/fr/User_fr.xml	(revision 13632)
@@ -0,0 +1,2474 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1"/>
+</Heading>
+<Title>
+<Text id="2">Guide de l'utilisateur de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Title>
+<Author>
+<Text id="3">Ian H. Witten, Stefan Boddie et John Thompson</Text>
+</Author>
+<Affiliation>
+<Text id="4">DÃ©partement d'informatique,<br/>UniversitÃ© de Waikato, Nouvelle-ZÃ©lande</Text>
+</Affiliation>
+<Comment>
+<Text id="5">Greenstone est une suite logicielle destinÃ©e Ã  la construction et Ã  la distribution de collections de bibliothÃšques numÃ©riques. Cette suite fournit une nouvelle maniÃšre d'organiser l'information et de la publier sur l'Internet ou sur un cÃ©dÃ©rom. Greenstone est produit par le projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande (dÃ©pendant de l'universitÃ© de Waikato), et distribuÃ© en coopÃ©ration avec l'UNESCO et le projet de bibliothÃšques pour l'humanitÃ©. C'est un logiciel Open Source, qu'on peut obtenir Ã  l'URLhttp://greenstone.org, et qui est diffusÃ© selon les termes de la licence publique gÃ©nÃ©rale de GNU.</Text>
+<Text id="6">Nous souhaitons nous assurer que ce logiciel fonctionne bien pour vous.<br/>Faites-nous part, en anglais, de tout problÃšme Ã  l'adresse Ã©lectronique<br/>.</Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.70</Text>
+</Version>
+<Date>
+<Text id="8">Mars 2006</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">Ã propos de ce manuel</Text>
+</Title>
+<Content>
+<Text id="10">Ce manuel fournit une description complÃšte de la maniÃšre d'utiliser le logiciel Greenstone pour accÃ©der Ã  et construire des collections de bibliothÃšques numÃ©riques.</Text>
+<Text id="11">La sectionÂ <CrossRef target="Chapter" ref="overview_of_greenstone"/> donne une vue d'ensemble des possibilitÃ©s du logiciel. La sectionÂ <CrossRef target="Chapter" ref="using_greenstone_collections"/> explique comment utiliser les collections de Greenstone. L'interface parle d'elle-mÃªmeÂ --Â la meilleure faÃ§on d'apprendre est d'essayerÂ --Â et cette section correspond aux informations d'aide en ligne fournies pour une collection typique. La sectionÂ <CrossRef target="Chapter" ref="making_greenstone_collections"/> explique la procÃ©dure de crÃ©ation d'une bibliothÃšque propre de collections en utilisant le "Greenstone Librarian Interface" (l'Interface BibliothÃ©caire de Greenstone). La sectionÂ <CrossRef target="Chapter" ref="administration"/> introduit l'outil d'administration, qui permet Ã  l'administrateur systÃšme de surveiller ce qui se passe, et de contrÃŽler les droits de construction de collections.</Text>
+<Text id="12">Les annexes listent les fonctionnalitÃ©s du logiciel Greenstone, et donnent un glossaire des termes utilisÃ©s dans la documentation de Greenstone.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="13">Documents d'accompagnement</Text>
+</Title>
+<Content>
+<Text id="14">L'ensemble des documents de Greenstone comprend quatre volumes:</Text>
+<BulletList>
+<Bullet>
+<Text id="15">Guide d'installation de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">Guide de l'utilisateur de la bibliothÃšque numÃ©rique Greenstone (<i>ce document-ci</i>)</Text>
+</Bullet>
+<Bullet>
+<Text id="17">Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="18">BibliothÃšque numÃ©rique Greenstone: du papier Ã  la collection</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">Remerciements</Text>
+</Title>
+<Content>
+<Text id="20">Le logiciel Greenstone a vu le jour grÃ¢ce Ã  un effort de collaboration entre de nombreuses personnes. Rodger McNab et Stefan Boddie en sont les principaux architectes et dÃ©veloppeurs. Des contributions ont Ã©tÃ© faites par David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, et Stuart Yeates. D'autres membres du Projet de bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande ont Ã©galement donnÃ© des conseils et inspirÃ© les concepteurs du systÃšme: Mark Apperley, Sally Jo Cunningham, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, et Lloyd Smith. Nous remercions aussi tous ceux qui ont contribuÃ© au dÃ©veloppement des modules sous licence GNU GPL qui font partie de cette distribution: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE, XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="overview_of_greenstone">
+<Title>
+<Text id="21">Vue d'ensemble de Greenstone</Text>
+</Title>
+<Content>
+<Text id="22">Greenstone est un systÃšme complet pour construire et prÃ©senter des collections de milliers ou de millions de documents, comprenant du texte, des images, des contenus audio et vidÃ©o.</Text>
+<Section id="collections">
+<Title>
+<Text id="23">Les collections</Text>
+</Title>
+<Content>
+<Text id="24">La bibliothÃšque numÃ©rique typique construite avec Greenstone contient de nombreuses collections, organisÃ©es individuellementÂ --Â mÃªme si elles ont un air de famille prononcÃ©. Elles sont faciles Ã  maintenir, et on peut facilement y ajouter du contenu et les reconstruire automatiquement.</Text>
+<Text id="25">Il existe plusieurs maniÃšres de retrouver de l'information dans la plupart des collections Greenstone. On peut par exemple<i>rechercher des mots particuliers</i>apparaissant dans le corps du texte ou dans une section du document. On peut aussi<i>consulter des documents par leur titre</i>: il suffit alors de cliquer sur un livre pour le lire. On peut encore<i>consulter des documents par thÃšme</i>. Les thÃšmes reprÃ©sentent les Ã©tagÃšres de la bibliothÃšque: il suffit de cliquer sur une Ã©tagÃšre pour en voir les livres. Quand cela a un sens, les documents sont fournis avec une table des matiÃšres: on peut alors cliquer sur un chapitre ou sur une sous-section pour en lire le contenu, on peut dÃ©velopper toute la table des matiÃšres, ou encore dÃ©velopper tout le document dans la fenÃªtre de son navigateur (ce qui est utile pour imprimer). Le site web de la bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande (nzdl.org) propose de nombreux exemples de collections.</Text>
+<Text id="26">La page de garde de chaque collection prÃ©sente l'objectif et la couverture de la collection, et en explique l'organisation. On peut consulter la plupart des collections en y <i>recherchant</i>des mots-clefs ou en y<i>naviguant</i>. Lors de recherches, le logiciel Greenstone examine l'ensemble du texte de tous les documents de la collection (ce qui s'appelle une Â«recherche dans le corps du texteÂ»). Dans la plupart des collections l'utilisateur peut choisir entre plusieurs index, construits Ã  partir de diffÃ©rentes portions des documents. Certaines collections disposent d'un index des documents complets, d'un index des paragraphes, et d'un index des titres, dans lesquels on peut rechercher des mots ou des groupes de mots particuliers. On peut de cette maniÃšre retrouver tous les documents contenant un ensemble de mots prÃ©cis (les mots pouvant s'Ã©taler sur tout le document), tous les paragraphes qui contiennent ce mÃªme ensemble de mots (les mots doivent alors tous apparaÃ®tre dans le mÃªme paragraphe), ou tous les documents dont les titres contiennent les mots recherchÃ©s (les mots doivent alors se trouver dans les titres du document). On peut rencontrer d'autres index, comme par exemple un index des sections, ou encore un index des en-tÃªtes de sections. Lors de navigations, l'utilisateur examine des listes: liste des auteurs, liste des titres, liste des dates, structures de classification hiÃ©rarchiques, etc. DiffÃ©rentes collections proposeront diffÃ©rentes maniÃšres de naviguer.</Text>
+</Content>
+</Section>
+<Section id="finding_information">
+<Title>
+<Text id="27">Trouver l'information</Text>
+</Title>
+<Content>
+<Text id="28">Greenstone construit des index portant sur le corps du texte Ã  partir des contenus textuels du documentÂ --Â ce sont des index qui permettent de rechercher tout mot apparaissant dans le texte du document. On peut rechercher dans les index des mots particuliers, des ensembles ou des groupes de mots, et les rÃ©sultats sont ordonnÃ©s en fonction de leur pertinence par rapport Ã  la requÃªte.</Text>
+<Text id="29">Dans la plupart des collections, des donnÃ©es descriptives telles que l'auteur, la date, des mots-clefs, etc., sont associÃ©es Ã  chaque document. On appelle ces informations Â«mÃ©ta-donnÃ©esÂ». De nombreuses collections de documents contiennent Ã©galement des index portant sur le texte de certains types de mÃ©ta-donnÃ©es. De nombreuses collections proposent par exemple un index de recherche dans les titres des documents.</Text>
+<Text id="30">Les utilisateurs peuvent naviguer de maniÃšre interactive Ã  travers des listes et des structures hiÃ©rarchiques qui sont engendrÃ©es Ã  partir des mÃ©ta-donnÃ©es associÃ©es Ã  chaque document de la collection. Les mÃ©ta-donnÃ©es forment la matiÃšre premiÃšre de la navigation: elles doivent Ãªtre explicitement fournies, ou bien il doit Ãªtre possible de les obtenir automatiquement Ã  partir des documents eux-mÃªmes. DiffÃ©rentes collections proposeront diffÃ©rentes maniÃšres de naviguer. Les index de recherche et de navigation sont crÃ©Ã©s lors d'un processus de Â«constructionÂ», en se basant sur les informations fournies dans le fichier de configuration de la collection.</Text>
+<Text id="31">Greenstone crÃ©e toutes ses structures d'index automatiquement Ã  partir des documents et des fichiers qui les accompagnent: rien n'est fait manuellement. Si de nouveaux documents du mÃªme format sont disponibles, ils peuvent Ãªtre automatiquement fusionnÃ©s au reste de la collection. En fait, pour la plupart des collections, tout ceci est pris en charge par des processus qui s'exÃ©cutent rÃ©guliÃšrement, partent Ã  la recherche de nouveaux contenus, et reconstruisent les indexÂ --Â le tout sans aucune intervention manuelle.</Text>
+</Content>
+</Section>
+<Section id="document_formats">
+<Title>
+<Text id="32">Les formats de documents</Text>
+</Title>
+<Content>
+<Text id="33">Les documents originaux sont dans un grand nombre de formats, et sont traduits sous une forme XML standard Ã  l'aide de Â«greffonsÂ» (plugins). Les greffons distribuÃ©s avec Greenstone sont capables de traiter des documents aux formats texte brut, HTML, Word, PDF, et les messages Ã©lectroniques (de courrier ou de groupes de discussion). On peut Ã©crire de nouveaux greffons pour de nouveaux types de documents (pour ce faire, il faudra prÃ©alablement Ã©tudier le Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone). Pour construire des structures de navigation Ã  partir de mÃ©ta-donnÃ©es, on utilise de mÃªme un systÃšme de Â«classificateursÂ». Ces derniers crÃ©ent des index de navigation de divers types: listes dÃ©roulantes, sÃ©lecteurs alphabÃ©tiques, dates et autres hiÃ©rarchies arbitraires. Ici encore, des programmeurs Greenstone peuvent crÃ©er de nouvelles structures de navigation.</Text>
+</Content>
+</Section>
+<Section id="multimedia_and_multilingual_documents">
+<Title>
+<Text id="34">Documents multimÃ©dia et multilingues</Text>
+</Title>
+<Content>
+<Text id="35">Les collections peuvent comprendre du texte, des images, des contenus audio et vidÃ©o. Les contenus non textuels peuvent Ãªtre reliÃ©s aux documents textuels ou accompagnÃ©s de descriptions textuelles (telles que les lÃ©gendes des figures) pour pouvoir Ãªtre accessibles depuis une recherche dans le corps du texte ou la navigation.</Text>
+<Text id="36">Greenstone utilise partout Unicode, qui est un systÃšme standard pour reprÃ©senter les jeux de caractÃšres des langues du monde. Ceci permet de traiter et de reprÃ©senter toutes les langues de maniÃšre consistante. On a construit des collections avec de l'anglais, de l'arabe, du chinois, de l'espagnol, du franÃ§ais, et du maori. Les collections multilingues intÃšgrent une reconnaissance automatique de la langue, et l'interface est disponible dans toutes les langues mentionnÃ©es ci-dessus (entre autres).</Text>
+</Content>
+</Section>
+<Section id="distributing_greenstone">
+<Title>
+<Text id="37">Distribuer Greenstone</Text>
+</Title>
+<Content>
+<Text id="38">Les collections sont mises Ã  disposition sur l'Internet ou publiÃ©es, sous une forme exactement semblable, sur un cÃ©dÃ©rom qui s'installe automatiquement sous Windows. Les textes et les index sont compactÃ©s, et un protocole CORBA permet de gÃ©rer les collections distribuÃ©es et les interfaces de requÃªtes graphiques.</Text>
+<Text id="39">La bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande (nzdl.org) fournit de nombreux exemples de collections, y compris des documents historiques, des informations humanitaires et de dÃ©veloppement, des rapports techniques et des bibliographies, des 1#1uvres littÃ©raires, et des magazines.</Text>
+<Text id="40">Sa nature Open Source fait de Greenstone un logiciel facile Ã  complÃ©ter, et il bÃ©nÃ©ficie de l'inclusion de modules sous licence publique gÃ©nÃ©rale de GNU pour la recherche dans le corps du texte, la gestion des bases de donnÃ©es, et l'extraction de texte depuis des formats de documents propriÃ©taires. Seule une coopÃ©ration internationale permettra aux logiciels de bibliothÃšque numÃ©rique de devenir suffisamment complets et de satisfaire les besoins des utilisateurs en richesse comme en souplesse.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="using_greenstone_collections">
+<Title>
+<Text id="41">Utilisation des collections Greenstone</Text>
+</Title>
+<Content>
+<Text id="42">Le logiciel Greenstone a Ã©tÃ© conÃ§u dans un souci d'ergonomie. Les interfaces des collections sont identiques, sur le web comme sur des cÃ©dÃ©roms. L'installation de Greenstone Ã  partir du cÃ©dÃ©rom est une opÃ©ration trÃšs simple, sur tout ordinateur Ã©quipÃ© de Windows ou de Linux: un programme d'installation standard complÃšte des binaires prÃ©-compilÃ©s. On peut utiliser une collection localement, sur l'ordinateur oÃ¹ elle est installÃ©e; on peut aussi, si cet ordinateur est reliÃ© Ã  un rÃ©seau, autoriser de maniÃšre automatique et transparente l'accÃšs Ã  cette collection depuis tous les autres ordinateurs du rÃ©seau.</Text>
+<Text id="43">La section suivante dÃ©crit l'installation d'un cÃ©dÃ©rom de Greenstone. Nous examinerons ensuite les possibilitÃ©s de recherche et de navigation offertes par une collection Greenstone reprÃ©sentative: la collection Â«DemoÂ», fournie avec Greenstone. D'autres collections prÃ©senteront des fonctionnalitÃ©s semblables: savoir en manipuler une, c'est savoir les manipuler toutes. Vient ensuite une explication sur la maniÃšre d'adapter l'interface Ã  vos propres besoins Ã  l'aide de la page de prÃ©fÃ©rences.</Text>
+<Section id="utilisation_d'using_a_greenstone_cd-rom">
+<Title>
+<Text id="44">Utilisation d'un cÃ©dÃ©rom de Greenstone</Text>
+</Title>
+<Content>
+<Text id="45">Le logiciel de bibliothÃšque numÃ©rique Greenstone lui-mÃªme est distribuÃ© sur un cÃ©dÃ©rom, et votre administrateur systÃšme ou vous l'avez dÃ©jÃ  installÃ© sur votre systÃšme, en suivant les instructions du Guide d'installation de la bibliothÃšque numÃ©rique Greenstone. Si telle est bien votre situation, Greenstone est dÃ©jÃ  installÃ© sur votre ordinateur et vous pouvez nÃ©gliger de lire le reste de la prÃ©sente section et passer directement Ã  la suivante.</Text>
+<Text id="46">Certaines collections Greenstone sont distribuÃ©es sur un cÃ©dÃ©rom minimal, qui contient juste assez du logiciel pour n'utiliser que cette collection. Pour utiliser un tel cÃ©dÃ©rom, il suffit de l'insÃ©rer dans le lecteur de cÃ©dÃ©rom sur tout ordinateur personnel Ã©quipÃ© de Windows. Dans la plupart des cas (si le programme autorun est activÃ©), une fenÃªtre apparaÃ®tra, qui vous invitera Ã  installer le logiciel Greenstone. Dans le cas contraire, trouvez le lecteur de cÃ©dÃ©rom (sur les systÃšmes Windows actuels, on y parvient en double-cliquant sur l'icone Mon ordinateur, situÃ©e sur le bureau), et double-cliquez dessus, puis sur le fichier Setup.exe qu'elle contient. Le programme Setup de Greenstone sera alors exÃ©cutÃ© et vous guidera tout au long de la procÃ©dure d'installation. La plupart des gens se contentent de rÃ©pondre oui (yes) Ã  toutes les questions.</Text>
+<Text id="47">Ã la fin de la procÃ©dure d'installation, vous trouverez la bibliothÃšque dans le sous-menu Programmes du menu DÃ©marrer de Windows, et elle portera le nom de la collection, comme par exemple, Humanity Libraries (Â«bibliothÃšques pour l'humanitÃ©) ou United Nations University (Â«universitÃ© des Nations-UniesÂ»).</Text>
+<Text id="48">Une fois que le logiciel a Ã©tÃ© installÃ©, vous entrerez automatiquement dans la bibliothÃšque Ã  chaque insertion du cÃ©dÃ©rom, si le programme autorun est activÃ©.</Text>
+</Content>
+</Section>
+<Section id="finding_information_1">
+<Title>
+<Text id="49">Trouver l'information</Text>
+</Title>
+<Content>
+<Text id="50">La meilleure maniÃšre d'apprendre Ã  utiliser une collection Greenstone est de pratiquer. Pas d'inquiÃ©tudeÂ --Â vous ne pouvez rien casser. Cliquez partout et sans crainte: la plupart des images qui apparaÃ®tront sur votre Ã©cran rÃ©agissent aux clics. Si vous maintenez le pointeur de la souris au-dessus d'une image, la plupart des navigateurs afficheront un message qui vous expliquera ce qui se passera si vous cliquez.</Text>
+<Text id="51">Faites l'expÃ©rience! Choisissez des mots communs tels que Â«leÂ» (the) ou Â«etÂ» (and) en tant que critÃšres de rechercheÂ --Â voilÃ  qui devrait fournir des rÃ©ponses, et vous ne pourrez rien casser.</Text>
+<Text id="52">Les bibliothÃšques numÃ©riques Greenstone comprennent souvent plusieurs collections distinctesÂ --Â par exemple, des rapports scientifiques et techniques, des 1#1uvres littÃ©raires, des FAQ de l'Internet, des magazines. Le systÃšme de bibliothÃšque numÃ©rique disposera d'une page d'accueil qui vous permettra d'accÃ©der Ã  toute collection publiquement accessible; de plus, chaque collection dispose de sa propre page Â«Ã  proposÂ» qui vous fournira toutes les informations relatives Ã  l'organisation de la collection et aux principes guidant ce qui y est inclus. Pour retrouver cette page Ã  tout moment, cliquez simplement sur l'icone de Â«collectionÂ» qui apparaÃ®t dans le coin supÃ©rieur gauche de toutes les pages de recherche et de navigation.</Text>
+<Text id="53">La figureÂ 1 prÃ©sente une copie d'Ã©cran de la collection Â«DemoÂ», fournie avec le logiciel Greenstone, et qui reprÃ©sente un tout petit sous-ensemble de la collection de bibliothÃšque de dÃ©veloppement pour l'humanitÃ©; nous l'utiliserons comme rÃ©fÃ©rence pour la description des diffÃ©rentes maniÃšres de trouver de l'information. Si vous ne trouvez pas la collection Â«DemoÂ», utilisez Ã  la place la bibliothÃšque de dÃ©veloppement pour l'humanitÃ©: elle lui ressemble en tous points. D'abord, on peut cliquer sur presque toutes les icones. Plusieurs icones apparaissent au sommet de la plupart des pages; le tableauÂ 1explique leur signification.</Text>
+<Figure id="using_the_demo_collection">
+<Title>
+<Text id="54">Utilisation de la collection Â«DemoÂ»</Text>
+</Title>
+<File url="images/User_Fig_1.png"/>
+</Figure>
+<Table id="what_the_icons_at_the_top_of_each_page_mean">
+<Title>
+<Text id="55">Signification des icones situÃ©es au sommet de chaque page</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="">
+<File url="images/User_Icon_1.png" height="32"/>
+</th>
+<th width="255">
+<Text id="56">Vous emmÃšne sur la page Â«Ã  proposÂ»</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_2.png" height="16"/>
+</th>
+<th width="255">
+<Text id="57">Vous emmÃšne sur la page d'accueil de la bibliothÃšque numÃ©rique, depuis laquelle vous pourrez choisir une autre collection</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_3.png" height="16"/>
+</th>
+<th width="255">
+<Text id="58">Fournit un texte d'aide similaire au prÃ©sent </Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_4.png" height="16"/>
+</th>
+<th width="255">
+<Text id="59">Vous permet de mettre en place des options d'interface utilisateur et de recherche qui seront dÃšs lors sÃ©lectionnÃ©es</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="60">La barre situÃ©e juste dessous, intitulÃ©e Â«recherche ... thÃšmes ... titres a-z ... organisation ... comment faireÂ» vous donne accÃšs aux fonctionnalitÃ©s de recherche et de navigation. Le bouton le plus Ã  gauche sert aux recherches, et les autres boutonsÂ --Â au nombre de quatre dans la cette collectionÂ --Â Ã©voquent plusieurs types de navigation. Ces quatre derniers boutons peuvent varier d'une collection Ã  l'autre.</Text>
+<Subsection id="how_to_find_information">
+<Title>
+<Text id="61">Comment trouver de l'information</Text>
+</Title>
+<Content>
+<Text id="62">Le tableauÂ 2montre les cinq maniÃšres de trouver de l'information dans la collection Â«DemoÂ».</Text>
+<Table id="table_icons_on_the_search_browse_bar">
+<Title>
+<Text id="63">Signification des icones de la barre de recherche/navigation</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="">
+<File url="images/User_Icon_5.png" height="12"/>
+</th>
+<th width="">
+<Text id="64">Recherche de mots-clefs particuliers</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_6.png" height="12"/>
+</th>
+<th width="">
+<Text id="65">AccÃšs aux publications par thÃšme</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_7.png" height="12"/>
+</th>
+<th width="">
+<Text id="66">AccÃšs aux publications par titre</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_8.png" height="12"/>
+</th>
+<th width="">
+<Text id="67">AccÃšs aux publications par organisation</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_9.png" height="12"/>
+</th>
+<th width="">
+<Text id="68">AccÃšs aux publications par listes de Â«comment faireÂ»</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="69">Vous pouvez <i>rechercher des mots-clefs particuliers</i>dans le corps du texte Ã  partir de la page de Â«rechercheÂ» (semblable en tous points Ã  la page Â«Ã  proposÂ» prÃ©sentÃ©e dans la figure 1, Ã  ceci prÃšs qu'elle ne contient pas la mention Ã  propos de cette collection). On atteint la page de recherche en cliquant sur le bouton Rechercher. Vous pouvez<i>accÃ©der aux publications par thÃšme</i>en cliquant sur le bouton ThÃšmes. Ceci affiche une liste de thÃšmes, reprÃ©sentÃ©s par des Ã©tagÃšres qu'on peut ensuite dÃ©velopper en cliquant dessus. Vous pouvez<i>accÃ©der aux publications par titre</i>en cliquant sur le bouton titres a-z. Ceci affiche une liste de livres par ordre alphabÃ©tique. Vous pouvez<i>accÃ©der aux publications par organisation</i>en cliquant sur le bouton organisation. Ceci affiche une liste d'organisations. Vous pouvez<i>accÃ©der aux publications par liste de Â«comment faireÂ»</i>en cliquant sur le bouton comment faire. Ceci affiche une liste de Â«comment faireÂ». Tous ces boutons sont visibles dans la figureÂ 1.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_to_read_the_documents">
+<Title>
+<Text id="70">Comment lire les documents</Text>
+</Title>
+<Content>
+<Figure id="a_book_in_the_demo_collection">
+<Title>
+<Text id="71">Un livre de la collection Â«DemoÂ»</Text>
+</Title>
+<File url="images/User_Fig_2.png"/>
+</Figure>
+<Text id="72">Dans la collection Â«DemoÂ», on sait qu'on est arrivÃ© Ã  un livre particulier quand on voit apparaÃ®tre la photographie de sa couverture (comme sur la figureÂ 2). Une table des matiÃšres jouxte cette image: la ligne en gras marque l'endroit courant, qui est dans le cas prÃ©sent Introduction and Summary (Â«introduction et rÃ©sumÃ©Â»), c'est-Ã -dire la premiÃšre section du livre considÃ©rÃ©. On peut dÃ©velopper cette table des matiÃšres: cliquer sur les dossiers aura pour effet de les ouvrir ou de les fermer. Cliquer sur le livre ouvert au sommet le fermera.</Text>
+<Text id="73">Vient ensuite le texte de la section courante (The international demand for tropical butterflies...Â --Â Â«la demande internationale en papillons tropicaux...Â» dans l'exemple citÃ©, juste sous l'illustration). Ã la fin de la lecture, des flÃšches vous proposeront de passer Ã  la section suivante ou de revenir sur la section prÃ©cÃ©dente.</Text>
+<Text id="74">Sous la photographie, on trouve quatre boutons. Cliquer sur DÃ©tacher crÃ©era une nouvelle fenÃªtre de navigateur pour ce seul livre (ce qui est utile si on souhaite comparer des livres, ou en lire plusieurs Ã  la fois). Si vous avez atteint ce livre suite Ã  une opÃ©ration de recherche, les termes de la recherche seront mis en valeur: le bouton Supprimer la mise en Ã©vidence dÃ©sactive cette fonctionnalitÃ©. Cliquer sur DÃ©velopper le texte dÃ©veloppera tout le texte de la section ou du livre en cours. Cliquer sur DÃ©velopper le contenu prÃ©sentera toute la table des matiÃšres du livre, de sorte que vous pourrez voir les titres de tous les chapitres et sous-sections.</Text>
+<Text id="75">Dans certaines collections, les documents ne disposent pas d'une telle structure hiÃ©rarchique. Dans ce cas, aucune table des matiÃšres n'est affichÃ©e lorsque l'on parvient sur un document particulierÂ --Â on ne dispose alors que du texte du document. Dans certains cas, le document est divisÃ© en pages, qu'on peut alors lire dans l'ordre, ou passer d'une page Ã  une autre.</Text>
+</Content>
+</Subsection>
+<Subsection id="what_the_icons_mean">
+<Title>
+<Text id="76">Signification des icones</Text>
+</Title>
+<Content>
+<Text id="77">Lorsque vous naviguerez dans la collection, vous trouverez les Ã©lÃ©ments prÃ©sentÃ©s au tableauÂ 3.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_to_search_for_particular_words">
+<Title>
+<Text id="78">Comment rechercher des mots-clefs particuliers</Text>
+</Title>
+<Content>
+<Text id="79">Ã partir de la page de recherche, suivez les Ã©tapes suivantes pour effectuer une requÃªte:</Text>
+<BulletList>
+<Bullet>
+<Text id="80">SpÃ©cifiez les unitÃ©s concernÃ©es par la recherche: dans la collection Â«DemoÂ» vous pouvez effectuer des recherches dans les titres des sections ou dans le corps du texte des livres.</Text>
+</Bullet>
+<Bullet>
+<Text id="81">PrÃ©cisez si vous souhaitez rechercher tout ou partie des mots-clefs indiquÃ©s.</Text>
+</Bullet>
+<Bullet>
+<Text id="82">Tapez les mots que vous souhaitez rechercher dans la boÃ®te de requÃªte.</Text>
+</Bullet>
+<Bullet>
+<Text id="83">Cliquez sur le bouton DÃ©buter la recherche.</Text>
+</Bullet>
+</BulletList>
+<Text id="84">Lorsque vous effectuez une requÃªte, les titres des documents correspondants seront prÃ©sentÃ©s par paquets de 20 au maximum. Un bouton situÃ© Ã  la fin vous emmÃ©nera aux 20 suivants, d'oÃ¹ d'autres boutons vous emmÃ©neront aux 20 suivants, ou vous permettront de revenir 20 premiers, et ainsi de suite. Cependant, des soucis d'efficacitÃ© ont dictÃ© le choix d'un maximum de 100 documents renvoyÃ©s pour toute requÃªte. Vous pourrez changer ces nombres en cliquant sur le bouton prÃ©fÃ©rences situÃ© au sommet de la page.</Text>
+<Table id="table_icons_that_you_will_encounter_when_browsing">
+<Title>
+<Text id="85">Icones que vous rencontrerez lors de la navigation</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="">
+<File url="images/User_Icon_10.png" height="16"/>
+</th>
+<th width="283">
+<Text id="86">Cliquez sur l'icone d'un livre pour lire le livre correspondant</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_11.png" height="16"/>
+</th>
+<th width="283">
+<Text id="87">Cliquez sur une Ã©tagÃšre pour examiner les livres relatifs Ã  ce thÃšme</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_12.png" height="16"/>
+</th>
+<th width="283">
+<Text id="88">Visualiser ce document</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_13.png" height="16"/>
+</th>
+<th width="283">
+<Text id="89">Ouvrir ce dossier et visualiser son contenu</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_14.png" height="16"/>
+</th>
+<th width="283">
+<Text id="90">Cliquez sur cette icone pour fermer le livre</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_15.png" height="16"/>
+</th>
+<th width="283">
+<Text id="91">Cliquez sur cette icone pour fermer le dossier</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_16.png" height="16"/>
+</th>
+<th width="283">
+<Text id="92">Cliquez sur la flÃšche pour continuer vers la prochaine section...</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_17.png" height="16"/>
+</th>
+<th width="283">
+<Text id="93">...ou pour revenir Ã  la section prÃ©cÃ©dente</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_18.png" height="16"/>
+</th>
+<th width="283">
+<Text id="94">Ouvrir cette page dans une nouvelle fenÃªtre</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_19.png" height="16"/>
+</th>
+<th width="283">
+<Text id="95">DÃ©velopper la table des matiÃšres</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_20.png" height="16"/>
+</th>
+<th width="283">
+<Text id="96">Afficher tout le texte</Text>
+</th>
+</tr>
+<tr>
+<th width="">
+<File url="images/User_Icon_21.png" height="16"/>
+</th>
+<th width="283">
+<Text id="97">Mettre en valeur les termes de la recherche</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="98">Cliquer sur le titre de tout document ou sur la petite icone qui le jouxte aura pour effet de l'ouvrir. L'icone peut reprÃ©senter un livre, un dossier, ou une page: ce sera un livre si vous recherchez parmi des livres; dans le cas contraire, si vous recherchez parmi des sections, ce sera une icone de dossier ou de page selon que la section trouvÃ©e dispose ou non de sous-sections.</Text>
+<Part id="search_terms">
+<Title>
+<Text id="99"><i>Termes de la recherche</i></Text>
+</Title>
+<Content>
+<Text id="100">Ce que vous taperez dans la boÃ®te de requÃªte sera interprÃ©tÃ© comme une liste de mots appelÃ©e Â«termes de la rechercheÂ». Chaque terme de la recherche ne peut contenir que des lettres de l'alphabet ou des chiffres, et les termes sont sÃ©parÃ©s par des blancs. Tous les autres caractÃšres apparaissant, tels que des signes de ponctuation, seront interprÃ©tÃ©s comme des sÃ©parateurs de termes, exactement comme les blancs. Ils ne seront donc pas pris en compte: vous ne pouvez pas rechercher des mots incluant des signes de ponctuation.</Text>
+<Text id="101">Par exemple, la requÃªte:</Text>
+<Text type="code" id="102">Agro-forestry in the Pacific Islands: Systems for Sustainability (1993)<br/>(Â«agriculture-et-forÃªt dans les Ã®les du Pacifique: systÃšmes de durabilitÃ© (1993)Â»)</Text>
+<Text id="103">sera traitÃ©e exactement comme:</Text>
+<Text type="code" id="104">Agro forestry in the Pacific Islands Systems for Sustainability 1993<br/>(Â«agriculture et forÃªt dans les Ã®les du Pacifique systÃšmes de durabilitÃ© 1993Â»)</Text>
+</Content>
+</Part>
+<Part id="query_type">
+<Title>
+<Text id="105"><i>Types de requÃªtes</i></Text>
+</Title>
+<Content>
+<Text id="106">On trouve deux types de requÃªtes:</Text>
+<BulletList>
+<Bullet>
+<Text id="107">Des requÃªtes sur tous les termes. Ces requÃªtes recherchent des documents (ou des chapitres, ou des titres) qui contiennent tous les termes spÃ©cifiÃ©s. Les documents qui satisfont la requÃªte sont affichÃ©s.</Text>
+</Bullet>
+<Bullet>
+<Text id="108">Des requÃªtes sur certains termes. Contentez-vous de lister des termes susceptibles d'apparaÃ®tre dans les documents que vous recherchez. Les documents sont affichÃ©s par ordre de degrÃ© de satisfaction de la requÃªte. Lors du calcul du degrÃ© de satisfaction d'une requÃªte:</Text>
+<BulletList>
+<Bullet>
+<Text id="109">plus un document contient de termes de recherche, mieux il correspond;</Text>
+</Bullet>
+<Bullet>
+<Text id="110">les termes rares sont plus importants que les termes communs;</Text>
+</Bullet>
+<Bullet>
+<Text id="111">les documents courts reÃ§oivent un score plus Ã©levÃ© que les documents volumineux.</Text>
+</Bullet>
+</BulletList>
+</Bullet>
+</BulletList>
+</Content>
+</Part>
+<Text id="112">Utilisez autant de termes de recherche que vous le dÃ©sirezÂ --Â une phrase complÃšte, ou mÃªme un paragraphe complet. Si vous ne spÃ©cifiez qu'un seul terme, le choix d'une requÃªte sur tous les termes ou sur certains termes n'aura que peu d'importance, Ã  ceci prÃšs que dans le second cas, les rÃ©sultats seront triÃ©s en fonction de la frÃ©quence d'apparition du terme de la recherche.</Text>
+</Content>
+</Subsection>
+<Subsection id="scope_of_queries">
+<Title>
+<Text id="113">PortÃ©e des requÃªtes</Text>
+</Title>
+<Content>
+<Text id="114">Dans la plupart des collections vous pourrez choisir parmi diffÃ©rents index de recherche. On peut trouver par exemple des index des auteurs ou des titres, ou bien des chapitres ou des paragraphes. En gÃ©nÃ©ral, tout le document correspondant est renvoyÃ©, quel que soit l'index de recherche utilisÃ©.</Text>
+<Text id="115">Si les documents sont des livres, ils seront ouverts Ã  l'endroit appropriÃ©.</Text>
+</Content>
+</Subsection>
+<Subsection id="advanced_search_features">
+<Title>
+<Text id="116">FonctionnalitÃ©s de recherche avancÃ©e</Text>
+</Title>
+<Content>
+<Text id="117">MÃªme si la plupart des besoins de recherche sont satisfaits par ce qui est dÃ©crit ci-dessus, Greenstone propose des fonctionnalitÃ©s de recherche avancÃ©e. On les active Ã  partir de la page de prÃ©fÃ©rences, qu'on atteint en cliquant sur le bouton prÃ©fÃ©rences, situÃ© au sommet de la page. AprÃšs avoir modifiÃ© vos prÃ©fÃ©rences, ne revenez pas Â«en arriÃšreÂ» dans votre navigateurÂ --Â cela aurait pour effet d'annuler les modifications. Cliquez plutÃŽt sur n'importe lequel des boutons de la barre de recherche/navigation.</Text>
+<Part id="case_sensitivity_and_stemming">
+<Title>
+<Text id="118"><i>DÃ©pendance Ã  la casse et troncature</i></Text>
+</Title>
+<Content>
+<Text id="119">Lors de la spÃ©cification de termes de recherche, on peut dÃ©cider si les majuscules et minuscules doivent correspondre entre la requÃªte et le document: c'est la Â«dÃ©pendance Ã  la casseÂ». On peut aussi choisir de ne prendre en compte que les racines des mots et d'ignorer les terminaisons: c'est la Â«troncatureÂ».</Text>
+<Text id="120">Sous Options de recherche dans la page prÃ©fÃ©rences, vous trouverez deux boutons libellÃ©s ignorer la casse et les majuscules et les minuscules doivent correspondre; ces boutons contrÃŽlent la dÃ©pendance Ã  la casse. Suivent deux boutons libellÃ©s ignorer la fin des mots et le mot entier doit correspondre: ils contrÃŽlent la troncature.</Text>
+<Text id="121">Si on sÃ©lectionne par exemple les boutons ignorer la casse et ignorer la fin des mots, la requÃªte:</Text>
+<Text type="code" id="122">African building<br/>(Â«Africaine constructionÂ»)</Text>
+<Text id="123">sera traitÃ©e de la mÃªme maniÃšre que:</Text>
+<Text type="code" id="124">africa builds<br/>(Â«afrique construitÂ»)</Text>
+<Text id="125">car la majuscule du mot Â«AfricanÂ» sera transformÃ©e en minuscule, et car les suffixes Â«nÂ» et Â«ingÂ» seront respectivement ÃŽtÃ©s des mots Â«AfricanÂ» et Â«buildingÂ» (de mÃªme, le suffixe Â«sÂ» serait ÃŽtÃ© du mot Â«buildsÂ»).</Text>
+<Text id="126">On conseille en gÃ©nÃ©ral d'ignorer la casse et les terminaisons sauf dans le cadre de recherches de mots ou d'acronymes particuliers.</Text>
+</Content>
+</Part>
+<Part id="phrase_searching">
+<Title>
+<Text id="127"><i>Recherche de groupes de mots</i></Text>
+</Title>
+<Content>
+<Text id="128">Si votre requÃªte comprend un groupe de mots entre apostrophes doubles (""), seuls les documents contenant ce groupe de mots, exactement tel que saisi par vous, seront renvoyÃ©s.</Text>
+<Text id="129">Si vous souhaitez utiliser la recherche de groupes de mots, il vous faut apprendre un peu son fonctionnement. Les groupes de mots sont traitÃ©s par un examen post-recherche. D'abord, la requÃªte est effectuÃ©e de la maniÃšre habituelleÂ --Â tous les mots du groupe de mots sont inclus dans les termes de la rechercheÂ --Â puis les documents renvoyÃ©s sont examinÃ©s pour Ã©liminer ceux oÃ¹ le groupe de mots prÃ©cisÃ© n'apparaÃ®t pas.</Text>
+<Text id="130">Lors de l'examen post-recherche, les groupes de mots sont pris tels qu'ils sont, et ceci inclut tout signe de ponctuation. Par exemple, la requÃªte:</Text>
+<Text type="code" id="131">what's a "post-retrieval scan?"<br/>(qu'est-ce qu'un Â«examen post-rechercheÂ»?)</Text>
+<Text id="132">rapatriera d'abord tous les documents correspondant aux mots:</Text>
+<CodeLine>what s a post retrieval scan</CodeLine>
+<Text id="133">puis les documents renvoyÃ©s seront examinÃ©s Ã  la recherche du groupe de mots:</Text>
+<Text type="code" id="134">post-retrieval scan?<br/>(examen post-recherche?)</Text>
+<Text id="135">Les recherches de groupes de mots sont indÃ©pendantes de la casse si on a sÃ©lectionnÃ© le bouton ignorer la casse sur la page prÃ©fÃ©rences.</Text>
+</Content>
+</Part>
+<Part id="advanced_query_mode">
+<Title>
+<Text id="136"><i>Mode de requÃªte avancÃ©</i></Text>
+</Title>
+<Content>
+<Text id="137">Dans le mode de requÃªte avancÃ©, qu'on peut sÃ©lectionner sur la page de prÃ©fÃ©rences, les requÃªtes pour tous les mots, telles que dÃ©crites ci-dessus, sont en rÃ©alitÃ© des requÃªtes boolÃ©ennes. Elles consistent en une liste de termes reliÃ©s par des opÃ©rateurs logiques Â«<i>&amp;</i>Â» (et), Â«<i>|</i>Â» (ou), et Â«<i>!</i>Â» (non). Toute absence d'opÃ©rateur entre des termes de recherche sera interprÃ©tÃ©e comme un Â«<i>&amp;</i>Â» (et): c'est pourquoi une recherche ne prÃ©cisant aucun opÃ©rateur renvoie des documents contenant tous les termes de la requÃªte.</Text>
+<Text id="138">Si les mots Â«ANDÂ», Â«ORÂ», et Â«NOTÂ»<FootnoteRef id="1"/>apparaissent dans votre requÃªte, ils sont traitÃ©s comme des termes de recherche ordinaires, et non pas comme des opÃ©rateurs. Pour utiliser les opÃ©rateurs il faut prÃ©ciser Â«<i>&amp;</i>Â», Â«<i>|</i>Â», et Â«<i>!</i>Â». On peut de plus utiliser des parenthÃšses pour prÃ©ciser les prioritÃ©s.</Text>
+</Content>
+</Part>
+<Part id="using_search_history">
+<Title>
+<Text id="139"><i>Utiliser l'historique de recherche</i></Text>
+</Title>
+<Content>
+<Text id="140">En activant la fonctionnalitÃ© d'Historique de la recherche dans la page de prÃ©fÃ©rences, vous aurez accÃšs Ã  vos derniÃšres recherches, ainsi qu'une vue synthÃ©tique du nombre de rÃ©sultats qu'elles ont fourni. Cliquez sur le bouton jouxtant l'une des recherches antÃ©rieures pour copier le texte de cette recherche dans la boÃ®te de requÃªte. Ceci facilite la rÃ©pÃ©tition de versions lÃ©gÃšrement modifiÃ©es de requÃªtes prÃ©cÃ©dentes. </Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="changing_the_preferences">
+<Title>
+<Text id="141">Changer les prÃ©fÃ©rences</Text>
+</Title>
+<Content>
+<Figure id="the_preferences_page">
+<Title>
+<Text id="142">La page de Â«prÃ©fÃ©rencesÂ»</Text>
+</Title>
+<File url="images/User_Fig_3.png"/>
+</Figure>
+<Text id="143">Cliquer sur le bouton prÃ©fÃ©rences situÃ© en haut de la page vous permettra de modifier certains aspects de l'interface pour qu'elle corresponde mieux Ã  vos propres souhaits. Les prÃ©fÃ©rences sont propres Ã  la collection; vous en trouverez un exemple dans la figureÂ 3. Lors de l'ajustement des prÃ©fÃ©rences de recherche, il vaut mieux cliquer sur le bouton Appliquer (illustrÃ© figure 3Â ). AprÃšs le positionnement des prÃ©fÃ©rences, ne revenez pas Â«en arriÃšreÂ» dans votre navigateurÂ --Â cela aurait pour effet d'annuler les modifications. Cliquez plutÃŽt sur n'importe lequel des boutons de la barre d'accÃšs, vers le haut de la page.</Text>
+<Subsection id="collection_preferences">
+<Title>
+<Text id="144">PrÃ©fÃ©rences de collection</Text>
+</Title>
+<Content>
+<Text id="145">Certaines collections comprennent plusieurs sous-collections, dans lesquelles on peut mener des recherches indÃ©pendantes ou groupÃ©es, comme si elles ne formaient qu'une unitÃ©. Si c'est le cas, vous pouvez choisir quelles sous-collections inclure dans vos recherches dans la page de prÃ©fÃ©rences.</Text>
+</Content>
+</Subsection>
+<Subsection id="language_preferences">
+<Title>
+<Text id="146">PrÃ©fÃ©rences de langue</Text>
+</Title>
+<Content>
+<Text id="147">Chaque collection dispose d'une langue de prÃ©sentation par dÃ©faut, mais vous pouvez choisir une autre langue si tel est votre dÃ©sir. Vous pouvez aussi modifier l'encodage utilisÃ© par Greenstone en alimentation de votre navigateurÂ --Â le logiciel a des valeurs par dÃ©faut raisonnables, mais un autre encodage fournit de meilleurs rÃ©sultats sur certains navigateurs. Toutes les collections permettent de passer d'une interface graphique standard Ã  une interface textuelle. Ceci est particuliÃšrement utile pour les mal voyants utilisant de grosses polices Ã  l'Ã©cran, ou pour les personnes utilisant un synthÃ©tiseur vocal sur leur ordinateur.</Text>
+</Content>
+</Subsection>
+<Subsection id="presentation_preferences">
+<Title>
+<Text id="148">PrÃ©fÃ©rences de prÃ©sentation</Text>
+</Title>
+<Content>
+<Text id="149">Selon les collections, on peut trouver d'autres options pour contrÃŽler la prÃ©sentation. Les collections de pages web vous permettront de supprimer la barre de navigation de Greenstone au sommet de chaque page de document, de telle sorte qu'une recherche vous mÃšne directement Ã  la page web correspondante, sans en-tÃªte Greenstone. Pour mener une autre recherche il vous faudra revenir Â«en arriÃšreÂ» dans votre navigateur. Ces collections vous permettront Ã©galement de supprimer le message d'avertissement de Greenstone lorsque vous cliquerez sur un lien qui vous mÃ©nera hors de la collection de bibliothÃšques numÃ©riques, vers le web. Enfin, certaines collections web vous permettront de dÃ©cider si les liens de la page de RÃ©sultats de la recherche doivent vous mener directement vers l'URL concernÃ©e, ou vers une copie de la page au niveau de la bibliothÃšque numÃ©rique.</Text>
+</Content>
+</Subsection>
+<Subsection id="search_preferences">
+<Title>
+<Text id="150">PrÃ©fÃ©rences de recherche</Text>
+</Title>
+<Content>
+<Text id="151">Sous PrÃ©fÃ©rences de recherche dans la figureÂ 3, les deux premiers boutons vous permettent d'obtenir une grosse boÃ®te de requÃªte, de maniÃšre Ã  effectuer facilement des recherches de la taille d'un paragraphe. Dans Greenstone, il est Ã©tonnamment rapide de rechercher des portions importantes de texte. Les deux paires de boutons suivantes contrÃŽlent le type de texte trouvÃ© par les recherches effectuÃ©es. Le premier groupe (libellÃ© Respecter la casse:) contrÃŽle la distinction majuscules/minuscules. Le second groupe, La fin des mots:, contrÃŽle la prise en compte ou non des fins de mots.</Text>
+<Text id="152">Le prochain couple de boutons vous fera passer en mode de recherche Â«avancÃ©eÂ», tel que dÃ©crit ci-dessus, ce qui vous permettra de spÃ©cifier des requÃªtes plus prÃ©cises en combinant des termes par les opÃ©rations Â«etÂ» (<i>&amp;</i>), Â«ouÂ» (<i>|</i>), et Â«nonÂ» (<i>!</i>). Vous pouvez activer ou dÃ©sactiver la fonctionnalitÃ© d'historique de recherche, mentionnÃ©e prÃ©cÃ©demment. Enfin, vous pouvez contrÃŽler le nombre de rÃ©sultats renvoyÃ©s, ainsi que le nombre de rÃ©sultats prÃ©sentÃ©s sur chaque Ã©cran, grÃ¢ce Ã  la derniÃšre entrÃ©e de la figureÂ 3.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="making_greenstone_collections">
+<Title>
+<Text id="153">CrÃ©er une collection Greenstone</Text>
+</Title>
+<Content>
+<Text id="154">La voie la plus simple pour crÃ©er de nouvelles bibliothÃšques est d'utiliser "Greenstone Librarian Interface" (l'Interface BibliothÃ©caire de Greenstone), GLI. Cela vous permet de rassembler une sÃ©rie de documents, importer ou assigner des mÃ©ta-donnÃ©es, de les intÃ©grer dans une collection Greenstone. Elle permet cinq activitÃ©s de base qui peuvent Ãªtre interpolÃ©es mais qui sont normalement entreprises dans cet ordre:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="155">Copier le document de l'espace fichiers de l'ordinateur, y compris les collections existantes, vers la nouvelle collection. Toute mÃ©ta-donnÃ© existante reste "attachÃ©e" Ã  ces documents. Des documents peuvent Ãªtre collectÃ©s Ã  partir du web par le biais d'une fonctionnalitÃ© de mirroring incorporÃ©e.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="156">Enrichir les documents en ajoutant des mÃ©tadatas supplÃ©mentaires Ã  des documents individuels ou des groupes de documents.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="157">Concevoir la bibliothÃšque en dÃ©terminant son aspect et les fonctionnalitÃ©s d'accÃšs qu'elle permet.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="158">Mettre sur pied la bibliothÃšque en utilisant Greenstone. </Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="159">PrÃ©visualiser la bibliothÃšque nouvellement crÃ©Ã©e, qui aura Ã©tÃ© installÃ©e dans votre page Greenstone en tant que collection ordinaire.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="160">"Librarian Interface" (l'Interface BibliothÃ©caire) vous permet d'ajouter aux documents ce qu'on appelle mÃ©ta-donnÃ©es "externes", des mÃ©ta-donnÃ©es rattachÃ©es au document dans son ensemble. Mais les documents ont souvent besoin d'Ãªtre structurÃ©s en sections et sous sections, et des mÃ©ta-donnÃ©es "internes" peuvent Ãªtre associÃ©es Ã  chaque partie. Dans Greenstone, des documents sources peuvent Ãªtre "marquÃ©s" avec cette information, ce qui sera expliquÃ© dans la sectionÂ 3.3.</Text>
+<Text id="161">Enfin, une autre alternative pour la crÃ©ation de collections est fournie par le Collecteur "Collector" qui aide Ã  confectionner de nouvelles collections, de modifier ou d'ajouter des Ã©lÃ©ments Ã  des collections existantes, ou de supprimer des collections. Dans la plupart des cas, le "Librarian Interface" (l'Interface BibliothÃ©caire), plus recent, devrait Ãªtre utilisÃ© en lieu et place du collecteur. Ceci sera dÃ©crit dans la sectionÂ 3.4.</Text>
+<Text id="162">Pour utiliser la puissance entiÃšre de Greenstone pour construire des collections avancÃ©es il faut aussi lire chapitre 2 du Guide de dÃ©veloppeur.</Text>
+<Section id="the_librarian_interface">
+<Title>
+<Text id="163">l'Interface du BibliothÃ©caire</Text>
+</Title>
+<Content>
+<Text id="164">Examinons un exemple simple pour expliquer le fonctionnement de l'Interface du BibliothÃ©caire de greenstone. Les figures de 4 Ã  15 sont des captures d'Ã©cran en divers points durant l'interaction. Cet exemple utilise les documents de la collection DLS "Development Library subset" qui est distribuÃ©e avec Greenstone. Pour des besoins de l'exposÃ©, la procÃ©dure prend la forme d'un passage simple Ã  travers les Ã©tapes Ã©numÃ©rÃ©es ci-dessus. Un modÃšle d'utilisation plus rÃ©aliste pour les utilisateurs est de passer successivement de l'avant Ã  l'arriiÃšre Ã  travers les diffÃ©rentes Ã©tapes au fur et Ã  mesure que l'exÃ©cution se poursuit.</Text>
+<Text id="165">L'interface bibliothÃ©caire peut fonctionner dans un de 4 mode: Assistant BibliothÃ©caire, BibliothÃ©caire, SpÃ©cialiste des Systemes BibliothÃ©caires, et Expert. Ces modes cotrolent les niveaux de dÃ©tails dans l'interface, et peut etre changÃ© Ã  travers 'PrÃ©fÃ©rences' par le menu 'Fichier'. Pour consulter cette partie, il faut que l'interface soit dans le mode prÃ©-construit, BibliothÃ©caire.</Text>
+<Subsection id="getting_started">
+<Title>
+<Text id="166">DÃ©marrage</Text>
+</Title>
+<Content>
+<Text id="167">Lancer le "Librarian Interface" (l'Interface BibliothÃ©caire) sous Windows en sÃ©lectionnant "Greenstone Digital Library" (BibliothÃšque numÃ©rique de Greenstone) dans la section des Programmes du menu "DÃ©marrer" et en choisissant "Librarian Interface". SI vous utilisez Unix, taper plutÃŽt:</Text>
+<CodeLine>cd ~/gsdl cd gli ./gli.sh</CodeLine>
+<Text id="168">oÃ¹Â /gsdl est le rÃ©pertoire contenant le systÃšme Greenstone. Pour commencer, on peut soit ouvrir une collection existante, soit en dÃ©buter une nouvelle. La figureÂ 4montre l'utilisateur en train de dÃ©buter une nouvelle collection. Il a sÃ©lectionnÃ© "Nouveau" dans le menu Fichier et a commencÃ© Ã  fournir les informations gÃ©nÃ©rales sur la collectionÂ --Â son titre, l'adresse Ã©lectronique de la personne responsable et une description sommaire du contenu, dans une fenÃªtre pop up. Le titre de la collection est une courte expression utilisÃ©e dans la bibliothÃšque numÃ©rique pour identifier le contenu de la collection : les collections existantes ont des noms tels que BibliothÃšque de la nourriture et de l'alimentation, BibliothÃšque de l'environnement Mondial et ainsi de suite. Lorsque vous tapez le titre, le systÃšme attribue un identificateur mnÃ©motechnique unique, le "nom" de la collection, pour un usage interne (Vous pouvez le changer si vous voulez). L'adresse Ã©lectronique prÃ©cise le premier point de contact pour tout problÃšme rencontrÃ© avec la collection.</Text>
+<Text id="169">La description sommaire est une dÃ©claration qui dÃ©crit les principes qui gouvernent ce qui est inclus dans la collection. Il apparaÃ®t sous le titre "Ã propos de cette collection" sur la page initiale de la collection.</Text>
+<Figure id="starting_a_new_collection">
+<Title>
+<Text id="170">CrÃ©ation d'une nouvelle collection</Text>
+</Title>
+<File url="images/User_Fig_4.png"/>
+</Figure>
+<Figure id="exploring_the_local_file_space">
+<Title>
+<Text id="171">Exploration de l'espace de fichiers local</Text>
+</Title>
+<File url="images/User_Fig_5.png"/>
+</Figure>
+<Text id="172">A ce point, l'utilisateur dÃ©cide soit de baser la nouvelle collection sur la structure d'une collection existante, soit de crÃ©er une collection d'un type totalement nouveau. Dans la figureÂ 4, il a choisi de la baser sur la collection DLS " Development Library Subset ". Cela implique que la sÃ©rie de mÃ©ta-donnÃ©es "DLS" qui est utilisÃ©e dans cette collection sera utilisÃ©e dans la nouvelle collection. (En fait, cette sÃ©rie de mÃ©ta-donnÃ©es a Ã©tÃ© utilisÃ©e pour mettre sur pied plusieurs collections Greenstone qui partagent une structure et une organisation communes mais avec un contenu diffÃ©rent, comme les collections DLS "Development Library Subset" et la collection de dÃ©monstration fournies comme modÃšles avec Greenstone.</Text>
+<Text id="173">Le jeu de mÃ©ta-donnÃ©es de DLS contient les Ã©lÃ©ments suivants:</Text>
+<BulletList>
+<Bullet>
+<Text id="174">Titre</Text>
+</Bullet>
+<Bullet>
+<Text id="175">Sujet</Text>
+</Bullet>
+<Bullet>
+<Text id="176">Langue</Text>
+</Bullet>
+<Bullet>
+<Text id="177">Organisation</Text>
+</Bullet>
+<Bullet>
+<Text id="178">Mot-clÃ© (c.-Ã -d. "Howto")</Text>
+</Bullet>
+</BulletList>
+<Text id="179">(En plus, il y a un Ã©lÃ©ment de mÃ©ta-donnÃ©e appelÃ© "AZList" qui est utilisÃ© pour dÃ©terminer la case de la liste alphabÃ©tique qui contient le titre du document, avec des valeurs comme "A-B" ou "C-D-E". Ceci est utilisÃ© pour avoir un contrÃŽle prÃ©cis sur les divisons Ã  l'intÃ©rieur de la liste. Pour la plupart des autres collections il est absent, et Greenstone attribue lui-mÃªme les rÃ©cipients.)</Text>
+<Text id="180">Si, au contraire, l'utilisateur avait choisi utilise "Nouvelle collection" Ã  ce stade, il lui est demandÃ© de sÃ©lectionner jeux de mÃ©ta-donnÃ©es qui doivent Ãªtre utilisÃ©s dans la nouvelle collection. Trois jeux standard sont prÃ©-fournis: "Dublin Core", le jeu de mÃ©ta-donnÃ©es DLS mentionnÃ©e ci-dessus et un jeu qui comprend les Ã©lÃ©ments de mÃ©ta-donnÃ©es extraits automatiquement par Greenstone Ã  partir des documents de la collection. L'utilisateur peut aussi crÃ©er de nouveaux jeux de mÃ©ta-donnÃ©es en utilisant un paneau popup activÃ© Ã  travers le menu "metadata" (mÃ©ta-donnÃ©es).</Text>
+<Text id="181">Plusieurs jeux de mÃ©ta-donnÃ©es diffÃ©rents peuvent Ãªtre associÃ©s Ã  la mÃªme collection; le systÃšme les maintient distinctes (si bien que par exemple, des documents peuvent avoir Ã  la fois un titre "Dublin Core" et un titre DLS). Les diffÃ©rents jeux sont clairement distinguÃ©es dans l'interface. Dans les coulisses, les jeux de mÃ©ta-donnÃ©es sont reprÃ©sentÃ©s en XML.</Text>
+</Content>
+</Subsection>
+<Subsection id="assembling_the_source_material">
+<Title>
+<Text id="182">Assemblage du matÃ©riel source</Text>
+</Title>
+<Content>
+<Text id="183">AprÃšs avoir cliquÃ© sur le bouton "OK" du popup "Nouvelle collection", les parties restantes de l'interface, qui Ã©taient grises avant, deviennent actives. Le panneau "Rassembler", sÃ©lectionnÃ© par l'onglet Ã©ponyme en haut de la figureÂ 4, est initialement affichÃ©. Ceci permet Ã  l'utilisateur d'explorer l'espace de fichiers local et les collections existantes tout en rassemblant les documents choisis pour la nouvelle collection. Le panneau est divisÃ© en deux sections, celle de gauche pour naviguer parmi les structures existantes et celle de droite pour les documents dans la collection.</Text>
+<Text id="184">Les opÃ©rations disponibles Ã  cette Ã©tape sont:</Text>
+<BulletList>
+<Bullet>
+<Text id="185">Navigation dans la hiÃ©rarchie de la structure existante des fichiers, et dans celle qui est en cours de crÃ©ation, de la maniÃšre usuelle.</Text>
+</Bullet>
+<Bullet>
+<Text id="186">"Glisser-coller" de fichiers dans la nouvelle collection.</Text>
+</Bullet>
+<Bullet>
+<Text id="187">SÃ©lection multiple de fichiers.</Text>
+</Bullet>
+<Bullet>
+<Text id="188">"Glisser-coller" de sous-hiÃ©rarchies entiÃšres.</Text>
+</Bullet>
+<Bullet>
+<Text id="189">Suppression de documents de la collection naissante.</Text>
+</Bullet>
+<Bullet>
+<Text id="190">CrÃ©ation de nouvelles sous-hiÃ©rarchies Ã  l'intÃ©rieur de la collection.</Text>
+</Bullet>
+<Bullet>
+<Text id="191">Filtrage des fichiers visibles aussi bien dans le systÃšme de fichiers local que dans la collection; filtrage basÃ© sur des groupes prÃ©dÃ©terminÃ©s ou sur des termes contenus dans des fichiers.</Text>
+</Bullet>
+<Bullet>
+<Text id="192">Invocation du programme appropriÃ© pour afficher les contenus du fichier sÃ©lectionnÃ© en le double-cliquant.</Text>
+</Bullet>
+</BulletList>
+<Text id="193">Une attention particuliÃšre est prise pour traiter les collisions de noms identiques quand des fichiers de mÃªme nom dans diffÃ©rentes parties de la structure de rÃ©pertoires de l'ordinateur sont copiÃ©s dans le mÃªme rÃ©pertoire de la collection.</Text>
+<Text id="194">Dans la figure 5, l'utilisateur utilise l'affichage interactif de l'arborescence des fichiers pour explorer le systÃšme local de fichiers. A ce stade, la collection sur la droite est vide; l'utilisateur la remplit en opÃ©rant un "glisser-coller" des fichiers d'intÃ©rÃªt du panneau de gauche vers le panneau de droite. De tels fichiers sont "copiÃ©s" plutÃŽt que "dÃ©places": de cette faÃ§on, le systÃšme de fichiers original n'est pas perturbÃ©. Les techniques usuelles de sÃ©lection multiple, de "glisser-coller", de structuration de la nouvelle collection en crÃ©ant des sous-rÃ©pertoires et de suppression de fichiers en les dÃ©plaÃ§ant vers la corbeille, sont toutes disponibles.</Text>
+<Text id="195">Les collections existantes sont reprÃ©sentÃ©es par un sous-rÃ©pertoire Ã  gauche appelÃ© "Collections Greenstone", qui peut Ãªtre ouvert et explorÃ© comme tout autre rÃ©pertoire. Cependant, les documents qui s'y trouvent diffÃšrent des fichiers ordinaires parce qu'ils ont des mÃ©ta-donnÃ©es qui leurs sont attachÃ©es et ceci est conservÃ© quand ils sont dÃ©placÃ©s vers une nouvelle collection. Des conflits peuvent arriver lorsque des mÃ©ta-donnÃ©es ont Ã©tÃ© assignÃ©es en utilisant un jeu de mÃ©ta-donnÃ©es diffÃ©rent de celui en cours d'utilisation, et il revient Ã  l'utilisateur de les rÃ©soudre. Dans la figure 6, l'utilisateur a sÃ©lectionnÃ© des documents Ã  partir de la collection existante et les a ajoutÃ©s Ã  la nouvelle collection. La fenÃªtre pop up explique que l'organisation des Ã©lÃ©ments de mÃ©ta-donnÃ©es ne peut pas Ãªtre automatiquement importÃ©e, et demande Ã  l'utilisateur soit de sÃ©lectionner un jeu de mÃ©ta-donnÃ©es et de cliquer sur "Ajouter" pour ajouter l'Ã©lÃ©ment de mÃ©ta-donnÃ©es Ã  ce jeu<FootnoteRef id="2"/>, soit de choisir un jeu de mÃ©ta-donnÃ©es, puis un Ã©lÃ©ment et ensuite cliquer sur "Fusionner" pour renommer l'ancien Ã©lÃ©ment de mÃ©ta-donnÃ©e en l'Ã©lÃ©ment nouveau en fusionnant les deux. Les mÃ©ta-donnÃ©es dans les documents suivants de la mÃªme collection subiront la mÃªme manipulation.</Text>
+<Text id="196">Lorsque des ensembles importants de fichiers sont sÃ©lectionnÃ©s, dÃ©posÃ©s par un "glisser-coller" dans la nouvelle collection, l'opÃ©ration de copie peut prendre quelque temps surtout quand il y a conversion de mÃ©ta-donnÃ©es. Pour indiquer la progression de l'opÃ©ration, l'interface montre le fichier qui est en train d'Ãªtre copiÃ© et le pourcentage de fichiers dÃ©jÃ  traitÃ©s.</Text>
+<Text id="197">Des fonctionnalitÃ©s spÃ©ciales sont fournies pour le traitement de gros jeux de fichiers. Par exemple, l'utilisateur peut choisir de filtrer l'arborescence des fichiers pour afficher seulement certains fichiers, en utilisant un menu dÃ©roulant de types de fichier affichÃ© en dessous des arborescences. Dans la figure 7, on montre seulement les fichiers HTM et HTML (et seuls ces fichiers seront copiÃ©s par l'opÃ©ration "glisser-coller".</Text>
+</Content>
+</Subsection>
+<Subsection id="enriching_the_documents">
+<Title>
+<Text id="198">Enrichir les documents</Text>
+</Title>
+<Content>
+<Text id="199">La prochaine Ã©tape dans la construction d'une collection consiste Ã  enrichir les documents en y ajoutant des mÃ©ta-donnÃ©es. L'onglet "Enrichir" affiche un nouveau panneau d'information (figureÂ 8), qui montre l'arborescence de documents reprÃ©sentant la collection sur la gauche, et permet, sur la droite, l'ajout de mÃ©ta-donnÃ©es datas Ã  des documents individuels ou des groupes de documents.</Text>
+<Text id="200">Les documents qui sont copiÃ©s durant la premiÃšre Ã©tape viennent avec des mÃ©ta-donnÃ©es quelcoques qui leurs sont associÃ©es. Si un document est une partie de la collection Greenstone, des mÃ©ta-donnÃ©es prÃ©cÃ©demment dÃ©finies sont transfÃ©rÃ©es vers la nouvelle collection. Il est Ã©vident que la nouvelle collection peut avoir un jeu diffÃ©rente de mÃ©ta-donnÃ©es ou, peut Ãªtre tout juste un sous-ensemble des mÃ©ta-donnÃ©es dÃ©finies, et seules les mÃ©ta-donnÃ©es qui appartiennent au jeu de la nouvelle collection sont transfÃ©rÃ©es. La rÃ©solution de tels conflits peut nÃ©cessiter l'intervention de l'utilisateur par le biais d'un dialogue supplÃ©mentaire (figureÂ 6). Tous les choix faits sont enregistrÃ©s et appliquÃ©s pour des copies de fichiers ultÃ©rieures.</Text>
+<Text id="201">Le panneau Enrich permet l'assignation de valeurs de meta-donnÃ©es aux documents de la collection. Par exemple, de nouvelles valeurs peuvent Ãªtre ajoutÃ©es au jeu de valeurs dÃ©jÃ  existantes pour un Ã©lÃ©ment. Si les valeurs de l'Ã©lÃ©ment ont une structure hiÃ©rarchique, la structure peut Ãªtre Ã©tendue de la mÃªme maniÃšre.</Text>
+<Figure id="importing_existing_metadata">
+<Title>
+<Text id="202">Importation de mÃ©ta-donnÃ©es existantes</Text>
+</Title>
+<File url="images/User_Fig_6.png"/>
+</Figure>
+<Figure id="filtering_the_file_trees">
+<Title>
+<Text id="203">Filtrage des arborescences de fichiers</Text>
+</Title>
+<File url="images/User_Fig_7.png"/>
+</Figure>
+<Figure id="assigning_metadata_using_enrich_view">
+<Title>
+<Text id="204">Assignation de mÃ©ta-donnÃ©es en utilisant "Enrich"</Text>
+</Title>
+<File url="images/User_Fig_8.png"/>
+</Figure>
+<Figure id="viewing_all_metadata_for_selected_files">
+<Title>
+<Text id="205">Affichage de toutes les mÃ©ta-donnÃ©es pour des fichiers sÃ©lectionnÃ©s</Text>
+</Title>
+<File url="images/User_Fig_9.png"/>
+</Figure>
+<Text id="206">Des valeurs de mÃ©ta-donnÃ©e peuvent aussi Ãªtre assignÃ©s Ã  des rÃ©pertoires, exactement de la mÃªme maniÃšre. Les documents dans ces rÃ©pertoires pour lesquels cette mÃ©ta-donnÃ©e n'est pas spÃ©cifiÃ©e, hÃ©ritent les valeurs de la mÃ©ta-donnÃ©e. Cependant, elles peuvent Ãªtre Ã©crasÃ©es par la suite en fournissant des valeurs diffÃ©rentes pour ces documents.</Text>
+<Text id="207">Les opÃ©rations Ã  ce stade comprennent:</Text>
+<BulletList>
+<Bullet>
+<Text id="208">Assignation de valeurs de mÃ©ta-donnÃ©es nouvelles ou existente aux documents.</Text>
+</Bullet>
+<Bullet>
+<Text id="209">Assignation de mÃ©ta-donnÃ©e Ã  un document individuel.</Text>
+</Bullet>
+<Bullet>
+<Text id="210">Assignation de mÃ©ta-donnÃ©e Ã  un rÃ©pertoire ( ceci est hÃ©ritÃ© par tous les documents dans le rÃ©pertoire, y compris ceux qui sont des sous-rÃ©pertoires.</Text>
+</Bullet>
+<Bullet>
+<Text id="211">Assignation de mÃ©ta-donnÃ©e hiÃ©rarchique dont la structure peut Ãªtre mise Ã  jour de faÃ§on dynamique si cela est nÃ©cessaire.</Text>
+</Bullet>
+<Bullet>
+<Text id="212">Edition et mise Ã  jour de mÃ©ta-donnÃ©e assignÃ©e.</Text>
+</Bullet>
+<Bullet>
+<Text id="213">Revue de mÃ©ta-donnÃ©es assignÃ©es Ã  une sÃ©lection de fichiers et rÃ©pertoires.</Text>
+</Bullet>
+</BulletList>
+<Text id="214">Pour notre exemple, dans la figureÂ 8l'utilisateur a sÃ©lectionnÃ© le dossier ec121e et a assignÃ© "Ec courier" comme son organisation de mÃ©ta-donnÃ©es. Les boutons pour mettre Ã  jour et supprimer les mÃ©ta-donnÃ©es sont activÃ©es suivant les sÃ©lections effectuÃ©es.</Text>
+<Text id="215">Durant cette phase d'enrichissement, en fait Ã  n'importe quel autre moment, l'utilisateur peut choisir d'afficher toutes les mÃ©ta-donnÃ©es qui ont Ã©tÃ© assignÃ©es aux documents de la collection. Ceci est fait en sÃ©lectionnant une sÃ©rie de documents et en choisissant "MÃ©ta-donnÃ©es assignÃ©es" Ã  partir du menu des jeux de mÃ©ta-donnÃ©es, ce qui ouvre une fenÃªtre popup comme celle de la figureÂ 9qui montre les mÃ©ta-donnÃ©es sous forme d'un tableau. Pour les grandes collections, il est utile de pouvoir afficher les mÃ©ta-donnÃ©es associÃ©es Ã  certains types de documents seulement, et quand l'utilisateur a spÃ©cifiÃ© un filtre de fichiers comme mentionnÃ© ci-dessus, seuls les documents sÃ©lectionnÃ©s sont visibles dans l'affichage des mÃ©ta-donnÃ©es.</Text>
+<Text id="216">Le panneau dans la figureÂ 10permet Ã  l'utilisateur d'Ã©diter les jeux de mÃ©ta-donnÃ©es. Ici, l'utilisateur regarde l'Ã©lÃ©ment "Subject" du jeu DLS. Les valeurs de cet Ã©lÃ©ment forment une hiÃ©rarchie, et l'utilisateur est en train d'examiner et peut Ãªtre de changer la liste des valeurs qui lui sont assignÃ©es. Le mÃªme panneau permet de changer le "profil" pour la mise en correspondance des Ã©lÃ©ments d'un jeu de mÃ©ta-donnÃ©es l'autre. Ce profil est crÃ©Ã© au cours de l'importation de documents Ã  partir de collections qui ont des mÃ©ta-donnÃ©es prÃ©-assignÃ©es.</Text>
+<Figure id="editing_the_metadata_set">
+<Title>
+<Text id="217">Edition deu jeu de mÃ©ta-donnÃ©es</Text>
+</Title>
+<File url="images/User_Fig_10.png"/>
+</Figure>
+<Figure id="designing_the_collection_1">
+<Title>
+<Text id="218">Conception de la collection</Text>
+</Title>
+<File url="images/User_Fig_11.png"/>
+</Figure>
+<Figure id="specifying_which_plug-ins_to_use">
+<Title>
+<Text id="219">SpÃ©cification des plugins Ã  utiliser</Text>
+</Title>
+<File url="images/User_Fig_12.png"/>
+</Figure>
+<Figure id="configuring_arguments_to_a_plug-in">
+<Title>
+<Text id="220">Configuration des arguments de plugin</Text>
+</Title>
+<File url="images/User_Fig_13.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="conception_de_la_collection">
+<Title>
+<Text id="221">Conception de la collection</Text>
+</Title>
+<Content>
+<Text id="222">Le panneau de conception (figureÂ 11Â --Â 18) permet la spÃ©cification de la structure, l'organisation et la prÃ©sentation de la collection qui est en train d'Ãªtre crÃ©Ã©e. Comme dÃ©jÃ  notÃ©, le rÃ©sultat de ce processus est enregistrÃ© dans le fichier de configuration de la collection "collection configuration file", qui est le moyen pour Greenstone d'exprimer les fonctionnalitÃ©s requises par une collection. Cette Ã©tape comprend une sÃ©rie d'Ã©crans d'interaction sÃ©parÃ©s, chacun traitant un aspect de la conception de la collection. En effet, il sert d'Ã©quivalent graphique Ã  l'opÃ©ration usuelle d'Ã©dition manuelle du fichier de configuration.</Text>
+<Text id="223">Les opÃ©rations comprennent:</Text>
+<BulletList>
+<Bullet>
+<Text id="224">Revue et Ã©dition de mÃ©ta-donnÃ©es de niveau collection, telles que titre, auteur et accÃšs public Ã  la collection.</Text>
+</Bullet>
+<Bullet>
+<Text id="225">DÃ©finition des indexes de texte complet Ã  construire.</Text>
+</Bullet>
+<Bullet>
+<Text id="226">CrÃ©ation de sous-collections et construction d'indexes Ã  leur allouer. </Text>
+</Bullet>
+<Bullet>
+<Text id="227">Ajout ou suppression de support de langues d'interface prÃ©dÃ©finies.</Text>
+</Bullet>
+<Bullet>
+<Text id="228">Construction d'une liste de plugins Ã  utiliser, et leurs arguments.</Text>
+</Bullet>
+<Bullet>
+<Text id="229">PrÃ©sentation de la liste Ã  l'utilisateur pour revue et modification.</Text>
+</Bullet>
+<Bullet>
+<Text id="230">Configuration de plugins individuels.</Text>
+</Bullet>
+<Bullet>
+<Text id="231">Construction d'une liste de "classificateurs", leurs arguments, affectation et configuration.</Text>
+</Bullet>
+<Bullet>
+<Text id="232">Affectation de chaÃ®nes de formatage Ã  divers contrÃŽles de la collection, en vue de changer son apparence.</Text>
+</Bullet>
+<Bullet>
+<Text id="233">Revue des jeux de mÃ©ta-donnÃ©es utilisÃ©s dans la collection ainsi que leurs Ã©lÃ©ments.</Text>
+</Bullet>
+</BulletList>
+<Text id="234">Dans la figureÂ 11, l'utilisateur a cliquÃ© sur l'onglet "Conception" et Ã©tudie les informations gÃ©nÃ©rales sur la collection, entrÃ©es lors de la crÃ©ation de la nouvelle collection. A gauche, sont listÃ©s les diffÃ©rentes facettes que l'utilisateur peut configurer : GÃ©nÃ©ral, Plug-ins de document , Type de recherche, Indexes de recherche, Indexes de partition, Recherche inter-collection, Classificateurs de navigation, FonctionnalitÃ©s de formatage, Traduction de texte, Jeux de mÃ©ta-donnÃ©es. L'apparence et la fonctionnalitÃ© varient entre celles-ci. Par exemple, en cliquant sur Plug-in, on a l'Ã©cran de la figureÂ 12qui vous permet d'ajouter, de supprimer ou de configurer des plugins, et de changer l'ordre dans lequel les plugins sont appliquÃ©s aux documents.</Text>
+<Text id="235">Les plugins et les classificateurs disposent de plusieurs arguments ou "Options" que l'utilisateur peut fournir. La boÃ®te de dialogue dans la figureÂ 13montre l'utilisateur prÃ©cisant des arguments Ã  certains plugins. Les champs grisÃ©s deviennent actifs quand l'utilisateur ajoute l'option en cliquant sur la case Ã  cocher se trouvant Ã  cÃŽtÃ©. Puisque Greenstone est un systÃšme open-source en croissance continuelle, le nombre d'options tend Ã  augmenter au fur et Ã  mesure que les dÃ©veloppeurs ajoutent de nouvelles fonctionnalitÃ©s. Pour aider Ã  y faire face, Greenstone a un programme fonctionnel "Plug-in information " qui liste les options disponibles pour chaque plugin, et le "Librarian Interface" (l'Interface BibliothÃ©caire) l'invoque automatiquement pour dÃ©terminer quelle option montrer. Ceci permet Ã  l'interface interactive de l'utilisateur de suivre automatiquement les dÃ©veloppements dans le logiciel.</Text>
+<Figure id="getting_ready_to_create_new_collection">
+<Title>
+<Text id="236">PrÃªt pour crÃ©er la nouvelle collection</Text>
+</Title>
+<File url="images/User_Fig_14.png"/>
+</Figure>
+<Figure id="previewing_the_newly_built_collection">
+<Title>
+<Text id="237">AperÃ§u de la collection nouvellement crÃ©Ã©e</Text>
+</Title>
+<File url="images/User_Fig_15.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="building_the_collection">
+<Title>
+<Text id="238">Construction de la collection</Text>
+</Title>
+<Content>
+<Text id="239">Le panneau "CrÃ©er" (figureÂ 14) est utilisÃ© pour construire une collection basÃ©e sur les documents et d'assigner des mÃ©ta-donnÃ©es. Le plus gros du travail est fait par le code Greenstone lui-mÃªme. L'utilisateur contrÃŽle le dÃ©roulement externe Ã  travers une sÃ©rie d'Ã©crans interactifs, chacun traitant les arguments fournis Ã  une certaine Ã©tape du processus de crÃ©ation.</Text>
+<Text id="240">L'utilisateur observe la construction en cours Ã  travers une fenÃªtre qui montre non seulement le texte gÃ©nÃšrÃ© par les scripts d'importation et de construction d'index, mais aussi par les barres de progression qui indiquent le degrÃ© global d'exÃ©cution de chaque script.</Text>
+<Text id="241">La figureÂ 14montre le "Create View" (Affichage CrÃ©er). Des options, pouvant Ãªtre appliquÃ©es pendant la crÃ©ation de ce processus, sont montrÃ©es en haut. L'utilisateur sÃ©lectionne les valeurs appropriÃ©es pour les options. La figure illustre un popup "tool tip" (boÃ®te Ã  outils) qui est disponible Ã  travers l'interface pour expliquer la fonction de chaque argument.</Text>
+<Text id="242">Lorsqu'il est satisfait avec ces arguments, l'utilisateur clique "Construire collection". Greenstone affiche continuellement un texte qui indique le dÃ©roulement et ceci est montrÃ© par le biais d'une barre de progression plus informative.</Text>
+</Content>
+</Subsection>
+<Subsection id="previewing">
+<Title>
+<Text id="243">AperÃ§u</Text>
+</Title>
+<Content>
+<Text id="244">Le bouton "PrÃ©visualiser la Collection" (figureÂ 14) est utilisÃ© pour visualiser la collection qui a Ã©tÃ© crÃ©Ã©e. L'appui sur ce bouton initiera la page web hebergeant cette collection (figureÂ 15). En pratique, l'aperÃ§u montre souvent des dÃ©fauts dans la conception de la collection ou sur les valeurs individuelles de mÃ©ta-donnÃ©es, et l'utilisateur retourne souvent aux Ã©tapes prÃ©cÃ©dentes pour les corriger. Ce bouton devient actif une fois que la collection a Ã©tÃ© crÃ©Ã©e. La collection nouvellement crÃ©Ã©e sera aussi installÃ©e dans votre page d'accueil Greenstone comme une des collections normales.</Text>
+</Content>
+</Subsection>
+<Subsection id="help">
+<Title>
+<Text id="245">Aide</Text>
+</Title>
+<Content>
+<Text id="246">L'aide en ligne est toujours disponible et elle est obtenue en utilisant l'Ã©lÃ©ment "Aide" situÃ© Ã  droite de la principale barre de menu, en haut de chacune des figures. Ceci ouvre un fichier hiÃ©rarchiquement structurÃ© du texte d'aide, et il est tenu compte du contexte courant de l'utilisateur pour mettre en relief la section qui est appropriÃ©e Ã  l'Ã©tape actuelle de l'interaction. En plus, comme notÃ© ci-dessus, Ã  chaque fois que la souris est maintenue sur tout objet interactif, une petite fenÃªtre popup apparaÃ®t afin de donner un "tool tip" textuel comme illustrÃ© vers le bas de la figureÂ 14.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="librarian_interface_user_guide">
+<Title>
+<Text id="247">L'interface bibliothÃ©caire du Guide d'Utilisateur</Text>
+</Title>
+<Content>
+<Subsection id="starting_off">
+<Title>
+<Text id="248">DÃ©marrage</Text>
+</Title>
+<Content>
+<Text id="249">Cette section explique comment crÃ©er, charger, enregistrer et supprimer des collections.</Text>
+<Part id="creating_a_new_collection">
+<Title>
+<Text id="250">CrÃ©er une nouvelle collection</Text>
+</Title>
+<Content>
+<Text id="251">Pour crÃ©er la nouvelle collection, ouvrir le menu "Fichier" et choisir "Nouveau". Plusieurs champs doivent Ãªtre remplis â mais leurs valeurs sont susceptibles dâÃªtre modifiÃ©es Ã  souhait dans lâaffichage de la conception.</Text>
+<Text id="252">"Titre de la collection" est le texte affichÃ© en haut de la page dâaccueil de votre collection. Sa longueur peut Ãªtre quelconque.</Text>
+<Text id="253">"Description du contenu" doit dÃ©crire avec le plus de dÃ©tails possibles ce que la collection est. Utiliser la touche [EntrÃ©e] pour la diviser en paragraphes.</Text>
+<Text id="254">On doit enfin spÃ©cifier soit que la nouvelle collection aura la mÃªme forme et les mÃªmes jeux de mÃ©ta-donnÃ©es que la collection existante, soit quâelle est initiÃ©e "Nouvelle collection" par dÃ©faut.</Text>
+<Text id="255">Cliquer sur "OK" pour crÃ©er la collection. Si on choisit "Nouvelle collection", les jeux de mÃ©ta-donnÃ©es disponibles sont affichÃ©es. On peut en choisir plus dâune et en ajouter dâautres ultÃ©rieurement.</Text>
+<Text id="256">Le clic sur "Annuler" ramÃšne immÃ©diatement lâÃ©cran principal.</Text>
+</Content>
+</Part>
+<Part id="saving_the_collection">
+<Title>
+<Text id="257">Ouvrir une collection existante</Text>
+</Title>
+<Content>
+<Text id="258">Enregistrer rÃ©guliÃšrement votre travail en choisissant "Enregistrer" dans le fichier "Menu". Enregistrer une collection ne signifie pas la rendre prÃªte Ã  lâutilisation dans Greenstone (see Confectionner votre Collection).</Text>
+<Text id="259">LâInterface BiblithÃ©caire protÃšge votre travail en lâenregistrant Ã  la fermeture du programme ou Ã  lâouverture dâune autre collection.</Text>
+<Text id="260">Les collections sont enregistrÃ©es en un fichier choisi pour la collection avec une extension ".col", localisÃ© dans un rÃ©pertoire de mÃªme nom Ã  lâintÃ©rieur du dossier "collect" de lâinstallation de Greenstone.</Text>
+</Content>
+</Part>
+<Part id="opening_an_existing_collection">
+<Title>
+<Text id="261">Ouvrir une collection existante</Text>
+</Title>
+<Content>
+<Text id="262">Pour ouvrir une collection existante, choisir "ouvrir" Ã  partir du menu "Fichier" pour obtenir le "PrÃªt Ã  lâouverture de la collection". Une liste de vos collections Greenstone apparaÃ®t. En sÃ©lectionner une pour voir sa description, et cliquer sur "Ouvrir" pour la charger. Si lâon cherche une collection qui est hors du dossier "Collect" de Greenstone, cliquer sur "Parcourir" pour un dialogue avec le systÃšme de fichiers concernÃ©.</Text>
+<Text id="263">Dans le cas oÃ¹ plusieurs programmes dâInterface BibliothÃ©caire de Greenstone sont exÃ©cutÃ©s simultanÃ©ment, les rÃ©pertoires concernÃ©s sont vÃ©rouillÃ©s pour prÃ©venir une interfÃ©rence. A lâouverture dâune collection, un petit fichier de verrouillage temporaire est crÃ©Ã© dans son dossier. Avant dâouvrir une collection, lâinterface BibliothÃ©caire vÃ©rifie quâaucun fichier de verrouillage nâexiste dÃ©jÃ . Le verrouillage dâune collection est indiquÃ© par la couleur de son icÃŽne : verte pour une collection normale, rouge quand elle est vÃ©rouillÃ©e. Cependant, quand lâon quitte lâInterface BibliothÃ©caire prÃ©maturÃ©ment, le fichier de verrouillage est parfois laissÃ© en place. Quand une telle collection est ouverte, lâInterface BibliothÃ©caire demande si lâon veut se dÃ©faire de son contrÃŽle. Ne jamais sosutraire une collection en cours dâutilisation par un autre.</Text>
+<Text id="264">Lorsque vous ouvrez une collection qui nâa pas Ã©tÃ© crÃ©Ã©e par Greenstone Librarian Interface, on vous demande de sÃ©lectionner un ou plusieurs jeux de mÃ©ta-donnÃ©es. Si vous nâen sÃ©lectionnez aucun, les mÃ©ta-donnÃ©es existantes seront ignorÃ©es. Dans le cas contraire, les mÃ©ta-donnÃ©es seront importÃ©es comme lorsque vous cliquez et glisser dans des fichiers contenant des mÃ©ta-donnÃ©es. Ce processus est dÃ©crit dans la section Importation de MÃ©ta-donnÃ©es PrÃ©cÃ©demment AssignÃ©es.</Text>
+</Content>
+</Part>
+<Part id="deleting_collections">
+<Title>
+<Text id="265">Suppression des collections</Text>
+</Title>
+<Content>
+<Text id="266">Pour supprimer dÃ©finitivement des collections de votre installation Greenstone, choisir "Supprimer..." dans le menu "Fichier". Une liste de vos collections Greenstone apparaÃ®t. Selectionner une collection pour vior sa description, puis cocher la case en bas du dialogue et clicquez "Supprimer" pour supprimer la collection. Cette operation est irrÃ©versible, vÃ©rifiez bien que vous nâavez plus besoin de cette collection avant de supprimer !</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="downloading_files_from_the_internet">
+<Title>
+<Text id="267">TÃ©lÃ©chargement de fichiers de lIinternet</Text>
+</Title>
+<Content>
+<Text id="268">La vue "TÃ©lÃ©chargement" vous permet de tÃ©lÃ©charger des resources de lâinternet. Cette section explique le processus de miroir de lâinterface bibliothÃ©caire.</Text>
+<Part id="the_download_view">
+<Title>
+<Text id="269">La vue TÃ©lÃ©chargement</Text>
+</Title>
+<Content>
+<Text id="270">Cette section dÃ©crit comment on configure une tache de tÃ©lÃ©chargement et comment on contrÃŽle le tÃ©lÃ©chargement. AccÃ©dez Ã  la vue "TÃ©lÃ©chargement" en cliquant son index. La moitiÃ© supÃ©rieure de lâÃ©cran montre le contrÃŽle des tÃ©lÃ©chargements. La moitiÃ© infÃ©rieure est initialement vide, mais montrera la liste des tÃ©lÃ©chargements en attente et rÃ©alisÃ©s.</Text>
+<Text id="271">Les fichiers sont tÃ©lÃ©chargÃ©s dans un dossier de lâespace de travail appelÃ© Â« Fichiers TÃ©lÃ©chargÃ©s Â», et peut Ãªtre utilisÃ© pour toutes les collections construites avec lâinterface bibliothÃ©caire. Les fichiers dans cette zone portent comme nom leur URL en entier. Un nouveau dossier est crÃ©Ã© pour chaque site hÃŽte, suivi par dâautres dossiers pour chaque Ã©lÃ©ment du chemin. Cela permet de sâassurer que chaque fichier a un nom distinct.</Text>
+<Text id="272">Utilisez le premier des contrÃŽles de la configuration de tÃ©lÃ©chargement, Â« Source URL Â», pour entrer lâURL de la ressource cible. Utilisez le contrÃŽle Â« Profondeur de TÃ©lÃ©chargement Â» pour limiter le nombre de liens hypertextes Ã  suivre pour le tÃ©lÃ©chargement : utiliser 0 pour tÃ©lÃ©charger une seule page ; utiliser 1 pour tÃ©lÃ©charger la page et toutes les pages rÃ©fÃ©rencÃ©es par des liens hypertextes. La profondeur limite est ignorÃ©e lors du tÃ©lÃ©chargement de mÃ©dia autres que des pages html. Ensuite il y a plusieurs cases Ã  cocher qui peuvent Ãªtre cochÃ©es pour activer lâoption spÃ©cifiÃ©e. Une fois la configuration prÃªte, cliquez Â« TÃ©lÃ©charger Â» pour dÃ©marrer lâopÃ©ration de tÃ©lÃ©chargement. Il y a deux autres boutons de contrÃŽle : Â« PrÃ©fÃ©rences Â», qui renvoie Ã  la section connexion de PrÃ©fÃ©rences ou les paramÃštre du proxy peuvent Ãªtre Ã©ditÃ©s ; et Â« Effacer la cache Â» qui supprimes tous les fichiers tÃ©lÃ©chargÃ©s prÃ©cÃ©demment.</Text>
+<Text id="273">La liste de tÃ©lÃ©chargement a une entrÃ©e pour chaque tÃ©lÃ©chargement de pageWeb. Chaque entrÃ©e a une rÃ©gion de textes qui donne les dÃ©tails de la tÃ¢che avec une barre de progrÃšs montrant lâactivitÃ© courante. Trois boutons apparaissent Ã  la gauche de chaque entrÃ©e. "Pause" est employÃ© pour pauser une tÃ¢che en cours de tÃ©lÃ©chargement. "Voir le rÃ©sumÃ©" ouvre une fenÃªtre montrant lâhistorique du tÃ©lÃ©chargement. "Fermer" termine le tÃ©lÃ©chargement et enlÃšve la tÃ¢che de la liste.</Text>
+<Text id="274">La section PrÃ©fÃ©rences explique comment Ã©tablir une connection Internet Ã  travers un proxy. Si lâauthentification est nÃ©cessaire, le proxy server demande lâidentification et le mot de passe. Lâinterface bibliothÃ©caire nâenregistre pas les mots de passe entre les sessions.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="collecting_files_for_your_collection">
+<Title>
+<Text id="275">Collecter les fichiers pour la Collection</Text>
+</Title>
+<Content>
+<Text id="276">DÃšs lors que lâon dispose dâune nouvelle collection, la nÃ©cessitÃ© se fait sentir de la doter de fichiers. Ils peuvent provenir de votre espace fichier ordinaire ou dâautres collections Greenstone. Quelques uns peuvent avoir des mÃ©ta-donnÃ©es attachÃ©es.Cette section dÃ©crit comment importer des fichiers.</Text>
+<Part id="the_gather_view">
+<Title>
+<Text id="277">Lâaffichage Rassembler</Text>
+</Title>
+<Content>
+<Text id="278">cette section introduit la zone Rassembler utilisÃ©e pour selectionner les fichiers Ã  inclure dans la collection Ã  crÃ©er. LâInterface BibliothÃ©caire dÃ©marre avec lâaffichage "Rassembler". Pour revenir ultÃ©rieurement Ã  celuici, cliquer directement sur lâonglet "Rassembler" au bas de la barre des menus.</Text>
+<Text id="279">Les deux vastes zones intitulÃ©es "Espace de travail" et "Collection" servent au transfert des fichiers vers la collection. Elles contiennent des arborescences de fichiers, des structures graphiques qui reprÃ©sentent des fichiers et des dossiers.</Text>
+<Text id="280">Choisir un Ã©lÃ©ment dans lâarborescence en cliquant dessus. (dâautres maniÃšres de le faire existent ; voir ci-dessous). Double-cliquer sur un dossier, ou cliquer simplement sur le symbole de commutateur placÃ© Ã  cÃŽtÃ© de lui, pour dÃ©velopper (ou rÃ©duire) son contenu. Double-cliquer sur un fichier pour lâouvrir en utilisant un programme dâapplication associÃ© (voir Association de fichiers).</Text>
+<Text id="281">Lâarbre des fichiers de lâespace de travail montre les sources de donnÃ©es disponibles pour lâinterface bibliothÃ©caire â le systÃšme de fichiers local (ainsi que les unitÃ©s de disques et Cd-rom), le contenu des collection Greenstone, et la cache des fichiers tÃ©lÃ©chargÃ©s. Vous pouvez copier et afficher ces fichiers mais vous ne pouvez pas les dÃ©placer, supprimer ou Ã©diter, Ã  lâexception des fichiers tÃ©lÃ©chargÃ©s qui peuvent Ãªtre supprimÃ©. Vous pouvez naviguer Ã  lâintÃ©rieur de cet espace pour trouver les documents que vous souhaitez ajouter Ã  la collection.</Text>
+<Text id="282">Lâarborescence des fichiers de la Collection ne reprÃ©sente jusque-lÃ  que le contenu de la collection. Elle est initialement vide.</Text>
+<Text id="283">On peut redimensionner les espaces en positionnant la souris sur la barre grise qui sÃ©pare les arborescences (le pointeur change de forme) et en la faisant glisser.</Text>
+<Text id="284">En bas de la fenÃªtre, il y a une barre dâÃ©tat qui montre lâÃ©volution des opÃ©rations sur les fichiers (copie, dÃ©placement et suppression). Ces opÃ©rations peuvent Ãªtre longues. Le bouton "Stop" arrÃªte toute tÃ¢che en cours.</Text>
+<Text id="285">Deux grands boutons occupent le coin droit infÃ©rieur de lâÃ©cran. "Nouveau dossier", avec une image dâun dossier, crÃ©e de nouveaux dossiers (voir CrÃ©ation de dossiers). "Supprimer", avec une corbeille, supprime les fichiers. Cliquer sur le bouton "Supprimer" dÃ©truit tous les fichiers sÃ©lectionnÃ©s de lâarborescence de fichiers de la collection. On peut de mÃªme rÃ©aliser cette suppression de fichiers en les faisant glisser jusquâau bouton "Supprimer".</Text>
+<Text id="286">Pour sÃ©lectionner plusieurs sÃ©quences dâÃ©lÃ©ments, sÃ©lectionner le premier, maintenir appuyÃ©e la touche [Maj] et cliquer sur le dernier Ã©lÃ©ment de la sÃ©quence â la sÃ©lection comprendra tous les Ã©lÃ©ments compris entre les deux. Pour la sÃ©lection de fichiers qui ne se suivent pas, maintenir la touche [Ctrl] appuyÃ©e en cliquant sur chacun dâeux. Ces deux mÃ©thodes peuvent Ãªtre utilisÃ©es ensemble pour la sÃ©lection de jeux dâÃ©lÃ©ments non adjacents.</Text>
+<Text id="287">Certains dossiers â tel que celui contenant vos propres pages Web â ont parfois une signification spÃ©ciale. LâInterface BibliothÃ©caire peut appliquer de tels dossiers au premier niveau de lâarborescence de fichiers. Pour ce faire double-cliquer droite sur le dossier visÃ©. Choisir "CrÃ©er un Raccourci", saisir le nom du dossier. Pour enlever un Ã©lÃ©ment, cliquer-droite sur le fichier concernÃ© et sÃ©lectionner "Supprimer Raccourci".</Text>
+</Content>
+</Part>
+<Part id="creating_folders">
+<Title>
+<Text id="288">CrÃ©er des dossiers</Text>
+</Title>
+<Content>
+<Text id="289">Utiliser les dossiers de lâarborescence de fichiers de la collection pour rejeur les fichiers et les rendre aisÃ©ment accessibles. Des dossiers peuvent Ãªtre placÃ©s Ã  lâintÃ©rieur dâautres dossiers. Aucune limite, virtuellement parlant, ni au nombre de dossiers dont on peut disposer ni Ã  la complexitÃ© de leur agencement.</Text>
+<Text id="290">Pour crÃ©er un nouveau dossier, on peut opter pour un dossier existant et cliquer sur le bouton Nouveau Dossier. Le nouveau dossier apparaÃ®t Ã  lâintÃ©rieur de celui choisi, ou au niveau supÃ©rieur si aucun nâest choisi. Le nom de ce dossier est rÃ©clamÃ© ( Ã  dÃ©faut, il sera nommÃ© "Nouveau Dossier").</Text>
+<Text id="291">Les dossiers peuvent aussi Ãªtre crÃ©Ã©s en cliquant sur le dossier avec le bouton droit, et en choisissant "Nouveau Dossier" et procÃ©der comme ci-dessus.</Text>
+</Content>
+</Part>
+<Part id="adding_files">
+<Title>
+<Text id="292">Ajouter des fichiers</Text>
+</Title>
+<Content>
+<Text id="293">Les fichiers peuvent Ãªtre copiÃ©s dans la collection par glisserdÃ©placer. Le pointeur Ã©pouse la forme de lâÃ©lÃ©ment sÃ©lectionnÃ© (ou, si la sÃ©lection comprend plus dâun, leur nombre). DÃ©poser la sÃ©lection dans lâarborescence de la collection pour les y copier (si la source est lâarborescence de lâespace de travail) ou les dÃ©placer Ã  lâintÃ©rieur de la collection (si la source est lâarborescence de la collection).</Text>
+<Text id="294">Lorsque des fichiers multiples sont copiÃ©s, ils sont tous placÃ© dans le dossier cible au mÃªme niveau, quelle que soit la structure du dossier qui les contenait avant. Si vous copier un second fichier avec le mÃªme nom dans le mÃªme dossier, la question de savoir si le premier fichier doit Ãªtre Ã©crasÃ© est posÃ©e. Si la rÃ©ponse est non, le fichier ne sera pas copiÃ©, mais les autres le seront. Pour annuler toutes les autre tÃ¢ches de copie, cliquer sur le bouton "Stop".</Text>
+<Text id="295">Seuls les Ã©lÃ©ments situÃ©s au-dessus dans la sÃ©lection sont dÃ©placÃ©s. Un dossier est plus Ã©levÃ© que son contenu. On ne peut sÃ©lectionner en mÃªme temps lâintÃ©rieur dâun dossier et le dossier lui-mÃªme.</Text>
+<Text id="296">Lorsquâun fichier est ajoutÃ©, lâInterface BibliothÃ©caire cherche les dossiers sources de fichiers auxiliaires contenant une mÃ©ta-donnÃ©e qui lui originellement assignÃ©es et, sâil en trouve, commence Ã  les importer. Au fur et Ã  mesure que lâopÃ©ration se poursuit, une confirmation est faite (peut-Ãªtre plusieurs fois) de fournir des informations complÃ©mentaires pour ajuster la mÃ©ta-donnÃ©e aux jeux de mÃ©ta-donnÃ©es de la collection. Ces confirmations sont dÃ©crites dans la section Importer des mÃ©tadonnÃ©es originellement assignÃ©es . Pour une explication plus dÃ©taillÃ©e de lâassociation de mÃ©ta-donnÃ©es avec les fichiers, lire le chapitre 2 du Guide de dÃ©veloppement de Greenstone â "Exploitez vos documents au maximum".</Text>
+</Content>
+</Part>
+<Part id="removing_files">
+<Title>
+<Text id="297">Supprimer des Fichiers</Text>
+</Title>
+<Content>
+<Text id="298">Il existe plusieurs mÃ©thodes pour supprimer des fichiers et des dossiers. On doit dâabord indiquer les Ã©lÃ©ments Ã  supprimer en sÃ©lectionnant un ou plusieurs fichiers et dossiers comme dÃ©crit dans LâAffichage Rassembler (The Gather view).</Text>
+<Text id="299">DÃšs lors que les fichiers sont sÃ©lectionnÃ©s, cliquer sur le bouton "Supprimer" pour les dÃ©truire, ou appuyer sur la touche [Delete] de votre clavier, ou les glisserdÃ©placer de la collection vers le bouton "Supprimer" et les y dÃ©poser.</Text>
+</Content>
+</Part>
+<Part id="filtering_the_tree">
+<Title>
+<Text id="300">Filtrer lâarborescence</Text>
+</Title>
+<Content>
+<Text id="301">Le "Filtrage" de lâarborescence de la collection permet de rÃ©duire la recherche de fichiers particuliers.</Text>
+<Text id="302">Le menu dÃ©roulant des "Montrer Fichiers" ("Show Files") au bas de chaque arborescence montre une liste de filtres prÃ©dÃ©finis, tels "Images". Son choix cache temporairement tous les autres fichiers de lâarborescence. Pour restorer celle-ci, changer le filtre en "Tous Fichiers". Ces opÃ©rations nâaltÃšrent ni la collection, ni nâaffectent les dossiers dans lâarborescence.</Text>
+<Text id="303">On peut spÃ©cifier un filtre usuel en saisissant un modÃšle assorti aux fichiers visÃ©s (systÃšmes Librairiens SpÃ©cialistes et modes Experts seulement). Utiliser un systÃšme standard dâabrÃ©viations de fichiers telles que "*.*" ou "*.doc" (*. concerne tous les caractÃšres).</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="enriching_the_collection_with_metadata">
+<Title>
+<Text id="304">Enrichir la Collection avec des mÃ©ta-donnÃ©es</Text>
+</Title>
+<Content>
+<Text id="305">AprÃšs avoir rassemblÃ© plusieurs fichiers dans la collection, on les enrichit dâune information complÃ©mentaire appelÃ©e "mÃ©ta-donnÃ©e". Cette section explique comment une mÃ©tadonnÃ©e est crÃ©Ã©e, Ã©ditÃ©e, assignÃ©e ou retirÃ©e, et comment utiliser les sources de mÃ©ta-donnÃ©es externes (voir aussi le chapitre 2 du Guide de dÃ©veloppement de Greenstone â "Exploitez vos documents au maximum").</Text>
+<Part id="the_enrich_view">
+<Title>
+<Text id="306">Lâaffichage Enrichir</Text>
+</Title>
+<Content>
+<Text id="307">Utiliser lâaffichage Enrichir pour assigner une mÃ©ta-donnÃ©e aux documents de la collection. Une mÃ©ta-donnÃ©e est une donnÃ©e sur une donnÃ©e â de faÃ§on typique titre, auteur, date de crÃ©ation, et ainsi de suite. Chaque Ã©lÃ©ment de mÃ©ta-donnÃ©e a deux parties : "elÃ©ment" indique le type dâÃ©lÃ©ment (par exemple auteur), "valeur" qui donne la valeur de cette mÃ©ta-donnÃ©e Ã©lÃ©ment (par exemple le nom de lâauteur).</Text>
+<Text id="308">Sur la gauche de lâaffichage "Enrichir" est lâarborescence de la collection. A sa droite, la Table de MÃ©ta-donnÃ©es, qui montre les mÃ©ta-donnÃ©es pour tous les fichiers et dossiers sÃ©lectionnÃ©es de lâarborescence de la collection. Les colonnes sont indiquÃ©es en gris en haut, et peuvent Ãªtre redimensionnÃ©es en faisant glisser la ligne de sÃ©paration. Si plusieurs fichiers sont sÃ©lectionnÃ©s, un texte en noir indique que la valeur est commune Ã  tous les fichiers sÃ©lectionnÃ©s, tandis quâun texte en gris en indique le contraire. les valeurs en noir peuvent Ãªtre mises Ã  jour ou supprimÃ©es, tandis que celles en gris peuvent Ãªtre supprimÃ©es de ceux qui lâont, ou ajoutÃ©es aux autres.</Text>
+<Text id="309">Une icÃŽne de dossier peut apparaÃ®tre Ã  cÃŽtÃ© de certaines entrÃ©es de mÃ©ta-donnÃ©es. Ceci indique que les valeurs ont Ã©tÃ© hÃ©ritÃ©es dâun dossier parent. Les mÃ©ta-donnÃ©es hÃ©ritÃ©es ne peuvent Ãªtre Ã©ditÃ©es ou supprimÃ©es, mais seulement ajoutÃ©es ou Ã©crasÃ©es. Cliquer sur lâicÃŽne du dossier pour aller immÃ©diatement au dossier oÃ¹ la mÃ©ta-donnÃ©e est assignÃ©e.</Text>
+<Text id="310">Si vous cliquez sur un lâÃ©lÃ©ment de metadata du tableau, celui-ci affichera les valeurs existantes pour lâ Ã©lÃ©ment dans le domaine "Valeurs existantes pour..." en dessous du tableau. Celle-ci, dÃ©veloppe et comprime. Câest une liste qui, de faÃ§on usuelle, montre toutes les valeurs prÃ©cÃ©demment saisies pour un Ã©lÃ©ment sÃ©lectionnÃ©. Le clic sur une entrÃ©e la place automatiquement dans le champ valeur. Inversement, la saisie dans le champ texte sÃ©lectionne lâentrÃ©e de lâArborescence Valeur qui dÃ©bute avec les caractÃšres saisis. Appuyer sur [Tab] complÃšte automatiquement la saisie de la valeur sÃ©lectionnÃ©e.</Text>
+<Text id="311">Les valeurs de mÃ©ta-donnÃ©e peuvent Ãªtre organisÃ©es en une hiÃ©rarchie.Ceci est montrÃ© dans lâArborescence Valeur utilisant des dossiers de niveau interne. Les valeurs hiÃ©rarchiques peuvent Ãªtre saisies en utilisant le caractÃšre "|" pour sÃ©parer les niveaux. Par exemple, "Cards|Red|Diamonds|Seven" peut Ãªtre utilisÃ© dans une hiÃ©rarchie qui reprÃ©sente un jeu de cartes. Cela permet le rejeument des valeurs. Les jeux peuvent aussi Ãªtrre assignÃ©s comme mÃ©ta-donnÃ©e.</Text>
+<Text id="312">Greenstone extrait automatiquement des mÃ©ta-donnÃ©es Ã  partir des documents en un jeu de mÃ©ta-donnÃ©es dont les Ã©lÃ©ments sont prÃ©fixÃ©s "ex.". Ceci nâa aucune valeur et ne peut Ãªtre Ã©ditÃ©.</Text>
+</Content>
+</Part>
+<Part id="selecting_metadata_sets">
+<Title>
+<Text id="313">SÃ©lectionner les jeux de mÃ©ta-donnÃ©es</Text>
+</Title>
+<Content>
+<Text id="314">Les sÃ©ries dâÃ©lÃ©ments de mÃ©ta-donnÃ©es prÃ©dÃ©finis sont connus comme "jeux de MÃ©ta-donnÃ©es". "Dublin Core" en est un exemple. Quand on ajoute un Groupe de MÃ©ta-donnÃ©es Ã  la collection, ses Ã©lÃ©ments peuvent Ãªtre sÃ©lectionnÃ©s. On peut avoir plus dâun jeu de mÃ©ta-donnÃ©es ; pour Ã©viter des tÃ©lescopages de nom, un identificateur abrÃ©gÃ© qui identifie le jeu de mÃ©ta-donnÃ©es est suspendu au nom de lâÃ©lÃ©ment. Par exemple lâÃ©lement crÃ©ateur de Dublin Core devient "dc.Creator". Les jeux de mÃ©ta-donnÃ©es sont sauvÃ©gardÃ©s dans le dossier de mÃ©ta-donnÃ©es de lâInterface BibliothÃ©caire et ont le sufixe ".mds".</Text>
+<Text id="315">Pour contrÃŽler les jeux de mÃ©ta-donnÃ©es utilisÃ©s dans une collection, utilisez lâentrÃ©e "Jeux MÃ©ta-DonnÃ©es" sur la vue "Conception".</Text>
+</Content>
+</Part>
+<Part id="appending_new_metadata">
+<Title>
+<Text id="316">Ajout de Nouvelles MÃ©ta-donnÃ©es</Text>
+</Title>
+<Content>
+<Text id="317">On ajoute un Ã©lÃ©ment mÃ©ta-donnÃ©e â Ã©lÃ©ment et valeur Ã  la fois â Ã  un fichier. SÃ©lectionner dâabord le fichier Ã  partir de lâarborescence de fichier de la collection situÃ©e Ã  gauche. Cette action entraÃ®ne lâapparition de toute mÃ©ta-donnÃ©e prÃ©-assignÃ©e dans le tableau de droite.</Text>
+<Text id="318">SÃ©lectionner ensuite lâÃ©lÃ©ment mÃ©ta-donnÃ©e Ã  ajouter en cliquant sur sa rangÃ©e dans le tableau.</Text>
+<Text id="319">Taper la valeur dans le champ valeur. Utilisez le charactÃšre "|" pour rapporter une structure, comme dÃ©crit dans The Enrich View. Vous pouvez sauver lâ information metadata en pressant les touches [Up] ou [Down] et bouger ainsi la sÃ©lection convenablement. En pressant la touche [Enter] lâinformation metadata sera sauvÃ©e et une nouvelle entrÃ©e vide sera crÃ©Ã©e pour lâ Ã©lÃ©ment metadata, vous permettant dÃ©signer multiples valeurs pour un Ã©lÃ©ment de metadata.</Text>
+<Text id="320">Vous pouvez aussi ajouter des mÃ©ta-donnÃ©es Ã  un dossier, ou Ã  plusieurs fichiers sÃ©lectionnÃ©s Ã  la fois. Elle est ajoutÃ©e Ã  tous les fichiers ou Ã  lâintÃ©rieur du dossier ou de la sÃ©lÃ©ction, et aux sous-dossiers. Garder Ã  lâesprit que si des mÃ©ta-donnÃ©es sont ajoutÃ©es Ã  un dossier tous les nouveaux fichiers en son sein hÃ©rite automatiquement des valeurs du dossier.</Text>
+</Content>
+</Part>
+<Part id="adding_previously_defined_metadata">
+<Title>
+<Text id="321">Ajouter des MÃ©ta-donnÃ©es prÃ©dÃ©finies</Text>
+</Title>
+<Content>
+<Text id="322">Pour ajouter une mÃ©ta-donnÃ©e ayant une valeur existante, sÃ©lectionner dâabord le fichier, et ensuite la valeur requise Ã  partir de lâarborescence des valeurs, en dÃ©veloppant si nÃ©cessaire les dossiers de hiÃ©rarchie. La valeur de lâentrÃ©e sÃ©lectionnÃ©e apparaÃ®t automatiquement dans le champ texte Valeur. (Utiliser alternativement la valeur auto-select de lâarborescence et les caractÃ©ristiques auto-complÃštes.</Text>
+<Text id="323">La procÃ©dure dâajouter mÃ©ta-donnÃ©es avec des valeurs dÃ©jÃ  existantes aux dossiers ou aux fichiers multiples est tout Ã  fait identique.</Text>
+</Content>
+</Part>
+<Part id="editing_or_removing_metadata">
+<Title>
+<Text id="324">Editant ou Ãliminant MÃ©ta-donnÃ©es</Text>
+</Title>
+<Content>
+<Text id="325">Pour Ã©diter ou Ã©liminer une partie de metadata, premiÃšrement selectionnez un fichier convenable, en suite la valeur de la metadata du tableau. Editer la valeur de champ supprimant tout le texte si vous dÃ©sirez Ã©liminer la metadata.</Text>
+<Text id="326">Le processus est identique pour la mise Ã  jour dâun dossier avec des sous-dossiers ou plusieurs fichiers, mais vous pouvez seulement mettre Ã  jour les mÃ©ta-donnÃ©es qui sont communes Ã  tous les fichiers/dossiers sÃ©lectionnÃ©s.</Text>
+<Text id="327">Lâ arbre de valeurs montre toutes les valeurs actuellement assignÃ©es de mÃªme que les valeurs prÃ©cÃ©dentes pour la prÃ©sente session, toutes les valeurs Ã©ditÃ©s ou Ã©liminÃ©e seront donc prÃ©sentes dans lâ arbre. Fermant la collection et la ouvrant encore une fois Ã©liminera les valeurs qui ne sont plus dÃ©signÃ©es.</Text>
+</Content>
+</Part>
+<Part id="reviewing_assigned_metadata">
+<Title>
+<Text id="328">Passer en revue les MÃ©ta-donnÃ©es assignÃ©es</Text>
+</Title>
+<Content>
+<Text id="329">On Ã©prouve parfois le besoin de voir, Ã  la fois, les mÃ©ta-donnÃ©es affectÃ©es Ã  plusieurs ou Ã  tous les fichiers â par exemple, pour dÃ©terminer combien de fichiers sont en cours dâutilisation ou pour avoir une idÃ©e de la chronologie.</Text>
+<Text id="330">SÃ©lectionnez les fichiers que vous souhaitez examiner, puis clicquez sur le bouton droit et choisissez "MÃ©ta-donnÃ©es AssociÃ©es...". Une fenÃªtre appelÃ©e "Toutes les MÃ©ta-donnÃ©es", sous forme dâun grand tableau avec plusieurs colonnes, apparaÃ®t. La premiÃšre colonne montre les noms de fichiers ; les lignes montrent toutes les valeurs de mÃ©ta-donnÃ©es assignÃ©es Ã  ces fichiers.</Text>
+<Text id="331">Dessiner le tableau peut prendre quelque temps si plusieurs fichiers sont sÃ©lectionnÃ©s. On peut continuer Ã  utiliser lâInterface BibliothÃ©caire pendant que la fenÃªtre "Toutes MÃ©ta-donnÃ©es" est ouverte.</Text>
+<Text id="332">Quand il devient trop large, on peut filtrer le tableau "Toutes MÃ©ta-donnÃ©es" en appliquant des filtres aux colonnes. Alors que de nouveaux filtres sont ajoutÃ©s, seules les lignes qui concernent restent visibles. Pour installer, modifier ou effacer un filtre, cliquez sur lâÃ®cone "Funnel" situÃ© en haut de la colonne. Une information sur le filtre est rÃ©clamÃ©e. Une fois le filtre installÃ©, lâen-tÃªte de la colonne change de couleur.</Text>
+<Text id="333">La confirmation possÃšde un onglet "simple" et " advancÃ©". La version simple filtre les colonnes afin quâelles ne montrent que des lignes qui contiennent une certaine valeur de mÃ©ta-donnÃ©e ("*" concerne toutes les valeurs). On peut sÃ©lectionner des valeurs de mÃ©ta-donnÃ©es Ã  partir dâune liste dÃ©roulante. La version advancÃ©e permet diffÃ©rentes opÃ©rations dâharmonisation : doit commencer avec, ne contient pas, alphabÃ©tiquement et est Ã©gal Ã . La valeur Ã  harmoniser peut Ãªtre Ã©ditÃ©e et prise sous forme dâune chaÃ®ne quelconque (y compris "*"), et on peut opter pour une harmonisation insensible aux caractÃšres. Enfin, on peut spÃ©cifier une deuxiÃšme condition dâharmonisation prÃ©cisant une gamme de valeurs (en sÃ©lectionnant AND) ou des valeurs alternatives (en selectionnant OR). En dessous de cette zone, une boÃ®te qui permet de changer lâordre de tri (ascendant ou descendant) est placÃ©e. Enfin, cliquer sur "Installer Filtre" pour appliquer le nouveau filtre Ã  la colonne. Cliquer sur "Effacer Filtre" pour enlever le filtre courant. Notez que les dÃ©tails du filtre sont retenus mÃªme si le filtre est effacÃ©.</Text>
+<Text id="334">Par exemple, pour trier le tableau "Toutes MÃ©ta-donnÃ©es" , choisir une colonne, sÃ©lectionner le cadre du filtre par dÃ©faut (Un filtre simple sur "*") et choisir un ordre ascendant ou descendant.</Text>
+</Content>
+</Part>
+<Part id="importing_previously_assigned_metadata">
+<Title>
+<Text id="335">Importer des MÃ©ta-donnÃ©es PrÃ©-assignÃ©es</Text>
+</Title>
+<Content>
+<Text id="336">Cette section explique comment importer des mÃ©ta-donnÃ©es affectÃ©es prÃ©cÃ©demment ; mÃ©ta-donnÃ©es affectÃ©es avant dâÃªtre ajoutÃ©es Ã  la collection.</Text>
+<Text id="337">Si la mÃ©ta-donnÃ©e dans une forme reconnue par lâInterface BibliothÃ©caire a Ã©tÃ© prÃ©alablement assignÃ©e Ã  un fichier, â par exemple, quand on choisit des documents dans une collection Greenstone existante â elle est importÃ©e automatiquement quand on ajoute le fichier. Pour ce faire, la mÃ©ta-donnÃ©e doit Ãªtre ajustÃ©e au jeu de mÃ©ta-donnÃ©es disponibles dans la collection.</Text>
+<Text id="338">LâInterface BibliothÃ©caire confirme lâinformation nÃ©cessaire. confirmation sous forme dâinstructions brÃšves et qui montre ensuite le nom de lâÃ©lÃ©ment mÃ©ta-donnÃ©e qui est importÃ©e, comme il apparaÃ®t dans le fichier source. Ce champ ne peut Ãªtre ni Ã©ditÃ© ni changÃ©. Ensuite on choisit sur quel jeu de mÃ©ta-donnÃ©e le nouveau Ã©lÃ©ment devrait Ãªtre calquÃ© et enfin lâÃ©lÃ©ment mÃ©ta-donnÃ©e appropriÃ©. Le sytÃšme selectionne automatiquement le meilleur ajustement, en terme de jeu et dâÃ©lÃ©ment pour la nouvelle mÃ©ta-donnÃ©e.</Text>
+<Text id="339">AprÃšs cela,on peut choisir "Ajouter" pour ajouter le nouvel Ã©lÃ©ment mÃ©ta-donnÃ©e au jeu de mÃ©ta-donnÃ©es choisi. (Ceci nâest possible que si aucun Ã©lement de mÃªme nom nâest prÃ©sent Ã  lâinterieur du jeu choisi.) "Fusionner" applique le nouvel Ã©lement Ã  celui choisi par lâutilisateur. Enfin, "Ignorer" nâimporte aucune mÃ©tadonnÃ©e avec ce nom dâÃ©lement. Une fois prÃ©cisÃ©e la maniÃšre dâimporter un certain Ã©lÃ©ment de mÃ©ta-donnÃ©e, lâinformation dâapplication est retenue pour la durÃ©e de vie de la collection.</Text>
+<Text id="340">Pour des dÃ©tails concenant les fichiers mÃ©ta-donnÃ©e.xml que Greenstone utilise pour sauvegarder les mÃ©ta-donnÃ©es, il faut vous refÃ©rer au chapitre 2 du guide du DÃ©veloppeur de Greenstone â "Exploitez vos documents au maximum".</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="designing_your_collection_appearance">
+<Title>
+<Text id="341">DÃ©coration de lâapparence de votre collection</Text>
+</Title>
+<Content>
+<Text id="342">Une fois les fichiers marquÃ©s avec les mÃ©ta-donnÃ©es, on peut dÃ©cider comment ils devraient apparaÃ®tre aux utilisateurs comme une collection Greenstone. Quel type dâinformation peut Ãªtre recherchÃ© ? Quels sont les moyens qui sont fournis pour naviguer Ã  travers les documents ? Quels sont les langages supportÃ©s ? oÃ¹ apparaissent les boutons sur la page ? ces choses peuvent Ãªtre adaptÃ©es ; cette section dÃ©crit comment procÃ©der.</Text>
+<Part id="the_design_view">
+<Title>
+<Text id="343">LâAffichage conception</Text>
+</Title>
+<Content>
+<Text id="344">Cette section prÃ©sente lâaffichage de conception et explique comment on navigue entre les diffÃ©rents affichages Ã  lâintÃ©rieur de cette vitrine.</Text>
+<Text id="345">Avec lâInterface BibliothÃ©caire, on peut configurer la faÃ§on dont la collection va apparaÃ®tre Ã  lâutilisateur. Les options de configuration sont divisÃ©es en diffÃ©rentes sections, chacune associÃ©e Ã  une Ã©tape particuliÃšre de navigation ou de prÃ©sentation dâinformation.</Text>
+<Text id="346">Sur la gauche est placÃ©e une liste de diffÃ©rents affichages et Ã  droite les commandes associÃ©es Ã  celles en cours. Pour passer Ã  un affichage diffÃ©rent, cliquer son nom dans la liste.</Text>
+<Text id="347">Pour comprendre les diffÃ©rentes Ã©tapes et les termes implmiquÃ©s dans la conception dâune collection, lire les chapitres 1 et 2 de Greenstoneâs Developerâs Guide.</Text>
+</Content>
+</Part>
+<Part id="general">
+<Title>
+<Text id="348">GÃ©nÃ©ral</Text>
+</Title>
+<Content>
+<Text id="349">Cette section explique comment passer en revue et changer les rÃ©glages gÃ©neraux associÃ©s Ã  la collection. Dâabord, sous "Design section" cliquer "General".</Text>
+<Text id="350">Les valeurs fournies ici peuvent Ãªtre modifiÃ©es au cours de la crÃ©ation de la collection.</Text>
+<Text id="351">Dâabord, les contacts E-mail du crÃ©ateur et mainteneur de la collection. Le champ suivant permet le changement de titre de la collection. Le dossier dans lequel est enregistrÃ© la collection est affichÃ© ensuite, mais ne peut Ãªtre Ã©ditÃ©. Celui qui suit spÃ©cifie (sous forme dâURL) lâÃ®cone Ã  montrer Ã  lâextrÃ©mitÃ© supÃ©rieure gauche de la page "About" de la collection et la suivante est lâÃ®cone utilisÃ©e dans la page de la bibliothÃ©que Greenstone Ã  lier Ã  la collection. Puis, une case permet de contrÃŽler si la collection est accessible au public. Enfin, la zone texte de "la description de la Collection" comme dÃ©crit CrÃ©er une nouvelle collection.</Text>
+</Content>
+</Part>
+<Part id="document_plugins">
+<Title>
+<Text id="352">Plugiciels de Document</Text>
+</Title>
+<Content>
+<Text id="353">Cette section dÃ©crit comment faire la configuration des plugiciels des documents que la collection utilise. Elle explique comment spÃ©cifier les plugiciels utilisÃ©s, quels paramÃštres leur passer et dans quel ordre ils se dÃ©roulent. Sous "Sections de conception", cliquer "Plugiciels de document".</Text>
+<Text id="354">Pour ajouter un plugiciel, sÃ©lectionner-le sur la liste dÃ©roulante de "Choisir le plugiciel Ã  ajouter" situÃ©e Ã  cÃŽtÃ© du bouton et ensuite cliquer "Ajouter plugiciel". Une fenÃªtre dÃ©nommÃ©e "Configurer les arguments" apparaÃ®t ; elle est dÃ©crite plus loin. Une fois la configuration du nouveau plugiciel achevÃ©e, il est ajoutÃ© Ã  la fin de la liste "Plugiciels couramment assignÃ©s". Veuillez noter que, Ã  lâexception de UnknownPlug, chaque plugin ne peut apparaÃ®tre quâune seule fois dans la liste.</Text>
+<Text id="355">Pour enlever un plugiciel, sÃ©lectionner-le sur la liste et cliquer sur "Enlever plugiciel".</Text>
+<Text id="356">Les plugiciels sont configurÃ©s en fournissant des arguments. Pour les changer, il faut sÃ©lectionner le plugiciel Ã  partir de la liste et cliquer "Configurer plugiciel" (Ou double-cliquer sur le plugiciel). Un dialogue "Configuration des arguments" apparaÃ®t avec diffÃ©rent contÃŽles pour spÃ©cifier les arguments.</Text>
+<Text id="357">Il existe plusieurs types de contrÃŽles. Certains sont des boÃ®tes de dialogue et cliquer sur lâune ajoute lâoption appropriÃ©e au plugiciel. Les autres sont des chaÃ®nes de textes avec une boÃ®te de dialogue et un champ texte. Cliquer sur la boÃ®te pour activer lâargument, ensuite saisir le texte appropriÃ© dans la boÃ®te (expression normale, chemin de fichier etc). Les autres sont des menus dÃ©roulants Ã  partir desquels on peut sÃ©lectionner Ã  partir dâune sÃ©rie de valeurs dÃ©terminÃ©es. Pour apprendre ce quâun argument peut faire, promener la souris planer sur son nom pendant un instant une description apparaÃ®tra.</Text>
+<Text id="358">Pour changer la configuration, cliquer sur "OK" pour valider et fermer la boÃ®te de dialogue, ou "Annuler" pour fermer la boÃ®te de dialogue sans changer les arguments du plugiciel.</Text>
+<Text id="359">Les plugiciels dans la liste sont executÃ©s en ordre et lâordre est parfois important. Lâ ordre des classificateurs ne peut Ãªtre changÃ© que dans la Librairie de SystÃšmes SpÃ©cialistes et modes Experts (voir PrÃ©fÃ©rences).</Text>
+</Content>
+</Part>
+<Part id="search_types">
+<Title>
+<Text id="360">Types de recherche</Text>
+</Title>
+<Content>
+<Text id="361">cette section explique comment modifier une nouvelle caractÃ©ristique de conception dans Greenstone, Types de recherche, qui permet une recherche de champ. Les types de recherche spÃ©cifient le type dâinterface de recherche Ã  fournir : formulaire, recherche par champs et/ou recherche simple. Sous "Sections de conception", cliquer sur "Types de recherche".</Text>
+<Text id="362">Lorsquâon pÃ©nÃštre dans lâaffichage Types de recherche, vÃ©rifier dâabord "Activer recherches avancÃ©es", qui active les autres contrÃŽles. Ceci change la collection Ã  utiliser un mÃ©chanisme dâ indexage qui permet une recherche de champs. La spÃ©cification de lâ indexe est lÃ©gÃšrement diffÃ©rente dans ce mode. (Quand Ã©changeant entre une recherche classique ou avancÃ©e, le GLI essaye de convertir la spÃ©cification de lâ indexe, mais peut ne pas le faire correctement.)</Text>
+<Text id="363">pour ajouter un type de recherche, sÃ©lectionner-le Ã  partir de la liste "Types de recherche" et cliquer sur "Ajouter Type de recherche". Chaque type nâapparaÃ®t quâune fois sur la liste. La premiÃšre recherche sera de type dÃ©faut et apparÃªtra dans la page de recherche de la conection Ã©tablie. Tout les autres pourons Ãªtre sÃ©lectionÃ©s dans la page de prÃ©fÃ©rences.</Text>
+<Text id="364">Pour enlever un type de recherche, il faut le selectionner Ã  partir de la liste "Currently Assigned Search type" et cliquer sur "Enlever type de recheche". La liste doit contenir au moins un type de recherche.</Text>
+</Content>
+</Part>
+<Part id="search_indexes">
+<Title>
+<Text id="365">Index de recherche</Text>
+</Title>
+<Content>
+<Text id="366">Les index prÃ©cisent les parties de la collection qui doivent Ãªtre recherchÃ©es. Cette section explique comment ajouter et enlever des index et fixer un index par dÃ©faut. Sous "Sections de conception", cliquer sur "Rechercher Index".</Text>
+<Text id="367">Pour ajouter un index, taper un nom choisi dans le champ "Nom de lâIndex". Selectionner les sources dâinformation Ã  indexer en cliquant les boÃ®tes de dialogue Ã  cÃŽtÃ© dâeux. La liste montre aussi bien tous les Ã©lÃ©ments de mÃ©ta-donnÃ©es assignÃ©s, que le texte entier. AprÃšs avoir sÃ©lectionnÃ© les sources de donnÃ©es, choisir la granularitÃ© de lâindex en utilisant le menu "Au niveau". Une fois ces dÃ©tails completÃ©s, "Ajouter Index" devient actif (Ã  moins quâil nâait un index existant avec les mÃªmes paramÃštres). Cliquez pour ajouter un nouvel index.</Text>
+<Text id="368">Pour Ã©diter un index, sÃ©lectionnez-le et changez les dÃ©tails de lâindex, puis clicquez sur "Remplacer lâindex".</Text>
+<Text id="369">Pour enlever un index, il faut le sÃ©lectionner sur la liste dâindex assignÃ©s et cliquer "Enlever index".</Text>
+<Text id="370">Pour crÃ©er un indexe couvrant texte et toute metadata, cliquez sur "Ajouter Tout".</Text>
+<Text id="371">Lâindex par dÃ©faut, celui qui est utilisÃ© dans la page de recherche de la collection est labellÃ© parc "[Index par dÃ©faut]" dans la liste "Index assignÃ©s".</Text>
+<Text id="372">Si la recherche avancÃ©e est activÃ©e (voir Affichage des types de recherche), les contrÃŽles dâindex sont diffÃ©rents. Il existe une nouvelle pseudo-source de donnÃ©es "Tous champs" qui fournit une recherche Ã  travers tous les index spÃ©cifiÃ©s Ã  la fois. Des niveaux ne sont pas assignÃ©s Ã  un index spÃ©cifique, mais sâapplique Ã  tous les index : ainsi index et niveaux sont ajoutÃ©s sÃ©parement. "Ajouter Tout" crÃ©e un indexe sÃ©parÃ© pour chaque champ de metadata dans ce mode.</Text>
+<Text id="373">Le nom de chaque index sera en dÃ©faut pour le nom de source. Pour changer le nom, SÃ©lectionner un index, changer ses dÃ©tails et cliquez "Remplacer Index".</Text>
+</Content>
+</Part>
+<Part id="partition_indexes">
+<Title>
+<Text id="374">Index de Partition</Text>
+</Title>
+<Content>
+<Text id="375">Les index sont construits sur un texte particulier ou des sources MÃ©ta-donnÃ©es. Lâespace de recherche peut Ãªtre plus tard contrÃŽlÃ© en morcelant lâindex soit par langage ou par filtre choisi Ã  lâavance. Cette section en dÃ©crit la procÃ©dure. Sous "Sections de conception", cliquer "Index de Partition".</Text>
+<Text id="376">Lâaffichage "Index de Partition" possÃšde trois onglets : "DÃ©finir les Filtres", "Assigner une partition" et "Assigner des langages". Pour en savoir davantage sur les partitions, lire sur les sous collections et les sous index au chapitre 2 de Greenstone developerâs guide.</Text>
+<Text id="377">La fenÃªtre des Indexes de Partition est seulement Ã©tablie dans la Librairie de SystÃšmes SpÃ©cialistes et modes Experts (voir PrÃ©fÃ©rences). Notez que le nombre total de partitions gÃ©nÃ©rÃ©es est une combinaison de tous les indexes, des filtres de sous colection et des langues choisis. Deux indexes avec deux filtres de sous-collections dans deux langues donnent huit partitions dâindex.</Text>
+</Content>
+</Part>
+<Part id="define_filters">
+<Title>
+<Text id="378">DÃ©finir les Filtres</Text>
+</Title>
+<Content>
+<Text id="379">Les filtres permettent de jeur en sous-collection tous les documents dans un index pour laquelle une valeur mÃ©ta-donnÃ©e correspond Ã  un type donnÃ©.</Text>
+<Text id="380">Pour crÃ©er un filtre, cliquer sur le bouton "DÃ©finir les Filtres" et entrer un nom pour le nouveau filtre dans le champ "Nom du filtre de sous collection". Ensuite choisir un attribut de document Ã  faire correspondre soit avec lâÃ©lÃ©ment de mÃ©ta-donnÃ©e soit avec le nom du fichier en question. Saisir une expression courante quâil faut utiliser durant la correspondance. Vous pouvez choisir entre "Inclure" les documents qui correspondent au fichier ou les "Exclure". Enfin, on peut spÃ©cifier lâun quelconque des drapeaux standard PERL dâexpression courante quâil faut utiliser pour la correspondance (par exemple "i" pour les correspondances ne tenant pas compte des caractÃšres.) Pour finir, cliquez sur "Ajouter un Filtre" pour ajouter le filtre Ã  la liste "Filtres de sous collection dÃ©finis".</Text>
+<Text id="381">Pour enlever un filtre, sÃ©lectionner-le sur la liste et cliquer sur "Enlever Filtre".</Text>
+<Text id="382">Pour changer un filtre, sÃ©lectionner-le sur la liste, changer lâune quelconque des valeurs apparaissant dans les contrÃŽles dâÃ©dition et cliquer sur "Remplacer Filtre" pour valider les modifications.</Text>
+</Content>
+</Part>
+<Part id="assign_partitions">
+<Title>
+<Text id="383">Assigner des Partitions</Text>
+</Title>
+<Content>
+<Text id="384">AprÃšs avoir dÃ©fini un filtre de sous-collection, utiliser lâonglet "Assigner des Partitions" pour construire ses indexes (ou ceux pour un jeu de filtres.) SÃ©lectionner le filtre (ou les filtres) de votre choix Ã  partir de la liste "DÃ©finir des Filtres de Sous-collection", entrer un nom pour la partition dans le champ "Nom de Partition Name", et cliquer sur "Ajouter Partition".</Text>
+<Text id="385">Pour supprimer une partition, sÃ©lectionner-la Ã  partir de la liste et cliquer sur "Enlever Partition".</Text>
+<Text id="386">Pour faire dâune partition celle par dÃ©faut, sÃ©lectionner-la Ã  partir de la liste et cliquer sur "Par DÃ©faut".</Text>
+</Content>
+</Part>
+<Part id="assign_languages">
+<Title>
+<Text id="387">Assigner Langages</Text>
+</Title>
+<Content>
+<Text id="388">Cette section donne les dÃ©tails de la maniÃšre de restreindre les index Ã  des langages particuliers. On le fait en gÃ©nÃ©rant une partition par le biais de lâonglet "Assigner Langages" de lâAffichage "Index de Partition".</Text>
+<Text id="389">Pour ajouter un nouveau langage, dont la partition par le biais de lâonglet "Assigner langues" confÃšre un index, SÃ©lectionner le langage souhaitÃ© Ã  partir de la liste "Langage Ã  ajouter" et cliquer sur "Ajouter langue".</Text>
+<Text id="390">Pour supprimer une langue, sÃ©lectionner-la Ã  partir de la liste "SÃ©lection de Langage" et cliquer sur "Enlever Langage".</Text>
+<Text id="391">Pour installer un language par dÃ©faut, sÃ©lectionner-la dans la liste et cliquez sur "Par dÃ©faut".</Text>
+</Content>
+</Part>
+<Part id="cross-collection_search">
+<Title>
+<Text id="392">Recherches Ã  travers collections</Text>
+</Title>
+<Content>
+<Text id="393">Greenstone peut rechercher dans plusieurs collections comme si elles nâen constituaient quâune. Ceci est fait en spÃ©cifiant une liste dâ une autre collection Ã  rechercher au mÃªme temps que celle en recherche. Sous "Sections de conception", cliquez sur "Recherche unique Ã  travers plusieurs collections".</Text>
+<Text id="394">LâAffichage de Recherche unique Ã  travers des collections montre une liste de collections disponibles. La collection courante est cochÃ©e et ne peut Ãªtre dÃ©-sÃ©lectionnÃ©e. Pour ajouter une autre collection quâon peut rechercher parallÃšlement, cliquer sur une collection dans la liste (cliquer une deuxiÃšme fois pour lâenlever). Lorsquâune seule collection est sÃ©lectionnÃ©e, aucune recherche Ã  travers collections nâest possible.</Text>
+<Text id="395">Si les collections individuelles nâont pas les mÃªmes indexes (y compris les les partitions de sous-collection et les partitions de language), la recherche ne pourra pas fonctionner. Lâutilisateur ne pourra alors quâeffectuer des recherches en utilisant les indexes communs Ã  toutes les collections.</Text>
+<Text id="396">Pour plus de dÃ©tails, voir Chapitre 1 du Guide du DÃ©veloppeur Greenstone.</Text>
+</Content>
+</Part>
+<Part id="browsing_classifiers">
+<Title>
+<Text id="397">Classificateurs de navigation</Text>
+</Title>
+<Content>
+<Text id="398">Cette section explique comment assigner Ã  une collection des "classificateurs" qui sont utilisÃ©s pour naviguer. Sous la section "Sections de conception", cliquer sur "Classificateurs de navigation".</Text>
+<Text id="399">Pour ajouter un classificateur, sÃ©lectionner-le en utilisant la liste dÃ©roulante "Choisir classificateur Ã  ajouter" et cliquer sur "Ajouter Classificateur". une fenÃªtre qui sâintitule "Configurer Arguments" apparaÃ®t ; les instructions concernant ce dialogue sont les mÃªmes que pour les plugiciels (voir plugiciels de Documents). Une fois le nouveau classificateur configurÃ©, il sâajoute Ã  la fin de la liste des "Classificateurs couramment AssignÃ©s".</Text>
+<Text id="400">Pour supprimer un classificateur, sÃ©lectionner-le dans la liste et cliquez sur "Supprimer Classificateur".</Text>
+<Text id="401">Pour changer les arguments dâun classificateur, sÃ©lectionner-le sur la liste et cliquer sur "Configurer Classificateur" (ou double-cliquer sur le classificateur sur la liste.)</Text>
+<Text id="402">Le tri des classificateurs dans la barre de navigation de la collection est fourni ici dans lâordre des classificateurs. Pour le changer, sÃ©lectionner le classificateur Ã  dÃ©placer et cliquer sur "DÃ©placer vers le haut" ou "DÃ©placer vers le bas".</Text>
+<Text id="403">Pour plus dâinformations sur les classificateurs lisez le chapitre 2 du Guide du DÃ©veloppeur Greenstone â Exploitez vos documents au maximum.</Text>
+</Content>
+</Part>
+<Part id="format_features">
+<Title>
+<Text id="404">CaractÃ©ristiques de Format</Text>
+</Title>
+<Content>
+<Text id="405">Les pages web que vous voyez en utilisant Greenstone ne sont pas prÃ©-stockÃ©s mais sont gÃ©nÃ©rÃ©es âÃ  la volÃ©eâ au fur et Ã  mesure quâon en fait appel. Les commandes de format sont utilisÃ©es pour changer lâapparence de ces pages gÃ©nÃ©rÃ©es. Ils influencent le lieu dâapparition des boutons lorsquâun document est affichÃ©, et dÃ©terminent les liens qui sont affichÃ©s par le classificateur DateList. Les commandes de format ne sont pas faciles Ã  concevoir, et la lecture du chapitre 2 de Greenstone Developerâs Guide est recommandÃ©e. Cette section concerne les cadres de format, et indique comment lâInterface BibliothÃ©caire en fournit lâaccÃšs. Sous "Sections de conception", cliquer sur "CaractÃ©ristiques de Format".</Text>
+<Text id="406">On peut appliquer une commande de format Ã  nâimporte quoi dans la liste dÃ©roulante "Choisir CaractÃ©ristique" qui comprend tous les classificateurs de mÃªme quâune liste prÃ©dÃ©finie de caractÃ©ristiques. Deux types de contrÃŽles existent lorsquâon sÃ©lectionne une caractÃ©ristique : Certaines caractÃ©ristiques sont simplement activÃ©es ou dÃ©sactivÃ©es, et le contrÃŽle se fait grÃ¢ce Ã  une liste de vÃ©rification. Dâautres requiÃšrent quâon spÃ©cifie une chaÃ®ne de format. Pour ces caractÃ©ristiques, il existe une liste de retrait ("Composante AffectÃ©e") pour la sÃ©lection des parties de la caraxtÃ©ristique oÃ¹ sâapplique la chaÃ®ne (si nÃ©cessaire), une zone de texte ("ChaÃ®ne de Format HTML") oÃ¹ on saisit la chaÃ®ne, et une sÃ©lection de "Variables" prÃ©dÃ©finies. Pour insÃ©rer une variable dans la position courante dans la chaÃ®ne de format, sÃ©lectionner la Ã  partir de la liste de retrait et cliquer sur "InsÃ©rer".</Text>
+<Text id="407">Vous pouvez spÃ©cifier un format par dÃ©faut pour une composante particuliÃšre en sÃ©lectionnant la caractÃ©ristique vierge.Ce format est alors appliquÃ© Ã  toutes les caractÃ©ristiques applicables sauf instruction contraire.</Text>
+<Text id="408">Pour ajouter une nouvelle commande de format, remplir lâinformation comme indiquÃ©e plus haut et cliquer sur "Ajouter Format". La nouvelle commande de Format apparaÃ®t dans la liste des "Commandes de Format frÃ©quemment AssignÃ©es". Seule une commande de format peut Ãªtre assignÃ©e pour chaque combinaison caractÃ©ristique/ composante.</Text>
+<Text id="409">Pour enlever une commande de format, sÃ©lectionner-la sur la liste et cliquer "Enlever Format".</Text>
+<Text id="410">Pour modifier une commande de format, sÃ©lectionner-la sur la liste et cliquer sur "Remplacer Format".</Text>
+<Text id="411">Pour de plus amples informations sur les variables et les composantes de caractÃ©ristiques, lire le chapitre 2 du Guide du DÃ©veloppeur de Greenstone.</Text>
+<Text id="412">Si la boÃ®te de vÃ©rification "Permettre options Ã©tendues" est cochÃ©e, certaines options avancÃ©es de formatage sont activÃ©es. La liste des caractÃ©ristiques pouvant Ãªtre formatÃ©es est lÃ©gÃšrement changÃ©e, et plusieurs variables sont disponibles dans la commande de format, offrant un contrÃŽle plus grand sur la mise en forme.</Text>
+</Content>
+</Part>
+<Part id="translate_text">
+<Title>
+<Text id="413">Traduire Texte</Text>
+</Title>
+<Content>
+<Text id="414">Cette section dÃ©crit lâAffichage de traduction, oÃ¹ on peut dÃ©finir des fragments de texte spÃ©cifiques Ã  un langage pour des parties de lâinterface de la collection. Sous "Sections de conception", cliquer sur "Traduire Texte".</Text>
+<Text id="415">Choisir dâabord une entrÃ©e dans la liste "CaractÃ©ristiques". Les chaÃ®nes spÃ©cifiques Ã  un langage associÃ©es Ã  la caractÃ©ristiques apparaissent en bas. Utiliser la liste dÃ©roulante de "Traduction de Langage" pour sÃ©lectionner le langage cible, et saisir le texte traduit dans la zone de texte, en se refÃ©rant Ã  "Fragment de Texte Initial" si nÃ©cessaire. Cliquez sur "Ajouter Traduction" Ã  la fin de lâopÃ©ration.</Text>
+<Text id="416">Pour supprimer une traduction existante, sÃ©lectionner-la Ã  partir du tableau "Traduction AssignÃ©e" et cliquer sur "Enlever Traduction".</Text>
+<Text id="417">Pour Ã©diter une traduction, sÃ©lectionner-la et Ã©diter-la dans la zone de texte "Texte Traduit", et cliquer sur "Remplacer Traduction".</Text>
+</Content>
+</Part>
+<Part id="metadata_sets">
+<Title>
+<Text id="418">jeux de MÃ©ta-donnÃ©es</Text>
+</Title>
+<Content>
+<Text id="419">Cette section explique le panel de visualisation du jeu de mÃ©ta-donnÃ©es. Sous "Sections de conception", cliquer sur "jeux de MÃ©ta-donnÃ©es".</Text>
+<Text id="420">Cette fenÃªtre sert Ã  la revue des jeux de mÃ©ta-donnÃ©es utilisÃ©s dans la collection, et les Ã©lÃ©ments qui sont disponibles dans chaque jeu. Choisir dans la liste de "jeux de mÃ©ta-donnÃ©es disponibles" pour voir des informations dÃ©taillÃ©es Ã  ces Ã©lÃ©ments.</Text>
+<Text id="421">Pour utiliser un autre jeu de mÃ©ta-donnÃ©es avec la collection chargÃ©e, clicquez sur "Ajouter un jeu de mÃ©ta-donnÃ©es" et sÃ©lectionnez le fichier mÃ©ta-donnÃ©es (.mds) pour le nouveau jeu mÃ©ta-donnÃ©es.</Text>
+<Text id="422">LâÃ©dition de jeux mÃ©ta-donnÃ©es se fait avec lâÃ©diteur Greenstone de mÃ©ta-donnÃ©es (GEMS). En clicquant sur le bouton "Ãditer un jeux mÃ©ta-donnÃ©es" vous obtiendrez des informations sur lâutilisation de GEMS.</Text>
+<Text id="423">Si vous nâavez plus besoin dâun jeu mÃ©ta-donnÃ©es, sÃ©lectionnez le et clickez sur "Suppression du jeu mÃ©ta-donnÃ©es" pour lâenlever. Si vous avez affecttÃ© des mÃ©tadonnÃ©es aux Ã©lÃ©ments du jeu supprimÃ©, on vous demandera ce que vous voulez en faire lorsque vous allez ouvrir Ã  nouveau cette collection.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="producing_your_collection">
+<Title>
+<Text id="424">Pour produire votre collection</Text>
+</Title>
+<Content>
+<Text id="425">AprÃšs avoir rassemblÃ© les documents de la collection, les avoir annotÃ©s avec les mÃ©ta-donnÃ©es, et dÃ©fini comment la collection va apparaÃ®tre, la production de la collection en utilisant Greenstone est alors possible. Cette section vous en explique la maniÃšre.</Text>
+<Part id="the_create_view">
+<Title>
+<Text id="426">LâAffichage CrÃ©er</Text>
+</Title>
+<Content>
+<Text id="427">LâAffichage CrÃ©er est utilisÃ© pour crÃ©er la collection en mettant en oeuvre les scripts Greenstone relatifs Ã  cette opÃ©ration. En cliquant sur "Construire Collection", on initie le processus de construction de la collection. Sa durÃ©e dÃ©pend de la taille de la collection et du nombre dâindex Ã  crÃ©er (pour les grandes collections cela peut prendre des heures). Une barre dâÃ©tat indique ou on en est dans le processus. Pour annuler le processus Ã  tout moment, cliquer sur "Annuler Construction".</Text>
+<Text id="428">Quand la collection est construite, appuyant "Preview Collection" initiera la page web hebergeant la collection.</Text>
+<Text id="429">En mode expert, vous pouvez utiliser lâentrÃ©e "Message Log" Ã  gauche pour revoir les tentatives prÃ©cÃ©dentes de construction de la collection avec ou san succÃ©s. SÃ©lectionnez le journal souhaitÃ© en cliquant sur la date correspondante dans la liste "Historique du Journal".</Text>
+</Content>
+</Part>
+<Part id="import_and_build_settings">
+<Title>
+<Text id="430">ParamÃštres dâImportation et de Construction</Text>
+</Title>
+<Content>
+<Text id="431">Cette section explique comment accÃ©der aux diffÃ©rents paramÃštres de construction et dâimportation. Pour plus dâinformations sur lâimportation et la construction lire le chapitre 1 du Guide du DÃ©veloppeur de Greenstone â Comprendre le processus de construction de la collection.</Text>
+<Text id="432">Le contrÃŽle des diffÃ©rents paramÃštres se fait de faÃ§on identique Ã  la fenÃªtre "Configurer Arguments" dÃ©crit dans la section Plugiciels de documents. Certains champs requiÃšrent des arguments numÃ©riques, et on peut : soit les incorporer en les saisissant, soit utiliser les flÃšches Haut et Bas pour augmenter ou diminuer la valeur prÃ©sente (dans certains cas, lâinterface limite la classe quâon peut entrer.) Dâautres sont activÃ©s en cliquant sur une case de vÃ©rification (re-cliquer pour dÃ©sactiver.)</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="miscellaneous">
+<Title>
+<Text id="433">Miscellaneous</Text>
+</Title>
+<Content>
+<Text id="434">Cette section dÃ©crit les caractÃ©ristiques de lâInterface BibliothÃ©caire qui ne sont pas associÃ©es Ã  une fenÃªtre dâaffichage particuliÃšre.</Text>
+<Part id="preferences">
+<Title>
+<Text id="435">PrÃ©fÃ©rences</Text>
+</Title>
+<Content>
+<Text id="436">Cette section explique le dialogue des prÃ©fÃ©rences, auquel on accÃšde en ouvrant "Fichier" -&gt; "PrÃ©fÃ©rences".</Text>
+<Text id="437">La premiÃšre option "General" est un champ texte pour saisir votre adresse courriel. Ceci sera utilisÃ© pour les Ã©lÃ©ments mÃ©ta-donnÃ©es "crÃ©ateur" et "Mainteneur" de la collection. Lâoption suivante est un liste dÃ©roulante des langues dans lesquelles lâinterface bibiothÃšquaire peut Ãªtre affichÃ©e. Si on change le dictionnaire par le choix dâun autre sur la liste, on doit redÃ©marrer lâInterface BibliothÃ©caire pour charger les chaÃ®nes du nouveau langage Ã  partir du dictionnaire.</Text>
+<Text id="438">Si on coche "Affichage MÃ©ta-donnÃ©es Ã©tendues", les diffÃ©rents contrÃŽles relatifs aux mÃ©ta-donnÃ©es affichent toujours toutes les mÃ©ta-donnÃ©es qui ont Ã©tÃ© extraites automatiquement des documents. Lorsquâon le dÃ©sÃ©lectionne, ces mÃ©ta-donnÃ©es sont cachÃ©es (bien quâelles restent disponibles pendant la conception de la collection, et dans la collection Greenstone finale.) Si on coche "Montrer les tailles des fichiers", la taille du fichier apparaÃ®t Ã  cÃŽtÃ© de chaque fichier dans lâespace de travail et dans les arborescences de fichiers de la collection dans les Affichages Rassembler et Enrichir.</Text>
+<Text id="439">Le panneau "Mode" est utilisÃ© pour contrÃŽler le niveau du dÃ©tail dans lâinterface. Dans sa configuration la plus basse, "Librarian Assistant", la vue de dÃ©coration, est dÃ©sactivÃ©e, les arguments qui requiÃšrent des expressions ordinaires sont cachÃ©s, et la construction de la collection produit un enregistrement minimal dâÃ©vÃšnements. Par contre, la configuration la plus Ã©levÃ©e, "Expert", donne lâaccÃšs Ã  toutes les fonctionnalitÃ©s de dÃ©coration, y compris le positionnement de plugin, et les arguments dâexpressions ordinaires ; elle permet aussi lâenregistrement de lâintÃ©gralitÃ© des messages lors de la construction de la collection. Pour changer ou revoir les modes, cliquez sur le bouton radio situÃ© Ã  cÃŽtÃ© du mode qui vous intÃ©resse. Vous pouvez contrÃŽler rapidement le mode dans lequel vous vous trouvez en regardant la barre de titre de Librarian Interface.</Text>
+<Text id="440">LâInterface BibliothÃ©caire est capable de supporter diffÃ©rents flux de travail en dÃ©terminant lesquels des diffÃ©rents onglets dâaffichage sont visibles. Utiliser lâonglet "Workflow" pour adapter les fenÃªtres dâaffichage disponibles en cochant les boÃ®tes qui sont Ã  cÃŽtÃ© des affichages souhaitÃ©s. On peut aussi utiliser la liste dÃ©roulante pour sÃ©lectionner des configurations prÃ©dÃ©terminÃ©es. La fermeture du dialogue des prÃ©fÃ©rences Ã©tablit ces paramÃštres de workflow (flux de travail). Ces paramÃštres sont emmagasinnÃ©s dans la collection, et non dans le fichier de configuration de lâInterface BibliothÃ©caire.</Text>
+<Text id="441">Lâonglet "Connexion" permet changer le chemin vers le serveur de bibliothÃšque local basÃ© sur Greenstone et utilisÃ© dans lâaperÃ§u des collections. Vous pouvez aussi prÃ©ciser le proxy de connection internet (c.a.d. pour lÃ©lÃ©charger les fichiers ; voir la TÃ©lÃ©charger les fichiers de lâInternet section pour les details). Cochez la case pour une connection proxy et donnez lâaddresse du proxy et son numÃ©ro de port. La connection proxy sera Ã©tablie aprÃšs fermeture du dialogue.</Text>
+<Text id="442">En cours de session, lâInterface BibliothÃ©ccaire peut dÃ©livrer des messages dâavertissement qui informent sur dâÃ©ventuelles consÃ©quences dâune action. On peut dÃ©sactiver le message en cochant la case "Ne pas afficher cet avertissement de nouveau" ("Do not show this warning again"). On peut rÃ©activer les messages dâavertissement en utilisant lâonglet "Avertissement" ("Warning"). Cocher la boÃ®te situÃ©e Ã  cÃŽtÃ© des messages dâavertissement que lâon souhaite reconsulter.</Text>
+</Content>
+</Part>
+<Part id="file_associations">
+<Title>
+<Text id="443">Associations de fichiers</Text>
+</Title>
+<Content>
+<Text id="444">LâInterface BibliothÃ©caire utilise des programmes dâapplication particuliÃšres pour ouvrir des types de fichiers particuliers. Pour modifier des associations ouvrez le menu "Fichier" et cliquer sur "Association de fichiers".</Text>
+<Text id="445">Pour ajouter une association, sÃ©lectionner lâextension du fichier cible dans la liste dÃ©roulant, ou taper dans une nouvelle extension (nây incluer pas le ".") Ensuite soit taper la commande qui lance lâapplication voulue dans la champ appropriÃ©, soit choisir lâapplication dans le dialogue "Navigation". "</Text>
+<Text id="446">Pour Ã©diter une association, sÃ©lectionner une extension de fichier existante. Toute commande existante associÃ©e est affichÃ©e dans le champ de la commande de lancement. Corriger-la, et puis cliquer sur "Remplacer".</Text>
+<Text id="447">Pour enlever une association, sÃ©lectionner une extension de fichier existante et cliquer sur "Supprimer". (Lâextension du fichier reste dans la liste dÃ©roulante "For Files Ending").</Text>
+<Text id="448">Les associations de fichiers sont stockÃ©es dans le dossier principal du rÃ©pertoire principal de lâInterface BibliothÃ©caire, dans un fichier appelÃ© "associations.xml".</Text>
+</Content>
+</Part>
+<Part id="exporting_collections_to_cddvd">
+<Title>
+<Text id="449">Exportation de collections vers CD/DVD</Text>
+</Title>
+<Content>
+<Text id="450">Greenstone peut exporter une ou plusieurs collections vers un CD/DVD dâauto-installation pour Windows. Pour ce faire, le paquetage Greenstone "Export to CD-ROM" doit Ãªtre installÃ©. Il nâest pas inclut par dÃ©faut, donc vous aurez peut Ãªtre Ã  modifier votre installation pour lâinclure.</Text>
+<Text id="451">Pour exporter une collection, ouvrir le menu "Fichier" et choisir "Exporter la Collection vers un CD-ROM". Une liste de collections Greenstone apparaÃ®t ; cliquez sur nâimporte laquelle pour obtenir une description. Cochez la case des collections Ã  exporter. Vous pouvez entrer le nom du CD/DVD dans la case : câest ce qui va apparaÃ®tre dans le menu de dÃ©marrage lorsque le CD/DVD aura Ã©tÃ© installÃ©. Puis cliquez sur "Exporter". Ce processus implique la copie de plusieurs fichiers et peut durer quelques minutes.</Text>
+<Text id="452">A la fin de lâopÃ©ration, Greenstone va afficher le nom dâun dossier contenant les collections exportÃ©es. Utilisez un graveur de CD/DVD pour copier le contenu dans un CD/DVD vierge.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="tagging_document_files">
+<Title>
+<Text id="453">Le balisage des fichiers de documents</Text>
+</Title>
+<Content>
+<Text id="454">Les documents source ont souvent besoin d'Ãªtre structurÃ©s en sections et sous-sections, et il faut communiquer cette information Ã  Greenstone de sorte qu'il puisse puisse conserver la structure hiÃ©rarchique des documents. On peut Ã©galement associer des mÃ©ta-donnÃ©es -- telles que son titre -- Ã  chaque section et sous-section.</Text>
+<Text id="455">Les documents source d'un processus de reconnaissance optique de caractÃšres (ROC) sont typiquement un ensemble de fichiers de traitement de texte, y compris des images. S'ils sont reprÃ©sentÃ©s sous la forme de fichiers Microsoft Word, on peut les importer dans Greenstone en utilisant le greffon Word. On peut aussi les convertir en HTML et les importer dans Greenstone en utilisant le greffon HTML.</Text>
+<Text id="456">Dans les deux cas, on peut indiquer la structure hiÃ©rarchique d'un document en insÃ©rant des balises dans le texte comme suit:</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<Text type="code" id="457">&lt;Metadata name="Title"&gt; Assurer le respect des droits de l'homme pour les pauvres: stratÃ©gies pour atteindre les cibles de dÃ©veloppement international &lt;/Metadata&gt;</Text>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="458"><i>(texte de la section)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="459">On utilise les marqueurs<i>&lt;!-- ... --&gt;</i>car ils dÃ©notent des commentaires en HTML; ces balises de section n'auront donc aucun impact sur la mise en forme du document. Il faut inclure ces autour des balises de sections, mÃªme si le document sur lequel on travaille n'est pas de l'HTML (si par exemple il s'agit d'un fichier de type Microsoft Word).</Text>
+<Text id="460">On peut spÃ©cifier d'autres types de mÃ©ta-donnÃ©es dans la portion Description (situÃ©e entre les balises<i>&lt;Description&gt;</i>et<i>&lt;/Description&gt;</i>), mais ce n'est pas le cas du style de collection dÃ©crit ici.</Text>
+<Text id="461">Il est important de se rappeler que l'on crÃ©e une table des matiÃšres hiÃ©rarchique lorsque l'on insÃšre des balises de sections dans le document. Cela signifie qu'on peut imbriquer des sections dans d'autres sections. En fait, il faut imbriquer toutes les sections dans une grande section qui recouvre l'ensemble du document.</Text>
+<Text id="462">L'exemple suivant illustre le cas d'un document composÃ© de deux chapitres, dont le second contient deux sous-sections. Vous trouverez des exemples concrets de documents source balisÃ©s de cette maniÃšre dans les documents source des collections Demo et DLS. </Text>
+<CodeLine>&lt;!-- &lt;Section&gt; &lt;Description&gt; &lt;Metadata name="Title"&gt;Mon document&lt;/Metadata&gt; &lt;/Description&gt; &lt;Section&gt; &lt;Description&gt; &lt;Metadata name="Title"&gt;Chapitre 1&lt;/Metadata&gt; &lt;/Description&gt; --&gt;</CodeLine>
+<Text type="code" id="463">(text du chapitre 1)</Text>
+<CodeLine>&lt;!-- &lt;/Section&gt; &lt;Section&gt; &lt;Description&gt; &lt;Metadata name="Title"&gt;Chapitre 2&lt;/Metadata&gt; &lt;/Description&gt; &lt;Section&gt; &lt;Description&gt; &lt;Metadata name="Title"&gt;Sous-section 1&lt;/Metadata&gt; &lt;/Description&gt; --&gt;</CodeLine>
+<Text type="code" id="464">(texte de la sous-section 1)</Text>
+<CodeLine>&lt;!-- &lt;/Section&gt; &lt;Section&gt; &lt;Description&gt; &lt;Metadata name="Title"&gt;Sous-section 2&lt;/Metadata&gt; &lt;/Description&gt; --&gt;</CodeLine>
+<Text type="code" id="465">(texte de la sous-section 2)</Text>
+<CodeLine>&lt;!-- &lt;/Section&gt; &lt;/Section&gt; &lt;/Section&gt; --&gt;</CodeLine>
+<Text id="466">Il faut noter que des mÃ©ta-donnÃ©es assignÃ©es Ã  partir dun onglet de section dans un document source prend le pas sur celle assignÃ©e au document tout entier. Ceci signifie que vous ne devez pas spÃ©cifier explicitement la mÃ©ta-donnÃ©e "Title" ("Titre") pour la section de plus haut niveau Ã  l'intÃ©rieur d'un document source Ã  moins que vous ne veuilliez Ã©craser le titre que vous lui avez donnÃ© en spÃ©cifiant la mÃ©ta-donnÃ©e. Dans l'exemple ci-dessus, Ã  moins de vouloir Ã©craser le titre du document existant, vous devriez omettre la ligne oÃ¹ on peut lire:</Text>
+<CodeLine>&lt;Metadata name="Title"&gt;Mon document&lt;/Metadata&gt;</CodeLine>
+</Content>
+</Section>
+<Section id="the_collector">
+<Title>
+<Text id="467">Le Collector</Text>
+</Title>
+<Content>
+<Text id="468">Le Collector est un outil d'assistance qui vous aidera Ã  crÃ©er de nouvelles collections, Ã  modifier ou ajouter Ã  des collections existantes, ou Ã  effacer des collections. Pour ce faire vous serez guidÃ©s Ã  travers un ensemble de pages web qui vous demanderont les informations nÃ©cessaires. Ces pages web parlent d'elles-mÃªmes, et la prÃ©sente section vous les dÃ©crira. Au lieu d'utiliser le Collector, on peut aussi construire des collections depuis la ligne de commandeÂ --Â les premiÃšres pages du Guide du dÃ©veloppeur dÃ©taillent ce processus pas Ã  pas.</Text>
+<Text id="469">Avant de construire et de distribuer des collections d'informations numÃ©riques, il faut rÃ©flÃ©chir aux consÃ©quences et aux responsabilitÃ©s que cela implique. On trouve des aspects lÃ©gaux relatifs aux droits: pouvoir accÃ©der Ã  des documents n'implique pas forcÃ©ment qu'on puisse les distribuer Ã  des tiers. On trouve aussi des aspects sociaux: les collections devraient respecter les coutumes de la communautÃ© dont leurs documents proviennent. Enfin, on trouve des aspects Ã©thiques: il existe des documents qu'il vaut mieux ne pas communiquer. La plume est plus puissante que l'Ã©pÃ©e! Soyez sensible au pouvoir de l'information, et faites-en sage usage.</Text>
+<Text id="470">Pour accÃ©der au Collector, cliquez sur le lien appropriÃ© depuis la page d'accueil de la bibliothÃšque numÃ©rique. </Text>
+<Text id="471">Dans Greenstone, la structure d'une collection est dÃ©terminÃ©e lors de sa mise en place. Cela comprend aussi bien le format des documents source, la maniÃšre de les reprÃ©senter Ã  l'Ã©cran, les sources de mÃ©ta-donnÃ©es, quelles possibilitÃ©s de navigation offrir, quels index de recherche dans le corps du texte fournir, et comment afficher les rÃ©sultats des recherches. AprÃšs la mise en place de la collection, il est facile d'y inclure de nouveaux documentsÂ --Â pour peu qu'ils soient dans le mÃªme format que les documents existants, et que les mÃªmes mÃ©ta-donnÃ©es soient fournies, exactement de la mÃªme maniÃšre.</Text>
+<Text id="472">Le Collector dispose des fonctions de base suivantes:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="473">crÃ©er une nouvelle collection de mÃªme structure qu'une collection existante;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="474">crÃ©er une nouvelle collection d'une structure diffÃ©rente de celle des collections existantes;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="475">ajouter du contenu Ã  une collection existante;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="476">modifier la structure d'une collection existante;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="477">effacer une collection; et</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="478">exporter une collection existante sur un cÃ©dÃ©rom autonome et auto-installable.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="479">Les figuresÂ 16aa et suivantes illustrent l'utilisation du Collector pour la crÃ©ation d'une nouvelle collection, Ã  partir d'un ensemble de fichiers HTML stockÃ©s localement dans le cas de cet exemple. Il faut d'abord dÃ©cider de travailler sur une collection existante ou d'en construire une nouvelle. Dans le premier cas, vous vous trouverez dans les deux premiers points de la liste numÃ©rotÃ©e ci-dessus; dans le second, ce seront les quatre derniers points qui vous concerneront. Dans la figureÂ 16aa, l'utilisateur opte pour la crÃ©ation d'une nouvelle collection.</Text>
+<Figure id="using_the_collector_to_build_a_new_collection">
+<Title>
+<Text id="480">Utiliser le Collector pour construire une nouvelle collection (Ã  suivre)</Text>
+<SubTitle>
+<Text id="481">(a)</Text>
+</SubTitle>
+</Title>
+<File url="images/User_Fig_16a.png"/>
+</Figure>
+<Subsection id="logging_in">
+<Title>
+<Text id="482">Se connecter</Text>
+</Title>
+<Content>
+<Text id="483">Dans tous les cas, il est nÃ©cessaire de se connecter avant de pouvoir faire quoi que ce soit. En gÃ©nÃ©ral, on utilise un navigateur web pour accÃ©der Ã  l'outil de construction de collection sur un ordinateur distant, afin de construire une collection sur ce serveur. Il est bien sÃ»r hors de question d'autoriser n'importe qui Ã  construire des collections (ne serait-ce que pour des raisons de droits), c'est pourquoi Greenstone renferme un systÃšme de sÃ©curitÃ© qui oblige qui veut construire des collections Ã  se connecter avant toute autre chose. Ceci permet Ã  un systÃšme central d'offrir un service Ã  ceux qui souhaitent construire des collections d'informations et utiliser le serveur pour les rendre disponibles Ã  d'autres. D'autre part, mÃªme si vous utilisez Greenstone sur votre ordinateur local et y construisez des collections, il est nÃ©cessaire de vous connecter car il ne faut pas autoriser des tiers utilisant Greenstone sur votre ordinateur Ã  construire des collections sans autorisation prÃ©alable.</Text>
+</Content>
+</Subsection>
+<Subsection id="dialog_structure">
+<Title>
+<Text id="484">Structure de dialogue</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_1">
+<Title>
+<Text id="485">Utiliser le Collector pour construire une nouvelle collection (Suite)</Text>
+<SubTitle>
+<Text id="486">(b)</Text>
+</SubTitle>
+</Title>
+<File url="images/User_Fig_16b.png"/>
+</Figure>
+<Text id="487">Suite Ã  la connexion, on voit apparaÃ®tre la page prÃ©sentÃ©e figureÂ 16bb. Elle montre la suite d'Ã©tapes impliquÃ©es dans la construction d'une collection, c'est-Ã -dire:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="488">Informations sur la collection</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="489">DonnÃ©es source</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="490">Configurer la collection </Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="491">Construire la collection</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="492">Afficher la collection.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="493">La premiÃšre Ã©tape consiste Ã  spÃ©cifier le nom de la collection et les informations associÃ©es. La deuxiÃšme Ã©tape est de prÃ©ciser d'oÃ¹ proviendront les donnÃ©es source. La troisiÃšme permet d'ajuster les options de configuration, une Ã©tape que vous trouverez de plus en plus utile Ã  mesure que vous serez plus expÃ©rimentÃ© avec Greenstone. La quatriÃšme Ã©tape indique oÃ¹ se fera tout le travail (de l'ordinateur). Durant le processus de Â«constructionÂ» le systÃšme construit tous les index et rassemble toutes les autres informations nÃ©cessaires au bon fonctionnement de la collection. La cinquiÃšme Ã©tape vous permettra de visualiser la collection nouvellement crÃ©Ã©e.</Text>
+<Text id="494">Ces cinq Ã©tapes sont reprÃ©sentÃ©es sous forme d'une suite de boutons gris au bas de l'Ã©cran figureÂ 16bb, ainsi qu'au bas de toutes les autres pages gÃ©nÃ©rÃ©es par le Collector. Cet affichage aide les utilisateurs Ã  se rappeler oÃ¹ ils en sont dans le processus. Le bouton Ã  cliquer pour passer Ã  la suite est affichÃ© en vert (informations sur la collection sur la figureÂ 16bb). Les boutons gris (tous les autres, sur la figureÂ 16bb) sont inactifs. Les boutons deviennent jaunes au fur et Ã  mesure de la progression dans les Ã©tapes, et l'utilisateur peut revenir Ã  une Ã©tape antÃ©rieure en cliquant sur le bouton jaune correspondant. Cet affichage est inspirÃ© des Â«assistantsÂ» largement utilisÃ©s dans les logiciels propriÃ©taires pour guider les utilisateurs tout au long des diffÃ©rentes Ã©tapes de l'installation de nouveaux logiciels.</Text>
+</Content>
+</Subsection>
+<Subsection id="collection_information">
+<Title>
+<Text id="495">Informations sur la collection</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_2">
+<Title>
+<Text id="496">Utiliser le Collector pour construire une nouvelle collection (Suite)</Text>
+<SubTitle>
+<Text id="497">(c)</Text>
+</SubTitle>
+</Title>
+<File url="images/User_Fig_16c.png"/>
+</Figure>
+<Text id="498">La prochaine Ã©tape, celle des informations de collection, est illustrÃ©e figureÂ 16cc. Lorsqu'on crÃ©e une nouvelle collection, il est nÃ©cessaire de donner certaines informations la concernant:</Text>
+<BulletList>
+<Bullet>
+<Text id="499">titre,</Text>
+</Bullet>
+<Bullet>
+<Text id="500">adresse de courrier Ã©lectronique de contact, et</Text>
+</Bullet>
+<Bullet>
+<Text id="501">une brÃšve description.</Text>
+</Bullet>
+</BulletList>
+<Text id="502">Le titre de la collection est une petite phrase utilisÃ©e Ã  travers la bibliothÃšque numÃ©rique pour identifier le contenu de la collection. On peut citer comme exemples de titres Â«BibliothÃšque de la nourriture et de la nutritionÂ», Â«BibliothÃšque environnementale mondialeÂ», Â«BibliothÃšque de dÃ©veloppement pour l'humanitÃ©Â», etc. L'adresse Ã©lectronique spÃ©cifie qui contacter pour tout problÃšme rencontrÃ© avec la collection. Si le logiciel Greenstone dÃ©tecte un problÃšme, il est possible qu'il y envoie un rapport dÃ©crivant l'erreur. Enfin, la brÃšve description est une phrase dÃ©crivant les critÃšres d'inclusion dans la collection. Elle apparaÃ®t sous l'en-tÃªte Ã  propos de la premiÃšre page, lors de la prÃ©sentation de la collection.</Text>
+<Text id="503">La position actuelle dans les Ã©tapes de construction de la collection est dÃ©notÃ©e par une flÃšche qui apparaÃ®t au bas de chaque pageÂ --Â dans ce cas, comme illustrÃ© par la figureÂ 16cc, nous nous trouvons Ã  l'Ã©tape des informations de la collection. On continue vers la figureÂ 16dd en cliquant sur le bouton vert donnÃ©es source.</Text>
+</Content>
+</Subsection>
+<Subsection id="source_data">
+<Title>
+<Text id="504">DonnÃ©es source</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_3">
+<Title>
+<Text id="505">Utiliser le Collector pour construire une nouvelle collection (Suite) </Text>
+<SubTitle>
+<Text id="506">(d)</Text>
+</SubTitle>
+</Title>
+<File url="images/User_Fig_16d.png"/>
+</Figure>
+<Text id="507">La figureÂ 16dd est le moment oÃ¹ l'utilisateur spÃ©cifie le texte source qui constituera la collection. On peut soit baser sa collection sur l'une des structures par dÃ©faut fournies, soit sur la structure d'une collection existante.</Text>
+<Text id="508">Si vous optez pour la structure par dÃ©faut, la nouvelle collection pourra contenir des documents HTML (fichiers d'extensions .htm ou .html), des fichiers texte (fichiers d'extensions .txt ou .text), des fichiers au format Microsoft Word (fichiers d'extensions .doc), des documents PDF (fichiers d'extensions .pdf), ou des courriers Ã©lectroniques (fichiers d'extensions .email). Vous trouverez plus d'informations sur les diffÃ©rents formats de documents qu'on peut inclure dans la sectionÂ 3.4.9.</Text>
+<Text id="509">Si vous basez votre nouvelle collection sur une collection existante, les fichiers de la nouvelle collection devront avoir exactement le mÃªme type que ceux utilisÃ©s pour construire la collection existante. Vous remarquerez que certaines collections utilisent des formats de fichiers en entrÃ©e non standard, et que d'autres utilisent des mÃ©ta-donnÃ©es stockÃ©es dans des fichiers auxiliaires. Si ces informations sont absentes de vos nouvelles donnÃ©es, certaines fonctionnalitÃ©s de navigation pourront mal fonctionner. Si par exemple vous clonez la collection Â«DemoÂ», vous remarquerez peut-Ãªtre que les boutons thÃšmes, organisation, et comment faire ne fonctionnent pas bien.</Text>
+<Text id="510">La page web propose des boÃ®tes pour indiquer la localisation des documents source: on peut spÃ©cifier jusqu'Ã  trois sources diffÃ©rentes en entrÃ©e dans la figureÂ 16dd. Si cela ne vous suffit pas, cliquez sur le bouton intitulÃ© More sources (Â«davantage de sourcesÂ»).</Text>
+<Text id="511">Il existe trois types de spÃ©cifications:</Text>
+<BulletList>
+<Bullet>
+<Text id="512">un nom de rÃ©pertoire dans le systÃšme du serveur Greenstone (commenÃ§ant par Â«file://Â»);</Text>
+</Bullet>
+<Bullet>
+<Text id="513">une adresse commenÃ§ant par Â«http://Â», pour les fichiers Ã  tÃ©lÃ©charger depuis le web;</Text>
+</Bullet>
+<Bullet>
+<Text id="514">une adresse commenÃ§ant par Â«ftp://Â», pour les fichiers Ã  tÃ©lÃ©charger en FTP anonyme.</Text>
+</Bullet>
+</BulletList>
+<Text id="515">Si vous utilisezfile://ouftp://pour spÃ©cifier un fichier, ce fichier sera rapatriÃ©.</Text>
+<Text id="516">Si vous utilisezhttp://, tout dÃ©pend si l'URL correspondante fournit dans le navigateur une page web normale ou une liste de fichiers. Si elle fournit une page web normale, cette page sera tÃ©lÃ©chargÃ©eÂ --Â ainsi que toutes les pages vers lesquelles elle pointe, et les pages vers lesquelles pointent ces derniÃšres, etc., pourvu que toutes rÃ©sident sur le mÃªme site, sous cette URL.</Text>
+<Text id="517">Si vous utilisezfile://ouftp://pour spÃ©cifier un dossier ou un rÃ©pertoire, ou si vous donnez une URL enhttp://qui mÃšne vers une liste de fichiers, tout le dossier et tous ses sous-dossiers seront inclus dans la collection.</Text>
+<Text id="518">Vous pouvez spÃ©cifier des sources de plusieurs types.</Text>
+<Text id="519">Dans le cas de la figureÂ 16dd, la nouvelle collection contiendra des documents copiÃ©s depuis un systÃšme de fichiers local ainsi que depuis un site web externe, qui sera copiÃ© localement (une copie Â«miroirÂ» en sera faite) pendant le processus de construction.</Text>
+<Text id="520">Quand on clique sur le bouton configurer la collection pour passer Ã  la prochaine Ã©tape de la construction, le Collector vÃ©rifie que toutes les sources de donnÃ©es spÃ©cifiÃ©es sont joignables. Ceci peut prendre quelques secondes, ou mÃªme quelques minutes si vous avez spÃ©cifiÃ© plusieurs sources. Si l'une ou l'autre des sources spÃ©cifiÃ©es ne sont pas disponibles, on obtient une page comme celle de la figureÂ 16ee, marquant d'une croix les sources non disponibles (dans le cas prÃ©sent, c'est le cas de toutes deux).</Text>
+<Figure id="using_the_collector_to_build_a_new_collection_4">
+<Title>
+<Text id="521">Utiliser le Collector pour construire une nouvelle collection (Suite)</Text>
+<SubTitle>
+<Text id="522">(e)</Text>
+</SubTitle>
+</Title>
+<File url="images/User_Fig_16e.png"/>
+</Figure>
+<Text id="523">Plusieurs raisons peuvent expliquer le fait que des sources soient non disponibles: </Text>
+<BulletList>
+<Bullet>
+<Text id="524">le fichier, le site FTP ou l'URL indiquÃ© n'existe pas;</Text>
+</Bullet>
+<Bullet>
+<Text id="525">il vous faut d'abord vous connecter Ã  votre FAI; </Text>
+</Bullet>
+<Bullet>
+<Text id="526">vous tentez d'accÃ©der Ã  une URL alors que vous vous trouvez derriÃšre un pare-feu.</Text>
+</Bullet>
+</BulletList>
+<Text id="527">Le dernier cas est potentiellement celui qui a l'air le plus mystÃ©rieux. Il se produit si en temps normal il vous faut fournir un nom d'utilisateur et un mot de passe pour accÃ©der Ã  l'Internet. Parfois, il est possible que votre navigateur web affiche correctement la page si on y en entre l'URL, alors que le Collector prÃ©tend que cette source n'est pas disponible. L'explication est que la version affichÃ©e dans votre navigateur provient peut-Ãªtre d'une copie tampon (cache). Malheureusement, les copies tampon locales sont invisibles au Collector. Dans un tel cas de figure, nous vous recommandons de tÃ©lÃ©charger d'abord les pages Ã  l'aide de votre navigateur.</Text>
+</Content>
+</Subsection>
+<Subsection id="configuring_the_collection">
+<Title>
+<Text id="528">Configurer la collection</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_5">
+<Title>
+<Text id="529">Utiliser le Collector pour construire une nouvelle collection (Suite)</Text>
+<SubTitle>
+<Text id="530">(f)</Text>
+</SubTitle>
+</Title>
+<File url="images/User_Fig_16f.png"/>
+</Figure>
+<Text id="531">La figureÂ 16ff prÃ©sente l'Ã©tape suivante. La construction et la prÃ©sentation de toutes les collections sont contrÃŽlÃ©es par des spÃ©cifications enregistrÃ©es dans un fichier de configuration de collection spÃ©cial (voir ci-dessous). Les utilisateurs expÃ©rimentÃ©s pourront utiliser cette page pour modifier les rÃ©glages de configuration, mais la plupart passeront directement Ã  la derniÃšre Ã©tape. En fait, dans la figureÂ 16dd, les boutons configurer la collection et construire la collection sont tous les deux affichÃ©s en vert, ce qui signifie bien que l'on peut complÃštement court-circuiter la troisiÃšme Ã©tape du processus.</Text>
+<Text id="532">Dans notre exemple, l'utilisateur a fait une petite modification au fichier de configuration par dÃ©faut en incluant le drapeau file_is_url Ã  l'aide du greffon (plugin) HTML. Ce drapeau provoque l'insertion des mÃ©ta-donnÃ©es d'URL dans chaque document, en se fondant sur la convention de nom de fichier adoptÃ©e par l'outil qui crÃ©e le miroir. Ces mÃ©ta-donnÃ©es sont utilisÃ©es dans la collection pour permettre aux utilisateurs de se rÃ©fÃ©rer Ã  la version originale du document, plutÃŽt qu'Ã  une copie locale.</Text>
+</Content>
+</Subsection>
+<Subsection id="building_the_collection_1">
+<Title>
+<Text id="533">Construire la collection</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_6">
+<Title>
+<Text id="534">Utiliser le Collector pour construire une nouvelle collection (Suite)</Text>
+<SubTitle>
+<Text id="535">(g)</Text>
+</SubTitle>
+</Title>
+<File url="images/User_Fig_16g.png"/>
+</Figure>
+<Text id="536">La figureÂ 16gg illustre l'Ã©tape de Â«constructionÂ». Jusqu'Ã  prÃ©sent, les rÃ©ponses fournies dans l'interface ont simplement Ã©tÃ© enregistrÃ©es dans un fichier temporaire. L'Ã©tape de construction est celle oÃ¹ tout le travail est rÃ©ellement effectuÃ©.</Text>
+<Text id="537">Lors de la construction, les index de navigation et de recherche sont construits en suivant les instructions du fichier de configuration de collection. Le processus de construction peut prendre de quelques minutes Ã  quelques heures, selon la taille de la collection et la puissance de l'ordinateur. Certaines collections trÃšs consÃ©quentes peuvent prendre plus d'un jour Ã  construire.</Text>
+<Text id="538">Lorsque vous atteindrez cette Ã©tape, une ligne d'Ã©tat situÃ©e au bas de la page web vous donnera un suivi de la progression de l'opÃ©ration, suivi mis Ã  jour toutes les 5 secondes. Le message visible dans la figureÂ 16gg indique que lors de la capture d'Ã©cran, Greenstone effectuait une conversion de format de document de PDF vers HTML.</Text>
+<Text id="539">Des avertissements seront affichÃ©s si certains fichiers ou URL requis en entrÃ©e n'existent pas, ou existent mais qu'aucun greffon (plugin) ne peut les traiter, ou que le greffon ne peut pas trouver un fichier associÃ©, telle qu'une image incrustÃ©e dans un document HTML. L'objectif est que vous suiviez cette progression en laissant cette fenÃªtre ouverte dans votre navigateur. Si des erreurs provoquent la fin prÃ©maturÃ©e du processus, elles seront enregistrÃ©e dans cette zone d'Ã©tat.</Text>
+<Text id="540">Vous pouvez arrÃªter le processus de construction Ã  tout instant en cliquant sur le bouton ArrÃªt de la construction, visible figureÂ 16gg. Si vous quittez la page web (sans avoir annulÃ© le processus de construction Ã  l'aide du bouton ArrÃªt de la construction), la construction continuera Ã  s'effectuer, et la nouvelle collection sera installÃ©e Ã  la fin de l'opÃ©ration. </Text>
+</Content>
+</Subsection>
+<Subsection id="viewing_the_collection">
+<Title>
+<Text id="541">Afficher la collection</Text>
+</Title>
+<Content>
+<Text id="542">Quand la collection est construite et installÃ©e, la suite de boutons visibles aux bas des figuresÂ 16bb Ã Â 16ff apparaÃ®t au bas de la figureÂ 16gg, avec le bouton afficher la collection activÃ©. Ce bouton emmÃšne directement l'utilisateur vers la collection nouvellement construite.</Text>
+<Text id="543">Enfin, il existe une fonctionnalitÃ© d'envoi de courrier d'Ã©lectronique Ã  l'adresse Ã©lectronique de contact de la collection ainsi qu'Ã  l'administrateur systÃšme, Ã  chaque crÃ©ation (ou modification) d'une collection. Ceci permet aux responsables de vÃ©rifier tout changement prenant place et de surveiller ce qui se passe sur le systÃšme. Cette fonctionnalitÃ© est dÃ©sactivÃ©e par dÃ©faut mais elle peut Ãªtre activÃ©e en Ã©ditant le fichier de configuration main.cfg (voir Ã  ce sujet le Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone, sectionÂ <CrossRef target="Chapter" external="Develop" lang="fr" ref="configuring_your_greenstone_site"/>).</Text>
+</Content>
+</Subsection>
+<Subsection id="working_with_existing_collections">
+<Title>
+<Text id="544">Travailler avec des collections existantes</Text>
+</Title>
+<Content>
+<Text id="545">Lorsque l'on dÃ©marre le Collector, il faut spÃ©cifier si on souhaite crÃ©er une collection entiÃšrement nouvelle, ou travailler avec une collection existante, en y ajoutant ou en en effaÃ§ant des donnÃ©es. Ãtant donnÃ© qu'il crÃ©e automatiquement toutes les structures de recherche et de navigation Ã  partir des documents eux-mÃªmes, Greenstone facilite l'ajout de nouvelles informations Ã  des collections existantes. Aucun lien n'Ã©tant insÃ©rÃ© manuellement, il est possible de fusionner automatiquement au reste de la collection de nouveaux documents disponibles, s'ils sont au mÃªme format.</Text>
+<Text id="546">Pour travailler avec une collection existante, il faut d'abord sÃ©lectionner la collection au sein d'une liste fournie par le logiciel. Certaines collections sont Â«protÃ©gÃ©es en Ã©critureÂ» et ne peuvent pas Ãªtre modifiÃ©es: de telles collections n'apparaÃ®tront pas dans la liste de sÃ©lections. Avec la collection retenue, vous pourrez:</Text>
+<BulletList>
+<Bullet>
+<Text id="547">Ajouter de nouvelles donnÃ©es et reconstruire la collection;</Text>
+</Bullet>
+<Bullet>
+<Text id="548">Ãditer le fichier de configuration de la collection;</Text>
+</Bullet>
+<Bullet>
+<Text id="549">Effacer entiÃšrement la collection;</Text>
+</Bullet>
+<Bullet>
+<Text id="550">Exporter la collection sur un cÃ©dÃ©rom.</Text>
+</Bullet>
+</BulletList>
+<Part id="add_new_data">
+<Title>
+<Text id="551">Ajouter de nouvelles donnÃ©es</Text>
+</Title>
+<Content>
+<Text id="552">Les fichiers spÃ©cifiÃ©s par vous seront ajoutÃ©s Ã  la collection. Assurez-vous de ne pas spÃ©cifier Ã  nouveau des fichiers dÃ©jÃ  prÃ©sents dans la collection, sans quoi deux copies en seraient incluses. Les fichiers sont identifiÃ©s par leur chemin d'accÃšs complet, et les pages web par leur adresse web absolue. On peut spÃ©cifier des rÃ©pertoires et des fichiers de la mÃªme maniÃšre que lors de la construction d'une nouvelle collection.</Text>
+<Text id="553">Si vous souhaitez ajouter des donnÃ©es Ã  une collection et que pour l'une ou l'autre raison, le processus de construction Ã©choue, l'ancienne version de la collection demeurera inchangÃ©e.</Text>
+</Content>
+</Part>
+<Part id="edit_configuration_file">
+<Title>
+<Text id="554">Ãditer le fichier de configuration</Text>
+</Title>
+<Content>
+<Text id="555">Les utilisateurs expÃ©rimentÃ©s peuvent Ã©diter le fichier de configuration de la collection, de la mÃªme maniÃšre que lors de la construction d'une nouvelle collection. La sectionÂ 4explique les rÃ©glages de configuration.</Text>
+</Content>
+</Part>
+<Part id="delete_the_collection">
+<Title>
+<Text id="556">Effacer la collection</Text>
+</Title>
+<Content>
+<Text id="557">On vous demandera de confirmer le fait que vous souhaitez vraiment effacer la collection. Une fois la collection effacÃ©e, Greenstone ne pourra pas la rÃ©cupÃ©rer!</Text>
+</Content>
+</Part>
+<Part id="export_the_collection">
+<Title>
+<Text id="558">Exporter la collection</Text>
+</Title>
+<Content>
+<Text id="559">Vous pouvez exporter la collection sous une forme qui lui permette d'Ãªtre Ã©crite sur un cÃ©dÃ©rom Windows autonome et auto-installable. Les logiciels propriÃ©taires crÃ©ant des cÃ©dÃ©roms auto-installables Ã©tant onÃ©reux, cette fonctionnalitÃ© comprend un module d'installation maison.</Text>
+<Text id="560">Lors de l'export de la collection, la boÃ®te de dialogue vous informe du nom du rÃ©pertoire oÃ¹ se trouve le rÃ©sultat de l'opÃ©ration. Ce rÃ©pertoire doit intÃ©gralement Ãªtre gravÃ© sur le cÃ©dÃ©rom en utilisant un logiciel standard de gravage.</Text>
+<Text id="561">L'immense variÃ©tÃ© des diffÃ©rentes configurations Windows possibles nous a empÃªchÃ© de tester et de dÃ©boguer l'installeur de Greenstone dans toutes les conditions possibles. Bien qu'il produise des cÃ©dÃ©roms qui fonctionneront sur la plupart des systÃšmes Windows, il est toujours en cours de dÃ©veloppement. Si vous rencontrez des problÃšmes et que vous disposez d'un logiciel d'installation propriÃ©taire (tel qu'InstallShield, par exemple), vous pouvez utiliser ce dernier pour crÃ©er des cÃ©dÃ©roms Ã  partir des informations fournies par Greenstone. Le rÃ©pertoire d'export mentionnÃ© ci-dessus contient quatre fichiers relatifs au processus d'installation, et trois sous-rÃ©pertoires qui contiennent la collection et le logiciel au complet. Ãtez les quatre fichiers et utilisez InstallShield pour crÃ©er une image de cÃ©dÃ©rom qui installera ces rÃ©pertoires et crÃ©era un raccourci vers le programme gsdlserver.exe.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="document_formats_1">
+<Title>
+<Text id="562">Formats de documents</Text>
+</Title>
+<Content>
+<Text id="563">Lors de la construction de collections, Greenstone traite chaque format de document source en recherchant un Â«greffonÂ» (plugin) qui est capable de le traiter. Les greffons sont spÃ©cifiÃ©s dans le fichier de configuration de la collection. Greenstone utilise en gÃ©nÃ©ral le nom de fichier pour dÃ©terminer le format de documentÂ --Â par exemple, toto.txt sera traitÃ© comme un fichier texte, toto.html comme un fichier HTML, et toto.doc comme un fichier Word.</Text>
+<Text id="564">Voici un rÃ©sumÃ© des greffons disponibles pour les formats de documents les plus courants. Vous trouverez plus de dÃ©tails sur ces greffons ainsi que des greffons supplÃ©mentaires, capables de traiter des formats moins courants, dans le Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone.</Text>
+<Part id="textplug">
+<Title>
+<Text id="565">TEXTPlug (*.txt, *.text)</Text>
+</Title>
+<Content>
+<Text id="566">TEXTPlug interprÃšte un fichier texte comme un simple document. Il ajoute des mÃ©ta-donnÃ©es de titre en se fondant sur la premiÃšre ligne du fichier.</Text>
+</Content>
+</Part>
+<Part id="htmlplug">
+<Title>
+<Text id="567"><i>HTMLPlug (*.htm, *.html; et aussi .shtml, .shm, .asp, .php, .cgi)</i></Text>
+</Title>
+<Content>
+<Text id="568">HTMLPlug traite les fichiers HTML. Il extrait les mÃ©ta-donnÃ©es de titre en se fondant sur la balise<i>&lt;title&gt;</i>, et peut aussi extraire toute autre mÃ©ta-donnÃ©e exprimÃ©e dans la syntaxe de la balise<i>&lt;meta&gt;</i>de HTML. Ce greffon dispose de nombreuses options, documentÃ©es dans le Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone.</Text>
+</Content>
+</Part>
+<Part id="wordplug">
+<Title>
+<Text id="569"><i>WORDPlug (*.doc)</i></Text>
+</Title>
+<Content>
+<Text id="570">WORDPlug importe des fichiers au format Microsoft Word. Il en existe de nombreuses variantes diffÃ©rentesÂ --Â et mÃªme les programmes de Microsoft sont coutumiers d'erreurs de conversion. Greenstone utilise des programmes indÃ©pendants pour convertir les fichiers Word en HTML. Pour certains anciens formats Word, le systÃšme utilise un simple algorithme d'extraction qui trouve toutes les portions de texte incluses dans le fichier en entrÃ©e.</Text>
+</Content>
+</Part>
+<Part id="pdfplug">
+<Title>
+<Text id="571"><i>PDFPlug (*.pdf)</i></Text>
+</Title>
+<Content>
+<Text id="572">PDFPlug importe des documents au format PDF d'Adobe (Â«format de document portableÂ»). Comme WORDPlug, il utilise un programme indÃ©pendant, qui s'appelle pdftohtml dans le cas prÃ©sent, pour convertir des fichiers PDF en HTML.</Text>
+<Text id="573">Comme dans le cas de WORDPlug, les collections afficheront par dÃ©faut l'Ã©quivalent HTML du fichier lorsque l'utilisateur cliquera sur l'icone document; cependant, on peut modifier les chaÃ®nes de format dans le fichier de configuration de la collection pour donner plutÃŽt accÃšs Ã  l'utilisateur au fichier PDF original, et nous vous recommandons de procÃ©der ainsi. Contentez-vous de remplacer les balises<i>&lt;link&gt; ... &lt;/link&gt;</i>par des balises<i>&lt;srclink&gt; ... &lt;/srclink&gt;</i>.</Text>
+<Text id="574">Le programme pdftohtml ne parvient pas Ã  traiter certains fichiers PDF. Le processus de conversion prend un temps exponentiellement long, et on voit souvent apparaÃ®tre Ã  l'Ã©cran un message traitant de ce processus. Si cela se produit, la seule solution que nous puissions proposer est d'ÃŽter le document concernÃ© de la collection. PDFPlug ne peut pas non plus traiter les fichiers PDF chiffrÃ©s.</Text>
+</Content>
+</Part>
+<Part id="psplug">
+<Title>
+<Text id="575"><i>PSPlug (*.ps)</i></Text>
+</Title>
+<Content>
+<Text id="576">PSPlug importe des documents au format PostScript. Il fonctionne au mieux si votre ordinateur dispose dÃ©jÃ  d'un programme standard sous Linux et appelÃ© ps2ascii. Ce programme est disponible sur la plupart des installations Linux, mais pas sous Windows. Si ce programme n'est pas disponible, PSPlug se limite Ã  un simple algorithme d'extraction de texte.</Text>
+</Content>
+</Part>
+<Part id="emailplug">
+<Title>
+<Text id="577"><i>EMAILPlug (*.email)</i></Text>
+</Title>
+<Content>
+<Text id="578">EMAILPlug importe des fichiers contenant du courrier Ã©lectronique, et traite les formats de courrier Ã©lectronique courants tels que ceux utilisÃ©s par Netscape, Eudora, et les lecteurs de courrier Ã©lectronique sous Unix. Chaque document source est examinÃ© Ã  la recherche d'un ou de plusieurs courriers Ã©lectroniques mis bout Ã  bout, et si cette recherche aboutit le contenu du document est traitÃ©. Le greffon extrait les mÃ©ta-donnÃ©es des champs Subject (Â«objetÂ»), To (Â«destinataireÂ»), From (Â«expÃ©diteurÂ»), et Date. Cependant, ce greffon ne traite pas encore correctement les courriers Ã©lectroniques encodÃ©s au format MIMEÂ --Â bien que lisibles, ils ont souvent un aspect Ã©trange.</Text>
+</Content>
+</Part>
+<Part id="zipplug">
+<Title>
+<Text id="579"><i>ZIPPlug (.gz, .z, .tgz, .taz, .bz, .zip, .tar)</i></Text>
+</Title>
+<Content>
+<Text id="580">Le greffon ZIPPlug traite les formats d'entrÃ©e compactÃ©s et/ou d'archives suivants: gzip (.gz, .z, .tgz, .taz), bzip (.bz), zip (.zip .jar), et tar (.tar). Il repose sur les programmes gunzip, bunzip, unzip, et tar, qui sont des outils standard sous Linux. ZIPPlug est dÃ©sactivÃ© sur les ordinateurs employant Windows.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="administration">
+<Title>
+<Text id="581">Administration</Text>
+</Title>
+<Content>
+<Text id="582">Chaque installation de Greenstone comprend un outil d'Â«administrationÂ», auquel on accÃšde en cliquant sur le lien appropriÃ© de la page d'accueil.</Text>
+<Text id="583">La premiÃšre page, prÃ©sentÃ©e figureÂ 17, donne des informations sur chacune des collections proposÃ©es par le systÃšme. Remarquez qu'il est possible que certaines collections Â«privÃ©esÂ» n'apparaissant pas sur la page d'accueil de Greenstone soient listÃ©es ici:<i>toutes</i>les collections sont ici prÃ©sentes. Chaque collection est accompagnÃ©e de son nom court, de son nom complet, du fait qu'elle est ou non publique, et du fait qu'elle est ou non en fonctionnement. Cliquer sur l'abrÃ©viation (abbrev.) d'une collection (la premiÃšre colonne de liens dans la figureÂ 17) fournira des informations sur cette collection, informations synthÃ©tisÃ©es Ã  partir du fichier de configuration de cette collection ainsi qu'Ã  partir d'autres structures internes crÃ©Ã©es pour elle. Si la collection est publique et en cours de fonctionnement, cliquer sur le nom complet de la collection (le deuxiÃšme lien) vous emmÃ©nera sur la collection Ã  proprement parler. </Text>
+<Text id="584">Une collection appelÃ©e wohiex, pour women's history excerpt, est visible prÃšs du bas de la figureÂ 17. FigureÂ 18montre l'information qui est affichÃ©e quand on appuie sur ce lien. Quand on choisit une collection, la premiÃšre section donne des informations sur le fichier de configuration et sur la taille de la collection (dans le cas prÃ©sent, elle comprend environ 1000 documents, un million de mots, et plus de 6 mÃ©ga-octets de donnÃ©es). Les sections suivantes contiennent des informations internes relatives au protocole de communication utilisÃ© pour accÃ©der aux collections. Par exemple, les options de filtre pour Â«QueryFilterÂ» montrent les options et les valeurs possibles qu'on peut utiliser lors de l'interrogation de la collection par requÃªtes.</Text>
+<Text id="585">L'outil d'administration prÃ©sente Ã©galement des informations de configuration relatives Ã  l'installation et permet de modifier cette derniÃšre. Il facilite l'examen du journal d'erreurs (qui enregistre les erreurs internes) et du journal utilisateur (qui consigne l'utilisation de la collection). Il permet Ã  un ou plusieurs utilisateurs spÃ©cifiÃ©s d'en autoriser d'autres Ã  construire des collections et Ã  ajouter du contenu Ã  des collections existantes. On accÃšde Ã  toutes ces fonctionnalitÃ©s de maniÃšre interactive Ã  partir d'Ã©lÃ©ments du menu situÃ© Ã  gauche sur la figureÂ 17.</Text>
+<Figure id="greenstone_administration_facility">
+<Title>
+<Text id="586">Outil d'administration de Greenstone</Text>
+</Title>
+<File url="images/User_Fig_17.png"/>
+</Figure>
+<Figure id="information_about_the_womens_history_excerpt_collection">
+<Title>
+<Text id="587">Informations relatives Ã  une collection particuliÃšre</Text>
+</Title>
+<File url="images/User_Fig_18a.png"/>
+<File url="images/User_Fig_18b.png"/>
+</Figure>
+<Section id="configuration_files">
+<Title>
+<Text id="588">Fichiers de configuration</Text>
+</Title>
+<Content>
+<Text id="589">Deux fichiers de configuration contrÃŽlent le fonctionnement de Greenstone: le fichier de configuration de site gsdlsite.cfg et le fichier de configuration principal main.cfg.</Text>
+<Text id="590">Le fichier gsdlsite.cfg sert Ã  configurer Greenstone pour le site particulier sur lequel il est installÃ©. Il est conÃ§u pour enregistrer les options de configuration propres Ã  un site donnÃ©, comme par exemple le nom du rÃ©pertoire abritant le logiciel, l'adresse HTTP du systÃšme Greenstone, et si l'option Â«Fast-CGIÂ» est utilisÃ©e ou non. Les entrÃ©es de ce fichier sont dÃ©crites dans le Guide d'installation de la bibliothÃšque numÃ©rique Greenstone</Text>
+<Text id="591">Le fichier main.cfg contient des informations communes Ã  l'interface et Ã  toutes les collections servies sur un site Greenstone. Il comprend l'adresse Ã©lectronique du mainteneur du systÃšme, le fait que les pages d'Ã©tat et de Collector sont activÃ©es ou non, le fait qu'on conserve ou non des journaux de l'activitÃ© utilisateur, et si l'on utilise ou non des Â«cookiesÂ» web pour identifier les utilisateurs.</Text>
+</Content>
+</Section>
+<Section id="logs">
+<Title>
+<Text id="592">Journaux</Text>
+</Title>
+<Content>
+<Text id="593">On peut examiner trois types de journaux: journaux d'utilisation, d'erreur, et d'initialisation. Les deux derniers types de journaux ne prÃ©senteront rÃ©ellement d'intÃ©rÃªt qu'aux yeux des mainteneurs du logiciel.</Text>
+<Text id="594">Le logiciel Greenstone peut consigner toute l'activitÃ© utilisateur, c'est-Ã -dire toutes les pages visitÃ©es par chaque utilisateur, bien qu'aucune information nominative ne soit stockÃ©e dans les journaux. On active la journalisation (qui est dÃ©sactivÃ©e par dÃ©faut) en incluant les lignes suivantes:</Text>
+<CodeLine>logcgiargs true usecookies true</CodeLine>
+<Text id="595">dans le fichier de configuration principal du systÃšme. Ces deux options ayant par dÃ©faut la valeur fausse false, aucune journalisation n'a lieu tant qu'elles ne reÃ§oivent pas la valeur vraie true. C'est la ligne logcgiargs qui a pour effet d'activer ou de dÃ©sactiver la journalisation. En activant usecookies, on affecte Ã  chaque utilisateur un code d'identification unique, ce qui permet de suivre dans le journal les interactions de chaque utilisateur.</Text>
+<Text id="596">Chaque ligne du journal utilisateur reprÃ©sente une page visitÃ©eÂ --Â mÃªme les pages gÃ©nÃ©rÃ©es pour la consultation des journaux sont ainsi consignÃ©es! Elle comprend (a) l'adresse IP de l'ordinateur de l'utilisateur, (b) une estampille temporelle entre crochets, (c) les arguments CGI entre parenthÃšses, et (d) le nom du navigateur de l'utilisateur (sachant que le navigateur de Netscape s'appelle Â«MozillaÂ»). Voici un exemple d'une telle ligne, Ã©chantillon ventilÃ© et annotÃ© pour en faciliter la lecture:</Text>
+<CodeLine>/fast-cgi-bin/niupepalibrary (a) its-www1.massey.ac.nz (b) [Thu Dec 07 23:47:00 NZDT 2000] (c) (a=p, b=0, bcp=, beu=, c=niupepa, cc=, ccp=0, ccs=0, cl=, cm=, cq2=, d=, e=, er=, f=0, fc=1, gc=0, gg=text, gt=0, h=, h2=, hl=1, hp=, il=l, j=, j2=, k=1, ky=, l=en, m=50, n=, n2=, o=20, p=home, pw=, q=, q2=, r=1, s=0, sp=frameset, t=1, ua=, uan=, ug=, uma=listusers, umc=, umnpw1=, umnpw2=, umpw=, umug=, umun=, umus=, un=, us=invalid, v=0, w=w, x=0, z=130.123.128.4-950647871) (d) "Mozilla/4.08 [en] (Win95; I ;Nav)" </CodeLine>
+<Text id="597">Le dernier argument CGI, Â«zÂ», est un code d'identification ou Â«cookieÂ» engendrÃ© par le navigateur de l'utilisateur: il comprend le numÃ©ro IP suivi d'une estampille temporelle portant la date de la premiÃšre visite de cet utilisateur Ã  la bibliothÃšque numÃ©rique.</Text>
+<Text id="598">Le journal usage.txt est placÃ© dans le rÃ©pertoire etc de la structure de fichiers de Greenstone (voir Ã  ce sujet le Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone). Lorsque la journalisation est activÃ©e, chaque action de chaque utilisateur est consignÃ©e. Cependant, seules les 100 derniÃšres entrÃ©es du journal sont affichÃ©es par le lien Journal de l'utilisation visible figureÂ 17.</Text>
+</Content>
+</Section>
+<Section id="user_management">
+<Title>
+<Text id="599">Gestion des utilisateurs</Text>
+</Title>
+<Content>
+<Text id="600">Greenstone incorpore un systÃšme d'authentification qu'on peut utiliser pour contrÃŽler l'accÃšs Ã  certaines fonctionnalitÃ©s. Pour le moment, il ne sert qu'Ã  restreindre l'accÃšs au Collector et Ã  certaines fonctions d'administration. Si pour une collection particuliÃšre il s'avÃ©rait nÃ©cessaire d'authentifier les utilisateurs avant de leur renvoyer des informations, cela serait Ã©galement possible. On pourrait par exemple protÃ©ger individuellement des documents de telle sorte que seuls des utilisateurs enregistrÃ©s puissent y accÃ©der en tapant un mot de passe. Cependant, aucune collection n'utilise cette possibilitÃ© actuellement. L'authentification se fait en requÃ©rant un nom d'utilisateur et un mot de passe, comme illustrÃ© figureÂ 16aa.</Text>
+<Text id="601">La page d'administration permet de lister les utilisateurs, d'en ajouter de nouveaux, et d'en effacer d'anciens. Ãvidemment, ce pouvoir est lui aussi protÃ©gÃ©: seuls les utilisateurs disposant de privilÃšges d'administration peuvent ajouter de nouveaux utilisateurs. Il est Ã©galement possible Ã  chaque utilisateur d'appartenir Ã  diffÃ©rents Â«groupesÂ». Actuellement, il n'existe que deux groupes, qui sont Â«administratorÂ» (administrateur) et Â«colbuilderÂ» (constructeur de collection). Les membres du premier groupe peuvent ajouter et effacer des utilisateurs, et modifier leurs groupes. Les membres du second peuvent accÃ©der aux fonctionnalitÃ©s dÃ©crites plus haut pour construire de nouvelles collections et modifier (ou effacer) des collections existantes. </Text>
+<Text id="602">Lors de l'installation de Greenstone, il existe un utilisateur, appelÃ© admin, qui appartient aux deux groupes. Son mot de passe est mis en place pendant le processus d'installation. Cet utilisateur peut crÃ©er de nouveaux identifiants et mots de passe associÃ©s pour des utilisateurs qui n'appartiendraient qu'au groupe colbuilder, ce qui est la mÃ©thode conseillÃ©e pour donner Ã  d'autres utilisateurs la possibilitÃ© de construire des collections. Les informations utilisateur sont stockÃ©es dans deux bases de donnÃ©es placÃ©es dans la structure de fichiers de Greenstone (voir Ã  ce sujet le Guide du dÃ©veloppeur de la bibliothÃšque numÃ©rique Greenstone).</Text>
+</Content>
+</Section>
+<Section id="technical_information">
+<Title>
+<Text id="603">Informations techniques</Text>
+</Title>
+<Content>
+<Text id="604">Les liens situÃ©s sous l'en-tÃªte Informations techniques fournissent davantage d'informations sur l'installation. Le lien GÃ©nÃ©ral donne accÃšs aux informations techniques, y compris les rÃ©pertoires de stockage. L'Ã©lÃ©ment de menu Protocoles donne, pour chaque type de protocole, des informations sur les collections accessibles par ce protocole.</Text>
+<Text id="605">Enfin, le code de l'interface utilisateur (appelÃ© le Â«rÃ©ceptionnisteÂ») utilise des<i>actions</i>pour communiquer les souhaits de l'utilisateur au systÃšme. Ces actions correspondent Ã  l'argument CGI libellÃ© Â«aÂ». Si par exemple<i>a=status</i>, le rÃ©ceptionniste invoque l'action status, qui affiche la page d'Ã©tats. Un Ã©lÃ©ment de menu donne accÃšs aux listes de toutes les actions proposÃ©es par le systÃšme, et un autre mÃšne aux arguments acceptÃ©s par ces actions.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_a_software_features">
+<Title>
+<Text id="606">FonctionnalitÃ©s du logiciel</Text>
+</Title>
+<Content>
+<Table class="hidden" id="table_appendixa">
+<Title/>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="607"><i>Accessible Ã  travers un navigateur web</i></Text>
+</th>
+<th width="397">
+<Text id="608">On accÃšde aux collections Ã  travers un navigateur web standard (tel que Netscape ou Internet Explorer), ce qui fournit Ã  la fois une navigation facile et des fonctionnalitÃ©s de recherche puissantes. </Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="609"><i>FonctionnalitÃ©s du logiciel</i></Text>
+</th>
+<th width="397">
+<Text id="610">L'utilisateur peut effectuer des recherches dans le corps du texte des documents, ou choisir parmi plusieurs index construits Ã  partir de diffÃ©rentes portions des documents. Certaines collections proposent par exemple un index des documents complets, un index des sections, un index des titres, et un index des auteurs, qu'on peut tous sÃ©lectionner pour rechercher certains mots ou groupes de mots. Les rÃ©sultats peuvent Ãªtre ordonnÃ©s par leur pertinence ou en utilisant une mÃ©ta-donnÃ©e.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="611"><i>Souplesse de la navigation</i></Text>
+</th>
+<th width="397">
+<Text id="612">L'utilisateur peut naviguer dans les listes des auteurs, des titres, des dates, des structures de classification, etc. Des collections diffÃ©rentes pourront proposer des fonctionnalitÃ©s de navigation diffÃ©rentes et mÃªme au sein d'une collection, on trouvera un large spectre d'interfaces de navigation. Les interfaces de recherche et de navigation sont prÃ©parÃ©es pendant le processus de construction, en se fondant sur les informations de configuration de la collection.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="613"><i>CrÃ©ation automatique de structures d'accÃšs</i></Text>
+</th>
+<th width="397">
+<Text id="614">Le logiciel Greenstone crÃ©e des collections d'informations trÃšs faciles Ã  maintenir. Toutes les structures de recherche et de navigation sont directement construites Ã  partir des documents eux-mÃªmes. Aucun lien n'est insÃ©rÃ© manuellement, mais tous les liens existant dans les originaux sont conservÃ©s. Cela signifie que si de nouveaux documents du mÃªme format sont disponibles, ils peuvent Ãªtre automatiquement fusionnÃ©s au reste de la collection. En fait, pour la plupart des collections, tout ceci est pris en charge par des processus qui s'exÃ©cutent rÃ©guliÃšrement, partent Ã  la recherche de nouveaux contenus, et reconstruisent les index~---~le tout sans aucune intervention manuelle. </Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="615"><i>Utilisation des mÃ©ta-donnÃ©es disponibles</i></Text>
+</th>
+<th width="397">
+<Text id="616">On peut associer Ã  chaque document ou Ã  chaque section de document des mÃ©ta-donnÃ©es, c'est-Ã -dire des informations de description telles que l'auteur, le titre, la date, des mots-clefs, etc. Les mÃ©ta-donnÃ©es forment la matiÃšre premiÃšre des index de navigation. Elles doivent Ãªtre explicitement fournies, ou bien il doit Ãªtre possible de les obtenir automatiquement Ã  partir des documents eux-mÃªmes. La plupart des documents Ã©lectroniques utilisent le schÃ©ma de mÃ©ta-donnÃ©es<i>Dublin Core</i>, mais il est Ã©galement possible d'utiliser d'autres schÃ©mas.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="617"><i>Extension des possibilitÃ©s du systÃšme par greffons (Â«pluginsÂ»)</i></Text>
+</th>
+<th width="397">
+<Text id="618">Pour pouvoir utiliser plusieurs types de documents source, le logiciel est organisÃ© d'une maniÃšre telle qu'on peut Ã©crire des Â«greffonsÂ» (plugins) pour de nouveaux formats de documents. Il existe actuellement des greffons pour les formats texte brut, HTML, Word, PDF, PostScript, courrier Ã©lectronique, certains formats propriÃ©taires, et pour l'exploration rÃ©cursive de structures de fichiers arborescentes et d'archives compactÃ©es contenant de telles structures. Une collection peut proposer des documents de plusieurs formats source. On utilise un schÃ©ma semblable de Â«classificateursÂ» pour construire des index de navigation Ã  partir des mÃ©ta-donnÃ©es: les classificateurs crÃ©ent des index de navigation de divers types en se fondant sur les mÃ©ta-donnÃ©es.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="619"><i>ConÃ§u pour gÃ©rer des collections de plusieurs mÃ©ga-octets</i></Text>
+</th>
+<th width="397">
+<Text id="620">Les collections peuvent contenir plusieurs millions de documents, ce qui fait du systÃšme Greenstone un logiciel adaptÃ© aux collections de taille allant jusqu'Ã  plusieurs giga-octets.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="621"><i>Les documents peuvent Ãªtre Ã©crits dans n'importe quelle langue</i></Text>
+</th>
+<th width="397">
+<Text id="622">Le logiciel utilise Unicode partout, ce qui permet de traiter tous les langages d'une maniÃšre consistante. Ã l'heure actuelle, on a construit des collections contenant du franÃ§ais, de l'espagnol, du maori, du chinois, de l'arabe, et de l'anglais. C'est une conversion Ã  la volÃ©e qui traduit le format Unicode utilisÃ© en interne en un alphabet reconnu par le navigateur web de l'utilisateur.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="623"><i>L'interface utilisateur est disponible dans de nombreuses langues</i></Text>
+</th>
+<th width="397">
+<Text id="624">L'interface peut Ãªtre affichÃ©e en de nombreuses langues. Elle est actuellement disponible en allemand, anglais, arabe, chinois, espagnol, franÃ§ais, hollandais, maori, et portugais. On peut facilement ajouter de nouvelles langues Ã  cette liste de traductions.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="625"><i>Les collections peuvent contenir du texte, des images, du son, et de la vidÃ©o</i></Text>
+</th>
+<th width="397">
+<Text id="626">Les collections Greenstone peuvent comprendre du texte, des images, des contenus audio et vidÃ©o. La plupart des contenus non textuels sont reliÃ©s aux documents textuels ou accompagnÃ©s de descriptions textuelles (telles que les lÃ©gendes des figures) pour pouvoir Ãªtre accessibles depuis une recherche dans le corps du texte ou la navigation. Cependant, l'architecture du logiciel rend possible l'implÃ©mentation de greffons (plugins) et de classificateurs pour des donnÃ©es non textuelles.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="627"><i>Utilisation de techniques de compression avancÃ©es</i></Text>
+</th>
+<th width="397">
+<Text id="628">Greenstone utilise des techniques de compression pour rÃ©duire la taille des index et du texte. La rÃ©duction de taille des index par voie de compression a de plus l'avantage d'accÃ©lÃ©rer la vitesse de rapatriement du texte.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="629"><i>Fourniture d'une fonction d'administration</i></Text>
+</th>
+<th width="397">
+<Text id="630">Une fonction d'Â«administrationÂ» permet Ã  des utilisateurs spÃ©cifiÃ©s d'en autoriser de nouveaux Ã  construire des collections, Ã  protÃ©ger des documents de telle sorte que seuls des utilisateurs enregistrÃ©s puissent y accÃ©der en tapant un mot de passe, Ã  examiner la composition de toutes les collections, etc. Les journaux d'activitÃ© utilisateur peuvent enregistrer toutes les requÃªtes effectuÃ©es vers chaque collection Greenstone.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="631"><i>Les nouvelles collections apparaissent dynamiquement</i></Text>
+</th>
+<th width="397">
+<Text id="632">On peut mettre des collections Ã  jour et en proposer de nouvelles Ã  tout moment, sans devoir arrÃªter le systÃšme: le processus en charge de l'interface utilisateur remarquera (grÃ¢ce Ã  un systÃšme de sondages rÃ©guliers) que de nouvelles collections sont apparues et les ajoutera Ã  la liste proposÃ©e Ã  l'utilisateur.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="633"><i>Les collections peuvent Ãªtre publiÃ©es sur l'Internet ou sur un cÃ©dÃ©rom</i></Text>
+</th>
+<th width="397">
+<Text id="634">On peut utiliser le logiciel pour servir des collections sur le web. Mais les collections Greenstone peuvent Ãªtre diffusÃ©es, sous une forme exactement semblable, sur cÃ©dÃ©rom. L'interface utilisateur utilisera un navigateur web standard (Netscape est inclus sur chaque disque), et l'interaction se dÃ©roulera de la mÃªme maniÃšre que sur le web, Ã  ceci prÃšs que les temps de rÃ©ponse seront plus faciles Ã  prÃ©dire, et plus reproductibles car moins soumis aux alÃ©as du rÃ©seau. Les cÃ©dÃ©roms fonctionnent sous toutes les versions du systÃšme d'exploitation Windows.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="635"><i>Les collections peuvent Ãªtre distribuÃ©es sur plusieurs ordinateurs</i></Text>
+</th>
+<th width="397">
+<Text id="636">Une structure de processus souple permet de faire servir diffÃ©rentes collections par des ordinateurs diffÃ©rents, bien que tout soit prÃ©sentÃ© Ã  l'utilisateur de maniÃšre unifiÃ©e, sur la mÃªme page web, comme faisant partie de la mÃªme bibliothÃšque numÃ©rique.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="637"><i>Fonctionne sous Windows comme sous Unix</i></Text>
+</th>
+<th width="397">
+<Text id="638">Greenstone fonctionne Ã  la fois sous Windows (versions 3.1/3.11, 95/98/Me, NT/2000) et sous Unix (Linux et SunOS). On peut utiliser n'importe lequel de ces systÃšmes comme serveur web. On ne peut pas construire des collections sur des systÃšmes Windows de bas de gamme, mais on peut y transfÃ©rer des collections prÃ©-construites ailleurs.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="639"><i>Ce que Greenstone apporte</i></Text>
+</th>
+<th width="397">
+<Text id="640">La bibliothÃšque numÃ©rique Greenstone est un logiciel libre, disponible depuis le site web de la bibliothÃšque numÃ©rique de Nouvelle-ZÃ©lande (<u>nzdl.org</u>) sous les termes de la licence publique gÃ©nÃ©rale de GNU. le logiciel comprend tout ce qui est dÃ©crit ci-dessus: service web, crÃ©ation de cÃ©dÃ©roms, construction de collection, possibilitÃ©s multilingues, greffons (plugins) et classificateurs permettant d'accepter un grand nombre de formats de documents source. Il comprend une fonctionnalitÃ© d'installation automatique pour faciliter cette opÃ©ration sur les systÃšmes Windows comme Unix. Dans l'esprit du logiciel libre, les utilisateurs sont encouragÃ©s Ã  nous communiquer tout rapport de bogue, correction, modification ou amÃ©lioration.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<Chapter id="appendix_b_glossary_of_terms">
+<Title>
+<Text id="641">Glossaire des termes</Text>
+</Title>
+<Content>
+<Table class="hidden" id="appendixb">
+<Title/>
+<TableContent>
+<tr>
+<th width="123">
+<Text id="642"><b>Terme</b></Text>
+</th>
+<th width="406">
+<Text id="643"><b>Signification</b></Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="644"><i>autoconf</i></Text>
+</th>
+<th width="406">
+<Text id="645">Programme Unix utilisÃ© pour configurer le paquetage d'installation du logiciel Greenstone et l'adapter Ã  votre systÃšme</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="646"><i>Autorun</i></Text>
+</th>
+<th width="406">
+<Text id="647">FonctionnalitÃ© de Windows qui dÃ©marre un programme automatiquement lors de l'insertion d'un cÃ©dÃ©rom</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="648">BoolÃ©enne, requÃªte</Text>
+</th>
+<th width="406">
+<Text id="649">RequÃªte dans un systÃšme de rapatriement d'informations qui peut contenir des ET, OU, et NON boolÃ©ens </Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="650">Navigation</Text>
+</th>
+<th width="406">
+<Text id="651">AccÃšs Ã  une collection en parcourant une liste organisÃ©e de valeurs de mÃ©ta-donnÃ©es associÃ©es aux documents (telles que l'auteur, le titre, la date, des mots-clefs)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="652"><i>buildcol.pl</i></Text>
+</th>
+<th width="406">
+<Text id="653">Programme de Greenstone utilisÃ© pour construire des collections</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="654">Construction</Text>
+</th>
+<th width="406">
+<Text id="655">Processus de crÃ©ation des structures d'indexation et de navigation utilisÃ©es pour accÃ©der Ã  une collection</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="656">C++</Text>
+</th>
+<th width="406">
+<Text id="657">Langage de programmation dans lequel est Ã©crit la majoritÃ© des logiciels Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="658">Casse, ignorer la</Text>
+</th>
+<th width="406">
+<Text id="659">Faire en sorte que les opÃ©rations de recherche ne distinguent pas les majuscules des minuscules</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="660">CGI</Text>
+</th>
+<th width="406">
+<Text id="661">Common Gateway Interface (interface commune de passerelle), systÃšme qui permet Ã  des utilisateurs d'activer des programmes sur l'ordinateur hÃŽte (ou serveur) en cliquant sur des pages web</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="662">CGI, script</Text>
+</th>
+<th width="406">
+<Text id="663">Code associÃ© Ã  un bouton, un menu, ou Ã  un lien sur une page web qui spÃ©cifie ce que l'ordinateur hÃŽte (ou serveur) doit faire lorsque l'utilisateur clique sur cet objet</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="664"><i>cgi-bin</i></Text>
+</th>
+<th width="406">
+<Text id="665">RÃ©pertoire de stockage des scripts CGI</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="666">Classificateur</Text>
+</th>
+<th width="406">
+<Text id="667">Module de code de Greenstone qui examine les mÃ©ta-donnÃ©es d'un document et crÃ©e un index de navigation</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="668">Collection</Text>
+</th>
+<th width="406">
+<Text id="669">Ensemble de documents rassemblÃ©s sous une interface de recherche et de navigation homogÃšne</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="670">Collection, fichier de configuration</Text>
+</th>
+<th width="406">
+<Text id="671">Fichier qui spÃ©cifie comment importer et construire une collection, quels index et quelles interfaces de langue fournir, etc.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="672">Collection, serveur de</Text>
+</th>
+<th width="406">
+<Text id="673">Programme fournissant l'accÃšs Ã  une collection en cours d'utilisation</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="674">Configuration, fichier de</Text>
+</th>
+<th width="406">
+<Text id="675">Voir Â«Collection, fichier de configurationÂ», Â«Principal, fichier de configurationÂ», et Â«Site, fichier de configuration deÂ»</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="676">CVS</Text>
+</th>
+<th width="406">
+<Text id="677">Concurrent Versioning System (systÃšme de versions concurrentes), systÃšme permettant de maintenir le code source utilisÃ© par Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="678"><i>db2txt</i></Text>
+</th>
+<th width="406">
+<Text id="679">Outil Greenstone permettant de visualiser une base de donnÃ©es GDBM sous forme textuelle (voir Â«GDBMÂ»)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="680">Â«DemoÂ», collection</Text>
+</th>
+<th width="406">
+<Text id="681">Sous-ensemble de la bibliothÃšque de dÃ©veloppement pour l'humanitÃ©, distribuÃ© avec le logiciel Greenstone Ã  des fins d'illustration et de didacticiel</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="682">BibliothÃšque numÃ©rique</Text>
+</th>
+<th width="406">
+<Text id="683">Collection d'objets numÃ©riques (textes, extraits audio ou vidÃ©o) ainsi que de mÃ©thodes d'accÃšs et de rapatriement, de sÃ©lection, d'organisation, et de maintenance</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="684"><i>HDL</i></Text>
+</th>
+<th width="406">
+<Text id="685">Humanity Development Library (bibliothÃšque de dÃ©veloppement pour l'humanitÃ©), collection Greenstone d'informations humanitaires pour les pays en voie de dÃ©veloppement</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="686">Document</Text>
+</th>
+<th width="406">
+<Text id="687">UnitÃ© de base servant Ã  construire des collections de bibliothÃšques numÃ©riques; elle peut contenir du texte, des graphiques, du son, de la vidÃ©o, etc.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="688">Dublin core</Text>
+</th>
+<th width="406">
+<Text id="689">ManiÃšre standardisÃ©e de dÃ©crire les mÃ©ta-donnÃ©es</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="690">Fast CGI</Text>
+</th>
+<th width="406">
+<Text id="691">Outil qui permet aux scripts CGI de demeurer actifs en permanence, de maniÃšre Ã  Ã©viter de les redÃ©marrer de zÃ©ro Ã  chacune de leurs invocations</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="692">Filtre, programme de</Text>
+</th>
+<th width="406">
+<Text id="693">La portion d'un serveur de collection Greenstone qui implÃ©mente les opÃ©rations de requÃªte et de navigation</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="694">Format, chaÃ®ne de</Text>
+</th>
+<th width="406">
+<Text id="695">ChaÃ®ne qui spÃ©cifie comment afficher les documents et autres listes dans Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="696">GB, encodage</Text>
+</th>
+<th width="406">
+<Text id="697">ManiÃšre standardisÃ©e d'encoder le chinois</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="698">GDBM</Text>
+</th>
+<th width="406">
+<Text id="699">GNU DataBase Manager (gestionnaire de bases de donnÃ©es de GNU), programme utilisÃ© par le logiciel Greenstone pour stocker les mÃ©ta-donnÃ©es de chaque document</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="700">GIMP</Text>
+</th>
+<th width="406">
+<Text id="701">GNU Image-Manipulation Program (programme de manipulation d'images de GNU), utilisÃ© (sur Unix) pour crÃ©er les icones de Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="702">GML</Text>
+</th>
+<th width="406">
+<Text id="703">Greenstone Markup Language (langage de balisage de Greenstone), un format compatible XML utilisÃ© pour stocker les documents de maniÃšre interne</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="704">GNU, licence publique gÃ©nÃ©rale (GPL)</Text>
+</th>
+<th width="406">
+<Text id="705">licence de logiciels qui permet aux utilisateurs de copier et de distribuer librement les programmes d'ordinateurs qu'elle couvre, ainsi que de les modifier, pour peu que toutes les modifications soient rendues publiques</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="706">Greenstone</Text>
+</th>
+<th width="406">
+<Text id="707">Nom de ce logiciel de bibliothÃšque numÃ©rique </Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="708">GSDL</Text>
+</th>
+<th width="406">
+<Text id="709">AbrÃ©viation de \lang{Greenstone Digital Library} (bibliothÃšque numÃ©rique Greenstone)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="710"><i>%GSDLHOME%</i></Text>
+</th>
+<th width="406">
+<Text id="711">Variable pour le systÃšme d'exploitation (Windows) reprÃ©sentant le rÃ©pertoire racine oÃ¹ tous les programmes et collections Greenstone sont stockÃ©s (<i>$GSDLHOME</i>sur des systÃšmes Unix)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="712"><i>%GSDLOS%</i></Text>
+</th>
+<th width="406">
+<Text id="713">Variable pour le systÃšme d'exploitation (Windows) reprÃ©sentant le systÃšme d'exploitation en cours d'utilisation (<i>$GSDLOS</i>sur des systÃšmes Unix)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="714"><i>hashfile</i>DL</Text>
+</th>
+<th width="406">
+<Text id="715">Programme Greenstone utilisÃ© au moment de l'import ou de la construction pour gÃ©nÃ©rer l'OID de chaque document</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="716">HTML</Text>
+</th>
+<th width="406">
+<Text id="717">HyperText Markup Language (langage de balisage pour l'hypertexte), le langage dans lequel la plupart des documents web sont Ã©crits</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="718"><i>import.pl</i></Text>
+</th>
+<th width="406">
+<Text id="719">Programme Greenstone utilisÃ© pour importer des documents</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="720">Importing</Text>
+</th>
+<th width="406">
+<Text id="721">Processus de rassemblement de collections de documents dans le systÃšme Greenstone </Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="722">Index</Text>
+</th>
+<th width="406">
+<Text id="723">Structure d'information utilisÃ©e pour la recherche ou la navigation au sein d'une collection</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="724">InstallShield</Text>
+</th>
+<th width="406">
+<Text id="725">Programme Windows, utilisÃ© par les cÃ©dÃ©roms Greenstone, qui permet Ã  un systÃšme d'Ãªtre installÃ© Ã  partir d'un cÃ©dÃ©rom</Text>
+</th>
+</tr>
+<tr>
+<tr>
+<th width="123">
+<Text id="726">Principal, fichier de configuration</Text>
+</th>
+<th width="406">
+<Text id="727">Fichier contenant les spÃ©cifications communes Ã  toutes les collections servies par un site</Text>
+</th>
+</tr>
+<th width="123">
+<Text id="728">MÃ©ta-donnÃ©es</Text>
+</th>
+<th width="406">
+<Text id="729">Informations de description telles que l'auteur, le titre, la date, des mots-clefs, etc., associÃ©es Ã  un document (ou Ã  une collection de documents)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="730">MG</Text>
+</th>
+<th width="406">
+<Text id="731">Managing Gigabytes (gÃ©rer les giga-octets), programme utilisÃ© par le systÃšme Greenstone pour l'indexation du corps du texte, embarquant des techniques de compression (voir Ã  ce sujet le livre de Witten, I.H., Moffat, A., et Bell, T. intitulÃ© \mytitle{Managing Gigabytes: compressing and indexing documents and images} (gÃ©rer les giga-octets: compression et indexation des documents et des images), Morgan Kaufmann, deuxiÃšme Ã©dition, 1999)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="732"><i>mgbuild</i></Text>
+</th>
+<th width="406">
+<Text id="733">Programme MG utilisÃ© pour construire un index de corps du texte</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="734"><i>mgquery</i></Text>
+</th>
+<th width="406">
+<Text id="735">Programme MG utilisÃ© pour effectuer des requÃªtes dans un index compressÃ© de corps du texte</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="736"><i>mkcol.pl</i></Text>
+</th>
+<th width="406">
+<Text id="737">Programme Greenstone qui crÃ©e et initialise la structure de rÃ©pertoire d'une nouvelle collection</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="738">Nouvelle-ZÃ©lande, projet de bibliothÃšque numÃ©rique de</Text>
+</th>
+<th width="406">
+<Text id="739">Projet de recherche du dÃ©partement d'informatique de l'universitÃ© de Waikato en Nouvelle-ZÃ©lande, qui a crÃ©Ã© le logiciel Greenstone (<u>nzdl.org</u>)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="740">OID</Text>
+</th>
+<th width="406">
+<Text id="741">Object Identifier (identifiant d'objet), code d'identification unique associÃ© Ã  un document</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="742">Perl</Text>
+</th>
+<th width="406">
+<Text id="743">Langage de programmation utilisÃ© pour une grande partie des opÃ©rations de manipulation de texte se dÃ©roulant lors du processus de construction</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="744">Ping</Text>
+</th>
+<th width="406">
+<Text id="745">Message envoyÃ© Ã  un systÃšme pour dÃ©terminer s'il est en fonctionnement ou non</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="746">Greffon (Â«pluginÂ»)</Text>
+</th>
+<th width="406">
+<Text id="747">Module de code qui gÃšre des documents de divers formats, utilisÃ© lors des processus d'import et de construction</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="748">Protocole</Text>
+</th>
+<th width="406">
+<Text id="749">Ensemble de conventions par lesquelles le rÃ©ceptionniste de Greenstone communique avec un serveur de collection</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="750">OrdonnÃ©e, requÃªte</Text>
+</th>
+<th width="406">
+<Text id="751">RequÃªte Ã  un systÃšme de rapatriement d'informations effectuÃ©e en langage naturel, et ordonnant les documents trouvÃ©s par ordre de pertinence</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="752">RÃ©ceptionniste</Text>
+</th>
+<th width="406">
+<Text id="753">Programme qui organise l'interface utilisateur de Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="754">RTF</Text>
+</th>
+<th width="406">
+<Text id="755">Rich Text Format (format de texte enrichi), format standard pour l'Ã©change de documents texte</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="756">Recherche</Text>
+</th>
+<th width="406">
+<Text id="757">AccÃšs Ã  une collection Ã  travers une recherche dans le corps du texte de ses contenus (ou d'une partie de ses contenus, telle que les titres de sections)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="758">Serveur</Text>
+</th>
+<th width="406">
+<Text id="759">Voir Â«Collection, serveur deÂ» et Â«Web, serveurÂ»</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="760"><i>setup.bat, setup.sh, setup.csh</i></Text>
+</th>
+<th width="406">
+<Text id="761">Script utilisÃ© pour mettre en place l'environnement nÃ©cessaire Ã  la reconnaissance du logiciel Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="762">Site, fichier de configuration de</Text>
+</th>
+<th width="406">
+<Text id="763">Fichier contenant les spÃ©cifications utilisÃ©es pour configurer le logiciel Greenstone pour le site particulier sur lequel il est installÃ©. </Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="764">Troncature</Text>
+</th>
+<th width="406">
+<Text id="765">Ãter la terminaison d'un mot dans un terme de requÃªte pour gÃ©nÃ©raliser la requÃªte</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="766">STL</Text>
+</th>
+<th width="406">
+<Text id="767">Standard template library} (bibliothÃšque standard de patrons), bibliothÃšque trÃšs rÃ©pandue de code C++, dÃ©veloppÃ©e par Silicon Graphics</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="768">txt2db</Text>
+</th>
+<th width="406">
+<Text id="769">Programme Greenstone utilisÃ© au moment de la construction pour crÃ©er la base de donnÃ©es GDBM</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="770">Unicode</Text>
+</th>
+<th width="406">
+<Text id="771">SystÃšme standard de reprÃ©sentation des ensembles de caractÃšres utilisÃ©s dans les langues du monde</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="772">UNU</Text>
+</th>
+<th width="406">
+<Text id="773">L'universitÃ© des Nations-Unies; on utilise Ã©galement ce sigle pour Ã©voquer une collection Greenstone crÃ©Ã©e pour cette organisation</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="774">Web, serveur</Text>
+</th>
+<th width="406">
+<Text id="775">Programme standard utilisÃ© par les ordinateurs pour publier de l'information sur le web</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="776">XML</Text>
+</th>
+<th width="406">
+<Text id="777">Format standard pour les documents et les donnÃ©es structurÃ©s sur le web (le langage de balisage de Greenstoneâvoir Ã  ce sujet Â«GMLÂ»âest un format compatible XML)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="778">N.D.T. : Respectivement Â«etÂ», Â«ouÂ», et Â«nonÂ» en anglais.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/manual.dtd
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/manual.dtd	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/manual.dtd	(revision 13632)
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--DTD generated by XMLSpy v2006 rel. 3 sp2 (http://www.altova.com)-->
+<!ELEMENT Affiliation (Text)>
+<!ELEMENT Author (Text)>
+<!ELEMENT BulletItem (Text, BulletList?)>
+<!ELEMENT BulletList (BulletItem+)>
+<!ELEMENT Chapter (Title, Content)>
+<!ATTLIST Chapter
+	id CDATA #REQUIRED
+>
+<!ELEMENT CodeLine (#PCDATA | i | br)*>
+<!ELEMENT Comment (Text)>
+<!ELEMENT Content (Text | BulletList | Section | Subsection | CodeLine | Figure | Indented | Table | NumberedList | Part)+>
+<!ELEMENT Date (Text)>
+<!ELEMENT Figure (Title, CodeLine*, File?)>
+<!ATTLIST Figure
+	id CDATA #REQUIRED
+	class CDATA #IMPLIED
+>
+<!ELEMENT File EMPTY>
+<!ATTLIST File
+	url CDATA #REQUIRED
+	height CDATA #REQUIRED
+	width CDATA #REQUIRED
+>
+<!ELEMENT Footnote (Text)>
+<!ATTLIST Footnote
+	id CDATA #REQUIRED
+>
+<!ELEMENT FootnoteList (Footnote+)>
+<!ELEMENT FootnoteRef EMPTY>
+<!ATTLIST FootnoteRef
+	id CDATA #REQUIRED
+>
+<!ELEMENT Heading (Text)>
+<!ELEMENT Indented (Text)>
+<!ELEMENT Manual (Heading, Title, Author, Affiliation, Text, Comment, Version, Date, Section+, Chapter+, FootnoteList)>
+<!ELEMENT NumberedItem (Text)>
+<!ELEMENT NumberedList (NumberedItem+)>
+<!ELEMENT Part (Title, Content)>
+<!ATTLIST Part
+	id CDATA #REQUIRED
+>
+<!ELEMENT Section (Title, Content)>
+<!ATTLIST Section
+	id CDATA #REQUIRED
+>
+<!ELEMENT Subsection (Title, Content)>
+<!ATTLIST Subsection
+	id CDATA #REQUIRED
+>
+<!ELEMENT Table (Title, TableContent)>
+<!ATTLIST Table
+	id CDATA #REQUIRED
+	class CDATA #IMPLIED
+>
+<!ELEMENT TableContent (tr+)>
+<!ELEMENT Text (#PCDATA | b | i | FootnoteRef | br | File)*>
+<!ATTLIST Text
+	id CDATA #REQUIRED
+>
+<!ELEMENT Title (Text*)>
+<!ELEMENT Version (Text)>
+<!ELEMENT b (#PCDATA | b | br)*>
+<!ELEMENT br EMPTY>
+<!ELEMENT i (#PCDATA | br)*>
+<!ELEMENT th (Text | CodeLine)+>
+<!ATTLIST th
+	width CDATA #REQUIRED
+>
+<!ELEMENT tr (th+)>
Index: /trunk/gsdl-documentation/manuals/xml-source/ru/Develop_ru.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/ru/Develop_ru.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/ru/Develop_ru.xml	(revision 13632)
@@ -0,0 +1,6233 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">ÐŠÐÐ€Ð ÐÐÐÐ¯ ÐÐÐÐÐÐÐ¢ÐÐÐ GREENSTONE</Text>
+</Heading>
+<Title>
+<Text id="2">Ð Ð£ÐÐÐÐÐÐ¡Ð¢ÐÐ</Text>
+</Title>
+<Author>
+<Text id="3">David Bainbridge, Dana McKay and Ian H. Witten</Text>
+</Author>
+<Affiliation>
+<Text id="4">Ð€Ð°ÐºÑÐ»ÑÑÐµÑ ÐÐŸÐŒÐ¿ÑÑÑÐµÑÐœÑÑ
+ ÐÐ°ÑÐº<br/> Ð£ÐœÐžÐ²ÐµÑÑÐžÑÐµÑ ÐÐ°Ð¹ÐºÐ°ÑÐŸ, ÐÐŸÐ²Ð°Ñ ÐÐµÐ»Ð°ÐœÐŽÐžÑ</Text>
+</Affiliation>
+<Text id="5">Greenstone - Ð¿Ð°ÐºÐµÑ Ð¿ÑÐžÐºÐ»Ð°ÐŽÐœÑÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ, Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐ¹ ÐŽÐ»Ñ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœÐžÑ ÑÐžÑÑÐŸÐ²ÑÑ
+ ÑÐŸÐœÐŽÐŸÐ² Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐº. Ð­ÑÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑÑÑ ÐœÐŸÐ²ÑÐŒ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž Ðž Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐž ÐµÐµ Ð² ÑÐµÑÐž ÐÐœÑÐµÑÐœÐµÑ ÐžÐ»Ðž ÐœÐ° CD-ROM. ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°ÐœÐŸ Ð² ÐÐŸÐ²ÐŸÐ·ÐµÐ»Ð°ÐœÐŽÑÐºÐŸÐŒ ÑÐœÐžÐ²ÐµÑÑÐžÑÐµÑÐµ ÐÐ°Ð¹ÐºÐ°ÑÐŸ, Ð² ÑÐ°ÐŒÐºÐ°Ñ
+ ÐÑÐŸÐµÐºÑÐ° ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÑÐžÑÑÐŸÐ²ÑÑ
+ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐº Ð² ÑÐŸÑÑÑÐŽÐœÐžÑÐµÑÑÐ²Ðµ Ñ Ð®ÐÐÐ¡ÐÐ Ðž ÐÐÐ Human Info. ÐÑÑ
+ÐŸÐŽÐœÑÐ¹ Ð¿ÑÐŸÐŽÑÐºÑ - ÑÑÐŸ ÑÐ²ÐŸÐ±ÐŸÐŽÐœÐŸ ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÐµÐŒÐŸÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÐŸÐ»ÑÑÐžÑÑ Ð¿ÐŸ Ð°ÐŽÑÐµÑÑ http://greenstone.org. ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐŽÐ°ÐœÐœÐŸÐ³ÐŸ Ð¿ÑÐŸÐŽÑÐºÑÐ° ÐŸÐ³ÐŸÐ²Ð°ÑÐžÐ²Ð°ÐµÑÑÑ Ð² ÐÐžÑÐµÐœÐ·ÐžÐŸÐœÐœÐŸÐŒ ÑÐŸÐ³Ð»Ð°ÑÐµÐœÐžÐž ÐŸ ÑÐ²ÐŸÐ±ÐŸÐŽÐœÐŸÐŒ ÐŽÐŸÑÑÑÐ¿Ðµ GNU.</Text>
+<Comment>
+<Text id="6">ÐÑ ÐœÐ°ÐŽÐµÐµÐŒÑÑ, ÑÑÐŸ ÑÑÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ñ
+ÐŸÑÐŸÑÐŸ. ÐÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, ÑÐŸÐŸÐ±ÑÐžÑÐµ ÐŸ Ð»ÑÐ±ÑÑ
+ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ°Ñ
+ Ð¿ÐŸ Ð°ÐŽÑÐµÑÑ: greenstone@cs.waikato.ac.nz</Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">ÐÐ°ÑÑ 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">ÐÐ± ÑÑÐŸÐ¹ ÐžÐœÑÑÑÑÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="10">ÐÐ°ÑÑÐŸÑÑÐµÐµ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ Ð¿ÑÐžÐœÑÐžÐ¿Ñ ÑÐ°Ð±ÐŸÑÑ Greenstone. ÐÐœÐŸ Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐŸ ÐŽÐ»Ñ ÑÐµÑ
+, ÐºÑÐŸ Ñ
+ÐŸÑÐµÑ ÑÐ°ÐŒÐŸÑÑÐŸÑÑÐµÐ»ÑÐœÐŸ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ Ðž ÐºÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ.</Text>
+<Text id="11">Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Chapter" ref="understanding_the_collection-building_process"/> ÐŽÐ°ÐµÑ ÑÑÐµÑÐœÑÑ Ð·Ð°Ð¿ÐžÑÑ Ð»ÐžÑÑ, ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ ÑÑÐ°ÑÑÐ²ÑÑÑÐµÐŒÑ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, Ð²ÐºÐ»ÑÑÐ°Ñ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐºÑ ÑÑÑÑÐºÑÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹, Ð²ÐœÑÑÑÐµÐœÐœÐµÐ³ÐŸ ÑÐŸÑÐŒÐ°ÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ðž ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑ ÑÑÑÑÐºÑÑÑÐŸÐ¹ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Chapter" ref="getting_the_most_out_of_your_documents"/> ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÑÐ°ÑÑÐž GreenÂ¬stone, ÐºÐŸÑÐŸÑÑÐµ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÑÑ ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ (Ðž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ) Ðž ÑÐµÐ³Ð»Ð°ÐŒÐµÐœÑÐžÑÑÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÑÐµÑÐµÐ· ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ. ÐÐŽÐµÑÑ ÑÐ°ÐºÐ¶Ðµ ÐŸÐ¿ÐžÑÑÐ²Ð°ÑÑÑÑ "Ð²ÐœÐµÑÐœÐžÐµ" Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐµ ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÑÑÑÑ Ð²ÐŒÐµÑÑÐµ Ñ Greenstone. Ð ÑÐ°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Chapter" ref="the_greenstone_runtime_system"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÑÑÑÑÐºÑÑÑÑ ÑÐžÑÑÐµÐŒÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ Greenstone, Ð° ÑÐ°ÐºÐ¶Ðµ ÐŽÐ°ÐœÐŸ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ, Ð¿ÑÐžÐ·Ð²Ð°ÐœÐœÐŸÐµ Ð¿ÐŸÐŒÐŸÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð»ÑÑÑÐµ Ð¿ÐŸÐœÑÑÑ, ÐºÐ°Ðº ÐŸÐœÐŸ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ðž ÐºÐ°Ðº ÐŒÐŸÐ¶ÐœÐŸ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÑÐžÑÑÐµÐŒÑ, ÑÑÐŸÐ±Ñ ÐŸÐœÐ° ÑÐŽÐŸÐ²Ð»ÐµÑÐ²ÐŸÑÑÐ»Ð° ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒ Ð¿ÐŸÑÑÐµÐ±ÐœÐŸÑÑÑÐŒ. Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Chapter" ref="configuring_your_greenstone_site"/> ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÑÐ°Ð¹Ð»Ñ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž Greenstone, Ð° Ð² ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐ° Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° ÑÐ°Ð±Ð»ÐŸÐœÐŸÐ² C++.</Text>
+<Text id="12">ÐÑÐž ÑÐ°Ð±ÐŸÑÐµ Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐŒ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµÐŒ GreenÂ¬stone ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÑÐŸÐ»ÐºÐœÑÑÑÑÑ ÑÐŸ ÑÑÑÐ»ÐºÐ°ÐŒÐž ÐœÐ° ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž ÑÐžÑÑÐµÐŒÑ, ÐºÐŸÑÐŸÑÑÐµ ÐœÐµ ÐŸÐ¿ÐžÑÐ°ÐœÑ Ð² ÐœÐ°ÑÑÐŸÑÑÐµÐŒ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ. Ð­ÑÐŸ ÑÐ²ÑÐ·Ð°ÐœÐŸ Ñ ÑÐµÐŒ, ÑÑÐŸ Greenstone ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸÐŒ ÑÐ°Ð·Ð²ÐžÑÐžÐž. Ð§ÑÐŸÐ±Ñ Ð±ÑÑÑ Ð² ÐºÑÑÑÐµ ÑÐµÐºÑÑÐµÐ¹ ÑÐ°Ð±ÐŸÑÑ, Ð¿ÐŸÐŽÐ¿ÐžÑÐžÑÐµÑÑ ÐœÐ° ÑÐ°ÑÑÑÐ»ÐºÑ Greenstone (ÐžÐœÑÑÑÑÐºÑÐžÐž ÐœÐ° ÑÐ°Ð¹ÑÐµ greenstone.org).</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="13">Ð¡ÐŸÐ¿ÑÑÑÑÐ²ÑÑÑÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ</Text>
+</Title>
+<Content>
+<Text id="14">ÐÐŸÐ»ÐœÑÐ¹ ÐºÐŸÐŒÐ¿Ð»ÐµÐºÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÐž Ðº Greenstone ÑÐŸÑÑÐŸÐžÑ ÐžÐ· Ð¿ÑÑÐž ÑÐŸÐŒÐŸÐ²:</Text>
+<BulletList>
+<Bullet>
+<Text id="15">Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð¿ÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">ÐÐœÑÑÑÑÐºÑÐžÑ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ (ÑÑÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ) ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="17">Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐº Ð° ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="18">ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: ÐŸÑ ÐÑÐŒÐ°Ð³Ðž ÐŽÐŸ ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Bullet>
+<Bullet>
+<Text id="19">ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÑÐ³Ð°ÐœÐ°Ð¹Ð·ÐµÑÐ°</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="20">ÐÐ»Ð°Ð³ÐŸÐŽÐ°ÑÐœÐŸÑÑÑ</Text>
+</Title>
+<Content>
+<Text id="21">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone - Ð¿ÑÐŸÐŽÑÐºÑ ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸÐ³ÐŸ ÑÑÑÐŽÐ° ÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ð° Ð»ÑÐŽÐµÐ¹. Rodger McNab Ðž Stefan Boddie Ð¿ÑÐžÐœÑÐžÐ¿ÐžÐ°Ð»ÑÐœÑÐµ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐž ÑÐžÑÑÐµÐŒÑ. ÐÐµÐŸÑÐµÐœÐžÐŒÑÐ¹ Ð²ÐºÐ»Ð°ÐŽ Ð²ÐœÐµÑÐ»Ðž David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, Ðž Stuart Yeates. ÐÑÑÐ°Ð»ÑÐœÑÐµ ÑÐ»ÐµÐœÑ ÐÑÐŸÐµÐºÑÐ° ÐÐŸÐ²ÐŸÐ·ÐµÐ»Ð°ÐœÐŽÑÐºÐŸÐ¹ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž  ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°Ð»Ðž Ð²ÐŽÐŸÑ
+ÐœÐŸÐ²ÐµÐœÐœÑÐ¹ ÐŽÐžÐ·Ð°Ð¹Ðœ Ð²ÑÐµÐ¹ ÑÐžÑÑÐµÐŒÑ: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols Ðž Lloyd Smith. ÐÑ ÑÐ°ÐºÐ¶Ðµ Ð²ÑÑÐ°Ð¶Ð°ÐµÐŒ ÑÐ²ÐŸÑ Ð¿ÑÐžÐ·ÐœÐ°ÑÐµÐ»ÑÐœÐŸÑÑÑ Ð²ÑÐµÐŒ ÑÐµÐŒ, ÐºÑÐŸ ÑÑÑÐŽÐžÐ»ÑÑ ÐœÐ°ÐŽ ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµÐŒ Ð¿Ð°ÐºÐµÑÐŸÐ², Ð¿ÐŸÐ¿Ð°ÐŽÐ°ÑÑÐžÑ
+ Ð¿ÐŸÐŽ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð»ÐžÑÐµÐœÐ·ÐžÐž  GNU, Ðž Ð²ÐºÐ»ÑÑÐµÐœÐœÑÑ
+ Ð² ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE Ðž XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="understanding_the_collection-building_process">
+<Title>
+<Text id="22">ÐÐŸÐœÑÑÐžÐµ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</Title>
+<Content>
+<Text id="23">ÐÐŸÐœÐµÑÐœÑÐ¹ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Greenstone ÐŒÐŸÐ¶ÐµÑ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ (Collector), ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐ¹ Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐµ <i>ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ</i> (Ð Ð°Ð·ÐŽÐµÐ» 3). ÐÐœ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐŸÑÐµÐœÑ Ð¿ÑÐŸÑÑÐŸ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐ° Ð±Ð°Ð·Ðµ ÑÐ¶Ðµ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÑ
+, ÐœÐŸ Ñ ÐœÐŸÐ²ÑÐŒ ÐœÐ°Ð¿ÐŸÐ»ÐœÐµÐœÐžÐµÐŒ. ÐÐŽÐœÐ°ÐºÐŸ ÐœÐµÐ²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐŸÐŒ Ð¿ÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ñ Ð°Ð±ÑÐŸÐ»ÑÑÐœÐŸ ÐœÐŸÐ²ÐŸÐ¹ ÑÑÑÑÐºÑÑÑÐŸÐ¹. Ð ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ Ð¿ÑÐžÐŽÐµÑÑÑ Ð²ÐœÐŸÑÐžÑÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð² ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐ¹, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑ ÑÑÑÑÐºÑÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð²ÐµÐŽÑ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÑÐ°ÐŽÐžÐºÐ°Ð»ÑÐœÑÐµ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð²ÐŸÐ·ÑÐŒÐµÐ»Ðž ÑÑÑÐµÐºÑ, ÐÐ°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð·ÐœÐ°ÑÑ Ð³ÐŸÑÐ°Ð·ÐŽÐŸ Ð±ÐŸÐ»ÑÑÐµ ÐŸ ÑÐžÑÑÐµÐŒÐµ Greenstone. ÐÐ°ÐœÐœÑÐ¹ ÑÐ°Ð·ÐŽÐµÐ» ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð²ÑÐµ, ÑÑÐŸ ÐÐ°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð·ÐœÐ°ÑÑ ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ. Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÑÐ°ÐºÐ¶Ðµ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑÑÑ ÑÑÑÑÐºÑÑÑÐ° ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹ Greenstone Ðž ÑÐŸÑÐŒÐ°Ñ Ð²ÐœÑÑÑÐµÐœÐœÐµÐ³ÐŸ Ñ
+ÑÐ°ÐœÐµÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+<Text id="24">ÐÑ Ð¿ÐŸÐŽÑÐ°Ð·ÑÐŒÐµÐ²Ð°ÐµÐŒ, ÑÑÐŸ ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÑÐžÑÑÐµÐŒÐ° Greenstone, ÑÐºÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÐœÐœÐ°Ñ Ð¿ÐŸÐŽ ÐŸÐ±ÐŸÐ»ÐŸÑÐºÑ Windows ÐžÐ»Ðž Unix. ÐÑÐ»Ðž  Ð²Ñ   ÐµÑÐµ  ÐœÐµ  ÑÑÑÐ°ÐœÐŸÐ²ÐžÐ»Ðž  ÑÐžÑÑÐµÐŒÑ, ÑÐŸ   ÑÐŽÐµÐ»Ð°Ð¹ÑÐµ  ÑÑÐŸ, Ð²ÐŸÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ð²ÑÐžÑÑ ÐºÐŸÐŒÐ¿Ð»ÐµÐºÑÐŸÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÐž <i>ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð¿ÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ</i>. ÐÐ»Ñ ÐŸÐ±ÑÐ°ÑÐµÐœÐžÑ Ðº ÐŸÑÐœÐŸÐ²ÐœÐŸÐŒÑ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ñ Greenstone Ð¿ÐŸÐ²ÑÐµÐŒÐµÑÑÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐžÐŒÑ <i>GSDLHOME</i>, ÐºÐŸÑÐŸÑÐŸÐµ ÐŽÐ»Ñ ÑÐžÑÑÐµÐŒÑ Windows Ð²ÑÐ³Ð»ÑÐŽÐžÑ ÐºÐ°Ðº <i>%GSDLHOME%</i>, Ð° ÐŽÐ»Ñ Unix - <i>$GSDLHOME</i>. ÐÑ ÑÐŸÐ·ÐŽÐ°ÐµÑÐµ ÑÑÐŸÑ ÐºÐ°ÑÐ°Ð»ÐŸÐ³ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Greenstone ÐœÐ° Ð²Ð°Ñ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑ.</Text>
+<Section id="building_collections_from_the_command_line">
+<Title>
+<Text id="25">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐžÐ· ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž</Text>
+</Title>
+<Content>
+<Text id="26">ÐÐ°ÑÐ°Ð² ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐžÐ· ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž, Ð²Ñ Ð¿ÑÐŸÐ¹ÐŽÐµÑÐµ Ð¿ÐŸ Ð²ÑÐµÐ¹ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÐµÐ¿ÐŸÑÐºÐµ, ÑÑÐŸ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÐžÑ Ð²Ð°ÐŒ Ð»ÑÑÑÐµ Ð¿ÐŸÐœÑÑÑ ÑÑÐŸÑ Ð¿ÑÐŸÑÐµÑÑ. Ð Ð°Ð·ÑÐŒÐµÐµÑÑÑ, ÐŽÐ»Ñ ÐœÐ°ÐžÐ±ÐŸÐ»ÑÑÐµÐ³ÐŸ ÑÐžÑÐ»Ð° ÑÑ
+ÐŸÐ¶ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð²Ñ Ð±ÑÐŽÐµÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐŸÐŒ. ÐÐ»Ñ Ð¿ÑÐžÐŒÐµÑÐ° ÐŒÑ Ð²ÐŸÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐµÐ¹ÑÑ ÐœÐ° ÑÑÑÐ°ÐœÐŸÐ²ÐŸÑÐœÐŸÐŒ CD-ROM Ðž ÑÐŸÑÑÐŸÑÑÐµÐ¹ ÐžÐ· ÐŽÐŸÐŒÐ°ÑÐœÐžÑ
+ WWW-ÑÑÑÐ°ÐœÐžÑ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ð° Ð»ÐžÑ, ÑÐ°Ð±ÐŸÑÐ°Ð²ÑÐžÑ
+ ÐœÐ°ÐŽ Ð¿ÑÐŸÐµÐºÑÐŸÐŒ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐÐŸÐ²ÐŸÐ·ÐµÐ»Ð°ÐœÐŽÑÐºÐŸÐ¹ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ðž ÑÐžÑÑÐµÐŒÐŸÐ¹ Greenstone.</Text>
+<Text id="27">ÐÑÐŽÐµÐ»ÑÐœÑÐµ Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»Ñ Ð¿ÑÐ°ÐºÑÐžÑÐµÑÐºÐž ÐœÐµ ÐŸÑÐ»ÐžÑÐ°ÑÑÑÑ ÐŽÑÑÐ³ ÐŸÑ ÐŽÑÑÐ³Ð°, ÐŸÐŽÐœÐ°ÐºÐŸ ÐŸÐœÐž Ð±ÑÐ»Ðž ÑÐŸÐ·ÐŽÐ°ÐœÑ ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ñ Greenstone Ð² ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÑÑ
+ ÑÑÐµÐŽÐ°Ñ
+, ÑÐ°ÐºÐžÑ
+ ÐºÐ°Ðº Windows Ðž Unix. ÐÐ°ÐŒ ÐŸÑÑÐ°ÐµÑÑÑ ÑÐŸÐ»ÑÐºÐŸ Ð²ÑÐ±ÑÐ°ÑÑ. ÐœÐ° Ð±Ð°Ð·Ðµ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ Ð²Ð°ÑÐµÐ³ÐŸ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°. ÐÑÐž Ð±ÐµÐ³Ð»ÐŸÐŒ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž ÐŒÐŸÐ³ÑÑ Ð²Ð°ÐŒ Ð¿ÐŸÐºÐ°Ð·Ð°ÑÑÑÑ ÐœÐµÐ¿ÐŸÐœÑÑÐœÑÐŒÐž Ðž ÑÐ°ÐžÐœÑÑÐ²ÐµÐœÐœÑÐŒÐž, ÐŸÐŽÐœÐ°ÐºÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐžÑÐµ ÐžÑ
+, Ð±Ð»ÐžÐ·ÐºÐŸ Ð¿ÑÐžÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑÑ Ðº ÐžÐœÑÑÑÑÐºÑÐžÑÐŒ - Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÑÑÐžÑ
+ ÐŸÐ¿ÐµÑÐ°ÑÐžÐ¹ Ð±ÑÐŽÐµÑ ÐŽÐ°ÐœÐŸ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ Ð¿ÐŸÐ·Ð¶Ðµ. Ð ÐºÐŸÐœÑÐµ Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»Ð° ÐŽÐ°ÐœÐŸ ÐºÑÐ°ÑÐºÐŸÐµ ÑÐµÐ·ÑÐŒÐµ ÐŸ ÑÐ°Ð·Ð»ÐžÑÐžÑÑ
+ ÐŒÐµÐ¶ÐŽÑ Ð¿ÑÐŸÑÐµÑÑÐ°ÐŒÐž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐœÐ° Ð±Ð°Ð·Ðµ Widows Ðž Unix.</Text>
+<Subsection id="collection_building_under_windows">
+<Title>
+<Text id="28">Ð€ÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð¿ÐŸÐŽ Windows</Text>
+</Title>
+<Content>
+<Text id="29">ÐÑÐž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Greenstone Ð² ÑÑÐµÐŽÐµ Windows ÑÐµÑÐµÐ· ÐºÐŸÐŒÐ°ÐœÐŽÐœÑÑ ÑÑÑÐŸÐºÑ ÐžÐ·ÐœÐ°ÑÐ°Ð»ÑÐœÐŸ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð·Ð°Ð¿ÑÑÑÐžÑÑ "command prompt" - Ð¿ÑÐžÐ³Ð»Ð°ÑÐµÐœÐžÐµ ÐŽÐ»Ñ Ð²Ð²ÐŸÐŽÐ° Ð²Ð°ÑÐžÑ
+ ÐºÐŸÐŒÐ°ÐœÐŽ. ÐÐŸÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÐŸÑÐŒÐŸÑÑÐµÑÑ ÑÐµÑÐµÐ· ÐŸÑÐœÐŸÐ²ÐœÐŸÐµ ÐŒÐµÐœÑ Start -^Programs, ÐœÐ°Ð¹ÐŽÐžÑÐµ MS-DOS Prompt, DOS Prompt, ÐžÐ»Ðž Command Prompt. ÐÑÐ»Ðž Ð²Ñ ÐœÐµ ÐœÐ°ÑÐ»Ðž ÐœÐžÑÐµÐ³ÐŸ ÐžÐ· ÐŸÐ¿ÐžÑÐ°ÐœÐœÐŸÐ³ÐŸ Ð²ÑÑÐµ, Ð·Ð°Ð¿ÑÑÑÐžÑÐµ Start ~$Run Ðž Ð² ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÐŸÐŒ ÐŸÐºÐœÐµ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ command (or cmd). ÐÑÐ»Ðž Ð·Ð°Ð¿ÑÑÐº ÐºÐŸÐŒÐ°ÐœÐŽÑ ÐŸÐºÐŸÐœÑÐžÐ»ÑÑ Ð±ÐµÐ·ÑÑÐ¿ÐµÑÐœÐŸ, ÑÐŸ ÐŸÐ±ÑÐ°ÑÐžÑÐµÑÑ Ðº ÑÐ²ÐŸÐµÐŒÑ ÑÐžÑÑÐµÐŒÐœÐŸÐŒÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑÑ.</Text>
+<Text id="30">ÐÐœÐµÑÐžÑÐµ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð² ÐºÐ°ÑÐ°Ð»ÐŸÐ³, Ð² ÐºÐŸÑÐŸÑÑÐ¹ Ð±ÑÐ»Ð° ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÑÐžÑÑÐµÐŒÐ° Greenstone. ÐÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Greenstone ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ Ð² ÐºÐ°ÑÐ°Ð»ÐŸÐ³, Ð² ÐºÐŸÑÐŸÑÑÐ¹ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÐŸÐ¿Ð°ÑÑÑ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð²</Text>
+<CodeLine>cd "C:\Program Files\gsdl "</CodeLine>
+<Text id="31">(ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐºÐ°Ð²ÑÑÐºÐž ÐžÐ·-Ð·Ð° Ð¿ÑÐŸÐ±ÐµÐ»Ð° Ð² ÐžÐŒÐµÐœÐž ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Program Files). ÐÐ°Ð»ÐµÐµ, Ð² ÑÐ»ÐµÐŽÑÑÑÐµÐŒ ÐŸÐºÐœÐµ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ</Text>
+<CodeLine>setup.bat</CodeLine>
+<Text id="32">Ð­ÑÐŸÑ ÑÐ°Ð¹Ð» (ÐºÐŸÑÐŸÑÑÐ¹ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ) ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÐžÑÑÐµÐŒÐµ, Ð³ÐŽÐµ ÐžÑÐºÐ°ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Greenstone<FootnoteRef id="1"/>. ÐÑÐ»Ðž Ð¿ÑÐž ÑÐ°Ð±ÐŸÑÐµ Ð² ÐžÐœÑÐµÑÐ°ÐºÑÐžÐ²ÐœÐŸÐŒ ÑÐµÐ°ÐœÑÐµ DOS prompt Ð²Ñ Ð·Ð°Ñ
+ÐŸÑÐžÑÐµ Ð²ÐµÑÐœÑÑÑÑÑ ÐœÐ° Ð²ÐµÑÑ
+ÐœÐžÐ¹ ÑÑÐŸÐ²ÐµÐœÑ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ð° Greenstone Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŽÐµÐ»Ð°ÑÑ ÑÑÐŸ, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð² cd "%GSDLHOME%" (ÐœÐµÐ¿ÑÐµÐŒÐµÐœÐœÐŸ Ð² ÐºÐ°Ð²ÑÑÐºÐ°Ñ
+). ÐÑÐ»Ðž Ð²Ñ Ð·Ð°ÐºÐŸÐœÑÐžÐ»Ðž ÑÐ°Ð±ÐŸÑÑ Ð² ÐŸÐºÐœÐµ DOS, Ð° Ð¿ÐŸÑÐŸÐŒ Ð·Ð°Ð¿ÑÑÑÐžÐ»Ðž ÐœÐŸÐ²ÑÑ ÑÐµÑÑÐžÑ, ÑÐŸ Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ Ð·Ð°Ð¿ÑÑÑÐžÑÑ Ð·Ð°ÐœÐŸÐ²ÐŸ setup.bat.</Text>
+<Text id="33">Ð¢ÐµÐ¿ÐµÑÑ Ð²Ñ ÐžÐŒÐµÐµÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÑÑ ÐžÐ»Ðž Ð¿ÐµÑÐµÑÐŸÑÐŒÐžÑÐŸÐ²ÑÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¡ÐœÐ°ÑÐ°Ð»Ð° ÐŒÑ ÑÐ°ÑÑÐŒÐŸÑÑÐžÐŒ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ mkcol.pl, ÐœÐ°Ð¿ÐžÑÐ°ÐœÐœÑÑ ÐœÐ° Perl, ÐžÐŒÑ ÐºÐŸÑÐŸÑÐŸÐ¹ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ "make a collection" (ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž). ÐÐµÑÐ²ÑÐ¹ Ð·Ð°Ð¿ÑÑÐº ÑÑÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÑÑÐµÑÑÐ²ÐžÑÑ, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð² perl -S mkcol.pl, Ð¿ÑÐž ÑÑÐŸÐŒ ÐœÐ° ÑÐºÑÐ°ÐœÐµ Ð¿ÐŸÑÐ²ÐžÑÑÑ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ Ðž ÑÐ¿ÐžÑÐŸÐº Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ². ÐÑÐ»Ðž ÐŸÐºÑÑÐ¶ÐµÐœÐžÐµ Ð²Ð°ÑÐµÐ¹ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ Windows ÐœÐ°ÑÑÑÐŸÐµÐœÐŸ ÐœÐ° ÑÐ°Ð±ÐŸÑÑ Ñ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑÐŒÐž Perl, ÑÐ°Ð¹Ð»Ð°ÐŒÐž Ñ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµÐŒ .pi, ÑÐŸ ÑÑÐ° Ð¿ÑÐŸÑÐµÐŽÑÑÐ° ÐœÐµ Ð·Ð°Ð¹ÐŒÐµÑ ÐŒÐœÐŸÐ³ÐŸ Ð²ÑÐµÐŒÐµÐœÐž. ÐÐ°Ðº Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐŽÐµÑÑ Ð² Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐœÐŸÐŒ Ð¿ÑÐžÐŒÐµÑÐµ, ÐµÐŽÐžÐœÑÑÐ²ÐµÐœÐœÑÐ¹ ÐŸÐ±ÑÐ·Ð°ÑÐµÐ»ÑÐœÑÐ¹ Ð°ÑÐ³ÑÐŒÐµÐœÑ - ÑÑÐŸ creator (ÑÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ), ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»Ð·ÑÐµÑÑÑ ÐŽÐ»Ñ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ Ð»ÐžÑÐ°, ÑÐŸÑÐŒÐžÑÑÑÑÐµÐ³ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ.</Text>
+<Text id="34">Ð¢ÐµÐ¿ÐµÑÑ ÐŒÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒ ÑÑÑ ÐºÐŸÐŒÐ°ÐœÐŽÑ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÑÑÐŸÑÑÐµÐ¹ ÐžÐ· ÐŽÐŸÐŒÐ°ÑÐœÐžÑ
+ WWW-ÑÑÑÐ°ÐœÐžÑ ÑÑÐ°ÑÑÐœÐžÐºÐŸÐ² Ð¿ÑÐŸÐµÐºÑÐ° ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐŠÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone. ÐÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ Ð¿ÑÐžÑÐ²ÐŸÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐŒÑ, Ñ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð»</Text>
+<CodeLine>perl âS mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<Text id="35">(ÐžÐ»Ðž mkcol.pl âcreator me@cs. waikato. ac. nz dlpeople ÐµÑÐ»Ðž Perl ÑÐ²ÑÐ·Ð°Ðœ Ñ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµÐŒ ÑÐ°Ð¹Ð»Ð° .ÑÐ). ÐÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, Ð·Ð°ÐŒÐµÐœÐžÑÐµ ÐŒÐŸÐ¹ email Ð°ÐŽÑÐµÑ ÐœÐ° ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÑÐ¹!</Text>
+<Text id="36">ÐÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ð²ÐœÐŸÐ²Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² Ð¿ÐµÑÐµÐ¹ÐŽÐµÐŒ Ð² ÑÐŸÐ»ÑÐºÐŸ-ÑÑÐŸ ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÐ¹ ÐºÐ°ÑÐ°Ð»ÐŸÐ³ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ»Ñ ÑÑÐŸÑ Ð¿ÐµÑÐ°ÑÐ°ÐµÐŒ:</Text>
+<CodeLine>cd "%GSDLHOME%\collect\dlpeople "</CodeLine>
+<Figure id="collection_configuration_file_created_by_mkcol">
+<Title>
+<Text id="37">Collection configuration file created by <i>mkcol.pl</i></Text>
+</Title>
+<CodeLine>creatorÂ Â Â Â Â Â Â Â Â Â Â Â Â me@cs.waikato.ac.nz</CodeLine>
+<CodeLine>maintainerÂ Â Â Â Â Â Â Â Â Â me@cs.waikato.ac.nz</CodeLine>
+<CodeLine>publicÂ Â Â Â Â Â Â Â Â Â Â Â Â Â true</CodeLine>
+<CodeLine>betaÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â true</CodeLine>
+<CodeLine>indexesÂ Â Â Â Â Â Â Â Â Â Â Â Â document:text</CodeLine>
+<CodeLine>defaultindexÂ Â Â Â Â Â Â Â document:text</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â ZIPPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â GAPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â TEXTPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â HTMLPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â EMAILPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â ArcPlug</CodeLine>
+<CodeLine>pluginÂ Â Â Â Â Â Â Â Â Â Â Â Â Â RecPlug</CodeLine>
+<CodeLine>classifyÂ Â Â Â Â Â Â Â Â Â Â Â AZList -metadata "Title"</CodeLine>
+<CodeLine>collectionmetaÂ collectionnameÂ Â Â Â "dlpeople"</CodeLine>
+<CodeLine>collectionmetaÂ iconcollectionÂ Â Â Â ""</CodeLine>
+<CodeLine>collectionmetaÂ collectionextraÂ Â Â ""</CodeLine>
+<CodeLine>collectionmetaÂ .document:textÂ Â Â Â "documents "</CodeLine>
+</Figure>
+<Text id="38">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð²   dir.   Ð ÐœÐµÐ¹ ÐŽÐŸÐ»Ð¶ÐœÐŸ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑÑ 7 Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹: archives, building, etc, images, import, index Ðž perllib.</Text>
+<Text id="39">Ð¢ÐµÐ¿ÐµÑÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð·Ð°Ð¿ÐŸÐ»ÐœÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒÐž. ÐÑÑÐŸÑÐœÐžÐº ÐŒÐ°ÑÐµÑÐžÐ°Ð»ÐŸÐ² ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž dlpeople ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐœÐ° ÑÑÑÐ°ÐœÐŸÐ²ÐŸÑÐœÐŸÐŒ CD-ROM Greenstone Ð² ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ðµ collect\dlpeople. Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð²ÑÑÐ°Ð²ÑÑÐµ CD-ROM Ð² ÑÐžÑÐ°ÑÑÐµÐµ ÑÑÑÑÐŸÐ¹ÑÑÐ²ÐŸ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, D:\). ÐÐ°Ð»ÐµÐµ ÑÐºÐŸÐ¿ÐžÑÑÐ¹ÑÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ð°D:\collect\dlpeople Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ import ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž dlpeople. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŽÐµÐ»Ð°ÑÑ ÑÑÐŸ Ð² ÑÐ»ÐµÐŽÑÑÑÐµÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ:</Text>
+<Indented>
+<Text id="40">Ð²ÑÐŽÐµÐ»ÐžÑÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ð° dlpeople Ðž Ð¿ÐµÑÐµÐŒÐµÑÑÐžÑÐµ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ import ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž dlpeople.</Text>
+</Indented>
+<Text id="41">Ð ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²Ñ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÑÑ ÑÐ»ÐµÐŽÑÑÑÑÑ ÐºÐŸÐŒÐ°ÐœÐŽÑ:</Text>
+<CodeLine>xcopy /s d:\collect\dlpeople\* import</CodeLine>
+<Text id="42">Ð ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž etc ÑÑÑÐµÑÑÐ²ÑÐµÑ ÑÐ°Ð¹Ð» Ñ ÐžÐŒÐµÐœÐµÐŒ collect, cfg. ÐÑÐºÑÐŸÐ¹ÑÐµ ÐµÐ³ÐŸ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð»ÑÐ±ÐŸÐ¹ ÑÐµÐºÑÑÐŸÐ²ÑÐ¹ ÑÐµÐŽÐ°ÐºÑÐŸÑ, Ð»ÐžÐ±ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÑÐµÐŽÐ°ÐºÑÐŸÑ, ÐœÐ°ÑÑÑÐŸÐµÐœÐœÑÐ¹ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ. Ð ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ Ð²Ñ ÑÐ²ÐžÐŽÐžÑÐµ ÐŸÐºÐœÐŸ, ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ Ð²ÑÐ³Ð»ÑÐŽÐžÑ ÑÐ°Ðº, ÐºÐ°Ðº Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="collection_configuration_file_created_by_mkcol"/>, Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°Ñ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ³ÐŸ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÐºÐŸÐŒÐ°ÐœÐŽÑ perl-S mkcol.pl -creator me@cs.waikato.ac.nz dlpeople.</Text>
+<Text id="43">Ð¢ÐµÐ¿ÐµÑÑ Ð²Ñ Ð³ÐŸÑÐŸÐ²Ñ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. Ð­ÑÐŸ Ð¿ÑÐŸÑÐµÑÑ Ð¿ÐµÑÐµÐœÐŸÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÑÐžÑÑÐµÐŒÑ Greenstone, ÑÑÐ°ÐœÐŽÐ°ÑÑÐžÐ·Ð°ÑÐžÐž ÑÐŸÑÐŒÐ°ÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð¿ÑÑÐž ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÑÑÑÑÐºÑÑÑÑ ÑÐ°Ð¹Ð»Ð°, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ Ð±ÑÐŽÑÑ Ñ
+ÑÐ°ÐœÐžÑÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ. ÐÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ perl -Simport.pl Ðž Ð² ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ Ð²Ñ Ð¿ÐŸÐ»ÑÑÐžÑÐµ ÑÐ¿ÐžÑÐŸÐº ÐŸÐ¿ÑÐžÐ¹ ÐŽÐ»Ñ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž ÐžÐŒÐ¿ÐŸÑÑÐ°. ÐÐ»Ñ ÑÐ¿ÑÐŸÑÐµÐœÐžÑ Ð¿ÑÐŸÑÐµÑÑÐ° Ð²ÐŸÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµÑÑ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ¹ ÐºÐŸÐŒÐ°ÐœÐŽÐŸÐ¹:</Text>
+<CodeLine>perl âS import.pl -removeold dlpeople</CodeLine>
+<Text id="44">ÐÐµ Ð±ÐµÑÐ¿ÐŸÐºÐŸÐ¹ÑÐµÑÑ Ð¿ÐŸ Ð¿ÐŸÐ²ÐŸÐŽÑ Ð±ÑÑÑÑÐŸ Ð±ÐµÐ³ÑÑÐµÐ³ÐŸ Ð¿ÐŸ ÑÐºÑÐ°ÐœÑ ÑÐµÐºÑÑÐ° - ÑÑÐŸ ÐŸÑÑÐµÑ ÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐž Ð¿ÑÐŸÑÐµÐŽÑÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ°. Ð ÑÐ²ÐµÐŽÐµÐœÐžÑ, Ð¿ÑÐŸÑÐµÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ° ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð·Ð°ÐœÐžÐŒÐ°ÐµÑ ÐŸÐºÐŸÐ»ÐŸ 5 ÐŒÐžÐœÑÑ ÐœÐ° 1 ÐÐ¢Ñ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ Ðž ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐ»ÑÑÐµ ÐœÐ° Ð±ÐŸÐ»ÐµÐµ ÐŒÐµÐŽÐ»ÐµÐœÐœÑÑ
+ ÐŒÐ°ÑÐžÐœÐ°Ñ
+. ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÑÐŸ, ÑÑÐŸ Ð²Ñ ÐœÐµ ÐŽÐŸÐ»Ð¶ÐœÑ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑÑ
+ collect ÐžÐ»Ðž dlpeople Ð¿ÑÐž Ð·Ð°Ð¿ÑÑÐºÐµ ÑÑÐŸÐ¹ ÐºÐŸÐŒÐ°ÐœÐŽÑ; T.K.GSDLHOME ÑÐ¶Ðµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÐ» ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ Greenstone ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ².</Text>
+<Text id="45">Ð¢ÐµÐ¿ÐµÑÑ ÐŽÐ°Ð²Ð°Ð¹ÑÐµ Ð²ÐœÐµÑÐµÐŒ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð² ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐ»Ñ ÐŒÐŸÐŽÐžÑÐžÐºÐ°ÑÐžÐž ÐµÐ³ÐŸ Ð²ÐžÐŽÐ°. Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð¿ÑÐžÑÐ²ÐŸÐžÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐŒÑ. ÐÐœÐŸ Ð±ÑÐŽÐµÑ Ð²ÐŸÑÐ¿ÑÐžÐœÑÑÐŸ Ð²ÐµÐ±-Ð±ÑÐŸÑÐ·ÐµÑÐŸÐŒ, ÐºÐ°Ðº Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐŽÐ»Ñ ÑÐžÑÑÐ»ÑÐœÐŸÐ³ÐŸ Ð»ÐžÑÑÐ° WWW-ÑÑÑÐ°ÐœÐžÑÑ, Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐžÐºÐŸÐœÐºÐž Ð¿ÑÐž ÐŸÑÑÑÑÑÑÐ²ÐžÐž ÑÐžÑÑÐœÐºÐ°. ÐÐ·ÐŒÐµÐœÐžÐŒ ÑÑÑÐŸÐºÑ collectionmeta collectionname "dlpeople" ÐœÐ° ÑÑÑÐŸÐºÑ Ð²ÐžÐŽÐ° collectionmeta collectionname "The People of the NZDL project".</Text>
+<Text id="46">ÐÐŸÐ±Ð°Ð²ÐžÐŒ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐµÐ¶ÐŽÑ ÐºÐ°Ð²ÑÑÐºÐ°ÐŒÐž: <i>collectionmeta collectionextra ""</i>. ÐÐœÐŸ Ð±ÑÐŽÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐŸ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ð° ÐŽÐ»Ñ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐž ÑÐ°Ð·ÐŽÐµÐ»Ð° "About" (ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž) ÐœÐ° ÐŽÐŸÐŒÐ°ÑÐœÐµÐ¹ WWW-ÑÑÑÐ°ÐœÐžÑÐµ. Ð¯ ÐŽÐŸÐ±Ð°Ð²ÐžÐ» "This collection is made up of the homepages of some of the people who have worked on the NZDL project." ÐÐ°Ð¶ÐœÐŸ Ð²Ð²ÐŸÐŽÐžÑÑ ÑÑÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐŸÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐŸÐ¹ - ÐœÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐŽÐ»Ñ ÐŸÑÐ±ÐžÐ²ÐºÐž ÐºÐ»Ð°Ð²ÐžÑÑ Enter/ÐÐ²ÐŸÐŽ. ÐÑÐ»Ðž Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð² Ð²Ð°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐœÐŸÐ³ÐŸÑÐ·ÑÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ, ÑÐŸ ÑÑÑÐµÑÑÐ²ÑÐµÑ ÑÐ¿ÐŸÑÐŸÐ± Ð²ÑÐ²ÐŸÐŽÐ° ÐŽÐ°ÐœÐœÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ° Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ Ð²ÑÐ±ÑÐ°ÐœÐœÑÐŒ ÑÐ·ÑÐºÐŸÐŒ. Ð­ÑÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ Ð±ÑÐŽÐµÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐŸ ÐŽÐ°Ð»ÐµÐµ Ð² ÑÐ°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="configuration_file"/>.</Text>
+<Text id="47">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐŽÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐžÐºÐŸÐœÐŸÐº ÐœÐ° WWW-ÑÑÑÐ°ÐœÐžÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž; ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ, ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐµ ÐŒÐœÐŸÑ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐŽÐµÑÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="collection_icon"/>. Ð£ÐºÐ°Ð¶ÐžÑÐµ Ð¿ÑÑÑ ÐœÐ°Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ Ð² ÐºÐ°Ð²ÑÑÐºÐ°Ñ
+ Ð² ÑÑÑÐŸÐºÐµ collectionmeta iconcollection "" ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž. ÐÐ»Ñ ÐºÑÐ°ÑÐºÐŸÑÑÐž Ðž ÐŒÐŸÐ±ÐžÐ»ÑÐœÐŸÑÑÐž _httpprefix_ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ðœ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÑÐ°ÑÑÐŸÐ²ÐŸÐ³ÐŸ URL ÑÐºÐ°Ð·ÑÐ²Ð°ÑÑÐµÐ³ÐŸ ÐœÐ° ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐµÐµÑÑ Ð² ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ¹ ÐŸÐ±Ð»Ð°ÑÑÐž Greenstone. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²Ð²ÐµÑÑÐž: _httppreflx_/collect/dlpeople/images/icon.gif ÐµÑÐ»Ðž Ð²Ñ Ð¿ÐŸÐŒÐµÑÑÐžÐ»Ðž Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÐµÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (Ð² ÐœÐ°ÑÐµÐŒ Ð¿ÑÐžÐŒÐµÑÐµ ÑÑÐŸ: collect\dlpeople\images ).</Text>
+<Text id="48">Ð¡ÐŸÑ
+ÑÐ°ÐœÐžÑÐµ ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð·Ð°ÐºÑÐŸÐ¹ÑÐµ ÐµÐ³ÐŸ - ÐŸÐœ Ð²Ð°ÐŒ Ð±ÐŸÐ»ÑÑÐµ ÐœÐµ Ð¿ÐŸÐœÐ°ÐŽÐŸÐ±ÐžÑÑÑ ÐœÐ° ÐŽÐ°ÐœÐœÐŸÐŒ ÑÑÐ°Ð¿Ðµ ÐŸÐ±ÑÑÐµÐœÐžÑ.</Text>
+<Text id="49">Ð¡Ð»ÐµÐŽÑÑÑÐ°Ñ ÑÐ°Ð·Ð° - "Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÐµ" ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð² ÐºÐŸÑÐŸÑÐŸÐ¹ Ð±ÑÐŽÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÑ Ð²ÑÐµ ÐžÐœÐŽÐµÐºÑÑ Ðž ÑÐ°Ð¹Ð»Ñ, ÐŸÑÐ²ÐµÑÐ°ÑÑÐžÐµ Ð·Ð° ÑÐ°Ð±ÐŸÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐµ perl âS buildcol.pl Ðž Ð¿ÐŸÐ»ÑÑÐžÑÐµ ÑÐ¿ÐžÑÐŸÐº ÐŸÐ¿ÑÐžÐ¹ ÐŽÐ»Ñ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÐŽÑÐŸÐ±ÐœÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÑÑÐžÑ
+ ÐŸÐ¿ÑÐžÐ¹ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐŸ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="import_and_build_processes"/>. ÐÐŸÐºÐ° Ð¶Ðµ Ð¿ÑÐžÐŽÐµÑÐ¶ÐžÐ²Ð°Ð¹ÑÐµÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ "Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ", ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð²:</Text>
+<CodeLine>perl âS buildcol.pl dlpeople</CodeLine>
+<Text id="50">Ð ÑÐœÐŸÐ²Ð° ÐœÐµ Ð±ÐµÑÐ¿ÐŸÐºÐŸÐ¹ÑÐµÑÑ ÐŸ Ð±ÑÑÑÑÐŸ Ð±ÐµÐ³ÑÑÐµÐŒ Ð¿ÐŸ ÑÐºÑÐ°ÐœÑ ÑÐµÐºÑÑÐµ - ÑÑÐŸ ÐŸÑÑÐµÑ ÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐž ÐºÐŸÐŒÐ°ÐœÐŽÑ.</Text>
+<Text id="51">Ð¢ÐµÐ¿ÐµÑÑ "ÐŸÐ¶ÐžÐ²ÐžÐŒ" ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ:</Text>
+<Text id="52">Ð²ÑÐŽÐµÐ»ÐžÑÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ð° building ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž dlpeople Ðž Ð¿ÐµÑÐµÐœÐµÑÐžÑÐµ ÐµÐ³ÐŸ Ð² ÐºÐ°ÑÐ°Ð»ÐŸÐ³ index.</Text>
+<Text id="53">Ð¢Ð°Ðº Ð¶Ðµ Ð²Ð² ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÐŽÐµÐ»Ð°ÑÑ ÑÑÑ ÐŸÐ¿ÐµÑÐ°ÑÐžÑ, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð² ÐºÐŸÐŒÐ°ÐœÐŽÑ:</Text>
+<CodeLine>rd /s index                 # on Windows NT/2000</CodeLine>
+<CodeLine>deltree /Y index       # on Windows 95/98</CodeLine>
+<Text id="54">Ðž ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐžÐŒÑ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ð° building ÐœÐ° index ÐºÐŸÐŒÐ°ÐœÐŽÐŸÐ¹</Text>
+<CodeLine>ren building index</CodeLine>
+<Text id="55">Ð Ð·Ð°ÐºÐ»ÑÑÐµÐœÐžÐµ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ:</Text>
+<CodeLine>mkdir building</CodeLine>
+<Text id="56">Ð¿ÐŸÐŽÐ³ÐŸÑÐŸÐ²ÐžÐ² ÑÐžÑÑÐµÐŒÑ ÐŽÐ»Ñ Ð±ÑÐŽÑÑÐžÑ
+ Ð¿ÐµÑÐµÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐ¹. ÐÐ°Ð¶ÐœÐŸ, ÑÑÐŸÐ±Ñ Ð²ÑÐµ ÑÑÐž ÐºÐŸÐŒÐ°ÐœÐŽÑ Ð±ÑÐ»Ðž Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÑ ÐžÐ· ÑÑÐµÐ±ÑÐµÐŒÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž (Ð² ÐŸÑÐ»ÐžÑÐžÐµ ÐŸÑ ÐºÐŸÐŒÐ°ÐœÐŽ Greenstone mkcol.pl, import.pl and buildcol.pl); ÐµÑÐ»Ðž ÑÐµÐºÑÑÐ°Ñ ÑÐ°Ð±ÐŸÑÐ°Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐœÐµ ÑÐ²Ð»ÑÐµÑÑÑ dlpeople, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ: cd "%GSDLHOME%\collect\dlpeople" ÐŽÐŸ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº Ð²Ñ Ð·Ð°Ð¿ÑÑÑÐžÑÐµ ÐœÐ° ÐžÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ ÐºÐŸÐŒÐ°ÐœÐŽÑ rd, ren Ðž mkdir.</Text>
+<Text id="57">ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐŒÐµÑÑ ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑ Ðº Ð²ÐœÐŸÐ²Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ñ Ð²Ð°ÑÐµÐ¹ ÐŽÐŸÐŒÐ°ÑÐœÐµÐ¹ ÑÑÑÐ°ÐœÐžÑÑ Greenstone. ÐÑÐ»Ðž ÑÑÐ° ÑÑÑÐ°ÐœÐžÑÐ° ÐŸÑÐºÑÑÑÐ° Ð² Ð²Ð°ÑÐµÐŒ Ð±ÑÐŸÑÐ·ÐµÑÐµ, Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÐµÐµ ÐŸÐ±ÐœÐŸÐ²ÐžÑÑ ÐžÐ»Ðž Ð·Ð°ÐºÑÑÑÑ ÐŸÐºÐœÐŸ Ð±ÑÐŸÑÐ·ÐµÑÐ° Ðž Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÐžÑÑ ÐµÐ³ÐŸ (ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐžÐ·Ð±ÐµÐ¶Ð°ÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒ ÐºÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ). ÐÑÐ»Ðž Ð²Ñ Ð¿ÐŸÐ»ÑÐ·ÑÐµÑÐµÑÑ "Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ Ð²ÐµÑÑÐžÐµÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž" Greenstone, ÑÐŸ ÐŽÐŸÐ»Ð¶ÐœÑ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÐžÑÑ Ð²ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ. ÐÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐµÐ»ÐºÐœÐžÑÐµ ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ ÐŒÑÑÐž Ð¿ÐŸ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ. ÐÐŸÐ»ÑÑÐµÐœÐœÑÐ¹ ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ²ÐžÐŽÐµÑÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="about_page_for_the_new_collection"/>.</Text>
+<Figure id="collection_icon">
+<Title>
+<Text id="58">ÐÐºÐŸÐœÐºÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<File width="156" height="120" url="images/Dev_Fig_006.png"/>
+</Figure>
+<Text id="59">Ð Ð·Ð°ÐºÐ»ÑÑÐµÐœÐžÐµ Ð¿ÑÐžÐ²ÐµÐŽÐµÐŒ ÐºÐŸÐŒÐ°ÐœÐŽÑ, ÑÐŸÐ·ÐŽÐ°ÑÑÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ:</Text>
+<CodeLine>cd "C:\Program Files\gsdl " # assuming default location</CodeLine>
+<CodeLine>setup.bat</CodeLine>
+<CodeLine>perl âS mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<CodeLine>cd "%GSDLHOME%\collect\dlpeople "</CodeLine>
+<CodeLine>xcopy   /s   d:\collect\dlpeople\*   import # assuming D drive</CodeLine>
+<CodeLine>perl âS import.pl dlpeople</CodeLine>
+<CodeLine>perl âS buildcol.pl dlpeople</CodeLine>
+<CodeLine>rd /s index           # on Windows NT/2000</CodeLine>
+<CodeLine>deltree /Y index # on Windows 95/98</CodeLine>
+<CodeLine>ren building index</CodeLine>
+<CodeLine>mkdir building</CodeLine>
+</Content>
+</Subsection>
+<Subsection id="collection_building_under_unix">
+<Title>
+<Text id="60">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÐŸÐŽ Unix</Text>
+</Title>
+<Content>
+<Text id="61">Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð²ÐœÐŸÑÐžÐŒ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ, Ð² ÐºÐŸÑÐŸÑÑÑ Ð±ÑÐ»Ð° ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÑÐžÑÑÐµÐŒÐ° Greenstone. Ð Ð¿ÑÐžÐŒÐµÑÑ, ÐµÑÐ»Ðž Greenstone Ð±ÑÐ»Ð° ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° Ñ ÐžÐŒÐµÐœÐµÐŒ "Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, ÑÐŸ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÐŸÐ¿Ð°ÑÑÑ, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð²:</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<Text id="62">ÐÐ°ÑÐµÐŒ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÑÑ:</Text>
+<CodeLine>source setup.bash     # if you're running the BASH shell</CodeLine>
+<CodeLine>source setup.csh       # if you're running the C shell</CodeLine>
+<Text id="63">Ð­ÑÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ñ (ÐºÐŸÑÐŸÑÑÐµ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ) ÑÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÑÐžÑÑÐµÐŒÐµ, Ð³ÐŽÐµ ÐžÑÐºÐ°ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Greenstone. ÐÑÐ»Ðž Ð¿ÐŸÐ·Ð¶Ðµ Ð²Ñ Ð·Ð°Ñ
+ÐŸÑÐžÑÐµ Ð²ÐµÑÐœÑÑÑÑÑ ÐœÐ° Ð²ÐµÑÑ
+ÐœÐžÐ¹ ÑÑÐŸÐ²ÐµÐœÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž GreenÂ¬stone, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐµ cd $GSDLHOME.</Text>
+<Text id="64">ÐÑÐ»Ðž Ð²Ñ ÐœÐµ ÑÐ²ÐµÑÐµÐœÑ Ð² ÑÐžÐ¿Ðµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐœÐŸÐ¹ ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÐŸÐ±ÐŸÐ»ÐŸÑÐºÐž, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐµ $0, Ð² ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ ÑÐµÐ³ÐŸ Ð²Ñ Ð¿ÐŸÐ»ÑÑÐžÑÐµ Ð¿ÐŸÐ»ÐœÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ. ÐÑÐ»Ðž Ð¿ÑÐž ÑÐ°Ð±ÐŸÑÐµ Ð²Ñ Ð¿ÐŸÐ»ÑÐ·ÑÐµÑÐµÑÑ ÐžÐœÐŸÐ¹ ÐŸÐ±ÐŸÐ»ÐŸÑÐºÐŸÐ¹, ÑÐŸ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ ÐŸÐ±ÑÐ°ÑÐžÑÑÑÑ Ð·Ð° ÑÐŸÐ²ÐµÑÐŸÐŒ Ðº Ð²Ð°ÑÐµÐŒÑ ÑÐžÑÑÐµÐŒÐœÐŸÐŒÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑÑ.</Text>
+<Text id="65">Ð¢ÐµÐ¿ÐµÑÑ Ð²Ñ ÐžÐŒÐµÐµÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÑÑ ÐžÐ»Ðž Ð¿ÐµÑÐµÑÐŸÑÐŒÐžÑÐŸÐ²ÑÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¡ÐœÐ°ÑÐ°Ð»Ð° ÐŒÑ ÑÐ°ÑÑÐŒÐŸÑÑÐžÐŒ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ mkcol.pl, ÐœÐ°Ð¿ÐžÑÐ°ÐœÐœÑÑ ÐœÐ° Perl, ÐžÐŒÑ ÐºÐŸÑÐŸÑÐŸÐ¹ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ "make a collection" (ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž). ÐÐµÑÐ²ÑÐ¹ Ð·Ð°Ð¿ÑÑÐº ÑÑÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÑÑÐµÑÑÐ²ÐžÑÑ, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð² mkcol.pl, Ð¿ÑÐž ÑÑÐŸÐŒ ÐœÐ°  ÑÐºÑÐ°ÐœÐµ Ð¿ÐŸÑÐ²ÐžÑÑÑ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ Ðž ÑÐ¿ÐžÑÐŸÐº Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ². ÐÐ°Ðº Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐŽÐµÑÑ Ð² Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÐŸÐŒ Ð¿ÑÐžÐŒÐµÑÐµ, ÐµÐŽÐžÐœÑÑÐ²ÐµÐœÐœÑÐ¹ ÐŸÐ±ÑÐ·Ð°ÑÐµÐ»ÑÐœÑÐ¹ Ð°ÑÐ³ÑÐŒÐµÐœÑ - ÑÑÐŸ creator (ÑÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ), ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»Ð·ÑÑÐµÑÑÑ ÐŽÐ»Ñ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ Ð»ÐžÑÐ°, ÑÐŸÑÐŒÐžÑÑÑÑÐµÐ³ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ.</Text>
+<Figure id="about_page_for_the_new_collection">
+<Title>
+<Text id="66">Ð¡ÑÑÐ°ÐœÐžÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž "About" (ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž)</Text>
+</Title>
+<File width="389" height="409" url="images/Dev_Fig_008.png"/>
+</Figure>
+<Text id="67">Ð¢ÐµÐ¿ÐµÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒ ÐºÐŸÐŒÐ°ÐœÐŽÑ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐ°ÑÐ°Ð»ÑÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² Ðž ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹, ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÑ
+ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐŽÐŸÐŒÐ°ÑÐœÐµÐ¹ ÑÑÑÐ°ÐœÐžÑÑ ÑÑÐ°ÑÑÐœÐžÐºÐŸÐ² Ð¿ÑÐŸÐµÐºÑÐ° ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐŠÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone. ÐÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ Ð¿ÑÐžÑÐ²ÐŸÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐŒÑ dlpeople, Ñ Ð¿ÐµÑÐ°ÑÐ°Ñ:</Text>
+<CodeLine>mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<Text id="68">ÐÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, ÐžÐ·ÐŒÐµÐœÐžÑÐµ ÐŒÐŸÐ¹ email Ð°ÐŽÑÐµÑ ÐœÐ° ÑÐ²ÐŸÐ¹ ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÑÐ¹!</Text>
+<Text id="69">ÐÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ð²ÐœÐŸÐ²Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² Ð¿ÐµÑÐµÐ¹ÐŽÐµÐŒ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ»Ñ ÑÑÐŸÐ³ÐŸ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÐµÐŒ:</Text>
+<CodeLine>cd $GSDLHOME/collect/dlpeople</CodeLine>
+<Text id="70">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÑÑÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð² Is. ÐÐŽÐµÑÑ ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð±ÑÑÑ 7 ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹: archives, building, etc, images, import, index Ðž perllib.</Text>
+<Text id="71">Ð¢ÐµÐ¿ÐµÑÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð·Ð°Ð¿ÐŸÐ»ÐœÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒÐž. ÐÑÑÐŸÑÐœÐžÐº ÐŒÐ°ÑÐµÑÐžÐ°Ð»ÐŸÐ² ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž dlpeople ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐœÐ° ÑÑÑÐ°ÐœÐŸÐ²ÐŸÑÐœÐŸÐŒ CD-ROM Greenstone Ð² ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ðµ collect/dlpeople. ÐÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž Ñ CD-ROM Ð¿ÐŸÐŽ Linux Ð²ÑÑÐ°Ð²ÑÑÐµ ÐŽÐžÑÐº Ð² ÑÐžÑÐ°ÑÑÐµÐµ ÑÑÑÑÐŸÐ¹ÑÑÐ²ÐŸ Ðž ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ ÐºÐŸÐŒÐ°ÐœÐŽÑ:</Text>
+<CodeLine>mount /cdrom</CodeLine>
+<Text id="72">(ÑÑÐ° ÐºÐŸÐŒÐ°ÐœÐŽÐ° ÐŒÐŸÐ¶ÐµÑ ÐŸÑÐ»ÐžÑÐ°ÑÑÑÑ ÐŸÑ ÑÐžÑÑÐµÐŒÑ Ðº ÑÐžÑÑÐµÐŒÐµ). ÐÐŸÑÐ»Ðµ ÑÑÑÐ°ÐœÐŸÐºÐž CD-ROM ÐŒÐŸÐ¶ÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ, ÐºÐ°Ðº Ð»ÑÐ±Ð°Ñ ÐŽÑÑÐ³Ð°Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ, Ðž ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð² Is /cdrom/collect, ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Ñ ÐžÐŒÐµÐœÐµÐŒ dlpeople ÐœÐ° CD-ROM.</Text>
+<Text id="73">ÐÐ°ÑÐµÐŒ ÑÐºÐŸÐ¿ÐžÑÑÐ¹ÑÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž /cdrom/collect/dlpeople  Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ $GSDLHOME/collect/dlpeople/import. ÐÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÑÐŽÐµÐ»Ð°ÑÑ ÑÑÐŸ, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ ÐºÐŸÐŒÐ°ÐœÐŽÑ:</Text>
+<CodeLine>cp âr /cdrom/collect/dlpeople/*   import/</CodeLine>
+<Text id="74">ÐÐ°ÑÐµÐŒ ÐœÐ°Ð±ÐµÑÐžÑÐµ:</Text>
+<CodeLine>umount /cdrom</CodeLine>
+<Text id="75">ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ Ð·Ð°ÐºÑÑÑÑ CD-ROM ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ</Text>
+<Text id="76">Ð ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž etc ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÑÐ°Ð¹Ð» collect.ucfg. ÐÑÐºÑÐŸÐ¹ÑÐµ ÐµÐ³ÐŸ, Ð²ÐŸÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ð²ÑÐžÑÑ Ð»ÑÐ±ÑÐŒ ÑÐµÐºÑÑÐŸÐ²ÑÐŒ ÑÐµÐŽÐ°ÐºÑÐŸÑÐŸÐŒ ÐžÐ»Ðž ÐœÐ°ÐžÐ±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐ¿ÑÐ»ÑÑÐœÑÐŒ Ð² Linux ÑÐµÐºÑÑÐŸÐ²ÑÐŒ ÑÐµÐŽÐ°ÐºÑÐŸÑÐŸÐŒ - emacs. Ð ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ Ð²Ñ ÑÐ²ÐžÐŽÐžÑÐµ ÐŸÐºÐœÐŸ, ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ Ð²ÑÐ³Ð»ÑÐŽÐžÑ, ÐºÐ°Ðº ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="collection_configuration_file_created_by_mkcol"/>, Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°Ñ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ³ÐŸ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÐºÐŸÐŒÐ°ÐœÐŽÑ mkcol.pl -creator me@cs.waikato.ac.nz dlpeople.</Text>
+<Text id="77">Ð¢ÐµÐ¿ÐµÑÑ Ð²Ñ Ð³ÐŸÑÐŸÐ²Ñ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. Ð­ÑÐŸ Ð¿ÑÐŸÑÐµÑÑ Ð¿ÐµÑÐµÐœÐŸÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÑÐžÑÑÐµÐŒÑ Greenstone, ÑÑÐ°ÐœÐŽÐ°ÑÑÐžÐ·Ð°ÑÐžÐž ÑÐŸÑÐŒÐ°ÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð¿ÑÑÐž ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÑÑÑÑÐºÑÑÑÑ ÑÐ°Ð¹Ð»Ð°, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ Ð±ÑÐŽÑÑ Ñ
+ÑÐ°ÐœÐžÑÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ. ÐÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ ÐºÐŸÐŒÐ°ÐœÐŽÑ import.pl Ðž Ð¿ÐŸÐ»ÑÑÐžÑÐµ Ð¿ÐŸÐ»ÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº ÐŸÐ¿ÑÐžÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐžÐŒÐ¿ÐŸÑÑÐ°. ÐÐ»Ñ ÑÐ¿ÑÐŸÑÐµÐœÐžÑ Ð¿ÑÐŸÑÐµÐŽÑÑÑ Ð²ÐŸÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµÑÑ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ¹ ÐºÐŸÐŒÐ°ÐœÐŽÐŸÐ¹</Text>
+<CodeLine>import.pl   dlpeople</CodeLine>
+<Text id="78">ÐÐµ Ð±ÐµÑÐ¿ÐŸÐºÐŸÐ¹ÑÐµÑÑ Ð¿ÐŸ Ð¿ÐŸÐ²ÐŸÐŽÑ Ð±ÑÑÑÑÐŸ Ð±ÐµÐ³ÑÑÐµÐ³ÐŸ Ð¿ÐŸ ÑÐºÑÐ°ÐœÑ ÑÐµÐºÑÑÐ° - ÑÑÐŸ ÐŸÑÑÐµÑ ÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐž Ð¿ÑÐŸÑÐµÐŽÑÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ°. Ð ÑÐ²ÐµÐŽÐµÐœÐžÑ, Ð¿ÑÐŸÑÐµÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ° ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð·Ð°ÐœÐžÐŒÐ°ÐµÑ ÐŸÐºÐŸÐ»ÐŸ 5 ÐŒÐžÐœÑÑ ÐœÐ° 1 ÐÐÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ Ðž ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐ»ÑÑÐµ ÐœÐ° Ð±ÐŸÐ»ÐµÐµ ÐŒÐµÐŽÐ»ÐµÐœÐœÑÑ
+ ÐŒÐ°ÑÐžÐœÐ°Ñ
+. ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÑÐŸ, ÑÑÐŸ Ð²Ñ ÐœÐµ ÐŽÐŸÐ»Ð¶ÐœÑ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑÑ
+ collect ÐžÐ»Ðž dlpeople Ð¿ÑÐž Ð·Ð°Ð¿ÑÑÐºÐµ ÑÑÐŸÐ¹ ÐºÐŸÐŒÐ°ÐœÐŽÑ, Ñ.Ðº. GSDLHOME ÑÐ¶Ðµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÐ» ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ Greenstone ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ².</Text>
+<Text id="79">Ð¢ÐµÐ¿ÐµÑÑ ÐŽÐ°Ð²Ð°Ð¹ÑÐµ Ð²ÐœÐµÑÐµÐŒ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð² ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐ»Ñ ÐŒÐŸÐŽÐžÑÐžÐºÐ°ÑÐžÐž ÐµÐµ Ð²ÐžÐŽÐ°. Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð¿ÑÐžÑÐ²ÐŸÐžÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐŒÑ. ÐÐœÐŸ Ð±ÑÐŽÐµÑ Ð²ÐŸÑÐ¿ÑÐžÐœÑÑÐŸ Ð²ÐµÐ±-Ð±ÑÐŸÑÐ·ÐµÑÐŸÐŒ ÐºÐ°Ðº Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐŽÐ»Ñ ÑÐžÑÑÐ»ÑÐœÐŸÐ³ÐŸ Ð»ÐžÑÑÐ° WWW-ÑÑÑÐ°ÐœÐžÑÑ, Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐžÐºÐŸÐœÐºÐž Ð¿ÑÐž ÐŸÑÑÑÑÑÑÐ²ÐžÐž ÑÐžÑÑÐœÐºÐ°. ÐÐ·ÐŒÐµÐœÐžÐŒ ÑÑÑÐŸÐºÑ collectionmeta collectionname "dlpeople" ÐœÐ° ÑÑÑÐŸÐºÑ Ð²ÐžÐŽÐ°: collectionmeta collectionname "The People of the NZDL project".</Text>
+<Text id="80">ÐÐŸÐ±Ð°Ð²ÐžÐŒ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐµÐ¶ÐŽÑ ÐºÐ°Ð²ÑÑÐºÐ°ÐŒÐž: <i>collectionmeta collectionextra ""</i>. ÐÐœÐŸ Ð±ÑÐŽÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐŸ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ð° ÐŽÐ»Ñ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÑÐ°Ð·ÐŽÐµÐ»Ð° "About" (ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž) ÐœÐ° ÐŽÐŸÐŒÐ°ÑÐœÐµÐ¹ WWW-ÑÑÑÐ°ÐœÐžÑÐµ. Ð¯ ÐŽÐŸÐ±Ð°Ð²ÐžÐ» "This collection is made up of the homepages of some of the people who have worked on the NZDL project." ÐÐ°Ð¶ÐœÐŸ Ð²Ð²ÐŸÐŽÐžÑÑ ÑÑÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐŸÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐŸÐ¹ - ÐœÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐŽÐ»Ñ ÐŸÑÐ±ÐžÐ²ÐºÐž ÐºÐ»Ð°Ð²ÐžÑÑ Enter/ÐÐ²ÐŸÐŽ. ÐÑÐ»Ðž Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð² Ð²Ð°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐœÐŸÐ³ÐŸÑÐ·ÑÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ, ÑÐŸ ÑÑÑÐµÑÑÐ²ÑÐµÑ ÑÐ¿ÐŸÑÐŸÐ± Ð²ÑÐ²ÐŸÐŽÐ° ÐŽÐ°ÐœÐœÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ° Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ Ð²ÑÐ±ÑÐ°ÐœÐœÑÐŒ ÑÐ·ÑÐºÐŸÐŒ. Ð­ÑÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ Ð±ÑÐŽÐµÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐŸ ÐŽÐ°Ð»ÐµÐµ Ð² ÑÐ°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="configuration_file"/>.</Text>
+<Text id="81">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐŽÑÑ ÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐžÐºÐŸÐœÐŸÐº ÐœÐ° WWW-ÑÑÑÐ°ÐœÐžÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ, ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐµ ÐŒÐœÐŸÑ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐŽÐµÑÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="collection_icon"/>. Ð£ÐºÐ°Ð¶ÐžÑÐµ Ð¿ÑÑÑ ÐœÐ°Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ Ð² ÐºÐ°Ð²ÑÑÐºÐ°Ñ
+ Ð² ÑÑÑÐŸÐºÐµ collectionmeta iconcollection "" ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž. ÐÐ»Ñ ÐºÑÐ°ÑÐºÐŸÑÑÐž Ðž ÐŒÐŸÐ±ÐžÐ»ÑÐœÐŸÑÑÐž _httpprefix_ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ðœ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÑÐ°ÑÑÐŸÐ²ÐŸÐ³ÐŸ URL, ÑÐºÐ°Ð·ÑÐ²Ð°ÑÑÐµÐ³ÐŸ ÐœÐ° ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐµÐµÑÑ Ð² ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ¹ ÐŸÐ±Ð»Ð°ÑÑÐž Greenstone. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²Ð²ÐµÑÑÐž: httpprefix_/collect/dlpeople/images/icon.gif ÐµÑÐ»Ðž Ð²Ñ Ð¿ÐŸÐŒÐµÑÑÐžÐ»Ðž Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÐµÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (Ð² ÐœÐ°ÑÐµÐŒ Ð¿ÑÐžÐŒÐµÑÐµ ÑÑÐŸ: collect\dlpeople\images ).</Text>
+<Text id="82">Ð¡ÐŸÑ
+ÑÐ°ÐœÐžÑÐµ ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð·Ð°ÐºÑÐŸÐ¹ÑÐµ ÐµÐ³ÐŸ - ÐŸÐœ Ð²Ð°ÐŒ Ð±ÐŸÐ»ÑÑÐµ ÐœÐµ Ð¿ÐŸÐœÐ°ÐŽÐŸÐ±ÐžÑÑÑ ÐœÐ° ÐŽÐ°ÐœÐœÐŸÐŒ ÑÑÐ°Ð¿Ðµ ÐŸÐ±ÑÑÐµÐœÐžÑ.</Text>
+<Text id="83">Ð¡Ð»ÐµÐŽÑÑÑÐ°Ñ ÑÐ°Ð·Ð° - "Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÐµ" ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð² ÐºÐŸÑÐŸÑÐŸÐ¹ Ð±ÑÐŽÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÑ Ð²ÑÐµ ÐžÐœÐŽÐµÐºÑÑ Ðž ÑÐ°Ð¹Ð»Ñ, ÐŸÑÐ²ÐµÑÐ°ÑÑÐžÐµ Ð·Ð° ÑÐ°Ð±ÐŸÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐµ buildcol.pl Ðž Ð¿ÐŸÐ»ÑÑÐžÑÐµ ÑÐ¿ÐžÑÐŸÐº ÐŸÐ¿ÑÐžÐ¹ ÐŽÐ»Ñ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÐŽÑÐŸÐ±ÐœÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÑÑÐžÑ
+ ÐŸÐ¿ÑÐžÐ¹ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐŸ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="import_and_build_processes"/>. ÐÐŸÐºÐ° Ð¶Ðµ Ð¿ÑÐžÐŽÐµÑÐ¶ÐžÐ²Ð°Ð¹ÑÐµÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ "Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ", ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð²:</Text>
+<CodeLine>buildcol.pl dlpeople</CodeLine>
+<Text id="84">Ð ÑÐœÐŸÐ²Ð° ÐœÐµ Ð±ÐµÑÐ¿ÐŸÐºÐŸÐ¹ÑÐµÑÑ ÐŸ Ð±ÑÑÑÑÐŸ Ð±ÐµÐ³ÑÑÐµÐŒ Ð¿ÐŸ ÑÐºÑÐ°ÐœÑ ÑÐµÐºÑÑÐµ - ÑÑÐŸ ÐŸÑÑÐµÑ ÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐž ÐºÐŸÐŒÐ°ÐœÐŽÑ.</Text>
+<Text id="85">Ð¡ÐŽÐµÐ»Ð°Ð¹ÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ "ÐŸÐ¿ÐµÑÐ°ÑÐžÐ²ÐœÐŸÐ¹", ÐºÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ñ Ð¿ÐŸÐŒÐµÑÐµÐœÑ Ð² ÐºÐ°ÑÐ°Ð»ÐŸÐ³ building, Ð¿ÐµÑÐµÑÐ»ÐžÑÐµ ÐžÑ
+ Ð² ÐºÐ°ÑÐ°Ð»ÐŸÐ³ index. ÐÑÐ»Ðž Ñ Ð²Ð°Ñ Ð¿ÑÐµÐ¶ÐŽÐµ Ð±ÑÐ»Ð° ÑÐ¶Ðµ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÑÐœÐ°ÑÐ°Ð»Ð° ÑÐŽÐ°Ð»ÐžÑÐµ ÑÑÐ°ÑÑÐµ ÐžÐœÐŽÐµÑÑ, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð² Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐµ:</Text>
+<CodeLine>rm âr index/*</CodeLine>
+<Text id="86">(Ð¿ÑÐµÐŽÐ¿ÐŸÐ»Ð°Ð³Ð°ÐµÑÑÑ, ÑÑÐŸ Ð²Ñ ÑÐ°Ð±ÐŸÑÐ°ÐµÑÐµ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž dlpeople). ÐÐ°ÑÐµÐŒ Ð²Ð²ÐµÐŽÐžÑÐµ:</Text>
+<CodeLine>mv building/* index/</CodeLine>
+<Table id="collection-building_differences_between_windows_and_linux">
+<Title>
+<Text id="87">Ð Ð°Ð·Ð»ÐžÑÐžÑ Ð² Ð¿ÑÐŸÑÐµÑÑÐ°Ñ
+ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐŽÐ»Ñ Windows Ðž Linux Windows</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="265">
+<Text id="88"><b>Windows</b></Text>
+</th>
+<th width="265">
+<Text id="89"><b>Linux</b></Text>
+</th>
+</tr>
+<tr>
+<th width="265">
+<Text id="90">Linux ÐÐ°Ð¿ÑÑÑÐžÑÐµ setup, bat, ÑÑÐŸÐ±Ñ ÑÐŽÐµÐ»Ð°ÑÑ  Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Greenstone ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž</Text>
+</th>
+<th width="265">
+<Text id="91">ÐÐ°Ð¿ÑÑÑÐžÑÐµ setup, bat, ÑÑÐŸÐ±Ñ ÑÐŽÐµÐ»Ð°ÑÑ                                       ÐÐ°Ð¿ÑÑÑÐžÑÐµ setup, bash ÐžÐ»Ðž setup, csh, ÑÑÐŸÐ±Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Greenstone ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="265">
+<Text id="92">Ð¡ÐºÐŸÐ¿ÐžÑÑÐ¹ÑÐµ ÑÐ°Ð¹Ð»Ñ Ñ CD-ROM, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŒÐµÐœÐµÐŽÐ¶ÐµÑ ÑÐ°Ð¹Ð»ÐŸÐ² ÐžÐ»Ðž Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐºÐŸÐŒÐ°ÐœÐŽ Windows</Text>
+</th>
+<th width="265">
+<Text id="93">Ð¡ÐºÐŸÐ¿ÐžÑÑÐ¹ÑÐµ ÑÐ°Ð¹Ð»Ñ Ñ CD-ROM, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ mount Ðž ÐºÐŸÐŒÐ°ÐœÐŽÑ Unix</Text>
+</th>
+</tr>
+<tr>
+<th width="265">
+<Text id="94">ÐÐ°ÐŒÐµÐœÐžÑÐµ ÐžÐœÐŽÐµÐºÑÑ ÑÑÐ°ÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð² rd /s index, Ð¿ÐŸÑÐŸÐŒ ren building index Ð·Ð°ÑÐµÐŒ mkdir building, ÐžÐ»Ðž Ð²ÐŸÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµÑÑ ÐŒÐµÐœÐµÐŽÐ¶ÐµÑÐŸÐŒ ÑÐ°Ð¹Ð»ÐŸÐ²</Text>
+</th>
+<th width="265">
+<Text id="95">ÐÐ°ÐŒÐµÐœÐžÑÐµ ÐžÐœÐŽÐµÐºÑÑ ÑÑÐ°ÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð² rm âr index/* , Ð° Ð·Ð°ÑÐµÐŒ mv building/* index</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="96">ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐŒÐµÑÑ ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑ Ðº Ð²ÐœÐŸÐ²Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ñ Ð²Ð°ÑÐµÐ¹ ÐŽÐŸÐŒÐ°ÑÐœÐµÐ¹ ÑÑÑÐ°ÐœÐžÑÑ Greenstone. ÐÑÐ»Ðž ÑÑÐ° ÑÑÑÐ°ÐœÐžÑÐ° ÐŸÑÐºÑÑÑÐ° Ð² Ð²Ð°ÑÐµÐŒ Ð±ÑÐŸÑÐ·ÐµÑÐµ, Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÐµÐµ ÐŸÐ±ÐœÐŸÐ²ÐžÑÑ ÐžÐ»Ðž Ð·Ð°ÐºÑÑÑÑ ÐŸÐºÐœÐŸ Ð±ÑÐŸÑÐ·ÐµÑÐ° Ðž Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÐžÑÑ ÐµÐ³ÐŸ (ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐžÐ·Ð±ÐµÐ¶Ð°ÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒ ÐºÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ). ÐÑÐ»Ðž Ð²Ñ Ð¿ÐŸÐ»ÑÐ·ÑÐµÑÐµÑÑ "Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ Ð²ÐµÑÑÐžÐµÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž" Greenstone, ÑÐŸ ÐŽÐŸÐ»Ð¶ÐœÑ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÐžÑÑ Ð²ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ. ÐÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐµÐ»ÐºÐœÐžÑÐµ ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ ÐŒÑÑÐž Ð¿ÐŸ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ. ÐÐŸÐ»ÑÑÐµÐœÐœÑÐ¹ ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ²ÐžÐŽÐµÑÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="about_page_for_the_new_collection"/>.</Text>
+<Text id="97">Ð Ð² Ð·Ð°ÐºÐ»ÑÑÐµÐœÐžÐµ Ð¿ÑÐžÐ²ÐµÐŽÐµÐŒ ÑÐ°ÑÐ¿ÐµÑÐ°ÑÐºÑ ÐºÐŸÐŒÐ°ÐœÐŽ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž dlpeople:</Text>
+<CodeLine>cd ~/gsdl # assuming default Greenstone in home directory</CodeLine>
+<CodeLine>source setup.bash     # if you're running the BASH shell</CodeLine>
+<CodeLine>source setup.csh       # if you're running the C shell</CodeLine>
+<CodeLine>mkcol.pl âcreator me@cs.waikato.ac.nz dlpeople</CodeLine>
+<CodeLine>cd $GSDLHOME/collect/dlpeople</CodeLine>
+<CodeLine>mount /cdrom # assuming this is where CD-ROM is mapped to</CodeLine>
+<CodeLine>cp âr /cdrom/collect/dlpeople/* import/</CodeLine>
+<CodeLine>umount /cdrom</CodeLine>
+<CodeLine>import.pl dlpeople</CodeLine>
+<CodeLine>buildcol.pl dlpeople</CodeLine>
+<CodeLine>rm -r index/*</CodeLine>
+<CodeLine>mv building/* index</CodeLine>
+</Content>
+</Subsection>
+<Subsection id="differences_between_windows_and_unix">
+<Title>
+<Text id="98">Ð Ð°Ð·Ð»ÐžÑÐžÑ ÐŒÐµÐ¶ÐŽÑ Windows Ðž Unix</Text>
+</Title>
+<Content>
+<Text id="99">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð² ÑÑÐµÐŽÐµ Unix Ðž ÑÑÐµÐŽÐµ Windows ÐŸÑÐµÐœÑ Ð¿ÐŸÑ
+ÐŸÐ¶Ðž, Ð·Ð° ÐžÑÐºÐ»ÑÑÐµÐœÐžÐµÐŒ ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÐœÐµÐ±ÐŸÐ»ÑÑÐžÑ
+ ÑÐ°ÑÑ
+ÐŸÐ¶ÐŽÐµÐœÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÑÐ²ÐµÐŽÐµÐœÑ Ð² Ð¢Ð°Ð±Ð»ÐžÑÑ <CrossRef target="Table" ref="collection-building_differences_between_windows_and_linux"/>.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="greenstone_directories">
+<Title>
+<Text id="100">ÐÐžÑÐµÐºÑÐŸÑÐžÐž Greenstone</Text>
+</Title>
+<Content>
+<Text id="101">ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="structure_of_the_gsdlhome_directory"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐ° ÑÑÑÑÐºÑÑÑÐ° ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹ GSDLHOME. Ð Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="where_to_find_information_about_directories"/> ÐŽÐ°ÐœÐŸ ÐºÑÐ°ÑÐºÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÐŸÐ¹ ÐœÐ° ÐŽÐžÐ°Ð³ÑÐ°ÐŒÐŒÐµ. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Ð±ÑÐŽÑÑ Ð±ÐŸÐ»ÐµÐµ ÐŽÐµÑÐ°Ð»ÑÐœÐŸ ÑÐ°ÑÑÐŒÐŸÑÑÐµÐœÑ Ð² Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐžÑ
+ ÑÐ°Ð·ÐŽÐµÐ»Ð°Ñ
+ ÐœÐ°ÑÑÐŸÑÑÐµÐ³ÐŸ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° - ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð°Ñ
+ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐ° Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="where_to_find_information_about_directories"/>.</Text>
+<Figure id="structure_of_the_gsdlhome_directory">
+<Title>
+<Text id="102">Ð¡ÑÑÑÐºÑÑÐ° ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž GSDLHOME</Text>
+</Title>
+<File width="415" height="143" url="images/Dev_Fig_010.png"/>
+</Figure>
+<Table id="where_to_find_information_about_directories">
+<Title>
+<Text id="103">Ð¡ÑÑÑÐºÑÑÑÐ° ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="331">
+<Text id="104">ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ</Text>
+</th>
+<th width="66">
+<Text id="105">ÑÐ°Ð·ÐŽÐµÐ»</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="106"><i>bin</i></Text>
+</th>
+<th width="331">
+<Text id="107">ÐÑÐ¿ÐŸÐ»ÐœÑÐµÐŒÑÐ¹ ÐŽÐ²ÐŸÐžÑÐœÑÐ¹ ÐºÐŸÐŽ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Ñ ÐžÐŒÐµÐœÐµÐŒ Ð²Ð°ÑÐµÐ¹ ÐÐ¡.</Text>
+</th>
+<th width="66">
+<Text id="108">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="109"><i>bin/script</i></Text>
+</th>
+<th width="331">
+<Text id="110">Ð¡ÐºÑÐžÐ¿ÑÑ ÑÐ·ÑÐºÐ° Perl, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž Ð²ÐµÐŽÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, import.pl and buildcol.pl). ÐÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÑÑÐžÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ ÐžÑ
+ ÐžÐŒÑ Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐµ.</Text>
+</th>
+<th width="66">
+<Text id="111">1.3</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="112"><i>perllib</i></Text>
+</th>
+<th width="331">
+<Text id="113">ÐÐŸÐŽÑÐ»Ñ ÑÐ·ÑÐºÐ° Perl, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž ÐžÐŒÐ¿ÐŸÑÑÐ°.</Text>
+</th>
+<th width="66">
+<Text id="114">2.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="115"><i>perllib/plugins</i></Text>
+</th>
+<th width="331">
+<Text id="116">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐ° ÑÐ·ÑÐºÐµ Perl - Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐŽÐ»Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+</th>
+<th width="66">
+<Text id="117">2.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="118"><i>perllib/classify</i></Text>
+</th>
+<th width="331">
+<Text id="119">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° - ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ ÐœÐ° ÑÐ·ÑÐºÐµ Perl (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐºÐŸÐŽ AZList, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐ·ÐŽÐ°ÐµÑ ÑÐ¿ÐžÑÐŸÐº ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² Ð°Ð»ÑÐ°Ð²ÐžÑÐœÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ Ð¿ÐŸ ÐœÐµÐºÐŸÑÐŸÑÐŸÐŒÑ Ð°ÑÑÐžÐ±ÑÑÑ).</Text>
+</th>
+<th width="66">
+<Text id="120">2.2</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="121"><i>cgi-bin</i></Text>
+</th>
+<th width="331">
+<Text id="122">ÐÑÐµ CGI -ÑÐºÑÐžÐ¿ÑÑ ÑÐžÑÑÐµÐŒÑ Greenstone, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐŒÐµÑÐµÐœÑ Ð² cgi-bin ÐºÐ°ÑÐ°Ð»ÐŸÐ³.</Text>
+</th>
+<th width="66">
+<Text id="123">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="124"><i>tmp</i></Text>
+</th>
+<th width="331">
+<Text id="125">ÐÐžÑÐµÐºÑÐŸÑÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ Greenstone ÐŽÐ»Ñ Ð²ÑÐµÐŒÐµÐœÐœÐŸÐ³ÐŸ Ñ
+ÑÐ°ÐœÐµÐœÐžÑ ÑÐ°Ð¹Ð»ÐŸÐ².</Text>
+</th>
+<th width="66">
+<Text id="126">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="127"><i>etc</i></Text>
+</th>
+<th width="331">
+<Text id="128">Ð€Ð°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐ¹, ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž Ðž ÐŸÑÑÐµÑÐ° ÐŸÐ± ÐŸÑÐžÐ±ÐºÐ°Ñ
+, Ð±Ð°Ð·Ð° Ð°Ð²ÑÐŸÑÐžÐ·Ð°ÑÐžÐž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹.</Text>
+</th>
+<th width="66">
+<Text id="129">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="130"><i>src</i></Text>
+</th>
+<th width="331">
+<Text id="131">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐ° C++, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐœÐžÑ
+ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÑÐµÑÐµÐ·   web-ÑÐµÑÐ²ÐµÑ.</Text>
+</th>
+<th width="66">
+<Text id="132">3</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="133"><i>src/colservr</i></Text>
+</th>
+<th width="331">
+<Text id="134">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐ° C++, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž âÐŸÑÐ²ÐµÑÑ ÐœÐ° Ð·Ð°Ð¿ÑÐŸÑÑ Ðž Ñ.Ð¿.</Text>
+</th>
+<th width="66">
+<Text id="135"><CrossRef target="Section" ref="protocol"/></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="136"><i>src/recpt</i></Text>
+</th>
+<th width="331">
+<Text id="137">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐ° C++, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ð¿ÐµÑÐµÐŽÐ°ÑÐž Ð·Ð°Ð¿ÑÐŸÑÐ° ÑÐµÑÐµÐ· ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ðž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŸÑÐ²ÐµÑÐ° ÐœÐ° Ð·Ð°Ð¿ÑÐŸÑ.</Text>
+</th>
+<th width="66">
+<Text id="138">3.9</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="139"><i>packages</i></Text>
+</th>
+<th width="331">
+<Text id="140">ÐÐ°ÐºÐµÑ ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ, ÐœÐµ Ð²Ñ
+ÐŸÐŽÑÑÐžÑ
+ Ð² ÑÐŸÑÑÐ°Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ Greenstone, ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ ÐžÐŒ </Text>
+</th>
+<th width="66">
+<Text id="141">2.5</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="142"><i>packages/mg</i></Text>
+</th>
+<th width="331">
+<Text id="143">ÐÑÑ
+ÐŸÐŽÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° MG, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Greenstone ÐŽÐ»Ñ ÑÐ¶Ð°ÑÐžÑ Ðž ÐžÐœÐŽÐµÐºÑÐ°ÑÐžÐž.</Text>
+</th>
+<th width="66">
+<Text id="144">2.5</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="145"><i>mappings</i></Text>
+</th>
+<th width="331">
+<Text id="146">ÐŸÐ²Ð°ÐœÐžÑ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² Unicode (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŽÐ»Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐºÐžÑÐ°Ð¹ÑÐºÐŸÐ¹ ÑÐ°ÑÐºÐ»Ð°ÐŽÐºÐž ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ²).</Text>
+</th>
+<th width="66">
+<Text id="147">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="148"><i>macros</i></Text>
+</th>
+<th width="331">
+<Text id="149">ÐÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ñ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°.</Text>
+</th>
+<th width="66">
+<Text id="150">2.4</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="151"><i>collect</i></Text>
+</th>
+<th width="331">
+<Text id="152">Collections being served from this copy of Greenstone</Text>
+</th>
+<th width="66">
+<Text id="153">1.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="154"><i>lib</i></Text>
+</th>
+<th width="331">
+<Text id="155">ÐžÑÑ
+ÐŸÐŽÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐ° C++, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ ÐºÐ°Ðº ÑÐµÑÐ²ÐµÑÐŸÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐ°Ðº Ðž ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐŸÐŒ</Text>
+</th>
+<th width="66">
+<Text id="156">3.1</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="157"><i>images</i></Text>
+</th>
+<th width="331">
+<Text id="158">ÐÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°.</Text>
+</th>
+<th width="66">
+<Text id="159">â</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="160"><i>docs</i></Text>
+</th>
+<th width="331">
+<Text id="161">ÐÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÑ</Text>
+</th>
+<th width="66">
+<Text id="162">â</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Section>
+<Section id="import_and_build_processes">
+<Title>
+<Text id="163">ÐÑÐŸÑÐµÑÑÑ import Ðž build</Text>
+</Title>
+<Content>
+<Text id="164">ÐÑÐž ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐµÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹ ÐžÐ· ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ Ð»ÐžÐœÐžÐž (ÑÐŒ. Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Section" ref="building_collections_from_the_command_line"/>) Ð±ÑÐ»Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÑ ÐºÐŸÐŒÐ°ÐœÐŽÑ import.pl ÐŽÐ»Ñ ÐžÐŒÐ¿ÐŸÑÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ðž buildcol.pl ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŽÐµÑÑ ÐŒÑ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐµÐµ ÑÐ°ÑÑÐŒÐŸÑÑÐžÐŒ, ÑÑÐŸ ÐŽÐµÐ»Ð°ÑÑ ÑÐ°ÐŒÐž ÑÑÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ðž ÐŸÐ¿ÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ ÐžÑ
+ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑ. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÑ col_name ÐŽÐ»Ñ ÐŸÐ±ÑÐ°ÑÐµÐœÐžÑ Ðº Ð²ÐœÐŸÐ²Ñ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐ¹ ÐžÐ»Ðž ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="165">ÐÑÐŸÑÐµÑÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ° Ðž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð²ÐŸ ÐŒÐœÐŸÐ³ÐŸÐŒ ÑÑ
+ÐŸÐ¶Ðž, Ð² ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ ÑÐµÐ³ÐŸ ÐžÐŒÐµÑÑ ÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÑÐžÑ
+ ÐŸÐ¿ÑÐžÐ¹, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÑ
+ Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/>. (ÐÐŸÐŒÐœÐžÑÐµ, ÑÑÐŸ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ ÑÐ²ÐžÐŽÐµÑÑ ÐŸÐ¿ÑÐžÐž ÐŽÐ»Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐºÑÐžÐ¿ÑÐŸÐ² Greenstone, ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ ÐœÐ°Ð±ÑÐ°ÑÑ Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐµ ÐµÐ³ÐŸ ÐžÐŒÑ Ð±ÐµÐ· ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÑ ÐŸÐ¿ÑÐžÐ¹).</Text>
+<Table id="options_for_the_import_and_build_processes">
+<Title>
+<Text id="166">ÐÐ¿ÑÐžÐž ÐŽÐ»Ñ Ð¿ÑÐŸÑÐµÑÑÐŸÐ² import Ðž build</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="104">
+<Text id="167"><b>ÐÑÐ³ÑÐŒÐµÐœÑ</b></Text>
+</th>
+<th width="293">
+<Text id="168"><b>Ð€ÑÐœÐºÑÐžÑ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="169"><i>-verbosity</i></Text>
+</th>
+<th width="104">
+<Text id="170">Ð§ÐžÑÐ»ÐŸ 0-3</Text>
+</th>
+<th width="293">
+<Text id="171">ÐÐŸÐœÑÑÐŸÐ»Ñ Ð·Ð° ÑÐµÐŒ, ÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐ°ÐœÐœÑÑ
+ ÐŸ Ð¿ÑÐŸÑÐµÑÑÐµ Ð·ÐœÐ°ÑÐžÑÑÑ ÐºÐ°Ðº ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ ÐŸÑÐžÐ±ÐºÐ°; 0 - ÐŒÐ°Ð»ÐŸ, 3 - ÐŒÐœÐŸÐ³ÐŸ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="172"><i>-archivedir</i></Text>
+</th>
+<th width="104">
+<Text id="173">ÐÐŒÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž</Text>
+</th>
+<th width="293">
+<Text id="174">Ð£ÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÐŒÐµÑÑÐŸ Ñ
+ÑÐ°ÐœÐµÐœÐžÑ Ð°ÑÑ
+ÐžÐ²ÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² Greenstone, ÐœÐ° ÑÐŸ, ÐºÑÐŽÐ° import.pl ÐŒÐŸÐ¶ÐµÑ ÐžÑ
+ Ð¿ÐŸÐŒÐµÑÑÐžÑÑ Ðž Ð³ÐŽÐµ buildcol.pl ÐŒÐŸÐ¶ÐµÑ ÐžÑ
+ ÐœÐ°Ð¹ÑÐž. ÐÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ GSDLHOME/collect/col name/archives</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="175"><i>-maxdocs</i></Text>
+</th>
+<th width="104">
+<Text id="176">Ð§ÐžÑÐ»ÐŸ &gt;0</Text>
+</th>
+<th width="293">
+<Text id="177">ÐÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐŒÐ°ÐºÑÐžÐŒÐ°Ð»ÑÐœÐŸÐµ ÑÐžÑÐ»ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÐœÐœÑÑ
+ ÐŸÐ¿ÑÐžÑÐŒÐž import ÐžÐ»Ðž built. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÑÐµÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐ»Ðž ÐœÐŸÐ²ÑÑ
+ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="178"><i>-collectdir</i></Text>
+</th>
+<th width="104">
+<Text id="179">ÐÐŒÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž</Text>
+</th>
+<th width="293">
+<Text id="180">Ð£ÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÐŒÐµÑÑÐŸ ÐœÐ°Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ GSDLHOME/collect</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="181"><i>-out</i></Text>
+</th>
+<th width="104">
+<Text id="182">ÐÐŒÑ ÑÐ°Ð¹Ð»Ð°</Text>
+</th>
+<th width="293">
+<Text id="183">Ð£ÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÑÐ°Ð¹Ð», Ð² ÐºÐŸÑÐŸÑÐŸÐŒ Ð·Ð°Ð¿ÐžÑÑÐ²Ð°ÑÑÑÑ Ð²ÑÐµ ÐžÑÑ
+ÐŸÐŽÑÑÐžÐµ ÑÐŸÐŸÐ±ÑÐµÐœÐžÑ, ÐŸÐ±ÑÑÐœÐŸ ÐŽÐ»Ñ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ
+ ÐŸÑÐžÐ±ÐŸÐº. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² ÑÐ°Ð±ÐŸÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹ ÐŸÑÐ»Ð°ÐŽÐºÐž ÐœÐ°Ð¹ÐŽÐµÐœÐœÑÑ
+ ÐŸÑÐžÐ±ÐŸÐº.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="184"><i>-keepold</i></Text>
+</th>
+<th width="104">
+<Text id="185">ÐÑÑÑÑÑÑÐ²ÑÐµÑ</Text>
+</th>
+<th width="293">
+<Text id="186">ÐÐµ ÑÐŽÐ°Ð»ÑÐµÑ ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ Ð¿ÑÐµÐŽÑÐŽÑÑÐžÑ
+ Ð·Ð°Ð¿ÑÑÐºÐŸÐ² Ð¿ÑÐŸÑÐµÑÑÐŸÐ² import ÐžÐ»Ðž build; Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÐžÐŒÐ¿ÐŸÑÑÐ° ÐœÐµ ÑÐŽÐ°Ð»ÑÐµÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž archives', Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐœÐµ ÐŸÑÐžÑÐ°ÐµÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž building.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="187"><i>âdebug</i></Text>
+</th>
+<th width="104">
+<Text id="188">ÐÑÑÑÑÑÑÐ²ÑÐµÑ</Text>
+</th>
+<th width="293">
+<Text id="189"> ÐÐµÑÐ°ÑÑ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² ÑÐ°Ð±ÐŸÑÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹ ÐŸÑÐ»Ð°ÐŽÐºÐž.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Subsection id="the_import_process">
+<Title>
+<Text id="190">ÐÑÐŸÑÐµÑÑ import</Text>
+</Title>
+<Content>
+<Text id="191">ÐÑÐŸÑÐµÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ° ÑÐ»ÑÐ¶ÐžÑ ÐŽÐ»Ñ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐžÐ· ÐžÑ
+ Ð¿ÐµÑÐ²ÐžÑÐœÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ² Ð² Ð€ÐŸÑÐŒÐ°Ñ ÐÑÑ
+ÐžÐ²Ð° Greenstone, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÑÐžÑÑÐµÐŒÐŸÐ¹ Greenstone, Ðž Ð·Ð°Ð¿ÐžÑÐž Ð² ÐºÐŸÐœÐµÑÐœÑÐ¹ ÑÐ°Ð¹Ð» (Ñ ÐžÐŒÐµÐœÐµÐŒ archives, inf), ÐºÐŸÑÐŸÑÑÐ¹ Ð±ÑÐŽÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ ÑÐŸÐ³ÐŽÐ°, ÐºÐŸÐ³ÐŽÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐ¶Ðµ Ð±ÑÐŽÐµÑ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐ°. Import.pl ÐŽÐŸÐ»Ð¶ÐµÐœ Ð·ÐœÐ°ÑÑ, ÐºÐ°ÐºÐŸÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð±ÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐŸ Ðž Ð³ÐŽÐµ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÑÐ°Ð¹Ð»-ÐŸÑÐžÐ³ÐžÐœÐ°Ð» ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÐŸÐ¿ÑÐžÐž ÐŽÐ»Ñ Ð¿ÑÐŸÑÐµÑÑÐŸÐ² ÐžÐŒÐ¿ÐŸÑÑÐ° Ðž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ; Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="additional_options_for_the_import_process"/> ÐŽÐ°ÐœÑ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÐµ ÐŸÐ¿ÑÐžÐž, ÐºÐ°ÑÐ°ÑÑÐžÐµÑÑ ÑÐŸÐ»ÑÐºÐŸ Ð¿ÑÐŸÑÐµÑÑÐ° ÐžÐŒÐ¿ÐŸÑÑÐ°. ÐÐ¿ÑÐžÐž OIDtype Ð·Ð°ÑÐ»ÑÐ¶ÐžÐ²Ð°ÑÑ Ð±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÐ³ÐŸ ÑÐ°ÑÑÐŒÐŸÑÑÐµÐœÐžÑ. ÐÐ°Ð¶ÐŽÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐžÐŒÐµÐµÑ ÑÐ²ÑÐ·Ð°ÐœÐœÑÐ¹ Object IdentiÂ¬fier (ÐÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑ ÐÐ±ÑÐµÐºÑÐ°) ÐžÐ»Ðž OID. Ð­ÑÐŸ ÐœÐ°ÐžÐ»ÑÑÑÐžÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÐŽÐ»Ñ Ñ
+ÐµÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° (hash/Ñ
+ÐµÑ). Ð¥ÐŸÑÑ ÐŸÐœ Ðž ÐŸÑÐµÐœÑ ÐŒÐµÐŽÐ»ÐµÐœÐœÑÐ¹, ÐœÐŸ Ð²ÑÐµ Ð¶Ðµ ÑÐ²Ð»ÑÐµÑÑÑ ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ Ð¿ÑÐŸÑÑÐŸÐ¹ Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²ÐŸÐ¹ ÐœÐ°ÐºÐŸÐ¿Ð»ÐµÐœÐžÑ, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÑÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐŸÐœÐž Ð±ÑÐ»Ðž ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÑ. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐœÐ°ÐºÐŸÐ¿Ð»ÐµÐœÐžÐµ ÐŽÐ»Ñ ÑÑÐºÐŸÑÐµÐœÐžÑ ÑÐ°Ð±ÐŸÑÑ, ÐœÐŸ Ð²ÑÐµ Ð¶Ðµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ Ñ
+ÐµÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð² ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž Ð¿ÐŸÐ·Ð¶Ðµ Ð·Ð°Ñ
+ÐŸÑÐžÑÐµ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ðº Ð²Ð°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (Ð±ÐµÐ· Ð¿ÐŸÐ²ÑÐŸÑÐœÐŸÐ¹ Ð¿ÑÐŸÑÐµÐŽÑÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ°).</Text>
+<Table id="additional_options_for_the_import_process">
+<Title>
+<Text id="192">ÐÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÐµ ÐŸÐ¿ÑÐžÐž ÐŽÐ»Ñ Ð¿ÑÐŸÑÐµÑÑÐ°</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="104">
+<Text id="193"><b>ÐÑÐ³ÑÐŒÐµÐœÑ</b></Text>
+</th>
+<th width="293">
+<Text id="194"><b>Ð€ÑÐœÐºÑÐžÑ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="195"><i>-importdir</i></Text>
+</th>
+<th width="104">
+<Text id="196">ÐÐŒÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž</Text>
+</th>
+<th width="293">
+<Text id="197">Ð£ÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÑÐŸ, Ð³ÐŽÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐœÐ°Ð¹ÐŽÐµÐœÑ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ. ÐÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ: GSDLHOME/collect/coljiame/import.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="198"><i>-removeold</i></Text>
+</th>
+<th width="104">
+<Text id="199">ÐÑÑÑÑÑÑÐ²ÑÐµÑ</Text>
+</th>
+<th width="293">
+<Text id="200">ÐÑÐžÑÐ°ÐµÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž archives Ð¿ÐµÑÐµÐŽ Ð¿ÑÐŸÑÐµÑÑÐŸÐŒ ÐžÐŒÐ¿ÐŸÑÑÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="201"><i>-gzip</i></Text>
+</th>
+<th width="104">
+<Text id="202">ÐÑÑÑÑÑÑÐ²ÑÐµÑ          </Text>
+</th>
+<th width="293">
+<Text id="203">Zip Ð°ÑÑ
+ÐžÐ²ÐžÑÑÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Greenstone, Ð¿ÐŸÐ»ÑÑÐµÐœÐœÑÐµ Ð² ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ Ð¿ÑÐŸÑÐµÑÑÐ° ÐžÐŒÐ¿ÐŸÑÑÐ° (ZIPPlug ÐŽÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ Ð²ÐºÐ»ÑÑÐµÐœ Ð² ÑÐ¿ÐžÑÐŸÐº Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹, a gzip ÐŽÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="204"><i>-groupsize</i></Text>
+</th>
+<th width="104">
+<Text id="205">Ð§ÐžÑÐ»ÐŸ Ð¥</Text>
+</th>
+<th width="293">
+<Text id="206">ÐÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð³ÑÑÐ¿Ð¿ÐžÑÑÐµÐŒÑÑ
+ Ð² ÐŸÐŽÐžÐœ Ð°ÑÑ
+ÐžÐ²ÐœÑÐ¹ ÑÐ°Ð¹Ð» Greenstone, Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ 1 (ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ 1 ÐŽÐŸÐºÑÐŒÐµÐœÑÐµ 1 ÑÐ°Ð¹Ð»).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="207"><i>âsortmeta</i></Text>
+</th>
+<th width="104">
+<Text id="208">ÐÐŒÑ ÑÑÐ³Ð°</Text>
+</th>
+<th width="293">
+<Text id="209">Ð¡ÐŸÑÑÐžÑÑÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² Ð°Ð»ÑÐ°Ð²ÐžÑÐœÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ Ð¿ÐŸ ÐžÐŒÐµÐœÐž ÑÑÐ³Ð° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+          ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐŽÐœÐ°ÐºÐŸ, ÐµÑÐ»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐŒÐµÐµÑ Ð±ÐŸÐ»ÐµÐµ 1 Ð³ÑÑÐ¿Ð¿Ñ Ð² ÐŸÐŽÐœÐŸÐŒ Ð°ÑÑ
+ÐžÐ²ÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ (Ñ.Ðµ. groupsize >1), ÑÑÐ° ÑÑÐœÐºÑÐžÑ Ð±ÑÐŽÐµÑ Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="210"><i>-OIDtype</i></Text>
+</th>
+<th width="104">
+<Text id="211">Ð¥ÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</th>
+<th width="293">
+<Text id="212">ÐÐµÑÐŸÐŽ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐÐš ÐŽÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²: Ñ
+ÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ, ÐŸÑÐµÐœÑ ÐžÐ»Ðž ÐœÐ°Ð¿ÐŸÐ»ÐœÐµÐœÐžÐµ     ÐŒÐµÐŽÐ»ÐµÐœÐœÑÐ¹ ÐŒÐµÑÐŸÐŽ; ÐŒÐµÑÐŸÐŽ ÐœÐ°Ð¿ÐŸÐ»ÐœÐµÐœÐžÑ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ð³ÐŸÑÐ°Ð·ÐŽÐŸ Ð±ÑÑÑÑÐµÐµ Ðž Ð·Ð°ÐºÐ»ÑÑÐ°ÐµÑÑÑ Ð² Ð¿ÑÐŸÑÑÐŸÐŒ Ð¿ÑÐžÑÐ²Ð°ÐžÐ²Ð°ÐœÐžÐž Ð²Ñ
+ÐŸÐŽÑÑÐžÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸÐ³ÐŸ ÐœÐŸÐŒÐµÑÐ°</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Figure id="steps_in_the_import_process">
+<Title>
+<Text id="213">ÐÐŸÑÐ°Ð³ÐŸÐ²ÐŸÐµ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ Ð¿ÑÐŸÑÐµÑÑÐ° import</Text>
+</Title>
+<File width="402" height="379" url="images/Dev_Fig_012.png"/>
+</Figure>
+<Text id="214">ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="steps_in_the_import_process"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ Ð¿ÑÐŸÑÐµÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ°, ÐžÐœÐžÑÐžÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ Ð¿ÑÐŸÑÐµÐŽÑÑÐŸÐ¹ ÑÐ°Ð±ÐŸÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ import.pl. ÐÐ°Ð¶ÐŽÑÐ¹ ÐŸÐ²Ð°Ð» Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑÑÐŸÐ±ÐŸÐ¹ ÐŒÐŸÐŽÑÐ»Ñ ÐžÑÐ¿ÐŸÐ»ÐœÑÑÑÐžÐ¹ Ð·Ð°ÐŽÐ°ÑÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐ¹ ÑÐ°ÑÑÐž ÑÐžÑÑÐµÐŒÑ Greenstone. ÐÑÐµ ÑÑÐž ÐŒÐŸÐŽÑÐ»Ðž ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž GSDLHOME/perllib.</Text>
+<Text id="215">ÐÐ»Ñ ÑÐ°Ð³Ð° 3. ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ, ÑÑÐŸ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÐµ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÑÐ°ÐºÐžÐµ ÐºÐ°Ðº importdir Ðž archivedir ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð·Ð°Ð¿ÑÑÐµÐœÑ ÐžÐ· ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž ÐžÐ»Ðž ÐžÐ· ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.ÐÑÐ»Ðž Ð·Ð°Ð¿ÑÑÐº Ð¿ÑÐŸÐžÐ·Ð²ÐµÐŽÐµÐœ ÐžÐ· ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž, ÑÐŸ Ð²ÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž, ÑÐŽÐµÐ»Ð°ÐœÐœÑÐµ ÑÐµÑÐµÐ· ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž, ÐžÐ³ÐœÐŸÑÐžÑÑÑÑÑÑ.</Text>
+<Text id="216">ÐÐ° 6 ÑÐ°Ð³Ðµ Ð±ÑÐ» ÑÐŸÐ·ÐŽÐ°Ðœ ÑÐ°Ð¹Ð» ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐŸÐ³ÐŸ Ð°ÑÑ
+ÐžÐ²Ð° (archives.ini).</Text>
+<Text id="217">ÐÐ° 7 ÑÐ°Ð³Ðµ Ð±ÑÐ» ÑÐŸÐ·ÐŽÐ°Ðœ ÐŸÐ±ÑÐµÐºÑ, ÐºÐŸÑÐŸÑÑÐ¹ Ñ
+ÑÐ°ÐœÐžÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÑÐŸÐŒ, ÐºÑÐŽÐ° Ð±ÑÐ»Ðž Ð·Ð°Ð¿ÐžÑÐ°ÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, Ðž Ð¿ÐŸÐŽÑÐžÐœÑÐµÑÑÑ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÐŒ ÐžÐœÑÑÑÑÐºÑÐžÑÐŒ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐžÑ (ÑÐ°ÐºÐžÐŒ ÐºÐ°Ðº sortmeta, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŸÑÑÐžÑÑÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž ÑÐŸ ÑÐ¿ÐµÑÐžÑÐžÐºÐŸÐ¹ ÑÑÐ³ÐŸÐ² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+).</Text>
+<Text id="218">ÐÐŸÐ»ÑÑÐ°Ñ ÑÐ°ÑÑÑ ÑÐ°Ð±ÐŸÑÑ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÐžÐŒÐ¿ÐŸÑÑÐ° ÐŽÐµÐ»Ð°ÐµÑÑÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑÐŒÐž, Ð²ÑÐ·ÑÐ²Ð°ÐµÐŒÑÐŒÐž ÐŒÐŸÐŽÑÐ»ÐµÐŒ plugin. Ð­ÑÐŸÑ ÐŒÐŸÐŽÑÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐºÐŸÐœÐ²ÐµÐ¹ÐµÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÑ
+ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐœ ÑÐ°ÐºÐ¶Ðµ ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐµÑ Ð·Ð°Ð¿ÐžÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð°ÑÑ
+ÐžÐ²Ð° Greenstone, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŸÐ±ÑÐµÐºÑ document.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_build_process">
+<Title>
+<Text id="219">ÐÑÐŸÑÐµÑÑ build</Text>
+</Title>
+<Content>
+<Text id="220">Ð ÑÐµÑÐµÐœÐžÐµ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ ÑÐ¶Ð°ÑÐžÐµ ÑÐµÐºÑÑÐ°, Ð¿ÐŸ Ð¿ÐŸÐ»ÐœÐŸÐŒÑ ÑÐµÐºÑÑÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ ÐžÐœÐŽÐµÐºÑÐ°ÑÐžÑ, ÐŸÐ¿ÐžÑÐ°ÐœÐœÐ°Ñ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐŸÐŒÐµ ÑÐŸÐ³ÐŸ, ÐœÐ° ÑÑÐŸÐŒ ÑÑÐ°Ð¿Ðµ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²ÐµÑÑÑ Ðž Ð¿ÐŸÐŽÐºÐ»ÑÑÐ°ÐµÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÑÐŸÐŒ, ÐºÐ°Ðº ÑÐ¶Ðµ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð±ÑÐŽÐµÑ Ð²ÑÐ³Ð»ÑÐŽÐµÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÐžÑÐœÐŸÐ¹ Ð¿Ð°ÑÑÐžÐœÐµ -ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŽÐ°ÐœÐœÑÐµ ÐŸ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ°Ñ
+ Ðž ÐžÐºÐŸÐœÐºÐ°Ñ
+, ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐŸÐœÐœÑÐµ ÐŽÐ°ÐœÐœÑÐµ Ðž Ñ.ÐŽ. Buildcol.pl ÐžÐŒÐµÐµÑ ÐŒÐœÐŸÐ³ÐŸ ÐŸÐ¿ÑÐžÐ¹, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸ Ñ import.pl, ÑÐŒ. Ð¢Ð°Ð±Ð»ÐžÑÑ <CrossRef target="Table" ref="options_for_the_import_and_build_processes"/>, Ðž ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐœÐžÐºÐ°Ð»ÑÐœÑÑ
+, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÑÑ
+ Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="additional_options_for_the_build_process"/>.</Text>
+<Table id="additional_options_for_the_build_process">
+<Title>
+<Text id="221">ÐÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÐµ ÐŸÐ¿ÑÐžÐž ÐŽÐ»Ñ Ð¿ÑÐŸÑÐµÑÑÐ°</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="104">
+<Text id="222"><b>ÐÑÐ³ÑÐŒÐµÐœÑ</b></Text>
+</th>
+<th width="293">
+<Text id="223"><b>Ð€ÑÐœÐºÑÐžÑ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="224"><i>-builddir</i></Text>
+</th>
+<th width="104">
+<Text id="225">ÐÐŒÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž</Text>
+</th>
+<th width="293">
+<Text id="226">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ, Ð³ÐŽÐµ Ð±ÑÐŽÐµÑ Ñ
+ÑÐ°ÐœÐžÑÑÑÑ ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ: <i>GSDLHOME/collect/col_name/building</i>).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="227"><i>-index</i></Text>
+</th>
+<th width="104">
+<Text id="228">ÐÐœÐŽÐµÐºÑÐœÐŸÐµ ÐžÐŒÑ</Text>
+</th>
+<th width="293">
+<Text id="229">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐžÐœÐŽÐµÐºÑÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ. ÐÐ°ÐœÐœÐ°Ñ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ '.Title) Ð¿ÑÐŸÑÐµÐŽÑÑÐ° Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Ð¿ÑÐžÑÐ²Ð°ÐžÐ²Ð°ÐµÑ ÐžÐœÐŽÐµÐºÑÑ, ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐœÑÐµ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="230"><i>-allclassifications</i></Text>
+</th>
+<th width="104">
+<Text id="231">ÐÑÑÑÑÑÑÐ²ÑÐµÑ</Text>
+</th>
+<th width="293">
+<Text id="232">Ð Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð¿ÑÐµÐŽÑÐ¿ÑÐµÐ¶ÐŽÐ°ÐµÑ ÑÐŽÐ°Ð»ÐµÐœÐžÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐ¹, ÐœÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÑ Ð¿ÐŸ Ð»ÐžÑÐµÑÐµ "X" Ð² Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐµ, Ð² ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž ÑÐ°ÐŒ ÐœÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÑÐµÐ¹ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐœÐ°ÑÐžÐœÐ°ÐµÑÑÑ Ñ Ð»ÐžÑÐµÑÑ "X").</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="233"><i>-create_images</i></Text>
+</th>
+<th width="104">
+<Text id="234">ÐÑÑÑÑÑÑÐ²ÑÐµÑ</Text>
+</th>
+<th width="293">
+<Text id="235">ÐÐ²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐºÐŸÐœÐŸÐº (ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÑÑÐŸÐ¹ ÐŸÐ¿ÑÐžÐµÐ¹ Ñ Ð²Ð°Ñ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ GIMP Ðž ÐŒÐŸÐŽÑÐ»Ñ Gimp Perl).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="236"><i>-mode</i></Text>
+</th>
+<th width="104">
+<Text id="237"><i>all</i>, <br/><i>compress_text</i>, <br/><i>infodb</i>, ÐžÐ»Ðž <br/><i>build index</i></Text>
+</th>
+<th width="293">
+<Text id="238">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ, ÑÑÐŸ ÐŽÐŸÐ»Ð¶ÐµÐœ ÑÐŽÐµÐ»Ð°ÑÑ Ð¿ÑÐŸÑÐµÑÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ all). All Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑ Ð¿ÐŸÐ»ÐœÐŸÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐµ, compress_text ÑÐŸÐ»ÑÐºÐŸ ÑÐ¶Ð°ÑÐžÐµ ÑÐµÐºÑÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, infodb ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž, ÐŸÑÐœÐŸÑÑÑÐµÐ¹ÑÑ Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž - ÐžÐŒÑ, ÑÐ°Ð¹Ð»Ñ, ÑÐ²ÑÐ·ÐœÑÐµ ÑÐ°Ð¹Ð»Ñ, ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐŸÐœÐœÐ°Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ Ðž Ñ.Ð¿., - build index -ÑÐŸÑÐŒÐžÑÑÐµÑ ÐžÐœÐŽÐµÐºÑÑ, ÑÐºÐ°Ð·Ð°ÐœÐœÑÐµ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»ÐµÐºÑÐžÐž ÐžÐ»Ðž Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="239"><i>âno_text</i></Text>
+</th>
+<th width="104"/>
+<th width="293">
+<Text id="240">ÐÐµ Ñ
+ÑÐ°ÐœÐžÑ ÑÐ¶Ð°ÑÑÐ¹ ÑÐµÐºÑÑ. ÐÐ°ÐœÐœÐ°Ñ ÐŸÐ¿ÑÐžÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² ÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ ÐŒÐžÐœÐžÐŒÐžÐ·ÐžÑÐŸÐ²Ð°ÑÑ ÑÐ°Ð·ÐŒÐµÑ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐœÑÑ
+ ÐžÐœÐŽÐµÐºÑÐŸÐ², Ð² ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž Ð²Ñ ÐœÐ°ÐŒÐµÑÐµÐœÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ Ð·Ð°Ð¿ÑÑÐºÐ° Ð²ÑÐµÐ³ÐŽÐ° Ð²ÑÐ²ÐŸÐŽÐžÑÑ ÐœÐ° ÑÐºÑÐ°Ðœ ÐŸÑÐžÐ³ÐžÐœÐ°Ð» ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Figure id="steps_in_the_build_process">
+<Title>
+<Text id="241">ÐÐŸÑÐ°Ð³ÐŸÐ²ÐŸÐµ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ Ð¿ÑÐŸÑÐµÑÑÐ° <i>build</i></Text>
+</Title>
+<File width="308" height="234" url="images/Dev_Fig_014.png"/>
+</Figure>
+<Text id="242">ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="steps_in_the_build_process"/> Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐ° ÐŽÐžÐ°Ð³ÑÐ°ÐŒÐŒÐ° Ð¿ÐŸÑÐ°Ð³ÐŸÐ²ÐŸÐ³ÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ Ð¿ÑÐŸÑÐµÑÑÐ° buildcol.pl. ÐÐœÐŸÐ³ÐžÐµ ÐžÐ· ÑÐ°Ð³ÐŸÐ² ÐŸÑÐœÐŸÑÑÑÑÑ Ðž Ðº Ð¿ÑÐŸÑÐµÑÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ°. ÐÐµÑÐ²ÑÐ¹ ÐŸÑÐ»ÐžÑÐžÑÐµÐ»ÑÐœÑÐ¹ ÑÐ°Ð³ - 4. ÐÐœ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ ÑÐŸÐ»ÑÐºÐŸ Ð² ÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÐŸÐ¿ÑÐžÑ create_images. ÐÐ°ÑÐµÐŒ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÐŸÐ·ÐŽÐ°ÑÑÑÑ Ðž ÑÐµÐ³ÐžÑÑÑÐžÑÑÑÑÑÑ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÑÐœÐºÑÐžÐµÐ¹ ÑÐºÑÐžÐ¿ÑÐ° buildcol.pl. ÐÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÑÑÐŸ ÑÑÐ°Ð±ÐŸÑÐ°Ð»ÐŸ, ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ Ðž ÑÐºÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÐœÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° GIMP (GNU Image Manipulation Program) Ðž ÐŒÐŸÐŽÑÐ»Ñ Gimp Perl. ÐÐŸÐŒÐžÐŒÐŸ ÑÑÐŸÐ³ÐŸ, Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÐžÐŒÐµÑÑ ÐŽÐŸÑÑÑÐ¿ Ñ Ð¿ÑÐ°Ð²ÐŸÐŒ Ð·Ð°Ð¿ÐžÑÐž (ÑÐ°Ðº Ð¶Ðµ, ÐºÐ°Ðº Ðž ÑÑÐµÐœÐžÑ) Ð² ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="243">ÐšÐ°Ð³ 5 ÑÐœÐ°ÑÐ°Ð»Ð° Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ ÐœÐ°Ð»ÐžÑÐžÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð¿ÑÐŸÑÐµÐŽÑÑÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÑÐµÐ±ÑÑÑ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÐŸÐ¹ ÑÐ°Ð·ÐŸÐ²ÐŸÐ¹ Ð¿ÑÐŸÑÐµÐŽÑÑÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ, Ð¿ÑÐž ÐºÐŸÑÐŸÑÐŸÐ¹ ÑÐºÐ°Ð·Ð°ÐœÐœÑÐ¹ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐŸÑÑÐ°Ð²ÐžÑÐµÐ»Ñ ÐŽÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ ÐŸÐ¿ÐžÑÐ°Ðœ, Ðž ÑÑÐ° Ð·Ð°Ð¿ÐžÑÑ (ÐžÐŒÑ ÑÐ°Ð¹Ð»Ð° ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð¿ÑÐžÑÑÐ°Ð²ÐºÑ "builder") Ð¿ÐŸÐŒÐµÑÐµÐœÐ° Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž perllib. Mgbuilder, Ð² ÑÐ²ÐŸÑ ÐŸÑÐµÑÐµÐŽÑ, Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐµÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ Ð·Ð°ÑÐ²Ð»ÐµÐœÐœÑÑ
+ ÑÐŸÑÑÐ°Ð²ÐžÑÐµÐ»ÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ° 5 ÑÐ°Ð³Ðµ ÑÐŸÑÑÐ°Ð²ÐžÑÐµÐ»Ñ (Ð»ÐžÐ±ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, Ð»ÐžÐ±ÐŸ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž) ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ ÐžÑÑ
+ÐŸÐŽÐœÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ, ÑÐ°ÐºÐžÐµ ÐºÐ°Ðº ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð²ÐºÐ»ÑÑÐ°ÐµÐŒÑÑ
+ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐŽÐŸÐ»Ð¶ÐœÐ° Ð»Ðž Ð±ÑÑÑ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐ° Ð¿ÑÐµÐŽÑÐŽÑÑÐ°ÑÑ Ð²ÐµÑÑÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð³ÐŽÐµ ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž building Ðž archive.</Text>
+<Text id="244">ÐÐ° 6 ÑÐ°Ð³Ðµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐµÐºÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐ¶Ð°Ñ Ðž Ð¿ÑÐŸÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°Ðœ, ÐžÐºÐŸÐœÐºÐž Ðž Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž Ð¿ÐŸÐŒÐµÑÐµÐœÑ Ð² ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÑÑ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐŽÐ°ÐœÐœÑÐµ ÑÑÑÑÐºÑÑÑÐžÑÐŸÐ²Ð°ÐœÑ Ð¿ÑÐž Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ², Ð²Ð¿ÐŸÑÐ»ÐµÐŽÑÑÐ²ÐžÐž Ð²ÑÐ·ÑÐ²Ð°ÐµÐŒÑÑ
+ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐµÐŒÐž ÑÑÐžÐŒÐž ÑÐ°Ð³Ð°ÐŒÐž ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑ mgbuilder (ÐžÐ»Ðž ÑÐ¿ÐŸÐ»ÐœÐŸÐŒÐŸÑÐµÐœÐœÑÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹ ÐºÐŸÐŒÐ¿Ð°ÐœÐŸÐ²ÑÐžÐº), ÐºÐŸÑÐŸÑÑÐ¹, Ð² ÑÐ²ÐŸÑ ÐŸÑÐµÑÐµÐŽÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐŽÐ»Ñ ÑÐ¶Ð°ÑÐžÑ Ðž ÐžÐœÐŽÐµÐºÑÐ°ÑÐžÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ MG ("ManÂ¬aging Gigabytes," ÑÐŒ. Witten et al., 1999).</Text>
+<Text id="245">Ð§Ð°ÑÑÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÑ ÐŸÐ¿ÑÐžÐµÐ¹ mode, ÐŸÐŽÐœÐ°ÐºÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÑÑ Ð²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÐµÐ¶ÐžÐŒ "Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ" - ÑÐ¶Ð°ÑÑ ÑÐµÐºÑÑ, Ð¿ÑÐŸÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐµÐ³ÐŸ, ÑÐŸÐŽÐ°ÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÑÑ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="246">ÐÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐŽÐŸÑÑÑÐ¿Ð° Ðº ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐµÑÐµÐ· ÑÐµÑÑ ÐÐœÑÐµÑÐœÐµÑ Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ Ð¿ÐµÑÐµÐŒÐµÑÑÐžÑÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž building Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ index. ÐÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐœÐµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐ° ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž inÂ¬dex, ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð±ÐŸÐ»ÑÑÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐŒÐŸÐ¶ÐµÑ ÐŽÐ»ÐžÑÑÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ°ÑÐŸÐ², Ð° ÑÐŸ Ðž ÐŽÐœÐµÐ¹. ÐÐ°Ð¶ÐœÐŸÐ¹ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÑÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐŸ, ÑÑÐŸ ÐŸÐœ ÐœÐµ Ð²ÐœÐŸÑÐžÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÐ¹ Ð² ÑÑÑÐµÑÑÐ²ÑÑÑÑÑ ÐºÐŸÐ¿ÐžÑ ÐŽÐŸ ÑÐµÑ
+ Ð¿ÐŸÑ, Ð¿ÐŸÐºÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐœÐµ Ð±ÑÐŽÐµÑ ÐŸÐºÐŸÐœÑÐ°ÑÐµÐ»ÑÐœÐŸ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐ°.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="greenstone_archive_documents">
+<Title>
+<Text id="247">ÐÑÑ
+ÐžÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Greenstone</Text>
+</Title>
+<Content>
+<Text id="248">ÐÑÐµ ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, Ð²ÐœÐŸÑÐžÐŒÑÐµ Ð² ÑÐžÑÑÐµÐŒÑ Greenstone ÐºÐŸÐœÐ²ÐµÑÑÐžÑÑÑÑÑÑ Ð² ÑÐŸÑÐŒÐ°Ñ, ÐžÐ·Ð²ÐµÑÑÐœÑÐ¹ ÐºÐ°Ðº Greenstone Archive Format (Ð€ÐŸÑÐŒÐ°Ñ ÐÑÑ
+ÐžÐ²Ð° Greenstone). Ð­ÑÐŸ ÑÐŸÑÐŒÐ°Ñ XML, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ°Ð·ÐŒÐµÑÐ°ÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð°ÐŒ Ðž Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ ÑÐµÐ¶ÐžÐŒ ÑÐ°Ð±ÐŸÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐœÐ° ÑÑÐŸÐ²ÐœÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐžÐ»Ðž ÑÐ°Ð·ÐŽÐµÐ»Ð°. ÐÐ°ÐŒ ÐœÐµ Ð¿ÑÐžÐŽÐµÑÑÑ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÑÐ°Ð¹Ð»Ñ Ð°ÑÑ
+ÐžÐ²Ð° Greenstone Ð²ÑÑÑÐœÑÑ, Ñ.Ðº. ÑÑÐŸÐ¹ ÑÐ°Ð±ÐŸÑÐŸÐ¹ Ð·Ð°ÐœÐžÐŒÐ°ÐµÑÑÑ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÐŸÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐŸÐ¿ÐžÑÐ°ÐœÐœÐŸÐµ Ð² ÑÐ»ÐµÐŽÑÑÑÐµÐ¹ Ð³Ð»Ð°Ð²Ðµ. ÐÐŽÐœÐ°ÐºÐŸ, Ñ.Ðº. ÑÑÐŸ ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÐŒÐŸÑÑ Ð² Ð¿ÐŸÐœÐžÐŒÐ°ÐœÐžÐž ÑÐŸÑÐŒÐ°ÑÐ° ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐžÑÑÐµÐŒÑ Greenstone, ÐŒÑ ÑÐµÑÐžÐ»Ðž Ð¿ÐŸÐŒÐµÑÑÐžÑÑ ÑÑÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐœÐžÐ¶Ðµ.</Text>
+<Text id="249">Ð XML ÑÑÐ³Ðž ÑÐ°Ð·ÐŒÐµÑÐºÐž Ð·Ð°ÐºÐ»ÑÑÐµÐœÑ Ð² Ð·ÐœÐ°ÐºÐž ÐŸ. Ð€ÐŸÑÐŒÐ°Ñ Ð°ÑÑ
+ÐžÐ²Ð° Greenstone Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÑÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÐµÑÑ Ð² ÑÐŸÑÐŒÐ°ÑÐµ HTML Ðž ÐŽÑ. Ð²ÑÑÐ°Ð²Ð»ÑÑ ÑÐžÐŒÐ²ÐŸÐ»Ñ &lt;, &gt;, ÐžÐ»Ðž " Ð² ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ ÑÐµÐºÑÑ Ðž ÐžÐ·Ð±ÐµÐ³Ð°Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ
+ ÑÑÐ»ÐŸÐ²ÐžÐ¹ &amp;lt;, &amp;gt; Ðž &amp;quot;.</Text>
+<Figure id="greenstone_archive_format">
+<Title>
+<Text id="250">Ð€ÐŸÑÐŒÐ°Ñ Ð°ÑÑ
+ÐžÐ²Ð° Greenstone: Ð°) Document Type DefiniÂ¬tion /ÐÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ ÑÐžÐ¿Ð°
+ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° (DTD); Ð±)  ÐÑÐžÐŒÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°</Text>
+<SubTitle>
+<Text id="251">(a)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;!DOCTYPE GreenstoneArchive [</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Section (Description,Content,Section*)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Description (Metadata*)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Content (#PCDATA)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;!ELEMENT Metadata (#PCDATA)&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;ATTLIST Metadata name CDATA #REQUIRED&gt;</CodeLine>
+<CodeLine>]&gt;</CodeLine>
+</Figure>
+<Figure id="greenstone_archive_format_1">
+<Title>
+<Text id="252"/>
+<SubTitle>
+<Text id="253">(b)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;?xml version="1.0"?&gt;</CodeLine>
+<CodeLine>&lt;!DOCTYPE GreenstoneArchive SYSTEM</CodeLine>
+<CodeLine>"http://greenstone.org/dtd/GreenstoneArchive/1.0/GreenstoneArchive.dtd" &gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "gsdlsourcefilename"&gt;ec158e.txt&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Freshwater Resources in Arid Lands&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "Identifier"&gt;HASH0158f56086efffe592636058&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "gsdlassocfile"&gt;cover.jpg:image/jpeg:&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Metadata name= "gsdlassocfile"&gt;p07a.png:image/png:&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Preface&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>This is the text of the preface</i>
+</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;First and only chapter&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Part 1&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>This is the first part of the first and only chapter</i>
+</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;Section&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â &lt;Metadata name= "Title"&gt;Part 2&lt;/Metadata&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;/Description&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <i>This is the second part of the first and only chapter</i>
+</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â Â Â &lt;/Content&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>Â Â Â &lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+</Figure>
+<Text id="254">ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="greenstone_archive_format"/> Ð²Ð°ÑÐµÐŒÑ Ð²ÐœÐžÐŒÐ°ÐœÑ Ð¿ÑÐµÐŽÐ»ÐŸÐ¶ÐµÐœ Document Type Definition/ ÐÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ ÑÐžÐ¿Ð° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° (DTD) ÑÐ·ÑÐºÐ° XML ÐŽÐ»Ñ ÑÐŸÑÐŒÐ°ÑÐ° Ð°ÑÑ
+ÐžÐ²Ð° GreenÂ¬stone. ÐÐ·ÐœÐ°ÑÐ°Ð»ÑÐœÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÑÐ°Ð·Ð±ÐžÐ²Ð°ÐµÑÑÑ ÐœÐ° Sections (ÑÐµÐºÑÐžÐž ÐžÐ»Ðž ÑÐ°Ð·ÐŽÐµÐ»Ñ), ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð²Ð»ÐŸÐ¶ÐµÐœÐœÑÐŒÐž. ÐÐ°Ð¶ÐŽÐ°Ñ Section ÐžÐŒÐµÐµÑ Description (ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ) ÐºÐŸÑÐŸÑÐŸÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÑ 0 ÐžÐ»Ðž Ð±ÐŸÐ»ÐµÐµ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² Metadata, Ð° ÑÐ°ÐºÐ¶Ðµ ConÂ¬tent (ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐµÐ»ÑÐœÑÑ ÑÐ°ÑÑÑ), ÐºÐŸÑÐŸÑÐ°Ñ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÑÐ°Ð²ÐœÐ° ÐœÑÐ»Ñ, Ð° ÑÐ°ÐºÑÐžÑÐµÑÐºÐž ÑÑÐŸ ÑÐ° ÑÐ°ÑÑÑ, Ð³ÐŽÐµ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐ°Ð¶ÐŽÐŸÐŒÑ ÑÐ»ÐµÐŒÐµÐœÑÑ Metadata ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÐµÑ ÐžÐŒÑ Ð°ÑÑÐžÐ±ÑÑÐ° Ðž ÑÐµÐºÑÑÐŸÐ²ÑÐµ ÐŽÐ°ÐœÐœÑÐµ. Ð XML, PCDATA ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ "parsed character ÑÐ«:Ð°"(Ð°ÐœÐ°Ð»ÐžÐ·ÐžÑÑÐµÐŒÑÐµ ÑÐžÐŒÐ²ÐŸÐ»ÑÐœÑÐµ ÐŽÐ°ÐœÐœÑÐµ): Ð² ÐŸÑÐœÐŸÐ²ÐœÐŸÐŒ ÑÐµÐºÑÑ.</Text>
+<Text id="255">Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="greenstone_archive_format_1"/> ÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÑÐµÑ Ð¿ÑÐžÐŒÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð² ÑÑÐŸÐŒ ÑÐŸÑÐŒÐ°ÑÐµ, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑÑÐžÐ¹ ÑÐŸÐ±ÐŸÐ¹ ÐœÐµÐ±ÐŸÐ»ÑÑÑÑ ÐºÐœÐžÐ³Ñ Ñ ÐŽÐ²ÑÐŒÑ ÑÐ²ÑÐ·ÐœÑÐŒÐž ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑÐŒÐž. Ð­ÑÐ° ÐºÐœÐžÐ³Ð° ÑÐŸÑÑÐŸÐžÑ ÐžÐ· ÐŽÐ²ÑÑ
+ ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ², ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÑ
+ Preface Ðž First and only chapter, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŸÑÑÐŸÐžÑ ÐžÐ· ÐŽÐ²ÑÑ
+ Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ². ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÑÐŸ, ÑÑÐŸ ÐœÐµÑ ÐœÐžÐºÐ°ÐºÐŸÐ³ÐŸ Ð¿ÐŸÐœÑÑÐžÑ "chapter": ÐŽÐ°ÐœÐœÑÐ¹ ÑÐ°Ð·ÐŽÐµÐ» Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ Ð¿ÑÐŸÑÑÐŸ ÐºÐ°Ðº ÑÐ°Ð·ÐŽÐµÐ» Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ.</Text>
+<Table id="greenstone_archive_format_values">
+<Title>
+<Text id="256">Ð€ÐŸÑÐŒÐ°Ñ Ð°ÑÑ
+ÐžÐ²Ð° Greenstone: ÐÐœÐ°ÑÐµÐœÐžÑ ÐŽÐ»Ñ Ð°ÑÑÐžÐ±ÑÑÐ° <i>name</i> ÑÑÐ³Ð° <i>Metadata</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="130">
+<Text id="257"><i>gsdlsourcefilename</i></Text>
+</th>
+<th width="400">
+<Text id="258">ÐÑÑ
+ÐŸÐŽÐœÑÐ¹ ÑÐ°Ð¹Ð», ÐžÐ· ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»ÐŸÐŒ Ð°ÑÑ
+ÐžÐ²Ð° Greenstone Ð±ÑÐ» ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°Ðœ</Text>
+</th>
+</tr>
+<tr>
+<th width="130">
+<Text id="259"><i>gsdlassocfile</i></Text>
+</th>
+<th width="400">
+<Text id="260">Ð€Ð°Ð¹Ð», ÑÐ²ÑÐ·Ð°ÐœÐœÑÐ¹ Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÑÐ°Ð¹Ð» ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="261">ÐÑÐºÑÑÐ²Ð°ÑÑÐžÐ¹ ÑÑÐ³ <i>&lt;Section&gt;</i> ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ ÐœÐ°ÑÐ°Ð»ÐŸ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, Ð°Ð° Ð·Ð°ÐºÑÑÐ²Ð°ÑÑÐžÐ¹ ÑÑÐ³ <i>&lt;/Section&gt;</i> - ÐºÐŸÐœÐµÑ ÑÐ°Ð·ÐŽÐµÐ»Ð°. ÐÐ° ÐºÐ°Ð¶ÐŽÑÐŒ ÑÑÐ³ÐŸÐŒ <i>&lt;Section&gt;</i> ÑÐ»ÐµÐŽÑÐµÑ ÑÐ°Ð·ÐŽÐµÐ» <i>&lt;Description&gt;</i>. Ð Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐŽÐ°ÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð° ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ ÑÐ»ÐµÐŒÐµÐœÑÑ <i>&lt;Metadata&gt;</i>. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ²ÑÐ·Ð°ÐœÑ Ñ ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÑÐŒÐž ÑÐ°Ð·ÐŽÐµÐ»Ð°ÐŒÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÐžÐ· ÐœÐžÑ
+ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐžÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÐ°ÐºÐžÑ
+ ÐºÐ°Ðº <i>&lt;Ð¢ÐšÐµ&gt;</i>. ÐÐ²Ð° Ð·ÐœÐ°ÑÐµÐœÐžÑ Ð°ÑÑÐžÐ±ÑÑÐ° name Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="greenstone_archive_format_values"/> Ðž ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÐŸ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°ÐœÑ Greenstone; Ð²ÑÐµ ÐŸÑÑÐ°Ð»ÑÐœÑÐµ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑÑ ÑÐŸÐ±ÐŸÐ¹ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, Ð¿ÑÐžÐ»Ð°Ð³Ð°ÐµÐŒÑÐµ Ðº ÐŽÐ°ÐœÐœÐŸÐŒÑ ÑÐ°Ð·ÐŽÐµÐ»Ñ. </Text>
+<Text id="262">Ð ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐ°Ð·Ð±ÐžÑÑ ÐœÐ° ÐŸÑÐŽÐµÐ»ÑÐœÑÐµ ÑÑÑÐ°ÐœÐžÑÑ. ÐÐœÐž ÐŸÐ·ÐœÐ°ÑÐµÐœÑ ÐºÐ°Ðº ÑÐ°Ð·ÐŽÐµÐ»Ñ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐºÐœÐžÐ³Ð° ÐŒÐŸÐ¶ÐµÑ ÐžÐŒÐµÑÑ ÑÐ°Ð·ÐŽÐµÐ»Ñ Ð¿ÐµÑÐ²ÐŸÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑ Ð³Ð»Ð°Ð²Ð°ÐŒ, Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ "ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ²", ÐºÐŸÑÐŸÑÑÐµ ÑÐ°ÐºÑÐžÑÐµÑÐºÐž ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑ ÐŸÑÐŽÐµÐ»ÑÐœÑÐŒ ÑÑÑÐ°ÐœÐžÑÐ°ÐŒ Ð³Ð»Ð°Ð²Ñ.</Text>
+<Subsection id="document_metadata">
+<Title>
+<Text id="263">ÐÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°</Text>
+</Title>
+<Content>
+<Text id="264">ÐÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸÐ¿ÐžÑÐ°ÑÐµÐ»ÑÐœÐŸÐ³ÐŸ Ñ
+Ð°ÑÐ°ÐºÑÐµÑÐ°, ÑÐ°ÐºÑÑ ÐºÐ°Ðº ÐŽÐ°ÐœÐœÑÐµ ÐŸÐ± Ð°Ð²ÑÐŸÑÐµ, Ð·Ð°Ð³Ð»Ð°Ð²ÐžÐµ, ÐŽÐ°ÑÑ, ÐºÐ»ÑÑÐµÐ²ÑÐµ ÑÐ»ÐŸÐ²Ð° Ðž Ñ.ÐŽ., ÐºÐ°ÑÐ°ÑÑÑÑÑÑ ÐºÐŸÐœÐºÑÐµÑÐœÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð, ÐºÐ°Ðº Ð±ÑÐ»ÐŸ ÑÐ¶Ðµ ÑÐºÐ°Ð·Ð°ÐœÐŸ Ð²ÑÑÐµ, ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ñ
+ÑÐ°ÐœÑÑÑÑ Ð²ÐŒÐµÑÑÐµ Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ. ÐÐŸÑÐŒÐŸÑÑÐµÐ² ÐœÐ° ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="greenstone_archive_format"/>, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ²ÐžÐŽÐµÑÑ, ÑÑÐŸ ÑÑÐ³ &lt;ÐÐµÐ³Ð°Ð¹?Ð°Ð³Ð°&gt; ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÑÐžÐ¿Ð° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðž Ð¿ÑÐžÑÐ²Ð°ÐžÐ²Ð°ÐµÑ ÐžÐŒ Ð·ÐœÐ°ÑÐµÐœÐžÐµ. ÐÐ±ÑÐ°ÑÐžÐŒÑÑ ÐŽÐ»Ñ Ð¿ÑÐžÐŒÐµÑÐ° Ðº ÑÑÑÐŸÐºÐµ &lt;Metadataname='"Etle "&gt;First and only chap-ter&lt;/Metadata&gt; ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="greenstone_archive_format_1"/> - Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÑÐ²Ð»ÑÐµÑÑÑ ÑÐ°ÑÑÑÑ ÑÐ²ÑÐ·Ð°ÐœÐœÑÑ
+ Ñ ÐœÐžÐŒ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÑÐžÐ¿ÐŸÐ² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ð±ÑÐ» ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ðœ Dublin Core metadata standard (Dublin Core, 2001, Weibel, 1999; Thiele, 1997).</Text>
+<Text id="265">Ð¢Ð°Ð±Ð»ÐžÑÐ° <CrossRef target="Table" ref="dublin_core_metadata_standard"/> ÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÑÐµÑ, ÐºÐ°ÐºÐžÐµ ÐžÐ· ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ
+ ÑÐžÐ¿ÐŸÐ², ÐŸÑÐŒÐµÑÐµÐœÐœÑÐµ Ð·Ð²ÐµÐ·ÐŽÐŸÑÐºÐ°ÐŒÐž, ÐŽÐŸÑÑÑÐ¿ÐœÑ ÑÐµÐ³ÐŸÐŽÐœÑ Ðº ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÐœÐ° Ð²ÐµÐ±-ÑÐ°Ð¹ÑÐµ New Zealand Digital Library. ÐÑÐ»Ðž ÐœÐµÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ð¿ÐŸÐŽÐŸÐ±ÑÐ°ÑÑ ÑÐžÐ¿, ÑÐŸÑÐœÐŸ ÐŸÐ¿ÐžÑÑÐ²Ð°ÑÑÐžÐ¹ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÑÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÑÑÐ³ÐŸÐ¹ ÑÐžÐ¿, ÐœÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐ¹ Ð² Dublin Core metadata standard. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð² ÐŽÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐŸÐŽÐµÑÐ¶ÐžÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ how to Ðž Magazine.</Text>
+<Table id="dublin_core_metadata_standard">
+<Title>
+<Text id="266">Dublin Core metadata standard</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="133">
+<Text id="267"><b>ÐÐŒÑ</b></Text>
+</th>
+<th width="94">
+<Text id="268"><b>ÐÐŸÐŽÑÑÐ³ <br/> ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</b></Text>
+</th>
+<th width="305">
+<Text id="269"><b>ÐÐ¿ÐžÑÐ°ÐœÐžÐµ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="270">*Title</Text>
+</th>
+<th width="94">
+<Text id="271">Title</Text>
+</th>
+<th width="305">
+<Text id="272">ÐÐŒÑ ÑÐµÑÑÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="273">*Creator</Text>
+</th>
+<th width="94">
+<Text id="274"><i>Creator</i></Text>
+</th>
+<th width="305">
+<Text id="275">ÐÐžÑÐŸ, ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸÐµ Ð·Ð° ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ ÑÐµÑÑÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="276">*Subject and keywords</Text>
+</th>
+<th width="94">
+<Text id="277"><i>Subject</i></Text>
+</th>
+<th width="305">
+<Text id="278">Ð¢ÐµÐŒÐ° ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ ÑÐµÑÑÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="279">*Description</Text>
+</th>
+<th width="94">
+<Text id="280"><i>Description</i></Text>
+</th>
+<th width="305">
+<Text id="281">ÐÐ¿ÐžÑÐ°ÐœÐžÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÑÐµÑÑÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="282">*Publisher</Text>
+</th>
+<th width="94">
+<Text id="283"><i>Publisher</i></Text>
+</th>
+<th width="305">
+<Text id="284">ÐÐžÑÐŸ, ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸÐµ Ð·Ð° ÐŽÐŸÑÑÑÐ¿ Ðº ÑÐµÑÑÑÑÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="285">Contributor</Text>
+</th>
+<th width="94">
+<Text id="286"><i>Contributor</i></Text>
+</th>
+<th width="305">
+<Text id="287">ÐÐžÑÐŸ, ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸÐµ Ð·Ð° Ð¿ÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ ÑÐµÑÑÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="288">*Date</Text>
+</th>
+<th width="94">
+<Text id="289"><i>Date</i></Text>
+</th>
+<th width="305">
+<Text id="290">ÐÐ°ÑÐ° Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐž ÑÐµÑÑÑÑÐ°, Ð»ÐžÐ±ÐŸ ÐŽÑÑÐ³Ð°Ñ Ð²Ð°Ð¶ÐœÐ°Ñ ÐŽÐ°ÑÐ°, ÑÐ²ÑÐ·Ð°ÐœÐœÐ°Ñ Ñ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÑÐŒ ÑÐµÑÑÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="291">Resource type</Text>
+</th>
+<th width="94">
+<Text id="292"><i>Type</i></Text>
+</th>
+<th width="305">
+<Text id="293">Ð¥Ð°ÑÐ°ÐºÑÐµÑ ÐžÐ»Ðž Ð¶Ð°ÐœÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ ÑÐµÑÑÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="294">Format</Text>
+</th>
+<th width="94">
+<Text id="295"><i>Format</i></Text>
+</th>
+<th width="305">
+<Text id="296">Ð€ÐžÐ·ÐžÑÐµÑÐºÐŸÐµ ÐžÐ»Ðž ÑÐžÑÑÐŸÐ²ÐŸÐµ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÑÐµÑÑÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="297">*Resource identifier</Text>
+</th>
+<th width="94">
+<Text id="298"><i>Identifier</i></Text>
+</th>
+<th width="305">
+<Text id="299">ÐÐŽÐœÐŸÐ·ÐœÐ°ÑÐœÐ°Ñ ÑÑÑÐ»ÐºÐ° ÐœÐ° ÑÐµÑÑÑÑ ÑÑÐŸ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑ ÐŸÐ±ÑÐµÐºÑÐ° ÐžÐ»Ðž OID</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="300">*Source</Text>
+</th>
+<th width="94">
+<Text id="301"><i>Source</i></Text>
+</th>
+<th width="305">
+<Text id="302">Ð¡ÑÑÐ»ÐºÐ° ÐœÐ° ÐžÑÑÐŸÑÐœÐžÐº, ÐžÐ· ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ Ð±ÑÐ» Ð¿ÐŸÐ»ÑÑÐµÐœ ÑÐµÑÑÑÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="303">*Language</Text>
+</th>
+<th width="94">
+<Text id="304"><i>Language</i></Text>
+</th>
+<th width="305">
+<Text id="305">Ð¯Ð·ÑÐº ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ ÑÐµÑÑÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="306">Relation</Text>
+</th>
+<th width="94">
+<Text id="307"><i>Relation</i></Text>
+</th>
+<th width="305">
+<Text id="308">Ð¡ÑÑÐ»ÐºÐ° ÐœÐ° ÑÐ²ÑÐ·ÐœÑÐ¹ ÑÐµÑÑÑÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="309">*Coverage</Text>
+</th>
+<th width="94">
+<Text id="310"><i>Coverage</i></Text>
+</th>
+<th width="305">
+<Text id="311">ÐÐ±Ð»Ð°ÑÑÑ ÐŸÑ
+Ð²Ð°ÑÐ° ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ ÑÐµÑÑÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="133">
+<Text id="312">Rights</Text>
+</th>
+<th width="94">
+<Text id="313"><i>Rights</i></Text>
+</th>
+<th width="305">
+<Text id="314">ÐÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ Ð¿ÑÐ°Ð²Ðµ Ð²Ð»Ð°ÐŽÐµÐœÐžÑÐž ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœÐžÑ ÑÐµÑÑÑÑÐ° management</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="inside_greenstone_archive_documents">
+<Title>
+<Text id="315">Inside Greenstone archive documents</Text>
+</Title>
+<Content>
+<Text id="316">Within a single document, the Greenstone archive format imposes a limited amount of structure. Documents are divided into paragraphs. They can be split hierarchically into sections and subsections; these may be nested to any depth. Each document has an associated Object Identifier or OIDâthese are extended to identify sections and subsections by appending section and subsection numbers, separated by periods, to the document's OID. For example, subsection 3 of section 2 of document HASHa7 is referred to as HASHa7.2.3.</Text>
+<Text id="317">When you read a book in a Greenstone collection, the section hierarchy is manifested in the table of contents of the book. For example, books in the Demo collection have a hierarchical table of contents showing chapters, sections, and subsections, as illustrated in Figure <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection"/>. Documents in the Computer Science Technical Reports collection do not have a hierarchical subsection structure, but each document is split into pages and you can browse around the pages of a retrieved document. Chapters, sections, subsections, and pages are all implemented simply as âsectionsâ within the document.</Text>
+<Figure id="hierarchical_structure_in_the_demo_collection">
+<Title>
+<Text id="318">ÐÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐ°Ñ ÑÑÑÑÐºÑÑÑÐ° ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+<SubTitle>
+<Text id="318a">(a)</Text>
+</SubTitle>
+</Title>
+<File width="373" height="251" url="images/Dev_Fig_015a.gif"/>
+</Figure>
+<Figure id="hierarchical_structure_in_the_demo_collection_1">
+<Title>
+<Text id="318b">ÐÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐ°Ñ ÑÑÑÑÐºÑÑÑÐ° ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+<SubTitle>
+<Text id="318c">(b)</Text>
+</SubTitle>
+</Title>
+<File width="373" height="251" url="images/Dev_Fig_015b.gif"/>
+</Figure>
+<Text id="319">Ð¡ÑÑÑÐºÑÑÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÑÐ°ÐºÐ¶Ðµ ÐžÐœÐŽÐµÐºÑÐžÑÑÐµÑÑÑ Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ°. ÐÐŽÐµÑÑ ÑÑÑÐµÑÑÐ²ÑÐµÑ 3 ÐŽÐŸÐ¿ÑÑÑÐžÐŒÑÑ
+ ÑÑÐŸÐ²ÐœÑ ÐžÐœÐŽÐµÐºÑÐ°ÑÐžÐž: <i>document</i>, <i>section</i> <i>^paragraph</i>, Ñ
+ÐŸÑÑ Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ðž ÐœÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ Ð²ÑÐµ ÑÑÐž ÑÑÐŸÐ²ÐœÑ ÐŽÐ»Ñ ÐžÐœÐŽÐµÐºÑÐ°ÑÐžÐž. ÐÐœÐŽÐµÐºÑ document ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð¿ÐŸÐ»ÐœÑÐ¹ ÑÐµÐºÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° - Ð²Ñ Ð¿ÐŸÐ»ÑÐ·ÑÐµÑÐµÑÑ ÐžÐŒ ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ° Ð²ÑÐµÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ ÐœÐ°Ð±ÐŸÑ ÑÐ»ÐŸÐ² (ÑÐ»ÐŸÐ²Ð° ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ°ÑÑÐµÑÐœÑ Ð¿ÐŸ Ð²ÑÐµÐŒÑ ÑÐµÐºÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°). ÐÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÐžÐœÐŽÐµÐºÑÐ° secÂ¬tion ÐžÐœÐŽÐµÐºÑÐžÑÑÐµÑÑÑ ÐºÐ°Ð¶ÐŽÐ°Ñ Ð¿ÐŸÑÑÐžÑ ÑÐµÐºÑÑÐ° ÐŸÑ ÐŸÐŽÐœÐŸÐ³ÐŸ ÑÑÐ³Ð° &lt;Section&gt; ÐŽÐŸ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÑ ÑÐ»ÐµÐŽÑÑÑÐµÐ³ÐŸ ÑÑÐ³Ð° &lt;Section&gt;. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, Ð³Ð»Ð°Ð²Ð°, ÑÑÐ°Ð·Ñ Ð¶Ðµ ÐœÐ°ÑÐžÐœÐ°ÑÑÐ°ÑÑÑ Ñ ÐœÐŸÐ²ÐŸÐ³ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð°, ÑÐŸÐ·ÐŽÐ°ÑÑ Ð¿ÑÑÑÐŸÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð¿ÑÐž ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐž. Ð Ð°Ð·ÐŽÐµÐ»Ñ Ðž Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»Ñ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÑÑÑÑ Ð¿ÐŸÐŽÐŸÐ±ÐœÑÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ: ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐ°Ñ ÑÑÑÑÐºÑÑÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÑÐ³Ð»Ð°Ð¶ÐžÐ²Ð°ÐµÑÑÑ Ñ ÑÐµÐ»ÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÑ
+ ÐžÐœÐŽÐµÐºÑÐŸÐ². ÐÑÐž ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐœÐ° ÑÑÐŸÐ²ÐœÐµ Ð¿Ð°ÑÐ°Ð³ÑÐ°ÑÐŸÐ² ÐºÐ°Ð¶ÐŽÑÐ¹ Ð¿Ð°ÑÐ°Ð³ÑÐ°Ñ ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÐµÑÑÑ ÐºÐ°Ðº ÑÐ°ÐŒÐŸÑÑÐŸÑÑÐµÐ»ÑÐœÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ, ÑÑÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð² ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÐµÐŒ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐžÑ Ð±ÐŸÐ»ÐµÐµ ÑÑÐŸÐºÑÑÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐ³ÐŸ Ð¿ÐŸÐžÑÐºÐ°. </Text>
+<Text id="320">ÐÑÐ¿Ð°ÐŽÐ°ÑÑÐµÐµ ÐŒÐµÐœÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection_1"/> ÐœÐ°Ð³Ð»ÑÐŽÐœÐŸ ÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÑÐµÑ Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÐµ ÐžÐœÐŽÐµÐºÑÑ ÐŽÐ»Ñ ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. "Chapters" Ðž "section titles" -Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑÑ ÑÐŸÐ±ÐŸÐ¹ ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐœÐ° ÑÑÐŸÐ²ÐœÐµ ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ², ÑÐŸÐ³ÐŽÐ° ÐºÐ°Ðº "entire books" - ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐœÐ° ÑÑÐŸÐ²ÐœÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð»ÑÐ±ÐŸÐ³ÐŸ Ð²ÐžÐŽÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐŸÑÑÑÐµÑÑÐ²Ð»ÐµÐœÐŸ ÑÐ°Ðº Ð¶Ðµ, ÐºÐ°Ðº ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐµÐºÑÑÐ°. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÑÑ ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐžÐœÐŽÐµÐºÑÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ² ÑÐ°Ð·ÐŽÐµÐ»Ð°, ÑÑÐŸ Ðž Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="hierarchical_structure_in_the_demo_collection_1"/>.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="configuration_file">
+<Title>
+<Text id="321">Ð€Ð°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="322">Ð€Ð°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑ ÑÑÑÑÐºÑÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐœÐ°ÑÑÑÐŸÐžÑÑ ÐµÐµ Ð²ÐœÐµÑÐœÐžÐ¹ Ð²ÐžÐŽ, Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ðž ÐžÑ
+ Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐž. ÐÑÐŸÑÑÐŸÐž ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐŸÐ·ÐŽÐ°ÐµÑÑÑ, ÐºÐŸÐ³ÐŽÐ° Ð²Ñ Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑÐµ mkcol.pl, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð·Ð°Ð¿ÐžÑÑ ÐŽÐ»Ñ Ð°ÐŽÑÐµÑÐŸÐ² E-mail Ð»ÐžÑ, ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÑÑ
+ Ð·Ð° ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ Ðž Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¡Ð»ÐµÐŽÑÐµÑ Ð¿ÐŸÐŒÐœÐžÑÑ, ÑÑÐŸ ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° creator ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÐžÐœÑÐŽÐžÑÐµÐ»ÑÐœÑÐŒ, ÐœÐŸ ÐµÑÐ»Ðž Ð²Ñ ÐŸÑÐŽÐµÐ»ÑÐœÐŸ ÐœÐµ ÐŸÐ³ÐŸÐ²Ð°ÑÐžÐ²Ð°ÐµÑÐµ, ÑÐŸ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐžÐ· ÑÑÐŸÐ³ÐŸ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð±ÑÐŽÐµÑ Ð¿ÐµÑÐµÐœÐµÑÐµÐœÐ° Ð² Ð¿ÐŸÐ»Ðµ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° maintainer.</Text>
+<Table id="items_in_the_collection_configuration_file">
+<Title>
+<Text id="323">Ð­Ð»ÐµÐŒÐµÐœÑÑ ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<CodeLine>creator</CodeLine>
+</th>
+<th width="397">
+<Text id="324">E-mail ÑÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>maintainer</i></CodeLine>
+</th>
+<th width="397">
+<Text id="325">E-mail ÑÐ»ÑÐ¶Ð±Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>public</i></CodeLine>
+</th>
+<th width="397">
+<Text id="326">ÐÐŸÐ»Ð¶ÐœÐ° Ð»Ðž Ð±ÑÑÑ ÐŸÐ¿ÑÐ±Ð»ÐžÐºÐŸÐ²Ð°ÐœÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>beta</i></CodeLine>
+</th>
+<th width="397">
+<Text id="327">Ð¯Ð²Ð»ÑÐµÑÑÑ Ð»Ðž ÐœÐ°ÑÑÐŸÑÑÐ°Ñ Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÑ beta-Ð²ÐµÑÑÐžÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>indexes</i></CodeLine>
+</th>
+<th width="397">
+<Text id="328">Ð¡Ð¿ÐžÑÐŸÐº ÐžÐœÐŽÐµÐºÑÐŸÐ² ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>defaultindex</i></CodeLine>
+</th>
+<th width="397">
+<Text id="329">ÐÐœÐŽÐµÐºÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>subcollection</i></CodeLine>
+</th>
+<th width="397">
+<Text id="330">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐŸÑÐœÐŸÐ²Ð°ÐœÐœÑÑ ÐœÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>indexsubcollections</i></CodeLine>
+</th>
+<th width="397">
+<Text id="331">Ð£ÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐŽÐ»Ñ ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>defaultsubcollection</i></CodeLine>
+</th>
+<th width="397">
+<Text id="332">ÐÐœÐŽÐµÐºÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐŽÐ»Ñ Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>languages</i></CodeLine>
+</th>
+<th width="397">
+<Text id="333">Ð¡Ð¿ÐžÑÐŸÐº ÑÐ·ÑÐºÐŸÐ² ÐŽÐ»Ñ ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>defaultlanguage</i></CodeLine>
+</th>
+<th width="397">
+<Text id="334">Ð¯Ð·ÑÐº ÐŽÐ»Ñ ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐœÑÐ¹ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>collectionmeta</i></CodeLine>
+</th>
+<th width="397">
+<Text id="335">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐœÐ° ÑÑÐŸÐ²ÐœÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>plugin</i></CodeLine>
+</th>
+<th width="397">
+<Text id="336">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ, ÑÑÐ°ÑÑÐ²ÑÑÑÐžÐµ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>format</i></CodeLine>
+</th>
+<th width="397">
+<Text id="337">Ð¡ÑÑÐŸÐºÐŸÐ²ÑÐ¹ ÑÐŸÑÐŒÐ°Ñ (ÐŸÐ±ÑÑÑÐœÐµÐœÐžÐµ ÑÐ»ÐµÐŽÑÐµÑ)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>classify</i></CodeLine>
+</th>
+<th width="397">
+<Text id="338">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="339">ÐÐ°Ð¶ÐŽÐ°Ñ ÑÑÑÐŸÐºÐ° ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÐŸ ÑÑÑÐµÑÑÐ²Ñ ÑÐ²Ð»ÑÐµÑÑÑ Ð¿Ð°ÑÐŸÐ¹ "Ð°ÑÑÐžÐ±ÑÑ, Ð·ÐœÐ°ÑÐµÐœÐžÐµ". ÐÐ°Ð¶ÐŽÑÐ¹ Ð°ÑÑÐžÐ±ÑÑ ÐœÐµÑÐµÑ ÑÐ°ÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÑÐŸ, ÐºÐ°Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐŽÐŸÐ»Ð¶ÐœÑ Ð²ÑÐ³Ð»ÑÐŽÐµÑÑ ÐžÐ»Ðž ÐºÐ°Ðº ÐŸÐœÐž ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÐœÑ. Ð ÑÐ°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="items_in_the_collection_configuration_file"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÑÐ»ÐµÐŒÐµÐœÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ Ð²ÐºÐ»ÑÑÐµÐœÑ Ð² ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ðž ÐŽÐ»Ñ ÑÐµÐ³ÐŸ ÐŸÐœÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ. Ð¢Ð°ÐºÐžÐŒ Ð¶Ðµ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð²ÑÐµ ÐŸÐ¿ÑÐžÐž ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž ÐŽÐ»Ñ import.pl Ðž buildcol.pl - ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, Ð¿ÑÐž Ð¿ÑÐŸÑÑÐµÐœÐžÐž no_text true ÐŽÐ»Ñ ÐŸÐ¿ÑÐžÐž buildcol.pl Ð±ÑÐŽÐµÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ Ð°ÑÑÐžÐ±ÑÑ no_text.</Text>
+<Text id="340">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÐºÑÐžÐ¿ÑÐ° mkcol.pl, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÐŸÐ³ÐŸ Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="collection_configuration_file_created_by_mkcd"/>, ÑÐ²Ð»ÑÐµÑÑÑ ÐŸÑÐµÐœÑ Ð¿ÑÐŸÑÑÑÐŒ Ðž ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÐ¹ ÐŒÐžÐœÐžÐŒÑÐŒ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž. Ð¡ÑÑÐŸÐºÐž 1 Ðž 2 ÑÐ²Ð»ÑÑÑÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÑÐŒÐž Ð°ÑÑÐžÐ±ÑÑÐ° creator, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÐŒÐž Ð² ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ ÑÐ°Ð±ÐŸÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ mkcol.pl, Ðž ÑÐŸÐŽÐµÑÐ¶Ð°Ñ Ð°ÐŽÑÐµÑÐ° ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ Ð»ÐžÑ, ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÑÑ
+ Ð·Ð° ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ Ðž ÐœÐ°Ð¿ÐŸÐ»ÐœÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐœÐµ ÐŸÐ±ÑÐ·Ð°ÑÐµÐ»ÑÐœÐŸ ÐŸÐŽÐžÐœ Ðž ÑÐŸÑ Ð¶Ðµ ÑÐµÐ»ÐŸÐ²ÐµÐº).</Text>
+<Table id="collection_configuration_file_created_by_mkcd">
+<Title>
+<Text id="341">Ð€Ð°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»ÐµÐºÑÐžÐž, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÐ¹ <i>mkcd.pl</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="342"><b>ÐÑÑÐžÐ±ÑÑ</b></Text>
+</th>
+<th width="265">
+<Text id="343"><b>ÐÐœÐ°ÑÐµÐœÐžÐµ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>1</CodeLine>
+</th>
+<th width="132">
+<CodeLine>creator</CodeLine>
+</th>
+<th width="265">
+<Text id="344">username@email.com</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>2</CodeLine>
+</th>
+<th width="132">
+<CodeLine>maintainer</CodeLine>
+</th>
+<th width="265">
+<Text id="345">username@email.com</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>3</CodeLine>
+</th>
+<th width="132">
+<CodeLine>public</CodeLine>
+</th>
+<th width="265">
+<Text id="346">True</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>4</CodeLine>
+</th>
+<th width="132">
+<CodeLine>beta</CodeLine>
+</th>
+<th width="265">
+<Text id="347">True</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>5</CodeLine>
+</th>
+<th width="132">
+<CodeLine>indexes</CodeLine>
+</th>
+<th width="265">
+<Text id="348">document:text</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>6</CodeLine>
+</th>
+<th width="132">
+<CodeLine>defaultindex</CodeLine>
+</th>
+<th width="265">
+<Text id="349">document:text</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>7</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="350">ZIPPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>8</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="351">GAPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>9</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="352">TextPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>10</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="353">HTMLPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>11</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="354">EMAILPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>12</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="355">ArcPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>13</CodeLine>
+</th>
+<th width="132">
+<CodeLine>plugin</CodeLine>
+</th>
+<th width="265">
+<Text id="356">RecPlug</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>14</CodeLine>
+</th>
+<th width="132">
+<CodeLine>classify</CodeLine>
+</th>
+<th width="265">
+<Text id="357">AZList metadata Title</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>15</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="358">collectionname       "sample collection"</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>16</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="359">iconcollection       ""</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>17</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="360">collectionextra     ""</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine>18</CodeLine>
+</th>
+<th width="132">
+<CodeLine>collectionmeta</CodeLine>
+</th>
+<th width="265">
+<Text id="361">.document:text     "documents"</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="362">Ð¡ÑÑÐŸÐºÐ° 3 ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÑÐŸÑ ÑÐ°ÐºÑ, Ð±ÑÐŽÐµÑ Ð»Ðž ÐŽÐ°ÐœÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð¿ÐŸÑÐ»Ðµ ÐµÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŽÐŸÑÑÑÐ¿ÐœÐ° ÑÐžÑÐŸÐºÐŸÐŒÑ ÐºÑÑÐ³Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹, Ðž Ð¿ÑÐžÐœÐžÐŒÐ°ÐµÑ 2 Ð·ÐœÐ°ÑÐµÐœÐžÑ: true (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð±ÑÐŽÐµÑ ÐŽÐŸÑÑÑÐ¿ÐœÐ° ÐŽÐ»Ñ Ð¿ÑÐ±Ð»ÐžÑÐœÐŸÐ³ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ) ÐžÐ»Ðž false (ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ ÐœÐµ Ð±ÑÐŽÐµÑ). ÐÐŸÑÐ»ÐµÐŽÐœÐµÐµ ÐŸÐ±ÑÑÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÑÐµÑÑÐŸÐ²ÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐžÐ»Ðž ÐŽÐ»Ñ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐŽÐ»Ñ ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÐŸÐ³ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ.</Text>
+<Text id="363">Line 5 determines what collection indexes are created at build time: in this example only the document text is to be indexed. Indexes can be constructed at the <i>document</i>, <i>section</i>, and <i>paragraph</i> levels. They can contain the material in <i>text</i>, or in any metadataâmost commonly <i>Title</i>. The form used to specify an index is <i>level:data</i>. For example, to include an index of section titles as well, you should change line 5 to <i>indexes document:text section:Title</i>. More than one type of data can be included in the same index by separating the data types with commas. For example, to create a section-level index of titles, text and dates, the line should read <i>indexes section:text,Title,Date.</i> The default index defined in line 6 is the default to be used on the collection's search page.</Text>
+<Text id="364">Lines 7â13 specify which plugins to use when converting documents to the Greenstone archive format and when building collections from archive files. Section <CrossRef target="Section" ref="plugins"/> gives information about what plugins are available. The order in which plugins are listed is the order in which they are tried on each document, and once a plugin that is able to process a document is found, no more are tried.</Text>
+<Text id="365">Line 14 specifies that an alphabetic list of titles is to be created for browsing purposes. Browsing structures are constructed by âclassifiersâ. Section <CrossRef target="Section" ref="classifiers"/> gives information about classifiers and what they can do.</Text>
+<Text id="366">Lines 15â18 are used to specify collection-level metadata. Specified through <i>collectionname</i>, the long form of the name is used as the collection's âtitleâ for the web browser. The <i>collectionicon</i> entry gives the URL of the collection's icon. If an index is specified (as in line 18), the string following is displayed as the name of that index on the collection's search page. ÐÐ°ÐžÐ±ÐŸÐ»ÐµÐµ Ð²Ð°Ð¶ÐœÐŸÐ¹ ÑÐ°ÑÑÑÑ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐ° ÑÑÐŸÐ²ÐœÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÑÐ²Ð»ÑÐµÑÑÑ collectionextra, ÐºÐŸÑÐŸÑÐ°Ñ ÐŽÐ°ÐµÑ ÑÐµÐºÑÑ ÑÐ°Ð·Ð²ÐµÑÐœÑÑÐŸÐ³ÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð·Ð°ÐºÐ»ÑÑÐµÐœÐœÑÐ¹ Ð² ÐŽÐ²ÐŸÐ¹ÐœÑÐµ ÐºÐ°Ð²ÑÑÐºÐž. Ð­ÑÐŸÑ ÑÐµÐºÑÑ Ð±ÑÐŽÐµÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÑÑÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÐŽÐ»Ñ ÑÑÑÐ°ÐœÐžÑÑ "About this collection" (Ð ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž). ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ Ð²Ð°ÑÐžÐ°ÐœÑÑ collectionextra ÐŽÐ»Ñ ÐŒÑÐ»ÑÑÐžÑÐ·ÑÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°, Ð¿ÑÑÐµÐŒ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÑ ÑÐ·ÑÐºÐŸÐ²ÐŸÐ³ÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ Ð² ÐºÐ²Ð°ÐŽÑÐ°ÑÐœÑÑ
+ ÑÐºÐŸÐ±ÐºÐ°Ñ
+. ÐÐ°Ð¿ÑÐžÐŒÐµÑ,</Text>
+<Indented>
+<Text id="367">collectionmeta collectionextra "collection description"</Text>
+</Indented>
+<Indented>
+<Text id="368">collectionmeta collectionextra [l=fr] "description in French"</Text>
+</Indented>
+<Indented>
+<Text id="369">collectionmeta collectionextra [l=mi] "description in Maori"</Text>
+</Indented>
+<Text id="370">ÐÑÐ»Ðž ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ ÑÐ·ÑÐº ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° "fr" ÐžÐ»Ðž "mi", ÑÐŸ Ð±ÑÐŽÐµÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐ°Ñ Ð²ÐµÑÑÐžÑ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ. ÐÐ»Ñ ÐŽÑÑÐ³ÐžÑ
+ ÑÐ·ÑÐºÐŸÐ² Ð¿ÐŸÑÐ²ÐžÑÑÑ Ð²ÐµÑÑÐžÑ, Ð·Ð°ÐŽÐ°ÐœÐœÐ°Ñ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ.</Text>
+<Text id="371">Ð­ÑÐŸÑ Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐœÐµ Ð²ÐºÐ»ÑÑÐ°ÑÑÐžÐ¹ ÐœÐž Ð¿ÑÐžÐŒÐµÑÐŸÐ² ÑÑÑÐŸÐº ÑÐŸÑÐŒÐ°ÑÐ°, ÐœÐž Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐœÐž ÑÑÐµÐŽÑÑÐ² ÑÐ·ÑÐºÐ°, Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐµÐŒÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐŒ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž. Ð¡ÑÑÐŸÐºÐŸÐ²ÑÐ¹ ÑÐŸÑÐŒÐ°Ñ Ð±ÑÐŽÐµÑ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐµÐµ ÑÐ°ÑÑÐŒÐŸÑÑÐµÐœ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="formatting_greenstone_output"/>, Ð° Ð·ÐŽÐµÑÑ ÐŒÑ ÑÐ°ÑÑÐŒÐŸÑÑÐžÐŒ ÑÐžÑÑÐ°ÑÐžÑ Ñ Ð¿ÐŸÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž Ðž ÑÐ·ÑÐºÐ°ÐŒÐž.</Text>
+<Subsection id="subcollections">
+<Title>
+<Text id="372">ÐÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="373">Greenstone Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐžÐ· ÐœÐžÑ
+ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÑÑ ÐŸÑÐŽÐµÐ»ÑÐœÑÐµ ÐžÐœÐŽÐµÐºÑÑ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð² ÐŸÐŽÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐŒÐµÐµÑÑÑ Ð±ÐŸÐ»ÑÑÐŸÐµ Ð¿ÐŸÐŽÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐžÐŒÐµÐœÑÐµÐŒÑÑ
+ <i>Food and Nutrition Bulletin</i>. ÐÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒ ÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð¿ÑÐžÐŒÐµÑÐ°.</Text>
+<Text id="374">Ð ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐŒÐµÑÑÑÑ 3 ÐžÐœÐŽÐµÐºÑÐ° Ðž Ð²ÑÐµ ÐœÐ° ÑÑÐŸÐ²ÐœÐµ ÑÐ°Ð·ÐŽÐµÐ»Ð°: ÐŸÐŽÐžÐœ - ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð²ÑÐŸÑÐŸÐ¹ - ÐŽÐ»Ñ  <i>Food and Nutrition Bulletin</i> Ðž ÑÑÐµÑÐžÐ¹ - ÐŽÐ»Ñ ÐŸÑÑÐ°Ð»ÑÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÐžÐ¶Ðµ Ð¿ÑÐžÐ²ÐµÐŽÐµÐœÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐµ ÑÑÑÐŸÐºÐž ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<CodeLine>indexes                           section:text</CodeLine>
+<CodeLine>subcollection               fn "Title/^Food and Nutrition Bulletin/i "</CodeLine>
+<CodeLine>subcollection               other "!Title/^Food and Nutrition Bulletin/i "</CodeLine>
+<CodeLine>indexsubcollections fn   other   fn,other</CodeLine>
+<Text id="375">ÐÑÐŸÑÐ°Ñ Ðž ÑÑÐµÑÑÑ ÑÑÑÐŸÐºÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÑÐ»ÐµÐŽÑÑÑÐžÐµ Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž: Ñ ÐžÐŒÐµÐœÐµÐŒ fn, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Food and Nutrition Bulletin, Ðž Ñ ÐžÐŒÐµÐœÐµÐŒ other, Ð² ÐºÐŸÑÐŸÑÐŸÐ¹ ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ ÐŸÑÑÐ°Ð»ÑÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ. Ð¢ÑÐµÑÑÐµ Ð¿ÐŸÐ»Ðµ ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÐµ ÐœÐ° ÑÐ·ÑÐºÐµ Perl, ÐºÐŸÑÐŸÑÐŸÐµ ÐžÐŽÐµÐœÑÐžÑÐžÑÐžÑÑÐµÑ ÑÑÐž Ð¿ÐŸÐŽÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ð°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐžÐ¿Ð° Title: Ð² Ð¿ÐµÑÐ²ÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐžÑÐµÐŒ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž, ÐºÐŸÑÐŸÑÑÐµ ÐœÐ°ÑÐžÐœÐ°ÑÑÑÑ Ñ Food and Nutrition Bulletin , Ð° Ð²ÐŸ Ð²ÑÐŸÑÐŸÐŒ - Ð² ÐºÐŸÑÐŸÑÑÑ
+ ÐŽÐ°ÐœÐœÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐŸÑÑÑÑÑÑÐ²ÑÐµÑ (ÐŸÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° Ð·ÐœÐ°Ðº "!"). ÐÐœÐ°Ðº i Ð² ÐºÐŸÐœÑÐµ ÑÑÑÐŸÐºÐž ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ Ð¿ÑÐž ÑÐ°Ð±ÐŸÑÐµ ÑÑÐžÑ
+ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹ ÑÐµÐ³ÐžÑÑÑ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² ÐœÐµ ÑÑÐžÑÑÐ²Ð°ÐµÑÑÑ. ÐÐŸÐ»Ðµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, Ð² ÐœÐ°ÑÐµÐŒ ÑÐ»ÑÑÐ°Ðµ Title, ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð»ÑÐ±ÑÐŒ ÐŽÐŸÐ¿ÑÑÑÐžÐŒÑÐŒ Ð¿ÐŸÐ»ÐµÐŒ, ÐžÐ»Ðž Filename, ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÐžÐŒ Ð¿ÐµÑÐ²ÐŸÐœÐ°ÑÐ°Ð»ÑÐœÐŸÐŒÑ ÐžÐŒÐµÐœÐž ÑÐ°Ð¹Ð»Ð° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð ÑÐµÑÐ²ÐµÑÑÐŸÐ¹ ÑÑÑÐŸÐºÐµ, indexsubcollections, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑÑÑ ÑÑÐž ÐžÐœÐŽÐµÐºÑÐ°: ÐŸÐŽÐžÐœ - ÐŽÐ»Ñ Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž fn, Ð²ÑÐŸÑÐŸÐ¹ - ÐŽÐ»Ñ Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž other Ðž ÑÑÐµÑÐžÐ¹ - ÐŽÐ»Ñ ÐŸÐ±ÐµÐžÑ
+ Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (Ñ.Ðµ. ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²). ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÑÐŸ, ÑÑÐŸ ÐµÑÐ»Ðž Ð±Ñ ÐŽÐ²Ð° Ð²Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ Ð±ÑÐ»Ðž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ Ð² ÑÑÑÐŸÐºÐµ indexes, ÑÐŸ ÐŸÐ±ÑÐµÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÑ
+ ÐžÐœÐŽÐµÐºÑÐŸÐ² Ð±ÑÐ»ÐŸ Ð±Ñ ÑÐµÑÑÑ, Ð° ÐœÐµ ÑÑÐž.</Text>
+<Text id="376">ÐÑÐ»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐœÐ° ÑÐ°Ð·ÐœÑÑ
+ ÑÐ·ÑÐºÐ°Ñ
+, ÑÐŸ ÐžÐœÐŽÐµÐºÑÑ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ ÐŸÑÐŽÐµÐ»ÑÐœÐŸ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐ·ÑÐºÐ°. Ð¯Ð·ÑÐº ÑÐ²Ð»ÑÐµÑÑÑ ÐžÐœÑÑÑÑÐºÑÐžÐµÐ¹ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+; Language is a metadata statement; Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑÑÑ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž ÑÐŸ ÑÑÐ°ÐœÐŽÐ°ÑÑÐŸÐŒ ISO 639 ÐŽÐ²ÑÑ
+Ð±ÑÐºÐ²ÐµÐœÐœÑÐŒ ÐºÐŸÐŽÐŸÐŒ, ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐ°ÑÑÐžÐŒ ÑÐ·ÑÐº - ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐµÐ¿ - ÑÑÐŸ English (Ð°Ð³Ð»ÐžÐ¹ÑÐºÐžÐ¹), zh - Chinese (ÐºÐžÑÐ°Ð¹ÑÐºÐžÐ¹), Ðž mi - ÑÑÐŸ Maori (ÐŒÐ°ÐŸÑÐž). Ð¢Ð°Ðº ÐºÐ°Ðº Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ ÐœÐ° ÑÑÐŸÐ²ÐœÐµ ÑÐ°Ð·ÐŽÐµÐ»Ð°, ÐŸÑÐŽÐµÐ»ÑÐœÑÐµ ÑÐ°ÑÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÐœÐ° ÑÐ°Ð·ÐœÑÑ
+ ÑÐ·ÑÐºÐ°Ñ
+.</Text>
+<Text id="377">ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐµÑÐ»Ðž ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÑÐŸÐŽÐµÑÐ¶ÐžÑ: ÑÐµÐºÑÑ ÑÐ°Ð·ÐŽÐµÐ»Ð°, Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÑÐ°Ð·ÐŽÐµÐ»Ð°, ÑÐµÐºÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ðž ÐžÐœÐŽÐµÐºÑÑ ÑÐµÐºÑÑÐ° Ð¿Ð°ÑÐ°Ð³ÑÐ°ÑÐ°, ÑÐŸ ÐŽÐ»Ñ Ð°ÐœÐ³Ð»ÐžÐ¹ÑÐºÐŸÐ³ÐŸ, ÐºÐžÑÐ°Ð¹ÑÐºÐŸÐ³ÐŸ Ðž ÑÐ·ÑÐºÐ° ÐŒÐ°ÐŸÑÐž Ð±ÑÐ»Ðž </Text>
+<CodeLine>indexes section:text section:Title document:text paragraph:text</CodeLine>
+<CodeLine>languages en zh mi</CodeLine>
+<Text id="378">Ð±ÑÐ»Ðž Ð±Ñ ÑÐŸÐ·ÐŽÐ°ÐœÑ ÐŽÐ²ÐµÐœÐ°ÐŽÑÐ°ÑÑ ÐžÐœÐŽÐµÐºÑÐŸÐ² Ð² ÑÐµÐ»ÐŸÐŒ. ÐÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐµ ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÑÐŒÐœÐŸÐ¶Ð°ÐµÑ ÑÐžÑÐ»ÐŸ ÐžÐœÐŽÐµÐºÑÐŸÐ². ÐÐŽÐœÐ°ÐºÐŸ, ÑÐ»ÐµÐŽÑÐµÑ Ñ ÐŸÑÑÐŸÑÐŸÐ¶ÐœÐŸÑÑÑÑ ÐŸÑÐœÐŸÑÐžÑÑÑÑ Ðº ÑÐ°Ð·ÐŽÑÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²Ð° ÐžÐœÐŽÐµÐºÑÐŸÐ².</Text>
+<Text id="379">(Ð­ÑÐ° ÐžÐœÐŽÐµÐºÑÐœÐ°Ñ ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÑ ÐŒÐŸÐ³Ð»Ð° Ð±Ñ Ð±ÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐ° Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÑÑÐµÐŽÑÑÐ² subcollection, Ð° ÐœÐµ ÑÑÐµÐŽÑÑÐ²ÐŸ languages. ÐÐŽÐœÐ°ÐºÐŸ, Ð² ÑÐ²ÑÐ·Ðž Ñ ÑÐµÐŒ, ÑÑÐŸ ÑÐžÐœÑÐ°ÐºÑÐžÑ Ð¿ÑÐµÐ¿ÑÑÑÑÐ²ÑÐµÑ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ "Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹", ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ ÐœÐµÐ²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÐŒ ÐŸÑÐŽÐµÐ»ÑÐœÐŸ ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐ·ÑÐº Ð² Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+).</Text>
+</Content>
+</Subsection>
+<Subsection id="cross-collection_searching">
+<Title>
+<Text id="380">ÐÐµÑÐµÐºÑÐµÑÑÐœÑÐ¹ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="381">Greenstone ÐžÐŒÐµÐµÑ ÑÑÐµÐŽÑÑÐ²ÐŸ ÐŽÐ»Ñ "Ð¿ÐµÑÐµÐºÑÐµÑÑÐœÐŸÐ³ÐŸ Ð¿ÐŸÐžÑÐºÐ° Ð¿ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž", ÐºÐŸÑÐŸÑÐŸÐµÐ¹ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒ ÑÑÐ°Ð·Ñ Ñ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÐµÐŒ ÐŸÐ±ÑÐµÐŽÐžÐœÐµÐœÐœÑÑ
+ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ², ÑÐ°Ðº, ÐºÐ°Ðº ÐµÑÐ»Ðž Ð±Ñ Ð²Ñ ÐžÑÐºÐ°Ð»Ðž Ð¿ÐŸ ÐŸÐŽÐœÐŸÐ¹ ÐŸÐ±ÑÐµÐŽÐžÐœÐµÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÐœÐŸ Ð»ÑÐ±ÐŸÐµ Ð¿ÐŸÐŽÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹: Preferences page (ÑÑÑÐ°ÐœÐžÑÐ° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÐ¹) Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐÐ°ÐŒ Ð²ÑÐ±ÐžÑÐ°ÑÑ, ÐºÐ°ÐºÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ Ð²ÐºÐ»ÑÑÐµÐœÑ Ð² Ð¿ÐŸÐžÑÐº.</Text>
+<Text id="382">ÐÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ Ð¿ÐµÑÐµÐºÑÐµÑÑÐœÐŸÐ³ÐŸ Ð¿ÐŸÐžÑÐºÐ° ÐŸÐ³ÐŸÐ²Ð°ÑÐžÐ²Ð°ÐµÑÑÑ ÑÑÑÐŸÐºÐŸÐ¹:</Text>
+<CodeLine>supercollection col _1 col _2 âŠ.</CodeLine>
+<Text id="383">Ð³ÐŽÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð²ÐŸÐ²Ð»ÐµÑÐµÐœÐœÑÐµ Ð² Ð¿ÐŸÐžÑÐº, ÐžÐŒÐµÐœÑÑÑÑÑ col_l, col_2,... Ð¢ÐŸÑÐœÐŸ ÑÐ°ÐºÐ°Ñ Ð¶Ðµ ÑÑÑÐŸÐºÐ° ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ Ðž Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÑÐµÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ Ð¿ÐµÑÐµÐºÑÐµÑÑÐœÐŸÐ³ÐŸ Ð¿ÐŸÐžÑÐºÐ°.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="getting_the_most_out_of_your_documents">
+<Title>
+<Text id="384">ÐÐŸÐ»ÑÑÐµÐœÐžÐµ Ð±ÐŸÐ»ÑÑÐµÐ³ÐŸ ÐŸÑ Ð²Ð°ÑÐžÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="385">ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÑ ÑÐ°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, ÑÑÐŸÐ±Ñ ÑÐ°Ð·Ð³ÑÐ°ÐœÐžÑÐžÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑÑÑÑ Ð² ÐœÐžÑ
+ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒÐž ÑÐ¿ÐŸÑÐŸÐ±Ð°ÐŒÐž ÐŽÐŸÑÑÑÐ¿Ð°. ÐÐ°ÑÑÐŸÑÑÐ°Ñ Ð³Ð»Ð°Ð²Ð° ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ, ÐºÐ°Ðº Greenstone ÐžÐ·Ð²Ð»ÐµÐºÐ°ÐµÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ðž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑ ÐµÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ: Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Section" ref="plugins"/> - ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Section" ref="classifiers"/> - ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ, Ð Ð°Ð·ÐŽÐµÐ»Ñ <CrossRef target="Section" ref="formatting_greenstone_output"/> Ðž <CrossRef target="Section" ref="controlling_the_greenstone_user_interface"/> -ÐžÐœÑÑÑÑÐŒÐµÐœÑÐ°Ð»ÑÐœÑÐµ ÑÑÐµÐŽÑÑÐ²Ð° ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ.</Text>
+<Section id="plugins">
+<Title>
+<Text id="386">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="387">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ Ð°ÐœÐ°Ð»ÐžÐ·ÐžÑÑÑÑ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ðž ÐžÐ·Ð²Ð»ÐµÐºÐ°ÑÑ ÐžÐ· ÐœÐžÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, HTML-Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐºÐŸÐœÐ²ÐµÑÑÐžÑÑÐµÑ HTML-ÑÑÑÐ°ÐœÐžÑÑ Ð² ÑÐŸÑÐŒÐ°Ñ Ð°ÑÑ
+ÐžÐ²Ð° Greenstone Ðž ÐžÐ·Ð²Ð»ÐµÐºÐ°ÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐºÐŸÑÐŸÑÑÐµ ÑÐ²Ð»ÑÑÑÑÑ ÑÐ²ÐœÑÐŒ Ð² ÑÐŸÑÐŒÐ°ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° - ÑÐ°ÐºÐžÐµ, ÐºÐ°Ðº Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž, Ð·Ð°ÐºÐ»ÑÑÐµÐœÐœÑÐµ ÑÐµÐ³Ð°ÐŒÐž <i>&lt;title&gt;&lt;/title&gt;</i>.</Text>
+<Text id="388">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐœÐ°Ð¿ÐžÑÐ°ÐœÑ ÐœÐ° ÑÐ·ÑÐºÐµ Perl. ÐÑÐµ ÐŸÐœÐž Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÑÑ ÐŸÑ ÐŸÑÐœÐŸÐ²ÐœÐŸÐ³ÐŸ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ BasPlug, ÐºÐŸÑÐŸÑÐŸÐµ Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÑ ÐºÐœÐžÐ²ÐµÑÑÐ°Ð»ÑÐœÑÐµ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž, ÑÐ°ÐºÐžÐµ ÐºÐ°Ðº ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐœÐŸÐ²ÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ Ð°ÑÑ
+ÐžÐ²Ð° Greenstone ÐŽÐ»Ñ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐµÐ¹ ÑÐ°Ð±ÐŸÑÑ Ñ ÐœÐžÐŒ, ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° ÐŸÐ±ÑÐµÐºÑÐ° (OID), ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ Ñ
+ÑÐ°ÐœÑÑÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž perllib/plugins.</Text>
+<Text id="389">Ð§ÑÐŸÐ±Ñ ÑÐ·ÐœÐ°ÑÑ Ð±ÐŸÐ»ÑÑÐµ ÐŸ Ð»ÑÐ±ÐŸÐŒ ÐžÐ· Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ <i>pluginfo.pl plugin-name</i> Ð² ÐŸÐ±Ð»Ð°ÑÑÐž ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž. (Ð¡ÐœÐ°ÑÐ°Ð»Ð°, Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ Ð²ÑÐ·Ð²Ð°ÑÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐ¹ ÑÐºÑÐžÐ¿ÑÑ <i>setup</i>, ÐµÑÐ»Ðž Ð²Ñ ÑÑÐŸÐ³ÐŸ ÐœÐµ ÐŽÐµÐ»Ð°Ð»Ðž ÑÐ°ÐœÐµÐµ. ÐÑÐ»Ðž Ð²Ð°ÑÐ° ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÐ°Ñ ÑÐžÑÑÐµÐŒÐ° ÐœÐµ ÐœÐ°ÑÑÑÐŸÐµÐœÐ° ÐœÐ° ÑÐŸ, ÑÑÐŸÐ±Ñ Ð²ÐŸÑÐ¿ÑÐžÐœÐžÐŒÐ°ÑÑ ÑÐ°Ð¹Ð»Ñ Ñ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµÐŒ .Ñl ÐºÐ°Ðº Ð²ÑÐ¿ÐŸÐ»ÐœÐžÐŒÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐœÐ° ÑÐ·ÑÐºÐµ Perl, ÑÐŸ Ð² Windows Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÑÑ <i>perl âS pluginfo.pl plugin-name</i>). Ð ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ ÐœÐ° ÑÐºÑÐ°ÐœÐµ Ð¿ÐŸÑÐ²ÐžÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸÐ± ÐžÐœÑÐµÑÐµÑÑÑÑÐµÐŒ Ð²Ð°Ñ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐž - ÐºÐ°ÐºÐžÐµ ÐŽÐ°ÐœÐœÐŸÐŒÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÑÑÐµÐ±ÑÑÑÑÑ ÑÐ¿ÐµÑÐžÑÐžÑÐœÑÐµ ÐŸÐ¿ÑÐžÐž Ðž ÐºÐ°ÐºÐžÐµ ÐŸÐ±ÑÐžÐµ.</Text>
+<Text id="390">ÐÑ Ð»ÐµÐ³ÐºÐŸ ÐŒÐŸÐ¶ÐµÑÐµ ÐœÐ°Ð¿ÐžÑÐ°ÑÑ ÐœÐŸÐ²ÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐŽÐ»Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÑÐŸÑÐŒÐ°ÑÐŸÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐœÐµ Ð¿ÑÐµÐŽÑÑÐŒÐŸÑÑÐµÐœÐœÑÑ
+ Ð² ÑÑÑÐµÑÑÐ²ÑÑÑÐžÑ
+ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑÑ
+, ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐŸÑÐŸÐ±ÑÐŒÐž ÑÐ¿ÐŸÑÐŸÐ±Ð°ÐŒÐž ÐžÐ»Ðž ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÑ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐœÐŸÐ²ÑÑ
+ Ð²ÐžÐŽÐŸÐ² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+<Subsection id="general_options">
+<Title>
+<Text id="391">ÐÐ±ÑÐžÐµ ÐŸÐ¿ÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="392">Ð Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="options_applicable_to_all_plugins"/> Ð¿ÑÐžÐ²ÐµÐŽÐµÐœÑ ÐŸÐ¿ÑÐžÐž, Ð¿ÑÐžÐœÐžÐŒÐ°ÐµÐŒÑÐµ Ð»ÑÐ±ÑÐŒ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐŒ, Ð¿ÐŸÐ»ÑÑÐµÐœÐœÑÐŒ ÐŸÑ BasPlug.</Text>
+<Table id="options_applicable_to_all_plugins">
+<Title>
+<Text id="393">ÐÐ¿ÑÐžÐž, Ð¿ÑÐžÐŒÐµÐœÑÐµÐŒÑÐµ ÐŽÐ»Ñ Ð²ÑÐµÑ
+ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<CodeLine><i>input_encoding</i></CodeLine>
+</th>
+<th width="397">
+<Text id="394">ÐÐŸÐŽÐžÑÐŸÐ²ÐºÐ° ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÐœÐ°ÑÐµÐœÐžÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÑÐµÑÐžÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ ÐºÐŸÐŽÐžÑÐŸÐ²ÐºÐž ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐœÐŸÐ³ÐŽÐ° Ð¿ÐŸÐ»ÐµÐ·ÐœÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÑÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ, Ñ
+ÐŸÑÑ, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐµÑÐ»Ðž Ð²Ñ ÑÐŸÑÐœÐŸ Ð·ÐœÐ°ÐµÑÐµ, ÑÑÐŸ Ð²ÑÐµ Ð²Ð°ÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ Ð² ASCII, ÑÑÑÐ°ÐœÐŸÐ²ÐºÐ° Ð²Ñ
+ÐŸÐŽÐœÐŸÐ¹ ÐºÐŸÐŽÐžÑÐŸÐ²ÐºÐž  ascii Ð·ÐœÐ°ÑÐžÑÐµÐ»ÑÐœÐŸ ÑÐ²ÐµÐ»ÐžÑÐžÐ²Ð°ÐµÑ ÑÐºÐŸÑÐŸÑÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ° Ðž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð²Ð°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ ÐŽÐŸÐ¿ÑÑÑÐžÐŒÑÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹. ÐÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ ÐžÑ
+ Ð¿ÐŸÐ»ÐœÐŸÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ° Ð²ÐŸÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµÑÑ pluginfo.pl BasPlug.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>default_encoding</i></CodeLine>
+</th>
+<th width="397">
+<Text id="395">ÐÐŸÐŽÐžÑÐŸÐ²ÐºÐ°, ÐºÐŸÑÐŸÑÐ°Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž ÐŽÐ»Ñ ÐŸÐ¿ÑÐžÐž input encoding ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ auto ÐžÐ»Ðž ÐŸÐ±ÐœÐ°ÑÑÐ¶ÐµÐœÑ ÑÐ±ÐŸÐž Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÐºÐŸÐŽÐžÑÐŸÐ²Ð°ÐœÐžÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>process_exp</i></CodeLine>
+</th>
+<th width="397">
+<Text id="396">ÐÐ±ÑÑÐœÐŸÐµ Perl-Ð²ÑÑÐ°Ð¶ÐµÐœÐžÐµ ÐŽÐ»Ñ ÑÐŸÐ³Ð»Ð°ÑÐŸÐ²Ð°ÐœÐžÑ ÐžÐŒÐµÐœ ÑÐ°Ð¹Ð»ÐŸÐ² (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÐŒÐµÑÑÐŸÐœÐ°Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ ÑÐ°Ð¹Ð»ÐŸÐ² Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐŒ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµÐŒ). ÐÐœÐŸ ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÑÐ°Ð¹Ð», ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑÑÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµÐŒ . ÐÐ°Ð¶ÐŽÐŸÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐžÐŒÐµÐµÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ (Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ HTMLPlug - (? i) .html? - Ñ.Ðµ. ÑÐ°Ð¹Ð» Ñ ÑÐ°ÑÐžÑÐµÐœÐžÐµÐŒ .htm ÐžÐ»Ðž .html).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>block_exp</i></CodeLine>
+</th>
+<th width="397">
+<Text id="397">ÐÐ±ÑÑÐœÐŸÐµ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÐµ ÐŽÐ»Ñ ÑÐŸÐ³Ð»Ð°ÑÐŸÐ²Ð°ÐœÐžÑ ÐžÐŒÐµÐœ ÑÐ°Ð¹Ð»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐœÐµ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ Ð¿ÐµÑÐµÐŽÐ°ÐœÑ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐžÐŒ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑÐŒ. Ð­ÑÐŸ ÐŒÐŸÐ¶ÐµÑ Ð¿ÑÐµÐŽÐŸÑÐ²ÑÐ°ÑÐžÑÑ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÐµ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐ¹ ÐŸÐ± ÐŸÑÐžÐ±ÐºÐ°Ñ
+ Ð² ÑÐ°Ð¹Ð»Ð°Ñ
+, ÐºÐŸÑÐŸÑÑÐŒÐž Ð²Ñ ÐœÐµ ÐžÐœÑÐµÑÐµÑÑÐµÑÐµÑÑ. ÐÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐžÐŒÐµÑÑ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÑ Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, HTMLPlug Ð±Ð»ÐŸÐºÐžÑÑÐµÑ ÑÐ°Ð¹Ð»Ñ Ñ ÑÐ°ÑÑÐžÑÐµÐœÐžÑÐŒÐž .gif .jpg .jpeg .png .rtf Ðž .css ÑÐ°ÑÑÐžÑÐµÐœÐžÑÐŒÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>cover_image</i></CodeLine>
+</th>
+<th width="397">
+<Text id="398">ÐÑÐµÑ jpg ÑÐ°Ð¹Ð» (Ñ ÑÐ°ÐºÐžÐŒ Ð¶Ðµ ÐžÐŒÐµÐœÐµÐŒ, ÑÑÐŸ Ðž ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÐŒÑÐ¹ ÑÐ°Ð¹Ð») Ðž ÑÐ²ÑÐ·ÑÐ²Ð°ÐµÑ ÐµÐ³ÐŸ Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŸÐ±Ð»ÐŸÐ¶ÐºÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_acronyms</i></CodeLine>
+</th>
+<th width="397">
+<Text id="399">Extract acronyms from documents and add them as metadata to the corresponding Greenstone archive documents.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>markup_acronyms</i></CodeLine>
+</th>
+<th width="397">
+<Text id="400">ÐÐŸÐ±Ð°Ð²Ð»ÑÐµÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸÐ± Ð°Ð±Ð±ÑÐµÐ²ÐžÐ°ÑÑÑÐµ Ð² ÑÐµÐºÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_language</i></CodeLine>
+</th>
+<th width="397">
+<Text id="401">Identify each document's language and associate it as metadata. Note that this is done automatically if <i>input_encoding</i> is <i>auto</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>default_language</i></CodeLine>
+</th>
+<th width="397">
+<Text id="402">Ð ÑÐ»ÑÑÐ°Ðµ ÑÐ±ÐŸÑ Ð¿ÑÐž Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐŸÐŒ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐž ÑÐ·ÑÐºÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÑÑ ÑÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>first</i></CodeLine>
+</th>
+<th width="397">
+<Text id="403">ÐÐ·Ð²Ð»ÐµÐºÐ°ÐµÑ ÑÑÐ°ÑÑÐŸÐº ÑÐµÐºÑÑÐ°, Ð·Ð°ÐºÐ»ÑÑÐµÐœÐœÑÐ¹ ÐŒÐµÐ¶ÐŽÑ Ð·Ð°Ð¿ÑÑÑÐŒÐž, ÐºÐ°Ðº ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ FirstNNN (ÑÐ°ÑÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð·Ð°ÐŒÐµÐœÑ ÐŽÐ»Ñ Title).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_email</i></CodeLine>
+</th>
+<th width="397">
+<Text id="404">ÐÐ·Ð²Ð»ÐµÐºÐ°ÐµÑ Ð°ÐŽÑÐµÑ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ Ðž ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑ ÐµÐ³ÐŸ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<CodeLine><i>extract_date</i></CodeLine>
+</th>
+<th width="397">
+<Text id="405">ÐÐ·Ð²Ð»ÐµÐºÐ°ÐµÑ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐŽÐ°ÑÑ, ÐºÐ°ÑÐ°ÑÑÐžÐµÑÑ ÐžÑÑÐŸÑÐžÑÐµÑÐºÐžÑ
+ ÑÐŸÐ±ÑÑÐžÐ¹, Ðž ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑ ÐžÑ
+ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Coverage.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="document_processing_plugins">
+<Title>
+<Text id="406">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ Greenstone</Text>
+</Title>
+<Content>
+<Table id="greenstone_plugins">
+<Title>
+<Text id="407">Greenstone plugins</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="60"/>
+<th width="72"/>
+<th width="236">
+<Text id="408"><b>ÐŠÐµÐ»Ñ</b></Text>
+</th>
+<th width="85">
+<Text id="409"><b>Ð¢ÐžÐ¿Ñ ÑÐ°Ð¹Ð»ÐŸÐ²</b></Text>
+</th>
+<th width="76">
+<Text id="410"><b>ÐÐ³ÐœÐŸÑÐžÑÑÐµÐŒÑÐµ ÑÐ°Ð¹Ð»Ñ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="411"><b>ÐÐ±ÑÐžÐµ</b></Text>
+</th>
+<th width="72">
+<Text id="412"><i>ArcPlug</i></Text>
+</th>
+<th width="236">
+<Text id="413">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐºÐ°Ð·Ð°ÐœÐœÑÑ
+ Ð² ÑÐ°Ð¹Ð»Ðµ archives.inf ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ  ÑÐ²ÑÐ·Ðž Ð¿ÑÐŸÑÐµÑÑÐŸÐ² ÐžÐŒÐ¿ÐŸÑÑÐ° Ðž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ. ÐÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ Ð²ÐºÐ»ÑÑÐµÐœ(ÐµÑÐ»Ðž import.pl ÐœÐµ Ð±ÑÐŽÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ).</Text>
+</th>
+<th width="85">
+<Text id="414"><i>â</i></Text>
+</th>
+<th width="76">
+<Text id="415"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="416"><i>RecPlug</i></Text>
+</th>
+<th width="236">
+<Text id="417">ÐÐ±ÑÐ°ÑÐ°ÑÑÑ ÑÐµÑÐµÐ· ÐŽÐžÑÐµÐºÑÐžÐ²ÐœÑÑ ÑÑÑÑÐºÑÑÑÑ, Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ, ÑÐ²Ð»ÑÐµÑÑÑ Ð»Ðž ÐžÐŒÑ ÑÐ°Ð¹Ð»Ð° ÐŽÐžÑÐµÐºÑÐŸÑÐžÐµÐ¹, Ðž ÐµÑÐ»Ðž ÑÐ²Ð»ÑÐµÑÑÑ, ÑÐŸ Ð²ÑÐµ ÑÐ°Ð¹Ð»Ñ ÑÑÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Ð²ÑÑÑÐ°ÐžÐ²Ð°ÑÑÑÑ Ð²ÐœÑÑÑÑ ÐºÐŸÐœÐ²ÐµÐ¹ÐµÑÐœÐŸÐ³ÐŸ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ. ÐÐ°Ð·ÐœÐ°ÑÐ°ÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐµÑÐ»Ðž ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÐŸÐ¿ÑÐžÑ use_metadata_files Ðž Ð¿ÑÐžÑÑÑÑÑÐ²ÑÑÑ ÑÐ°Ð¹Ð»Ñ metadata.xml.</Text>
+</th>
+<th width="85">
+<Text id="418"><i>â</i></Text>
+</th>
+<th width="76">
+<Text id="419"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="420"><i>GAPlug</i></Text>
+</th>
+<th width="236">
+<Text id="421">ÐÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ import.plÑÐ°Ð¹Ð»Ñ Ð°ÑÑ
+ÐžÐ²Ð° Greenstone. ÐÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ Ð²ÐºÐ»ÑÑÐµÐœ (ÐµÑÐ»Ðž import.pl ÐœÐµ Ð±ÑÐŽÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ðœ).</Text>
+</th>
+<th width="85">
+<Text id="422"><i>.xml</i></Text>
+</th>
+<th width="76">
+<Text id="423"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="424">TEXTPlug</Text>
+</th>
+<th width="236">
+<Text id="425">ÐÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÑÐµÐºÑÑ, Ð¿ÐŸÐŒÐµÑÐ°Ñ ÐµÐ³ÐŸ ÐŒÐµÐ¶ÐŽÑ ÑÑÐ³Ð°ÐŒÐž (Ð¿ÑÐµÐŽÑÐŸÑÐŒÐ°ÑÐœÐ°Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐ°).</Text>
+</th>
+<th width="85">
+<Text id="426"><i>.txt, .text</i></Text>
+</th>
+<th width="76">
+<Text id="427"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="428"><i>HTMLPlug</i></Text>
+</th>
+<th width="236">
+<Text id="429">ÐÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ HTML, ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸ Ð¿ÐµÑÐµÐŒÐµÑÐ°Ñ Ð³ÐžÐ¿ÐµÑÑÑÑÐ»ÐºÐž. ÐÑÐ»Ðž ÑÐ²ÑÐ·Ð°ÐœÐœÐ°Ñ Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ ÑÑÑÐ°ÐœÐžÑÐ° ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð²ÐœÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸ Ð²ÑÑÐ°Ð²Ð»ÑÐµÑÑÑ Ð¿ÑÐŸÐŒÐµÐ¶ÑÑÐŸÑÐœÐ°Ñ ÑÑÑÐ°ÐœÐžÑÐ°, Ð¿ÑÐµÐŽÑÐ¿ÑÐµÐ¶ÐŽÐ°ÑÑÐ°Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŸ ÑÐŸÐŒ, ÑÑÐŸ Ð¿ÑÐž Ð¿ÐµÑÐµÑ
+ÐŸÐŽÐµ Ð¿ÐŸ ÑÑÑÐ»ÐºÐµ ÐŸÐœ Ð¿ÐŸÐºÐžÐœÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐ·Ð²Ð»ÐµÐºÐ°ÐµÑ Ð¿ÐŸÐŽÐ³ÐŸÑÐŸÐ²Ð»ÐµÐœÐœÑÐµ ÐŽÐ»Ñ ÐŽÐŸÑÑÑÐ¿Ð° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐ°ÐºÐžÐµ ÐºÐ°Ðº Title</Text>
+</th>
+<th width="85">
+<Text id="430"><i>.htm, .html, .cgi, .php, .asp, .shm, .shtml</i></Text>
+</th>
+<th width="76">
+<Text id="431"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="432"><i>WordPlug</i></Text>
+</th>
+<th width="236">
+<Text id="433">ÐÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Microsoft Word, ÐžÐ·Ð²Ð»ÐµÐºÐ°ÐµÑ ÐŽÐ°ÐœÐœÑÐµ ÐŸÐ± Ð°Ð²ÑÐŸÑÐµ Ðž Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐµ Ðž ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑ ÐŽÐžÐ°Ð³ÑÐ°ÐŒÐŒÑ Ðž ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ Ð² ÐœÐ°ÐŽÐ»ÐµÐ¶Ð°ÑÐžÑ
+ ÐŒÐµÑÑÐ°Ñ
+. ÐÐŸÐœÐ²ÐµÑÑÐžÐŸÐœÐœÑÐµ ÑÑÐžÐ»ÐžÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ ÑÑÐžÐŒ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµÐŒ, ÐžÐœÐŸÐ³ÐŽÐ° ÑÐŸÐ·ÐŽÐ°ÑÑ HTML, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿Ð»ÐŸÑ
+ÐŸ ÐŸÑÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°Ðœ. ÐÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ, ÑÑÐŸÐ±Ñ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐÑ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐ»Ðž ÐŸÑÐžÐ³ÐžÐœÐ°Ð»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÐµÑÐ»Ðž ÑÐŸÑÐŒÐžÑÑÐµÑÐµ ÑÐ²ÐŸÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐ· ÑÐ°Ð¹Ð»ÐŸÐ² WORD. Ð¢ÐµÐºÑÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÐ·Ð²Ð»ÐµÐºÐ°ÐµÑÑÑ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÑÐ°, ÑÐ²Ð»ÑÐµÑÑÑ Ð°ÐŽÐµÐºÐ²Ð°ÑÐœÑÐŒ ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ° Ðž ÑÐµÐ»ÐµÐ²ÐŸÐ³ÐŸ ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ.</Text>
+</th>
+<th width="85">
+<Text id="434"><i>.doc</i></Text>
+</th>
+<th width="76">
+<Text id="435"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="436"><i>PDFPlug</i></Text>
+</th>
+<th width="236">
+<Text id="437">Processes PDF documents, extracting the first line of text as a title. The <i>pdftohtml</i> program fails on some PDF files. What happens is that the conversion process takes an exceptionally long time, and often an error message relating to the conversion process appears on the screen. If this occurs, the only solution that we can offer is to remove the offending document from the collection and re-import.</Text>
+</th>
+<th width="85">
+<Text id="438"><i>.pdf</i></Text>
+</th>
+<th width="76">
+<Text id="439"><i>.gif, .jpeg, .jpg, .png, .css, .rtf</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="440"><i>PSPlug</i></Text>
+</th>
+<th width="236">
+<Text id="441">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² PostScript, Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+: ÐŽÐ°ÑÑ, Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° Ðž ÐœÐŸÐŒÐµÑÐ° ÑÑÑÐ°ÐœÐžÑ.</Text>
+</th>
+<th width="85">
+<Text id="442"><i>.ps</i></Text>
+</th>
+<th width="76">
+<Text id="443"><i>.eps</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="444"><i>EMAILPlug</i></Text>
+</th>
+<th width="236">
+<Text id="445">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° E-mail ÑÐŸÐŸÐ±ÑÐµÐœÐžÐ¹ Ð¿ÑÑÐµÐŒ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°ÐœÐžÑ Ð°Ð²ÑÐŸÑÐ°, ÑÐµÐŒÑ, ÐŽÐ°ÑÑ Ðž Ñ.ÐŽ. ÐÐ°ÐœÐœÐŸÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ Ð¿ÐŸÐºÐ° ÐœÐµ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÐŽÐŸÐ»Ð¶ÐœÑÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ ÑÐŸÐŸÐ±ÑÐµÐœÐžÑ Ð² ÐºÐŸÐŽÐžÑÐŸÐ²ÐºÐµ MIME - Ð·Ð°ÑÐ°ÑÑÑÑ ÐŸÐœÐž Ð²ÑÐ³Ð»ÑÐŽÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÑÑÐ°ÐœÐœÐŸ.</Text>
+</th>
+<th width="85">
+<Text id="446">Must end in digits or digits followed by <i>.Email</i></Text>
+</th>
+<th width="76">
+<Text id="447"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="448"><i>BibTexPlug</i></Text>
+</th>
+<th width="236">
+<Text id="449">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÑÐ°Ð¹Ð»ÐŸÐ² Ð±ÐžÐ±Ð»ÐžÐŸÐ³ÑÐ°ÑÐžÐž Ð² ÑÐŸÑÐŒÐ°ÑÐµ BibText </Text>
+</th>
+<th width="85">
+<Text id="450"><i>.bib</i></Text>
+</th>
+<th width="76">
+<Text id="451"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="452"><i>ReferPlug</i></Text>
+</th>
+<th width="236">
+<Text id="453">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÑÐ°Ð¹Ð»ÐŸÐ² Ð±ÐžÐ±Ð»ÐžÐŸÐ³ÑÐ°ÑÐžÐž Ð² ÑÐŸÑÐŒÐ°ÑÐµ refer</Text>
+</th>
+<th width="85">
+<Text id="454"><i>.bib</i></Text>
+</th>
+<th width="76">
+<Text id="455"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="456"><i>SRCPlug</i></Text>
+</th>
+<th width="236">
+<Text id="457">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ</Text>
+</th>
+<th width="85">
+<Text id="458"><i>Makefile, Readme, .c, .cc, .cpp, .h, .hpp, .pl, .pm, .sh</i></Text>
+</th>
+<th width="76">
+<Text id="459"><i>.o, .obj, .a, .so, .dll</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="460"><i>ImagePlug</i></Text>
+</th>
+<th width="236">
+<Text id="461">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÑÐ°Ð¹Ð»ÐŸÐ² ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐ¹ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐ¹. Ð Ð°Ð±ÐŸÑÐ°ÐµÑ ÑÐŸÐ»ÑÐºÐŸ Ð² UNIX.</Text>
+</th>
+<th width="85">
+<Text id="462"><i>.jpeg, .jpg, .gif, .png, .bmp, .xbm, .tif, .tiff</i></Text>
+</th>
+<th width="76">
+<Text id="463"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="464"><i>SplitPlug</i></Text>
+</th>
+<th width="236">
+<Text id="465">ÐÐŸÐŽÐŸÐ±ÐœÐŸ BasPlug Ðž ConvertToPlug, ÐŽÐ°ÐœÐœÐŸÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐœÐµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð²ÑÐ·Ð²Ð°ÐœÐŸ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ, ÐŸÐŽÐœÐ°ÐºÐŸ ÐŸÐœÐŸ ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÑ Ð·Ð° byplugins Ð² ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž ÑÑÐµÐ±ÑÐµÑÑÑ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÑÐ°Ð¹Ð»Ð°, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐµÐ³ÐŸ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+</th>
+<th width="85">
+<Text id="466"><i>â</i></Text>
+</th>
+<th width="76">
+<Text id="467"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="468"><i>FOXPlug</i></Text>
+</th>
+<th width="236">
+<Text id="469">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÑÐ°Ð¹Ð»ÐŸÐ² dbt FoxBASE</Text>
+</th>
+<th width="85">
+<Text id="470"><i>.dbt, .dbf</i></Text>
+</th>
+<th width="76">
+<Text id="471"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="472"><i>ZIPPlug</i></Text>
+</th>
+<th width="236">
+<Text id="473">Ð Ð°Ð·Ð°ÑÑ
+ÐžÐ²Ð°ÑÐžÑ gzip, bzip, zip Ðž tar ÑÐ°Ð¹Ð»ÐŸÐ², ÐµÑÐ»Ðž ÐŽÐŸÑÑÑÐ¿ÐœÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐµ ÑÑÐµÐŽÑÑÐ²Ð° GNU.</Text>
+</th>
+<th width="85">
+<Text id="474"><i>.gzip, .bzip, .zip, .tar, .gz, .bz, .tgz, .taz</i></Text>
+</th>
+<th width="76">
+<Text id="475"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60">
+<Text id="476"><b>ÐÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž <br/> ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</b></Text>
+</th>
+<th width="72">
+<Text id="477"><i>PrePlug</i></Text>
+</th>
+<th width="236">
+<Text id="478">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° ÐºÐŸÐœÐµÑÐœÐŸÐ¹ HTML, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ PRESCRIPT, ÑÐ°Ð·Ð±ÐžÐµÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐ°Ñ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Computer Science Technical Reports.</Text>
+</th>
+<th width="85">
+<Text id="479"><i>.html, .html.gz</i></Text>
+</th>
+<th width="76">
+<Text id="480"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="481"><i>GBPlug</i></Text>
+</th>
+<th width="236">
+<Text id="482">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° E-text (ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ°) Project Gutenberg (ÐÑÐŸÐµÐºÑÐ° ÐÑÑÐµÐœÐ±ÐµÑÐ³), Ð²ÐºÐ»ÑÑÐ°ÑÑÐ°Ñ ÑÑÑÐœÐŸÐ¹ Ð²Ð²ÐŸÐŽ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐŸ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ°Ñ
+.</Text>
+</th>
+<th width="85">
+<Text id="483"><i>.txt.gz, .html, .htm</i></Text>
+</th>
+<th width="76">
+<Text id="484"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="60"/>
+<th width="72">
+<Text id="485"><i>TCCPlug</i></Text>
+</th>
+<th width="236">
+<Text id="486">ÐÐ±ÑÐ°Ð±ÐŸÑÐºÐ° E-mail ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð¿ÐŸÑÑÑÐ¿ÐžÐ²ÑÐžÑ
+ ÐŸÑ ÐµÐ¶ÐµÐœÐµÐŽÐµÐ»ÑÐœÐžÐºÐ° Computistsâ Weekly</Text>
+</th>
+<th width="85">
+<Text id="487">ÐÐ±ÑÐ·Ð°ÐœÐ° ÐœÐ°ÑÐžÐœÐ°ÑÑÑÑ Ñ tcc ÐžÐ»Ðž cw</Text>
+</th>
+<th width="76">
+<Text id="488"><i>â</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="489">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐŽÐ»Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐŒ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµÐŒ, ÑÐŸÑÐŒÐžÑÑÑÑÐžÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐŽÐ»Ñ Ð°ÐœÐ°Ð»ÐžÐ·Ð° ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ ÐµÐ³ÐŸ ÑÐŸÑÐŒÐ°ÑÐŸÐŒ. Ð€Ð°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÐµÑÐµÑÐžÑÐ»ÑÐµÑ Ð²ÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ Ð¿ÑÐž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐž ÑÐ°ÐŒÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð Ð¿ÑÐŸÑÐµÑÑÐµ ÐžÐŒÐ¿ÐŸÑÑÐ° ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐ°Ð¹Ð» ÐžÐ»Ðž ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ Ð°ÐœÐ°Ð»ÐžÐ·ÐžÑÑÑÑÑÑ ÐºÐ°Ð¶ÐŽÑÐŒ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµÐŒ ÐŽÐŸ ÑÐµÑ
+ Ð¿ÐŸÑ, Ð¿ÐŸÐºÐ° ÑÑÐµÐ±ÑÐµÐŒÑÐµ ÐœÐµ Ð±ÑÐŽÑÑ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÐœÑ - Ð±ÐŸÐ»ÐµÐµ ÑÐ°ÐœÐœÐžÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐžÐŒÐµÑÑ Ð¿ÑÐžÐŸÑÐžÑÐµÑ Ð¿ÐµÑÐµÐŽ Ð±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐ·ÐŽÐœÐžÐŒÐž. ÐÑÐ»Ðž ÐœÐµÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÑÐŒÐŸÐ³Ð»Ðž Ð±Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐœÐµÐºÐžÐ¹ ÑÐ°Ð¹Ð», Ð±ÑÐŽÐµÑ Ð²ÑÐŽÐ°ÐœÐŸ Ð¿ÑÐµÐŽÑÐ¿ÑÐµÐ¶ÐŽÐµÐœÐžÐµ (ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐµ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐµ ÐŸÐ± ÐŸÑÐžÐ±ÐºÐµ) Ðž Ð¿ÑÐŸÑÐµÑÑ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž Ð¿ÐµÑÐµÐ¹ÐŽÐµÑ Ðº ÑÐ»ÐµÐŽÑÑÑÐµÐŒÑ ÑÐ°Ð¹Ð»Ñ. (Ð­ÑÐŸ ÑÐŸÑ ÑÐ»ÑÑÐ°Ð¹, Ð³ÐŽÐµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐ° ÐŸÐ¿ÑÐžÑ block_exp - Ð¿ÑÐµÐŽÐŸÑÐ²ÑÐ°ÑÐµÐœÐžÐµ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÑ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐ¹ ÐŸÐ± ÐŸÑÐžÐ±ÐºÐµ ÐŽÐ»Ñ ÑÐµÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ², Ð¿ÑÐžÑÑÑÑÑÐ²ÐžÐµ ÐºÐŸÑÐŸÑÑÑ
+ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð±ÐµÐ· ÐžÑ
+ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž). Ð Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÑÐ° Ð¶Ðµ ÑÐ°ÐŒÐ°Ñ Ð¿ÑÐŸÑÐµÐŽÑÑÐ°, ÑÐŸÐ»ÑÐºÐŸ Ð²ÐŒÐµÑÑÐŸ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž archives ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ import.</Text>
+<Text id="490">Ð¡Ð¿ÐžÑÐŸÐº ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ
+ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹ Greenstone Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="greenstone_plugins"/>. ÐÐ»Ñ Ð¿ÑÐŸÑ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ Ð¿ÐŸ ÐŽÐµÑÐµÐ²Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐ° ÑÐµÐºÑÑÑÐžÑ. Ð¥ÐŸÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐžÐŒÐ¿ÐŸÑÑÐ° Ðž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐœÐµ Ð²ÑÐ¿ÐŸÐ»ÐœÑÑÑ ÑÐ²ÐœÑÑ ÑÐµÐºÑÑÑÐžÑ, ÐœÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ Ð¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐºÐŸÑÐ²ÐµÐœÐœÐŸÐ¹ ÑÐµÐºÑÑÑÐžÐµÐ¹ Ð¿ÑÐž Ð¿ÑÐŸÑ
+ÐŸÐ¶ÐŽÐµÐœÐžÐž ÐžÐŒÐµÐœ ÑÐ°Ð¹Ð»ÐŸÐ² ÐžÐ»Ðž ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹ ÑÐµÑÐµÐ· ÐºÐŸÐœÐ²ÐµÐ¹ÐµÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐµ Ð¿ÑÐŸÑ
+ÐŸÐ¶ÐŽÐµÐœÐžÐµ ÑÐµÐºÑÑÑÐžÐž Ð¿ÐŸ ÐŽÐµÑÐµÐ²Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑÑÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµÐŒ RecPlug, Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐŒÐž ÐžÐŒÐµÐœÐœÐŸ ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ, ÐµÑÐ»Ðž, ÐºÐŸÐœÐµÑÐœÐŸ, ÐŸÐœÐŸ Ð±ÑÐŽÐµÑ Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐŒ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐŒ Ð² ÐºÐŸÐœÐ²ÐµÐ¹ÐµÑÐµ. ÐÐŸÑÐ²ÐµÐœÐœÑÑ Ð¶Ðµ ÑÐµÐºÑÑÑÐžÑ Ð²ÑÐ·ÑÐ²Ð°ÑÑ ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ²Ð° Ð¿ÐµÑÐ²ÑÑ
+ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐžÐ· Ð¢Ð°Ð±Ð»ÐžÑÑ <CrossRef target="Table" ref="greenstone_plugins"/>.</Text>
+<Text id="491">ÐÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ Ð±ÑÐ»Ðž ÐœÐ°Ð¿ÐžÑÐ°ÐœÑ ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐžÐŒÐµÑÑÐžÑ
+ ÐŸÑÐŸÐ±ÑÐ¹ ÑÐŸÑÐŒÐ°Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð¿ÐŸÐŽÐŸÐ±ÐœÐŸ E-text (ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐŒÑ ÑÐµÐºÑÑÑ), ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐŒÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Gutenberg. Ð­ÑÐž ÑÐ¿ÐµÑÐžÑÐžÑÐœÑÐµ ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ Ð² ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž perllib/plugins. ÐÐ°ÐœÐœÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÑ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐŸÑÐŒÐµÐœÐžÑÑ ÐŸÐ±ÑÐžÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ Ñ ÑÐ°ÐºÐžÐŒ Ð¶Ðµ ÐžÐŒÐµÐœÐµÐŒ.</Text>
+<Text id="492">ÐÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ Ð²ÐœÐµÑÐœÐžÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÐºÐŸÑÐŸÑÑÐµ Ð°ÐœÐ°Ð»ÐžÐ·ÐžÑÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐµ ÑÐ°ÑÑÐœÑÐµ ÑÐŸÑÐŒÐ°ÑÑ, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŽÐ»Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÑÐµÐºÑÑÐ° - Microsoft Word ÐžÐ»Ðž HTML. ÐÐ±ÑÐµÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ConvertToPlug Ð²ÑÐ·ÑÐ²Ð°ÐµÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÐž Ðž Ð¿ÐµÑÐµÐŽÐ°ÐµÑ ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž Ð»ÐžÐ±ÐŸ TEXTPlug, Ð»ÐžÐ±ÐŸ HTMLPlug. ÐÐ°Ð»ÐµÐµ ÐŒÑ ÐŸÑÑÐ°ÐœÐŸÐ²ÐžÐŒÑÑ ÐœÐ° ÑÑÐŸÐŒ Ð±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸ.</Text>
+<Text id="493">ÐÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐžÐŒÐµÑÑ ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÑÐµ ÐŸÐ¿ÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑ Ð¿ÑÐŸÑÐµÑÑÐ°ÐŒÐž Ð±ÐŸÐ»ÐµÐµ ÐŽÐµÑÐ°Ð»ÑÐœÐŸ, ÑÐµÐŒ ÑÑÐŸ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ ÐŸÐ±ÑÐžÐµ ÐŸÐ¿ÑÐžÐž. ÐÐœÐž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="plugin-specific_options"/>.</Text>
+<Table id="plugin-specific_options">
+<Title>
+<Text id="494">ÐÐ¿ÑÐžÐž, ÑÐ¿ÐµÑÐžÑÐžÑÐœÑÐµ ÐŽÐ»Ñ Ð¿ÑÐžÐŸÐ¶ÐµÐœÐžÐ¹</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="495"><b>ÐÐ¿ÑÐžÑ</b></Text>
+</th>
+<th width="265">
+<Text id="496"><b>ÐŠÐµÐ»Ñ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="497"><i>HTMLPlug</i></Text>
+</th>
+<th width="132">
+<Text id="498"><i>nolinks</i></Text>
+</th>
+<th width="265">
+<Text id="499">ÐÐµ ÐŸÐ±ÑÑÐ²Ð°ÑÑ ÑÑÑÐ»ÐºÐž Ð²ÐœÑÑÑÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð­ÑÐŸ ÑÑÐºÐŸÑÑÐµÑ Ð¿ÑÐŸÑÐµÑÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ°/ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐŸÐŽÐœÐ°ÐºÐŸ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÑÑÑÐ»ÐºÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÐ±ÐŸÑÐ²Ð°ÐœÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="500"><i>description_tags</i></Text>
+</th>
+<th width="265">
+<Text id="501">ÐÐœÑÐµÑÐ¿ÑÐµÑÐžÑÐŸÐ²Ð°ÑÑ ÑÐ°Ð¹Ð»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÐºÐ°Ðº ÐŸÐ¿ÐžÑÐ°ÐœÐŸ ÐœÐžÐ¶Ðµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="502"><i>keep_head</i></Text>
+</th>
+<th width="265">
+<Text id="503">ÐÐµ ÐŸÑÐ±ÑÐ°ÑÑÐ²Ð°ÑÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž HTML.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="504"><i>no_metadata</i></Text>
+</th>
+<th width="265">
+<Text id="505">ÐÐµ ÐžÑÐºÐ°ÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ (ÑÑÐŸ ÐŒÐŸÐ¶ÐµÑ ÑÐ²ÐµÐ»ÐžÑÐžÑÑ ÑÐºÐŸÑÐŸÑÑÑ Ð¿ÑÐŸÑÐµÑÑÐŸÐ² ÐžÐŒÐ¿ÐŸÑÑÐ°/ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ).</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="506"><i>metadata_fields</i></Text>
+</th>
+<th width="265">
+<Text id="507">ÐÑÐŸÐ±ÑÐ°ÑÑ ÐŽÐ»Ñ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐµÐ³ÐŸ ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÑ ÐŸÑÐŽÐµÐ»ÐµÐœÐœÑÐµ Ð·Ð°Ð¿ÑÑÑÐŒÐž ÑÐžÐ¿Ñ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Title). ÐÐµÑÐµÐžÐŒÐµÐœÐŸÐ²Ð°ÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŽÐ»Ñ ÑÐ°Ð¹Ð»Ð° Ð°ÑÑ
+ÐžÐ²Ð° Greenstone, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ tag, Ð³ÐŽÐµ tag-ÑÑÐŸ HTML-ÑÑÐ³, Ð° newname-ÑÑÐŸ ÐœÐŸÐ²ÐŸÐµ ÐžÐŒÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="508"><i>hunt_creator_metadata</i></Text>
+</th>
+<th width="265">
+<Text id="509">ÐÐ±ÐœÐ°ÑÑÐ¶ÐžÑÑ Ð²ÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŸÐ± Ð°Ð²ÑÐŸÑÑÑÐ²Ðµ Ðž Ð¿ÐŸÐŒÐµÑÑÐžÑÑ ÐžÑ
+ Ð² Ð°ÑÑ
+ÐžÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Greenstone Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÑÐžÐ¿Ð° Creator. Ð¢Ð°ÐºÐ¶Ðµ Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð²ÐºÐ»ÑÑÐžÑÑ Creator, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŸÐ¿ÑÐžÑ metadata_fields.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="510"><i>file_is_url</i></Text>
+</th>
+<th width="265">
+<Text id="511">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÑÑ ÐŸÐ¿ÑÐžÑ, ÐµÑÐ»Ðž ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÑÑÑÑÐºÑÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐŽÑÑ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ð»Ð°ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° web-Ð·ÐµÑÐºÐ°Ð»ÐžÑÐŸÐ²Ð°ÐœÐžÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="512"><i>assoc_files</i></Text>
+</th>
+<th width="265">
+<Text id="513">ÐÑÐµÐŽÑÑÐ°Ð²ÐžÑÑ ÐŸÐ±ÑÑÐœÐŸÐµ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÐµ ÐœÐ° ÑÐ·ÑÐºÐµ Perl, ÐŸÐ¿ÐžÑÑÐ²Ð°ÑÑÐµÐµ ÑÐžÐ¿Ñ ÑÐ°Ð¹Ð»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐŽÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÑ ÐºÐ°Ðº ÑÐ²ÑÐ·ÐœÑÐµ ÑÐ°Ð¹Ð»Ñ. ÐÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÑÑÐŸ .jpg, .jpeg, .gif, .png, .css</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="514"><i>rename_assoc_files</i></Text>
+</th>
+<th width="265">
+<Text id="515">ÐÐµÑÐµÐžÐŒÐµÐœÐŸÐ²Ð°ÑÑ ÑÐ²ÑÐ·Ð°ÐœÐœÑÐµ Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ ÑÐ°Ð¹Ð»Ñ. ÐÐ° Ð²ÑÐµÐŒÑ ÑÑÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐµÑÑÐ° ÐŽÐžÑÐµÐºÑÐžÐ²ÐœÐ°Ñ ÑÑÑÑÐºÑÑÑÐ° Ð»ÑÐ±ÑÑ
+ ÑÐ²ÑÐ·ÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² ÑÑÐ°Ð»Ð° Ð±Ñ ÐœÐ°ÐŒÐœÐŸÐ³ÐŸ Ð±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐ²ÐµÑÑ
+ÐœÐŸÑÑÐœÐŸÐ¹ (ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² ÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, ÐºÐŸÐ³ÐŽÐ° Ð¿ÐŸÐŽ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐŸÑÐ²ÐµÐŽÐµÐœÐŸ ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÐœÐŸÐµ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²ÐŸ).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="516"><i>HTMLPlug</i> and <br/><i>TEXTPlug</i></Text>
+</th>
+<th width="132">
+<Text id="517"><i>title_sub</i></Text>
+</th>
+<th width="265">
+<Text id="518">ÐÑÑÐ°Ð¶ÐµÐœÐžÐµ Ð·Ð°ÐŒÐµÐœÑ ÐœÐ° ÑÐ·ÑÐºÐµ Perl ÐŽÐ»Ñ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ².</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="519"><i>PSPlug</i></Text>
+</th>
+<th width="132">
+<Text id="520"><i>extract_date</i></Text>
+</th>
+<th width="265">
+<Text id="521">ÐÐ·Ð²Ð»ÐµÑÑ ÐŽÐ°ÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐžÐ· Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° PostScript Ðž ÑÐŸÑ
+ÑÐ°ÐœÐžÑÑ ÐºÐ°Ðº ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="522"><i>extract_title</i></Text>
+</th>
+<th width="265">
+<Text id="523">ÐÐ·Ð²Ð»ÐµÑÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐžÐ· Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° PostScript Ðž ÑÐŸÑ
+ÑÐ°ÐœÐžÑÑ ÐºÐ°Ðº ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="132">
+<Text id="524"><i>extract_pages</i></Text>
+</th>
+<th width="265">
+<Text id="525">ÐÐ·Ð²Ð»ÐµÑÑ ÐœÐŸÐŒÐµÑÐ° ÑÑÑÐ°ÐœÐžÑ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° PostScript Ðž ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐžÑ
+ Ðº ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ð°ÐŒ ÐºÐ°Ðº ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ñ ÑÑÐ³ÐŸÐŒ Pages.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="526"><i>RecPlug</i></Text>
+</th>
+<th width="132">
+<Text id="527"><i>use_metadata_files</i></Text>
+</th>
+<th width="265">
+<Text id="528">ÐÐ°Ð·ÐœÐ°ÑÐžÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŽÐ»Ñ ÑÐ°Ð¹Ð»Ð°, ÐºÐ°Ðº ÐŸÐ¿ÐžÑÐ°ÐœÐŸ ÐœÐžÐ¶Ðµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="529"><i>ImagePlug</i></Text>
+</th>
+<th width="132">
+<Text id="530">Various options</Text>
+</th>
+<th width="265">
+<Text id="531">Ð¡ÐŒ. ImagePlug.pm.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="532"><i>SRCPlug</i></Text>
+</th>
+<th width="132">
+<Text id="533"><i>remove_prefix</i></Text>
+</th>
+<th width="265">
+<Text id="534">Ð¡ÐŸÐ·ÐŽÐ°ÑÑ ÐŸÐ±ÑÑÐœÐŸÐµ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÐµ ÐœÐ° ÑÐ·ÑÐºÐµ Perl ÐŽÐ»Ñ ÑÐ°Ð±Ð»ÐŸÐœÐ°, ÐºÐŸÑÐŸÑÑÐ¹ ÐŽÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ ÑÐŽÐ°Ð»ÐµÐœ ÐžÐ· ÐžÐŒÐµÐœÐž ÑÐ°Ð¹Ð»Ð°. Ð ÑÐµÐ¶ÐžÐŒÐµ Ð¿ÐŸ
+ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÑÐµÐ»ÐžÐºÐŸÐŒ ÑÐŽÐ°Ð»ÑÐµÑÑÑ Ð¿ÑÑÑ.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="plugins_to_import_proprietary_formats">
+<Title>
+<Text id="535">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐŽÐ»Ñ ÐžÐŒÐ¿ÐŸÑÑÐ° ÑÐ°ÑÑÐœÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="536">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐœÐµÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ² ÑÐ²Ð»ÑÐµÑÑÑ ÑÑÑÐŽÐœÐŸÑÐ°Ð·ÑÐµÑÐžÐŒÐŸÐ¹ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐŸÐ¹ ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÑÐžÑÑÐŸÐ²ÑÑ
+ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÑ
+ ÑÐžÑÑÐµÐŒ. Ð Ñ
+ÐŸÑÑ ÑÐ°Ð±ÐŸÑÐ°Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÑ Ð¿ÐŸ ÑÑÐžÐŒ ÑÐŸÑÐŒÐ°ÑÐ°ÐŒ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð²Ð¿ÐŸÐ»ÐœÐµ ÐŽÐŸÑÑÑÐ¿ÐœÐŸÐ¹, ÐŸÐŽÐœÐ°ÐºÐŸ ÑÐ°ÐŒ Ð¿ÑÐµÐŽÐŒÐµÑ Ð²ÐœÐµÑÐµÐœÐžÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÐ¹ ÐŸÑÑÐ°ÐµÑÑÑ Ð² ÐœÐµÐ¹ Ð±ÐµÐ· ÐŸÑÑÐ°Ð¶ÐµÐœÐžÑ, ÑÑÐŸ ÐŸÑÑÐ°Ð²Ð»ÑÐµÑ ÑÑÑÐŽÐœÐŸÑÑÐž Ð¿ÑÐž Ð²ÐœÐµÑÐµÐœÐžÐž ÐžÐ·ÐŒÐµÐœÐµÐœÐžÐ¹. Ð¡ÐžÑÑÐµÐŒÐ° Greenstone Ð¿ÐŸÑÐ»Ð° Ð¿ÐŸ Ð¿ÑÑÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ GPL (GNU Public License) ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÑ
+ ÑÑÐžÐ»ÐžÑ ÐŽÐ»Ñ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°ÐœÑ Ð»ÑÐŽÑÐŒÐž, ÑÐ¿ÐµÑÐžÐ°Ð»ÐžÐ·ÐžÑÑÑÑÐžÐŒÐžÑÑ ÐžÐŒÐµÐœÐœÐŸ ÐœÐ° ÑÐ°ÐºÐžÑ
+ ÑÐ°Ð±ÐŸÑÐ°Ñ
+. Ð£ÑÐžÐ»ÐžÑÑ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐŸÑÐŒÐ°ÑÐŸÐ² Word Ðž PDF Ð²ÐºÐ»ÑÑÐµÐœÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ packages. ÐÐœÐž ÐºÐŸÐœÐ²ÐµÑÑÐžÑÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÑÐµÐºÑÑ ÐžÐ»Ðž HTML. ÐÐ°ÑÐµÐŒ HTMLPlug Ðž TEXTPlug Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÑÑÑ ÐžÑ
+ Ð² ÑÐŸÑÐŒÐ°Ñ Ð°ÑÑ
+ÐžÐ²Ð° Greenstone. ConvertToPlug ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ð²ÐºÐ»ÑÑÐµÐœÐžÑ ÑÑÐžÑ
+ ÑÑÐžÐ»ÐžÑ. Ð ÑÐ°Ðº Ð¶Ðµ ÐºÐ°Ðº BasPlug, ÐœÐžÐºÐŸÐ³ÐŽÐ° ÐœÐµ Ð²ÑÐ·ÑÐ²Ð°ÐµÑÑÑ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ. ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="plugin_inheritance_hierarchy"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ, ÐœÐ°Ð¿ÐžÑÐ°ÐœÐœÑÐµ ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ². ConvertToPlug, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑ
+ÐµÐŒÑ ÐŽÐžÐœÐ°ÐŒÐžÑÐµÑÐºÐŸÐ³ÐŸ ÑÐ°ÑÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ Perl Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑ TEXTPlug ÐžÐ»Ðž HTMLPlug Ð² Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÑÐŸÑÐŒÐ°ÑÐ°, Ð² ÐºÐŸÑÐŸÑÑÐ¹ Ð±ÑÐ»Ðž ÐºÐŸÐœÐ²ÐµÑÑÐžÑÐŸÐ²Ð°ÐœÑ ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ.</Text>
+<Figure id="plugin_inheritance_hierarchy">
+<Title>
+<Text id="537">ÐÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐ°Ñ ÑÑÑÑÐºÑÑÑÐ° ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐ¹</Text>
+</Title>
+<File width="229" height="193" url="images/Dev_Fig_024.jpg"/>
+</Figure>
+<Text id="538">ÐÐŸÐ³ÐŽÐ° ConvertToPlug Ð¿ÐŸÐ»ÑÑÐ°ÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ, ÐŸÐœ Ð²ÑÐ·ÑÐ²Ð°ÐµÑ gsConvert.pl (ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž GSDLHOME/bin/script) ÐŽÐ»Ñ Ð·Ð°Ð¿ÑÑÐºÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐ¹ ÑÑÐžÐ»ÐžÑÑ. ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð±ÑÐŽÐµÑ Ð¿ÑÐŸÐºÐŸÐœÐ²ÐµÑÑÐžÑÐŸÐ²Ð°Ðœ, ÐŸÐœ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑÑÑ Ðº ConvertToPlug, ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÑÐ·ÑÐ²Ð°ÐµÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÑÐµÐºÑÑÐ° ÐžÐ»Ðž HTML. ÐÑÐ±ÐŸÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ, Ð²ÑÐ·Ð²Ð°ÐœÐœÐŸÐµ ConvertToPlug, ÐžÐŒÐµÐµÑ ÐŸÐ¿ÑÐžÑ convertjto, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð°ÑÐ³ÑÐŒÐµÐœÑ textvum html, ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ Ð¿ÑÐµÐŽÐŸÑÑÐžÑÐµÐ»ÑÐœÐŸÐ³ÐŸ ÑÐŸÑÐŒÐ°ÑÐ°. Ð Ð°Ð±ÐŸÑÐ° Ñ ÑÐµÐºÑÑÐŸÐŒ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ Ð·ÐœÐ°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð±ÑÑÑÑÐµÐµ, ÐŸÐŽÐœÐ°ÐºÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑ, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÑÐ¹ Ð² ÑÐŸÑÐŒÐ°ÑÐµ HTML, Ð²ÑÐ³Ð»ÑÐŽÐžÑ ÐœÐ°ÐŒÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÐµÑÐœÐµÐµ Ðž ÐŒÐŸÐ¶ÐµÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÐžÐ»Ð»ÑÑÑÑÐ°ÑÐžÐž.</Text>
+<Text id="539">ÐÐœÐŸÐ³ÐŽÐ° ÐŽÐ»Ñ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÑÐŸÑÐŒÐ°ÑÐ° ÑÑÑÐµÑÑÐ²ÑÐµÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÑÐžÐ»ÐžÑ, Ðž gsConvert ÐŒÐŸÐ¶ÐµÑ Ð¿ÑÑÐ°ÑÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐžÑ
+. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŽÐ»Ñ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÐž Word Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐžÑÐµÐ»ÑÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÑÐžÐ»ÐžÑÑ wvWare, ÐŸÐŽÐœÐ°ÐºÐŸ ÐŸÐœÐ° ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÐµ Ð² ÑÐµÐŽÐ°ÐºÑÐŸÑÐµ Word ÐœÐµ ÐœÐžÐ¶Ðµ 6 Ð²ÐµÑÑÐžÐž, Ð° Ð²ÐŸÑ ÑÑÐžÐ»ÐžÑÑ AnyToHTML, ÐºÐŸÑÐŸÑÐ°Ñ no-ÑÑÑÐµÑÑÐ²Ñ ÐžÐ·Ð²Ð»ÐµÐºÐ°ÐµÑ ÑÐŸÐ»ÑÐºÐŸ ÑÐµÐºÑÑÐŸÐ²ÑÐµ ÑÑÑÐŸÐºÐž, which essentially just extracts whatever text strings can be found, Ð²Ð¿ÐŸÐ»ÐœÐµ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÐ»Ñ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐžÐ· Word 5.</Text>
+<Text id="540">ÐšÐ°Ð³Ðž Ð·Ð°Ð³ÑÑÐ·ÐºÐž ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÑÐžÐ»ÐžÑÑ ÐŽÐ»Ñ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÑ Ð²ÐœÐµÑÐœÐžÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="541">Ð£ÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÐœÐŸÐ²ÑÑ ÑÑÐžÐ»ÐžÑÑ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ ÑÑÐµÐ±ÐŸÐ²Ð°ÐœÐžÑÐŒÐž Greenstone (Ð¿ÐŸÐŒÐµÑÑÐžÑÑ ÐµÐµ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ <i>packages</i>).</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="542">ÐÐœÐµÑÑÐž   ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð² gsConvert.pl ÐŽÐ»Ñ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐµÐ³ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÑÑÐžÐ»ÐžÑÑ. ÐÐœÐž Ð·Ð°ÐºÐ»ÑÑÐ°ÑÑÑÑ Ð² ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐž ÐœÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÑÐµÐŽÐ»ÐŸÐ¶ÐµÐœÐžÑ Ñ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÐŸÐŒ if Ð² ÑÑÐœÐºÑÐžÑ main, Ðž ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐž ÑÑÐœÐºÑÐžÐž, Ð²ÑÐ·ÑÐ²Ð°ÑÑÐµÐ¹ ÐœÐŸÐ²ÑÑ ÑÑÐžÐ»ÐžÑÑ.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="543">W3.	ÐÐ°Ð¿ÐžÑÐ°ÑÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐœÐ° ÑÑÐŸÐ²ÐµÐœÑ, ÑÐ»ÐµÐŽÑÑÐžÐ¹ Ð·Ð°  <i>ConvertToPlug</i>, ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ Ð¿ÐµÑÐµÑ
+Ð²Ð°ÑÐžÑÑ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÑ Ð² ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐ¹ ÑÐŸÑÐŒÐ°Ñ, Ð¿ÐŸÐŽÐŒÐµÐœÐžÐ² ÐµÐ³ÐŸ ÐœÐ° ÐœÑÐ¶ÐœÑÐ¹.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Subsection>
+<Subsection id="assigning_metadata_from_a_file">
+<Title>
+<Text id="544">ÐÐ°Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐžÐ· ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ³ÐŸ ÑÐ°Ð¹Ð»Ð°</Text>
+</Title>
+<Content>
+<Text id="545">Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ RecPlug Ð¿ÐŸÐŒÐžÐŒÐŸ Ð²ÑÐµÐ³ÐŸ, ÐžÐŒÐµÐµÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÐœÐ°Ð·ÐœÐ°ÑÐ°ÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð²ÑÑÑÐœÑÑ (ÐžÐ»Ðž Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž), ÑÐŸÐ·ÐŽÐ°Ð²Ð°Ñ XML-ÑÐ°Ð¹Ð»Ñ. ÐÑÑÐ°ÐœÐŸÐ²ÐžÐŒÑÑ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐµÐµ ÐœÐ° ÑÑÐŸÐŒ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ Ð²Ñ ÑÐ°ÐŒÐž ÑÐŒÐŸÐ³Ð»Ðž ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÑÐ°Ð¹Ð»Ñ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ Ð²Ð°ÑÐžÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ². ÐÑÐ»Ðž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐ° ÐŸÐ¿ÑÐžÑ usejnetadatajiles, ÑÐŸ RecPlug ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Ð²ÑÐ¿ÐŸÐŒÐŸÐ³Ð°ÑÐµÐ»ÑÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ - metadata.xml. ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="xml_format"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ XML Document Type Definition (DTD) ÐŽÐ»Ñ ÑÐŸÑÐŒÐ°ÑÐ° ÑÐ°Ð¹Ð»Ð° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, Ð° ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="xml_format_1"/> Ð¿ÑÐžÐ²ÐµÐŽÐµÐœ Ð¿ÑÐžÐŒÐµÑ ÑÐ°Ð¹Ð»Ð° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ metadata.xml.</Text>
+<Figure id="xml_format">
+<Title>
+<Text id="546">Ð€ÐŸÑÐŒÐ°Ñ XML. a) Document Type Definition (DTD); Ð±) Ð¿ÑÐžÐŒÐµÑ ÑÐ°Ð¹Ð»Ð°</Text>
+<SubTitle>
+<Text id="547">(a)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;!DOCTYPE GreenstoneDirectoryMetadata [</CodeLine>
+<CodeLine>   &lt;!ELEMENT DirectoryMetadata (FileSet*)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT FileSet (FileName+,Description)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT FileName (#PCDATA)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT Description (Metadata*)&gt;</CodeLine>
+<CodeLine>   &lt;!ELEMENT Metadata (#PCDATA)&gt;</CodeLine>
+<CodeLine>   &lt;ATTLIST Metadata name CDATA #REQUIRED&gt;</CodeLine>
+<CodeLine>   &lt;ATTLIST Metadata mode (accumulate|override) "override"&gt;</CodeLine>
+<CodeLine>]&gt;</CodeLine>
+</Figure>
+<Figure id="xml_format_1">
+<Title>
+<Text id="548"/>
+<SubTitle>
+<Text id="549">(b)</Text>
+</SubTitle>
+</Title>
+<CodeLine>&lt;?xml version="1.0" ?&gt;</CodeLine>
+<CodeLine>&lt;!DOCTYPE GreenstoneDirectoryMetadata SYSTEM</CodeLine>
+<CodeLine>"http://greenstone.org/dtd/GreenstoneDirectoryMetadata/<br/>1.0/GreenstoneDirectoryMetadata.dtd"&gt;</CodeLine>
+<CodeLine>&lt;DirectoryMetadata&gt;</CodeLine>
+<CodeLine>   &lt;FileSet&gt;</CodeLine>
+<CodeLine>       &lt;FileName&gt;nugget.*&lt;/FileName&gt;</CodeLine>
+<CodeLine>       &lt;Description&gt;</CodeLine>
+<CodeLine>       &lt;Metadata name="Title"&gt;Nugget Point Lighthouse&lt;/Metadata&gt;</CodeLine>
+<CodeLine>           &lt;Metadata name="Place" mode="accumulate"&gt;Nugget Point&lt;/Metadata&gt;</CodeLine>
+<CodeLine>       &lt;/Description&gt;</CodeLine>
+<CodeLine>   &lt;/FileSet&gt;</CodeLine>
+<CodeLine>   &lt;FileSet&gt;</CodeLine>
+<CodeLine>       &lt;FileName&gt;nugget-point-1.jpg&lt;/FileName&gt;</CodeLine>
+<CodeLine>       &lt;Description&gt;</CodeLine>
+<CodeLine>           &lt;Metadata name="Title"&gt;Nugget Point Lighthouse , The Catlins &lt;/Metadata&gt;</CodeLine>
+<CodeLine>           &lt;Metadata name="Subject"&gt;Lighthouse&lt;/Metadata&gt;</CodeLine>
+<CodeLine>       &lt;/Description&gt;</CodeLine>
+<CodeLine>   &lt;/FileSet&gt;</CodeLine>
+<CodeLine>&lt;/DirectoryMetadata&gt;</CodeLine>
+</Figure>
+<Text id="550">Ð Ð¿ÑÐžÐŒÐµÑÐµ Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ ÑÐ°Ð¹Ð», ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐŽÐ²Ðµ ÑÑÑÑÐºÑÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. Ð ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+, ÑÐ»ÐµÐŒÐµÐœÑ filename ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÑÐ°Ð¹Ð», Ðº ÐºÐŸÑÐŸÑÐŸÐŒÑ ÐŸÑÐœÐŸÑÑÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, Ð² Ð²ÐžÐŽÐµ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐ³ÐŸ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÑ. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, <FileName>nugget. *</FileName> ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÑÐŸ, ÑÑÐŸ Ð¿ÐµÑÐ²Ð°Ñ Ð·Ð°Ð¿ÐžÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŸÑÐœÐŸÑÐžÑÑÑ ÐºÐŸ Ð²ÑÐµÐŒ ÑÐ°Ð¹Ð»Ð°ÐŒ, ÑÑÐµ ÐžÐŒÑ ÐœÐ°ÑÐžÐœÐ°ÐµÑÑÑ Ñ "nugget"<FootnoteRef id="2"/>. ÐÐ»Ñ ÑÑÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐžÐ¿Ð° Title ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÐºÐ°Ðº "Nugget Point Lighthouse".</Text>
+<Text id="551">Ð­Ð»ÐµÐŒÐµÐœÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŸÑÑÐ°Ð±Ð°ÑÑÐ²Ð°ÑÑÑÑ Ð² ÑÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐŸÐœÐž Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ. ÐÑÐŸÑÐ°Ñ Ð·Ð°Ð¿ÐžÑÑ ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐžÐ¿Ð° Title ÐŽÐ»Ñ ÑÐ°Ð¹Ð»Ð° nuggetpoint- l.jpg ÐºÐ°Ðº "Nugget Point Lighthouse, The Catlins", ÑÐµÐŒ ÑÐ°ÐŒÑÐŒ ÐŸÑÐŒÐµÐœÑÑ Ð¿ÑÐµÐŽÑÐŽÑÑÐžÐµ ÑÐºÐ°Ð·Ð°ÐœÐžÑ. ÐÐŽÐµÑÑ ÑÐ°ÐºÐ¶Ðµ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐŸ Ð¿ÐŸÐ»Ðµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Subject.</Text>
+<Text id="552">ÐÐœÐŸÐ³ÐŽÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐžÐŒÐµÑÑÐžÐµ ÑÐ¶Ðµ ÐœÐµÐºÐŸÑÐŸÑÐŸÐµ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ Ðž Ð¿ÐŸÐ»ÑÑÐ°Ñ ÐœÐŸÐ²ÑÐµ, ÐŽÐŸÐ»Ð¶ÐœÑ ÐžÑ
+ ÐœÐ°ÐºÐ°Ð¿Ð»ÐžÐ²Ð°ÑÑ, Ð²ÐŒÐµÑÑÐŸ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐŸÑÐŒÐµÐœÑÑÑ Ð¿ÑÐµÐŽÑÐŽÑÑÐžÐµ. Ð­ÑÐŸ ÐŽÐµÐ»Ð°ÐµÑÑÑ Ð²Ð²ÐµÐŽÐµÐœÐžÐµÐŒ Ð°ÑÑÐžÐ±ÑÑÐ° mode=accumulate. Ð ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ ÐŸÐ¿ÑÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Place Ð¿ÐµÑÐµÐŒÐµÑÐ°ÐµÑÑÑ ÐœÐ° Ð¿ÐŸÐ·ÐžÑÐžÑ Ð²ÑÑÐµ Ðž ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ ÑÐ¿ÐŸÑÐŸÐ±ÐœÐŸÐ¹ ÐœÐ°ÐºÐ°Ð¿Ð»ÐžÐ²Ð°ÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ. ÐÐ»Ñ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ° Ðº ÐµÐŽÐžÐœÑÑÐ²ÐµÐœÐœÐŸÑÑÐž Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ ÐŽÐ»Ñ ÑÐ»ÐµÐŒÐµÐœÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐœÐ°Ð¿ÐžÑÐžÑÐµ: <i>&lt;Metadata name=âPlaceâ mode=âoverrideâ&gt;New Zealand&lt;/Metadata&gt;</i>. Ð€Ð°ÐºÑÐžÑÐµÑÐºÐž, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÐ¿ÑÑÑÐžÑÑ ÑÑÑ ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÑ ÑÐµÐ¶ÐžÐŒÐ°, Ð¿ÐŸÑÐºÐŸÐ»ÑÐºÑ ÐºÐ°Ð¶ÐŽÑÐ¹ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐžÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ ÐŸÑÐŒÐµÐœÑÐµÑ Ð¿ÑÐµÐŽÑÐŽÑÑÐžÐ¹, ÐµÑÐ»Ðž ÑÑÐŸ Ð·Ð°ÑÐ°ÐœÐµÐµ ÐœÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ. ÐÐ»Ñ ÐœÐ°ÐºÐŸÐ¿Ð»ÐµÐœÐžÑ Ð² ÐœÐµÐºÐŸÑÐŸÑÐŸÐŒ Ð¿ÐŸÐ»Ðµ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ð¿ÑÐž ÐºÐ°Ð¶ÐŽÐŸÐŒ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÐž ÐºÐŸÑÐŸÑÑÑ
+ ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð±ÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐœÐŸ: mode=accumulate.</Text>
+<Text id="553">ÐÐŸÐ³ÐŽÐ° ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÐŸÐ¿ÑÐžÑ usejnetadatajiles, RecPlug Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ ÐºÐ°Ð¶ÐŽÑÑ Ð²Ð²ÐŸÐŽÐžÐŒÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐŽÐ»Ñ XML ÑÐ°Ð¹Ð»Ð° metadata.xml Ðž Ð¿ÑÐžÐŒÐµÐœÑÐµÑ ÐµÐ³ÐŸ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐºÐŸ Ð²ÑÐµÐŒ ÑÐ°Ð¹Ð»Ð°ÐŒ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Ðž Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹.</Text>
+<Text id="554">ÐÐµÑ
+Ð°ÐœÐžÐ·ÐŒ ÑÐ°Ð±ÐŸÑÑ metadata.xml, ÐºÐŸÑÐŸÑÑÐ¹ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ Ð² RecPlug, ÑÐ²Ð»ÑÐµÑÑÑ ÐµÐŽÐžÐœÑÑÐ²ÐµÐœÐœÑÐŒ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐµ. ÐÑÐµÐœÑ Ð¿ÑÐŸÑÑÐŸ ÐœÐ°Ð¿ÐžÑÐ°ÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ ÑÐŒÐŸÐ³ÑÑ Ð¿ÑÐžÐœÐžÐŒÐ°ÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÑÐ¿ÐµÑÐžÑÐžÑÐœÑÐµ ÐŽÐ»Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ².</Text>
+</Content>
+</Subsection>
+<Subsection id="tagging_document_files">
+<Title>
+<Text id="555">ÐÐ°ÑÐºÐžÑÐŸÐ²ÐºÐ° ÑÐ°Ð¹Ð»Ð° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÑÑÐ³Ð°ÐŒÐž</Text>
+</Title>
+<Content>
+<Text id="556">Ð§Ð°ÑÑÐŸ Ð²ÐŸÐ·ÐœÐžÐºÐ°ÐµÑ Ð¿ÐŸÑÑÐµÐ±ÐœÐŸÑÑÑ ÑÑÑÑÐºÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐœÐ° ÑÐ°Ð·ÐŽÐµÐ»Ñ Ðž Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»Ñ. Ð¡ ÑÐµÐ»ÑÑ Ð¿ÑÐµÐŽÐŸÑÐ²ÑÐ°ÑÐµÐœÐžÑ ÐœÐ°ÑÑÑÐµÐœÐžÐ¹ Ð² ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐŸÐ¹ ÑÑÑÑÐºÑÑÑÐµ ÑÑÐ° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ ÑÐŸÐŸÐ±ÑÐµÐœÐ° ÑÐžÑÑÐµÐŒÐµ Greenstone. ÐÐŸÐŒÐžÐŒÐŸ ÑÑÐŸÐ³ÐŸ, ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐŸÐ±ÑÑÐœÐŸ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž, ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÑÐ²ÑÐ·Ð°ÐœÑ Ñ ÐºÐ°Ð¶ÐŽÑÐŒ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐŒ ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐŒ ÐžÐ»Ðž Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»ÐŸÐŒ.</Text>
+<Text id="557">Ð¡Ð°ÐŒÑÐ¹ Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÑÐŽÐµÐ»Ð°ÑÑ ÑÑÐŸ Ð·Ð°ÐºÐ»ÑÑÐ°ÐµÑÑÑ Ð² Ð¿ÑÐŸÑÑÐŸÐŒ ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ². HTML-Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐžÐŒÐµÐµÑ ÐŸÐ¿ÑÐžÑ description_tags, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÑÑÐ³Ðž Ð² ÑÐµÐºÑÑÐµ:</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>   &lt;Description&gt;</CodeLine>
+<CodeLine>       &lt;Metadata name="Title"&gt; Realizing human rights for poor people: Strategies for achieving the international development targets&lt;/Metadata&gt;</CodeLine>
+<CodeLine>   &lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="558"><i>(text of section goes here)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="559">ÐÐ°ÑÐºÐµÑÑ &lt;!-- âŠ --&gt; ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð² HTML ÐŽÐ»Ñ Ð²ÑÑÐ°Ð²ÐºÐž ÐºÐŸÐŒÐŒÐµÐœÑÐ°ÑÐžÐµÐ²; ÑÐ°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, ÑÑÐž ÑÑÐ³Ðž ÐœÐµ Ð±ÑÐŽÑÑ Ð²Ð»ÐžÑÑÑ ÐœÐ° ÐŸÐ±ÑÐµÐµ ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð ÑÐ°ÑÑÐž Description ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ ÐŽÑÑÐ³ÐžÐµ Ð²ÐžÐŽÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐœÐŸ Ð² ÐœÐ°ÑÐµÐŒ ÑÐ»ÑÑÐ°Ðµ ÑÑÐŸ ÑÐŽÐµÐ»Ð°ÐœÐŸ ÐœÐµ Ð±ÑÐ»ÐŸ. ÐÐŸÐŒÐžÐŒÐŸ ÑÑÐŸÐ³ÐŸ, ÑÑÐ³Ðž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ -Ð²Ð»ÐŸÐ¶ÐµÐœÐœÑÐŒÐž. Ð¢Ð°Ðº ÑÑÑÐŸÐºÐ° Ð¿ÐŸÐŒÐµÑÐµÐœÐœÐ°Ñ text of section goes here (ÑÐµÐºÑÑ ÑÐ°Ð·ÐŽÐµÐ»Ð°), Ð² ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÐµÐŒ ÐŒÐŸÐ¶ÐµÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ Ð² ÑÐµÐ±Ñ Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»Ñ, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ,</Text>
+<Text id="560"><i>(text of first part of section goes here)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>   &lt;Description&gt;</CodeLine>
+<CodeLine>       &lt;Metadata name="Title"&gt; The international development targets&lt;/Metadata&gt;</CodeLine>
+<CodeLine>   &lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="561"><i>(text of subsection goes here)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="562"><i>(text of last part of section goes here)</i></Text>
+<Text id="563">Ð­ÑÐžÐŒÐž ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐŒÐž Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑÐŒÐž ÐŸÐ±Ð»Ð°ÐŽÐ°ÐµÑ Ð»ÑÐ±ÐŸÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÐµÐµ HTMLPlug. Ð ÑÐ°ÑÑÐœÐŸÑÑÐž, Word-Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ ÐºÐŸÐœÐ²ÐµÑÑÐžÑÑÑÑ ÐžÑÑ
+ÐŸÐŽÑÐ¹ ÑÐ°Ð¹Ð» Ð² HTML, ÑÐ°Ðº ÑÑÐŸ Ð² ÑÐ»ÑÑÐ°Ðµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐŸÑÐŒÐ°ÑÐ° Word (Ðž RTF), ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ Ð¿ÐŸ ÑÑÐµÐœÐ°ÑÐžÑ ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÑ ÐžÑ
+ ÐžÐ· ÑÐŸÑÐŒÐ°ÑÐ° HTML. (Ð ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ Ð¿ÑÐžÐŽÐµÑÑÑ ÐœÐµÐŒÐœÐŸÐ³ÐŸ Ð¿ÐŸÑÐ°Ð±ÐŸÑÐ°ÑÑ, Ñ.Ðº. ÐŽÐ»Ñ ÐœÐŸÑÐŒÐ°Ð»ÑÐœÐŸÐ¹ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Word Ð² ÑÐŸÑÐŒÐ°Ñ HTML ÑÑÐµÐ±ÑÐµÑÑÑ ÑÐŽÐ°Ð»ÐžÑÑ Ð¿ÐŸÐ±ÐŸÑÐœÑÐµ ÑÐžÐŒÐ²ÐŸÐ»Ñ "&lt;" Ðž "&gt;"; ÐŒÑ Ð¿ÑÐŸÐžÐ·Ð²ÐµÐ»Ðž ÐžÑ
+ ÑÐ¿ÐŸÑÑÐŽÐŸÑÐµÐœÐžÐµ, ÐœÐµ Ð¿ÑÐžÐœÐžÐŒÐ°Ñ Ð²ÐŸ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ Ð¿ÑÐžÐ²ÐµÐŽÐµÐœÐœÑÐµ Ð²ÑÑÐµ ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÐž). ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÑÐŸ, ÑÑÐŸ ÑÐŸÑÐœÐŸ ÑÐ°ÐºÐŸÐ¹ Ð¶Ðµ ÑÐŸÑÐŒÐ°Ñ, ÐºÐ°Ðº ÐŸÐ¿ÐžÑÐ°ÐœÐŸ Ð²ÑÑÐµ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ðž Ð² ÑÐ»ÑÑÐ°Ðµ Word - ÑÐ°Ð¹Ð»ÐŸÐ², ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÑ
+ "&lt;!â" Ðž"~&gt;". ÐšÑÐžÑÑ Ðž ÐžÐœÑÐµÑÐ²Ð°Ð» ÐžÐ³ÐœÐŸÑÐžÑÑÑÑÑÑ.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="classifiers">
+<Title>
+<Text id="564">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ</Text>
+</Title>
+<Content>
+<Text id="565">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐžÐœÐŽÐµÐºÑÐŸÐ² Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐžÐŒÐµÑÐ°ÐŒÐž ÑÐ²Ð»ÑÑÑÑÑ ÐžÐœÐŽÐµÐºÑÑ Titles A-Z ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž dlpeople, Ð° ÑÐ°ÐºÐ¶Ðµ ÐžÐœÐŽÐµÐºÑÑ Subject, How to, Organisation Ðž Titles A-Z Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Humanity Development Library - ÐŸÐŽÐœÐŸÐ¹ ÐžÐ· Ð¿ÐŸÐŽÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ð° ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹. ÐÐ°Ð²ÐžÐ³Ð°ÑÐžÐŸÐœÐœÐŸÐµ ÐŒÐµÐœÑ Ð² Ð²ÐµÑÑ
+ÐœÐµÐ¹ ÑÐ°ÑÑÐž ÑÐºÑÐ°ÐœÐ° ÐœÐ° ÑÐžÑÑÐœÐºÐ°Ñ
+ 3 Ðž 8Ð° ÐžÐŒÐµÐµÑ ÑÑÐœÐºÑÐžÑ search, ÐºÐŸÑÐŸÑÐ°Ñ Ð²ÑÐµÐ³ÐŽÐ° ÑÐœÐ°Ð±Ð¶ÐµÐœÐ° ÐºÐœÐŸÐ¿ÐºÐ°ÐŒÐž ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ. ÐÐœÑÐŸÑÐŒÐ°ÑÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ ÐŽÐ»Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°, ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑÑÑ Ð² ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ Ð±Ð°Ð·Ðµ ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÑÐŽÐ° ÐŸÐœÐ° Ð¿ÐŸÐŒÐµÑÐ°ÐµÑÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°ÐŒÐž, Ð²ÑÐ·ÑÐ²Ð°ÐµÐŒÑÐŒÐž ÐœÐ° ÐºÐŸÐœÐµÑÐœÐŸÐ¹ ÑÑÐ°ÐŽÐžÐž ÑÐ°Ð±ÐŸÑÑ buildcol.pl.</Text>
+<Figure id="azlist_classifier">
+<Title>
+<Text id="566">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ <i>AZList</i></Text>
+</Title>
+<File width="390" height="182" url="images/Dev_Fig_026.png"/>
+</Figure>
+<Text id="567">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ, Ð¿ÐŸÐŽÐŸÐ±ÐœÐŸ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑÐŒ, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑÑÑ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÑÑÐµÑÑÐ²ÑÐµÑ ÑÑÑÐŸÐºÐ°, ÐœÐ°ÑÐžÐœÐ°ÑÑÐ°ÑÑÑ Ñ ÐºÐ»ÑÑÐµÐ²ÐŸÐ³ÐŸ ÑÐ»ÐŸÐ²Ð° classify Ðž ÑÐŸÐ¿ÑÐŸÐ²ÐŸÐ¶ÐŽÐ°ÐµÐŒÐ°Ñ ÐžÐŒÐµÐœÐµÐŒ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° Ðž ÑÑÐµÐ±ÑÐµÐŒÑÑ
+ ÐŸÐ¿ÑÐžÐ¹. ÐÑÐœÐŸÐ²ÐœÐŸÐ¹ ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐŸÐ±ÑÑÐ¶ÐŽÐµÐœÐœÑÐ¹ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="configuration_file"/>, Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÑÑÑÐŸÐºÑ classify AZList âmetadata Title, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð°Ð»ÑÐ°Ð²ÐžÑÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ², ÐžÐ·Ð²Ð»ÐµÐºÐ°Ñ ÐžÑ
+ ÐžÐ· Ð¿ÐŸÐ»Ñ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Title, Ð·Ð°ÑÐµÐŒ ÑÐŸÑÑÐžÑÑÐµÑ ÐžÑ
+ Ðž ÑÐ°Ð·Ð±ÐžÐ²Ð°ÐµÑ Ð¿ÐŸ Ð°Ð»ÑÐ°Ð²ÐžÑÐœÑÐŒ ÐŽÐžÐ°Ð¿Ð°Ð·ÐŸÐœÐ°ÐŒ. ÐÑÐžÐŒÐµÑ Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="azlist_classifier"/>.</Text>
+<Figure id="list_classifier">
+<Title>
+<Text id="568">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ <i>List</i></Text>
+</Title>
+<File width="394" height="143" url="images/Dev_Fig_028.png"/>
+</Figure>
+<Text id="569">ÐÑÐŸÑÑÐµÐ¹ÑÐžÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ, ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÐ¹ List, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="list_classifier"/>. ÐÐœ ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐŸÑÑÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÐµÑ ÐµÐ³ÐŸ Ð±ÐµÐ· ÐºÐ°ÐºÐžÑ
+-Ð»ÐžÐ±ÐŸ Ð°Ð»ÑÐ°Ð²ÐžÑÐœÑÑ
+ Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ². ÐÑÐžÐŒÐµÑÐŸÐŒ ÐŒÐŸÐ³ÑÑ Ð¿ÐŸÑÐ»ÑÐ¶ÐžÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ how to ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐ·ÐŽÐ°ÐœÑ ÑÑÑÐŸÐºÐŸÐ¹ classify List âmetadata Howto Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž<FootnoteRef id="3"/>. ÐÑÑÐ³ÐŸÐ¹ ÑÐœÐžÐ²ÐµÑÑÐ°Ð»ÑÐœÐŸÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ ÑÐ¿ÐžÑÐºÐ° DateList, ÐºÐŸÑÐŸÑÑÐ¹ Ð³ÐµÐœÐµÑÐžÑÑÐµÑ ÑÐ¿ÐžÑÐŸÐº ÐŽÐ°Ñ, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="datelist_classifier"/>. (ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ DateList ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone Archives).</Text>
+<Figure id="datelist_classifier">
+<Title>
+<Text id="570">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ <i>DateList</i></Text>
+</Title>
+<File width="390" height="159" url="images/Dev_Fig_030.png"/>
+</Figure>
+<Text id="571">ÐÑÑÐ³ÐžÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ Ð³ÐµÐœÐµÑÐžÑÑÑÑ ÑÑÑÑÐºÑÑÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°, ÐºÐŸÑÐŸÑÑÐµ ÑÐ²Ð»ÑÑÑÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐžÐŒÐž. ÐÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐžÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð² ÑÐ»ÑÑÐ°Ðµ Ð¿ÑÐµÐŽÐŒÐµÑÐœÑÑ
+ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐ¹ Ðž Ð¿ÐŸÐŽÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐ¹, Ð° ÑÐ°ÐºÐ¶Ðµ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐŸÐœÐœÑÑ
+ ÐžÐµÑÐ°ÑÑ
+ÐžÐ¹. Ð€Ð°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÑÑÐŸÐºÑ classify Hierarchy âhflle sub.txt âmetadata Subject âsort Title, Ðž ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="hierarchy_classifier"/> Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐŽÐµÑÑ Ð¿ÑÐµÐŽÐŒÐµÑÐœÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑ, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÑÑ Ð² Ð±ÑÐŸÑÐ·ÐµÑÐµ. ÐÐºÐŸÐœÐºÐ° "ÐºÐœÐžÐ¶ÐœÐ°Ñ Ð¿ÐŸÐ»ÐºÐ°" Ñ Ð²ÑÐŽÐµÐ»ÐµÐœÐœÑÐŒ Ð¶ÐžÑÐœÑÐŒ ÑÑÐžÑÑÐŸÐŒ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐŒ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑ Ð¿ÐµÑÐ²ÑÐ¹ ÑÑÐŸÐ²ÐµÐœÑ; Ð²ÑÑÐµ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐŽÐµÑÑ Ð¿ÑÐµÐŽÐŒÐµÑÐœÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÑ, Ðº ÐºÐŸÑÐŸÑÐŸÐ¹ Ð¿ÑÐžÐœÐ°ÐŽÐ»ÐµÐ¶ÐžÑ ÑÐ¿ÐŸÐŒÑÐœÑÑÑÐ¹ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº. Ð ÑÑÐŸÐŒ Ð¿ÑÐžÐŒÐµÑÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐŸÐœÐœÐ°Ñ ÐžÐµÑÐ°ÑÑ
+ÐžÑ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² Ð¿ÑÐŸÑÑÐŸÐŒ ÑÐµÐºÑÑÐŸÐ²ÐŸÐŒ ÑÐŸÑÐŒÐ°ÑÐµ Ð² ÑÐ°Ð¹Ð»Ðµ sub.txt.</Text>
+<Figure id="hierarchy_classifier">
+<Title>
+<Text id="572">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ <i>Hierarchy</i></Text>
+</Title>
+<File width="394" height="198" url="images/Dev_Fig_032.png"/>
+</Figure>
+<Text id="573">ÐÑÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ Ð³ÐµÐœÐµÑÐžÑÑÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÑÑ ÑÑÑÑÐºÑÑÑÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÐžÐœÐŽÐµÐºÑÐ° Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°. ÐÐ° ÑÐ°ÐŒÐŸÐŒ ÐœÐžÐ¶ÐœÐµÐŒ ÑÑÐŸÐ²ÐœÐµ ÐžÐµÑÐ°ÑÑ
+ÐžÐž (Ñ.Ðµ. Ð»ÐžÑÑÐµ) ÐŸÐ±ÑÑÐœÐŸ ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÐœÐŸ Ð² ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°Ñ
+ - ÑÑÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ñ. ÐÐœÑÑÑÐµÐœÐœÐžÐµ ÑÐ·Ð»Ñ ÐžÐµÑÐ°ÑÑ
+ÐžÐž - ÑÑÐŸ Vlist, Hlist, ÐžÐ»Ðž Datelist. Vlist - ÑÑÐŸ ÑÐ¿ÐžÑÐŸÐº ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ², Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑÑ
+ Ð²ÐµÑÑÐžÐºÐ°Ð»ÑÐœÐŸ, Ð²ÐœÐžÐ·Ñ ÑÑÑÐ°ÐœÐžÑÑ, Ð¿ÐŸÐŽÐŸÐ±ÐœÐŸ ÐžÐœÐŽÐµÐºÑÑ "how to" Ð² ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÑÐŒ.ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="list_classifier"/>). Hlist ÑÐ°ÑÐ¿ÐŸÐ»Ð°Ð³Ð°ÐµÑÑÑ Ð³ÐŸÑÐžÐ·ÐŸÐœÑÐ°Ð»ÑÐœÐŸ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, AZList, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÑÐ¹ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="azlist_classifier"/>,- ÑÑÐŸ ÐžÐµÑÐ°ÑÑ
+ÐžÑ Ñ ÐŽÐ²ÑÐŒÑ ÑÑÐŸÐ²ÐœÑÐŒÐž Ð²ÐœÑÑÑÐµÐœÐœÐžÑ
+ ÑÐ·Ð»ÐŸÐ², ÑÐŸÑÑÐŸÑÑÐžÑ
+ ÐžÐ· Hlist (Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐŒ A-Z ) Ñ ÐŽÐŸÑÐµÑÐœÐžÐŒÐž Ð·Ð°Ð¿ÐžÑÑÐŒÐž Vlists. Ð­ÑÐž ÐŽÐŸÑÐµÑÐœÐžÐµ Ð·Ð°Ð¿ÐžÑÐž ÑÐ²Ð»ÑÑÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒÐž. Datelist (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="datelist_classifier"/>) ÑÐ²Ð»ÑÐµÑÑÑ ÐŸÑÐŸÐ±ÑÐŒ Ð²ÐžÐŽÐŸÐŒ Vlist, Ðž Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑ Ð²ÑÐ±ÐŸÑÐºÑ Ð¿ÐŸ Ð³ÐŸÐŽÑ Ðž  ÐŒÐµÑÑÑÑ.</Text>
+<Text id="574">Ð¡ÑÑÐŸÐºÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ² Ð² ÑÐ°Ð¹Ð»Ð°Ñ
+ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÑ
+ Ð°ÑÐ³ÑÐŒÐµÐœÑ metadata, ÐžÐŽÐµÐœÑÐžÑÐžÑÐžÑÑÑÑÐžÐ¹ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, Ð¿ÐŸ ÐºÐŸÑÐŸÑÑÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÑÐžÑÐŸÐ²Ð°ÐœÑ Ðž ÐŸÑÑÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÑ. ÐÑÐ±ÐŸÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÐ°Ñ ÐœÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž, Ð±ÑÐŽÐµÑ ÐžÐ·Ð±Ð°Ð²Ð»ÐµÐœ ÐŸÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° (ÐœÐŸ ÐŸÐœ Ð²ÑÐµ Ð¶Ðµ ÐžÐœÐŽÐµÐºÑÐžÑÑÐµÑÑÑ, Ðž ÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸ, ÐŽÐŸÑÑÑÐ¿ÐµÐœ ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ°). ÐÑÐ»Ðž ÐœÐžÐºÐ°ÐºÐŸÐ¹ Ð¿Ð°ÑÐ°ÐŒÐµÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐœÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœ, Ð²ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð²ÐºÐ»ÑÑÐ°ÑÑÑÑ Ð² ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ Ð² ÑÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐŸÐœÐž Ð¿ÐŸÑÑÑÐ¿Ð°ÑÑ Ð² Ñ
+ÐŸÐŽÐµ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ. Ð­ÑÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð² ÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÑÐ¿ÐžÑÐŸÐº Ð²ÑÐµÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² Ð²Ð°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Table id="greenstone_classifiers">
+<Title>
+<Text id="575">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="576"><b>ÐÑÐ³ÑÐŒÐµÐœÑ</b></Text>
+</th>
+<th width="305">
+<Text id="577"><b>ÐÐµÐ¹ÑÑÐ²ÐžÐµ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="578"><i>Hierarchy</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="579">ÐÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐ°Ñ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="580"><i>hfile</i></Text>
+</th>
+<th width="305">
+<Text id="581">Ð€Ð°Ð¹Ð» ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="582"><i>metadata</i></Text>
+</th>
+<th width="305">
+<Text id="583">Ð­Ð»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ ÑÐµÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð²ÐŸÐ¿ÑÐµÐºÐž ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑÑ hfile</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="584"><i>sort</i></Text>
+</th>
+<th width="305">
+<Text id="585">Ð­Ð»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÐŸÑÑÐžÑÑÑÑÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ Ð»ÐžÑÑÐ° (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ - Title)</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="586"><i>buttonname</i></Text>
+</th>
+<th width="305">
+<Text id="587">ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐœÐŸÐ¿ÐºÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐ¹ ÐŽÐ»Ñ ÐŸÐ±ÑÐ°ÑÐµÐœÐžÑ Ðº ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ - Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+) </Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="588"><i>List</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="589">ÐÐ»ÑÐ°Ð²ÐžÑÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="590"><i>metadata</i></Text>
+</th>
+<th width="305">
+<Text id="591">ÐÐºÐ»ÑÑÐµÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÑ
+ ÑÑÐŸÑ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="592"><i>buttonname</i></Text>
+</th>
+<th width="305">
+<Text id="593">ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐœÐŸÐ¿ÐºÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐ¹ ÐŽÐ»Ñ ÐŸÐ±ÑÐ°ÑÐµÐœÐžÑ Ðº ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ - Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="594"><i>SectionList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="595">Ð¡Ð¿ÐžÑÐŸÐº ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² </Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="596"><i>AZList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="597">Ð¡Ð¿ÐžÑÐŸÐº ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÑÐ°Ð·Ð±ÐžÑÑÑ
+ ÐœÐ° Ð°Ð»ÑÐ°Ð²ÐžÑÐœÑÐµ ÐŽÐžÐ°Ð¿Ð°Ð·ÐŸÐœÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="598"><i>metadata</i></Text>
+</th>
+<th width="305">
+<Text id="599">ÐÐºÐ»ÑÑÐµÐœÐžÐµ Ð²ÑÐµÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÑ
+ ÑÑÐŸÑ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</th>
+</tr>
+<tr>
+<th width="132"/>
+<th width="92">
+<Text id="600"><i>buttonname</i></Text>
+</th>
+<th width="305">
+<Text id="601">ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐœÐŸÐ¿ÐºÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐ¹ ÐŽÐ»Ñ ÐŸÐ±ÑÐ°ÑÐµÐœÐžÑ Ðº ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ - Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+) ÐÐŸÐŽÐŸÐ±ÐœÐŸ AZList,ÐœÐŸ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð²ÑÐµ ÑÐ°Ð·ÐŽÐµÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐÐŸÐŽÐŸÐ±ÐœÐŸ AZList, ÐœÐŸ ÑÐŸÑÑÐžÑÑÐµÑ Ð¿ÐŸ ÐŽÐ°ÑÐµ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="602"><i>AZSectionList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="603">ÐÐŸÐŽÐŸÐ±ÐœÐŸ AZList,ÐœÐŸ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð²ÑÐµ ÑÐ°Ð·ÐŽÐµÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="604"><i>DateList</i></Text>
+</th>
+<th width="92"/>
+<th width="305">
+<Text id="605">ÐÐŸÐŽÐŸÐ±ÐœÐŸ AZList, ÐœÐŸ ÑÐŸÑÑÐžÑÑÐµÑ Ð¿ÐŸ ÐŽÐ°ÑÐµ</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="606">Ð¢ÐµÐºÑÑÐžÐ¹ ÐœÐ°Ð±ÐŸÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ² Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="greenstone_classifiers"/>. ÐÐ°Ðº Ð±ÑÐ»ÐŸ ÑÐ°ÑÑÐŒÐŸÑÑÐµÐœÐŸ ÑÐ°ÐœÐµÐµ, ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ Ð»ÑÐ±ÐŸÐŒ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐž, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ pluginfo.pl. Ð¢Ð°ÐºÐ¶Ðµ Ð² ÑÐ»ÑÑÐ°Ðµ Ñ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°ÐŒÐž ÑÑÑÐµÑÑÐ²ÑÐµÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° classinfo.pl, ÐºÐŸÑÐŸÑÐ°Ñ ÐŽÐ°ÐµÑ Ð²Ð°ÐŒ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ Ð»ÑÐ±ÐŸÐŒ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐµ Ðž ÐŽÐŸÑÑÑÐ¿ÐœÑÑ
+ ÐµÐŒÑ ÐŸÐ¿ÑÐžÑÑ
+.</Text>
+<Text id="607">ÐÑÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ Ð¿ÑÐžÐœÐžÐŒÐ°ÑÑ Ð°ÑÐ³ÑÐŒÐµÐœÑ buttonname, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑÐžÐ¹ ÐœÐ°ÐŽÐ¿ÐžÑÑ ÐœÐ° ÐœÐ°Ð²ÐžÐ³Ð°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐœÐŸÐ¿ÐºÐµ Greenstone, ÐºÐŸÑÐŸÑÐ°Ñ Ð²ÑÐ·ÑÐ²Ð°ÐµÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+). ÐÐœÐŸÐ¿ÐºÐž ÑÑÑÐµÑÑÐ²ÑÑÑ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐžÐ¿Ð° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Dublin Core Ðž ÐŽÐ»Ñ ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÐŽÑÑÐ³ÐžÑ
+ ÑÐžÐ¿ÐŸÐ² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+<Text id="608">ÐÐ°Ð¶ÐŽÑÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ Ð¿ÐŸÐ»ÑÑÐ°ÐµÑ ÐœÐµÑÐ²ÐœÐŸÐµ ÐžÐŒÑ, Ð·Ð°Ð²ÐžÑÑÑÐµÐµ ÐŸÑ ÐµÐ³ÐŸ Ð¿ÐŸÐ·ÐžÑÐžÐž Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÑÑÐµÑÐžÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ, ÑÐºÐ°Ð·Ð°ÐœÐœÑÐ¹ Ð² ÑÐ°Ð¹Ð»Ðµ, ÐœÐ°Ð·ÑÐ²Ð°ÑÑ CL3. Ð­ÑÐž ÐžÐŒÐµÐœÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹ Ð¿ÐŸÐ»ÐµÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÐžÐµÑÐ°ÑÑ
+ÐžÐž ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°.</Text>
+<Text id="609">ÐÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐœÐ°Ð¿ÐžÑÐ°ÐœÑ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž perllib/classify. Development Library ÐžÐŒÐµÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ Ð¿ÐŸ ÐžÐŒÐµÐœÐž HDLList, ÐºÐŸÑÐŸÑÑ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐŒÐµÐœÑÑÐµÐœÐœÑÐŒ Ð²Ð°ÑÐžÐ°ÐœÑÐŸÐŒ AZList.</Text>
+<Subsection id="list_classifiers">
+<Title>
+<Text id="610">Ð¡Ð¿ÐžÑÐŸÐº ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="611">ÐÐžÐ¶Ðµ Ð¿ÑÐžÐ²ÐµÐŽÐµÐœ ÑÐ¿ÐžÑÐŸÐº ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ²:</Text>
+<BulletList>
+<Bullet>
+<Text id="612"><i>SectionList</i>âÐ¿ÐŸÑ
+ÐŸÐ¶ ÐœÐ° List, ÐœÐŸ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ² Ð²ÑÑÑÑÐ¿Ð°ÑÑ Ð»ÐžÑÑÑ, Ð° Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÑ. ÐÐºÐ»ÑÑÐ°ÐµÑ Ð²ÑÐµ ÑÐ°Ð·ÐŽÐµÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÐºÑÐŸÐŒÐµ Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÐµ ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ  ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÑÐ¿ÐžÑÐºÐ° ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ²   (ÑÑÐ°ÑÐµÐ¹, Ð³Ð»Ð°Ð² Ðž Ñ.ÐŽ.), ÐºÐ°ÐºÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Computists' Weekly   (ÐŽÐŸÑÑÑÐ¿ÐœÐ° ÐœÐ° ÑÐ°Ð¹ÑÐµ nzdl.org), Ð³ÐŽÐµ ÐºÐ°Ð¶ÐŽÑÐ¹ Ð²ÑÐ¿ÑÑÐº - ÑÑÐŸ ÐŸÑÐŽÐµÐ»ÑÐœÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐœÐµÐ·Ð°Ð²ÐžÑÐžÐŒÑ ÑÑÐ°ÑÐµÐ¹, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÑ
+ÑÑ Ð² ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÑÑ
+ ÑÐ°Ð·ÐŽÐµÐ»Ð°Ñ
+.</Text>
+</Bullet>
+<Bullet>
+<Text id="613"><i>AZList</i>âÐ³ÐµÐœÐµÑÐžÑÑÐµÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑ Ñ ÐŽÐ²ÑÐŒÑ ÑÑÐŸÐ²ÐœÑÐŒÐž, Ð²ÐºÐ»ÑÑÐ°ÑÑÑÑ HLis ÐŽÐŸÑÐµÑÐœÐžÐµ Ð·Ð°Ð¿ÐžÑÐž ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ.</Text>
+</Bullet>
+<Bullet>
+<Text id="614"><i>AZSectionList</i>âÐ¿ÐŸÑ
+ÐŸÐ¶ ÐœÐ° AZList, ÐœÐŸ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ² Ð²ÑÑÑÑÐ¿Ð°ÑÑ Ð»ÐžÑÑÑ Ð° ÐœÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="615"><i>DateList</i>âÐ¿ÐŸÑ
+ÐŸÐ¶ ÐœÐ° AZList, Ð·Ð° ÐžÑÐºÐ»ÑÑÐµÐœÐžÐµÐŒ ÑÐŸÐ³ÐŸ, ÑÑÐŸ Ð²ÐµÑÑ
+ÐœÐžÐ¹ ÑÑÐŸÐ²ÐµÐœÑ HLL Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐŽÐµÐ»Ð°ÑÑ Ð²ÑÐ±ÐŸÑÐºÑ Ð¿ÐŸ Ð³ÐŸÐŽÑ, Ð° ÐµÐ³ÐŸ ÐŽÐŸÑÐµÑÐœÐžÐµ Ð·Ð°Ð¿ÐžÑÐž - DateLists, Ð° Ðº VLists. ÐÐœÐ°ÑÐµÐœÐžÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ - Date.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="the_hierarchy_classifier">
+<Title>
+<Text id="616">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ ÐžÐµÑÐ°ÑÑ
+ÐžÐž</Text>
+</Title>
+<Content>
+<Text id="617">ÐÑÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÑÐ²Ð»ÑÑÑÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐžÐŒÐž. ÐÐŽÐœÐ°ÐºÐŸ, ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ: ÑÐ¿ÐžÑÐºÐ°, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐµ Ð²ÑÑÐµ, ÐžÐŒÐµÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐœÐŸÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÑÑÐŸÐ²ÐœÐµÐ¹, ÑÐŸÑÑ ÐºÐ°Ðº ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ "ÐžÐµÑÐ°ÑÑ
+ÐžÐž", ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐµ Ð² ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ, ÐžÐŒÐµÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐ»ÑÐœÐŸÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÑÑÐŸÐ²ÐœÐµÐ¹. ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÐž Ð±ÐŸÐ»ÐµÐµ ÑÐ»ÐŸÐ¶Ðž ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ, ÑÐµÐŒ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÑÐ¿ÐžÑÐºÐ°.</Text>
+<Figure id="part_of_the_file_sub">
+<Title>
+<Text id="618">Part of the file <i>sub.txt</i></Text>
+</Title>
+<CodeLine>1           1       "General reference"</CodeLine>
+<CodeLine>1.2       1.2       "Dictionaries, glossaries, language courses, terminology</CodeLine>
+<CodeLine>2           2       "Sustainable Development, International cooperation, Pro</CodeLine>
+<CodeLine>2.1       2.1       "Development policy and theory, international cooperatio</CodeLine>
+<CodeLine>2.2       2.2       "Development, national planning, national plans"</CodeLine>
+<CodeLine>2.3       2.3       "Project planning and evaluation (incl. project managem</CodeLine>
+<CodeLine>2.4       2.4       "Regional development and planning incl. regional profil</CodeLine>
+<CodeLine>2.5       2.5       "Nongovernmental organisations (NGOs) in general, self-</CodeLine>
+<CodeLine>2.6       2.6       "Organisations, institutions, United Nations (general, d</CodeLine>
+<CodeLine>2.6.1   2.6.1       "United Nations"</CodeLine>
+<CodeLine>2.6.2   2.6.2       "International organisations"</CodeLine>
+<CodeLine>2.6.3   2.6.3       "Regional organisations"</CodeLine>
+<CodeLine>2.6.5   2.6.5       "European Community - European Union"</CodeLine>
+<CodeLine>2.7       2.7       "Sustainable Development, Development models and example</CodeLine>
+<CodeLine>2.8       2.8       "Basic Human Needs"</CodeLine>
+<CodeLine>2.9       2.9       "Hunger and Poverty Alleviation"</CodeLine>
+</Figure>
+<Text id="619">ÐÑÐ³ÑÐŒÐµÐœÑ hflle ÐŽÐ°ÐµÑ ÐžÐŒÑ ÑÐ°Ð¹Ð»Ð°, ÐºÐ°Ðº Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="part_of_the_file_sub"/>, ÐºÐŸÑÐŸÑÐŸÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐ°Ð¶ÐŽÐ°Ñ ÑÑÑÐŸÐºÐ° ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÐŸÐŽÐœÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÑ, Ð° ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÑÐŸÑÑÐŸÑÑ ÐžÐ· ÑÑÐµÑ
+ ÑÐ°ÑÑÐµÐ¹:</Text>
+<BulletList>
+<Bullet>
+<Text id="620">ÐÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÐµÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ (Ð·Ð°ÐŽÐ°ÐœÐœÐŸÐ³ÐŸ Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐŒ metadata) Ð¿ÐŸ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž.</Text>
+</Bullet>
+<Bullet>
+<Text id="621">ÐÐ°ÑÐºÐµÑ Ð¿ÐŸÐ·ÐžÑÐžÐž-Ð²-ÐžÐµÑÐ°ÑÑ
+ÐžÐž, Ð² ÐŒÐœÐŸÐ³Ð¿ÐµÑÐžÐŸÐŽÐœÐŸÐ¹ ÑÐžÑÐ»ÐŸÐ²ÐŸÐ¹ ÑÐŸÑÐŒÐµ, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ 2,2.12,2.12.6.</Text>
+</Bullet>
+<Bullet>
+<Text id="622">ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž (ÐµÑÐ»Ðž ÐŸÐœÐŸ ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð¿ÑÐŸÐ±ÐµÐ»Ñ, ÑÐŸ ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð±ÑÑÑ Ð·Ð°ÐºÐ»ÑÑÐµÐœÐŸ Ð² ÐºÐ°Ð²ÑÑÐºÐž).</Text>
+</Bullet>
+</BulletList>
+<Text id="623">ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="part_of_the_file_sub"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐ° ÑÐ°ÑÑÑ ÑÐ°Ð¹Ð»Ð° sub.txt, ÑÐŸÐ·ÐŽÐ°ÑÑÐµÐ³ÐŸ Ð¿ÐŸÐŽÑÐžÐœÐµÐœÐœÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Development Library (Ðž Ð² ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž). Ð­ÑÐŸÑ Ð¿ÑÐžÐŒÐµÑ - ÐœÐµÐŒÐœÐŸÐ³ÐŸ Ð·Ð°Ð¿ÑÑÐ°ÐœÐœÑÐ¹, Ñ.Ðº. ÐœÐŸÐŒÐµÑ, ÑÐºÐ°Ð·ÑÐ²Ð°ÑÑÐžÐ¹ ÐœÐ° ÐžÐµÑÐ°ÑÑ
+ÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ²Ð°Ð¶ÐŽÑ ÐœÐ° ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÑÑÑÐŸÐºÐµ. Ð¢ÐžÐ¿ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Hierarchy Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°Ñ
+ ÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑÐŒÐž Ð² ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐŸÐ¹ ÑÐžÑÐ»ÐŸÐ²ÐŸÐ¹ ÑÐŸÑÐŒÐµ, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÐ±ÑÑÑÐœÑÐµÑ Ð¿ÐµÑÐ²ÐŸÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ. ÐÑÐŸÑÐŸÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐœÐŸÐŒÐµÑÐ° ÑÑÐµÐ±ÑÐµÑÑÑ ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÐžÐµÑÐ°ÑÑ
+ÐžÐž, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÐµÑÑÑ Ð±ÑÐŸÑÐ·ÐµÑÐŸÐŒ ÐžÐµÑÐ°ÑÑ
+ÐžÐž.</Text>
+<Text id="624">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ hierarchy ÐžÐŒÐµÐµÑ ÐŸÐ¿ÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐ¹ Ð°ÑÐ³ÑÐŒÐµÐœÑ sort, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ, ÐºÐ°Ðº ÑÐ¿ÐŸÑÑÐŽÐŸÑÐžÐ²Ð°ÑÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² Ð»ÐžÑÑÐ°Ñ
+. ÐÑÐ±ÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ ÐºÐ°Ðº ÐºÐ»ÑÑ ÑÐŸÑÑÐžÑÐŸÐ²ÐºÐž. ÐÐœÐ°ÑÐµÐœÐžÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐŽÐŸÐ»Ð¶ÐœÐŸ ÑÐŸÐ·ÐŽÐ°ÑÑ ÑÐ¿ÐžÑÐŸÐº Ð² ÑÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÑÐŸÑ
+ÐŸÐŽÐžÐ»Ðž Ð¿ÑÐŸÑÐµÑÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ. Ð£Ð¿ÐŸÑÑÐŽÐŸÑÐµÐœÐžÐµ Ð²ÐŸ Ð²ÐœÑÑÑÐµÐœÐœÐžÑ
+ ÑÐ·Ð»Ð°Ñ
+ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ Ð¿ÐŸÑÑÐŽÐºÐŸÐŒ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÑÐ»ÐµÐŒÐµÐœÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ Ð² Ð°ÑÐ³ÑÐŒÐµÐœÑÐµ hfile.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_classifiers_work">
+<Title>
+<Text id="625">ÐÐ°Ðº ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ</Text>
+</Title>
+<Content>
+<Text id="626">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÑÐ²Ð»ÑÑÑÑÑ ÐŸÐ±ÑÐµÐºÑÐ°ÐŒÐž ÑÐ·ÑÐºÐ° Perl, Ð¿ÐŸÐ»ÑÑÐµÐœÐœÑÐŒÐž ÐŸÑ BasClas.pm Ðž Ñ
+ÑÐ°ÐœÐžÐŒÑÐŒÐž Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž perllib/classijy. ÐÐœÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÑÐŸÐ³ÐŽÐ°, ÐºÐŸÐ³ÐŽÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐ¶Ðµ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐ°. ÐÑÐž Ð·Ð°Ð¿ÑÑÐºÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ² Ð²ÑÐ¿ÐŸÐ»ÐœÑÑÑÑÑ ÑÐ»ÐµÐŽÑÑÑÐžÐµ ÑÐ°Ð³Ðž.</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="627">ÐÐµÑÐŸÐŽ new ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐŸÐ±ÑÐµÐºÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="628">ÐÐµÑÐŸÐŽ init ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·ÐžÑÑÐµÑ ÐŸÐ±ÑÐµÐºÑ Ð¿ÐŸ ÑÐ°ÐºÐžÐŒ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ°ÐŒ, ÐºÐ°Ðº ÑÐžÐ¿ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐœÐŸÐ¿ÐºÐž Ðž ÐºÑÐžÑÐµÑÐžÐž ÑÐŸÑÑÐžÑÐŸÐ²ÐºÐž.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="629">ÐÐµÑÐŸÐŽ classify ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŸÐŽÐžÐœ ÑÐ°Ð· ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ðž Ñ
+ÑÐ°ÐœÐžÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž, Ð¿ÑÐŸÐžÐ·Ð²ÐµÐŽÐµÐœÐœÐŸÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐŒ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐŸÐ±ÑÐµÐºÑÐ°.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="630">ÐÐµÑÐŸÐŽ get_classijy_info Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž   Ð¿ÑÐŸÑÐµÑÑÑ ÐºÐŸÐŒÐ¿ÐŸÐœÐŸÐ²ÐºÐž, ÐºÐŸÑÐŸÑÑÐ¹ Ð·Ð°Ð¿ÐžÑÑÐ²Ð°ÐµÑ ÐµÐµ Ð² ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÑÑ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐ»Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ, Ð²ÐŸ Ð²ÑÐµÐŒÑ ÑÐ°Ð±ÐŸÑÑ Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="631">ÐÐµÑÐŸÐŽ classify ÐŸÑÑÑÐºÐžÐ²Ð°ÐµÑ OID ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, Ðž Ð² ÑÐ»ÑÑÐ°Ðµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÐž, Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ ÑÐŸÑÑÐžÑÐŸÐ²ÐºÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÐµÑÐŸÐŽ get_classify_info Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑ Ð²ÑÑ ÑÐŸÑÑÐžÑÐŸÐ²ÐºÑ Ðž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐŒ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÑ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð² ÑÐ»ÑÑÐ°Ðµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° AZList, ÐŸÐœ ÑÐ°Ð·Ð±ÐžÐ²Ð°ÐµÑ ÑÐ¿ÐžÑÐŸÐº ÐœÐ° Ð°Ð»ÑÐ°Ð²ÐžÑÐœÑÐµ ÐŽÐžÐ°Ð¿Ð°Ð·ÐŸÐœÑ.</Text>
+<Text id="632">ÐÑÐŸÑÐµÑÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·ÐžÑÑÐµÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ, ÐºÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐŸÐ±ÑÐµÐºÑ builder Ð±ÑÐŽÐµÑ ÑÐŸÐ·ÐŽÐ°Ðœ. ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž ÑÐŸÐ·ÐŽÐ°ÑÑÑÑ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐºÐŸÐ³ÐŽÐ° classify.pm, Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸ ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÐ¹ÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž perllib Greenstone, ÑÐŸÐ·ÐŽÐ°ÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÑÑ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+<Table id="items_appearing_in_format_strings">
+<Title>
+<Text id="633">Ð­Ð»ÐµÐŒÐµÐœÑÑ âÑÐŸÑÐŒÐ°ÑÐ° ÑÑÑÐŸÐºÐžâ</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="634"><i>[Text]</i></Text>
+</th>
+<th width="397">
+<Text id="635">Ð¢ÐµÐºÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="636"><i>[link] âŠ [/link]</i></Text>
+</th>
+<th width="397">
+<Text id="637">HTML ÐŽÐ»Ñ ÑÐ²ÑÐ·Ðž ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="638"><i>[icon]</i></Text>
+</th>
+<th width="397">
+<Text id="639">Ð¡ÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐ°Ñ ÐžÐºÐŸÐœÐºÐ° (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐœÐµÐ±ÐŸÐ»ÑÑÐ°Ñ ÑÐµÐºÑÑÐŸÐ²Ð°Ñ ÐžÐºÐŸÐœÐºÐ° Ð² ÑÑÑÐŸÐºÐµ Search Results)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="640"><i>[num]</i></Text>
+</th>
+<th width="397">
+<Text id="641">ÐÐŸÐŒÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° (ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÐŸÑÐ»Ð°ÐŽÐºÐž).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="642"><i>[metadata-name]</i></Text>
+</th>
+<th width="397">
+<Text id="643">ÐÐœÐ°ÑÐµÐœÐžÐµ ÑÑÐŸÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ <i>[Title]</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="formatting_greenstone_output">
+<Title>
+<Text id="644">ÐÑÑ
+ÐŸÐŽÐœÐŸÐ¹ ÑÐŸÑÐŒÐ°Ñ Greenstone</Text>
+</Title>
+<Content>
+<Text id="645">Web-ÑÑÑÐ°ÐœÐžÑÑ, ÐºÐŸÑÐŸÑÑÐµ Ð²Ñ Ð²ÐžÐŽÐžÑÐµ Ð¿ÑÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž Greenstone, ÐœÐµ ÑÐŸÐ·ÐŽÐ°Ð²Ð°Ð»ÐžÑÑ Ð·Ð°ÑÐ°ÐœÐµÐµ, Ð° Ð±ÑÐ»Ðž ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÑ "ÐœÐ° Ð»ÐµÑÑ", Ð¿ÐŸ ÐŒÐµÑÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÐž. ÐÐ°ÑÑÑÐŸÐ¹ÐºÐ° Ð²ÐœÐµÑÐœÐµÐ³ÐŸ Ð²ÐžÐŽÐ° ÐŒÐœÐŸÐ³ÐžÑ
+ Ð°ÑÐ¿ÐµÐºÑÐŸÐ² ÑÑÑÐ°ÐœÐžÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ "ÑÐŸÑÐŒÐ°ÑÐ° ÑÑÑÐŸÐº". Ð¡ÑÑÐŸÐºÐž ÑÐŸÑÐŒÐ°ÑÐ° ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑÑ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð²Ð²ÐŸÐŽÑÑÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÐŸÑÐŒÐ°Ñ ÐºÐ»ÑÑÐµÐ²ÑÑ
+ ÑÐ»ÐŸÐ², ÑÐŸÐ¿ÑÐŸÐ²ÐŸÐ¶ÐŽÐ°ÐµÐŒÑÐ¹ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµÐŒ ÑÐ»ÐµÐŒÐµÐœÑÐ°, Ðº ÐºÐŸÑÐŸÑÐŸÐŒÑ ÑÐŸÑÐŒÐ°Ñ ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ. ÐÑÑÑ ÐŽÐ²Ð° ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð²ÐžÐŽÐ° ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑÑÑ ÑÑÑÐŸÐºÐ°ÐŒÐž ÑÐŸÑÐŒÐ°ÑÐ°. ÐÐµÑÐ²ÑÐ¹ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐžÐœÑÑÑÑÐŒÐµÐœÑÑ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐžÐ»Ðž ÑÐ°ÑÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÑÐŸÑÐŸÐ¹ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÑÐ¿ÐžÑÐºÐž, Ð¿ÑÐŸÐžÐ·Ð²ÐµÐŽÐµÐœÐœÑÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°ÐŒÐž ÐžÐ»Ðž Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÐµ ÑÐ¿ÐžÑÐºÐž. ÐÑÐµ ÑÑÑÐŸÐºÐž ÑÐŸÑÐŒÐ°ÑÐ° ÐžÐœÑÐµÑÐ¿ÑÐµÑÐžÑÑÑÑÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÑÑÐ°ÐœÐžÑÑ. Ð ÑÐ²ÑÐ·Ðž Ñ ÑÐµÐŒ, ÑÑÐŸ Ð²ÐœÐµÑÐµÐœÐœÑÐµ Ð²Ð°ÐŒÐž ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð²ÑÑÑÐ¿Ð°ÑÑ Ð² ÑÐžÐ»Ñ Ñ ÐŒÐŸÐŒÐµÐœÑÐ° ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐžÑ ÐžÑ
+ Ð² collect.cfg, ÑÐºÑÐ¿ÐµÑÐžÐŒÐµÐœÑ ÑÐŸ ÑÑÑÐŸÐºÐ°ÐŒÐž ÑÐŸÑÐŒÐ°ÑÐ° ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ Ð±ÑÑÑÑÑÐŒ Ðž Ð¿ÑÐŸÑÑÑÐŒ.</Text>
+<Text id="646">Ð Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="items_appearing_in_format_strings"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÑ, Ð·Ð°ÐŽÐ°ÑÑÐžÐµ ÑÐŸÑÐŒÐ°Ñ, ÐºÐŸÑÐŸÑÑÐµ Ð·Ð°ÑÑÐ°Ð³ÐžÐ²Ð°ÑÑ Ð¿ÑÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÐ¿ÑÐžÑ DocumentButtons ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑ ÑÐµÐŒ, ÐºÐ°ÐºÐžÐµ ÐºÐœÐŸÐ¿ÐºÐž ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÑ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐŽÐµÑÑ string - ÑÐ¿ÐžÑÐŸÐº ÐºÐœÐŸÐ¿ÐŸÐº (ÐŸÑÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÐŽÑÑÐ³ ÐŸÑ ÐŽÑÑÐ³Ð° |), ÑÑÐŸ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Detach, Highlight, Expand Text Ðž Expand Contents (ÐÑÐŽÐµÐ»ÐžÑÑ, ÐÐŸÐŽÑÐ²ÐµÑÐžÑÑ, Ð Ð°Ð·Ð²ÐµÑÐœÑÑÑ Ð¢ÐµÐºÑÑ Ðž Ð Ð°Ð·Ð²ÐµÑÐœÑÑÑ Ð¡ÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ).ÐÐµÑÐµÑÐ¿ÐŸÑÑÐŽÐŸÑÐµÐœÐžÐµ ÑÐ¿ÐžÑÐºÐ° Ð¿ÐµÑÐµÑÐ¿ÐŸÑÑÐŽÐŸÑÐžÐ²Ð°ÐµÑ Ðž ÐºÐœÐŸÐ¿ÐºÐž.</Text>
+<Table id="the_format_options">
+<Title>
+<Text id="647">ÐÐ¿ÑÐžÐž format</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="246">
+<Text id="648"><i>format DocumentImages true/false</i></Text>
+</th>
+<th width="283">
+<Text id="649">ÐÑÐ»Ðž true, ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÐµÑ ÑÐžÑÑÐœÐŸÐº ÐŸÐ±Ð»ÐŸÐ¶ÐºÐž Ð² Ð²ÐµÑÑ
+ÐœÐµÐŒ Ð»ÐµÐ²ÐŸÐŒ ÑÐ³Ð»Ñ ÑÑÑÐ°ÐœÐžÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ -false)</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="650"><i>format DocumentHeading formatstring</i></Text>
+</th>
+<th width="283">
+<Text id="651">formatstring       ÐÑÐ»Ðž Documentlmages   - false, ÑÐŸÑÐŒÐ°Ñ ÑÑÑÐŸÐºÐž ÐºÐŸÐœÑÑÐŸÐ»ÐžÑÑÐµÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° Ð² Ð²ÐµÑÑ
+ÐœÐµÐ¹ Ð»ÐµÐ²ÐŸÐ¹ ÑÐ°ÑÑÐž ÑÑÑÐ°ÐœÐžÑÑ  (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ [Title]).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="652"><i>format DocumentContents true/false</i></Text>
+</th>
+<th width="283">
+<Text id="653">ÐÑÐ»Ðž ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐžÐŒÐµÐµÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑ, ÑÐŸ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ, ÐµÑÐ»Ðž ÐœÐµÑ, ÑÐŸ ÑÑÑÐµÐ»ÐºÐž next /previous section (Ðº ÑÐ»ÐµÐŽÑÑÑÐµÐŒÑ/ Ð¿ÑÐµÐŽÑÐŽÑÑÐµÐŒÑ ÑÐ°Ð·ÐŽÐµÐ»Ñ) Ðž ÑÐµÐºÑÑ âpage k of nâ (ÑÑÑÐ°ÐœÐžÑÐ° â k ÐžÐ· n).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="654"><i>format DocumentButtons string</i></Text>
+</th>
+<th width="283">
+<Text id="655">ÐÐŸÐœÑÑÐŸÐ»ÐžÑÑÐµÑ ÐºÐœÐŸÐ¿ÐºÐž ÐŒÐµÐœÑ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Detach\Highlighf).</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="656"><i>format DocumentText formatstring</i></Text>
+</th>
+<th width="283">
+<Text id="657">Ð€ÐŸÑÐŒÐ°ÑÐžÑÑÐµÑ ÑÐµÐºÑÑ, ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÐµÐŒÑÐ¹ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°: Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ </Text>
+<CodeLine>Â Â Â Â <i>&lt;center&gt;&lt;table width=537&gt;</i></CodeLine>
+<CodeLine><i>Â Â Â Â Â Â &lt;tr&gt;&lt;td&gt;[Text]&lt;/td&gt;&lt;/tr&gt;</i></CodeLine>
+<CodeLine><i>Â Â Â Â Â Â &lt;/table&gt;&lt;/center&gt;</i></CodeLine>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="658"><i>format DocumentArrowsBottom true/false</i></Text>
+</th>
+<th width="283">
+<Text id="659">ÐÑÐŸÐ±ÑÐ°Ð¶Ð°ÐµÑ ÑÑÑÐµÐ»ÐºÐž next/previous section (Ðº ÑÐ»ÐµÐŽÑÑÑÐµÐŒÑ/ Ð¿ÑÐµÐŽÑÐŽÑÑÐµÐŒÑ ÑÐ°Ð·ÐŽÐµÐ»Ñ) Ð² ÐºÐŸÐœÑÐµ ÑÑÑÐ°ÐœÐžÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ true)</Text>
+</th>
+</tr>
+<tr>
+<th width="246">
+<Text id="660"><i>format DocumentUseHTML true/false</i></Text>
+</th>
+<th width="283">
+<Text id="661">ÐÑÐ»Ðž true, ÐºÐ°Ð¶ÐŽÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÐµÑÑÑ Ð² ÐŸÑÐŽÐµÐ»ÑÐœÐŸÐŒ ÑÑÐµÐ¹ÐŒÐµ. Preferences page   (ÑÑÑÐ°ÐœÐžÑÐ° Ð²ÑÐ±ÐŸÑÐ°) ÑÐŸÐ¶Ðµ ÑÐ»ÐµÐ³ÐºÐ° ÐžÐŒÐµÐœÐžÑÑÑ, ÐŽÐŸÐ±Ð°Ð²ÑÑÑÑ ÐŸÐ¿ÑÐžÐž, Ð¿ÑÐžÐŒÐµÐœÐžÐŒÑÐµ Ðº ÑÐŸÐ²ÐŸÐºÑÐ¿ÐœÐŸÑÑÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž HTML-ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð²ÐºÐ»ÑÑÐ°Ñ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸÐ³ÐŸ Ð¿ÐµÑÐµÑ
+ÐŸÐŽÐ° Ðº ÐžÑÑ
+ÐŸÐŽÐœÐŸÐŒÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ  (Ð³ÐŽÐµ-ÐœÐžÐ±ÑÐŽÑ Ð² Web), Ð° ÐœÐµ Ðº ÐºÐŸÐ¿ÐžÐž Greenstone.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Subsection id="formatting_greenstone_lists">
+<Title>
+<Text id="662">Ð€ÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐ¿ÐžÑÐºÐŸÐ² Greenstone</Text>
+</Title>
+<Content>
+<Text id="663">Ð¡ÑÑÐŸÐºÐž ÑÐŸÑÐŒÐ°ÑÐ°, ÐºÐŸÑÐŸÑÑÐµ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐŸÐŒ ÑÐ¿ÐžÑÐºÐŸÐ², ÐŒÐŸÐ³ÑÑ Ð¿ÑÐžÐŒÐµÐœÑÑÑÑÑ ÐœÐ° ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÑÐŸÐ²ÐœÑÑ
+ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÑÑÑÐºÑÑÑÑ. ÐÐœÐž ÐŒÐŸÐ³ÑÑ ÐžÐ·ÐŒÐµÐœÐžÑÑ Ð²ÑÐµ ÑÐ¿ÐžÑÐºÐž ÐœÐµÐºÐŸÑÐŸÑÐŸÐ³ÐŸ ÑÐžÐ¿Ð° Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ DateList) ÐžÐ»Ðž Ð²ÑÐµÑ
+ ÑÐ°ÑÑÐµÐ¹ ÑÐ¿ÐžÑÐºÐ° (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, Ð²ÑÐµ Ð²Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ Ð² ÑÐ¿ÐžÑÐºÐµ Search), ÐžÐ»Ðž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÑÐ°ÑÑÑÑ
+ ÐœÐµÐºÐŸÑÐŸÑÐŸÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ° (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, Ð²ÐµÑÑÐžÐºÐ°Ð»ÑÐœÐ°Ñ ÑÐ°ÑÑÑ ÑÐ¿ÐžÑÐºÐ° Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ² ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° AZList).</Text>
+<Text id="664">Ð¡Ð»ÐµÐŽÑÑÑÐžÐ¹ - ÑÑÐŸ format ÐºÐ»ÑÑÐµÐ²ÐŸÐ³ÐŸ ÑÐ»ÐŸÐ²Ð°, ÑÐŸÑÑÐŸÑÑÐµÐ³ÐŸ ÐžÐ· ÐŽÐ²ÑÑ
+ ÑÐ°ÑÑÐµÐ¹, ÐŸÐŽÐœÐ° ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ Ð¿ÑÐžÐœÑÐŽÐžÑÐµÐ»ÑÐœÐ°. ÐÐµÑÐ²Ð°Ñ ÑÐ°ÑÑÑ ÐžÐŽÐµÐœÑÐžÑÐžÑÐžÑÑÐµÑ ÑÐ¿ÐžÑÐŸÐº, Ðº ÐºÐŸÑÐŸÑÐŸÐŒÑ ÑÐŸÑÐŒÐ°Ñ ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ. Ð¡Ð¿ÐžÑÐŸÐº, ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ Ð¿ÐŸÐžÑÐºÐŸÐŒ, ÐœÐ°Ð·ÑÐ²Ð°ÑÑ Search, Ð² ÑÐŸ Ð²ÑÐµÐŒÑ ÐºÐ°Ðº ÑÐ¿ÐžÑÐºÐž, ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°ÐŒÐž, ÐœÐ°Ð·ÑÐ²Ð°ÑÑ CL1, CL2, CL3, ... ÐŽÐ»Ñ Ð¿ÐµÑÐ²ÐŸÐ³ÐŸ, Ð²ÑÐŸÑÐŸÐ³ÐŸ, ÑÑÐµÑÑÐµÐ³ÐŸ, ... ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÑÐŸ Ð² collect.cfg. ÐÑÐŸÑÐ°Ñ ÑÐ°ÑÑÑ ÐºÐ»ÑÑÐµÐ²ÐŸÐ³ÐŸ ÑÐ»ÐŸÐ²Ð° - ÑÐ°ÑÑÑ ÑÐ¿ÐžÑÐºÐ°, Ðº ÐºÐŸÑÐŸÑÐŸÐŒÑ ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð¿ÑÐžÐŒÐµÐœÑÑÑÑÑ ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ - Ð»ÑÐ±ÐŸÐ¹ HList (ÐŽÐ»Ñ Ð³ÐŸÑÐžÐ·ÐŸÐœÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ° Ð¿ÐŸÐŽÐŸÐ±ÐœÐŸ A-Z ÑÐµÐ»ÐµÐºÑÐŸÑÑ Ð² AZList), VList (ÐŽÐ»Ñ Ð²ÐµÑÑÐžÐºÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ°,</Text>
+<Indented>
+<Text id="665"><i>format CL4VList ...</i> Ð¿ÑÐžÐŒÐµÐœÑÐµÑ ÐºÐŸ Ð²ÑÐµÐŒ <i>VLists</i> Ð² CL4</Text>
+</Indented>
+<Indented>
+<Text id="666"><i>format CL2HList ...</i> Ð¿ÑÐžÐŒÐµÐœÑÐµÑ ÐºÐŸ Ð²ÑÐµÐŒ <i>HLists</i> Ð² CL2</Text>
+</Indented>
+<Indented>
+<Text id="667"><i>format CL1DateList ...</i> Ð¿ÑÐžÐŒÐµÐœÑÐµÑ ÐºÐŸ Ð²ÑÐµÐŒ <i>DateLists</i> Ð² CL1</Text>
+</Indented>
+<Indented>
+<Text id="668"><i>format SearchVList ...</i> Ð¿ÑÐžÐŒÐµÐœÑÐµÑ ÐºÐŸ Ð²ÑÐµÐŒ Search Results list</Text>
+</Indented>
+<Indented>
+<Text id="669"><i>format CL3 ...</i> Ð¿ÑÐžÐŒÐµÐœÑÐµÑ ÐºÐŸ Ð²ÑÐµÐŒ ÑÐ·ÐµÐ»ÐºÐ°ÐŒ Ð² CL3, ÐµÑÐ»Ðž ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸ ÐœÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ</Text>
+</Indented>
+<Indented>
+<Text id="670"><i>format VList ...</i> Ð¿ÑÐžÐŒÐµÐœÑÐµÑ ÐºÐŸ Ð²ÑÐµÐŒ VLists Ð²ÐŸ Ð²ÑÐµÑ
+ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°Ñ
+, ÐµÑÐ»Ðž ÐœÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸ.</Text>
+</Indented>
+<Text id="671">"..." Ð² ÑÑÐžÑ
+ Ð¿ÑÐžÐŒÐµÑÐ°Ñ
+ Ð·Ð°ÐŒÐµÑÐ°ÑÑ ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÐž ÑÐŸÑÐŒÐ°ÑÐ° HTML, ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑÐžÐµ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹ Ðž ÐµÐµ ÑÐ°Ð·ÐŒÐµÑÐµÐœÐžÐµÐŒ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ ÐœÐ° web-ÑÑÑÐ°ÐœÐžÑÐ°Ñ
+, ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÑÑÐžÑ
+ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ. Ð¢Ð°Ðº Ð¶Ðµ, ÐºÐ°Ðº ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÐž HTML, Ð»ÑÐ±ÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŒÐŸÐ³ÑÑ Ð·Ð°ÐºÐ»ÑÑÐ°ÑÑÑÑ Ð² ÐºÐ²Ð°ÐŽÑÐ°ÑÐœÑÐµ ÑÐºÐŸÐ±ÐºÐž: ÑÑÐž Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐžÐœÑÐµÑÐ¿ÐŸÐ»ÐžÑÐŸÐ²Ð°ÐœÑ Ð² ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐœÐŸÐŒ ÐŒÐµÑÑÐµ. Ð¢Ð°ÐºÐ¶Ðµ Ð»ÑÐ±ÐŸÐ¹ ÐžÐ· ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="the_format_options"/> ÐŒÐŸÐ¶ÐµÑ Ð¿ÑÐžÐŒÐµÐœÑÑÑÑÑ Ð² ÑÑÑÐŸÐºÐ°Ñ
+ ÑÐŸÑÐŒÐ°ÑÐ°. Ð¡ÐžÐœÑÐ°ÐºÑÐžÑ ÐŽÐ»Ñ ÑÑÑÐŸÐº ÑÐ°ÐºÐ¶Ðµ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÑÑÐ»ÐŸÐ²ÐœÑÑ ÐžÐœÑÑÑÑÐºÑÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐ° Ð² Ð¿ÑÐžÐŒÐµÑÐµ ÐœÐžÐ¶Ðµ.</Text>
+<Text id="672">ÐÐµÑÐµÐ²ÑÐ·ÐŸÐ² Ð²ÑÐµÑ
+ ÑÑÐžÑ
+ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ² ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐžÐµÑÐ°ÑÑ
+ÐžÐž. ÐÐ°Ð¶ÐŽÑÐ¹ ÑÑÐŸÐ²ÐµÐœÑ ÐžÐµÑÐ°ÑÑ
+ÐžÐž ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœ ÐŸÐŽÐœÐžÐŒ ÐžÐ· ÑÐµÑÑÑÐµÑ
+ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÑ
+ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐ². ÐÑ ÑÐ¶Ðµ ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°Ð»Ðž HLIST, VList Ðž DateList. Ð ÐœÐžÐŒ ÐŸÑÐœÐŸÑÐžÑÑÑ ÑÐ°ÐºÐ¶Ðµ Invisible, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ²Ð»ÑÐµÑÑÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµÐŒ ÐºÑÐ°ÐŒÑÑ
+ Ð²ÐµÑÑ
+ÐœÑ
+ ÑÑÐŸÐ²ÐœÐµÐ¹ ÐžÐµÑÐ°ÑÑ
+ÐžÐ¹, Ñ.Ðº. ÐžÐŒÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° Ð²ÑÐµÐ³ÐŽÐ° Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÐŸÑÐŽÐµÐ»ÑÐœÐŸ ÐŸÑ ÐœÐ°Ð²ÐžÐ³Ð°ÑÐžÐŸÐœÐœÐŸÐ³ÐŸ ÐŒÐµÐœÑ GreenÂ¬stone .</Text>
+</Content>
+</Subsection>
+<Subsection id="examples_of_classifiers_and_format_strings">
+<Title>
+<Text id="673">ÐÑÐžÐŒÐµÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ² Ðž ÑÑÑÐŸÐº ÑÐŸÑÐŒÐ°ÑÐ°</Text>
+</Title>
+<Content>
+<Figure id="excerpt_from_the_demo_collection_collect" class="withLineNumber">
+<Title>
+<Text id="674">ÐÑÐ±ÐŸÑÐºÐ° ÐžÐ· ÑÐ°Ð¹Ð»Ð° collectcfg ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐž</Text>
+</Title>
+<CodeLine>classify Hierarchy -hfile sub.txt -metadata Subject -sort Title</CodeLine>
+<CodeLine>classify AZList       -metadata Title</CodeLine>
+<CodeLine>classify Hierarchy -hfile org.txt -metadata Organisation -sort Title</CodeLine>
+<CodeLine>classify List           -metadata Howto</CodeLine>
+<CodeLine>format SearchVList " &lt;td valign=top [link][icon][/link]&lt;/td&gt;&lt;td&gt;{If}</CodeLine>
+<CodeLine>                                       {[parent(All':'):Title],[parent(All':'):Title]:}</CodeLine>
+<CodeLine>                                       [link][Title][/link]&lt;/td&gt; "</CodeLine>
+<CodeLine>format CL4Vlist                 "&lt;br&gt;[link][Howto][/link] "</CodeLine>
+<CodeLine>format DocumentImages   true</CodeLine>
+<CodeLine>format DocumentText       "&lt;h3&gt;[Title]&lt;/h3&gt;\\n\\n&lt;p&gt;[Text]"</CodeLine>
+<CodeLine>format DocumentButtons " Expand Text|Expand contents|Detach|Highlight"</CodeLine>
+</Figure>
+<Text id="675">ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐ° ÑÐ°ÑÑÑ ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐŽÐ»Ñ ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒ ÐµÐ³ÐŸ ÐºÐ°Ðº Ð¿ÑÐžÐŒÐµÑ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŸÐœ ÐžÐŒÐµÐµÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐŸÑÐ»ÐžÑÐœÐŸ ÐŸÑÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÑ. ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ, ÑÑÐŸ ÐžÐœÑÑÑÑÐºÑÐžÐž Ð² ÑÐ°Ð¹Ð»Ð°Ñ
+ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐµ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÑÐžÐŒÐ²ÐŸÐ»Ñ ÐœÐŸÐ²ÐŸÐ¹ ÑÑÑÐŸÐºÐž - Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ Ð±ÐŸÐ»ÐµÐµ ÐŽÐ»ÐžÐœÐœÑÐµ ÑÑÑÐŸÐºÐž ÑÐ°Ð·Ð±ÐžÐ²Ð°ÑÑÑÑ ÐŽÐ»Ñ ÑÐŽÐŸÐ±ÐŸÑÐžÑÐ°ÐµÐŒÐŸÑÑÐž.</Text>
+<Text id="676">Ð¡ÑÑÐŸÐºÐ° 4 ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ How To ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐœ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐµÑÐ²ÐµÑÑÑÐŒ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð¿ÐŸÑÑÐŸÐŒÑ ÑÐ¿ÐŸÐŒÐžÐœÐ°ÐµÑÑÑ ÐºÐ°Ðº CL4. ÐÐœÐ°Ð»ÐŸÐ³ÐžÑÐœÐŸÑ ÑÐŸÑÐŒÑÐ»ÐžÑÐŸÐ²ÐºÐ° ÑÐŸÑÐŒÐ°ÑÐ° - ÑÑÑÐŸÐºÐ° 7 ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>. ÐÐœÑÐŸÑÐŒÐ°ÑÐžÑ "how to" Ð³ÐµÐœÐµÑÐžÑÑÐµÑÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐŒ List, Ð° ÐµÐ³ÐŸ ÑÑÑÑÐºÑÑÑÐ° - ÑÑÐŸ Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐ¿ÐžÑÐŸÐº Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ² (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="list_classifier"/>). ÐÐ°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž ÑÐ²ÑÐ·Ð°ÐœÑ Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒÐž ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ: ÑÐµÐ»ÑÐŸÐº ÐŒÑÑÑÑ ÐœÐ° Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐµ Ð²ÑÐ·ÑÐ²Ð°ÐµÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ. ÐÐŸÑÐµÑÐœÐžÐµ Ð·Ð°Ð¿ÐžÑÐž Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ ÐžÐµÑÐ°ÑÑ
+ÐžÐž ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÑ ÐºÐ°Ðº VList (Ð²ÐµÑÑÐžÐºÐ°Ð»ÑÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº), ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐµÑÐµÑÐžÑÐ»ÑÐµÑ ÑÐ°Ð·ÐŽÐµÐ»Ñ Ð²ÐµÑÑÐžÐºÐ°Ð»ÑÐœÐŸ. ÐÐŸÑÐºÐŸÐ»ÑÐºÑ ÑÐ²ÑÐ·Ð°ÐœÐœÑÐ¹ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑ format ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÑÐŸ, ÑÑÐŸ ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ ÑÐ¿ÐžÑÐºÐ° ÐœÐ°ÑÐžÐœÐ°ÐµÑÑÑ Ñ ÐœÐŸÐ²ÐŸÐ¹ ÑÑÑÐŸÐºÐž ("&lt;br&gt;") Ðž ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÐµÐºÑÑ Howto, Ð³ÐžÐ¿ÐµÑÑÐ²ÑÐ·Ñ Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ.</Text>
+<Text id="677">Ð¡ÑÑÐŸÐºÐ° 1 ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÑ Subject ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐ¿ÐŸÐŒÑÐœÑÑÑÑ ÐºÐ°Ðº CL1 (Ð¿ÐµÑÐ²ÑÐ¹ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž), ÑÑÑÐŸÐºÐ° 3 ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÑ Organisation - CL3. ÐÐ±Ðµ ÑÑÑÐŸÐºÐž ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐŒ Hierarchy Ðž Ð¿ÐŸÑÑÐŸÐŒÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÑÑ ÑÑÑÑÐºÑÑÑÑ VLists.</Text>
+<Text id="678">Ð¡ÑÑÐŸÐºÐ° 2 ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐŸÑÑÐ°Ð²ÑÑÑÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÑ ÐŽÐ»Ñ ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Titles A-Z (CL2). ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÐŸÑÑÑÑÑÑÐ²ÐžÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÑ
+ ÑÑÑÐŸÐº ÑÐŸÑÐŒÐ°ÑÐ° ÐŽÐ»Ñ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ² CL1. CL3. Greenstone ÐžÐŒÐµÐµÑ Ð²ÑÑÑÐŸÐµÐœÐœÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐžÐ¿Ð° ÑÑÑÐŸÐºÐž ÑÐŸÑÐŒÐ°ÑÐ° Ðž Ð¿ÐŸÑÑÐŸÐŒÑ ÐœÐµÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÐž ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑ ÑÑÑÐŸÐºÑ ÑÐŸÑÐŒÐ°ÑÐ°, ÐµÑÐ»Ðž ÐÑ ÐœÐµ ÑÐŸÐ±ÐžÑÐ°ÐµÑÐµÑÑ ÐŸÑÐŒÐµÐœÑÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ.</Text>
+<Figure id="formatting_the_document">
+<Title>
+<Text id="679">Ð€ÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°</Text>
+</Title>
+<File width="394" height="277" url="images/Dev_Fig_038.png"/>
+</Figure>
+<Text id="680">Ð­ÑÐŸ ÑÑÐµÑÐœÐ°Ñ Ð·Ð°Ð¿ÐžÑÑ ÐŽÐ»Ñ ÑÑÑÐŸÐºÐž classify (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>). ÐÐŸ ÑÐŸÐ²Ð¿Ð°ÐŽÐµÐœÐžÑ, ÐµÑÑÑ ÑÐ°ÐºÐ¶Ðµ ÑÐµÑÑÑÐµ ÑÑÑÐŸÐºÐž format. ÐÐŽÐœÑ ÐŒÑ ÑÐ¶Ðµ ÐŸÐ±ÑÑÐŽÐžÐ»Ðž - ÑÑÐŸ CL4VHst. ÐÑÑÐ°Ð²ÑÐžÐµÑÑ ÑÑÐž - Ð¿ÐµÑÐ²ÑÐ¹ ÑÐžÐ¿ ÑÑÑÐŸÐºÐž ÑÐŸÑÐŒÐ°ÑÐ°, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÑÐ¹ Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="items_appearing_in_format_strings"/>. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÑÑÑÐŸÐºÐ° 8 Ð¿ÐŸÐŒÐµÑÐ°ÐµÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ ÐŸÐ±Ð»ÐŸÐ¶ÐºÐž, Ð² Ð²ÐµÑÑ
+ÐœÐµÐŒ Ð»ÐµÐ²ÐŸÐŒ ÑÐ³Ð»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð¡ÑÑÐŸÐºÐ° 9 ÑÐŸÑÐŒÐ°ÑÐžÑÑÐµÑ ÑÐ°ÐºÑÐžÑÐµÑÐºÐžÐ¹ ÑÐµÐºÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ñ ÑÐºÐ°Ð·Ð°ÐœÐžÐµÐŒ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐ¹ Ð³Ð»Ð°Ð²Ñ ÐžÐ»Ðž ÑÐ°Ð·ÐŽÐµÐ»Ð°, ÑÑÐŸÑÑÐžÑ
+ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ Ð¿ÐµÑÐµÐŽ ÑÐµÐºÑÑÐŸÐŒ. ÐÑÐµ ÑÑÐŸ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="formatting_the_document"/>.</Text>
+<Figure id="formatting_the_search_results">
+<Title>
+<Text id="681">Ð€ÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² Ð¿ÐŸÐžÑÐºÐ°</Text>
+</Title>
+<File width="396" height="243" url="images/Dev_Fig_040.png"/>
+</Figure>
+<Text id="682">Ð¡ÑÑÐŸÐºÐ° 5 ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/> - ÑÐºÐŸÑÐµÐµ ÑÐ»ÐŸÐ¶ÐœÐ°Ñ ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŸÑÐŒÐ°ÑÐžÑÑÐµÑ ÑÐ¿ÐžÑÐŸÐº ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐ° Ð·Ð°Ð¿ÑÐŸÑÐ°, Ð²ÐŸÐ·Ð²ÑÐ°ÑÐµÐœÐœÑÐ¹ Ð¿ÐŸÐžÑÐºÐŸÐŒ, ÑÐ°ÑÑÐž ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="formatting_the_search_results"/>. Ð£Ð¿ÑÐŸÑÐµÐœÐœÐ°Ñ Ð²ÐµÑÑÐžÑ ÑÑÑÐŸÐºÐž ÑÐŸÑÐŒÐ°ÑÐ°</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;</CodeLine>
+<CodeLine>&lt;td&gt;[link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="683">ÐÐœÐ° ÑÐ¿ÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐ° ÑÐ°Ðº, ÑÑÐŸÐ±Ñ ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÑÑÑÑ Ð² Ð²ÐžÐŽÐµ ÑÑÑÐŸÐºÐž ÑÐ°Ð±Ð»ÐžÑÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐ¿ÐžÑÐºÐŸÐŒ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž Ð·Ð°Ð¿ÑÐŸÑÐ°. ÐÐœÐ° ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐœÐµÐ±ÐŸÐ»ÑÑÑÑ ÐžÐºÐŸÐœÐºÑ, ÑÐ²ÑÐ·Ð°ÐœÐœÑÑ Ñ ÑÐµÐºÑÑÐŸÐŒ, Ð° Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐŸÐ±ÑÑÐœÐŸ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÐµÑ Ð³ÐžÐ¿ÐµÑÑÐ²ÑÐ·Ñ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ.</Text>
+<Text id="684">Ð ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐž. Ð€Ð°ÐºÑÐžÑÐµÑÐºÐž, Ð²ÑÑÐµÑÐ¿ÐŸÐŒÑÐœÑÑÐ°Ñ Ð³ÐžÐ¿ÐµÑÑÐ²ÑÐ·Ñ Ð·Ð°ÐºÑÐµÐ¿Ð»ÑÐµÑÑÑ Ð·Ð° Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ð°, Ð²ÐŸÐ·Ð²ÑÐ°ÑÐµÐœÐœÐŸÐ³ÐŸ Ð·Ð°Ð¿ÑÐŸÑÐŸÐŒ. ÐÐŽÐœÐ°ÐºÐŸ, Ð±ÑÐ»ÐŸ Ð±Ñ Ð»ÑÑÑÐµ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÑ ÐŽÐ°ÐœÐœÑÑ Ð¿ÑÐŸÑÐµÐŽÑÑÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐŒ Ð²Ð»ÐŸÐ¶ÐµÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð°, Ð²Ð»ÐŸÐ¶ÐµÐœÐœÐŸÐ¹ Ð³Ð»Ð°Ð²Ñ Ðž ÐºÐœÐžÐ³Ðž, Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐºÐŸÑÐŸÑÑÑ
+ ÐŸÐœÐ° Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ. Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ parent, ÐºÐŸÑÐŸÑÑÐ¹ ÐœÐµ ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑÑÑ Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°Ñ
+, ÐœÐŸ ÐœÐµÑÐ²ÐœÐŸ Ð¿ÑÐžÑÑÑÑÑÐ²ÑÐµÑ Ð² Ð»ÑÐ±ÐŸÐŒ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐŸÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐµ, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐ·ÐŽÐ°ÐµÑ ÑÐ°ÐºÐŸÐ¹ ÑÐ¿ÐžÑÐŸÐº. ÐÐœ Ð»ÐžÐ±ÐŸ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ ÑÐŸÐŽÐžÑÐµÐ»ÑÑÐºÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ, Ð»ÐžÐ±ÐŸ, ÐµÑÐ»Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐŸÑ All, ÑÐ¿ÐžÑÐŸÐº ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐŸÐ³ÐŸ Ð²ÐºÐ»ÑÑÐµÐœÐžÑ ÑÐŸÐŽÐžÑÐµÐ»ÐµÐ¹, ÐŸÑÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÑÐžÐŒÐ²ÐŸÐ»ÑÐœÐŸÐ¹ ÑÑÑÐŸÐºÐŸÐ¹, ÐºÐŸÑÐŸÑÑÑ ÐŒÐŸÐ¶ÐœÐŸ Ð²ÑÑÐ°Ð²ÐžÑÑ Ð¿ÐŸÑÐ»Ðµ ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° All. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt; <br/>&lt;td&gt;{[parent(All': '):Title]: }[link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="685">ÐžÐŒÐµÐµÑ ÑÐŒÑÑÐ» Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²ÐžÑÑ ÑÐ¿ÐžÑÐŸÐº, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÐ¹ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐºÐœÐžÐ³Ðž, Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº Ð³Ð»Ð°Ð²Ñ Ðž Ñ.ÐŽ., ÐºÐŸÑÐŸÑÑÐµ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÐºÐŸÐœÐµÑÐœÑÐ¹ ÑÐ°Ð·ÐŽÐµÐ», ÐŸÑÐŽÐµÐ»ÐµÐœÐœÑÐ¹ ÐŽÐ²ÐŸÐµÑÐŸÑÐžÐµÐŒ, Ñ ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÐžÐŒ ÐŽÐ²ÐŸÐµÑÐŸÑÐžÐµÐŒ, ÑÐŸÐ¿ÑÐŸÐ²ÐŸÐ¶ÐŽÐ°ÐµÐŒÑÐŒ Ð³ÐžÐ¿ÐµÑÑÐ²ÑÐ·ÑÑ Ñ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐŒ ÑÑÐŸÐ³ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð°.</Text>
+<Text id="686">Ð ÑÐŸÐ¶Ð°Ð»ÐµÐœÐžÑ, ÐµÑÐ»Ðž ÐºÐŸÐœÐµÑÐœÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ - ÑÐ°ÐŒÐŸÑÑÐŸÑÑÐµÐ»ÑÐœÐ°Ñ ÐºÐœÐžÐ³Ð°, ÐºÐŸÑÐŸÑÐ°Ñ ÐœÐµ ÐžÐŒÐµÐµÑ ÑÐŸÐŽÐžÑÐµÐ»ÑÑÐºÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÑÐŸ Ð¿ÐŸÑÐ²ÐžÑÑÑ Ð¿ÑÑÑÐ°Ñ ÑÑÑÐŸÐºÐ°, ÑÐŸÐ¿ÑÐŸÐ²ÐŸÐ¶ÐŽÐ°ÐµÐŒÐ°Ñ ÐŽÐ²ÐŸÐµÑÐŸÑÐžÐµÐŒ. Ð§ÑÐŸÐ±Ñ ÐžÐ·Ð±ÐµÐ¶Ð°ÑÑ ÑÑÐŸÐ³ÐŸ, Ð²ÐŸÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµÑÑ ÑÑÐ»ÐŸÐ²ÐœÑÐŒÐž ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÐ°ÐŒÐž ifÐœÐŸÐ³ ... else Ð² ÑÑÑÐŸÐºÐµ ÑÐŸÑÐŒÐ°ÑÐ°:</Text>
+<CodeLine>{If}{[metadata], action-if-non-null, action-if-null}</CodeLine>
+<CodeLine>{Or}{action, else another-action, else another-action, etc}</CodeLine>
+<Text id="687">ÐÐ°ÐœÐœÑÐµ Ð² ÑÐžÐ³ÑÑÐœÑÑ
+ ÑÐºÐŸÐ±ÐºÐ°Ñ
+ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ ÐžÐœÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÐŸ ÑÐŸÐŒ, ÑÑÐŸ ÑÑÐŸ ÐžÐœÑÑÑÑÐºÑÐžÑ ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ ÐœÐµ ÑÐŸÐ»ÑÐºÐŸ ÑÐ°ÑÐ¿ÐµÑÐ°ÑÐ°ÐœÐ° ÐºÐ°Ðº ÑÐµÐºÑÑ, ÐœÐŸ Ðž ÐžÐœÑÐµÑÐ¿ÑÐµÑÐžÑÐŸÐ²Ð°ÐœÐ°. If Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ, Ð¿ÑÑÑÑ Ð»Ðž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ðž Ð±ÐµÑÐµÑ Ð¿ÐµÑÐ²ÐŸÐµ Ð¿ÑÐµÐŽÐ»ÐŸÐ¶ÐµÐœÐžÐµ, Ð² Ð¿ÑÐŸÑÐžÐ²ÐœÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ - Ð²ÑÐŸÑÐŸÐµ (ÐµÑÐ»Ðž ÐŸÐœÐŸ ÑÑÑÐµÑÑÐ²ÑÐµÑ). ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ ÐŒÐŸÐ¶ÐµÑ Ð»ÑÐ±ÐŸÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, Ð²Ð¿Ð»ÐŸÑÑ ÐŽÐŸ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÑÐ°Ð·ÐŽÐµÐ»ÐžÑÐµÐ»Ñ. ÐÐ¿ÐµÑÐ°ÑÐŸÑ Or ÐŸÑÐµÐœÐžÐ²Ð°ÐµÑ ÐºÐ°Ð¶ÐŽÐŸÐµ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐµÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ ÐŽÐŸ ÑÐµÑ
+ Ð¿ÐŸÑ, Ð¿ÐŸÐºÐ° ÐœÐµ ÐœÐ°Ð¹ÐŽÐµÑÑÑ ÐœÐµÐœÑÐ»ÐµÐ²ÐŸÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ. Ð ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ ÑÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÐºÐŸÐŒÐ°ÐœÐŽÐ° - Ð¿ÑÐŸÐ¿ÑÑÑÐžÑÑ ÐŸÑÑÐ°Ð»ÑÐœÑÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ.</Text>
+<Text id="688">ÐÐŸÐ·Ð²ÑÐ°ÑÐ°ÑÑÑ Ðº ÑÑÑÐŸÐºÐµ 5 Ð ÐžÑÑÐœÐºÐ° <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÐŒ Ð¿ÐŸÐ»ÐœÑÐ¹ ÑÐŸÑÐŒÐ°Ñ ÑÑÑÐŸÐºÐž</Text>
+<CodeLine>&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;</CodeLine>
+<CodeLine>&lt;td&gt;{If}{[parent(All': '):Title],</CodeLine>
+<CodeLine>           [parent(All': '):Title]:}</CodeLine>    
+<CodeLine>      [link][Title][/link]&lt;/td&gt;</CodeLine>
+<Text id="689">Ð­ÑÐŸ Ð¿ÑÐµÐŽÑÐµÑÑÐ²ÑÐµÑ ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÐž parent Ñ ÑÑÐ»ÐŸÐ²ÐœÑÐŒ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÐµÐŒ, ÐºÐŸÑÐŸÑÐŸÐµ Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ, Ð¿ÑÑÑ Ð»Ðž ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ, Ðž Ð² Ð¿ÑÐŸÑÐžÐ²ÐœÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ Ð²ÑÐŽÐ°ÐµÑ ÑÐŸÐŽÐžÑÐµÐ»ÑÑÐºÑÑ Ð·Ð°Ð¿ÐžÑÑ. ÐÑÑÐ°ÑÐž, parent ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœ Ð¢ÐŸÑ Ð²ÐŒÐµÑÑÐŸ ÐÐ, ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÑÐŽÐ°ÐµÑ ÐžÐŒÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ, Ð²ÐºÐ»ÑÑÐ°ÑÑÐµÐµ ÑÐ°Ð·ÐŽÐµÐ» - Ð² ÐœÐ°ÑÐµÐŒ ÑÐ»ÑÑÐ°Ðµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐœÐžÐ³Ðž. ÐÑÐŽÐµÐ»ÐµÐœÐžÐµ ÑÑÑÐŸÐºÐŸÐ¹ ÐŽÐ»Ñ Ð¢ÐŸÑ ÐœÐµ ÑÑÐµÐ±ÑÐµÑÑÑ.</Text>
+<Text id="690">ÐÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐµ Ð¿ÑÐžÐŒÐµÑÑ ÐžÐ»Ð»ÑÑÑÑÐžÑÑÑÑ ÐŽÑÑÐ³ÐžÐµ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž. DateList ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="datelist_classifier"/> ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž Dates Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Computists' Weekly (ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ²Ð»ÑÐµÑÑÑ Ð²ÑÐŸÑÑÐŒ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐŒ - CL2). ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ Ðž ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÐž ÑÐŸÑÐŒÐ°ÑÐ° Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ ÐœÐžÐ¶Ðµ. ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ DateList ÐŸÑÐ»ÐžÑÐ°ÐµÑÑÑ ÐŸÑ AZList ÑÐµÐŒ, ÑÑÐŸ Ð²ÑÐµÐ³ÐŽÐ° ÑÐŸÑÑÐžÑÑÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Dates, Ð° Ð²ÐµÑÐ²Ðž ÐŸÑÐœÐŸÐ²Ð°ÐœÐžÑ ÐžÐµÑÐ°ÑÑ
+ÐžÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ DateList Ð²ÐŒÐµÑÑÐŸ VList, ÐºÐŸÑÐŸÑÑÐ¹ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑ Ð³ÐŸÐŽ Ðž ÐŒÐµÑÑÑ ÑÐ»ÐµÐ²Ð° ÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°.</Text>
+<CodeLine>classify AZSectionList metadata=Creator</CodeLine>
+<CodeLine>format CL2Vlist "&lt;td&gt;[link][icon][/link]&lt;/td&gt; <br/>&lt;td&gt;[Creator]&lt;/td&gt; <br/>&lt;td&gt;&amp;nbsp;&amp;nbsp;[Title]&lt;/td&gt; <br/>&lt;td&gt;[parent(Top):Date]&lt;/td&gt; "</CodeLine>
+<Text id="691">Ð€ÐŸÑÐŒÐ°Ñ ÑÐ¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÐž Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ VLists ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐŒ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ.</Text>
+<Text id="692">ÐÐµÑ
+Ð°ÐœÐžÐ·ÐŒ ÑÑÑÐŸÐºÐŸÐ²ÐŸÐ³ÐŸ ÑÐŸÑÐŒÐ°ÑÐ° ÑÐ²Ð»ÑÐµÑÑÑ Ð³ÐžÐ±ÐºÐžÐŒ, ÐœÐŸ Ð·Ð°Ð¿ÑÑÐ°ÐœÐœÑÐŒ ÐŽÐ»Ñ ÐžÐ·ÑÑÐµÐœÐžÑ. ÐÑÑÑÐžÐ¹ Ð¿ÑÑÑ - ÑÑÐŸ ÐžÐ·ÑÑÐµÐœÐžÐµ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</Content>
+</Subsection>
+<Subsection id="linking_to_different_document_versions">
+<Title>
+<Text id="693">Ð¡ÐŸÐµÐŽÐžÐœÐµÐœÐžÑ Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒÐž Ð²ÐµÑÑÐžÑÐŒÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="694">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒÐ° [link] ... [/link] Ð² ÑÑÑÐŸÐºÐŸÐ²ÐŸÐŒ ÑÐŸÑÐŒÐ°ÑÐµ ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð³ÐžÐ¿ÐµÑÑÐ²ÑÐ·Ñ Ñ ÑÐµÐºÑÑÐŸÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐŸÐ³ÐŽÐ° ÑÑÑÐ»ÐºÐ° Ð°ÐºÑÐžÐ²ÐžÑÑÐµÑÑÑ, ÐœÐ° ÑÐºÑÐ°ÐœÐµ ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÐµÑÑÑ HTML- Ð²ÐµÑÑÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÐŽÑÑÐ³ÐžÑ
+ Ð²ÐµÑÑÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Microsoft Word Ð±ÑÐ»ÐŸ Ð±Ñ ÐœÐµÐ¿Ð»ÐŸÑ
+ÐŸ ÐŸÑÐŸÐ±ÑÐ°Ð·ÐžÑÑ ÐŸÑÐžÐ³ÐžÐœÐ°Ð»ÑÐœÑÑ Ð²ÐµÑÑÐžÑ Ð² ÑÐŸÑÐŒÐ°ÑÐµ Word ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, Ð° ÐœÐµ ÐºÐŸÐœÐ²ÐµÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ Ð² HTML Ð²Ð°ÑÐžÐ°ÐœÑ; ÑÐŸ Ð¶Ðµ ÑÐ°ÐŒÐŸÐµ ÐºÐ°ÑÐ°ÐµÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐŸÑÐŒÐ°ÑÐ° PDF.</Text>
+<Text id="695">ÐÐ»ÑÑ, Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÑÑÐžÐ¹ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ Ð¿ÐŸÐºÐ°Ð·Ð° ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð²ÐµÑÑÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐŽÐŸÐ»Ð¶ÐµÐœ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐŒÐµÑÑÐµ ÐžÑ
+ Ñ
+ÑÐ°ÐœÐµÐœÐžÑ - ÐŸÐ± Ð°ÑÑ
+ÐžÐ²Ðµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Greenstone. ÐÐœÑÐŸÑÐŒÐ°ÑÐžÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑÑÑ Ð² ÑÐŸÑÐŒÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐŸÐŒÐµÑÐ°ÐµÐŒ</Text>
+<CodeLine>[link][Title][/link]</CodeLine>
+<Text id="696">Ð² ÑÑÑÐŸÐºÑ ÑÐŸÑÐŒÐ°ÑÐ°, ÑÐŸÐ·ÐŽÐ°ÑÑÐµÐ³ÐŸ ÑÑÑÐ»ÐºÑ Ðº HTML-ÐŽÐŸÐºÑÐŒÐµÐœÑÑ. Ð ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð¿ÐŸÐŒÐµÑÐµÐœÐœÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ðœ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑ Word Ðž PDF Ð³ÐµÐœÐµÑÐžÑÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ srclink, ÑÐ°Ðº ÑÑÐŸ ÐµÑÐ»Ðž ÐÑ Ð¿ÐŸÐŒÐµÑÑÐžÐ»Ðž</Text>
+<CodeLine>[srclink][Title][/srclink]</CodeLine>
+<Text id="697">Ð² ÑÐŸÑÐŒÐ°Ñ ÑÑÑÐŸÐºÐž, ÑÐŸ Ð±ÑÐŽÐµÑ ÑÐŸÐ·ÐŽÐ°ÐœÐ° ÑÑÑÐ»ÐºÐ° Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐŸÑÐŒÐ°ÑÐ° Word ÐžÐ»Ðž PDF; Ð² ÑÑÐŸÐŒ Ð¿ÑÐžÐŒÐµÑÐµ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð¿ÐŸÐŒÐµÑÐµÐœÐœÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ° ÑÐœÐŸÐ²Ð° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ðœ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð¡ÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐµ ÐžÐºÐŸÐœÐºÐž ÐŽÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Word Ðž PDF ÑÐ°ÐºÐ¶Ðµ Ð³ÐµÐœÐµÑÐžÑÑÑÑÑÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµÐŒ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ srcicon</Text>
+<CodeLine>[srclink][srcicon][/srclink]</CodeLine>
+<Text id="698">ÐÐœÐŸ ÑÐŸÐ·ÐŽÐ°ÐµÑ ÑÑÑÐ»ÐºÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð±ÑÐŽÐµÑ ÐŸÑÐŒÐµÐœÐµÐœÐ° ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐ¹ ÐžÐºÐŸÐœÐºÐŸÐ¹ Word ÐžÐ»Ðž PDF (ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸ ÑÐžÐ¿Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°), Ð²ÐŒÐµÑÑÐŸ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="controlling_the_greenstone_user_interface">
+<Title>
+<Text id="699">Ð£Ð¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐžÐŒ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐŸÐŒ Greenstone</Text>
+</Title>
+<Content>
+<Text id="700">ÐÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Greenstone ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑÑÑ ÐŒÐ°ÐºÑÐŸÑÐ°ÐŒÐž, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸ ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ Ð² ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ðµ GSDLHOME/macros. ÐÐœÐž ÐœÐ°Ð¿ÐžÑÐ°ÐœÑ ÐœÐ° ÑÐ·ÑÐºÐµ, ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°ÐœÐœÐŸÐŒ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÐŸ ÐŽÐ»Ñ Greenstone, Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ ÐŽÐ»Ñ Ð³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐžÑ web-ÑÑÑÐ°ÐœÐžÑ. Ð¢ÑÐ°ÐœÑÐ»ÑÑÐžÑ ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐºÐ° Ð² HTML -Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐ¹ ÑÐ°Ð³ Ð² ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐž ÑÑÑÐ°ÐœÐžÑÑ. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð² ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ðµ ÐœÐµÐŒÐµÐŽÐ»ÐµÐœÐœÐŸ ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÑÑÑÑ ÐœÐ° ÑÐºÑÐ°ÐœÐµ, Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð±ÑÑÑÑÑÐ¹ Ðž ÐŸÑÐµÐœÑ Ð¿ÑÐŸÑÑÐŸÐ¹ ÐžÐœÑÑÑÑÐŒÐµÐœÑ. ÐÑÐµ ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ñ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ Greenstone, Ð¿ÐµÑÐµÑÐžÑÐ»ÐµÐœÑ Ð² GSDLHOME/etc/main.cfg Ðž Ð·Ð°Ð³ÑÑÐ¶Ð°ÑÑÑÑ ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐ°Ð·, ÐºÐŸÐ³ÐŽÐ° ÐžÑ
+ Ð²ÑÐ·ÑÐ²Ð°ÑÑ. ÐÐŽÐžÐœÑÑÐ²ÐµÐœÐœÐŸÐµ ÐžÑÐºÐ»ÑÑÐµÐœÐžÐµ ÐºÐ°ÑÐ°ÐµÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ Windows Local Library - Ð² ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð±ÑÐŽÐµÑ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÐžÑÑ Ð¿ÑÐŸÑÐµÑÑ.</Text>
+<Text id="701">Web-ÑÑÑÐ°ÐœÐžÑÑ Ð³ÐµÐœÐµÑÐžÑÑÑÑÑÑ ÐœÐ° Ð»ÐµÑÑ Ð¿ÐŸ ÑÑÐŽÑ Ð¿ÑÐžÑÐžÐœ, Ðž ÐŒÐ°ÐºÑÐŸÑÐžÑÑÐµÐŒÐ° Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Greenstone ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑ ÑÑÐŸ Ñ ÐœÐµÐ²ÐµÑÐŸÑÑÐœÐŸÐ¹ Ð³ÐžÐ±ÐºÐŸÑÑÑÑ. Ð¡ÑÑÐ°ÐœÐžÑÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÐœÐ° ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÑÐ·ÑÐºÐ°Ñ
+, ÑÐµÐºÑÑ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° ÐºÐŸÑÐŸÑÑÑ
+ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐ·ÑÐºÐ° Ð±ÑÐŽÐµÑ Ñ
+ÑÐ°ÐœÐžÑÑÑÑ Ð² ÑÐ°Ð·ÐœÑÑ
+ ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ð°Ñ
+. ÐÐŸÐ³ÐŽÐ° Greenstone ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÐµÑ ÑÑÑÐ°ÐœÐžÑÑ, ÐŒÐ°ÐºÑÐŸ ÐžÐœÑÐµÑÐ¿ÑÐµÑÐ°ÑÐŸÑ Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÑ ÑÐ·ÑÐºÐ° Ðž Ð·Ð°Ð³ÑÑÐ¶Ð°ÐµÑ ÑÑÑÐ°ÐœÐžÑÑ ÐœÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐŒ ÑÐ·ÑÐºÐµ (ÑÑÐŸ, Ðº ÑÐŸÐ¶Ð°Ð»ÐµÐœÐžÑ, ÐœÐµ ÐŸÑÐœÐŸÑÐžÑÑÑ Ðº ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°). ÐÐœÐ°ÑÐµÐœÐžÑ ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÑÐºÑÐ°ÐœÐœÑÑ
+ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÑ
+, Ð¿ÐŸÐŽÐŸÐ±ÐœÑÑ
+ ÐœÐŸÐŒÐµÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð¿ÐŸÐ»ÑÑÐµÐœÐœÑÑ
+ Ð² ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ Ð¿ÐŸÐžÑÐºÐ°, ÐœÐµ ÐžÐ·Ð²ÐµÑÑÐœÑ Ð·Ð°ÑÐ°ÐœÐµÐµ; ÐŸÐœÐž ÐžÐœÑÐµÑÐ¿ÐŸÐ»ÐžÑÐŸÐ²Ð°ÐœÑ Ð² ÑÐµÐºÑÑ ÑÑÑÐ°ÐœÐžÑÑ Ð² ÑÐŸÑÐŒÐµ ÐŒÐ°ÐºÑÐŸÑÐ°.</Text>
+<Subsection id="the_macro_file_format">
+<Title>
+<Text id="702">Ð€ÐŸÑÐŒÐ°Ñ ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ð°</Text>
+</Title>
+<Content>
+<Text id="703">ÐÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ñ ÐžÐŒÐµÑÑ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµ .dm. ÐÐ°Ð¶ÐŽÑÐ¹ ÑÐ°Ð¹Ð» ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐŸÐŽÐžÐœ ÐžÐ»Ðž Ð±ÐŸÐ»ÐµÐµ packages, ÐºÐ°Ð¶ÐŽÑÐ¹ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÑÐŽ ÐŒÐ°ÐºÑÐŸÑÐŸÐ², ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ Ñ ÐµÐŽÐžÐœÑÑÐ²ÐµÐœÐœÐŸÐ¹ ÑÐµÐ»ÑÑ. Ð¢Ð°ÐºÐ¶Ðµ, ÐºÐ°Ðº Ðž Ð² ÑÐ»ÑÑÐ°Ðµ Ñ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°ÐŒÐž Ðž Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÑÐŒÐž, ÑÑÑÐµÑÑÐ²ÑÐµÑ ÑÐ°Ð¹Ð» base.dm, Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐ¹ ÐŽÐ»Ñ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŒÐ°ÐºÑÐŸÑÐŸÐ²; ÑÑÐŸÑ ÑÐ°Ð¹Ð» ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐŸÑÐœÐŸÐ²ÐœÐŸÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÑÑÑÐ°ÐœÐžÑÑ.</Text>
+<Text id="704">ÐÐ°ÐºÑÐŸÑÑ ÐžÐŒÐµÑÑ ÐžÐŒÐµÐœÐ°, ÐºÐŸÑÐŸÑÑÐµ ÐœÐ°ÑÐžÐœÐ°ÑÑÑÑ Ðž Ð·Ð°ÐºÐ°ÐœÑÐžÐ²Ð°ÑÑÑÑ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐŒ Ð¿ÐŸÐŽÑÐµÑÐºÐžÐ²Ð°ÐœÐžÑ, Ð° ÐžÑ
+ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ Ð·Ð°ÐºÐ»ÑÑÐ°ÐµÑÑÑ Ð² ÑÐžÐ³ÑÑÐœÑÐµ ÑÐºÐŸÐ±ÐºÐž. Ð¡ÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÑÐµÐºÑÑÐŸÐŒ, HTML (Ð²ÐºÐ»ÑÑÐ°Ñ ÑÑÑÐ»ÐºÐž Ðº Java-Ð°Ð¿Ð¿Ð»ÐµÑÐ°ÐŒ Ðž JavaScript), ÐžÐŒÐµÐœÐµÐŒ ÐŒÐ°ÐºÑÐŸÑÐ° ÐžÐ»Ðž Ð»ÑÐ±ÐŸÐ¹ ÐºÐŸÐŒÐ±ÐžÐœÐ°ÑÐžÐµÐ¹ ÐžÐ· Ð²ÑÑÐµÐ¿ÐµÑÐµÑÐžÑÐ»ÐµÐœÐœÑÑ
+ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ². ÐÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÐ° ÐŸÑ base.dm ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÑÑÑÐ°ÐœÐžÑÑ, ÐµÑÐ»Ðž ÐŸÑÑÑÑÑÑÐ²ÑÐµÑ ÐºÐ°ÐºÐ°Ñ-Ð»ÐžÐ±ÐŸ ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÐ° ÐŸÑÐŒÐµÐœÑ:</Text>
+<CodeLine>_content_ {&lt;p&gt;&lt;h2&gt;Oops&lt;/h2&gt;_textdefaultcontent_}</CodeLine>
+<Text id="705">Ð¡ÑÑÐ°ÐœÐžÑÐ° Ð±ÑÐŽÐµÑ ÑÐžÑÐ°ÑÑ "Oops" ÐœÐ°Ð²ÐµÑÑ
+Ñ, Ðž Jextdefaultcontent _, ÐºÐŸÑÐŸÑÑÐ¹ ÐœÐ° Ð°ÐœÐ³Ð»ÐžÐ¹ÑÐºÐŸÐŒ ÑÐ·ÑÐºÐµ Ð±ÑÐŽÐµÑ Ð²ÑÐŽÐ°Ð²Ð°ÑÑ The requested page could not be found. Please use your browsers 'back' button or the above home button to return to the Greenstone Digital Library (ÐÐ°Ð¿ÑÑÐµÐœÐœÐ°Ñ ÑÑÑÐ°ÐœÐžÑÐ° ÐœÐµ ÐœÐ°Ð¹ÐŽÐµÐœÐ°. ÐÐŸÐ¶Ð°ÑÐ¹ÑÑÐ°, Ð²ÐŸÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµÑÑ ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ° Ð² Ð²Ð°ÑÐµÐŒ Ð±ÑÐŸÑÐ·ÐµÑÐµ ÐžÐ»Ðž ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ° ÐœÐ° ÐŽÐŸÐŒÐ°ÑÐœÑÑ ÑÑÑÐ°ÐœÐžÑÑ ÐŠÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone), ÐºÐ°Ðº Ðž ÐœÐ° ÐŽÑÑÐ³ÐžÑ
+ ÑÐ·ÑÐºÐ°Ñ
+.</Text>
+<Text id="706">_textdefaultcontent_ Ðž _content_ ÐŸÐ±Ð° Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸ ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ Ð² Ð¿Ð°ÐºÐµÑÐµ global, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŸÐœÐž Ð·Ð°Ð¿ÑÐ°ÑÐžÐ²Ð°ÑÑÑÑ Ð²ÑÐµÐŒÐž ÑÐ°ÑÑÑÐŒÐž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°. ÐÐ°ÐºÑÐŸÑÑ ÐŒÐŸÐ³ÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŒÐ°ÐºÑÐŸÑÑ ÐžÐ· ÐŽÑÑÐ³ÐžÑ
+ Ð¿Ð°ÐºÐµÑÐŸÐ², ÐœÐŸ ÑÐŸÐ³ÐŽÐ° ÐŸÐœÐž ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ Ð² Ð¿ÑÐµÑÐžÐºÑÐµ ÐžÑ
+ ÐžÐŒÐµÐœÐ° Ðž ÐžÐŒÑ Ð¿Ð°ÐºÐµÑÐ°. ÐÐ°Ð¿ÑÐžÐŒÐµÑ,</Text>
+<CodeLine>_collectionextra_ {This collection contains _about:numdocs_ documents. It was last built _about:builddate_ days ago.)</CodeLine>
+<Text id="707">ÐžÑÑ
+ÐŸÐŽÐžÑ ÐžÐ· english.dm Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐºÐ°Ðº Ð·Ð°ÐŽÐ°ÐœÐœÐŸÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. _collectionextra_ - ÑÐ°ÑÑÑ Ð¿Ð°ÐºÐµÑÐ° global , ÐœÐŸ _numdocs_ Ðž _builddate_ - ÐŸÐ±Ð° ÐžÐ·  Ð¿Ð°ÐºÐµÑÐ° about, ÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸ ÑÐ»ÐµÐŽÑÐµÑ Ð¿ÐžÑÐ°ÑÑ _about:wMsi_. </Text>
+<Text id="708">ÐÐ°ÑÐ°ÑÑÑÑ ÐŒÐ°ÐºÑÐŸÑ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÑÐ»ÐŸÐ²ÐœÑÐµ ÐžÐœÑÑÑÑÐºÑÐžÐž. ÐÐœÐž ÐœÐ°Ð¿ÐŸÐŒÐžÐœÐ°ÑÑ ÑÑÐ»ÐŸÐ²ÐœÐŸÐµ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÐµ ÑÑÑÐŸÐºÐž ÑÐŸÑÐŒÐ°ÑÐ°, ÐŸÐ¿ÐžÑÐ°ÐœÐœÐŸÐµ Ð²ÑÑÐµ, Ñ
+ÐŸÑÑ ÐžÑ
+ Ð²ÐžÐŽ ÐœÐµÐŒÐœÐŸÐ³ÐŸ ÐŸÑÐ»ÐžÑÐ°ÐµÑÑÑ. ÐÑÐœÐŸÐ²ÐœÐŸÐ¹ ÑÐŸÑÐŒÐ°Ñ - _If_ (Ñ
+, Ñ, z), Ð³ÐŽÐµ Ñ
+ - ÑÑÐ»ÐŸÐ²ÐžÐµ, Ñ -ÐŒÐ°ÐºÑÐŸÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ, ÐµÑÐ»Ðž ÑÑÐ»ÐŸÐ²ÐžÐµ ÐžÑÑÐžÐœÐœÐŸ, Ðž z -ÐŒÐ°ÐºÑÐŸÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ, ÐµÑÐ»Ðž ÑÑÐ»ÐŸÐ²ÐžÐµ ÑÐ²Ð»ÑÐµÑÑÑ Ð»ÐŸÐ¶ÐœÑÐŒ. ÐÐ¿ÐµÑÐ°ÑÐŸÑÑ ÑÑÐ°Ð²ÐœÐµÐœÐžÑ ÑÐµ Ð¶Ðµ ÑÐ°ÐŒÑÐµ, ÑÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð² Perl (ÐŒÐµÐœÑÑÐµ ÑÐµÐŒ, Ð±ÐŸÐ»ÑÑÐµ ÑÐµÐŒ, ÑÐ°Ð²ÐœÐŸ, ÐœÐµ ÑÐ°Ð²ÐœÐŸ). Ð ÑÑÐŸÐŒ Ð¿ÑÐžÐŒÐµÑÐµ base.dm ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐµÑÐµÐœÐžÑ Ð·Ð°ÐŽÐ°ÑÐž ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ Ð²ÐµÑÐœÐµÐ¹ ÑÐ°ÑÑÐž ÑÑÑÐ°ÐœÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž about (ÑÑÑÐ°ÐœÐžÑÐ° ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž):</Text>
+<CodeLine>_imagecollection_ {</CodeLine>
+<CodeLine>       _If_( "_iconcollection_ " ne "",</CodeLine>
+<CodeLine>                 &lt;a href = "_httppageabout_ "&gt; </CodeLine>
+<CodeLine>                         &lt;img src = "_iconcollection_ " border = 0&gt;</CodeLine>
+<CodeLine>                         &lt;/a&gt;,</CodeLine>
+<CodeLine>                 _imagecollectionv_)</CodeLine>
+<CodeLine>}</CodeLine>
+<Text id="709">ÐÐ°ÐœÐœÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ Ð²ÑÐ³Ð»ÑÐŽÐžÑ ÐœÐµÐŒÐœÐŸÐ³ÐŸ ÐœÐµÐ¿ÐŸÐœÑÑÐœÑÐŒ. _iconcollection_ ÐŸÑÑÑÐ»Ð°ÐµÑ Ðº Ð¿ÑÑÑÐŸÐ¹ ÑÑÑÐŸÐºÐµ, ÐµÑÐ»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐœÐµ ÐžÐŒÐµÐµÑ ÐžÐºÐŸÐœÐºÐž ÐžÐ»Ðž ÐžÐŒÐµÐœÐž ÑÐ°Ð¹Ð»Ð° ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ. ÐÐµÑÐµÑÑÐ°Ð·ÐžÑÑÐµÐŒ Ð²ÑÑÐµÑÐ¿ÐŸÐŒÑÐœÑÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ: ÐÑÐ»Ðž ÐµÑÑÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð²ÑÐ²ÐµÑÑÐž Ð² Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐµ ÑÑÑÐ°ÐœÐžÑÑ About this Collection (ÑÐ¿ÐŸÐŒÑÐœÑÑÑÐ¹ Jittppageabout _), Ð° Ð·Ð°ÑÐµÐŒ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ; ÐžÐœÐ°ÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²ÐœÑÐ¹ Ð²ÑÐ²ÐŸÐŽ _imagecollectionv_.</Text>
+<Text id="710">ÐÐ°ÐºÑÐŸÑÑ ÐŒÐŸÐ³ÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ Ð°ÑÐ³ÑÐŒÐµÐœÑÑ. ÐÐŸÑ Ð²ÑÐŸÑÐŸÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ ÐŽÐ»Ñ _imagecollection_ ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐœÐµÐŒÐµÐŽÐ»ÐµÐœÐœÐŸ ÑÐ»ÐµÐŽÑÐµÑ Ð·Ð° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµÐŒ, ÐŽÐ°ÐœÐœÑÐŒ Ð²ÑÑÐµ Ð² ÑÐ°Ð¹Ð»Ðµ base.dm:</Text>
+<CodeLine>_imagecollection_[v=1]{_imagecollectionv_}</CodeLine>
+<Text id="711">ÐÐ°ÑÐ°ÐŒÐµÑÑ [v=l] ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ, ÑÑÐŸ Ð²ÑÐŸÑÐŸÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ, ÐºÐŸÐ³ÐŽÐ° Greenstone ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ð² ÑÐµÐºÑÑÐŸÐ²ÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ. ÐÐ°ÐºÑÐŸÑ ÑÐ·ÑÐºÐ° ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ð¿ÐŸÑ
+ÐŸÐ¶Ðµ -ÐžÑÐºÐ»ÑÑÐµÐœÐžÐµ ÑÐŸÑÑÐ°Ð²Ð»ÑÐµÑ english.dm, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÑÐ²Ð»ÑÐµÑÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµÐŒ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, Ð²ÑÐµ ÐŒÐ°ÐºÑÐŸÑÑ ÑÐ·ÑÐºÐ° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÑÐ·ÑÐº ÐºÐ°Ðº Ð¿Ð°ÑÐ°ÐŒÐµÑÑ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ,</Text>
+<CodeLine>_textimagehome_ {Home Page}</CodeLine>
+<Text id="712">Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ Ð² Ð°ÐœÐ³Ð»ÐžÐ¹ÑÐºÐŸÐŒ ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ðµ ÑÐ·ÑÐºÐ°, ÑÐŸÐ³ÐŽÐ° ÐºÐ°Ðº ÐŽÐ»Ñ ÐœÐµÐŒÐµÑÐºÐŸÐ¹ Ð²ÐµÑÑÐžÐž</Text>
+<CodeLine>_textimagehome_ [l=de] {Hauptaseite}</CodeLine>
+<Text id="713">ÐÐœÐ³Ð»ÐžÐ¹ÑÐºÐ°Ñ Ðž ÐœÐµÐŒÐµÑÐºÐ°Ñ Ð²ÐµÑÑÐžÐž ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ Ð² ÑÐŸÐŒ Ð¶Ðµ ÑÐ°ÐŒÐŸÐŒ Ð¿Ð°ÐºÐµÑÐµ, Ñ
+ÐŸÑÑ Ðž Ð² ÐŸÑÐŽÐµÐ»ÑÐœÑÑ
+ ÑÐ°Ð¹Ð»Ð°Ñ
+ (ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ Ð¿Ð°ÐºÐµÑÐ° ÐŒÐŸÐ³ÑÑ ÐŸÑ
+Ð²Ð°ÑÐžÑÑ Ð±ÐŸÐ»ÑÑÐµ, ÑÐµÐŒ ÐŸÐŽÐžÐœ ÑÐ°Ð¹Ð»). Greenstone ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ /Ð¿Ð°ÑÐ°ÐŒÐµÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ Ð·Ð°Ð¿ÑÑÐºÐ°, ÑÑÐŸÐ±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÑÐ·ÑÐº ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ.</Text>
+<Figure id="part_of_the_aboutdm_macro_file">
+<Title>
+<Text id="714">Part of the <i>about.dm</i> macro file</Text>
+</Title>
+<CodeLine>package about</CodeLine>
+<CodeLine>##############################################</CodeLine>
+<CodeLine># about page content</CodeLine>
+<CodeLine>###############################################</CodeLine>
+<CodeLine>_pagetitle_ {_collectionname_}</CodeLine>
+<CodeLine>_content_ {</CodeLine>
+<CodeLine>&lt;center&gt;</CodeLine>
+<CodeLine>_navigationbar_</CodeLine>
+<CodeLine>&lt;/center&gt;</CodeLine>
+<CodeLine>_query:queryform_</CodeLine>
+<CodeLine>&lt;p&gt;_iconblankbar_</CodeLine>
+<CodeLine>&lt;p&gt;_textabout_</CodeLine>
+<CodeLine>_textsubcollections_</CodeLine>
+<CodeLine>&lt;h3&gt;_help:textsimplehelpheading_&lt;/h3&gt;</CodeLine>
+<CodeLine>_help:simplehelp_</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine>_textabout_ {</CodeLine>
+<CodeLine>&lt;h3&gt;_textabcol_&lt;/h3&gt;</CodeLine>
+<CodeLine>_Global:collectionextra_</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="715">Ð Ð·Ð°ÐºÐ»ÑÑÐµÐœÐžÐµ Ð¿ÑÐžÐ²ÐµÐŽÐµÐŒ ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="part_of_the_aboutdm_macro_file"/>, ÐœÐ° ÐºÐŸÑÐŸÑÐŸÐŒ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ ÐŸÑÑÑÐ²ÐŸÐº ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ð° aboutdm, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ð³ÐµÐœÐµÑÐ°ÑÐžÐž ÑÑÑÐ°ÐœÐžÑÑ "About this collection" (Ð ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž) ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐŽÐµÑÑ ÑÐ°Ð±ÐŸÑÑ ÑÑÐµÑ
+ ÐŒÐ°ÐºÑÐŸÑÐŸÐ² _pagetitle _, _content_ Ðž _textabout_.</Text>
+</Content>
+</Subsection>
+<Subsection id="using_macros">
+<Title>
+<Text id="716">Using macros</Text>
+</Title>
+<Content>
+<Text id="717">ÐÐ°ÐºÑÐŸÑ ÑÐ²Ð»ÑÐµÑÑÑ ÐŒÐŸÑÐœÑÐŒ ÐžÐœÑÑÑÑÐŒÐµÐœÑÐŸÐŒ Ðž ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐœÐµÐŒÐœÐŸÐ³ÐŸ ÐœÐµÐ¿ÐŸÐœÑÑÐµÐœ. ÐÐŽÐœÐ°ÐºÐŸ, Ð¿ÑÐž Ñ
+ÐŸÑÐŸÑÐµÐŒ Ð·ÐœÐ°ÐœÐžÐž HTML Ðž ÐœÐµÐ±ÐŸÐ»ÑÑÐŸÐŒ Ð¿ÑÐ°ÐºÑÐžÑÐµÑÐºÐŸÐŒ ÐŸÐ¿ÑÑÐµ, ÐŸÐœÐž ÑÑÐ°ÐœÐŸÐ²ÑÑÑÑ Ð±ÑÑÑÑÑÐŒ Ðž Ð¿ÑÐŸÑÑÑÐŒ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž Ð²Ð°ÑÐµÐ³ÐŸ Greenstone -ÑÐ°Ð¹ÑÐ°.</Text>
+<Text id="718">ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐµÑÐ»Ðž Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ ÑÐŸÐ·ÐŽÐ°ÑÑ ÑÑÐ°ÑÐžÑÐµÑÐºÑÑ ÑÑÑÐ°ÐœÐžÑÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐœÐ°Ð¿ÐŸÐŒÐžÐœÐ°Ð»Ð° Ð±Ñ Ð²Ð°Ñ ÑÐµÐºÑÑÐžÐ¹ Greenstone-ÑÐ°Ð¹Ñ. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐœÐŸÐ²ÑÐ¹ Ð¿Ð°ÐºÐµÑ, ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÐ¹ static, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, Ð² ÐœÐŸÐ²ÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ Ðž ÐŸÑÐŒÐµÐœÐžÑÑ ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÑ _content_ . ÐÐŸÐ±Ð°Ð²ÑÑÐµ ÐœÐŸÐ²ÐŸÐµ ÐžÐŒÑ ÑÐ°Ð¹Ð»Ð° Ð² ÑÐ¿ÐžÑÐŸÐº ÐŒÐ°ÐºÑÐŸÑÐŸÐ² Ð² GSDLHOME/etc/main.cfg, ÐºÐŸÑÐŸÑÑÐ¹ Greenstone Ð·Ð°Ð³ÑÑÐ¶Ð°ÐµÑ ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐ°Ð·. ÐÐ°ÐºÐŸÐœÐµÑ, ÐŸÐ±ÑÐ°ÑÐžÑÐµÑÑ Ðº ÐœÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð²Ð°Ñ Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÑÐ¹ URL Greenstone, ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑ Ð² ÐºÐŸÐœÐµÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑ ?a=p&amp;p=static (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, http://servername/cgi-bin/library?a=p&amp;p=static).</Text>
+<Text id="719">Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÑÑÑ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Greenstone, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ Ð¿Ð°ÐºÐµÑÑ base Ðž style. Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐŽÐŸÐŒÐ°ÑÐœÑÑ ÑÑÑÐ°ÐœÐžÑÑ Greenstone, ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÑÐ¹ÑÐµ Ð¿Ð°ÐºÐµÑ home (ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐŒÐŸÐ¶ÐœÐŸ ÐœÐ°Ð¹ÑÐž Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÐž ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð¿ÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ). ÐÐ»Ñ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ ÑÑÑÐ°ÐœÐžÑÑ Ð·Ð°Ð¿ÑÐŸÑÐŸÐ² ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÑÐ¹ÑÐµ query.dm.</Text>
+<Text id="720">Ð¡Ð²ÐŸÐ±ÐŸÐŽÐœÐŸ ÑÐºÑÐ¿ÐµÑÐžÐŒÐµÐœÑÐžÑÑÐ¹ÑÐµ Ñ ÐŒÐ°ÐºÑÐŸÑÐ°ÐŒÐž. ÐÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ ÐœÐµÐŒÐµÐŽÐ»ÐµÐœÐœÐŸ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŒÐ°ÐºÑÐŸÑ ÐžÐœÑÐµÑÐ¿ÑÐµÑÐžÑÑÐµÑÑÑ Ð¿ÐŸ ÐŒÐµÑÐµ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÑÑÐ°ÐœÐžÑÑ. ÐÐ°ÐºÑÐŸÑÐ·ÑÐº - Ð¿ÐŸÐ»ÐµÐ·ÐœÑÐ¹ ÐžÐœÑÑÑÑÐŒÐµÐœÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÐŒÐŸÐ¶ÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ, ÑÑÐŸÐ±Ñ ÑÐŸÐ·ÐŽÐ°ÑÑ Ð²Ð°Ñ ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÑÐ¹, ÑÐœÐžÐºÐ°Ð»ÑÐœÑÐ¹ ÑÑÐžÐ»Ñ ÑÐ°Ð¹ÑÐ° ÐœÐ° Ð±Ð°Ð·Ðµ Greenstone.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="the_packages_directory">
+<Title>
+<Text id="721">ÐÐžÑÐµÐºÑÐŸÑÐžÑ packages</Text>
+</Title>
+<Content>
+<Table id="the_packages_directory_1">
+<Title>
+<Text id="722">ÐÐžÑÐµÐºÑÐŸÑÐžÑ packages</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="217">
+<Text id="723"><b>ÐÐ°ÐºÐµÑ</b></Text>
+</th>
+<th width="180">
+<Text id="724"><b>URL</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="725"><i>mg</i></Text>
+</th>
+<th width="217">
+<Text id="726">MG, ÑÐŸÐºÑÐ°ÑÐµÐœÐœÐŸ ÐŸÑ âManaging Gigabytes.â Ð¡Ð¶Ð°ÑÐžÐµ, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž Ð¿ÐŸÐžÑÐºÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ð»ÐŸÑÑ ÐŽÐ»Ñ ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ ÑÐµÐºÑÑÐŸÐ²ÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+ Greenstone.</Text>
+</th>
+<th width="180">
+<Text id="727"><i>www.citri.edu.au/mg</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="728"><i>wget</i></Text>
+</th>
+<th width="217">
+<Text id="729">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ web Ð·ÐµÑÐºÐ°Ð»ÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŽÐ»Ñ Greenstone. ÐÐ°Ð¿ÐžÑÐ°ÐœÐŸ ÐœÐ° C++.</Text>
+</th>
+<th width="180">
+<Text id="730"><i>www.tuwien.ac.at/~prikryl/ wget.html</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="731"><i>w3mir</i></Text>
+</th>
+<th width="217">
+<Text id="732">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° web-Ð·ÐµÑÐºÐ°Ð»ÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐœÐ°Ð¿ÐžÑÐ°ÐœÐœÐ°Ñ ÐœÐ° Perl. ÐÐµ ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐžÑÐµÐ»ÑÐœÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐŸÐ¹ Ð·ÐµÑÐºÐ°Ð»ÐžÑÐŸÐ²Ð°ÐœÐžÑ Greenstone, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŸÑÐœÐŸÐ²Ð°ÐœÐ° ÐœÐ° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐ¹ ÑÑÑÐ°ÑÐµÐ»ÐŸÐ¹ Ð²ÐµÑÑÐžÐž ÐœÐµÐºÐŸÑÐŸÑÐŸÐ³ÐŸ Perl-ÐŒÐŸÐŽÑÐ»Ñ (ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž w3mir). ÐÐ°ÐºÐµÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð¿ÑÐž Ð·Ð°Ð¿ÑÑÐºÐµ Ð¿ÐŸÐŽ Windows.</Text>
+</th>
+<th width="180">
+<Text id="733"><i>www.math.uio.no/~janl/w3mir</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="734"><i>windows</i></Text>
+</th>
+<th width="217">
+<Text id="735">ÐÐ°ÐºÐµÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð¿ÑÐž Ð·Ð°Ð¿ÑÑÐºÐµ Ð¿ÐŸÐŽ Windows.</Text>
+</th>
+<th width="180">
+<Text id="736"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="737"><i>windows/gdbm</i></Text>
+</th>
+<th width="217">
+<Text id="738">ÐÐµÑÑÐžÑ GNU Database Manager ÐŽÐ»Ñ ÑÑÐµÐŽÑ Windows. GDBM ÑÐ²Ð»ÑÐµÑÑÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐ¹ ÑÐ°ÑÑÑÑ Linux.</Text>
+</th>
+<th width="180">
+<Text id="739"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="740"><i>windows/crypt</i></Text>
+</th>
+<th width="217">
+<Text id="741">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐºÐŸÐŽÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ð¿Ð°ÑÐŸÐ»ÐµÐ¹ ÐœÐ° ÑÑÐŸÐ²ÐœÐµ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ Greenstone.</Text>
+</th>
+<th width="180">
+<Text id="742"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="743"><i>windows/stlport</i></Text>
+</th>
+<th width="217">
+<Text id="744">Standard Template Library (Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° ÑÐ°Ð±Ð»ÐŸÐœÐŸÐ²) ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð¿ÑÐž ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐžÐž Greenstone ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸ Ñ ÐœÐµÐºÐŸÑÐŸÑÑÐŒÐž ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐŸÑÐ°ÐŒÐž Windows.</Text>
+</th>
+<th width="180">
+<Text id="745"><i>â</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="746"><i>wv</i></Text>
+</th>
+<th width="217">
+<Text id="747">ÐÐŸÐœÐ²ÐµÑÑÐµÑ Microsoft Word (ÐŽÐ»Ñ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐŸÑÐŒÐ°ÑÐ° Word).</Text>
+</th>
+<th width="180">
+<Text id="748"><i>sourceforge.net/projects/ wvware</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="749"><i>pdftohtml</i></Text>
+</th>
+<th width="217">
+<Text id="750">ÐÐŸÐœÐ²ÐµÑÑÐŸÑ PDF ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐŸÑÐŒÐ°ÑÐ° PDF.</Text>
+</th>
+<th width="180">
+<Text id="751"><i>www.ra.informatik.uni-stutt gart.de/ <br/>~gosho/pdftohtml</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="752"><i>yaz</i></Text>
+</th>
+<th width="217">
+<Text id="753">Z39.50 Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐºÐ»ÐžÐµÐœÑÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ ÐŽÐ»Ñ ÐžÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ ÑÐŸÐ²ÐŒÐµÑÑÐžÐŒÐŸÑÑÐž Greenstone Ñ Z39.50. Ð Ð¿ÑÐŸÐ³ÑÐµÑÑÐµ ÑÐŸÐŸÐ±ÑÐ°ÑÑ Ð² ÑÐ°Ð¹Ð»Ðµ README.gsdl.</Text>
+</th>
+<th width="180">
+<Text id="754"><i>www.indexdata.dk</i></Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="755">ÐÐžÑÐµÐºÑÐŸÑÐžÑ packages , ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÐºÐŸÑÐŸÑÐŸÐ¹ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="the_packages_directory_1"/>, - ÑÑÐŸ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ, Ð² ÐºÐŸÑÐŸÑÐŸÐ¹ Ñ
+ÑÐ°ÐœÑÑÑÑ Ð²ÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ Greenstone, ÐœÐŸ ÐœÐ°Ð¿ÐžÑÐ°ÐœÐœÑÐµ ÐŽÑÑÐ³ÐžÐŒÐž ÐžÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐžÐŒÐž Ð³ÑÑÐ¿Ð¿Ð°ÐŒÐž. ÐÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ, ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÐµÐŒÐŸÐµ ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸ Ñ Greenstone, Ð¿ÐŸÐ¿Ð°ÐŽÐ°ÐµÑ Ð¿ÐŸÐŽ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ ÐÐžÑÐµÐœÐ·ÐžÐŸÐœÐœÐŸÐ³ÐŸ ÑÐŸÐ³Ð»Ð°ÑÐµÐœÐžÑ ÐŸ ÑÐ²ÐŸÐ±ÐŸÐŽÐœÐŸÐŒ ÐŽÐŸÑÑÑÐ¿Ðµ GNU. ÐÐ°Ð¿ÑÑÐºÐ°ÐµÐŒÑÐµ ÑÐ°Ð¹Ð»Ñ, Ð¿ÑÐŸÐžÐ·Ð²ÐµÐŽÐµÐœÐœÑÐµ ÑÑÐžÐŒÐž Ð¿Ð°ÐºÐµÑÐ°ÐŒÐž, Ð¿ÐŸÐŒÐµÑÐµÐœÑ Ð² ÐºÐ°ÑÐ°Ð»ÐŸÐ³ Greenstone -bin. ÐÐ°Ð¶ÐŽÑÐ¹ Ð¿Ð°ÐºÐµÑ Ñ
+ÑÐ°ÐœÐžÑÑÑ Ð² ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÐŸÐŒ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ðµ. ÐÐœÐž ÐŸÐ±Ð»Ð°ÐŽÐ°ÑÑ ÑÐžÑÐŸÐºÐžÐŒ ÑÐ¿ÐµÐºÑÑÐŸÐŒ ÑÑÐœÐºÑÐžÐ¹, ÐŸÑ ÐžÐœÐŽÐµÐºÑÐ°ÑÐžÐž Ðž ÑÐ¶Ð°ÑÐžÑ ÐŽÐŸ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Microsoft Word Ð² HTML. ÐÐ°Ð¶ÐŽÑÐ¹ Ð¿Ð°ÐºÐµÑ ÐžÐŒÐµÐµÑ README ÑÐ°Ð¹Ð», ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="the_greenstone_runtime_system">
+<Title>
+<Text id="756">Ð Ð°Ð±ÐŸÑÐ° ÑÐžÑÑÐµÐŒÑ Greenstone</Text>
+</Title>
+<Content>
+<Text id="757">Ð­ÑÐ° Ð³Ð»Ð°Ð²Ð° ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ Greenstone, ÑÑÐŸÐ±Ñ Ð²Ñ ÐŒÐŸÐ³Ð»Ðž Ð¿ÐŸÐœÑÑÑ, ÑÐ²ÐµÐ»ÐžÑÐžÑÑ Ðž ÑÐ°ÑÑÐžÑÐžÑÑ ÐµÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž. ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÐœÐ°Ð¿ÐžÑÐ°ÐœÐŸ ÐœÐ° Ð¡ ++ Ðž Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐµÑ Ð±ÐŸÐ»ÑÑÐžÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ Ð²ÐžÑÑÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÐœÐ°ÑÐ»ÐµÐŽÐžÑ. ÐÑÐ»Ðž Ð²Ñ ÐœÐµÐ·ÐœÐ°ÐºÐŸÐŒÑ Ñ ÑÑÐžÐŒ ÑÐ·ÑÐºÐŸÐŒ, Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÐžÐ·ÑÑÐžÑÑ ÐµÐ³ÐŸ Ð¿ÐµÑÐµÐŽ ÑÐµÐŒ, ÐºÐ°Ðº Ð¿ÑÐžÑÑÑÐ¿ÐžÑÑ Ðº ÑÐ°Ð±ÐŸÑÐµ. ÐÐµÐ¹ÑÐµÐ»Ñ Ðž ÐÐµÐ¹ÑÐµÐ»Ñ (1994) Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²ÐžÐ»Ðž Ð²ÑÐµÑÑÐŸÑÐŸÐœÐœÑÑ ÐŸÐ±ÑÑÐ°ÑÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, Ð° Ð¡ÑÑÐ°ÑÑÑÑÑÐ¿ (1997) - Ð»Ð°ÐºÐŸÐœÐžÑÐœÑÐ¹ ÑÐ¿ÑÐ°Ð²ÐŸÑÐœÐžÐº. </Text>
+<Text id="758">ÐÑ ÐœÐ°ÑÐžÐœÐ°ÐµÐŒ ÑÐ°ÑÑÐºÐ°Ð· ÐŸ ÑÐžÐ»ÐŸÑÐŸÑÐžÐž ÐŽÐžÐ·Ð°Ð¹ÐœÐ° Ð¿ÐŸÑÐ»Ðµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ, ÑÐ°Ðº ÐºÐ°Ðº ÐŸÐœ Ð±ÑÐŽÐµÑ ÐœÐ°Ð¿ÑÑÐŒÑÑ Ð·Ð°Ð²ÐžÑÐµÑÑ ÐŸÑ ÑÑÐŸÐ³ÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ. Ð¢ÐµÐ¿ÐµÑÑ Ð¿ÑÐžÑÑÑÐ¿ÐžÐŒ Ðº ÐŽÐµÑÐ°Ð»ÑÐŒ, ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ ÑÐŸÑÑÐŸÐžÑ ÐŸÑÐœÐŸÐ²ÐœÐ°Ñ ÑÐ°ÑÑÑ Ð³Ð»Ð°Ð²Ñ. ÐÐµÑÑÐžÑ Greenstone, ÐŸÐ¿ÐžÑÐ°ÐœÐœÐ°Ñ Ð·ÐŽÐµÑÑ - ÑÑÐŸ CGI-Ð²ÐµÑÑÐžÑ (Web Library if for Windows users/Web -Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Windows). Windows Local Library ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÑÑ Ð¶Ðµ ÑÐ°ÐŒÑÑ ÐžÑÑ
+ÐŸÐŽÐœÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÐœÐŸ ÐžÐŒÐµÐµÑ Ð²ÑÑÑÐŸÐµÐœÐœÑÐ¹ web-ÑÐµÑÐ²ÐµÑ. ÐÐ»ÑÑ ÐºÐŸ Ð²ÑÐµÐŒÑ, Local Library - Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸ Ð¿ÑÐŸÐŽÐŸÐ»Ð¶Ð°ÑÑÐžÐ¹ÑÑ Ð¿ÑÐŸÑÐµÑÑ. </Text>
+<Section id="process_structure">
+<Title>
+<Text id="759">Ð¡ÑÑÑÐºÑÑÑÐ° Ð¿ÑÐŸÑÐµÑÑÐ°</Text>
+</Title>
+<Content>
+<Figure id="overview_of_a_general_greenstone_system">
+<Title>
+<Text id="760">ÐÑÐ°ÑÐºÐžÐ¹ ÐŸÐ±Ð·ÐŸÑ ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ Greenstone</Text>
+</Title>
+<File width="382" height="335" url="images/Dev_Fig_044.png"/>
+</Figure>
+<Text id="761">ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/> Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ, ÐºÐ°Ðº ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ (ÐŸÐœÐž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ Ð² Ð²ÐžÐŽÐµ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐœÑÑ
+ ÑÐµÑÐŒÐžÐœÐ°Ð»ÐŸÐ² ÐœÐ°Ð²ÐµÑÑ
+Ñ ÐŽÐžÐ°Ð³ÑÐ°ÐŒÐŒÑ) ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑÑ Ðº ÑÑÐµÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒ Greenstone. ÐÐµÑÐµÐŽ ÑÐµÐŒ, ÐºÐ°Ðº Ð¿ÑÐµÐŽÑÑÐ°ÑÑ Ð² ÑÐµÐ¶ÐžÐŒÐµ on-line, ÑÑÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÐŸÑ
+ÐŸÐŽÑÑ Ð¿ÑÐŸÑÐµÑÑÑ ÐžÐŒÐ¿ÐŸÑÑÐ° Ðž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÐŸÐ¿ÐžÑÐ°ÐœÑ Ð² Ð¿ÑÐµÐŽÑÐŽÑÑÐžÑ
+ Ð³Ð»Ð°Ð²Ð°Ñ
+. Ð¡ÐœÐ°ÑÐ°Ð»Ð° ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÑÐµ Ð²ÐœÐžÐ·Ñ ÑÐžÑÑÐœÐºÐ°, ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÑ Ð² XML-ÑÐŸÐ²ÐŒÐµÑÑÐžÐŒÑÐ¹ Ð€ÐŸÑÐŒÐ°Ñ ÐÑÑ
+ÐžÐ²Ð° Greenstone. Ð¢ÐµÐ¿ÐµÑÑ ÐŽÐ»Ñ ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐŸÐ·ÐŽÐ°ÐœÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÐŽÐŸÑÑÑÐ¿ÐœÑÐµ ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ° ÐžÐœÐŽÐµÐºÑÑ Ðž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐ°Ñ Ð±Ð°Ð·Ð° ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÐ°Ñ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐžÐµ ÑÑÑÑÐºÑÑÑÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°. ÐÐŸÐœÐµÑÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð³ÐŸÑÐŸÐ²Ð° Ðº ÑÐ°Ð±ÐŸÑÐµ Ð² ÑÐµÐ¶ÐžÐŒÐµ on-line Ðž ÑÐ¿ÐŸÑÐŸÐ±ÐœÐ° Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ Ð¿ÐŸ Ð·Ð°Ð¿ÑÐŸÑÐ°ÐŒ.</Text>
+<Text id="762">ÐÐ²Ð° ÑÐµÐœÑÑÐ°Ð»ÑÐœÑÑ
+ ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑÐ° ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÑÑ ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ: "receptionists" (ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÑ) Ðž "collection servers" (ÑÐµÑÐ²ÐµÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž). Ð¡ ÑÐŸÑÐºÐž Ð·ÑÐµÐœÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ, ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÑ - ÑÐŸÑÐºÐ° ÐºÐŸÐœÑÐ°ÐºÑÐ° Ñ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐŸÐ¹. ÐÐœÐž Ð¿ÑÐžÐœÐžÐŒÐ°ÑÑ Ð·Ð°Ð¿ÑÐŸÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð² ÑÐŸÑÐŒÐµ ÐºÐ»Ð°Ð²ÐžÐ°ÑÑÑÐœÐŸÐ³ÐŸ Ð²Ð²ÐŸÐŽÐ° Ðž ÑÐµÐ»ÑÐºÐŸÐ² ÐŒÑÑÐž, Ð°ÐœÐ°Ð»ÐžÐ·ÐžÑÑÑÑ ÐžÑ
+, Ð° Ð·Ð°ÑÐµÐŒ Ð¿ÐŸÑÑÐ»Ð°ÑÑ Ð·Ð°Ð¿ÑÐŸÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐŒÑ ÑÐµÑÐ²ÐµÑÑ (ÐžÐ»Ðž ÑÐµÑÐ²ÐµÑÐ°ÐŒ) ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŽÐµÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑÑÑ ÐŒÐµÑÑÐŸÐœÐ°Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÐµ ÑÑÐµÐ±ÑÐµÐŒÐŸÐ¹ ÑÐ°ÑÑÐž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž Ðž Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑÑÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÑ ÐŽÐ»Ñ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ. Ð¡ÐµÑÐ²ÐµÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐµÐ¹ÑÑÐ²ÑÑÑ ÐºÐ°Ðº Ð°Ð±ÑÑÑÐ°ÐºÑÐœÑÐ¹ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒ, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð² ÑÐŸ Ð²ÑÐµÐŒÑ ÐºÐ°Ðº ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÑ ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÑ Ð·Ð° ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ.</Text>
+<Figure id="greenstone_system_using_the_null_protocol">
+<Title>
+<Text id="763">Ð¡ÐžÑÑÐµÐŒÐ° Greenstone, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÐ°Ñ ÐœÑÐ»ÐµÐ²ÐŸÐ¹ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»</Text>
+</Title>
+<File width="329" height="424" url="images/Dev_Fig_046.png"/>
+</Figure>
+<Text id="764">ÐÐ°Ðº Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/>, ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÑ ÑÐ²ÑÐ·ÑÐ²Ð°ÑÑÑÑ Ñ ÑÐµÑÐ²ÐµÑÐ°ÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ Ð¿ÑÐŸÑÐŸÐºÐŸÐ». ÐÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ ÑÑÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° Ð·Ð°Ð²ÐžÑÐžÑ ÐŸÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°, ÐœÐ° ÐºÐŸÑÐŸÑÐŸÐŒ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÑÐžÑÑÐµÐŒÐ° ÑÐžÑÑÐŸÐ²ÑÑ
+ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐº. ÐÐ°ÐžÐ±ÐŸÐ»ÐµÐµ Ð¿ÑÐŸÑÑÐŸÐ¹ Ðž Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÐžÐ¹ Ð²ÑÐ±ÐŸÑ - ÑÑÐŸ ÐŸÐŽÐžÐœ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ Ðž ÐŸÐŽÐžÐœ ÑÐµÑÐ²ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ ÐŸÐ±Ð° ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÐœÐ° ÐŸÐŽÐœÐŸÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ. ÐÑ Ð¿ÐŸÐ»ÑÑÐ°ÐµÑÐµ ÐžÐŒÐµÐœÐœÐŸ ÑÐ°ÐºÑÑ ÐŒÐŸÐŽÐžÑÐžÐºÐ°ÑÐžÑ, ÐºÐŸÐ³ÐŽÐ° ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÐµ ÑÐžÑÑÐµÐŒÑ Greenstone Ñ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ°ÐŒÐž Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ. Ð ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐŸÐ±Ð° Ð¿ÑÐŸÑÐµÑÑÐ° ÐŸÐ±ÑÐµÐŽÐžÐœÐµÐœÑ Ð² ÐŸÐŽÐžÐœ Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÐŒÑÐ¹ ÑÐ°Ð¹Ð» (ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÑÐ¹ library), Ðž ÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° ÑÐ²ÐŸÐŽÐžÑÑÑ Ðº ÑÐŸÐ·ÐŽÐ°ÐœÐžÑÑ ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÑÑ
+ Ð·Ð°Ð¿ÑÐŸÑÐŸÐ². ÐÑ ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒ ÑÑÐŸ null protocol (ÐœÑÐ»ÐµÐ²ÑÐŒ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»ÐŸÐŒ). ÐÐœ ÑÐŸÑÐŒÐžÑÑÐµÑ ÐŸÑÐœÐŸÐ²Ñ ÐŽÐ»Ñ ÑÑÐ°ÐœÐŽÐ°ÑÑÐ° out-of-the-box (ÐžÐ· Ð±Ð»ÐŸÐºÐ°) ÑÐžÑÑÐŸÐ²ÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐº Greenstone. ÐÐµ ÑÐ¿ÑÐŸÑÐµÐœÐœÐ°Ñ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐ° ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="greenstone_system_using_the_null_protocol"/> Ñ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐŸÐŒ, Ð¿ÑÐŸÑÐŸÐºÐŸÐ»ÐŸÐŒ Ðž ÑÐµÑÐ²ÐµÑÐŸÐŒ ÑÐŸÐ²ÐŸÐºÑÐ¿ÐœÐŸÑÑÐž, ÑÐ²ÑÐ·Ð°ÐœÐœÑÐŒÐž Ð²ÐŒÐµÑÑÐµ Ð² ÐŸÐŽÐžÐœ ÐŸÐ±ÑÐµÐºÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž. ÐŠÐµÐ»Ñ ÑÑÐŸÐ¹ Ð³Ð»Ð°Ð²Ñ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ ÐŸÐ±ÑÑÑÐœÐžÑÑ Ð²Ð°ÐŒ, ÐºÐ°Ðº Ð²ÑÐµ ÑÑÐŸ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ.</Text>
+<Text id="765">ÐÐ±ÑÑÐœÐŸ "ÑÐµÑÐ²ÐµÑ" - Ð¿ÐŸÑÑÐŸÑÐœÐœÑÐ¹ Ð¿ÑÐŸÑÐµÑÑ: ÐµÐŽÐžÐœÐŸÐ¶ÐŽÑ Ð·Ð°Ð¿ÑÑÐµÐœÐœÑÐ¹, ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸ, ÐŸÑÐ²ÐµÑÐ°Ñ ÐœÐ° Ð»ÑÐ±ÑÐµ Ð²Ñ
+ÐŸÐŽÑÑÐžÐµ Ð·Ð°Ð¿ÑÐŸÑÑ. ÐÐµÑÐŒÐŸÑÑÑ ÐœÐ° ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÑÐµÑÐ²ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐœÑÐ»ÐµÐ²ÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° ÐœÐµ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐµÑÐ²ÐµÑÐŸÐŒ Ð² Ð¿ÑÐžÐ²ÑÑÐœÐŸÐŒ ÑÐŒÑÑÐ»Ðµ ÑÐ»ÐŸÐ²Ð°. Ð€Ð°ÐºÑÐžÑÐµÑÐºÐž, ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐ°Ð·, ÐºÐŸÐ³ÐŽÐ° Ð²ÑÐ·ÑÐ²Ð°ÑÑ Ð»ÑÐ±ÑÑ web-ÑÑÑÐ°ÐœÐžÑÑ Greenstone, Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° library (CGI ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒÐŸÐŒ), ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÑÐ²ÐµÑÐ°ÐµÑ ÐœÐ° Ð·Ð°Ð¿ÑÐŸÑ Ðž Ð·Ð°ÑÐµÐŒ Ð²ÑÐ³ÑÑÐ¶Ð°ÐµÑÑÑ. Ð­ÑÐŸ ÐŒÑ ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒ "ÑÐµÑÐ²ÐµÑÐŸÐŒ", Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸ ÐŸÐœ ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœ ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ñ Ð±ÐŸÐ»ÐµÐµ ÐŸÐ±ÑÐµÐ¹ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐµÐ¹ (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/>).</Text>
+<Text id="766">Ð£ÐŽÐžÐ²ÐžÑÐµÐ»ÑÐœÐŸ, ÐœÐŸ ÑÐžÐºÐ» Ð·Ð°Ð¿ÑÑÐºÐ°, ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž Ðž Ð²ÑÑ
+ÐŸÐŽÐ° ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÐœÐµ ÑÐ°Ðº ÐŒÐµÐŽÐ»ÐµÐœÐœÐŸ, ÐºÐ°Ðº ÐŒÐŸÐ¶ÐœÐŸ Ð±ÑÐ»ÐŸ ÐŸÐ¶ÐžÐŽÐ°ÑÑ. ÐÐŽÐœÐ°ÐºÐŸ, ÑÑÐŸ Ð°Ð±ÑÐŸÐ»ÑÑÐœÐŸ ÐœÐµÑÑÑÐµÐºÑÐžÐ²ÐœÐŸ. Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒ Fast-CGI (www.fastcgi.com), ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ ÑÑÐµÐŽÐœÐžÐ¹ ÑÑÐŸÐ²ÐµÐœÑ. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐµÐ³ÐŸ, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° library ÐŒÐŸÐ¶ÐµÑ ÐŸÑÑÐ°ÑÑÑÑ Ð² Ð¿Ð°ÐŒÑÑÐž Ð² ÐºÐŸÐœÑÐµ Ð¿ÐµÑÐ²ÐŸÐ³ÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ Ðž ÐœÐ°ÐºÐ°Ð¿Ð»ÐžÐ²Ð°ÑÑ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐžÐµ ÐœÐ°Ð±ÐŸÑÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² CGI, ÑÐ°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ ÐžÐ·Ð±ÐµÐ³Ð°Ñ Ð¿ÐŸÐ²ÑÐŸÑÐœÑÑ
+ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐ¹ Ðž ÐŽÐŸÑÑÐžÐ³Ð°Ñ Ð¿ÐŸÑÑÐž ÑÐ°ÐºÐŸÐ³ÐŸ Ð¶Ðµ ÑÑÐŸÐ²ÐœÑ ÑÐ°Ð±ÐŸÑÑ, ÐºÐ°Ðº ÑÐµÑÐ²ÐµÑ. Fast-CGI Ð² Greenstone ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐºÐ°Ðº ÐŸÐ¿ÑÐžÑ, ÐŽÐŸÐ¿ÑÑÐºÐ°Ñ Ð¿ÐŸÐ²ÑÐŸÑÐœÑÑ ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐžÑ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ° Ñ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐŒÐž Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÐŒÐž.</Text>
+<Text id="767">ÐÐ°Ðº Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²Ð° ÐœÑÐ»ÐµÐ²ÐŸÐŒÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ñ, Ð¿ÑÐŸÑÐŸÐºÐŸÐ» Greenstone Ð±ÑÐ» ÑÐ°ÐºÐ¶Ðµ ÑÐŸÐ·ÐŽÐ°Ðœ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÐžÐ·Ð²ÐµÑÑÐœÐŸÐ¹ ÑÑ
+ÐµÐŒÑ CORBA (Slama et al, 1999). ÐÐœ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐŸÐ±ÑÐµÐŽÐžÐœÐµÐœÐœÑÑ ÐŸÐ±ÑÐµÐºÑÐœÐŸ-ÐŸÑÐžÐµÐœÑÐžÑÐŸÐ²Ð°ÐœÐœÑÑ Ð¿Ð°ÑÐ°ÐŽÐžÐ³ÐŒÑ, ÑÑÐŸÐ±Ñ ÑÐ°Ð·ÑÐµÑÐžÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒ Ð¿ÑÐŸÑÐµÑÑÐ°ÐŒ, Ð²ÑÐ¿ÐŸÐ»ÐœÑÑÑÐžÐŒÑÑ ÐœÐ° ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐœÑÑ
+ Ð¿Ð»Ð°ÑÑÐŸÑÐŒÐ°Ñ
+ Ðž ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÑ
+ ÐœÐ¿ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐ·ÑÐºÐ°Ñ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑ Ðº ÐŸÐŽÐœÐŸÐŒÑ Ðž ÑÐŸÐŒÑ Ð¶Ðµ ÐœÐ°Ð±ÐŸÑÑ ÑÐ°ÑÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÐŸÐ±ÑÐµÐºÑÐŸÐ² Ð² Internet (ÐžÐ»Ðž Ð»ÑÐ±ÐŸÐ¹ ÐŽÑÑÐ³ÐŸÐ¹ ÑÐµÑÐž). Ð¢ÐŸÐ³ÐŽÐ° ÑÑÐµÐœÐ°ÑÐžÐž, Ð¿ÐŸÐŽÐŸÐ±ÐœÐŸ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐœÐŸÐŒÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="overview_of_a_general_greenstone_system"/>, ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¿ÐŸÐ»ÐœÐŸÑÑÑÑ ÐŸÑÑÑÐµÑÑÐ²Ð»ÐµÐœÑ ÑÐŸ Ð²ÑÐµÐŒÐž ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐ°ÐŒÐž Ðž ÑÐµÑÐ²ÐµÑÐ°ÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐ°Ð±ÐŸÑÐ°ÑÑÐžÐŒÐž ÐœÐ° ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°Ñ
+.</Text>
+<Figure id="graphical_query_interface_to_greenstone">
+<Title>
+<Text id="768">ÐÑÐ°ÑÐžÑÐµÑÐºÐžÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð·Ð°Ð¿ÑÐŸÑÐ° Greenstone</Text>
+</Title>
+<File width="397" height="348" url="images/Dev_Fig_048.png"/>
+</Figure>
+<Text id="769">Ð­ÑÐŸ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑ ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ñ ÑÐµÐŒÐž Ð¶Ðµ ÑÐ°ÐŒÑÐŒÐž ÑÐžÑÑÐŸÐ²ÑÐŒÐž Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž ÐœÐ°ÐŒÐœÐŸÐ³ÐŸ Ð±ÐŸÐ»ÐµÐµ ÑÐ»ÐŸÐ¶ÐœÑÐµ ÐžÐœÑÐµÑÑÐµÐ¹ÑÑ. Ð ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð¿ÑÐžÐŒÐµÑÐ° ÑÐ°ÑÑÐŒÐŸÑÑÐžÐŒ ÐŸÐŽÐžÐœ ÑÐžÑÑÐœÐŸÐº (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="graphical_query_interface_to_greenstone"/>), ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð³ÑÐ°ÑÐžÑÐµÑÐºÐžÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð·Ð°Ð¿ÑÐŸÑÐ°, ÐŸÑÐœÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐœÐ° ÐŽÐžÐ°Ð³ÑÐ°ÐŒÐŒÐ°Ñ
+ ÐÐµÐœÐœÐ°, Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑÐžÐ¹ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑ ÐÑÐ»ÐµÐ²ÑÐŒÐž Ð·Ð°Ð¿ÑÐŸÑÐ°ÐŒÐž. ÐÐ°Ð¿ÐžÑÐ°ÐœÐœÑÐ¹ ÐœÐ° Java, ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑÑÑ Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸ ÐœÐ° ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÐŸÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÑ CORBA, ÐŸÐœ ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ Ðº ÐŸÑÐŽÐ°Ð»ÐµÐœÐœÐŸÐŒÑ ÑÐµÑÐ²ÐµÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone, ÐœÐ°Ð¿ÐžÑÐ°ÐœÐœÐŸÐŒÑ ÐœÐ° C++.</Text>
+<Text id="770">Ð Ð°ÑÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» Ð²ÑÐµ ÐµÑÐµ ÑÐŸÐ²ÐµÑÑÐµÐœÑÑÐ²ÑÐµÑÑÑ Ðž Ð³ÐŸÑÐŸÐ²ÐžÑÑÑ ÐŽÐ»Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ, ÑÐ°Ðº ÑÑÐŸ Ð² ÑÑÐŸÐŒ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ ÐŒÑ Ð±ÐŸÐ»ÐµÐµ ÐœÐµ ÑÑÐ°ÐœÐµÐŒ ÐµÐ³ÐŸ ÐŸÐ±ÑÑÐ¶ÐŽÐ°ÑÑ (ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÑÐŒ. Bainbridge et al., 2001).</Text>
+</Content>
+</Section>
+<Section id="conceptual_framework">
+<Title>
+<Text id="771">ÐÐŸÐœÑÐµÐ¿ÑÑÐ°Ð»ÑÐœÐ°Ñ ÑÑÑÑÐºÑÑÑÐ°</Text>
+</Title>
+<Content>
+<Figure id="generating_the_about_this_collection_page">
+<Title>
+<Text id="772">ÐÐµÐœÐµÑÐ°ÑÐžÑ ÑÑÑÐ°ÐœÐžÑÑ "about this collection"</Text>
+</Title>
+<File width="398" height="354" url="images/Dev_Fig_050.png"/>
+</Figure>
+<Text id="773">Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="generating_the_about_this_collection_page"/> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÑÑÐ°ÐœÐžÑÑ "about this collection" (ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž) ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone (ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐÑÐŸÐµÐºÑÐ° Gutenberg). Ð¡ÐŒÐŸÑÑÐžÑÐµ URL ÐœÐ°Ð²ÐµÑÑ
+Ñ. Ð¡ÑÑÐ°ÐœÐžÑÐ° ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐ° Ð² ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ CGI-Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ library, ÐºÐŸÑÐŸÑÐ°Ñ, ÐºÐ°Ðº Ð³ÐŸÐ²ÐŸÑÐžÐ»ÐŸÑÑ Ð²ÑÑÐµ,ÑÐ²Ð»ÑÐµÑÑÑ Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÐŒÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐŸÐ¹, Ð²ÐºÐ»ÑÑÐ°ÑÑÐµÐ¹ Ðž ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ Ðž ÑÐµÑÐ²ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐ²ÑÐ·Ð°ÐœÐœÑÐ¹ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ ÐœÑÐ»ÐµÐ²ÑÐŒ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»ÐŸÐŒ. ÐÑÐ³ÑÐŒÐµÐœÑÑ library - c=gberg, a=p, Ðž p=about. ÐÐœÐž ÐŒÐŸÐ³ÑÑ ÐžÐœÑÐµÑÐ¿ÑÐµÑÐžÑÐŸÐ²Ð°ÑÑÑÑ ÑÐ»ÐµÐŽÑÑÑÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ:</Text>
+<Indented>
+<Text id="774">ÐÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐÑÐŸÐµÐºÑ Gutenberg (c=gberg) ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð³ÐµÐœÐµÑÐžÑÑÐµÑ ÑÑÑÐ°ÐœÐžÑÑ (Ð°=Ñ), ÑÐ³ÐµÐœÑÐžÑÐŸÐ²Ð°ÐœÐœÐ°Ñ ÑÑÑÐ°ÐœÐžÑÐ° ÐœÐ°Ð·Ð²Ð°ÐœÐ° "about" (p=about).</Text>
+</Indented>
+<Figure id="greenstone_runtime_system">
+<Title>
+<Text id="775">Ð Ð°Ð±ÐŸÑÐ° ÑÐžÑÑÐµÐŒÑ Greenstone</Text>
+</Title>
+<File width="534" height="345" url="images/Dev_Fig_052.png"/>
+</Figure>
+<Text id="776">Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="greenstone_runtime_system"/> ÐžÐ»Ð»ÑÑÑÑÐžÑÑÐµÑ ÐŸÑÐœÐŸÐ²ÐœÑÐµ ÑÐ°ÑÑÐž ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ Greenstone. ÐÐ°Ð²ÐµÑÑ
+Ñ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ ÑÐœÐ°ÑÐ°Ð»Ð° ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·ÐžÑÑÐµÑ ÑÐ²ÐŸÐž ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑÑ, Ð·Ð°ÑÐµÐŒ Ð°ÐœÐ°Ð»ÐžÐ·ÐžÑÑÐµÑ CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÑ, ÑÑÐŸÐ±Ñ ÑÐµÑÐžÑÑ, ÐºÐ°ÐºÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð·Ð°Ð¿ÑÑÑÐžÑÑ. ÐÑÐž Ð·Ð°Ð¿ÑÑÐºÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ (ÐºÐŸÑÐŸÑÐŸÐµ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð² ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÐµÐŒ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÑ CGI Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐ²), Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ», ÑÑÐŸÐ±Ñ ÐŸÐ±ÑÐ°ÑÐžÑÑÑÑ Ðº ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐ²ÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ð³ÐµÐœÐµÑÐ°ÑÐžÐž web-ÑÑÑÐ°ÐœÐžÑÑ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑÐ° ÑÐŸÑÐŒÐ°ÑÐ° Ðž ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐºÐ°.</Text>
+<Text id="777">ÐÐ°ÐºÑÐŸÑÐ·ÑÐº, ÐºÐŸÑÐŸÑÑÐ¹ ÐŒÑ Ð²ÐžÐŽÐµÐ»ÐžÐ² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="controlling_the_greenstone_user_interface"/>, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ, ÑÑÐŸÐ±Ñ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÑÑ ÑÐžÑÑÐŸÐ²ÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÑ ÑÐžÑÑÐµÐŒÑ Greenstone Ð»Ð°ÐºÐŸÐœÐžÑÐœÑÐŒ ÑÑÐžÐ»ÐµÐŒ Ðž ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐžÐœÑÐµÑÑÐµÐ¹ÑÑ ÐœÐ° ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐ·ÑÐºÐ°Ñ
+. ÐÐ·Ð°ÐžÐŒÐŸÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐŸÐ¹ Ð³ÐµÐœÐµÑÐžÑÑÐµÑ ÑÐºÐµÐ»ÐµÑ web-ÑÑÑÐ°ÐœÐžÑ; ÐŒÐ°ÐºÑÐŸÑ Ð² GSDLHOME/macros ÐœÐ°ÑÐ°ÑÐžÐ²Ð°ÐµÑ ÐœÐ° ÑÑÐŸÑ ÑÐºÐµÐ»ÐµÑ Ð¿Ð»ÐŸÑÑ.</Text>
+<Text id="778">ÐÐ±ÑÐµÐºÑ Macro Language (ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐº) ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="greenstone_runtime_system"/> ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐµÐœ Ð·Ð° ÑÑÐµÐœÐžÐµ ÑÐ°Ð¹Ð»ÐŸÐ² Ðž ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐžÐµ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐ° Ð°ÐœÐ°Ð»ÐžÐ·Ð° ÑÑÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² Ð² Ð¿Ð°ÐŒÑÑÐž. ÐÑÐ±ÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ ÐŒÐŸÐ¶ÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ, ÑÑÐŸÐ±Ñ ÑÐ°Ð·Ð²ÐµÑÐœÑÑÑ ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÑ. ÐÐœÐŸ ÐŒÐŸÐ¶ÐµÑ ÐŽÐ°Ð¶Ðµ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐœÐŸÐ²ÑÐµ ÐŒÐ°ÐºÑÐŸÑÑ Ðž ÐŸÑÐŒÐµÐœÐžÑÑ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ, ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑ ÐŽÐžÐœÐ°ÐŒÐžÑÐµÑÐºÐŸÐµ ÑÐ°ÑÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ Ð² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž ÐŒÐ°ÐºÑÐŸÑÐŸÐ².</Text>
+<Text id="779">ÐÐœÐµÑÐœÐžÐ¹ Ð²ÐžÐŽ ÑÑÑÐ°ÐœÐžÑÑ "about this collection" (ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="generating_the_about_this_collection_page"/>) ÐžÐ·Ð²ÐµÑÑÐµÐœ ÐŽÐŸ ÐŒÐŸÐŒÐµÐœÑÐ° Ð·Ð°Ð¿ÑÑÐºÐ° Ðž Ð·Ð°ÐºÐŸÐŽÐžÑÐŸÐ²Ð°Ðœ Ð² ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ðµ about.dm. ÐÐ°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž, ÐœÐžÐ¶ÐœÐžÐµ ÐºÐŸÐ»ÐŸÐœÑÐžÑÑÐ»Ñ Ðž ÑÐŸÐœÐŸÐ²Ð°Ñ Ð·Ð°Ð»ÐžÐ²ÐºÐ° ÐŽÐ°Ð¶Ðµ ÐœÐµ ÑÐ¿ÐŸÐŒÑÐœÑÑÑ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŸÐœÐž ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÑ Ð² Ð¿Ð°ÐºÐµÑÐµ ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÑ Global. ÐÐŽÐœÐ°ÐºÐŸ, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ "about" ÑÐµÐºÑÑ (ÑÐµÐºÑÑ ÐŽÐ»Ñ ÑÑÑÐ°ÐœÐžÑÑ "Ð ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž") ÐŽÐ»Ñ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐµ ÐžÐ·Ð²ÐµÑÑÐµÐœ Ð·Ð°ÑÐ°ÐœÐµÐµ, ÐŸÐœ Ñ
+ÑÐ°ÐœÐžÑÑÑ Ð² ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ Ð±Ð°Ð·Ðµ ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð² ÑÐµÑÐµÐœÐžÐµ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ. Ð­ÑÐ° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ Ð²ÑÐ·ÑÐ²Ð°ÐµÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° Ðž Ñ
+ÑÐ°ÐœÐžÑÑÑ ÐºÐ°Ðº _collectionextra_ Ð² Ð¿Ð°ÐºÐµÑÐµ ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÑ Global. ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÑÐŸ, ÑÑÐŸ ÐžÐŒÑ ÐŒÐ°ÐºÑÐŸÑÐ° - Ð¿ÐŸ ÑÑÑÐµÑÑÐ²Ñ ÐžÐŒÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐµ ÐŽÐ»Ñ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÑÑÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐŸÐ¿ÐžÑÐ°ÐœÐœÐŸÐŒ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="configuration_file"/>. Ð§ÑÐŸÐ±Ñ ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÑÑÑÐ°ÐœÐžÑÑ, Ð±ÑÐ»Ð° ÑÐ°ÑÑÐžÑÐµÐœÐ° ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÐ° _content_ Ð² Ð¿Ð°ÐºÐµÑÐµ about (ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="part_of_the_aboutdm_macro_file"/>) . ÐÐœÐ° Ð² ÑÐ²ÐŸÑ ÐŸÑÐµÑÐµÐŽÑ Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑ _textabout _, ÐºÐŸÑÐŸÑÑÐ¹ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ Ðº _collectionextra _, ÑÐŸÐ»ÑÐºÐŸ ÑÑÐŸ ÐŽÐžÐœÐ°ÐŒÐžÑÐµÑÐºÐž Ð¿ÐŸÐŒÐµÑÐµÐœÐœÐŸÐ¹ ÑÑÐŽÐ°.</Text>
+<Text id="780">Ð¡Ð»ÐµÐŽÑÑÑÐžÐ¹ Ð²Ð°Ð¶ÐœÑÐ¹ ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑ - ÐŸÐ±ÑÐµÐºÑ Format. ÐÐ¿ÐµÑÐ°ÑÐŸÑÑ Ð·Ð°ÐŽÐ°ÐœÐžÑ ÑÐŸÑÐŒÐ°ÑÐ° Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð·Ð°ÑÑÐ°Ð³ÐžÐ²Ð°ÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐžÑ
+ ÑÐ°ÑÑÐµÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž, ÐºÐ°Ðº ÐŸÐ¿ÐžÑÐ°ÐœÐŸ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="formatting_greenstone_output"/>. ÐÐœÐž ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÐœÑ ÐŸÐ±ÑÐµÐºÑÐŸÐŒ Format (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="greenstone_runtime_system"/>). ÐÑÐœÐŸÐ²ÐœÐ°Ñ Ð·Ð°ÐŽÐ°ÑÐ° ÑÑÐŸÐ³ÐŸ ÐŸÐ±ÑÐµÐºÑÐ° ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ Ð°ÐœÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÑÑ Ðž ÐŸÑÐµÐœÐžÐ²Ð°ÑÑ ÐžÐœÑÑÑÑÐºÑÐžÐž ÑÐžÐ¿Ð° ÑÑÑÐŸÐº ÑÐŸÑÐŒÐ°ÑÐ° (ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="excerpt_from_the_demo_collection_collect"/>). ÐÐ°Ðº ÑÑÐ°Ð»ÐŸ ÑÑÐœÐŸ ÐžÐ· Ð Ð°Ð·ÐŽÐµÐ»Ð° <CrossRef target="Section" ref="formatting_greenstone_output"/>, ÐŸÐœÐž ÐŒÐŸÐ³ÑÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÑÑÑÐ»ÐºÐž ÐœÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð² ÐºÐ²Ð°ÐŽÑÐ°ÑÐœÑÑ
+ ÑÐºÐŸÐ±ÐºÐ°Ñ
+ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, [Title]), ÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÐ»Ð¶ÐµÐœÑ Ð±ÑÑÑ ÐœÐ°Ð¹ÐŽÐµÐœÑ ÑÐµÑÐ²ÐµÑÐŸÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ·Ð°ÐžÐŒÐŸÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ ÐŒÐµÐ¶ÐŽÑ ÐŸÐ±ÑÐµÐºÑÐŸÐŒ Format Ðž ÐŸÐ±ÑÐµÐºÑÐŸÐŒ Macro Language, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÑ Ð·Ð°ÐŽÐ°ÐœÐžÑ ÑÐŸÑÐŒÐ°ÑÐ° ÐŒÐŸÐ³ÑÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÐŒÐ°ÐºÑÐŸÑÑ, ÐºÐŸÑÐŸÑÑÐµ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÐ°ÑÑÐžÑÐµÐœÐžÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐºÐŸÑÐŸÑÑÐµ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÐ°ÑÑÐžÑÐµÐœÐžÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÐŒÐ°ÐºÑÐŸÑÑ Ðž ÑÐ°Ðº ÐŽÐ°Ð»ÐµÐµ.</Text>
+<Text id="781">ÐÐœÐžÐ·Ñ ÑÐžÑÑÐœÐºÐ° <CrossRef target="Figure" ref="greenstone_runtime_system"/>, ÑÐµÑÐ²ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐŸÑ
+ÐŸÐŽÐžÑ Ð¿ÑÐŸÑÐµÑÑ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž, ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°Ñ ÐŸÐ±ÑÐµÐºÑÑ Filter Ðž Source, ÑÑÐŸÐ±Ñ ÐŸÑÐ²ÐµÑÐžÑÑ ÐœÐ° Ð²Ñ
+ÐŸÐŽÑÑÐžÐµ Ð·Ð°Ð¿ÑÐŸÑÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°, Ðž ÐŸÐ±ÑÐµÐºÑ Search, ÑÑÐŸÐ±Ñ ÐŸÐ±Ð»ÐµÐ³ÑÐžÑÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ Ð·Ð°ÐŽÐ°ÑÐž. Ð ÐºÐŸÐœÐµÑÐœÐŸÐŒ ÑÑÐµÑÐµ ÐŸÐœÐž ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑ Ðº ÐžÐœÐŽÐµÐºÑÐ°ÐŒ Ðž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ Ð±Ð°Ð·Ðµ ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°Ð»ÐžÑÑ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="782">ÐÐ³ÐœÐŸÑÐžÑÑÑ Ð¿ÑÑÑÑÐµ ÑÑÑÐŸÐºÐž, ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ ÑÐŸÐŽÐµÑÐ¶ÐžÑ 15 000 ÑÑÑÐŸÐº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ. Ð¡ÐµÑÐ²ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÐŸÐ»ÑÐºÐŸ 5 000 ÑÑÑÐŸÐº (75 % ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ Ð·Ð°ÐœÐžÐŒÐ°ÑÑ ÑÐ°Ð¹Ð»Ñ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ°). Ð¡ÐµÑÐ²ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð±ÐŸÐ»ÐµÐµ ÐºÐŸÐŒÐ¿Ð°ÐºÑÐµÐœ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÑÐµÐ»ÐµÐ²Ð°ÐœÑÐœÑÐ¹ Ð¿ÐŸÐžÑÐº Ð¿ÑÐŸÑ
+ÐŸÐŽÐžÑ ÑÐµÑÐµÐ· ÐŽÐ²Ðµ Ð¿ÑÐµÐŽÐŸÑÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐžÐŸÐœÐœÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ. ÐÐ»Ñ Ð¿ÐŸÐžÑÐºÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²Ð°Ñ Ð¿ÐŸÐžÑÐºÐŸÐ²Ð°Ñ ÑÐžÑÑÐµÐŒÐ° MG, Ð° ÐŽÐ»Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð¡Ð£ÐÐ GDBM.</Text>
+<Text id="783">ÐÐ»Ñ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ ÑÐ°ÑÑÐžÑÑÐµÐŒÐŸÑÑÐž Ðž Ð³ÐžÐ±ÐºÐŸÑÑÐž Greenstone ÑÐžÑÐŸÐºÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Ð¿ÐŸÑÑÐŽÐŸÐº ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ Action, Filter, Source Ðž Search. ÐÐ»Ñ Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž, ÑÐ¿ÐµÑÐžÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐ¹ ÐœÐ° ÑÐµÐºÑÑÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÑÐŸ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐ·ÐœÐ°ÑÑ ÐœÐµÐŒÐœÐŸÐ³ÐŸ Ð±ÐŸÐ»ÑÑÐµ, ÑÑÐŸÐ±Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÑÑ ÑÐžÑÑÐµÐŒÑ. ÐÐŽÐœÐ°ÐºÐŸ, ÑÑÐŸ ÑÐ°ÐºÐ¶Ðµ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ MG Ðž GDBM ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð»ÐµÐ³ÐºÐŸ Ð·Ð°ÐŒÐµÐœÐµÐœÑ, ÐµÑÐ»Ðž Ð²ÐŸÐ·ÐœÐžÐºÐœÐµÑ Ð¿ÐŸÑÑÐµÐ±ÐœÐŸÑÑÑ. ÐÑÐŸÐŒÐµ ÑÐŸÐ³ÐŸ, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐ°Ñ Ð°ÑÑ
+ÐžÑÐµÐºÑÑÑÐ° ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ Ð±ÐŸÐ³Ð°ÑÐ°, ÑÑÐŸÐ±Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶Ð°ÑÑ Ð¿ÐŸÐ»ÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÐŒÑÐ»ÑÑÐžÐŒÐµÐŽÐžÐ°, ÑÐžÐ¿Ð° ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐŸÐŒ ÑÐµÑÐµÐ· ÑÑÑÑÐŸÐ¹ÑÑÐ²ÐŸ ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ Ð²Ð²ÐŸÐŽÐ° ÐžÐ»Ðž Ð¿ÐµÑÐµÐŽÐ°ÑÐž Ð·Ð°Ð¿ÑÐŸÑÐŸÐ² Ð² Ð²ÐžÐŽÐµ Ð³ÑÐ°ÑÐžÑÐµÑÐºÑ
+ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐ¹.</Text>
+</Content>
+</Section>
+<Section id="how_the_conceptual_framework_fits_together">
+<Title>
+<Text id="784">Ð¡ÐŸÐ²ÐŒÐµÑÑÐžÐŒÐŸÑÑÑ ÐºÐŸÐœÑÐµÐ¿ÑÑÐ°Ð»ÑÐœÐŸÐ¹ ÑÑÑÑÐºÑÑÑÑ</Text>
+</Title>
+<Content>
+<Text id="785">Ð Ð°Ð·ÐŽÐµÐ»Ñ <CrossRef target="Section" ref="collection_server"/> Ðž <CrossRef target="Section" ref="receptionist"/> ÐŸÐ±ÑÑÑÐœÑÑÑ Ð²Ð·Ð°ÐžÐŒÐŸÐŽÐµÐ¹ÑÑÐ²ÐžÐµ ÑÐµÑÐ²ÐµÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐ° Ð±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸ, ÐŸÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑÑ ÐœÐ° ÐºÐ°Ð¶ÐŽÐŸÐŒ ÐŒÐŸÐŽÑÐ»Ðµ ÑÐžÑÑÐœÐºÐ° <CrossRef target="Figure" ref="greenstone_runtime_system"/> Ðž ÐŸÐ¿ÐžÑÑÐ²Ð°Ñ, ÐºÐ°Ðº ÑÑÐŸ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ. ÐÐŸÐ»ÐµÐ·ÐœÐŸ ÑÐœÐ°ÑÐ°Ð»Ð° ÑÐ°Ð·ÐŸÐ±ÑÐ°ÑÑÑÑ ÐœÐ° Ð¿ÑÐžÐŒÐµÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ, Ð²Ð·Ð°ÐžÐŒÐŸÐŽÐµÐ¹ÑÑÐ²ÑÑÑÐµÐ³ÐŸ Ñ Greenstone, Ðž ÐŸÐ¿ÐžÑÑÐ²Ð°ÑÑ ÑÐŸ, ÑÑÐŸ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ. ÐÑÐµÐŽÐ¿ÐŸÐ»Ð°Ð³Ð°ÐµÑÑÑ, ÑÑÐŸ Ðº ÐœÐ°ÑÑÐŸÑÑÐµÐŒÑ ÐŒÐŸÐŒÐµÐœÑÑ Ð²ÑÐµ ÐŸÐ±ÑÐµÐºÑÑ Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÑ. ÐÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÑ - Ð·Ð°Ð¿ÑÑÐ°ÐœÐœÐ°Ñ Ð¿ÑÐŸÑÐµÐŽÑÑÐ°, Ðº ÐºÐŸÑÐŸÑÐŸÐ¹ ÐŒÑ Ð²ÐµÑÐœÐµÐŒÑÑ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="initialisation"/>.</Text>
+<Subsection id="performing_a_search">
+<Title>
+<Text id="786">ÐÐŸÐžÑÐº</Text>
+</Title>
+<Content>
+<Figure id="searching_gutenberg_for_darcy">
+<Title>
+<Text id="787">ÐÐŸÐžÑÐº Ð¿ÐŸ Ð·Ð°Ð¿ÑÐŸÑÑ Darcy Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Gutenberg</Text>
+</Title>
+<File width="396" height="353" url="images/Dev_Fig_054.png"/>
+</Figure>
+<Text id="788">ÐÐŸÐ³ÐŽÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð²Ð²ÐŸÐŽÐžÑ Ð·Ð°Ð¿ÑÐŸÑ, ÐœÐ°Ð¶ÐžÐŒÐ°Ñ ÐºÐœÐŸÐ¿ÐºÑ Begin search ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ Ð¿ÐŸÐžÑÐºÐ°, Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑÑÑ ÐœÐŸÐ²ÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Greenstone, ÐºÐŸÑÐŸÑÐŸÐµ Ð·Ð°ÐºÐ°ÐœÑÐžÐ²Ð°ÑÑÑ, Ð³ÐµÐœÐµÑÐžÑÑÐµÑ ÐœÐŸÐ²ÑÑ HTML-ÑÑÑÐ°ÐœÐžÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐº. ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/> Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ Ð¿ÐŸÐžÑÐºÐ° Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Project Gutenberg ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐŸÐ²ÐŸÐ³ÐŸ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÑ Darcy. Ð Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ Ð¿ÐµÑÐ²ÐŸÐœÐ°ÑÐ°Ð»ÑÐœÐŸÐ¹ HTML -ÑÑÑÐ°ÐœÐžÑÑ ÑÐºÑÑÑÐ° ÐžÐœÑÑÑÑÐºÑÐžÑ Ð¿ÐŸÐžÑÐºÐ° a=q. ÐÐŸÐ³ÐŽÐ° ÐºÐœÐŸÐ¿ÐºÐ° Ð¿ÐŸÐžÑÐºÐ° ÐœÐ°Ð¶Ð°ÑÐ°, ÑÑÐ° ÐžÐœÑÑÑÑÐºÑÐžÑ Ð°ÐºÑÐžÐ²ÐžÐ·ÐžÑÑÐµÑÑÑ Ðž ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ ÐœÐŸÐ²ÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ - queryaction. ÐÐ°Ð¿ÑÑÐº queryaction ÐœÐ°Ð¿ÑÐ°Ð²Ð»ÑÐµÑ Ð·Ð°Ð¿ÑÐŸÑ Ðº ÐŸÐ±ÑÐµÐºÑÑ Filter/Ð€ÐžÐ»ÑÑÑ (c=gberg), ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÐŒÑÐ¹ ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐµÑÐµÐ· Ð¿ÑÐŸÑÐŸÐºÐŸÐ».</Text>
+<Text id="789">Ð€ÐžÐ»ÑÑÑÑ - Ð²Ð°Ð¶ÐœÐ°Ñ ÐŸÑÐœÐŸÐ²ÐœÐ°Ñ ÑÑÐœÐºÑÐžÑ ÑÐµÑÐ²ÐµÑÐŸÐ² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐžÑÐ¿ÐŸÑÐŸÐ±Ð»ÐµÐœÐœÑÐµ ÐŽÐ»Ñ ÐŽÐµÐ¹ÑÑÐ²ÐžÐ¹ Ð¿ÐŸÐžÑÐºÐ° Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°, ÐŸÐœÐž ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÑÑ ÑÐ¿ÐŸÑÐŸÐ±Ñ Ð²ÑÐ±ÐŸÑÐ° Ð¿ÐŸÐŽÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ð° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐžÐ· ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, queryaction ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ Ð·Ð°Ð¿ÑÐŸÑ ÑÐžÐ»ÑÑÑÐ°:</Text>
+<BulletList>
+<Bullet>
+<Text id="790">ÑÑÑÐ°ÐœÐ°Ð²ÐºÐ° ÑÐžÐ¿Ð° ÑÐžÐ»ÑÑÑÐ° Ð·Ð°Ð¿ÑÐŸÑÐ° QueryFilter (Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Section" ref="collection_server"/> ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÑÐžÐ¿Ñ ÑÐžÐ»ÑÑÑÐŸÐ²);</Text>
+</Bullet>
+<Bullet>
+<Text id="791">ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐžÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐŸÐº Ð¿ÐŸÐžÑÐºÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð² ÑÐžÐ»ÑÑÑÐµ Ð·Ð°Ð¿ÑÐŸÑÐ°;</Text>
+</Bullet>
+<Bullet>
+<Text id="792">Ð²ÑÐ·ÐŸÐ² ÑÑÐœÐºÑÐžÐž filterQ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐœÑÐ»ÐµÐ²ÐŸÐ¹ Ð¿ÑÐŸÑÐŸÐºÐŸÐ».</Text>
+</Bullet>
+</BulletList>
+<Text id="793">ÐÐ°Ð¿ÑÐŸÑÑ Ðº Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ñ ÑÐžÐœÑ
+ÑÐŸÐœÐœÑ. Ð ÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ ÑÑÑÐµÐºÑÐžÐ²ÐœÐŸ Ð±Ð»ÐŸÐºÐžÑÑÐµÑÑÑ, Ð¿ÐŸÐºÐ° Ð·Ð°Ð¿ÑÐŸÑ ÑÐžÐ»ÑÑÑÐ° ÐœÐµ Ð±ÑÐŽÐµÑ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°Ðœ ÑÐµÑÐ²ÐµÑÐŸÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð²ÑÐµ ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÐŽÐ°ÐœÐœÑÐµ Ð±ÑÐŽÑÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÑ.</Text>
+<Text id="794">ÐÐŸÐ³ÐŽÐ° Ð·Ð°Ð¿ÑÐŸÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° ÑÐžÐ¿Ð° QueryFilter ÑÐŽÐµÐ»Ð°Ðœ, ÐŸÐ±ÑÐµÐºÑ Filter (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="greenstone_runtime_system"/>) ÐŽÐµÐºÐŸÐŽÐžÑÑÐµÑ Ð²Ð°ÑÐžÐ°ÐœÑÑ Ðž Ð·Ð°Ð¿ÑÐ°ÑÐžÐ²Ð°ÐµÑ ÐŸÐ±ÑÐµÐºÑ Search, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ MG ÐŽÐ»Ñ ÑÐ°ÐºÑÐžÑÐµÑÐºÐŸÐ³ÐŸ Ð¿ÐŸÐžÑÐºÐ°. Ð ÐŸÐ»Ñ ÐŸÐ±ÑÐµÐºÑÐ° Search ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ ÐŸÐœ ÐŽÐŸÐ»Ð¶ÐµÐœ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÑÑ Ð°Ð±ÑÑÑÐ°ÐºÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐžÑÐº, ÐœÐµÐ·Ð°Ð²ÐžÑÐžÐŒÐŸ ÐŸÑ ÐŸÑÐœÐŸÐ²ÐœÐŸÐ³ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐ³ÐŸ ÑÑÐµÐŽÑÑÐ²Ð° Ð¿ÐŸÐžÑÐºÐ°. Ð€ÐŸÑÐŒÐ°Ñ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÑÑ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÑ, ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐµÐŽÐ¿ÐžÑÑÐ²Ð°ÐµÑ Ð°Ð±ÑÑÑÐ°ÐºÑÐžÑ, ÑÑÐµÐ±ÑÑ ÐŸÑ ÐŸÐ±ÑÐµÐºÑÐ° Search ÑÑÐ°ÐœÑÐ»ÐžÑÐŸÐ²Ð°ÑÑ ÐŽÐ°ÐœÐœÑÐµ, ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÑÑÐµÐŽÑÑÐ²ÐŸÐŒ Ð¿ÐŸÐžÑÐºÐ° Ð² ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ ÑÐŸÑÐŒÑ.</Text>
+<Text id="795">ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÑ Ð¿ÐŸÐžÑÐºÐ° Ð²ÐŸÐ·Ð²ÑÐ°ÑÐµÐœÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÑ, ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÐžÐŒ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµÐŒ ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² ÐŽÐ»Ñ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŸÐ±ÑÐµÐºÑ Format Ðž ÐÐ°ÐºÑÐŸÑÐ·ÑÐº. ÐÐ°Ðº Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/>, ÐŸÐœ Ð²ÑÐ³Ð»ÑÐŽÐžÑ ÑÐ»ÐµÐŽÑÑÑÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ: ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐ¹ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº Greenstone, ÐœÐžÐ¶ÐœÐžÐ¹ ÐºÐŸÐ»ÐŸÐœÑÐžÑÑÐ», ÐœÐ°Ð²ÐžÐ³Ð°ÑÐžÐŸÐœÐœÐ°Ñ ÐŸÐ±Ð»Ð°ÑÑÑ Ðž ÑÐŸÐœ; Ð¿ÐŸÐ²ÑÐŸÑÐµÐœÐžÐµ ÐŸÑÐœÐŸÐ²ÐœÐŸÐ¹ ÑÐ°ÑÑÐž ÑÑÑÐ°ÐœÐžÑÑ Ð·Ð°Ð¿ÑÐŸÑÐ° ÑÐŸÐ»ÑÐºÐŸ ÐœÐžÐ¶Ðµ ÐœÐ°Ð²ÐžÐ³Ð°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐŸÐ±Ð»Ð°ÑÑÐž; ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ ÐºÐœÐžÐ¶ÐœÐŸÐ³ÐŸ Ð·ÐœÐ°ÑÐºÐ°, Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° Ðž Ð°Ð²ÑÐŸÑÐ° ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐœÐ°Ð¹ÐŽÐµÐœÐœÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸ. Ð€ÐŸÑÐŒÐ°Ñ Ð¿ÐŸÑÐ»ÐµÐŽÐœÐµÐ¹ ÑÐ°ÑÑÐž ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑÑÑ ÐžÐœÑÑÑÑÐºÑÐžÐµÐ¹ format SearchVList Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐµÐ¶ÐŽÐµ ÑÐµÐŒ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº Ðž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð°Ð²ÑÐŸÑÐ° Ð±ÑÐŽÑÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÑ, ÐŸÐœÐž ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐœÐ°Ð¹ÐŽÐµÐœÑ ÑÐµÑÐ²ÐµÑÐŸÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¢ÑÑ ÑÑÐµÐ±ÑÐµÑÑÑ Ð·Ð°Ð¿ÑÐŸÑ Ðº Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ñ, ÐœÐ° ÑÐµÐ¹ ÑÐ°Ð· ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ BrowseFilter.</Text>
+</Content>
+</Subsection>
+<Subsection id="retrieving_a_document">
+<Title>
+<Text id="796">Retrieving a document</Text>
+</Title>
+<Content>
+<Text id="797">ÐÐŸÑÐ»Ðµ Ð²ÑÑÐµÑÐ¿ÐŸÐŒÑÐœÑÑÐŸÐ³ÐŸ Ð·Ð°Ð¿ÑÐŸÑÐ° ÐŽÐ»Ñ Darcy, ÑÐ°ÑÑÐŒÐŸÑÑÐžÐŒ ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÐµÐŒÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ. Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="the_golf_course_mystery"/> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ ÑÐµÐ»ÑÐºÐ° Ð¿ÐŸ ÐžÐºÐŸÐœÐºÐµ ÐŸÐºÐŸÐ»ÐŸ The Golf Course Mystery ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/>.</Text>
+<Figure id="the_golf_course_mystery">
+<Title>
+<Text id="798"><i>The Golf Course Mystery</i></Text>
+</Title>
+<File width="393" height="349" url="images/Dev_Fig_056.png"/>
+</Figure>
+<Text id="799">ÐÑÑ
+ÐŸÐŽÐœÑÐ¹ ÑÐµÐºÑÑ ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Gutenberg Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐŸÐŽÐžÐœ ÐŽÐ»ÐžÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐºÐœÐžÐ³Ðž. ÐÐŸ Ð²ÑÐµÐŒÑ ÐºÐŸÐŒÐ¿ÐŸÐœÐŸÐ²ÐºÐž, ÑÑÐŸÑ ÑÐ°Ð¹Ð» ÑÐ°Ð·Ð±ÐžÑ ÐœÐ° ÐŸÑÐŽÐµÐ»ÑÐœÑÐµ ÑÑÑÐ°ÐœÐžÑÑ, ÐºÐ°Ð¶ÐŽÐ°Ñ Ð¿ÐŸ 200 ÑÑÑÐŸÐº ÐžÐ»Ðž ÐŸÐºÐŸÐ»ÐŸ ÑÑÐŸÐ³ÐŸ, Ðž ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐ°Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐ° Ð² ÐžÐœÐŽÐµÐºÑÐ°Ñ
+ Ðž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ Ð±Ð°Ð·Ðµ ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð Ð²ÐµÑÑ
+ÐœÐµÐ¹ ÑÐ°ÑÑÐž ÑÐžÑÑÐœÐºÐ° <CrossRef target="Figure" ref="the_golf_course_mystery"/> ÑÐºÐ°Ð·Ð°ÐœÐŸ, ÑÑÐŸ ÑÑÐ° ÐºÐœÐžÐ³Ð° ÑÐŸÐŽÐµÑÐ¶ÐžÑ 104 ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÐµÐŒÑÑ
+ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐŸÐŒ ÑÑÑÐ°ÐœÐžÑÑ, Ðž ÐœÐžÐ¶Ðµ - ÐœÐ°ÑÐ°Ð»ÐŸ ÑÑÑÐ°ÐœÐžÑÑ ÐŸÐŽÐžÐœ: ÐºÑÐŸ Ð²Ð²ÐµÐ» ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº, Ð°Ð²ÑÐŸÑ, ÐœÐ°ÑÐ°Ð»ÐŸ ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÑ (ÑÑÐŸ ÑÐ°ÑÑÑ ÑÐ°Ð±Ð»ÐžÑÐœÐŸÐ¹ ÑÐŸÑÐŒÑ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ° Gutenberg, ÐŸÐœÐ° ÐœÐµ Ð±ÑÐ»Ð° ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐ° Greenstone). Ð Ð²ÐµÑÑ
+ÐœÐµÐ¹ Ð»ÐµÐ²ÐŸÐ¹ ÑÐ°ÑÑÐž ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ ÐºÐœÐŸÐ¿ÐºÐž, ÐºÐŸÑÐŸÑÑÐµ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑ Ð²ÐœÐµÑÐœÐžÐŒ Ð²ÐžÐŽÐŸÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°: ÑÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐœÐ° ÑÑÑÐ°ÐœÐžÑÐ° ÐžÐ»Ðž ÑÐµÐ»ÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ; Ð¿ÐŸÐŽÑÐ²ÐµÑÐºÐ° ÑÐµÑÐŒÐžÐœÐ° Ð·Ð°Ð¿ÑÐŸÑÐ° Ð²ÐºÐ». ÐžÐ»Ðž Ð²ÑÐºÐ».; ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸ Ð»Ðž ÐºÐœÐžÐ³Ð° ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° Ð² ÐµÐµ ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÐŸÐŒ ÐŸÐºÐœÐµ; ÐŸÑÐŽÐµÐ»ÐµÐœÐžÐµ Ð¿ÐŸÐžÑÐºÐŸÐ²ÐŸÐ¹ ÑÐ°ÑÑÐž ÐŸÑ ÐŸÐºÐœÐ° Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°. Ð Ð²ÐµÑÑ
+ÐœÐµÐ¹ Ð¿ÑÐ°Ð²ÐŸÐ¹ ÑÐ°ÑÑÐž - ÐœÐ°Ð²ÐžÐ³Ð°ÑÐžÐŸÐœÐœÐ°Ñ Ð¿ÐŸÐŒÐŸÑÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÑÑÐŒÐŸÐ¹ ÐŽÐŸÑÑÑÐ¿ Ðº Ð»ÑÐ±ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ Ð² ÐºÐœÐžÐ³Ðµ: Ð¿ÑÐŸÑÑÐŸ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ ÐœÐŸÐŒÐµÑ ÑÑÑÐ°ÐœÐžÑÑ Ðž ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐºÐœÐŸÐ¿ÐºÑ "go to page" (Ð¿ÐµÑÐµÐ¹ÑÐž Ðº ÑÑÑÐ°ÐœÐžÑÐµ). ÐÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÐ»Ñ Ð¿ÐµÑÐµÑ
+ÐŸÐŽÐ° Ð¿ÐŸ ÑÑÑÐ°ÐœÐžÑÐ°ÐŒ ÑÑÑÐµÐ»ÐºÐž next/previous pages (ÑÐ»ÐµÐŽÑÑÑÐ°Ñ/Ð¿ÑÐµÐŽÑÐŽÑÑÐ°Ñ ÑÑÑÐ°ÐœÐžÑÐ°).</Text>
+<Text id="800">ÐÐµÐ¹ÑÑÐ²ÐžÐµ Ð¿ÐŸÐžÑÐºÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² documentaction ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐŸÐ¹ a=d Ðž ÐžÐŒÐµÐµÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÑ
+ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ². ÐÐ°ÐžÐ±ÐŸÐ»ÐµÐµ Ð²Ð°Ð¶ÐœÑÐ¹ - ÐŽÐ¿ÐŸÐžÑÐº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°: ÑÑÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ ÑÐµÑÐµÐ· Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÑ d. ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="the_golf_course_mystery"/> ÑÑÐŸ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐŸ ÐºÐ°Ðº d=HASH51e598821ed6cbbdf0942b. 1 ÐœÐ°Ð¹ÑÐž Ð¿ÐµÑÐ²ÑÑ ÑÑÑÐ°ÐœÐžÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ñ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐŒ HASH51e598821ed6cbbdf0942b, Ð·ÐœÐ°Ñ Ð±ÐŸÐ»ÐµÐµ ÐŽÑÑÐ¶ÐµÑÑÐ²ÐµÐœÑÐ¹ ÑÐµÑÐŒÐžÐœ The Golf Course Mystery. ÐÑÑÐ°Ð»ÑÐœÑÐµ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ: Ð²ÐºÐ». ÐžÐ»Ðž Ð²ÑÐºÐ». Ð¿ÐŸÐŽÑÐ²ÐµÑÐºÑ ÑÐµÑÐŒÐžÐœÐ° Ð·Ð°Ð¿ÑÐŸÑÐ° (hi), ÐŸÑÐŸÐ±ÑÐ°Ð·ÐžÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÑÐŸÐŒ, ÐºÐ°ÐºÐ°Ñ ÑÑÑÐ°ÐœÐžÑÐ° ÐºÐœÐžÐ³Ðž ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° (gt). Ð­ÑÐž Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž ÐŽÐµÐ¹ÑÑÐ²ÐžÐ¹, Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÐµÐŒÑÑ
+ ÐºÐœÐŸÐ¿ÐºÐ°ÐŒÐž ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="the_golf_course_mystery"/>), ÐŸÐ¿ÐžÑÐ°ÐœÐœÐŸÐ¹ Ð²ÑÑÐµ. ÐÐœÐ°ÑÐµÐœÐžÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ, ÐµÑÐ»Ðž Ð»ÑÐ±Ð°Ñ ÐžÐ· ÑÑÐžÑ
+ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÑ
+ ÐŸÐ¿ÑÑÐµÐœÐ°.</Text>
+<Text id="801">ÐÐµÐ¹ÑÑÐ²ÐžÐµ ÑÐ»ÐµÐŽÑÐµÑ Ð·Ð° Ð¿ÑÐŸÑÐµÐŽÑÑÐŸÐ¹ queryaction: ÐŸÑÐµÐœÐºÐ° CGI -Ð°ÑÐ³ÑÐŒÐµÐœÑÐ°, ÐŽÐŸÑÑÑÐ¿ Ðº ÑÐµÑÐ²ÐµÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» Ðž ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ ÐŽÐ»Ñ Ð³ÐµÐœÐµÑÐ°ÑÐžÐž web-ÑÑÑÐ°ÐœÐžÑÑ. ÐÐ°ÑÐžÐ°ÐœÑÑ, ÐºÐ°ÑÐ°ÑÑÐžÐµÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÐŽÐµÐºÐŸÐŽÐžÑÐŸÐ²Ð°ÐœÑ CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐŒ Ðž ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÑ Ð² ÐŸÐ±ÑÐµÐºÑÐµ ÐŽÐ»Ñ ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÐµÐ¹ ÑÐ°Ð±ÐŸÑÑ. Ð§ÑÐŸÐ±Ñ ÐŸÑÑÑÐºÐ°ÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐœÐ° ÑÐµÑÐ²ÐµÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒ ÑÐŸÐ»ÑÐºÐŸ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÑÑÐŸÐ±Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ð·Ð°Ð¿ÑÐŸÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° Ðº get_document (). ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÑÐµÐºÑÑ ÐœÐ°Ð¹ÐŽÐµÐœ, ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð±ÑÑÑ Ð¿ÑÐŸÐžÐ·Ð²ÐµÐŽÐµÐœÐŸ Ð·ÐœÐ°ÑÐžÑÐµÐ»ÑÐœÐŸÐµ ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ. ÐÐ»Ñ ÑÑÐŸÐ³ÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐŽÐŸÑÑÑÐ¿Ð° Ðº documentaction ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑ Ð°ÑÐ³ÑÐŒÐµÐœÑ Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐŸÐ±ÑÐµÐºÑ Format Ðž ÐÐ°ÐºÑÐŸÑÐ·ÑÐº.</Text>
+</Content>
+</Subsection>
+<Subsection id="browsing_a_hierarchical_classifier">
+<Title>
+<Text id="802">ÐÑÐŸÑÐŒÐŸÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°</Text>
+</Title>
+<Content>
+<Text id="803">ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/> Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ Ð¿ÑÐžÐŒÐµÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°, Ð³ÐŽÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð²ÑÐ±ÑÐ°Ð» Titles Ð-Z (ÐÐ°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž A-Z) Ðž ÐŸÐ±ÑÐ°ÑÐžÐ»ÑÑ Ðº Ð³ÐžÐ¿ÐµÑÑÐ²ÑÐ·Ðž ÐŽÐ»Ñ ÑÐžÐŒÐ²ÐŸÐ»Ð° Ð. Ð­ÑÐŸ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ Ð±Ð»Ð°Ð³ÐŸÐŽÐ°ÑÑ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ documentaction, ÐºÐŸÑÐŸÑÐŸÐµ Ð·Ð°ÐŽÐ°ÐµÑÑÑ CGI -Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐŒ a=d. ÐÐŽÐœÐ°ÐºÐŸ, ÐŽÐŸ Ð¿ÐŸÐŽÐºÐ»ÑÑÐµÐœÐžÑ Ð¿ÐµÑÐµÐŒÐµÐœÐœÐŸÐ¹ d ÑÑÐŸÐžÑ ÐŸÐ³ÐŸÐ²ÐŸÑÐžÑÑÑÑ, ÑÑÐŸ Ð² ÐŽÐ°ÐœÐœÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐŸÐœÐ° ÐœÐµ Ð±ÑÐ»Ð° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐ°. ÐÐŒÐµÑÑÐŸ ÑÑÐŸÐ³ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ð»ÑÑ ÑÐ·ÐµÐ» Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐŽÐŸÑÑÑÐ¿ÐœÐŸÐ¹ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐžÐµÑÐ°ÑÑ
+ÐžÐž ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž, ÑÑÐŸÐ±Ñ ÐŸÑÐŸÐ±ÑÐ°Ð·ÐžÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÑ cl. Ð ÐŽÐ°ÐœÐœÐŸÐŒ Ð¿ÑÐžÐŒÐµÑÐµ ÐŸÐœÐ° Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž, ÑÐ³ÑÑÐ¿Ð¿ÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐŒ Ð. Ð­ÑÐŸÑ ÑÐ¿ÐžÑÐŸÐº Ð±ÑÐ» ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°Ðœ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÐºÐŸÐŒÐ¿Ð°ÐœÐŸÐ²ÐºÐž Ðž ÑÐŸÑ
+ÑÐ°ÐœÐµÐœ Ð² ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ Ð±Ð°Ð·Ðµ ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Figure id="browsing_titles_in_the_gutenberg_collection">
+<Title>
+<Text id="804">ÐÑÐŸÑÐŒÐŸÑÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Gutenberg</Text>
+</Title>
+<File width="394" height="351" url="images/Dev_Fig_058.png"/>
+</Figure>
+<Text id="805">ÐÐ°Ð¿ÐžÑÐž, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑÑ ÑÐ·Ð»Ñ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° Ð² Ð±Ð°Ð·Ðµ ÐŽÐ°ÐœÐœÑÑ
+, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ Ð¿ÑÐµÑÐžÐºÑ CL, ÑÐŸÐ¿ÑÐŸÐ²ÐŸÐ¶ÐŽÐ°ÐµÐŒÑÐ¹ ÑÐžÑÐ»Ð°ÐŒÐž, ÐŸÑÐŽÐµÐ»ÐµÐœÐœÑÐŒÐž Ð¿ÐµÑÐžÐŸÐŽÐ°ÐŒÐž (.), ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑÐžÐŒÐž ÐžÑ
+ ÐœÐ°Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÐµ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ Ð²Ð»ÐŸÐ¶ÐµÐœÐœÐŸÐ¹ ÑÑÑÑÐºÑÑÑÑ. ÐÐ³ÐœÐŸÑÐžÑÑÑ ÐºÐœÐŸÐ¿ÐºÑ Ð¿ÐŸÐžÑÐºÐ° (Ð»ÐµÐ²ÑÐ¹ ÐºÑÐ°Ð¹ Ð² ÐœÐ°Ð²ÐžÐ³Ð°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐŸÐ±Ð»Ð°ÑÑÐž), ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ Ð¿ÑÐŸÐœÑÐŒÐµÑÐŸÐ²Ð°ÐœÑ Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸ Ð² Ð¿ÐŸÑÑÐŽÐºÐµ Ð²ÐŸÐ·ÑÐ°ÑÑÐ°ÐœÐžÑ, ÑÐ»ÐµÐ²Ð° ÐœÐ°Ð¿ÑÐ°Ð²ÐŸ, ÐœÐ°ÑÐžÐœÐ°Ñ Ñ 1. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, ÑÐ·ÐµÐ» ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ ÐŽÐ»Ñ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ² Ð² ÐœÐ°ÑÐµÐŒ Ð¿ÑÐžÐŒÐµÑÐµ - CL1, Ð° ÑÐ°Ð·ÑÑÐºÐžÐ²Ð°ÐµÐŒÐ°Ñ ÑÑÑÐ°ÐœÐžÑÐ° ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐ° ÑÑÑÐ°ÐœÐŸÐ²ÐºÐŸÐ¹ cl=CLl.ll. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ²ÐžÐŽÐµÑÑ ÑÑÐŸ Ð² ÑÑÑÐŸÐºÐµ URL ÐœÐ°Ð²ÐµÑÑ
+Ñ ÑÐžÑÑÐœÐºÐ° <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/>.</Text>
+<Text id="806">ÐÐ»Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž Ð·Ð°Ð¿ÑÐŸÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° cl ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŸÐ±ÑÐµÐºÑ Filter, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÑÑÑÐºÐžÐ²Ð°ÐµÑ ÑÐ·ÐµÐ» Ð¿ÐŸ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ñ. Ð²ÐŸÐ·Ð²ÑÐ°ÑÐµÐœÐœÑÑ
+ ÐŽÐ°ÐœÐœÑÑ
+, ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÐžÐµ Ð·Ð°Ð¿ÑÐŸÑÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° ÑÐŽÐµÐ»Ð°ÐœÑ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐŸÑÑÑÐºÐ°ÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð ÐŽÐ°ÐœÐœÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐœÐ°Ð¹ÐŽÐµÐœÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž ÐºÐœÐžÐ³. ÐÐŽÐœÐ°ÐºÐŸ, ÐµÑÐ»Ðž ÑÐ·ÐµÐ» Ð±ÑÐ» Ð²ÐœÑÑÑÐµÐœÐœÐžÐ¹, ÐŽÐŸÑÐµÑÐœÐžÐµ Ð·Ð°Ð¿ÐžÑÐž ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ - ÑÐ°ÐŒÐŸÑÑÐŸÑÑÐµÐ»ÑÐœÑÐµ ÑÐ·Ð»Ñ, ÑÐŸ Ð±ÑÐ»Ðž Ð±Ñ ÐœÐ°Ð¹ÐŽÐµÐœÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž ÐŽÐŸÑÐµÑÐœÐžÑ
+ Ð²ÐµÑÑÐžÐœ. Ð¡ ÑÐŸÑÐºÐž Ð·ÑÐµÐœÐžÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÑÑÐŸ ÑÐŸÐ¶Ðµ ÑÐ°ÐŒÐŸÐµ Ðž ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÐœÐŸ ÑÐµÐŒ Ð¶Ðµ ÑÐ°ÐŒÑÐŒ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒÐŸÐŒ.</Text>
+<Text id="807">ÐÐ°ÐºÐŸÐœÐµÑ, Ð²ÑÑ ÐœÐ°Ð¹ÐŽÐµÐœÐœÐ°Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÑÐ²ÑÐ·Ð°ÐœÐ° Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐºÐ° Ðž ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° ÐœÐ° web-ÑÑÑÐ°ÐœÐžÑÐµ, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÐŸÐ¹ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="browsing_titles_in_the_gutenberg_collection"/>.</Text>
+</Content>
+</Subsection>
+<Subsection id="generating_the_home_page">
+<Title>
+<Text id="808">Generating the home page</Text>
+</Title>
+<Content>
+<Figure id="greenstone_home_page">
+<Title>
+<Text id="809">ÐÐµÐœÐµÑÐ°ÑÐžÑ ÐŽÐŸÐŒÐ°ÑÐœÐµÐ¹ ÑÑÑÐ°ÐœÐžÑÑ</Text>
+</Title>
+<File width="397" height="393" url="images/Dev_Fig_060.png"/>
+</Figure>
+<Text id="810">Ð ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð¿ÐŸÑÐ»ÐµÐŽÐœÐµÐ³ÐŸ Ð¿ÑÐžÐŒÐµÑÐ° ÐŒÑ ÑÐ°ÑÑÐŒÐŸÑÑÐžÐŒ ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐŽÐŸÐŒÐ°ÑÐœÐµÐ¹ ÑÑÑÐ°ÐœÐžÑÑ Greenstone . Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="greenstone_home_page"/> ÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÑÐµÑ ÐŽÐŸÐŒÐ°ÑÐœÑÑ ÑÑÑÐ°ÐœÐžÑÑ Greenstone, ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐœÑÑ ÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑÐŒÐž Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ. ÐÐµ URL, ÐºÐŸÑÐŸÑÑÐ¹ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐŽÐµÑÑ ÐœÐ°Ð²ÐµÑÑ
+Ñ ÑÐºÑÐ°ÐœÐ°, Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð°ÑÐ³ÑÐŒÐµÐœÑÑ Ð°=Ñ np=home. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, Ð¿ÐŸÐŽÐŸÐ±ÐœÐŸ ÑÑÑÐ°ÐœÐžÑÐµ "about this collection" (ÐŸÐ± ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž), ÐŸÐœÐ° Ð±ÑÐ»Ð° ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐ°ÑÐ°^ÐµÐ°ÑÐ¹'ÐŸÐž (Ð°=Ñ), ÐœÐŸ ÐœÐ° ÑÐµÐ¹ ÑÐ°Ð· Ð¿ÑÐžÐŒÐµÐœÑÐ»ÐŸÑÑ home (p=home). ÐÐŸÑÑÐŸÐŒÑ ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐº ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ Ðº ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ home.dm. Ð ÐŽÐ°ÐœÐœÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐœÐµÑ ÐœÐžÐºÐ°ÐºÐŸÐ¹ ÐœÐ°Ð±ÐŸÐŽÐœÐŸÑÑÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ (Ñ Ð¿ÐµÑÐµÐŒÐµÐœÐœÐŸÐ¹ Ñ).</Text>
+<Text id="811">The purpose of the home page is to show what collections are available. Clicking on an icon takes the user to the âabout this collectionâ page for that collection. The menu of collections is dynamically generated every time the page is loaded, based on the collections that are in the file system at that time. When a new one comes online, it automatically appears on the home page when that page is reloaded (provided the collection is stipulated to be âpublicâ).</Text>
+<Text id="812">To do this the receptionist uses the protocol (of course). As part of appraising the CGI arguments, <i>pageaction</i> is programmed to detect the special case when <i>p=home</i>. Then, the action uses the protocol call <i>get_collection_list()</i> to establish the current set of online collections. For each of these it calls <i>get_collectinfo()</i> to obtain information about it. This information includes whether the collection is publicly available, what the URL is for the collection's icon (if any), and the collection's full name. This information is used to generate an appropriate entry for the collection on the home page.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="source_code">
+<Title>
+<Text id="813">Source code</Text>
+</Title>
+<Content>
+<Table id="standalone_programs_included_in_greenstone">
+<Title>
+<Text id="814">Standalone programs included in Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="815"><i>setpasswd/</i></Text>
+</th>
+<th width="397">
+<Text id="816">Password support for Windows.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="817"><i>getpw/</i></Text>
+</th>
+<th width="397">
+<Text id="818">Password support for Unix.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="819"><i>txt2db/</i></Text>
+</th>
+<th width="397">
+<Text id="820">Convert an XML-like ASCII text format to Gnu's database format.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="821"><i>db2txt/</i></Text>
+</th>
+<th width="397">
+<Text id="822">Convert the Gnu database format to an XML-like ASCII text format.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="823"><i>phind/</i></Text>
+</th>
+<th width="397">
+<Text id="824">Hierarchical phrase browsing tool.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="825"><i>hashfile/</i></Text>
+</th>
+<th width="397">
+<Text id="826">Compute unique document ID based on content of file.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="827"><i>mgpp/</i></Text>
+</th>
+<th width="397">
+<Text id="828">Rewritten and updated version of Managing Gigabytes package in C++.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="829"><i>w32server/</i></Text>
+</th>
+<th width="397">
+<Text id="830">Local library server for Windows.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="831"><i>checkis/</i></Text>
+</th>
+<th width="397">
+<Text id="832">Specific support for installing Greenstone under Windows.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="833">The source code for the runtime system resides in <i>GSDLHOME/src</i>. It occupies two subdirectories, <i>recpt</i> for the receptionist's code and <i>colservr</i> for the collection server's. Greenstone runs on Windows systems right down to Windows 3.1, and unfortunately this imposes an eight-character limit on file and directory names. This explains why cryptic abbreviations like <i>recpt</i> and <i>colservr</i> are used. The remaining subdirectories include standalone utilities, mostly in support of the building process. They are listed in Table <CrossRef target="Table" ref="standalone_programs_included_in_greenstone"/>.</Text>
+<Text id="834">Another directory, <i>GSDLHOME/lib</i>, includes low-level objects that are used by both receptionist and collection server. This code is described in Section <CrossRef target="Section" ref="common_greenstone_types"/>.</Text>
+<Text id="835">Greenstone ÑÐžÑÐŸÐºÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Standard Template Library (STL)/ Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ ÑÐ°Ð±Ð»ÐŸÐœÐŸÐ² Ð¡ ++,- ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÑ Silicon Graphics (www.sgi.com), ÐºÐŸÑÐŸÑÐ°Ñ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐŒ ÐŒÐœÐŸÐ³ÐžÑ
+ Ð»ÐµÑ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐºÐž Ðž ÑÐ°Ð·Ð²ÐžÑÐžÑ. ÐÐŸÐŽÐŸÐ±ÐœÐŸ Ð²ÑÐµÐŒ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÐŒ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐŸÐœÐ° ÑÑÐµÐ±ÑÐµÑ ÐœÐµÐºÐŸÑÐŸÑÐŸÐ³ÐŸ Ð²ÑÐµÐŒÐµÐœÐž ÐœÐ° ÐžÐ·ÑÑÐµÐœÐžÐµ. ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ Ð ÐŽÐ°ÐµÑ ÐºÑÐ°ÑÐºÐžÐ¹ ÐŸÐ±Ð·ÐŸÑ ÐºÐ»ÑÑÐµÐ²ÑÑ
+ ÑÐ°ÑÑÐµÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð²ÑÑÐŽÑ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ Greenstone. ÐÐ»Ñ Ð±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐ»ÐœÐŸÐ³ÐŸ ÐŸÐ·ÐœÐ°ÐºÐŸÐŒÐ»ÐµÐœÐžÑ ÐŸÐ±ÑÐ°ÑÐ°Ð¹ÑÐµÑÑ Ðº ÐŸÑÐžÑÐžÐ°Ð»ÑÐœÐŸÐŒÑ STL ÑÐ¿ÑÐ°Ð²ÐŸÑÐœÐŸÐŒÑ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ñ, ÐŽÐŸÑÑÑÐ¿ÐœÐŸÐŒÑ ÐœÐ° ÑÐ°Ð¹ÑÐµ www.sgi.com, ÐžÐ»Ðž Ðº ÐŸÐŽÐœÐŸÐŒÑ ÐžÐ· ÐŒÐœÐŸÐ³ÐžÑ
+ ÑÑÐµÐ±ÐœÐžÐºÐŸÐ² STL, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ Josuttis (1999).</Text>
+</Content>
+</Section>
+<Section id="common_greenstone_types">
+<Title>
+<Text id="836">ÐÐ±ÑÐžÐµ ÑÐžÐ¿Ñ Greenstone</Text>
+</Title>
+<Content>
+<Text id="837">ÐÐ±ÑÐµÐºÑÑ, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐµ Ð² GSDLHOME/lib, ÑÐ²Ð»ÑÑÑÑÑ ÐŸÐ±ÑÐµÐºÑÐ°ÐŒÐž Greenstone ÐœÐžÐ¶ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ, ÐŸÑÐœÐŸÐ²ÑÐ²Ð°ÑÑÑ ÐœÐ° Ð²ÐµÑÑÐžÐœÐµ STL, ÐºÐŸÑÐŸÑÑÐµ Ð²Ñ
+ÐŸÐŽÑÑ Ð² ÐžÑÑ
+ÐŸÐŽÐœÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ. Ð¡ÐœÐ°ÑÐ°Ð»Ð° ÐŒÑ ÐŽÐµÑÐ°Ð»ÑÐœÐŸ ÑÐ°ÑÑÐŒÐŸÑÑÐžÐŒ Ð±ÑÐµÐºÑ text_t, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÑÐµÐºÑÑÐ° Ð² ÑÐŸÑÐŒÐ°ÑÐµ Unicode. ÐÐŸÑÐ»Ðµ ÑÐµÐ³ÐŸ ÐŒÑ ÑÐŒÐŸÐ¶ÐµÐŒ ÐºÑÐ°ÑÐºÐŸ ÐžÐ·Ð»ÐŸÐ¶ÐžÑÑ ÑÐµÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð° Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž.</Text>
+<Subsection id="the_text_t_object">
+<Title>
+<Text id="838">ÐÐ±ÑÐµÐºÑ text_t</Text>
+</Title>
+<Content>
+<Text id="839">Greenstone ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ñ ÐŒÐœÐŸÐ³ÐžÐŒÐž ÑÐ·ÑÐºÐ°ÐŒÐž Ðž ÐŽÐ»Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ðž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°. ÐÐ»Ñ ÑÑÐŸÐ³ÐŸ ÐžÑÑ
+ÐŸÐŽÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð¿ÐŸÐ²ÑÐµÐŒÐµÑÑÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Unicode. ÐÑÐœÐŸÐ²ÐœÑÐŒ ÐŸÐ±ÑÐµÐºÑÐŸÐŒ, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐœÐžÐŒÐ°ÐµÑ ÑÑÑÐŸÐºÑ Unicode ÑÐ²Ð»ÑÐµÑÑÑ <i>text_t</i>.</Text>
+<Figure id="the_text_t_api" class="withLineNumber">
+<Title>
+<Text id="840"><i>text_t</i> API (Ð² ÑÐŸÐºÑÐ°ÑÐµÐœÑ)</Text>
+</Title>
+<CodeLine>typedef vector&lt;unsigned short&gt; usvector;</CodeLine>
+<CodeLine/>
+<CodeLine>class text_t {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>usvector text;</CodeLine>
+<CodeLine>unsigned short encoding; // 0 = unicode, 1 = other</CodeLine>
+<CodeLine/>
+<CodeLine>public:</CodeLine>
+<CodeLine>   // constructors</CodeLine>
+<CodeLine>   text_t ();</CodeLine>
+<CodeLine>   text_t (int i);</CodeLine>
+<CodeLine>   text_t (char *s); // assumed to be a normal c string</CodeLine>
+<CodeLine/>
+<CodeLine>   void setencoding (unsigned short theencoding);</CodeLine>
+<CodeLine>   unsigned short getencoding ();</CodeLine>
+<CodeLine/>
+<CodeLine>   // STL container support</CodeLine>
+<CodeLine>   iterator begin ();</CodeLine>
+<CodeLine>   iterator end ();</CodeLine>
+<CodeLine/>
+<CodeLine>   void erase(iterator pos);</CodeLine>
+<CodeLine>   void push_back(unsigned short c);</CodeLine>
+<CodeLine>   void pop_back();</CodeLine>
+<CodeLine/>
+<CodeLine>   void reserve (size_type n);</CodeLine>
+<CodeLine/>
+<CodeLine>   bool empty () const {return text.empty();}</CodeLine>
+<CodeLine>   size_type size() const {return text.size();}</CodeLine>
+<CodeLine/>
+<CodeLine>   // added functionality</CodeLine>
+<CodeLine>   void clear ();</CodeLine>
+<CodeLine>   void append (const text_t &amp;t);</CodeLine>
+<CodeLine/>
+<CodeLine>   // support for integers</CodeLine>
+<CodeLine>   void appendint (int i);</CodeLine>
+<CodeLine>   void setint (int i);</CodeLine>
+<CodeLine>   int getint () const;</CodeLine>
+<CodeLine/>
+<CodeLine>   // support for arrays of chars</CodeLine>
+<CodeLine>   void appendcarr (char *s, size_type len);</CodeLine>
+<CodeLine>   void setcarr (char *s, size_type len);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="841">Unicode ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐŽÐ²Ð° Ð±Ð°Ð¹ÑÐ° ÐŽÐ»Ñ Ñ
+ÑÐ°ÐœÐµÐœÐžÑ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐžÐŒÐ²ÐŸÐ»Ð°. ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="the_text_t_api"/> Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ Ð³Ð»Ð°Ð²ÐœÑÐµ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž text_t Application Program Interface/ ÐÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÑÐžÐºÐ»Ð°ÐŽÐœÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ (API). ÐÐœ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐžÑÑ ÐŽÐ²ÑÑ
+Ð±Ð°Ð¹ÑÐŸÐ²ÐŸÐµ ÑÑÐµÐ±ÐŸÐ²Ð°ÐœÐžÐµ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð¡ ++ Ð²ÑÑÑÐŸÐµÐœÐœÑÐ¹ ÑÐžÐ¿ short, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœ ÐºÐ°Ðº ÐŽÐ²ÑÑ
+Ð±Ð°Ð¹ÑÐŸÐ²ÐŸÐµ ÑÐµÐ»ÐŸÐµ ÑÐžÑÐ»ÐŸ. ÐŠÐµÐœÑÑÐ°Ð»ÑÐœÑÐ¹ ÑÐžÐ¿ ÐŽÐ°ÐœÐœÑÑ
+ ÐŸÐ±ÑÐµÐºÑÐ° text_t - ÑÑÐŸ ÐŽÐžÐœÐ°ÐŒÐžÑÐµÑÐºÐžÐ¹ ÐŒÐ°ÑÑÐžÐ², ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ short, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ STL ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ vector&lt;unsigned short&gt; Ðž Ð¿ÐŸÐ»ÑÑÐµÐœÐœÐŸÐµ ÑÐŸÐºÑÐ°ÑÐµÐœÐœÐŸÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ usvector.</Text>
+<Text id="842">Ð€ÑÐœÐºÑÐžÐž ÐºÐŸÐœÑÑÑÑÐºÑÐŸÑÐ° (ÑÑÑÐŸÐºÐž 10-12) ÑÐ²ÐœÐŸ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑ ÑÑÐž ÑÐŸÑÐŒÑ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž: ÐºÐŸÐœÑÑÑÑÐºÑÐžÑ Ð±ÐµÐ· Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ², ÐºÐŸÑÐŸÑÐ°Ñ Ð³ÐµÐœÐµÑÐžÑÑÐµÑ Ð¿ÑÑÑÑÑ ÑÑÑÐŸÐºÑ Unicode; ÐºÐŸÐœÑÑÑÑÐºÑÐžÑ Ñ ÑÐµÐ»ÐŸÑÐžÑÐ»ÐµÐœÐœÑÐŒ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐŒ, ÐºÐŸÑÐŸÑÐ°Ñ Ð³ÐµÐœÐµÑÐžÑÑÐµÑ Ð²ÐµÑÑÐžÑ ÑÐµÐºÑÑÐ° Unicode ÑÐžÑÐ»ÐŸÐ²ÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐœÐŸÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑ; ÐºÐŸÐœÑÑÑÑÐºÑÐžÑ Ñ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐŒ char*, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ Ð°ÑÐ³ÑÐŒÐµÐœÑ ÐºÐ°Ðº ÑÑÑÐŸÐºÑ Ð¡ ++ Ñ ÐœÑÐ»ÐµÐ²ÑÐŒ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐŒ Ð² ÐºÐŸÐœÑÐµ Ðž Ð³ÐµÐœÐµÑÐžÑÑÐµÑ Ð²ÐµÑÑÐžÑ Unicode.</Text>
+<Text id="843">ÐÐŸÑÐ»Ðµ ÑÑÐŸÐ³ÐŸ, Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² (ÑÑÑÐŸÐºÐž 17-28), Ð¿ÐµÑÐµÑ
+ÐŸÐŽÑÑ ÐœÐ° ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐœÐžÐµ STL Ð²ÐµÐºÑÐŸÑÐœÐŸÐ³ÐŸ ÐºÐŸÐœÑÐµÐ¹ÐœÐµÑÐ°: beginQ, endQ,push_back(), emptyQ Ðž Ñ.ÐŽ. ÐÐŽÐµÑÑ ÐžÐŒÐµÐµÑÑÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° ÐŸÑÐžÑÑÐºÐž Ðž ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÑ ÑÑÑÐŸÐºÐž, Ð° ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ ÑÐµÐ»ÐŸÑÐžÑÐ»ÐµÐœÐœÐŸÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑ Ð² ÑÑÑÐŸÐºÑ ÑÐµÐºÑÑÐ° Unicode, Ðž Ð²ÐŸÐ·Ð²ÑÐ°ÑÐµÐœÐžÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐ³ÐŸ ÑÐµÐ»ÐŸÑÐžÑÐ»ÐµÐœÐœÐŸÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÑÐµÐºÑÑÐ°, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑ ÐœÐŸÐŒÐµÑ.</Text>
+<Figure id="overloaded_operators_to_text_t" class="withLineNumber">
+<Title>
+<Text id="844">ÐÐµÑÐµÐ³ÑÑÐ¶ÐµÐœÐœÑÐµ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÑ <i>text_t</i></Text>
+</Title>
+<CodeLine>class text_t {</CodeLine>
+<CodeLine>   // ...</CodeLine>
+<CodeLine>   public:</CodeLine>
+<CodeLine>   text_t &amp;operator=(const text_t &amp;x);</CodeLine>
+<CodeLine>   text_t &amp;operator+= (const text_t &amp;t);</CodeLine>
+<CodeLine>   reference operator[](size_type n);</CodeLine>
+<CodeLine/>
+<CodeLine>   text_t &amp;operator=(int i);</CodeLine>
+<CodeLine>   text_t &amp;operator+= (int i);^ \\</CodeLine>
+<CodeLine>   text_t &amp;operator= (char *s);</CodeLine>
+<CodeLine>   text_t &amp;operator+= (char *s);</CodeLine>
+<CodeLine/>
+<CodeLine>   friend inline bool operator!=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator==(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&lt; (const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&gt; (const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&gt;=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   friend inline bool operator&lt;=(const text_t&amp; x, const text_t&amp; y);</CodeLine>
+<CodeLine>   // ...</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="845">Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ Ð¿ÐµÑÐµÐ³ÑÑÐ¶ÐµÐœÐœÑÑ
+ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÐŸÐ² , ÐºÐŸÑÐŸÑÑÐµ ÐœÐµ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="the_text_t_api"/>. ÐÑÐŸÐ±ÐŸ Ð·ÐœÐ°ÑÐžÐŒÑÐµ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="overloaded_operators_to_text_t"/>. Ð¡ÑÑÐŸÐºÐ° 4 Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŸÐŽÐœÐŸÐ³ÐŸ ÐŸÐ±ÑÐµÐºÑÐ° text_t ÐŽÑÑÐ³ÐŸÐŒÑ, Ð° ÑÑÑÐŸÐºÐ° 5 Ð¿ÐµÑÐµÐ³ÑÑÐ¶Ð°ÐµÑ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑ+ = , ÑÑÐŸÐ±Ñ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÑÑ Ð±ÐŸÐ»ÐµÐµ ÐµÑÑÐµÑÑÐ²ÐµÐœÐœÑÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÑ ÐŸÐŽÐœÐŸÐ³ÐŸ ÐŸÐ±ÑÐµÐºÑÐ° text_t Ð² ÐºÐŸÐœÐµÑ ÐŽÑÑÐ³ÐŸÐ³ÐŸ. Ð¢Ð°ÐºÐ¶Ðµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ ÑÐµÑÐµÐ· ÑÑÑÐŸÐºÑ 6 ÐŸÐ±ÑÐ°ÑÐžÑÑÑÑ Ðº ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐŸÐŒÑ ÑÐžÐŒÐ²ÐŸÐ»Ñ Unicode (Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÐŸÐŒÑ ÐºÐ°Ðº short), ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð·ÐœÐ°Ðº ÐŒÐ°ÑÑÐžÐ²Ð° []. ÐÐ°Ð»ÐµÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐœÐ°Ð·ÐœÐ°ÑÐžÑÑ Ðž ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ Ð² ÐºÐŸÐœÐµÑ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÑ, Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐµ ÐŽÐ»Ñ ÑÑÑÐŸÐº C++ Ðž ÑÐµÐ»ÑÑ
+ ÑÐžÑÐµÐ». Ð¡ÑÑÐŸÐºÐž 12-18 Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑÑ ÐÑÐ»ÐµÐ²Ñ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÑ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÑÑÐ°Ð²ÐœÐžÑÑ ÐŽÐ²Ð° ÐŸÐ±ÑÐµÐºÑÐ° text_t: ÑÐ°Ð²ÐœÐŸ, ÐœÐµ ÑÐ°Ð²ÐœÐŸ, Ð¿ÑÐµÐŽÑÐµÑÑÐ²ÑÐµÑ Ð² Ð°Ð»ÑÐ°Ð²ÐžÑÐœÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ Ðž ÑÐ°Ðº ÐŽÐ°Ð»ÐµÐµ.</Text>
+<Text id="846">Ð€ÑÐœÐºÑÐžÑ-ÑÐ»ÐµÐœ, ÐºÐŸÑÐŸÑÐ°Ñ Ð±ÐµÑÐµÑ Ð°ÑÐ³ÑÐŒÐµÐœÑ const Ð²ÐŒÐµÑÑÐŸ ÐœÐµ-const, ÑÐ°ÐºÐ¶Ðµ ÐžÐŒÐµÐµÑÑÑ (ÐœÐŸ ÐœÐ° ÑÐžÑÑÐœÐºÐµ ÐœÐµ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐ°). Ð¢Ð°ÐºÐŸÐµ Ð¿ÐŸÐ²ÑÐŸÑÐµÐœÐžÐµ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸ ÐŽÐ»Ñ ÐŸÐ±ÑÐµÐºÑÐŸÐ² C++, ÐŽÐµÐ»Ð°Ñ API Ð±ÐŸÐ»ÐµÐµ Ð²ÐµÑÐŸÐŒÑÐŒ, ÐœÐŸ ÐœÐµ Ð±ÐŸÐ»ÐµÐµ ÐºÐŸÐœÑÐµÐ¿ÑÑÐ°Ð»ÑÐœÑÐŒ. Ð ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸÑÑÐž, ÐŒÐœÐŸÐ³ÐžÐµ ÐžÐ· ÑÑÐžÑ
+ ÑÑÐœÐºÑÐžÐ¹ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÐºÐ°Ðº ÐŸÑÐŽÐµÐ»ÑÐœÑÐµ ÐŽÐµÐ¹ÑÑÐ²ÑÑÑÐžÐµ ÐžÐœÑÑÑÑÐºÑÐžÐž. ÐÐ»Ñ Ð±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÐ³ÐŸ ÐžÐ·ÑÑÐµÐœÐžÑ ÐŸÐ±ÑÐ°ÑÐžÑÐµÑÑ Ðº ÐžÑÑ
+ÐŸÐŽÐœÐŸÐŒÑ ÑÐ°Ð¹Ð»Ñ GSDLHOME/lib/text_t.h.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_greenstone_library_code">
+<Title>
+<Text id="847">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Title>
+<Content>
+<Text id="848">Ð€Ð°Ð¹Ð»Ñ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° Ð² GSDLHOME/lib Ð²ÐºÐ»ÑÑÐ°ÑÑ ÑÐŒÐµÑÑ ÑÑÐœÐºÑÐžÐ¹ Ðž ÐŸÐ±ÑÐµÐºÑÐŸÐ², ÑÑÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ Greenstone. ÐÐ»Ñ Ð±ÐŸÐ»ÑÑÐµÐ¹ ÑÑÑÐµÐºÑÐžÐ²ÐœÐŸÑÑÐž ÐŸÑÐœÐŸÑÐµÐœÐžÑ, ÑÑÐœÐºÑÐžÐž Ðž ÑÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÑ ÐŸÐ±ÑÑÐ²Ð»ÐµÐœÑ ÐºÐ°Ðº inline. ÐÐ»Ñ Ð±ÐŸÐ»ÑÑÐµÐ¹ ÑÐ°ÑÑÐž Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÑÑÐž Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑÑ Ð² ÐºÐŸÐ¿ÐžÐž ÑÐ°Ð¹Ð»Ð° Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° .ÑÑÑ.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="100">
+<Text id="849"><b>cfgread.h</b></Text>
+</th>
+<th width="450">
+<Text id="850">Ð€ÑÐœÐºÑÐžÐž ÐŽÐ»Ñ ÑÑÐµÐœÐžÑ Ðž Ð·Ð°Ð¿ÐžÑÐž ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, read_cfg_line () ÐºÐ°Ðº Ð°ÑÐ³ÑÐŒÐµÐœÑ ÐŽÐ»Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ Ð±ÐµÑÐµÑ Ð²Ñ
+ÐŸÐŽÐœÐŸÐ¹ Ð¿ÐŸÑÐŸÐº Ðž text_tarray (ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÐœÐœÑÐ¹ ÐŽÐ»Ñ vector&lt;text_t&gt;), ÑÑÐŸÐ±Ñ Ð·Ð°Ð¿ÐŸÐ»ÐœÐžÑÑ ÐŽÐ°ÐœÐœÑÐŒÐž ÐŽÐ»Ñ ÑÑÐµÐœÐžÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="851"><b>display.h</b></Text>
+</th>
+<th width="450">
+<Text id="852">Ð¡Ð»ÐŸÐ¶ÐœÑÐ¹ ÐŸÐ±ÑÐµÐºÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐŸÐŒ ÐŽÐ»Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž, Ñ
+ÑÐ°ÐœÐµÐœÐžÑ Ðž ÑÐ°ÑÑÐžÑÐµÐœÐžÑ ÐŒÐ°ÐºÑÐŸÑÐ°, Ð¿Ð»ÑÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž ÑÐžÐ¿ÐŸÐ². ÐÐŸÐŽÑÐŸÐ±ÐœÐŸÑÑÐž Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐœÐ°Ð¹ÑÐž Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="receptionist"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="853"><b>fileutil.h</b></Text>
+</th>
+<th width="450">
+<Text id="854">Ð€ÑÐœÐºÑÐžÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž ÐœÐµÐ·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ²ÑÑ
+ ÑÑÐžÐ»ÐžÑ Ð² ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÐµ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, fllename_cat () Ð±ÐµÑÐµÑ ÐŽÐŸ ÑÐµÑÑÐž text_t Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² Ðž Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ textjt, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐŒ ÑÐ²ÑÐ·ÑÐ²Ð°ÐœÐžÑ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ², ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐ¹ ÐŽÐžÑÐµÐºÑÐžÐ²ÐœÑÐ¹ ÑÐ°Ð·ÐŽÐµÐ»ÐžÑÐµÐ»Ñ ÐŽÐ»Ñ ÑÐµÐºÑÑÐµÐ¹ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="855"><b>gsdlconf.h</b></Text>
+</th>
+<th width="450">
+<Text id="856">Ð¡ÐžÑÑÐµÐŒÐœÐŸ-ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐžÐµ ÑÑÐœÐºÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ ÐŸÑÐ²ÐµÑÐ°ÑÑ ÐœÐ° Ð²ÐŸÐ¿ÑÐŸÑÑ ÑÐžÐ¿Ð°: ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÐ°Ñ ÑÐžÑÑÐµÐŒÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ ÐŽÐ»Ñ ÑÑÐ°ÐœÑÐ»ÑÑÐžÐž, ÐŽÐŸÐ»Ð¶ÐœÐ° ÐŸÐ±ÑÐ°ÑÐžÑÑÑÑ Ðº strings.h ÑÐ°Ðº Ð¶Ðµ, ÐºÐ°Ðº string.ht ÐÐµÐ¹ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸ Ð»Ðž Ð²ÑÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŽÐ»Ñ Ð·Ð°ÐºÑÑÑÐžÑ ÑÐ°Ð¹Ð»Ð°, Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐ³ÐŸ?</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="857"><b>gsdltimes.h</b></Text>
+</th>
+<th width="450">
+<Text id="858">Ð€ÑÐœÐºÑÐžÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž ÐŽÐ°Ñ Ðž Ð²ÑÐµÐŒÐµÐœÐž. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, time2text () Ð±ÐµÑÐµÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐœÐŸÐµ Ð²ÑÐµÐŒÑ, Ð²ÑÑÐ°Ð¶ÐµÐœÐœÐŸÐµ Ð² ÐºÐŸÐ»ÐžÑÐµÑÑÐ²Ðµ ÑÐµÐºÑÐœÐŽ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐŸÑÐ»Ðž Ñ 1 ÑÐœÐ²Ð°ÑÑ 1970, ÐºÐŸÐœÐ²ÐµÑÑÐžÑÑÐµÑ ÐžÑ
+ Ð² ÑÐŸÑÐŒÑ YYYY/MM/DD (ÐÐÐÐ/ÐÐ/ÐÐ), hh:mm:ss (ÑÑ:ÐŒÐŒ:ÑÑ) Ðž Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ ÐºÐ°Ðº ÑÐžÐ¿ textjt.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="859"><b>gsdltools.h</b></Text>
+</th>
+<th width="450">
+<Text id="860">Ð Ð°Ð·Ð»ÐžÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ Greenstone: ÐŸÐ±ÑÑÑÐœÑÐµÑ, ÐµÑÐ»Ðž HttleEndian ÐžÐ»Ðž bigEndian; Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ, ÐŽÐŸÑÑÑÐ¿ÐµÐœ Ð»Ðž Perl; Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÑ ÑÐžÑÑÐµÐŒÐœÑÑ ÐºÐŸÐŒÐ°ÐœÐŽÑ (Ñ ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÐŒÐž ÐœÐµÐœÑÐ¶ÐœÑÐŒÐž ÑÐ²ÐŸÐ¹ÑÑÐ²Ð°ÐŒÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ) Ðž ÐžÐ·Ð±Ð°Ð²Ð»ÑÐµÑ ÐŸÑ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÑ
+ ÐŒÐ°ÐºÑÐŸÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² Ð² text_t ÑÑÑÐŸÐºÐµ. </Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="861"><b>gsdlunicode.h</b></Text>
+</th>
+<th width="450">
+<Text id="862">Ð ÑÐŽ ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÑ
+ ÐŸÐ±ÑÐµÐºÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÑ Unicode text_t ÑÑÑÐŸÐºÐž ÑÐµÑÐµÐ· Ð¿ÐŸÑÐŸÐºÐž Ð®, ÑÐžÐ¿Ð° Unicode Ðº UTF-8 Ðž ÐœÐ°ÐŸÐ±ÐŸÑÐŸÑ; ÑÐŽÐ°Ð»ÐµÐœÐžÐµ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ² ÐœÑÐ»ÐµÐ²ÐŸÐ¹ ÑÐžÑÐžÐœÑ. ÐÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° ÑÐ°Ñ-ÑÐ°Ð¹Ð»ÐŸÐ² ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐ° ÑÐµÑÐµÐ· ÐŸÐ±ÑÐµÐºÑ mapconvert Ñ ÑÐ°ÑÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑÐŒÐž, Ð·Ð°Ð³ÑÑÐ¶ÐµÐœÐœÑÐŒÐž ÐžÐ· GSDLHOME/mappings.</Text>
+</th>
+</tr>
+<tr>
+<th width="100">
+<Text id="863"><b>text_t.h</b></Text>
+</th>
+<th width="450">
+<Text id="864">ÐÑÐµÐ¶ÐŽÐµ Ð²ÑÐµÐ³ÐŸ ÑÑÐŸ ÐŸÐ±ÑÐµÐºÑ ÑÐµÐºÑÑÐ° Unicode, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐ¹ Ð²ÑÑÐµ. ÐÐŸ ÑÐ°ÐºÐ¶Ðµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ ÐŽÐ²Ð° ÐºÐ»Ð°ÑÑÐ° ÐŽÐ»Ñ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ Ð¿ÐŸÑÐŸÐºÐŸÐ²: inconvertclass Ðž outconvertclass. Ð­ÑÐŸ - Ð±Ð°Ð·ÐŸÐ²ÑÐµ ÐºÐ»Ð°ÑÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ Ð² gsdlunicode.h.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="collection_server">
+<Title>
+<Text id="865">Collection server</Text>
+</Title>
+<Content>
+<Text id="866">Ð¢ÐµÐ¿ÐµÑÑ ÐŽÐµÑÐ°Ð»ÑÐœÐŸ ÐŸÐ±ÑÑÑÐœÐžÐŒ Ð²ÑÐµ ÐŸÐ±ÑÐµÐºÑÑ Ð² ÐºÐŸÐœÑÐµÐ¿ÑÑÐ°Ð»ÑÐœÐŸÐ¹ ÑÑÑÑÐºÑÑÑÐµ ÑÐžÑÑÐœÐºÐ° <CrossRef target="Figure" ref="greenstone_runtime_system"/>. ÐÑ ÐœÐ°ÑÐœÐµÐŒ Ñ ÐœÐžÐ·Ð° ÐŽÐžÐ°Ð³ÑÐ°ÐŒÐŒÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐ°ÐºÐ¶Ðµ ÐŸÑÐœÐŸÐ²ÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ, Ðž Ñ Search (ÐÐŸÐžÑÐº), Source (ÐÑÑÐŸÑÐœÐžÐº), Ð ÐšÐµÐ³(Ð€ÐžÐ»ÑÑ) Ðž Ð¿ÑÐŸÐŽÐŸÐ»Ð¶ÐžÐŒ ÐœÐ°Ñ Ð¿ÑÑÑ ÑÐµÑÐµÐ· ÑÑÐŸÐ²ÐµÐœÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° Ðº ÑÐµÐœÑÑÐ°Ð»ÑÐœÑÐŒ ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑÐ°ÐŒ Ð² ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐµ: Actions (ÐÐµÐ¹ÑÑÐ²ÐžÑ), Format (Ð€ÐŸÑÐŒÐ°Ñ) Ðž Macro Language (ÐÐ°ÐºÑÐŸÑÐ·ÑÐº). ÐÐ°ÑÐµÐŒ ÐŒÑ ÑÐŸÑÑÐµÐŽÐŸÑÐŸÑÐžÐŒÑÑ ÐœÐ° ÐŸÐ±ÑÐµÐºÑÐœÐŸÐ¹ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž, ÑÐ°Ðº ÐºÐ°Ðº ÑÑÐŸ Ð±ÑÐŽÐµÑ Ð¿ÑÐŸÑÐµ Ð¿ÐŸÐœÑÑÑ, ÐµÑÐ»Ðž ÑÐ¶Ðµ ÐžÐ·Ð²ÐµÑÑÐœÐ° ÑÐŸÐ»Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐŸÐ±ÑÐµÐºÑÐŸÐ².</Text>
+<Text id="867">ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÐºÐ»Ð°ÑÑÐŸÐ², ÑÐµÐœÑÑÐ°Ð»ÑÐœÑÑ
+ Ð² ÐºÐŸÐœÑÐµÐ¿ÑÑÐ°Ð»ÑÐœÐŸÐ¹ ÑÑÑÑÐºÑÑÑÐµ, Ð²ÑÑÐ°Ð¶ÐµÐœÐŸ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ Ð²ÐžÑÑÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ, ÑÑÐŸÐ±Ñ Ð¿ÐŸÐŒÐŸÑÑ ÑÐ°ÑÑÐžÑÑÐµÐŒÐŸÑÑÐž. ÐÑÐž Ð²ÐžÑÑÑÐ°Ð»ÑÐœÐŸÐŒ ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÐž ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐµ ÐŸÐ±ÑÐµÐºÑÑ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÐµÑÐµÐŽÐ°ÑÑ Ð¿ÐŸ ÐºÑÑÐ³Ñ, ÐºÐ°Ðº ÐžÑ
+ Ð±Ð°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ, ÐœÐŸ ÐºÐŸÐ³ÐŽÐ° Ð²ÑÐ·Ð²Ð°ÐœÐ° ÑÑÐœÐºÑÐžÑ-ÑÐ»ÐµÐœ, ÐµÐµ Ð²ÐµÑÑÐžÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐ° Ð² Ð¿ÑÐžÐ·Ð²Ð°ÐœÐœÐŸÐŒ ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐŒ ÐŸÐ±ÑÐµÐºÑÐµ. ÐÐ°ÑÐ°ÐœÑÐžÑÑÑ, ÑÑÐŸ ÐžÑÑ
+ÐŸÐŽÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Ð±Ð°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ Ð¿ÐŸÐ²ÑÑÐŽÑ, ÐºÑÐŸÐŒÐµ ÑÐŸÑÐºÐž ÐŸÐ±ÑÐµÐºÑÐ° ÐºÐŸÐœÑÑÑÑÐºÑÐžÐž, ÑÑÐŸ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ ÑÐ°Ð·Ð»ÐžÑÐœÐŸÐµ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ - ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ ÐœÐ° ÐŸÑÐœÐŸÐ²Ðµ ÑÐ°ÐŽÐžÐºÐ°Ð»ÑÐœÐŸ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐµÑ
+ÐœÐŸÐ»ÐŸÐ³ÐžÐ¹ - ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð»ÐµÐ³ÐºÐŸ ÑÐ°Ð·ÐŒÐµÑÐµÐœÐŸ ÐœÐ° ÐŒÐµÑÑÐµ.</Text>
+<Text id="868">ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð¿ÑÐµÐŽÐ¿ÐŸÐ»ÐŸÐ¶ÐžÐŒ, ÑÑÐŸ Ð±Ð°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ Ð¿ÐŸ ÐžÐŒÐµÐœÐž BaseCalc ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ ÐŸÑÐœÐŸÐ²ÐœÑÑ Ð°ÑÐžÑÐŒÐµÑÐžÐºÑ: ÑÐ»ÐŸÐ¶ÐµÐœÐžÐµ, Ð²ÑÑÐžÑÐ°ÐœÐžÐµ, ÑÐŒÐœÐŸÐ¶ÐµÐœÐžÐµ Ðž ÐŽÐµÐ»ÐµÐœÐžÐµ. ÐÑÐ»Ðž Ð²ÑÐµ ÐµÐ³ÐŸ ÑÑÐœÐºÑÐžÐž ÐŸÐ±ÑÑÐ²Ð»ÐµÐœÑ Ð²ÐžÑÑÑÐ°Ð»ÑÐœÑÐŒÐž, Ð° Ð°ÑÐ³ÑÐŒÐµÐœÑÑ Ðž Ð²ÐŸÐ·Ð²ÑÐ°ÑÐœÑÐµ ÑÐžÐ¿Ñ Ð²ÑÐµ ÐŸÐ±ÑÑÐ²Ð»ÐµÐœÑ ÐºÐ°Ðº ÑÑÑÐŸÐºÐž, ÐŒÑ ÐŒÐŸÐ¶ÐµÐŒ Ð»ÐµÐ³ÐºÐŸ ÐŸÑÑÑÐµÑÑÐ²ÐžÑÑ ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÐµ Ð²ÐµÑÑÐžÐž ÐŸÐ±ÑÐµÐºÑÐ°. ÐÐŽÐžÐœ ÐžÐ· ÐœÐžÑ
+, ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÐ¹ FixedPrecisionCalc, ÐŒÐŸÐ³ Ð±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐµ ÑÑÐœÐºÑÐžÐž Ð¡, ÑÑÐŸÐ±Ñ ÑÐŸÐ²ÐµÑÑÐ°ÑÑ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÑ ÐŒÐµÐ¶ÐŽÑ ÑÑÑÐŸÐºÐ°ÐŒÐž Ðž ÑÐµÐ»ÑÐŒÐž ÑÐžÑÐ»Ð°ÐŒÐž Ðž ÐŸÐ±ÑÐ°ÑÐœÐŸ, ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑ Ð²ÑÑÐžÑÐ»ÐµÐœÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐµ Ð°ÑÐžÑÐŒÐµÑÐžÑÐµÑÐºÐžÐµ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÑ: +, -, *, Ðž /. ÐÑÑÐ³ÐŸÐ¹, ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÐ¹ InfinitePrecisionCalc, ÐŒÐŸÐ³ Ð±Ñ ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑ Ðº ÑÑÑÐŸÐºÐŸÐ²ÑÐŒ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ°ÐŒ Ðž ÑÐžÐŒÐ²ÐŸÐ»Ð°ÐŒ ÐŸÐŽÐœÐŸÐ²ÑÐµÐŒÐµÐœÐœÐŸ, ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑ Ð°ÑÐžÑÐŒÐµÑÐžÑÐµÑÐºÐžÐµ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž Ñ Ð±ÐµÑÐºÐŸÐœÐµÑÐœÐŸÐ¹ ÑÐŸÑÐœÐŸÑÑÑÑ. ÐÐ°Ð¿ÐžÑÐ°ÐœÐœÐ°Ñ Ð³Ð»Ð°Ð²ÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ BaseCalc Ð¿ÐŸÐ²ÑÑÐŽÑ, Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÐµÐµ ÑÐ°Ð±ÐŸÑÑ ÐŒÐŸÐ³ÑÑ ÑÐµÐ³ÑÐ»ÐžÑÐŸÐ²Ð°ÑÑÑÑ Ð¿ÐµÑÐµÐºÐ»ÑÑÐµÐœÐžÐµÐŒ ÐŒÐµÐ¶ÐŽÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐœÐŸÐ¹ ÑÐŸÑÐœÐŸÑÑÑÑ Ðž Ð±ÐµÑÐºÐŸÐœÐµÑÐœÐŸÐ¹ ÑÐŸÑÐœÐŸÑÑÑÑ, ÑÐµÐŽÐ°ÐºÑÐžÑÑÑ ÑÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐœÑ ÑÑÑÐŸÐºÑ: Ð¿ÑÐœÐºÑ, Ð³ÐŽÐµ ÑÐŸÐ·ÐŽÐ°Ðœ ÐŸÐ±ÑÐµÐºÑ - ÐºÐ°Ð»ÑÐºÑÐ»ÑÑÐŸÑ.</Text>
+<Subsection id="the_search_object">
+<Title>
+<Text id="869">ÐÐ±ÑÐµÐºÑ Search</Text>
+</Title>
+<Content>
+<Figure id="search_base_class_api">
+<Title>
+<Text id="870">Search Ð±Ð°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ API</Text>
+</Title>
+<CodeLine>class searchclass {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   searchclass ();</CodeLine>
+<CodeLine>   virtual ~searchclass ();</CodeLine>
+<CodeLine>   // the index directory must be set before any searching</CodeLine>
+<CodeLine>   // is done</CodeLine>
+<CodeLine>   virtual void setcollectdir (const text_t &amp;thecollectdir);</CodeLine>
+<CodeLine>   // the search results are returned in queryresults</CodeLine>
+<CodeLine>   // search returns 'true' if it was able to do a search</CodeLine>
+<CodeLine>   virtual bool search(const queryparamclass &amp;queryparams,</CodeLine>
+<CodeLine>                         queryresultsclass &amp;queryresults)=0;</CodeLine>
+<CodeLine>   // the document text for 'docnum' is placed in 'output'</CodeLine>
+<CodeLine>   // docTargetDocument returns 'true' if it was able to</CodeLine>
+<CodeLine>   // try to get a document</CodeLine>
+<CodeLine>   // collection is needed to see if an index from the</CodeLine>
+<CodeLine>   // collection is loaded. If no index has been loaded</CodeLine>
+<CodeLine>   // defaultindex is needed to load one</CodeLine>
+<CodeLine>   virtual bool docTargetDocument(const text_t &amp;defaultindex,</CodeLine>
+<CodeLine>                                               const text_t &amp;defaultsubcollection,</CodeLine>
+<CodeLine>                                               const text_t &amp;defaultlanguage,</CodeLine>
+<CodeLine>                                               const text_t &amp;collection,</CodeLine>
+<CodeLine>                                               int docnum,</CodeLine>
+<CodeLine>                                               text_t &amp;output)=0;</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   querycache *cache;</CodeLine>
+<CodeLine>   text_t collectdir; // the collection directory</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="871">Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="search_base_class_api"/> ÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÑÐµÑ Ð»ÐžÑÑÐžÐœÐ³ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÑ API ÐŽÐ»Ñ ÐŸÐ±ÑÐµÐºÑÐ° Search (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="greenstone_runtime_system"/>). Ð­ÑÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐŽÐ²Ðµ Ð²ÐžÑÑÑÐ°Ð»ÑÐœÑÐµ ÑÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÑ: search() Ðž docTargetDocument(). ÐÐ· ÑÐžÑÑÐœÐºÐ° Ð²ÐžÐŽÐœÐŸ, ÑÑÐŸ =0, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ»ÐµÐŽÑÐµÑ Ð·Ð° ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµÐŒ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ°, ÑÑÐŸ ÑÑÐœÐºÑÐžÑ ÑÐžÐ³Ðµ, ÐŸÐ·ÐœÐ°ÑÐ°ÑÑÐ°Ñ, ÑÑÐŸ ÐºÐ»Ð°ÑÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÐœÐ°ÑÐ»ÐµÐŽÑÐµÑ ÐŸÐ±ÑÐµÐºÑ, ÐŽÐŸÐ»Ð¶ÐµÐœ ÐŸÑÑÑÐµÑÑÐ²ÐžÑÑ ÐŸÐ±Ðµ ÑÑÐœÐºÑÐžÐž (ÐžÐœÐ°ÑÐµ ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐŸÑ Ð²ÑÐŽÐ°ÑÑ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐµ).</Text>
+<Text id="872">ÐÐ»Ð°ÑÑ ÑÐ°ÐºÐ¶Ðµ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐŽÐ²Ð° Ð·Ð°ÑÐžÑÐµÐœÐœÑÑ
+ Ð¿ÐŸÐ»Ñ ÐŽÐ°ÐœÐœÑÑ
+: collectdir Ðž cache. ÐÐ±ÑÐµÐºÑ Search ÐžÐ»Ð»ÑÑÑÑÐžÑÑÐµÑÑÑ Ð¿ÑÐžÐŒÐµÑÐ°ÐŒÐž ÐŽÐ»Ñ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð° Ð¿ÐŸÐ»Ðµ collectdir ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ñ
+ÑÐ°ÐœÐµÐœÐžÑ ÑÐžÑÑÐµÐŒÑ ÑÐ°Ð¹Ð»ÐŸÐ² (Ðž ÑÑÐŸ ÐµÑÐµ Ð±ÐŸÐ»ÐµÐµ Ð²Ð°Ð¶ÐœÐŸ - ÐžÑ
+ ÑÐ°Ð¹Ð»Ñ ÐžÐœÐŽÐµÐºÑÐ°) Ð² ÐŒÐµÑÑÐµ ÐœÐ°Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÐ»Ðµ ÑÐ°ÑÐ¹ÐµÑÐŸÑ
+ÑÐ°ÐœÑÐµÑ ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ Ð·Ð°Ð¿ÑÐŸÑÐ°. Ð­ÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ, ÑÑÐŸÐ±Ñ ÑÑÐºÐŸÑÐžÑÑ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÑ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐžÑ
+ Ð·Ð°Ð¿ÑÐŸÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐŽÑÑ ÐŽÑÐ±Ð»ÐžÑÐŸÐ²Ð°ÑÑ ÑÑÐŸÑ Ð·Ð°Ð¿ÑÐŸÑ (Ðž ÐµÐ³ÐŸ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ). Ð ÑÐŸ Ð²ÑÐµÐŒÑ, ÐºÐ°Ðº ÐžÐŽÐµÐœÑÐžÑÐœÑÐµ Ð²ÐŸÐ¿ÑÐŸÑÑ ÐŒÐŸÐ³ÑÑ ÐºÐ°Ð·Ð°ÑÑÑÑ ÐŒÐ°Ð»ÐŸÐ²ÐµÑÐŸÑÑÐœÑÐŒÐž, ÑÐ°ÐºÑÐžÑÐµÑÐºÐž ÐŸÐœÐž Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÑÑ ÑÐµÐ³ÑÐ»ÑÑÐœÐŸ. ÐÑÐŸÑÐŸÐºÐŸÐ» Greenstone ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÐŸÑÑÑÐŒ. Ð§ÑÐŸÐ±Ñ ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÑÑ ÑÑÑÐ°ÐœÐžÑÑ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ², Ð¿ÐŸÐŽÐŸÐ±ÐœÑÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐœÐŸÐ¹ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="searching_gutenberg_for_darcy"/>, ÐœÐŸ ÐŽÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ñ 11 Ð¿ÐŸ 20 ÑÐŸÐ³ÐŸ Ð¶Ðµ ÑÐ°ÐŒÐŸÐ³ÐŸ Ð·Ð°Ð¿ÑÐŸÑÐ°, Ð¿ÐŸÐžÑÐº ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ ÑÐœÐŸÐ²Ð°, ÐœÐ° ÑÐµÐ¹ ÑÐ°Ð· ÐŸÐ³ÐŸÐ²ÐŸÑÐžÐ² Ð·Ð°ÑÐ°ÐœÐµÐµ, Ð²ÐŸÐ·Ð²ÑÐ°Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² 11-20. ÐÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐŽÐµÐ»Ð°ÐµÑ ÑÑÐŸ ÑÑÑÐµÐºÑÐžÐ²ÐœÑÐŒ, ÑÐŸÑ ÑÐ°ÐºÑ, ÑÑÐŸ Ð¿ÐŸÐžÑÐº Ð±ÑÐ» ÑÐ¶Ðµ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœ, ÐŸÐ±ÐœÐ°ÑÑÐ¶ÐµÐœÐœÑÐµ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐžÐ·Ð²Ð»ÐµÑÐµÐœÑ Ð¿ÑÑÐŒÐŸ ÐžÐ· ÐºÑÑÐ°.</Text>
+<Text id="873">ÐÐ±Ð° Ð¿ÐŸÐ»Ñ ÐŽÐ°ÐœÐœÑÑ
+ Ð¿ÑÐžÐŒÐµÐœÐžÐŒÑ Ðº ÐºÐ°Ð¶ÐŽÐŸÐŒÑ ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐŒÑ ÐŸÐ±ÑÐµÐºÑÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÐµÑ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒ Ð¿ÐŸÐžÑÐºÐ°. Ð­ÑÐŸ - ÑÐŸ, Ð¿ÐŸÑÐµÐŒÑ ÐŸÐœÐž Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ Ð² Ð°Ð·ÐŸÐ²ÐŸÐŒ ÐºÐ»Ð°ÑÑÐµ, Ðž ÐŸÐ±ÑÑÐ²Ð»ÐµÐœÑ Ð·Ð°ÑÐžÑÐµÐœÐœÐŸÐ¹ ÑÐµÐºÑÐžÐµÐ¹ ÐºÐ»Ð°ÑÑÐ° ÑÐ°Ðº, ÑÑÐŸÐ±Ñ ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐµ ÐºÐ»Ð°ÑÑÑ ÐŒÐŸÐ³Ð»Ðž Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÐœÐžÐŒ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ.</Text>
+</Content>
+</Subsection>
+<Subsection id="search_and_retrieval_with_mg">
+<Title>
+<Text id="874">Search and retrieval with MG</Text>
+</Title>
+<Content>
+<Text id="875">Greenstone ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ MG (ÑÐŸÐºÑÐ°ÑÐµÐœÐœÐŸ ÐŸÑ Managing Gigabytes, CM.Witten et al., 1999) ÐŽÐ»Ñ ÐžÐœÐŽÐµÐºÑÐ°ÑÐžÐž Ðž Ð²ÐŸÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐžÑÑ
+ÐŸÐŽÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð²ÐºÐ»ÑÑÐµÐœÐ° Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ GSDLHOME/packages. MG ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐŒÐµÑÐŸÐŽÑ ÑÐ¶Ð°ÑÐžÑ, ÑÑÐŸÐ±Ñ ÐŒÐ°ÐºÑÐžÐŒÐ°Ð»ÑÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŒÐµÑÑÐŸ ÐœÐ° ÐŽÐžÑÐºÐµ, ÐœÐµ ÑÑÐ°Ð²Ñ Ð¿ÐŸÐŽ ÑÐ³ÑÐŸÐ·Ñ ÑÐºÐŸÑÐŸÑÑÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ. ÐÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐœÐ° Ð°ÐœÐ³Ð»ÐžÐ¹ÑÐºÐŸÐŒ ÑÐ·ÑÐºÐµ ÑÐ¶Ð°ÑÑÐ¹ ÑÐµÐºÑÑ Ðž Ð¿ÐŸÐ»ÐœÑÐ¹ ÑÐµÐºÑÑ ÐžÐœÐŽÐµÐºÑÐžÑÑÑÑÑÑ Ð²ÐŒÐµÑÑÐµ Ðž ÐŸÑÑÐœÐŸ Ð·Ð°ÐœÐžÐŒÐ°ÑÑ ÐŸÐŽÐœÑ ÑÑÐµÑÑ ÐŒÐµÑÑÐ°, Ð·Ð°ÐœÐžÐŒÐ°ÐµÐŒÐŸÐ³ÐŸ ÐœÐµÑÐ¶Ð°ÑÑÐŒ ÑÐµÐºÑÑÐŸÐŒ. ÐÐŸÐžÑÐº Ðž ÐžÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÑÐ°ÑÑÐŸ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÑÑ Ð±ÑÑÑÑÐµÐµ, ÑÐµÐŒ Ð¿ÐŸÐŽÐŸÐ±ÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ ÐœÐ° ÐœÐµÑÐ¶Ð°ÑÐŸÐ¹ Ð²ÐµÑÑÐžÐž, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ ÐŒÐµÐœÑÑÐµ ÐŽÐžÑÐºÐŸÐ²ÑÑ
+ ÐŸÐ¿ÐµÑÐ°ÑÐžÐ¹.</Text>
+<Figure id="api_for_direct_access_to_mg">
+<Title>
+<Text id="876">API ÐŽÐ»Ñ Ð¿ÑÑÐŒÐŸÐ³ÐŸ ÐŽÐŸÑÑÑÐ¿Ð° Ðº MG (ÑÐŸÐºÑÐ°ÑÐµÐœÐœÑÐ¹ Ð²Ð°ÑÐžÐ°ÐœÑ)</Text>
+</Title>
+<CodeLine>enum result_kinds {</CodeLine>
+<CodeLine>   result_docs,           // Return the documents found in last search</CodeLine>
+<CodeLine>   result_docnums,     // Return document id numbers and weights</CodeLine>
+<CodeLine>   result_termfreqs, // Return terms and frequencies</CodeLine>
+<CodeLine>   result_terms           // Return matching query terms</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>int mgq_ask(char *line);</CodeLine>
+<CodeLine>int mgq_results(enum result_kinds kind, int skip, int howmany,</CodeLine>
+<CodeLine>                               int (*sender)(char *, int, int, float, void *),</CodeLine>
+<CodeLine>                               void *ptr);</CodeLine>
+<CodeLine>int mgq_numdocs(void);</CodeLine>
+<CodeLine>int mgq_numterms(void);</CodeLine>
+<CodeLine>int mgq_equivterms(unsigned char *wordstem,</CodeLine>
+<CodeLine>                           int (*sender)(char *, int, int, float, void *),</CodeLine>
+<CodeLine>                           void *ptr);</CodeLine>
+<CodeLine>int mgq_docsretrieved (int *total_retrieved, int *is_approx);</CodeLine>
+<CodeLine>int mgq_getmaxstemlen ();</CodeLine>
+<CodeLine>void mgq_stemword (unsigned char *word);</CodeLine>
+</Figure>
+<Text id="877">MG ÐŸÐ±ÑÑÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² ÐžÐœÑÐµÑÐ°ÐºÑÐžÐ²ÐœÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ, Ð¿ÐµÑÐ°ÑÐ°Ñ ÐºÐŸÐŒÐ°ÐœÐŽÑ Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐµ. ÐÐŽÐžÐœ ÐžÐ· ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐ² Ð°ÐºÑÐžÐ²Ð°ÑÐžÐž mgsearchclass Ð·Ð°ÐºÐ»ÑÑÐ°ÐµÑÑÑ Ð² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ð¡ systemQ, Ð²ÑÐ·ÑÐ²Ð°ÐµÐŒÐŸÐ¹ Ñ ÐŸÐ±ÑÐµÐºÑÐŸÐŒ, Ð·Ð°Ð¿ÑÑÐºÐŸÐŒ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐ¹ ÐºÐŸÐŒÐ°ÐœÐŽÑ MG. ÐÐŸÐ»ÐµÐµ ÑÑÑÐµÐºÑÐžÐ²ÐœÑÐ¹ Ð¿ÐŸÐŽÑ
+ÐŸÐŽ, ÐŸÐŽÐœÐ°ÐºÐŸ, ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ ÐŸÑÐºÑÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ MG ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑÐœÐºÑÐžÑ Ð²ÑÐ·ÐŸÐ²Ð°. ÐÐŽÐœÐ°ÐºÐŸ, ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ ÑÑÐµÐ±ÑÐµÑÑÑ Ð±ÐŸÐ»ÐµÐµ Ð³Ð»ÑÐ±ÐŸÐºÐŸÐµ Ð·ÐœÐ°ÐœÐžÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ MG. ÐÐŸÐ»ÑÑÐ°Ñ ÑÐ°ÑÑÑ ÑÑÑÐŽÐœÐŸÑÑÐµÐ¹ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÑÐºÑÑÑÐ° Ð·Ð° ÐœÐŸÐ²ÑÐŒ API , ÐºÐŸÑÐŸÑÑÐ¹ ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ ÑÐŸÑÐºÐŸÐ¹ ÑÐŸÐ¿ÑÐžÐºÐŸÑÐœÐŸÐ²ÐµÐœÐžÑ ÐŽÐ»Ñ ÐŸÐ±ÑÐµÐºÑÐ° mgsearchclass. Ð­ÑÐŸ - ÑÐŸÐ»Ñ colserver/mgq. Ñ, ÑÐµÐ¹ API Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="api_for_direct_access_to_mg"/>.</Text>
+<Text id="878">Ð¡Ð¿ÐŸÑÐŸÐ± Ð¿ÐµÑÐµÐŽÐ°ÑÐž Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² Ðº MG - ÑÐµÑÐµÐ· mgq_ask (), ÐºÐŸÑÐŸÑÑÐ¹ Ð±ÐµÑÐµÑ Ð²Ð°ÑÐžÐ°ÐœÑÑ ÑÐµÐºÑÑÐ° Ð² ÑÐŸÑÐŒÐ°ÑÐµ, ÐžÐŽÐµÐœÑÐžÑÐœÐŸÐŒ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐŒÑ Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐµ:</Text>
+<CodeLine>mgq_ask( ".set casefold off ");</CodeLine>
+<Text id="879">Ð­ÑÐŸ ÑÐ°ÐºÐ¶Ðµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð¿ÑÐž Ð²ÑÐ·ÐŸÐ²Ðµ Ð·Ð°Ð¿ÑÐŸÑÐ°. Ð ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐ°ÐŒ ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑ ÑÐµÑÐµÐ· mgq_results, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ñ ÐœÐ° ÑÑÐœÐºÑÐžÑ, ÐºÐ°Ðº ÐµÐµ ÑÐµÑÐ²ÐµÑÑÑÐ¹ Ð¿Ð°ÑÐ°ÐŒÐµÑÑ. Ð­ÑÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð³ÐžÐ±ÐºÐžÐ¹ ÑÐ¿ÐŸÑÐŸÐ± Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž, Ð²ÐŸÐ·Ð²ÑÐ°ÑÐµÐœÐœÐŸÐ¹ Ð² ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+ MG Ð¿ÐŸ ÑÑÐµÐ±ÐŸÐ²Ð°ÐœÐžÑ mgsearchclass. ÐÑÐ·ÐŸÐ² mgqjiumdocs Ð, mgqjiumterms () Ðž mgq_docsretrieved () ÑÐ°ÐºÐ¶Ðµ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, ÐœÐŸ ÐœÐ° ÑÐµÐ¹ ÑÐ°Ð· Ñ Ð±ÐŸÐ»ÐµÐµ Ð¶ÐµÑÑÐºÐžÐŒÐž ÑÑÐ»ÐŸÐ²ÐžÑÐŒÐž. ÐÐŸÑÐ»ÐµÐŽÐœÐžÐµ ÐŽÐ²Ð° ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Ð¿ÑÐž Ð²ÐŸÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐžÐž.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_source_object">
+<Title>
+<Text id="880">ÐÐ±ÑÐµÐºÑ Source</Text>
+</Title>
+<Content>
+<Figure id="source_base_class_api">
+<Title>
+<Text id="881">Source Ð±Ð°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ API</Text>
+</Title>
+<CodeLine>class sourceclass {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   sourceclass ();</CodeLine>
+<CodeLine>   virtual ~sourceclass ();</CodeLine>
+<CodeLine>   // configure should be called once for each configuration line</CodeLine>
+<CodeLine>   virtual void configure (const text_t &amp;key, const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   // init should be called after all the configuration is done but</CodeLine>
+<CodeLine>   // before any other methods are called</CodeLine>
+<CodeLine>   virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   // translate_OID translates OIDs using " .pr " , . " fc " etc.</CodeLine>
+<CodeLine>   virtual bool translate_OID (const text_t &amp;OIDin, text_t &amp;OIDout, comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   // get_metadata fills out the metadata if possible, if it is not</CodeLine>
+<CodeLine>   // responsible for the given OID then it return s false.</CodeLine>
+<CodeLine>   virtual bool get_metadata (const text_t &amp;requestParams, const text_t &amp;refParams,</CodeLine>
+<CodeLine>                           bool getParents, const text_tset &amp;fields, const text_t &amp;OID,</CodeLine>
+<CodeLine>                           MetadataInfo_tmap &amp;metadata, comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool get_document (const text_t &amp;OID, text_t &amp;doc, </CodeLine>
+<CodeLine>                           comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="882">Ð ÐŸÐ»Ñ Source (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="greenstone_runtime_system"/>) - ÐŽÐŸÑÑÑÐ¿ Ðº ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒ Ðž ÑÐµÐºÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐ³ÐŸ Ð±Ð°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="source_base_class_api"/>. Ð€ÑÐœÐºÑÐžÑ-ÑÐ»ÐµÐœ ÐœÐ°ÐœÐŸÑÐžÑ ÐœÐ° ÐºÐ°ÑÑÑ Ðº ÐºÐ°Ð¶ÐŽÐŸÐ¹ Ð·Ð°ÐŽÐ°ÑÐµ: getjnetadata () Ðž get_document () ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸ. ÐÐ±Ð° ÐŸÐ±ÑÑÐ²Ð»ÐµÐœÑ virtual, ÑÐ°Ðº ÑÑÐŸ Ð²ÐµÑÑÐžÑ, ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÑÑÑÑÑÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµÐŒ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ°, Ð²ÑÐ·ÑÐ²Ð°ÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÑÐ°Ð±ÐŸÑÑ. ÐÐŽÐœÐ° ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐ°Ñ Ð²ÐµÑÑÐžÑ ÑÑÐŸÐ³ÐŸ ÐŸÐ±ÑÐµÐºÑÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ GDBM, ÑÑÐŸÐ±Ñ Ð·Ð°Ð¿ÑÑÑÐžÑÑ get_metadata 0 Ðž MG, ÑÑÐŸÐ±Ñ Ð·Ð°Ð¿ÑÑÑÐžÑÑ get_document (): ÐŒÑ ÐŽÐµÑÐ°Ð»ÐžÐ·ÐžÑÑÐµÐŒ ÑÑÑ Ð²ÐµÑÑÐžÑ ÐœÐžÐ¶Ðµ.</Text>
+<Text id="883">ÐÑÑÐ³Ð°Ñ ÑÑÐœÐºÑÐžÑ-ÑÐ»ÐµÐœ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐ° ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="source_base_class_api"/> - configure^, init () Ðž translate_OID Q. ÐÐµÑÐ²ÑÐµ ÐŽÐ²Ð° ÐºÐ°ÑÐ°ÑÑÑÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž, ÐŸÐ¿ÐžÑÐ°ÐœÐœÐŸÐ³ÐŸ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="initialisation"/>.</Text>
+<Text id="884">ÐÑÑÐ°Ð²ÑÐ°ÑÑÑ, translate_OID (), ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ñ ÑÐžÐœÑÐ°ÐºÑÐžÑÐŸÐŒ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ Ð²ÑÑÐ°Ð·ÐžÑÑ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="the_golf_course_mystery"/> ÐŒÑ Ð²ÐžÐŽÐµÐ»Ðž, ÐºÐ°Ðº ÐœÐŸÐŒÐµÑ ÑÑÑÐ°ÐœÐžÑÑ ÐŒÐŸÐ³ Ð±ÑÑÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœ Ð² ÐºÐŸÐœÐµÑ Ðº ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÑÑÐŸÐ±Ñ Ð²ÑÐ·Ð²Ð°ÑÑ ÑÐŸÐ»ÑÐºÐŸ ÑÑÑ ÑÑÑÐ°ÐœÐžÑÑ. Ð­ÑÐŸ Ð±ÑÐ»ÐŸ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÑÑÑÐ°ÐœÐžÑÑ Ð±ÑÐ»Ðž ÐžÐŽÐµÐœÑÐžÑÐžÑÐžÑÐŸÐ²Ð°ÐœÑ ÐºÐ°Ðº "ÑÐ°Ð·ÐŽÐµÐ»Ñ" Ð¿ÑÐž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐµ Ð² ÐºÐŸÐœÐµÑ " . 1" Ðº OID Ð²ÑÐ·ÑÐ²Ð°ÐµÑ Ð¿ÐµÑÐ²ÑÐ¹ ÑÐ°Ð·ÐŽÐµÐ» ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð Ð°Ð·ÐŽÐµÐ»Ñ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð²Ð»ÐŸÐ¶ÐµÐœÐœÑÐŒÐž Ðž ÐŽÐŸÑÑÑÐ¿ÐœÑ ÐŽÐ»Ñ ÐŸÐ±ÑÐ°ÑÐµÐœÐžÑ Ð±Ð»Ð°Ð³ÐŸÐŽÐ°ÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐŒÑ ÐœÐŸÐŒÐµÑÑ, ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐœÐŸÐŒÑ Ð¿ÐµÑÐžÐŸÐŽÐ°ÐŒÐž.</Text>
+<Text id="885">Ð¢Ð°Ðº Ð¶Ðµ, ÐºÐ°Ðº ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐžÐµ ÐœÐŸÐŒÐµÑÐ° ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ², ÑÐžÐœÑÐ°ÐºÑÐžÑ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ ÑÐŸÑÐŒÑ ÐŸÑÐœÐŸÑÐžÑÐµÐ»ÑÐœÐŸÐ³ÐŸ ÐŽÐŸÑÑÑÐ¿Ð°. ÐÐ»Ñ ÑÐµÐºÑÑÐµÐ³ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº first child, ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑ Ð² ÐºÐŸÐœÐµÑ /Ñ, Ðº last child, ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑ Ð² ÐºÐŸÐœÐµÑ .1Ñ, Ðº parent, ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑ Ð² ÐºÐŸÐœÐµÑ .ÑÐ³, Ðº next sibling, ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑ Ð² ÐºÐŸÐœÐµÑ .ns Ðž ^previous sibling, ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑ Ð² ÐºÐŸÐœÐµÑ .ps.</Text>
+<Text id="886"> Ð€ÑÐœÐºÑÐžÑ translate_OID () ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ OIDin Ðž OIDout, ÑÑÐŸÐ±Ñ Ñ
+ÑÐ°ÐœÐžÑÑ ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ Ð²Ð°ÑÐžÐ°ÐœÑ Ðž ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ. Ð¢ÑÐµÐ±ÑÐµÑÑÑ ÐŽÐ²Ð° ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÑ
+ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ° - err Ðž logout. ÐÐœÐž ÑÐŸÐŸÐ±ÑÐ°ÑÑ Ð»ÑÐ±ÐŸÐ¹ ÑÑÐ°ÑÑÑ ÐŸÑÐžÐ±ÐºÐž, ÐºÐŸÑÐŸÑÑÐ¹ ÐŒÐŸÐ¶ÐµÑ Ð²ÐŸÐ·ÐœÐžÐºÐœÑÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ Ð¿ÐµÑÐµÐ²ÐŸÐŽÐ°, Ðž ÑÐµÑÐ°ÑÑ, ÐºÐŸÐ³ÐŽÐ° Ðž ÐºÑÐŽÐ° Ð¿ÐŸÑÐ»Ð°ÑÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐŸÐœÐœÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ. ÐÐ°ÑÐ°ÐŒÐµÑÑÑ ÑÐ²Ð»ÑÑÑÑÑ Ð±Ð»ÐžÐ·ÐºÐžÐŒÐž ÑÐŸÑÐ·ÐœÐžÐºÐ°ÐŒÐž Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°, ÐŒÑ Ðº ÑÑÐŸÐŒÑ Ð²ÐµÑÐœÐµÐŒÑÑ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="protocol"/>.</Text>
+<Part id="database_retrieval_with_gdbm">
+<Title>
+<Text id="887">ÐÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ Ð±Ð°Ð· ÐŽÐ°ÐœÐœÑÑ
+ Ñ gdbm</Text>
+</Title>
+<Content>
+<Text id="888">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° GDBM - ÐŒÐµÐœÐµÐŽÐ¶ÐµÑ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ GNU (www.gnu.org). ÐÐœÐ° ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÐµÑ Ð¿ÑÐŸÑÑÑÑ ÑÑÑÑÐºÑÑÑÑ Ð·Ð°Ð¿ÐžÑÐµÐ¹ Ð¿Ð°Ñ ÐºÐ»ÑÑ/ÐŽÐ°ÐœÐœÑÐµ Ðž ÑÐŸÐ²ÐŒÐµÑÑÐžÐŒÐ° Ñ DBM Ðž NDBM. ÐÐ¿ÐµÑÐ°ÑÐžÐž Ð²ÐºÐ»ÑÑÐ°ÑÑ Ñ
+ÑÐ°ÐœÐµÐœÐžÐµ, ÐžÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ Ðž ÑÐŽÐ°Ð»ÐµÐœÐžÐµ Ð·Ð°Ð¿ÐžÑÐµÐ¹ Ð¿ÐŸ ÐºÐ»ÑÑÑ, Ð° ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐµÑÐµÑÐµÐœÐžÐµ Ð²ÑÐµÑ
+ ÐœÐµÐ·Ð°ÐºÐ°Ð·Ð°ÐœÐœÑÑ
+ ÐºÐ»ÑÑÐµÐ¹. </Text>
+<Figure id="gdbm_database_for_the_gutenberg_collection">
+<Title>
+<Text id="889">GDBM Ð±Ð°Ð·Ð° ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Gutenberg (ÑÑÐ°Ð³ÐŒÐµÐœÑ)</Text>
+</Title>
+<CodeLine>[HASH01d7b30d4827b51282919e9b]</CodeLine>
+<CodeLine>&lt;doctype&gt;         doc</CodeLine>
+<CodeLine>&lt;hastxt&gt;           0</CodeLine>
+<CodeLine>&lt;Title&gt;             The Winter's Tale</CodeLine>
+<CodeLine>&lt;Creator&gt;         William Shakespeare</CodeLine>
+<CodeLine>&lt;archivedir&gt;   HASH01d7/b30d4827.dir</CodeLine>
+<CodeLine>&lt;thistype&gt;       Invisible</CodeLine>
+<CodeLine>&lt;childtype&gt;     Paged</CodeLine>
+<CodeLine>&lt;contains&gt;        " .1; " .2; " .3; " .4; " .5; " .6; " .7; " .8; " .9; " .10; " .11; " .12;            \ <br/>                           " .13; " .14; " .15; " .16; " .17; " .18; " .19; " .20; " .21; " .22;            \ <br/>                           " .23; " .24; " .25; " .26; " .27; " .28; " .29; " .30; " .31; " .32;            \ <br/>                           " .33; " .34; " .35</CodeLine>
+<CodeLine>&lt;docnum&gt;           168483</CodeLine>
+<CodeLine>âââââââââââââââââââââââ-</CodeLine>
+<CodeLine>[CL1]</CodeLine>
+<CodeLine>&lt;doctype&gt;         classify</CodeLine>
+<CodeLine>&lt;hastxt&gt;           0</CodeLine>
+<CodeLine>&lt;childtype&gt;     HList</CodeLine>
+<CodeLine>&lt;Title&gt;             Title</CodeLine>
+<CodeLine>&lt;numleafdocs&gt; 1818</CodeLine>
+<CodeLine>&lt;thistype&gt;       Invisible</CodeLine>
+<CodeLine>&lt;contains&gt;       " .1; " .2; " .3; " .4; " .5; " .6; " .7; " .8; " .9; " .10; " .11; " .12;          \ <br/>                           " .13; " .14; " .15; " .16; " .17; " .18; " .19; " .20; " .21; " .22;          \ <br/>                            " .23; " .24</CodeLine>
+<CodeLine>âââââââââââââââââââââââ-</CodeLine>
+<CodeLine>[CL1.1]</CodeLine>
+<CodeLine>&lt;doctype&gt;         classify</CodeLine>
+<CodeLine>&lt;hastxt&gt;           0</CodeLine>
+<CodeLine>&lt;childtype&gt;     VList</CodeLine>
+<CodeLine>&lt;Title&gt;             A</CodeLine>
+<CodeLine>&lt;numleafdocs&gt; 118</CodeLine>
+<CodeLine>&lt;contains&gt;      HASH0130bc5f9f90089b3723431f;HASH9cba43bacdab5263c98545;\</CodeLine>
+<CodeLine>                          HASH12c88a01da6e8379df86a7;HASH9c86579a83e1a2e4cf9736;   \</CodeLine>
+<CodeLine>                           HASHdc2951a7ada1f36a6c3aca;HASHea4dda6bbc7cdeb4abfdee;   \</CodeLine>
+<CodeLine>                          HASHce55006513c47235ac38ba;HASH012a33acaa077c0e612b9351;\</CodeLine>
+<CodeLine>                          HASH010dd1e923a123826ae30e4b;HASHaf674616785679fed4b7ee;\</CodeLine>
+<CodeLine>                         HASH0147eef4b9d1cb135e096619;HASHe69b9dbaa83ffb045d963b;\</CodeLine>
+<CodeLine>                         HASH01abc61c646c8e7a8ce88b10;HASH5f9cd13678e21820e32f3a;\</CodeLine>
+<CodeLine>                         HASHe8cbba1594c72c98f9aa1b;HASH01292a2b7b6b60dec96298bc;\</CodeLine>
+<CodeLine>                         ...</CodeLine>
+</Figure>
+<Text id="890">Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑ ÑÑÐ°Ð³ÐŒÐµÐœÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐ° Ð¿ÑÐž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Gutenberg. Ð€ÑÐ°Ð³ÐŒÐµÐœÑ Ð±ÑÐ» ÑÐŸÐ·ÐŽÐ°Ðœ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑÐžÐ»ÐžÑÑ db2txt ÑÐžÑÑÐµÐŒÑ Greenstone, ÐºÐŸÑÐŸÑÐ°Ñ ÐºÐŸÐœÐ²ÐµÑÑÐžÑÑÐµÑ GDBM ÐŽÐ²ÐŸÐ¹ÐœÐŸÐ¹ ÑÐŸÑÐŒÐ°Ñ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ Ð² ÑÐµÐºÑÑÐŸÐ²ÑÑ ÑÐŸÑÐŒÑ. Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÑÐž Ð·Ð°Ð¿ÐžÑÐž, ÐŸÑÐŽÐµÐ»ÐµÐœÐœÑÐµ Ð³ÐŸÑÐžÐ·ÐŸÐœÑÐ°Ð»ÑÐœÑÐŒÐž Ð»ÐžÐœÐžÑÐŒÐž. ÐÐµÑÐ²ÑÐ¹ - Ð²Ñ
+ÐŸÐŽ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÐŽÑÑÐ³ÐžÐµ ÐŽÐ²Ð° - ÑÐ°ÑÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÐž, ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐŒ AZList ÐŽÐ»Ñ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐµÑÐ²Ð°Ñ ÑÑÑÐŸÐºÐ° ÐºÐ°Ð¶ÐŽÐŸÐ¹ Ð·Ð°Ð¿ÐžÑÐž - ÐµÐµ ÐºÐ»ÑÑ.</Text>
+<Text id="891">ÐÐ°Ð¿ÐžÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ñ
+ÑÐ°ÐœÐžÑ Ð·Ð°Ð³Ð»Ð°Ð²ÐžÐµ ÐºÐœÐžÐ³Ðž, Ð°Ð²ÑÐŸÑÐ° Ðž Ð»ÑÐ±ÑÐµ ÐŽÑÑÐ³ÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÐµ (ÐžÐ»Ðž ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐœÑÐµ) Ð²ÐŸ Ð²ÑÐµÐŒÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ°Ð¿ÐžÑÑ ÑÐ°ÐºÐ¶ÐµÐ±ÑÐ²Ð°ÐµÑ ÐŽÐ»Ñ Ð²ÐœÑÑÑÐµÐœÐœÐµÐ³ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ Ðž Ñ
+ÑÐ°ÐœÐžÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÑÐŸÐŒ, Ð³ÐŽÐµ ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ ÑÐ°Ð¹Ð»Ñ, ÑÐ²ÑÐ·Ð°ÐœÐœÑÐµ Ñ ÑÑÐžÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ (<i>&lt;archivedir&gt;</i>), Ðž ÐœÐŸÐŒÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ Ð²ÐœÑÑÑÐž MG (<i>&lt;docnum&gt;</i>).</Text>
+<Text id="892">ÐÐŸÐ»Ðµ <i>&lt;contains&gt;</i> Ñ
+ÑÐ°ÐœÐžÑ ÑÐ¿ÐžÑÐŸÐº ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ², ÐŸÑÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÑÐŸÑÐºÐ°ÐŒÐž Ñ Ð·Ð°Ð¿ÑÑÐŸÐ¹. Ð­ÑÐŸ ÑÐŸÑÐºÐž, ÑÐ²ÑÐ·ÑÐ²Ð°ÑÑÐžÐµ Ð·Ð°Ð¿ÐžÑÐž Ð² Ð±Ð°Ð·Ðµ ÐŽÐ°ÐœÐœÑÑ
+. ÐÐ»Ñ Ð·Ð°Ð¿ÐžÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° <i>&lt;contains&gt;</i> ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ, ÑÑÐŸÐ±Ñ ÑÐºÐ°Ð·Ð°ÑÑ ÐœÐ° Ð²Ð»ÐŸÐ¶ÐµÐœÐœÑÐµ ÑÐ°Ð·ÐŽÐµÐ»Ñ. ÐÐŸÑÐ»ÐµÐŽÑÑÑÐžÐµ ÐºÐ»ÑÑÐž Ð·Ð°Ð¿ÐžÑÐž ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÑ, ÑÐ²ÑÐ·ÑÐ²Ð°Ñ ÑÐµÐºÑÑÐžÐ¹ ÐºÐ»ÑÑ Ñ ÐŸÐŽÐœÐžÐŒ ÐžÐ· ÐŽÐŸÑÐµÑÐœÐžÑ
+ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² (ÐŸÑÐŽÐµÐ»ÐµÐœÐœÑÑ
+ Ð¿ÐµÑÐžÐŸÐŽÐŸÐŒ).</Text>
+<Text id="893">ÐÑÐŸÑÐ°Ñ Ð·Ð°Ð¿ÐžÑÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="gdbm_database_for_the_gutenberg_collection"/> - Ð³Ð»Ð°Ð²ÐœÑÐ¹ ÑÐ·ÐµÐ» ÐŽÐ»Ñ ÐžÐµÑÐ°ÑÑ
+ÐžÐž ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž Titles AâZ. ÐÐ³ÐŸ ÐŽÐµÑÐž ÐŽÐŸÑÑÑÐ¿ÐœÑ ÑÐµÑÐµÐ· Ð¿ÐŸÐ»Ðµ &lt;contains&gt;, Ð²ÐºÐ»ÑÑÐ°Ñ CL 1.1, CL1.2, CL1.3 Ðž ÑÐ°Ðº ÐŽÐ°Ð»ÐµÐµ, ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐµ ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÑÐŒ ÑÑÑÐ°ÐœÐžÑÐ°ÐŒ ÐŽÐ»Ñ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² Ð, Ð, Ð¡ Ðž Ñ.ÐŽ. ÐÐŒÐµÐµÑÑÑ ÑÐŸÐ»ÑÐºÐŸ 24 ÑÐµÐ±ÐµÐœÐºÐ°: ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ AZList ÑÐ»ÐžÐ» Q-R Ðž Y-Z Ð²Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŸÐœÐž ÐŸÑ
+Ð²Ð°ÑÐžÐ»Ðž ÑÐŸÐ»ÑÐºÐŸ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ Ð·Ð°Ð³Ð»Ð°Ð²ÐžÐ¹.</Text>
+<Text id="894">ÐÐµÑÐž Ð² Ð¿ÐŸÐ»Ðµ <i>&lt;contains&gt;</i> ÑÑÐµÑÑÐµÐ¹ Ð·Ð°Ð¿ÐžÑÐž, CL 1.1,- ÑÑÐŸ ÐºÐŸÐœÐµÑÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ. ÐÐŸÐ·ÐŒÐŸÐ¶ÐœÑ Ðž Ð±ÐŸÐ»ÐµÐµ ÑÐ»ÐŸÐ¶ÐœÑÐµ ÑÑÑÑÐºÑÑÑÑ - Ð¿ÐŸÐ»Ðµ <i>&lt;contains&gt;</i> ÐŒÐŸÐ¶ÐµÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÑÐŒÐµÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ CL ÑÐ·Ð»ÐŸÐ². ÐÐ»ÑÑÐž, Ð²ÑÑÐ°Ð¶ÐµÐœÐœÑÐµ ÐŸÑÐœÐŸÑÐžÑÐµÐ»ÑÐœÐŸ ÑÐµÐºÑÑÐµÐ³ÐŸ, ÐŸÑÐ»ÐžÑÐ°ÑÑ ÐŸÑ Ð°Ð±ÑÐŸÐ»ÑÑÐœÑÑ
+ ÐºÐ»ÑÑÐµÐ¹, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŸÐœÐž ÐœÐ°ÑÐžÐœÐ°ÑÑÑÑ Ñ ÐºÐ°Ð²ÑÑÐµÐº (").</Text>
+</Content>
+</Part>
+<Part id="using_mg_and_gdbm_to_implement_a_source_object">
+<Title>
+<Text id="895">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ MG Ðž GDBM ÐŽÐ»Ñ ÑÐµÐ°Ð»ÐžÐ·Ð°ÑÐžÐž ÐŸÐ±ÑÐµÐºÑÐ° Source</Text>
+</Title>
+<Content>
+<Figure id="api_for_mg_and_gdbm_based_version_of_sourceclass">
+<Title>
+<Text id="896">API ÐŽÐ»Ñ sourceclass Ð±Ð°Ð·ÐŸÐ²ÐŸÐ¹ Ð²ÐµÑÑÐžÐž MG Ðž GDBM (ÑÐŸÐºÑÐ°ÑÐµÐœÐœÑÐ¹ Ð²Ð°ÑÐžÐ°ÐœÑ)</Text>
+</Title>
+<CodeLine>class mggdbmsourceclass : public sourceclass {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   // Omitted, data fields that store:</CodeLine>
+<CodeLine>   //     collection specific file information</CodeLine>
+<CodeLine>   //     index substructure</CodeLine>
+<CodeLine>   //     information about parent</CodeLine>
+<CodeLine>   //     pointers to gdbm and mgsearch objects</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   mggdbmsourceclass ();</CodeLine>
+<CodeLine>   virtual ~mggdbmsourceclass ();</CodeLine>
+<CodeLine>   void set_gdbmptr (gdbmclass *thegdbmptr);</CodeLine>
+<CodeLine>   void set_mgsearchptr (searchclass *themgsearchptr);</CodeLine>
+<CodeLine>   void configure (const text_t &amp;key, const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   bool translate_OID (const text_t &amp;OIDin, text_t &amp;OIDout,</CodeLine>
+<CodeLine>                                           comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   bool get_metadata (const text_t &amp;requestParams,</CodeLine>
+<CodeLine>                                           const text_t &amp;refParams,</CodeLine>
+<CodeLine>                                         bool getParents, const text_tset &amp;fields,</CodeLine>
+<CodeLine>                                         const text_t &amp;OID, MetadataInfo_tmap &amp;metadata,</CodeLine>
+<CodeLine>                                         comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   bool get_document (const text_t &amp;OID, text_t &amp;doc,</CodeLine>
+<CodeLine>                                         comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="897">ÐÐ±ÑÐµÐºÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐµÐŽÐžÐœÑÐµÑ MG Ðž GDBM, ÑÑÐŸÐ±Ñ ÑÐµÐ°Ð»ÐžÐ·ÐŸÐ²Ð°ÑÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ sourceclass -ÑÑÐŸ mggdbmsourceclass. Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="api_for_mg_and_gdbm_based_version_of_sourceclass"/> ÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÑÐµÑ ÐµÐ³ÐŸ API. ÐÐ²Ðµ ÐœÐŸÐ²ÑÑ
+ ÑÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÐ° set_gdbmptr () Ðž set_mgsearchptr () Ñ
+ÑÐ°ÐœÑÑ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ðž ÐœÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐµ ÐžÐŒ ÐŸÐ±ÑÐµÐºÑÑ, ÑÐ°Ðº, ÑÑÐŸÐ±Ñ Ð¿ÑÐž Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐž getjnetadata Ð Ðž get_document () ÐžÐŒÐµÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐŒ ÐžÐœÑÑÑÑÐŒÐµÐœÑÐ°Ð»ÑÐœÑÐŒ ÑÑÐµÐŽÑÑÐ²Ð°ÐŒ ÐŽÐ»Ñ Ð·Ð°Ð²ÐµÑÑÐµÐœÐžÑ ÑÐ°Ð±ÐŸÑÑ.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="the_filter_object">
+<Title>
+<Text id="898">ÐÐ±ÑÐµÐºÑ Filter</Text>
+</Title>
+<Content>
+<Figure id="api_for_the_filter_base_class">
+<Title>
+<Text id="899">API for the Filter base class</Text>
+</Title>
+<CodeLine>class filterclass {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   text_t gsdlhome;</CodeLine>
+<CodeLine>   text_t collection;</CodeLine>
+<CodeLine>   text_t collectdir;</CodeLine>
+<CodeLine>   FilterOption_tmap filterOptions;</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   filterclass ();</CodeLine>
+<CodeLine>   virtual ~filterclass ();</CodeLine>
+<CodeLine>   virtual void configure (const text_t &amp;key,Â const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   // returns the name of this filter</CodeLine>
+<CodeLine>   virtual text_t get_filter_name ();</CodeLine>
+<CodeLine>   // returns the current filter options</CodeLine>
+<CodeLine>   virtual void get_filteroptions (InfoFilterOptionsResponse_t &amp;response,</CodeLine>
+<CodeLine>                                 comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void filter (const FilterRequest_t &amp;request,</CodeLine>
+<CodeLine>                         FilterResponse_t &amp;response,</CodeLine>
+<CodeLine>                         comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="900">API Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ° ÐŽÐ»Ñ ÐŸÐ±ÑÐµÐºÑÐ° Filter (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="greenstone_runtime_system"/>) Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ ÐœÐ° Ð ÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="api_for_the_filter_base_class"/>. ÐÐœ ÐœÐ°ÑÐžÐœÐ°ÐµÑÑÑ Ñ Ð·Ð°ÑÐžÑÐµÐœÐœÑÑ
+ Ð¿ÐŸÐ»ÐµÐ¹ ÐŽÐ°ÐœÐœÑÑ
+ gsdlhome, collection Ðž collectdir. ÐÐœÐž ÐŸÐ±ÑÑÐœÐŸ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÑÑ Ð² ÐºÐ»Ð°ÑÑÐ°Ñ
+, ÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÐ»Ð¶ÐœÑ ÐŸÐ±ÑÐ°ÑÐžÑÑÑÑ Ðº ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹ ÑÐ°Ð¹Ð»Ð°ÐŒ.</Text>
+<BulletList>
+<Bullet>
+<Text id="901"><i>gsdlhome</i> ÑÐŸÑÐœÐŸ ÑÐ°ÐºÐŸÐ¹ Ð¶Ðµ, ÐºÐ°Ðº GSDLHOME, Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐŸÐ±ÑÐµÐºÑ ÐŒÐŸÐ³ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÐŒÐµÑÑÐŸÐœÐ°Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÐµ ÑÐ°Ð¹Ð»ÐŸÐ² Greenstone.</Text>
+</Bullet>
+<Bullet>
+<Text id="902"><i>collection</i> - ÐžÐŒÑ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ð°, ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐ³ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</Bullet>
+<Bullet>
+<Text id="903"><i>collectdir</i> - Ð¿ÐŸÐ»ÐœÐŸÐµ ÐžÐŒÑ Ð¿ÑÑÐž Ðº ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÑÑÐŸ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐœÐµ ÐŽÐŸÐ»Ð¶ÐœÐ° Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑÑ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ GSDLHOME ÐŸÐ±Ð»Ð°ÑÑÐž).</Text>
+</Bullet>
+</BulletList>
+<Text id="904"><i>mggdbsourceclass</i> - ÐŽÑÑÐ³ÐŸÐ¹ ÐºÐ»Ð°ÑÑ, ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÑÑÐž ÑÑÐž Ð¿ÐŸÐ»Ñ ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+<Text id="905">Ð€ÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÑ conflgure() Ðž init() (ÑÐ°ÐœÐµÐµ ÑÐ¿ÐŸÐŒÐžÐœÐ°Ð²ÑÐžÐµÑÑ Ð² sourceclass) ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð¿ÑÐŸÑÐµÑÑÐŸÐŒ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž. Ð¡Ð°ÐŒ ÐŸÐ±ÑÐµÐºÑ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐœÐµÐŽÐ°Ð»ÐµÐºÐŸ ÐŸÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐ¹ ÑÐ°ÑÑÐž ÑÐžÐ»ÑÑÑÐ° Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°; Ð² ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž getjilteroptions Ð Ðž fllter() ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑ ÐŸÐŽÐžÐœ ÐŽÑÑÐ³ÐŸÐŒÑ.</Text>
+<Figure id="how_a_filter_option_is_stored">
+<Title>
+<Text id="906">ÐÐ°Ðº Ñ
+ÑÐ°ÐœÐžÑÑÑ ÐŸÐ¿ÑÐžÑ filter</Text>
+</Title>
+<CodeLine>struct FilterOption_t {</CodeLine>
+<CodeLine>   void clear (); \   void check_defaultValue ();</CodeLine>
+<CodeLine>   FilterOption_t () {clear();}</CodeLine>
+<CodeLine>   text_t name;</CodeLine>
+<CodeLine>   enum type_t {booleant=0, integert=1, enumeratedt=2, stringt=3};</CodeLine>
+<CodeLine>   type_t type;</CodeLine>
+<CodeLine>   enum repeatable_t {onePerQuery=0, onePerTerm=1, nPerTerm=2};</CodeLine>
+<CodeLine>   repeatable_t repeatable;</CodeLine>
+<CodeLine>   text_t defaultValue;</CodeLine>
+<CodeLine>   text_tarray validValues;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>struct OptionValue_t {</CodeLine>
+<CodeLine>   void clear ();</CodeLine>
+<CodeLine>   text_t name;</CodeLine>
+<CodeLine>   text_t value;</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="907">Ð ÑÐµÐœÑÑÐ°Ð»ÑÐœÑÐŒ ÐŸÐ¿ÑÐžÑÐŒ ÑÐžÐ»ÑÑÑÐ° ÐŸÑÐœÐŸÑÑÑÑÑ ÐŽÐ²Ð° ÐºÐ»Ð°ÑÑÐ°, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÑÐµ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="how_a_filter_option_is_stored"/>. Ð¡ÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÑÐµ Ð²ÐœÑÑÑÐž FilterOption_t - ÑÑÐŸ Ð¿Ð°ÑÐµ ÐŸÐ¿ÑÐžÐž, ÐµÐµ type Ðž ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸ Ð»Ðž ÑÑÐŸ - repeatable. ÐÐœÑÐµÑÐ¿ÑÐµÑÐ°ÑÐžÑ validValues Ð·Ð°Ð²ÐžÑÐžÑ ÐŸÑ ÑÐžÐ¿Ð° ÐŸÐ¿ÑÐžÐž. ÐÐ»Ñ ÐÑÐ»ÐµÐ²Ð° ÑÐžÐ¿Ð° Ð¿ÐµÑÐ²ÑÐŒ Ð·ÐœÐ°ÑÐµÐœÐžÐµÐŒ Ð¿ÐµÑÐµÐŒÐµÐœÐŸÐ¹ ÑÐ²Ð»ÑÐµÑÑÑ^Ð³/5Ðµ,Ð° Ð²ÑÐŸÑÑÐŒ - true. ÐÐ»Ñ ÑÐµÐ»ÐŸÑÐžÑÐ»ÐµÐœÐœÐŸÐ³ÐŸ ÑÐžÐ¿Ð° Ð¿ÐµÑÐ²ÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ - ÐŒÐžÐœÐžÐŒÐ°Ð»ÑÐœÑÐ¹ ÐœÐŸÐŒÐµÑ, Ð²ÑÐŸÑÐŸÐ¹ - ÐŒÐ°ÐºÑÐžÐŒÐ°Ð»ÑÐœÑÐ¹. ÐÐ»Ñ Ð¿ÐµÑÐµÑÐžÑÐ»ÑÐµÐŒÐŸÐ³ÐŸ ÑÐžÐ¿Ð° Ð²ÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ Ð¿ÐµÑÐµÑÐžÑÐ»ÐµÐœÑ. ÐÐ»Ñ ÑÑÑÐŸÐºÐŸÐ²ÐŸÐ³ÐŸ ÑÐžÐ¿Ð° Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐžÐ³ÐœÐŸÑÐžÑÑÐµÑÑÑ. ÐÐ»Ñ Ð±ÐŸÐ»ÐµÐµ Ð¿ÑÐŸÑÑÑÑ
+ ÑÐžÑÑÐ°ÑÐžÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ OptionValue_t, Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð·Ð°Ð¿ÐžÑÐž ÐºÐ°Ðº text_t name ÐŸÐ¿ÑÐžÐž Ðž ÐµÐµ value.</Text>
+<Text id="908">ÐÐ°Ð¿ÑÐŸÑ Ðž ÐŸÑÐ²ÐµÑ ÐŸÐ±ÑÐµÐºÑÐ° Ð¿ÑÐŸÑ
+ÐŸÐŽÑÑ ÐºÐ°Ðº Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ juuLJilterclass. Ð¡ÐŸÐ·ÐŽÐ°ÐœÑÑ ÐžÐ· ÐœÐžÑ
+ ÐŽÐ²Ð° ÐºÐ»Ð°ÑÑÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÐµ ÐŒÐ°ÑÑÐžÐ²Ñ, ÑÑÐŸÐ±Ñ ÑÐŸÑ
+ÑÐ°ÐœÐžÑÑ ÐœÐ°Ð±ÐŸÑ ÑÐžÐ¿ÐŸÐ² ÐŸÐ¿ÑÐžÐ¹, ÑÑÐµÐ±ÑÐµÐŒÑÑ
+ ÐŽÐ»Ñ InfoFilterOptionsResponseJ. ÐÐ»Ñ ÐŽÐµÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÐžÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ Ð²ÐŸÐ¿ÑÐŸÑÐ° ÑÐŒÐŸÑÑÐžÑÐµ GSDLHOME/src/recpt/comtypes.h.</Text>
+</Content>
+</Subsection>
+<Subsection id="inherited_filter_objects">
+<Title>
+<Text id="909">ÐÐ±ÑÐµÐºÑÑ ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ Filter</Text>
+</Title>
+<Content>
+<Figure id="inheritance_hierarchy_for_filter">
+<Title>
+<Text id="910">ÐÐµÑÐ°ÑÑ
+ÐžÑ ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ Filter</Text>
+</Title>
+<File width="337" height="245" url="images/Dev_Fig_080.png"/>
+</Figure>
+<Text id="911">ÐÐ²Ð° ÑÑÐŸÐ²ÐœÑ ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ ÑÐžÐ»ÑÑÑÐŸÐ², ÐºÐ°Ðº Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="inheritance_hierarchy_for_filter"/>. Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð±ÑÐ»ÐŸ ÑÐŽÐµÐ»Ð°ÐœÐŸ ÑÐ°Ð·Ð»ÐžÑÐžÐµ ÐŒÐµÐ¶ÐŽÑ ÑÐžÐ»ÑÑÑÐ°ÐŒÐž Query Ðž Browse, Ð° Ð·Ð°ÑÐµÐŒ Ð¿ÐµÑÐ²ÐŸÐŒÑ ÐžÐ· ÐœÐžÑ
+ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ, ÐŸÑÐœÐŸÐ²Ð°ÐœÐœÐŸÐµ ÐœÐ° MG. ÐÐ»Ñ ÐºÐŸÑÑÐµÐºÑÐœÐŸÐ¹ ÑÐ°Ð±ÐŸÑÑ mgqueryfilterclass ÑÑÐµÐ±ÑÐµÑÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº MG ÑÐµÑÐµÐ· mgsearchclass Ðž Ðº GDBM ÑÐµÑÐµÐ· gdbmclass. browsefllterclass ÐœÑÐ¶ÐŽÐ°ÐµÑÑÑ Ð² ÐŽÐŸÑÑÑÐ¿Ðµ ÑÐŸÐ»ÑÐºÐŸ Ðº GDBM. Ð£ÐºÐ°Ð·Ð°ÑÐµÐ»Ðž ÐœÐ° ÑÑÐž ÐŸÐ±ÑÐµÐºÑÑ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÑ ÐºÐ°Ðº Ð·Ð°ÑÐžÑÐµÐœÐœÑÐµ Ð¿ÐŸÐ»Ñ ÐŽÐ°ÐœÐœÑÑ
+ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÑ
+ ÐºÐ»Ð°ÑÑÐŸÐ².</Text>
+</Content>
+</Subsection>
+<Subsection id="the_collection_server_code">
+<Title>
+<Text id="912">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÑÐµÑÐ²ÐµÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="913">Ð Ð°ÑÑÐŒÐŸÑÑÐžÐŒ ÑÐ°Ð¹Ð»Ñ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° Ð² GSDLHOME/SRC/COLSERVR Ñ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµÐŒ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐžÐ· ÐœÐžÑ
+. ÐÐŒÑ ÑÐ°Ð¹Ð»Ð° Ð²ÐŸÐŸÐ±ÑÐµ Ð¿ÐŸÐ²ÑÐŸÑÑÐµÑ ÐžÐŒÑ ÐŸÐ±ÑÐµÐºÑÐ°, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐµ Ð² ÐµÐ³ÐŸ Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="120">
+<Text id="914"><b>browsefilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="915">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ mfilterdass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ ÐŽÐŸÑÑÑÐ¿ Ðº GDBM (ÐÐ¿ÐžÑÐ°Ðœ Ð²ÑÑÐµ).</Text>
+</th>
+</tr>
+<tr>
+<th width="120"/>
+</tr>
+<tr>
+<th width="120">
+<Text id="916"><b>collectserver.h</b></Text>
+</th>
+<th width="420">
+<Text id="917">Ð­ÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÑÐ²ÑÐ·ÑÐ²Ð°ÐµÑ Ð²ÐŒÐµÑÑÐµ Filters Ðž Sources ÐŽÐ»Ñ ÐŸÐŽÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÑÐŒÐžÑÑÑ ÐŸÐ±ÑÐµÐºÑ Collection, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÑÐ¹ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="greenstone_runtime_system"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="918"><b>colservrconfig.h</b></Text>
+</th>
+<th width="420">
+<Text id="919">Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° ÐŽÐ»Ñ ÑÑÐµÐœÐžÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹ ÑÐ°Ð¹Ð»ÐŸÐ² etc/'collect, cfg Ðž index/build, cfg. ÐÐµÑÐ²ÑÐ¹ ÐžÐ· ÐœÐžÑ
+ - ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÑÐ»ÐµÐŽÐœÐžÐ¹ - ÑÐ°Ð¹Ð», ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ Ð¿ÑÐŸÑÐµÑÑÐŸÐŒ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÐŽÐµÐ»Ð°ÐµÑ Ð·Ð°Ð¿ÐžÑÑ Ð²ÑÐµÐŒÐµÐœÐž Ð¿ÐŸÑÐ»ÐµÐŽÐœÐµÐ¹ ÑÑÐ¿ÐµÑÐœÐŸÐ¹ ÐºÐŸÐŒÐ¿ÐŸÐœÐŸÐ²ÐºÐž, ÐºÐ°ÑÑÑ ÐžÐœÐŽÐµÐºÑÐœÐŸÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ°, Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð±ÑÐ»ÐŸ ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐŸ Ðž ÐºÐ°Ðº ÑÐºÐŸÐ»ÑÐºÐŸ Ð±Ð°Ð¹Ñ ÐŸÐœÐž Ð·Ð°ÐœÐžÐŒÐ°ÑÑ (Ð² ÑÐ°ÑÐ¿Ð°ÐºÐŸÐ²Ð°ÐœÐœÐŸÐŒ Ð²ÐžÐŽÐµ).</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="920"><b>filter.h</b></Text>
+</th>
+<th width="420">
+<Text id="921">ÐÐ±ÑÐµÐºÑ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ° Filter fllterclass ÐŸÐ¿ÐžÑÐ°Ðœ Ð²ÑÑÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="922"><b>maptools.h</b></Text>
+</th>
+<th width="420">
+<Text id="923">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐºÐ»Ð°ÑÑ, ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÐ¹ stringmap, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ Ðž Ð±ÑÑÑÑÑÐ¹ Ð¿ÑÐŸÑÐŒÐŸÑÑ, Ð¿ÐŸÐŒÐœÐžÑ Ð¿ÐµÑÐ²ÐŸÐœÐ°ÑÐ°Ð»ÑÐœÑÐ¹ Ð¿ÐŸÑÑÐŽÐŸÐº ÐºÐ°ÑÑÑ text_t. ÐÑÐ¿ÐŸÐ»ÑÐ·ÐµÑÑÑ Ð² mggdbmsourceclass Ðž query'fllterclass.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="924"><b>mggdbmsource.h</b></Text>
+</th>
+<th width="420">
+<Text id="925">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ sourcedass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐµÑ ÐŽÐŸÑÑÑÐ¿ Ðº MG Ðž GDBM (ÐŸÐ¿ÐžÑÐ°Ðœ Ð²ÑÑÐµ).</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="926"><b>mgppqueryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="927">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ query'filterclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ QueryFilter, ÐŸÑÐœÐŸÐ²Ð°ÐœÐœÐŸÐ³ÐŸ ÐœÐ° MG++, ÑÐ»ÑÑÑÐµÐœÐœÐŸÐ¹ Ð²ÐµÑÑÐžÐž MG, ÐœÐ°Ð¿ÐžÑÐ°ÐœÐœÐŸÐ¹ ÐœÐ° C++. ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ, ÑÑÐŸ Greenstone ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ, ÑÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ MG Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, ÑÐ°Ðº ÐºÐ°Ðº MG++ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð²ÑÐµ ÐµÑÐµ Ð² ÑÐ°Ð·Ð²ÐžÑÐžÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="928"><b>mgppsearch.h</b></Text>
+</th>
+<th width="420">
+<Text id="929">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ searchclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ Search /ÐÐŸÐžÑÐºÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ MG++. ÐÐŸÐŽÐŸÐ±ÐœÐŸ mgppqueryfllterclass, ÐŸÐœ ÐœÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="930"><b>mgq.h</b></Text>
+</th>
+<th width="420">
+<Text id="931">ÐÐœÑÐµÑÑÐµÐ¹Ñ ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ Ðº Ð¿Ð°ÐºÐµÑÑ MG. ÐÑÐœÐŸÐ²ÐœÑÐµ ÑÑÐœÐºÑÐžÐž <i>mg_ask()</i> Ðž <i>mg_results()</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="932"><b>mgqueryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="933">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ queryfllterclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµÐÐžÐµÐ³ÑÐ ÐšÐµÐ³, ÐŸÑÐœÐŸÐ²Ð°ÐœÐœÐŸÐ³ÐŸ ÐœÐ° MG.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="934"><b>mgsearch.h</b></Text>
+</th>
+<th width="420">
+<Text id="935">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ searchclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ Search, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ MG (ÐŸÐ¿ÐžÑÐ°Ðœ Ð²ÑÑÐµ.)</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="936"><b>phrasequeryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="937">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ mgqueryclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ Ð·Ð°Ð¿ÑÐŸÑÐ°, ÐŸÑÐœÐŸÐ²Ð°ÐœÐœÐŸÐ³ÐŸ ÐœÐ° ÑÑÐ°Ð·Ðµ. ÐÐœ ÐœÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² Ð·Ð°ÐŽÐ°ÐœÐœÐŸÐ¹ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž. ÐÐŒÐµÑÑÐŸ ÑÑÐŸÐ³ÐŸ mgqueryfllterclass ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ ÑÑÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÑÐµÑÐµÐ· ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÑÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ ÐŸÑ phrasesearch.h.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="938"><b>phrasesearch.h</b></Text>
+</th>
+<th width="420">
+<Text id="939">Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐžÑ Ð¿ÐŸÐžÑÐºÐ° Ð¿ÐŸ ÑÑÐ°Ð·Ðµ, ÐºÐ°Ðº ÐŸÐ¿ÐµÑÐ°ÑÐžÑ Ð¿ÐŸÑÑÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="940"><b>querycache.h</b></Text>
+</th>
+<th width="420">
+<Text id="941">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ searchclass Ðž ÐµÐ³ÐŸ ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐŒÐž ÐºÐ»Ð°ÑÑÐ°ÐŒÐž ÐŽÐ»Ñ ÐºÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² Ð·Ð°Ð¿ÑÐŸÑÐ°, Ð¿ÑÐž Ð³ÐµÐœÐµÑÐ°ÑÐžÐž ÑÑÑÐ°ÐœÐžÑ Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÑ
+ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² ÐœÐ°ÐžÐ±ÐŸÐ»ÐµÐµ ÑÑÑÐµÐºÑÐžÐ²ÐµÐœ (ÐŸÐ¿ÐžÑÐ°Ðœ Ð²ÑÑÐµ.)</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="942"><b>queryfilter.h</b></Text>
+</th>
+<th width="420">
+<Text id="943">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ° Filter filterclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÑÐœÐŸÐ²ÑÐ²Ð°ÐµÑ Ð±Ð°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ ÐŽÐ»Ñ ÐŸÐ±ÑÐµÐºÑÐŸÐ² Query filter (ÐŸÐ¿ÐžÑÐ°Ðœ Ð²ÑÑÐµ.)</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="944"><b>queryinfo.h</b></Text>
+</th>
+<th width="420">
+<Text id="945">ÐÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° Ð¿ÐŸÐžÑÐºÐ°: ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÐŸÐ±ÑÐµÐºÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ Ð·Ð°Ð¿ÑÐŸÑÐ°, ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÑ Ð¿ÐŸÐžÑÐºÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ðž ÑÐ°ÑÑÐŸÑÑ Ð²ÑÑÑÐµÑÐ°ÐµÐŒÐŸÑÑÐž ÑÐµÑÐŒÐžÐœÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="946"><b>search.h</b></Text>
+</th>
+<th width="420">
+<Text id="947">ÐÐ°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ Search ÐŸÐ±ÑÐµÐºÑ searchclass (ÐŸÐ¿ÐžÑÐ°Ðœ Ð²ÑÑÐµ.) </Text>
+</th>
+</tr>
+<tr>
+<th width="120">
+<Text id="948"><b>source.h</b></Text>
+</th>
+<th width="420">
+<Text id="949">ÐÐ°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑÐÐŸÐžÐ³ÑÐµ ÐŸÐ±ÑÐµÐºÑ sourceclass (ÐŸÐ¿ÐžÑÐ°Ðœ Ð²ÑÑÐµ.)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="protocol">
+<Title>
+<Text id="950">ÐÑÐŸÑÐŸÐºÐŸÐ»</Text>
+</Title>
+<Content>
+<Table id="list_of_protocol_calls">
+<Title>
+<Text id="951">Ð¡Ð¿ÐžÑÐŸÐº Ð·Ð°Ð¿ÑÐŸÑÐŸÐ² Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="952"><i>get_protocol_name()</i></Text>
+</th>
+<th width="397">
+<Text id="953">ÐÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ ÐžÐŒÑ ÑÑÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°. ÐÑÐ±ÐŸÑÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ nullproto, corbaproto Ðž z3950proto. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÑÐ°Ð±ÐŸÑÑ ÑÐžÑÑÐµÐŒÑ ÑÑÐ²ÑÑÐ²ÐžÑÐµÐ»ÑÐœÑÐŒÐž Ðº Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ñ ÑÐ°ÑÑÑÐŒÐž, ÑÑÐŸÐ±Ñ ÑÐµÑÐžÑÑ, ÐºÐ°ÐºÐžÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð·Ð°Ð¿ÑÑÑÐžÑÑ ÐœÐ° Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="954"><i>get_collection_list()</i></Text>
+</th>
+<th width="397">
+<Text id="955">ÐÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ ÑÐ¿ÐžÑÐŸÐº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐŸ ÐºÐŸÑÐŸÑÑÑ
+ ÑÑÐŸÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» ÐžÐŒÐµÐµÑ ÑÐ²ÐµÐŽÐµÐœÐžÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="956"><i>has_collection()</i></Text>
+</th>
+<th width="397">
+<Text id="957">ÐÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐžÑÑÐžÐœÑ, ÐµÑÐ»Ðž Ð¿ÑÐŸÑÐŸÐºÐŸÐ» ÐŒÐŸÐ¶ÐµÑ ÑÐ²ÑÐ·Ð°ÑÑÑÑ Ñ ÐœÐ°Ð·Ð²Ð°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹, ÑÐŸ ÐµÑÑÑ ÑÑÐŸ - Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÑÐ¿ÐžÑÐºÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="958"><i>ping()</i></Text>
+</th>
+<th width="397">
+<Text id="959">ÐÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐžÑÑÐžÐœÑ, ÐµÑÐ»Ðž ÑÑÐ¿ÐµÑÐœÐŸ Ð±ÑÐ»Ð° ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÑÐ²ÑÐ·Ñ Ñ ÐœÐ°Ð·Ð²Ð°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹. Ð ÐœÑÐ»ÐµÐ²ÐŸÐŒ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ðµ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ ÐžÐŽÐµÐœÑÐžÑÐœÐŸ <i>has_collection().</i></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="960"><i>get_collectinfo()</i></Text>
+</th>
+<th width="397">
+<Text id="961">ÐÐŸÐ»ÑÑÐ°ÐµÑ ÐŸÐ±ÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž: ÐºÐŸÐ³ÐŽÐ° ÐŸÐœÐ° Ð±ÑÐ»Ð° ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐ°, ÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐŸÐœÐ° ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ðž Ñ.ÐŽ. Ð¢Ð°ÐºÐ¶Ðµ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ   ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž: ÑÐµÐºÑÑ ÐŽÐ»Ñ ÑÑÑÐ°ÐœÐžÑÑ"Ð°ÐªÐŸÐž1 this collection"; ÐžÐºÐŸÐœÐºÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ñ.ÐŽ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="962"><i>get_filterinfo()</i></Text>
+</th>
+<th width="397">
+<Text id="963">ÐÐŸÐ»ÑÑÐ°ÐµÑ ÑÐ¿ÐžÑÐŸÐº Ð²ÑÐµÑ
+ Filters ÐŽÐ»Ñ ÐœÐ°Ð·Ð²Ð°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. get</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="964"><i>get_filteroptions()</i></Text>
+</th>
+<th width="397">
+<Text id="965">ÐÐŸÐ»ÑÑÐ°ÐµÑ Ð²ÑÐµ Ð²Ð°ÑÐžÐ°ÐœÑÑ ÐŽÐ»Ñ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐŸÐ³ÐŸ Filter Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐœÐ°Ð·Ð²Ð°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="966"><i>filter()</i></Text>
+</th>
+<th width="397">
+<Text id="967">ÐÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐžÑÐº Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑ, ÐŽÐ»Ñ ÐŽÐ°ÐœÐœÐŸÐ³ÐŸ ÑÐžÐ¿Ð° ÑÐžÐ»ÑÑÑÐ° Ðž Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž, ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ Ðº ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÑÑÐŸÐ±Ñ Ð²ÐŸÑÐ¿ÑÐŸÐžÐ·Ð²ÐµÑÑÐž ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÑÑÐžÐ»ÑÑÑÐŸÐ²Ð°Ðœ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ°ÐŒÐž ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž. ÐÐŸÐ·Ð²ÑÐ°ÑÐµÐœÐœÑÐµ Ð¿ÐŸÐ»Ñ ÐŽÐ°ÐœÐœÑÑ
+ ÑÐ°ÐºÐ¶Ðµ Ð·Ð°Ð²ÐžÑÑÑ ÐŸÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž: Ð¿ÑÐžÐŒÐµÑÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÑÐ°ÑÑÐŸÑÑ Ð²ÑÑÑÐµÑÐ°ÐµÐŒÐŸÑÑÐž ÑÐµÑÐŒÐžÐœÐ° Ð·Ð°Ð¿ÑÐŸÑÐ° Ðž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="968"><i>get_document()</i></Text>
+</th>
+<th width="397">
+<Text id="969">ÐÐŸÐ»ÑÑÐ°ÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐžÐ»Ðž ÑÐ°Ð·ÐŽÐµÐ» ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="970">Ð¢Ð°Ð±Ð»ÐžÑÐ° <CrossRef target="Table" ref="list_of_protocol_calls"/> Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑ ÑÐ¿ÐžÑÐŸÐº Ð·Ð°Ð¿ÑÐŸÑÐŸÐ² ÑÑÐœÐºÑÐžÐž Ðº Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ñ Ðž ÑÐµÐ·ÑÐŒÐµ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ Ð²Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ. ÐÑÐžÐŒÐµÑÑ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="how_the_conceptual_framework_fits_together"/> ÐŸÑ
+Ð²Ð°ÑÐžÐ»Ðž Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÐžÐ· ÐœÐžÑ
+. Ð€ÑÐœÐºÑÐžÐž, ÐœÐµ ÑÐ¿ÐŸÐŒÑÐœÑÑÑÐµ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ - has_collection (), ping (), get_protocol_name () Ðž get_filteroptions (). ÐÐµÑÐ²ÑÐµ ÐŽÐ²Ðµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÑÑ ÐŸÑÐ²ÐµÑÑ ÐŽÐ°\ÐœÐµÑ ÐœÐ° Ð²ÐŸÐ¿ÑÐŸÑÑ "ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÑÑÐµÑÑÐ²ÑÐµÑ ÐœÐ° ÑÑÐŸÐŒ ÑÐµÑÐ²ÐµÑÐµ? " Ðž "ÑÑÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÑÑÑ? ". ÐŠÐµÐ»Ñ ÐŽÐ²ÑÑ
+ ÐŽÑÑÐ³ÐžÑ
+ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶Ð°ÑÑ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐµÐœÐœÑÐµ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ñ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ Ð°ÑÑ
+ÐžÑÐµÐºÑÑÑÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐ°ÑÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐ° Ð¿ÐŸ ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°ÐŒ, Ð° ÐœÐµ ÑÐŸÐ»ÑÐºÐŸ ÐœÑÐ»ÐµÐ²ÐŸÐ¹ Ð¿ÑÐŸÑÐŸÐºÐŸÐ», Ð±Ð°Ð·ÐžÑÑÑÑÐžÐ¹ÑÑ ÐœÐ° ÐŸÑÐŽÐµÐ»ÑÐœÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÐŒÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ, ÐŸÐ¿ÐžÑÐ°ÐœÐœÐŸÐ¹ Ð·ÐŽÐµÑÑ. ÐÐŽÐœÐ° ÐžÐ· ÐœÐžÑ
+ ÑÐ°Ð·Ð»ÐžÑÐ°ÐµÑ, ÐºÐ°ÐºÐŸÐ¹ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ. ÐÑÑÐ³Ð°Ñ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÑ ÐŸÐ¿ÑÐ°ÑÐžÐ²Ð°ÑÑ ÑÐµÑÐ²ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÑÐŸÐ±Ñ ÐœÐ°Ð¹ÑÐž, ÐºÐ°ÐºÐžÐµ Ð²Ð°ÑÐžÐ°ÐœÑÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑÑÑ, Ðž ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ ÐŽÐžÐœÐ°ÐŒÐžÑÐµÑÐºÐž Ð²ÑÐ±ÐžÑÐ°ÑÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž, ÑÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð²ÑÐµ Ð¿ÑÐµÐžÐŒÑÑÐµÑÑÐ²Ð° ÑÑÐ»ÑÐ³, Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÐµÐŒÑÑ
+ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐžÐŒ ÑÐµÑÐ²ÐµÑÐŸÐŒ.</Text>
+<Figure id="null_protocol_api">
+<Title>
+<Text id="971">ÐÑÐ»ÐµÐ²ÐŸÐ¹ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» API (ÑÐŸÐºÑÐ°ÑÐµÐœÐœÑÐ¹ Ð²Ð°ÑÐžÐ°ÐœÑ)</Text>
+</Title>
+<CodeLine>class nullproto : public recptproto {</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   virtual text_t get_protocol_name ();</CodeLine>
+<CodeLine>   virtual void get_collection_list (text_tarray &amp;collist,</CodeLine>
+<CodeLine>                comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void has_collection (const text_t &amp;collection,</CodeLine>
+<CodeLine>                bool &amp;hascollection,</CodeLine>
+<CodeLine>                comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void ping (const text_t &amp;collection,</CodeLine>
+<CodeLine>                  bool &amp;wassuccess,</CodeLine>
+<CodeLine>                  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_collectinfo (const text_t &amp;collection,</CodeLine>
+<CodeLine>                  ColInfoResponse_t &amp;collectinfo,</CodeLine>
+<CodeLine>                  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_filterinfo (const text_t &amp;collection,</CodeLine>
+<CodeLine>                   InfoFiltersResponse_t &amp;response,</CodeLine>
+<CodeLine>                   comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_filteroptions (const text_t &amp;collection,</CodeLine>
+<CodeLine>                   const InfoFilterOptionsRequest_t &amp;request,</CodeLine>
+<CodeLine>                   InfoFilterOptionsResponse_t &amp;response,</CodeLine>
+<CodeLine>                   comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void filter (const text_t &amp;collection,</CodeLine>
+<CodeLine>                   FilterRequest_t &amp;request,</CodeLine>
+<CodeLine>                   FilterResponse_t &amp;response,</CodeLine>
+<CodeLine>                   comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_document (const text_t &amp;collection,</CodeLine>
+<CodeLine>                  const DocumentRequest_t &amp;request,</CodeLine>
+<CodeLine>                  DocumentResponse_t &amp;response,</CodeLine>
+<CodeLine>                  comerror_t &amp;err, ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="972">Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="null_protocol_api"/> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ API ÐŽÐ»Ñ ÐœÑÐ»ÐµÐ²ÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°. ÐÐŸÐŒÐŒÐµÐœÑÐ°ÑÐžÐž Ðž ÐœÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÑÑÐž ÐœÐžÐ·ÐºÐŸÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ Ð±ÑÐ»Ðž ÐŸÐ¿ÑÑÐµÐœÑ (ÑÐŒ. ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ ÑÐ°Ð¹Ð» recpt/nullproto.h ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÑÑÐµÐ¹).</Text>
+<Text id="973">Ð­ÑÐŸÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°Ð»ÑÑ ÐŸÑ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ° recptproto. ÐÐžÑÑÑÐ°Ð»ÑÐœÐŸÐµ ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÑÐ°Ðº, ÑÑÐŸÐ±Ñ Ð±ÐŸÐ»ÑÑÐµ, ÑÐµÐŒ ÐŸÐŽÐžÐœ ÑÐžÐ¿ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°, ÐŽÐ°Ð¶Ðµ ÐœÐµ Ð·Ð°ÐŽÑÐŒÐ°ÐœÐœÐŸÐ³ÐŸ, Ð²ÑÐµ Ð¶Ðµ ÐŒÐŸÐ³ Ð»ÐµÐ³ÐºÐŸ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑÑÑ ÐŸÑÑÐ°Ð»ÑÐœÐŸÐ¹ ÑÐ°ÑÑÑÑ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ.</Text>
+<Text id="974">ÐÐ° ÐžÑÐºÐ»ÑÑÐµÐœÐžÐµÐŒ get_protocol_name (), ÐºÐŸÑÐŸÑÑÐ¹ ÐœÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ Ðž Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ ÐžÐŒÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° ÐºÐ°Ðº ÑÑÑÐŸÐºÑ ÑÐµÐºÑÑÐ° Unicode, Ð²ÑÐµ ÑÑÐœÐºÑÐžÐž Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° Ð²ÐºÐ»ÑÑÐ°ÑÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑ ÐŸÑÐžÐ±ÐºÐž Ðž Ð²ÑÑ
+ÐŸÐŽÐœÐŸÐ¹ Ð¿ÐŸÑÐŸÐº, ÐºÐ°Ðº Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐµ ÐŽÐ²Ð° Ð°ÑÐ³ÑÐŒÐµÐœÑÐ°. ÐÐ°ÑÐ°ÐŒÐµÑÑ ÐŸÑÐžÐ±ÐºÐž ÐŽÐµÐ»Ð°ÐµÑ Ð·Ð°Ð¿ÐžÑÑ Ð»ÑÐ±ÑÑ
+ ÐŸÑÐžÐ±ÐŸÐº, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÑÑ Ð² Ñ
+ÐŸÐŽÐµ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ Ð·Ð°Ð¿ÑÐŸÑÐ° Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°, Ð° Ð²ÑÑ
+ÐŸÐŽÐœÐŸÐ¹ Ð¿ÐŸÑÐŸÐº ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐž ÑÐµÐ»Ðž. Ð€ÑÐœÐºÑÐžÐž ÐŸÑÐœÐŸÑÑÑÑÑ Ðº ÑÐžÐ¿Ñ void - ÐŸÐœÐž ÐœÐµ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐºÐ°Ðº ÐžÑ
+ Ð·Ð°ÐºÐ»ÑÑÐžÑÐµÐ»ÑÐœÐ°Ñ ÐžÐœÑÑÑÑÐºÑÐžÑ, ÐœÐŸ Ð²ÐŒÐµÑÑÐŸ ÑÑÐŸÐ³ÐŸ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÑÑ ÐŽÐ°ÐœÐœÑÐµ ÑÐµÑÐµÐ· ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÐŒÑÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÑÐžÐ¿Ð° ÑÐ¶Ðµ Ð²Ð²ÐµÐŽÐµÐœÐœÐŸÐ³ÐŸ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ° ÐŸÑÐžÐ±ÐºÐž. Ð ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÑÐ·ÑÐºÐ°Ñ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐ°ÐºÐžÐµ Ð¿ÐŸÐŽÐ¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð±ÑÐ»Ðž Ð±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ ÐºÐ°Ðº Ð¿ÑÐŸÑÐµÐŽÑÑÑ, Ð° ÐœÐµ ÑÑÐœÐºÑÐžÐž, ÐœÐŸ C++ ÐœÐµ ÐŽÐµÐ»Ð°ÐµÑ ÐœÐžÐºÐ°ÐºÐŸÐ³ÐŸ ÑÐžÐœÑÐ°ÐºÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÑÐ°Ð·Ð»ÐžÑÐžÑ.</Text>
+<Text id="975">ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÑÑÐœÐºÑÐžÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐžÐŒÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐºÐ°Ðº Ð¿Ð°ÑÐ°ÐŒÐµÑÑ. Ð¢ÑÐž ÑÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÑ, get_filteroptions (), filterQ, Ðž get_document (), ÑÐ»ÐµÐŽÑÑÑ Ð·Ð° ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµÐŒ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ° Request Ðž Ð¿ÐŸÐ»ÑÑÐµÐœÐžÐµÐŒ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² Ð² Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐµ Response.</Text>
+</Content>
+</Section>
+<Section id="receptionist">
+<Title>
+<Text id="976">Ð ÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ</Text>
+</Title>
+<Content>
+<Text id="977">ÐÐ°ÐºÐ»ÑÑÐžÑÐµÐ»ÑÐœÑÐ¹ ÑÑÐŸÐ²ÐµÐœÑ ÐºÐŸÐœÑÐµÐ¿ÑÑÐ°Ð»ÑÐœÐŸÐ¹ ÐŒÐŸÐŽÐµÐ»Ðž - ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ. ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÑ Ð±ÑÐŽÑÑ Ð¿ÑÐŸÐ°ÐœÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÑ, ÐŸÑÐœÐŸÐ²ÐœÐ°Ñ ÐŽÐµÑÑÐµÐ»ÑÐœÐŸÑÑÑ Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑ ÐœÐ° Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ Action, Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÐŒÑÑ ÐŸÐ±ÑÐµÐºÑÐ°ÐŒÐž Format Ðž Macro Language. ÐÐœÐž ÐŸÐ¿ÐžÑÐ°ÐœÑ ÐœÐžÐ¶Ðµ. Ð¥ÐŸÑÑ ÐŸÐœÐž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÐºÐ°Ðº ÐŸÐ±ÑÐµÐºÑÑ Ð² ÐºÐŸÐœÑÐµÐ¿ÑÑÐ°Ð»ÑÐœÐŸÐ¹ ÑÑÑÑÐºÑÑÑÐµ, ÐŸÐ±ÑÐµÐºÑÑ Format Ðž Macro Language - ÐœÐµ ÑÐŸÐ²ÑÐµÐŒ ÑÐ²Ð»ÑÑÑÑÑ ÐŸÐ±ÑÐµÐºÑÐ°ÐŒÐž Ñ ÑÐŸÑÐºÐž Ð·ÑÐµÐœÐžÑ C++. Ð ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸÑÑÐž, Format - ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÑÑÑÐºÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+ Ñ ÐœÐ°Ð±ÐŸÑÐŸÐŒ ÑÑÐœÐºÑÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÐŸÐ¿ÐµÑÐžÑÑÑÑ ÐžÐŒÐž, Ð° ÐŸÐ±ÑÐµÐºÑ Macro Language ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°Ðœ Ð²ÐŸÐºÑÑÐ³ display class, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœ Ð² lib/display.h, Ñ Ð¿ÐŸÑÐŸÐºÐŸÐ²ÐŸÐ¹ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐŸÐ¹ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÐž ÐŸÑ lib/gsdlunicode.h.</Text>
+<Subsection id="actions">
+<Title>
+<Text id="978">ÐÐµÐ¹ÑÑÐ²ÐžÑ</Text>
+</Title>
+<Content>
+<Table id="actions_in_greenstone">
+<Title>
+<Text id="979">Actions Ð² ÑÐžÑÑÐµÐŒÐµ Greenstone</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="980"><i>action</i></Text>
+</th>
+<th width="397">
+<Text id="981">ÐÐ°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ ÐŽÐ»Ñ Ð²ÐžÑÑÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="982"><i>authenaction</i></Text>
+</th>
+<th width="397">
+<Text id="983">ÐÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÐž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ: Ð·Ð°Ð¿ÑÐŸÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŸÑÐœÐŸÑÐžÑÐµÐ»ÑÐœÐŸ Ð¿Ð°ÑÐŸÐ»Ñ, ÐµÑÐ»Ðž ÐœÐµ Ð±ÑÐ» Ð²Ð²ÐµÐŽÐµÐœ; Ð¿ÑÐŸÐ²ÐµÑÐºÐ° Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸÑÑÐž; Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð¿ÐŸÐ²ÑÐŸÑÐœÐŸÐ³ÐŸ Ð²Ñ
+ÐŸÐŽÐ°, ÐµÑÐ»Ðž ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸÐµ Ð²ÑÐµÐŒÑ ÐžÑÑÐµÐºÐ»ÐŸ ÐŒÐµÐ¶ÐŽÑ ÐŽÐŸÑÑÑÐ¿Ð°ÐŒÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="984"><i>collectoraction</i></Text>
+</th>
+<th width="397">
+<Text id="985">ÐÐµÐœÐµÑÐžÑÑÐµÑ ÑÑÑÐ°ÐœÐžÑÑ ÐŽÐ»Ñ Collector (Ð¡ÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="986"><i>documentaction</i></Text>
+</th>
+<th width="397">
+<Text id="987">ÐÑÑÑÐºÐžÐ²Ð°ÐµÑ   ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÑÐ°Ð·ÐŽÐµÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÑÐ°ÑÑÐž ÐžÐµÑÐ°ÑÑ
+ÐžÐž ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž ÐžÐ»Ðž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŽÐ»Ñ ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÑ .</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="988"><i>extlinkaction</i></Text>
+</th>
+<th width="397">
+<Text id="989">ÐÐµÑÐµÐœÐŸÑÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ Ðº   URL, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ²Ð»ÑÐµÑÑÑ Ð²ÐœÐµÑÐœÐžÐŒ ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, no-Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÑÐœÐ°ÑÐ°Ð»Ð° Ð³ÐµÐœÐµÑÐžÑÑÑ Ð°Ð²Ð°ÑÐžÐ¹ÐœÑÑ ÑÑÑÐ°ÐœÐžÑÑ (Ð¿ÑÐŸÐŽÐžÐºÑÐŸÐ²Ð°ÐœÐœÑÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐ°ÐŒÐž Preferences).</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="990"><i>pageaction</i></Text>
+</th>
+<th width="397">
+<Text id="991">ÐÐµÐœÐµÑÐžÑÑÐµÑ ÑÑÑÐ°ÐœÐžÑÑ Ð²ÐŒÐµÑÑÐµ Ñ ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐºÐŸÐŒ. pingaction   ÐÑÑÑÐœÑÐµÑ, ÐžÐœÑÐµÑÐ°ÐºÑÐžÐ²ÐœÐ° Ð»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. queryaction   ÐÑÐ¿ÐŸÐ»ÐœÑÐµÑ Ð¿ÐŸÐžÑÐº.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="992"><i>pingaction</i></Text>
+</th>
+<th width="397">
+<Text id="993">Checks to see whether a collection is online.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="994"><i>queryaction</i></Text>
+</th>
+<th width="397">
+<Text id="995">Performs a search.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="996"><i>statusaction</i></Text>
+</th>
+<th width="397">
+<Text id="997">ÐÐµÐœÐµÑÐžÑÑÐµÑ ÑÑÑÐ°ÐœÐžÑÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="998"><i>tipaction</i></Text>
+</th>
+<th width="397">
+<Text id="999">ÐÑÐŽÐ°ÐµÑ ÑÐ»ÑÑÐ°Ð¹ÐœÑÐ¹ ÑÐŸÐ²ÐµÑ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1000"><i>usersaction</i></Text>
+</th>
+<th width="397">
+<Text id="1001">ÐÐŸÐ±Ð°Ð²Ð»ÑÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ, ÑÐŽÐ°Ð»ÐµÐœÐžÐµ Ðž ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐžÐŒ ÐŽÐŸÑÑÑÐ¿ÐŸÐŒ.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="1002">Greenstone Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ ÐŸÐŽÐžÐœÐœÐ°ÐŽÑÐ°ÑÑ ÐŽÐµÐ¹ÑÑÐ²ÐžÐ¹, ÑÐ²ÐµÐŽÐµÐœÐœÑÑ
+ Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="actions_in_greenstone"/>.</Text>
+<Figure id="using_the_cgiargsinfoclass_from_pageactioncpp" class="withLineNumber">
+<Title>
+<Text id="1003">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ cgiargsinfoclass ÐžÐ· pageaction.cpp</Text>
+</Title>
+<CodeLine>cgiarginfo arg_ainfo;</CodeLine>
+<CodeLine>arg_ainfo.shortname = " a " ;</CodeLine>
+<CodeLine>arg_ainfo.longname = " action" ;</CodeLine>
+<CodeLine>arg_ainfo.multiplechar = true;</CodeLine>
+<CodeLine>arg_ainfo.argdefault = " p" ;</CodeLine>
+<CodeLine>arg_ainfo.defaultstatus = cgiarginfo::weak;</CodeLine>
+<CodeLine>arg_ainfo.savedarginfo = cgiarginfo::must;</CodeLine>
+<CodeLine>argsinfo.addarginfo (NULL, arg_ainfo);</CodeLine>
+<CodeLine/>
+<CodeLine>arg_ainfo.shortname = " p" ;</CodeLine>
+<CodeLine>arg_ainfo.longname = " page" ;</CodeLine>
+<CodeLine>arg_ainfo.multiplechar = true;</CodeLine>
+<CodeLine>arg_ainfo.argdefault = " home" ;</CodeLine>
+<CodeLine>arg_ainfo.defaultstatus = cgiarginfo::weak;</CodeLine>
+<CodeLine>arg_ainfo.savedarginfo = cgiarginfo::must;</CodeLine>
+<CodeLine>argsinfo.addarginfo (NULL, arg_ainfo);</CodeLine>
+</Figure>
+<Text id="1004">CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÑ ÑÐ²Ð»ÑÑÑÑÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÐŒÐž ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐŒÐž ÑÐŸÑÐŒÐ°Ð»ÑÐœÐŸ ÐŸÐ±ÑÑÐ²Ð»ÐµÐœÐœÑÐŒÐž Ð² ÑÑÐœÐºÑÐžÐž ÐºÐŸÐœÑÑÑÑÐºÑÐŸÑÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÐžÐŒÐž cgiarginfo (ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ Ð² recpt/cgiargs.h). Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð²ÑÐ±ÐŸÑÐºÑ ÐžÐ· pageaction ÑÑÐœÐºÑÐžÐž ÐºÐŸÐœÑÑÑÑÐºÑÐŸÑÐ°, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÑÐ°Ð·ÐŒÐµÑ Ðž ÑÐ²ÐŸÐ¹ÑÑÐ²Ð° CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐ² Ð° Ðž Ñ.</Text>
+<Text id="1005">ÐÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° ÐºÐŸÐœÑÑÑÑÐºÑÐŸÑ ÐŽÐŸÐ»Ð¶ÐµÐœ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÐµÐ³ÐŸ ÐºÑÐ°ÑÐºÐŸÐµ ÐžÐŒÑ (ÑÑÑÐŸÐºÐž 2 Ðž 10), ÐºÐŸÑÐŸÑÐŸÐµ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ ÑÐ²Ð»ÑÐµÑÑÑ ÐžÐŒÐµÐœÐµÐŒ CGI-Ð¿ÐµÑÐµÐŒÐµÐœÐœÐŸÐ¹; Ð¿ÐŸÐ»ÐœÐŸÐµ ÐžÐŒÑ (ÑÑÑÐŸÐºÐž 3 Ðž 11), ÐºÐŸÑÐŸÑÐŸÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ, ÑÑÐŸÐ±Ñ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÑÑ Ð±ÐŸÐ»ÐµÐµ Ð·ÐœÐ°ÑÐžÐŒÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ; Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑ Ð»Ðž ÑÑÐŸ ÐµÐŽÐžÐœÑÑÐ²ÐµÐœÐœÐŸÐµ ÐžÐ»Ðž ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐµÐœÐœÐŸÐµ ÑÐžÐŒÐ²ÐŸÐ»ÑÐœÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ (ÑÑÑÐŸÐºÐž 4 Ðž 12); Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ (ÑÑÑÐŸÐºÐž 5 Ðž 13); ÑÑÐŸ ÑÐ»ÑÑÐ°ÐµÑÑÑ, ÐºÐŸÐ³ÐŽÐ° Ð·Ð°ÐŽÐ°ÐœÐŸ Ð±ÐŸÐ»ÑÑÐµ ÑÐµÐŒ ÐŸÐŽÐœÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ (ÑÑÑÐŸÐºÐž 6 Ðž 14) (ÑÐ°Ðº ÐºÐ°Ðº Ð·ÐœÐ°ÑÐµÐœÐžÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐŒÐŸÐ³ÑÑ ÑÐ°ÐºÐ¶Ðµ Ð±ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ Ð² ÑÐ°Ð¹Ð»Ð°Ñ
+ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž); ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸ Ð»Ðž Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑÑÑ Ð² ÐºÐŸÐœÑÐµ ÑÑÐŸÐ³ÐŸ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ (ÑÑÑÐŸÐºÐž 7 Ðž 15).</Text>
+<Text id="1006">Ð¢Ð°Ðº ÐºÐ°Ðº ÑÑÐŸ Ð²ÑÑÑÐŸÐµÐœÐŸ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, web-ÑÑÑÐ°ÐœÐžÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÐŽÐµÑÐ°Ð»ÐžÐ·ÐžÑÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž. Statusaction Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑ ÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ²ÐžÐŽÐµÑÑ ÑÑÐŸ, Ð²Ð²ÐµÐŽÑ URL ÑÑÑÐ°ÐœÐžÑÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ Greenstone.</Text>
+<Text id="1007">ÐÐ²ÐµÐœÐ°ÐŽÑÐ°ÑÑ ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÑ
+ ÐŽÐµÐ¹ÑÑÐ²ÐžÐ¹ ÑÐŸÐ·ÐŽÐ°ÐœÑ Ð² main(), ÑÑÐœÐºÑÐžÑ Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ ÐŽÐ»Ñ Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÐŒÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ library, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ ÐºÐŸÑÐŸÑÐŸÐ¹ ÐŽÐ°ÐµÑÑÑ Ð² recpt/librarymain.cpp, ÑÐ°ÐŒ Ð¶Ðµ, Ð³ÐŽÐµ Ð±ÑÐ» ÑÐŸÐ·ÐŽÐ°Ðœ ÐŸÐ±ÑÐµÐºÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐ° (ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ Ð² recpt/receptionist.cpp). ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸÑÑÑ Ð·Ð° Ð²ÑÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ Ð¿ÐµÑÐµÐŽÐ°ÑÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÐžÑ
+, ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°Ñ ÐºÐ°Ðº Ð¿ÐŸÐ»Ðµ ÐŽÐ°ÐœÐœÑÑ
+ Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÐŸÐ³ÐŸ ÐŒÐ°ÑÑÐžÐ²Ð° Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ° Action, ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐ³ÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµÐŒ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ.</Text>
+<Figure id="action_base_class_api">
+<Title>
+<Text id="1008">Action Ð±Ð°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ API</Text>
+</Title>
+<CodeLine>class action {</CodeLine>
+<CodeLine>protected:</CodeLine>
+<CodeLine>   cgiargsinfoclass argsinfo;</CodeLine>
+<CodeLine>   text_t gsdlhome;</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   action ();</CodeLine>
+<CodeLine>   virtual ~action ();</CodeLine>
+<CodeLine>   virtual void configure (const text_t &amp;key, const text_tarray &amp;cfgline);</CodeLine>
+<CodeLine>   virtual bool init (ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual text_t get_action_name ();</CodeLine>
+<CodeLine>   cgiargsinfoclass getargsinfo ();</CodeLine>
+<CodeLine>   virtual bool check_cgiargs (cgiargsinfoclass &amp;argsinfo,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args, ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool check_external_cgiargs (cgiargsinfoclass &amp;argsinfo,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              outconvertclass &amp;outconvert,</CodeLine>
+<CodeLine>              const text_t &amp;saveconf,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void get_cgihead_info (cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              response_t &amp;response,</CodeLine>
+<CodeLine>              text_t &amp;response_data,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool uses_display (cgiargsclass &amp;args);</CodeLine>
+<CodeLine>   virtual void define_internal_macros (displayclass &amp;disp,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual void define_external_macros (displayclass &amp;disp,</CodeLine>
+<CodeLine>              cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>   virtual bool do_action (cgiargsclass &amp;args,</CodeLine>
+<CodeLine>              recptprotolistclass *protos,</CodeLine>
+<CodeLine>              browsermapclass *browsers,</CodeLine>
+<CodeLine>              displayclass &amp;disp,</CodeLine>
+<CodeLine>              outconvertclass &amp;outconvert,</CodeLine>
+<CodeLine>              ostream &amp;textout,</CodeLine>
+<CodeLine>              ostream &amp;logout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1009">Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="action_base_class_api"/> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ API ÐŽÐ»Ñ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ° Action. ÐÑÐž Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐž ÐŽÐµÐ¹ÑÑÐ²ÐžÑ, receptionist (ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ) Ð²ÑÐ·ÑÐ²Ð°ÐµÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÑÐœÐºÑÐžÐ¹, ÐœÐ°ÑÐžÐœÐ°Ñ Ñ check_cgiargs (). ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ Ð¿ÐŸÐŒÐŸÐ³Ð°ÑÑ Ð¿ÑÐŸÐ²ÐµÑÐžÑÑ, ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ, Ðž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ Ðž ÐŒÐ°ÐºÑÐŸÑÑ; Ð² ÑÐŸ Ð²ÑÐµÐŒÑ ÐºÐ°Ðº dojzction () ÑÐ°ÐºÑÐžÑÐµÑÐºÐž Ð³ÐµÐœÐµÑÐžÑÑÐµÑ ÑÑÑÐ°ÐœÐžÑÑ Ð²ÑÐ²ÐŸÐŽÐ°. Ð ÑÐ°ÑÑÐœÐŸÑÑÐž, ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÐ±ÑÐµÐºÑ ÐœÐµ ÐžÐŒÐµÐµÑ ÐœÐžÐºÐ°ÐºÐŸÐ³ÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÐŽÐ»Ñ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐŸÐ¹ ÑÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÐ°, ÑÑÐŸ Ð¿ÑÐŸÑ
+ÐŸÐŽÐžÑ ÑÐµÑÐµÐ· ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ°, ÐºÐŸÑÐŸÑÐŸÐµ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÐµÑ Ð·Ð°ÐŽÐ°ÐœÐœÐŸÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Ð¿ÐŸÐ²ÐµÐŽÐµÐœÐžÐµ.</Text>
+<Text id="1010">ÐÐ±ÑÑÑÐœÐµÐœÐžÑ ÑÑÐœÐºÑÐžÐ¹-ÑÐ»ÐµÐœÐŸÐ² ÑÐ»ÐµÐŽÑÑÑÐžÐµ.</Text>
+<BulletList>
+<Bullet>
+<Text id="1011"><i>get_action_name()</i>  Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµ CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐ°, ÐºÐŸÑÐŸÑÐŸÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÑÑÐŸ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ. ÐÐŒÑ ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð±ÑÑÑ ÐºÐŸÑÐŸÑÐºÐžÐŒ, ÐœÐŸ Ð±ÐŸÐ»ÐµÐµ ÐŸÐŽÐœÐŸÐ³ÐŸ ÑÐžÐŒÐ²ÐŸÐ»Ð°.</Text>
+</Bullet>
+<Bullet>
+<Text id="1012"><i>check_cgiargs()</i> Ð²ÑÐ·ÑÐ²Ð°ÐµÑÑÑ Ð¿ÑÐµÐ¶ÐŽÐµ get_cgihead_info(),deflne_external_macros() Ðž do_action (). ÐÑÐ»Ðž ÐŸÑÐžÐ±ÐºÐ° ÐœÐ°Ð¹ÐŽÐµÐœÐ°, ÑÐŸÐŸÐ±ÑÐµÐœÐžÐµ ÐžÐœÑÐŸÑÐŒÐžÑÑÐµÑ ÐŸ Ð²ÑÑ
+ÐŸÐŽÐµ ÐžÐ· ÑÐžÑÑÐµÐŒÑ; ÐµÑÐ»Ðž ÑÑÐŸ ÑÐµÑÑÐµÐ·ÐœÐŸ, ÑÑÐœÐºÑÐžÑ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµ false Ðž ÐœÐžÐºÐ°ÐºÐ°Ñ Ð·Ð°Ð³ÑÑÐ·ÐºÐ° ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÑÑÑÐ°ÐœÐžÑÑ ÐœÐµ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="1013"><i>check_external_cgiargs()</i> Ð²ÑÐ·ÑÐ²Ð°ÐµÑÑÑ Ð¿ÐŸÑÐ»Ðµ check_cgiargs () ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÐŽÐµÐ¹ÑÑÐ²ÐžÐ¹. ÐÐœÐ° Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐ° ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐŸÑÐŒÐµÐœÐžÑÑ ÐœÐµÐºÐŸÑÐŸÑÐŸÐµ ÐœÐŸÑÐŒÐ°Ð»ÑÐœÐŸÐµ Ð¿ÐŸÐ²ÐµÐŽÐµÐœÐžÐµ, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ Ð²ÐŸÑÐ¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÑ ÑÑÑÐ°ÐœÐžÑÑ Ð²Ñ
+ÐŸÐŽÐ° Ð² ÑÐžÑÑÐµÐŒÑ, ÐºÐŸÐ³ÐŽÐ° ÑÑÐµÐ±ÑÐµÑÑ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="1014"><i>get_cgihead_info()</i> ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐµ CGI. ÐÑÐ»Ðž response (ÐŸÑÐ²ÐµÑ) ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ, ÐºÐ°Ðº location (ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐµ), ÑÐŸ response_data ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð¿ÐµÑÐµÐ°ÐŽÑÐµÑÐ°ÑÐžÑ. ÐÑÐ»Ðž response  ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ, ÐºÐ°Ðº content (ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ), ÑÐŸ response_data ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÐžÐ¿ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="1015"><i>uses_display()</i> Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ true, ÐµÑÐ»Ðž displayclass ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒ, ÐŽÐ»Ñ Ð²ÑÐ²ÐŸÐŽÐ° ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÑÑÑÐ°ÐœÐžÑÑ (Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ).</Text>
+</Bullet>
+<Bullet>
+<Text id="1016"><i>define_internal_macros()</i> ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ Ð²ÑÐµ ÐŒÐ°ÐºÑÐŸÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÑÐ²ÑÐ·Ð°ÐœÑ ÑÐŸ ÑÑÑÐ°ÐœÐžÑÐ°ÐŒÐž, ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐŒÐž ÑÑÐžÐŒ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµÐŒ.</Text>
+</Bullet>
+<Bullet>
+<Text id="1017"><i>define_external_macros()</i> ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ Ð²ÑÐµ ÐŒÐ°ÐºÑÐŸÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³Ð»Ðž Ð±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ ÐŽÑÑÐ³ÐžÐŒÐž ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐŒÐž ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÑÑÑÐ°ÐœÐžÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="1018"><i>do_action()</i> Ð³ÐµÐœÐµÑÐžÑÑÐµÑ ÑÑÑÐ°ÐœÐžÑÑ Ð²ÑÐ²ÐŸÐŽÐ° ÐŸÐ±ÑÑÐœÐŸ Ð² Ð¿ÐŸÑÐŸÐºÐµ ÐŸÐ±ÑÐµÐºÑÐ° ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐºÐ° display Ðž Ð²ÑÐ²ÐŸÐŽÐžÑ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÐµ ÐŸÐ±ÑÐµÐºÑÐ° textout. ÐÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµ false, ÐµÑÐ»Ðž Ð¿ÑÐŸÐžÐ·ÐŸÑÐ»Ð° ÐŸÑÐžÐ±ÐºÐ°, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÑÐµÐŽÐŸÑÐ²ÑÐ°ÑÐžÐ»Ð° ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ ÐºÐ°ÐºÐŸÐ³ÐŸ-ÐœÐžÐ±ÑÐŽÑ Ð²ÑÐ²ÐŸÐŽÐ°.</Text>
+</Bullet>
+</BulletList>
+<Text id="1019">Ð ÐœÐ°ÑÐ°Ð»Ðµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÐºÐ»Ð°ÑÑÐ° argsinfo - ÑÑÐŸ Ð·Ð°ÑÐžÑÐµÐœÐœÐŸÐµ Ð¿ÐŸÐ»Ðµ ÐŽÐ°ÐœÐœÑÑ
+ (ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐµ Ð² Ð²ÑÐ±ÐŸÑÐºÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÑÐŒ.ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/>), ÐºÐŸÑÐŸÑÐŸÐµ Ñ
+ÑÐ°ÐœÐžÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐ°, ÑÐºÐ°Ð·Ð°ÐœÐœÑÑ Ð² ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐ¹ ÑÑÐœÐºÑÐžÐž ÐºÐŸÐœÑÑÑÑÐºÑÐŸÑÐ° Action. ÐÑÑÐ³ÐŸÐµ Ð¿ÐŸÐ»Ðµ ÐŽÐ°ÐœÐœÑÑ
+, gsdlhome, ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð·Ð°Ð¿ÐžÑÑ GSDLHOME ÐŽÐ»Ñ ÑÐŽÐŸÐ±ÐœÐŸÐ³ÐŸ ÐŽÐŸÑÑÑÐ¿Ð°<FootnoteRef id="4"/>. ÐÐ±ÑÐµÐºÑ ÑÐ°ÐºÐ¶Ðµ Ð²ÐºÐ»ÑÑÐ°ÐµÑ conflgure() Ðž init () Ñ ÑÐµÐ»ÑÑ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž.</Text>
+</Content>
+</Subsection>
+<Subsection id="formatting">
+<Title>
+<Text id="1020">Ð€ÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</Title>
+<Content>
+<Figure id="core_data_structures_in_format">
+<Title>
+<Text id="1021">ÐÑÐœÐŸÐ²ÐœÑÐµ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+ Ð² Format</Text>
+</Title>
+<CodeLine>enum command_t {comIf, comOr, comMeta, comText, comLink, comEndLink,</CodeLine>
+<CodeLine>         comNum, comIcon, comDoc,</CodeLine>
+<CodeLine>         comHighlight, comEndHighlight};</CodeLine>
+<CodeLine>enum pcommand_t {pNone, pImmediate, pTop, pAll};</CodeLine>
+<CodeLine>enum dcommand_t {dMeta, dText};</CodeLine>
+<CodeLine>enum mcommand_t {mNone, mCgiSafe};</CodeLine>
+<CodeLine>struct metadata_t {</CodeLine>
+<CodeLine>   void clear();</CodeLine>
+<CodeLine>   metadata_t () {clear();}</CodeLine>
+<CodeLine>   text_t metaname;</CodeLine>
+<CodeLine>   mcommand_t metacommand;</CodeLine>
+<CodeLine>   pcommand_t parentcommand;</CodeLine>
+<CodeLine>   text_t parentoptions;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>// The decision component of an {If}{decision,true-text,false-text}</CodeLine>
+<CodeLine>// formatstring. The decision can be based on metadata or on text;</CodeLine>
+<CodeLine>// normally that text would be a macro like</CodeLine>
+<CodeLine>// _cgiargmode_.</CodeLine>
+<CodeLine>struct decision_t {</CodeLine>
+<CodeLine>   void clear();</CodeLine>
+<CodeLine>   decision_t () {clear();}</CodeLine>
+<CodeLine>   dcommand_t command;</CodeLine>
+<CodeLine>   metadata_t meta;</CodeLine>
+<CodeLine>   text_t text;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine>struct format_t {</CodeLine>
+<CodeLine>   void clear();</CodeLine>
+<CodeLine>   format_t () {clear();}</CodeLine>
+<CodeLine>   command_t command;</CodeLine>
+<CodeLine>   decision_t decision;</CodeLine>
+<CodeLine>   text_t text;</CodeLine>
+<CodeLine>   metadata_t meta;</CodeLine>
+<CodeLine>   format_t *nextptr;</CodeLine>
+<CodeLine>   format_t *ifptr;</CodeLine>
+<CodeLine>   format_t *elseptr;</CodeLine>
+<CodeLine>   format_t *orptr;</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1022">Ð¥ÐŸÑÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="greenstone_runtime_system"/> ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐŸ ÐºÐ°Ðº ÐŸÑÐŽÐµÐ»ÑÐœÑÐ¹ ÐŸÐ±ÑÐµÐºÑ, Ð² ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸÑÑÐž ÐŸÐœÐŸ ÑÐŸÑÑÐ°Ð²Ð»ÑÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÑÑÑÐºÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÑÑÐœÐºÑÐžÐ¹. ÐÐœÐž ÑÐŸÐ±ÑÐ°ÐœÑ Ð²ÐŒÐµÑÑÐµ Ð¿ÐŸÐŽ ÑÐ°Ð¹Ð»ÐŸÐŒ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° recpt/formattools.h. ÐÑÐœÐŸÐ²ÐœÑÐµ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="core_data_structures_in_format"/>.</Text>
+<Figure id="data_structures_built_for_sample_format_statement">
+<Title>
+<Text id="1023">Ð¡ÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+, ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÐŽÐ»Ñ Ð²ÑÐ±ÐŸÑÐºÐž ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÐ° /ormutf</Text>
+</Title>
+<File width="395" height="152" url="images/Dev_Fig_090.png"/>
+</Figure>
+<Text id="1024">Ð­ÑÐŸÑ Ð¿ÑÐŸÑÐµÑÑ Ð»ÑÑÑÐµ Ð²ÑÐµÐ³ÐŸ ÐŸÐ±ÑÑÑÐœÐžÑÑ ÐœÐ° Ð¿ÑÐžÐŒÐµÑÐµ. ÐÐŸÐ³ÐŽÐ° ÐŸÐ¿ÐµÑÐ°ÑÐŸÑ Ð·Ð°ÐŽÐ°ÐœÐžÑ ÑÐŸÑÐŒÐ°ÑÐ°</Text>
+<CodeLine>format CL1Vlist</CodeLine>
+<Text id="1025" type="code">"[link][Title]{If}{[Creator], by [Creator]}[/link]} "</Text>
+<Text id="1026">ÑÐžÑÐ°ÐµÑÑÑ ÐžÐ· ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐŸÐœ Ð°ÐœÐ°Ð»ÐžÐ·ÐžÑÑÐµÑÑÑ ÑÑÐœÐºÑÐžÑÐŒÐž Ð² formattools.cpp Ðž ÑÐŸÑÐŒÐžÑÑÐµÑ ÑÐ²ÑÐ·Ð°ÐœÐœÑÐµ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÑÐµ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="data_structures_built_for_sample_format_statement"/>.</Text>
+<Text id="1027">ÐÐœÐ°ÑÐµÐœÐžÐµ ÐŽÐ»Ñ gsdlhome ÐžÑÑ
+ÐŸÐŽÐžÑ ÐžÐ· gsdlsite.cfg, ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐœÐŸÐ³ÐŸ Ð² ÑÐŸÐŒ Ð¶Ðµ ÑÐ°ÐŒÐŸÐŒ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ðµ, ÑÑÐŸ Ðž CGI-Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÐŒÐ°Ñ library, ÑÐŸÐ³ÐŽÐ° ÐºÐ°Ðº GSDLHOME ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ Ð·Ð°Ð¿ÑÑÐºÐŸÐŒ ÑÐºÑÐžÐ¿ÑÐ° setup, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ Ðº ÐŽÑÑÐ³ÐŸÐŒÑ ÑÐ°Ð¹Ð»Ñ, ÑÐ°Ðº ÐºÐ°Ðº ÑÐµÑ
+ÐœÐžÑÐµÑÐºÐž ÑÑÐŸ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ ÐŽÐ»Ñ ÐŽÐ²ÑÑ
+ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹. Ð¥ÐŸÑÑ ÑÑÐŸ Ðž Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ, ÐœÐŸ Ð²ÑÐµ Ð¶Ðµ ÐœÐµ Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÐŸ, Ðž Ð²ÑÐµ Ð²ÑÑÐµÑÐºÐ°Ð·Ð°ÐœÐœÐŸÐµ ÐœÐ°Ð¿ÐžÑÐ°ÐœÐŸ Ð² Ð¿ÑÐµÐŽÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐž, ÑÑÐŸ ÑÐ°Ð¹Ð»Ñ ÑÐµ Ð¶Ðµ ÑÐ°ÐŒÑÐµ. ÐÐŸÐ³ÐŽÐ° ÐŸÐ¿ÐµÑÐ°ÑÐŸÑ Ð·Ð°ÐŽÐ°ÐœÐžÑ ÑÐŸÑÐŒÐ°ÑÐ° ÐŽÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ ÐŸÑÐµÐœÐµÐœ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµÐŒ, ÑÑÑÑÐºÑÑÑÐ° ÐŽÐ°ÐœÐœÑÑ
+ Ð¿ÐµÑÐµÑÐµÐºÐ°ÐµÑÑÑ. ÐÐ°ÑÑÑÑÑ, Ð¿ÑÐµÐŽÐ¿ÑÐžÐœÑÑÑÐ¹ Ð² comIf  Ðž  comOr ÑÐ·Ð»Ð°Ñ
+, Ð·Ð°Ð²ÐžÑÐžÑ ÐŸÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐºÐŸÑÐŸÑÑÐµ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÑÑ Ð·Ð°Ð¿ÑÐŸÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ñ. ÐÐŽÐœÐŸ ÐŸÑÐ»ÐŸÐ¶ÐœÐµÐœÐžÐµ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ, ÐºÐŸÐ³ÐŽÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐœÐ°Ð¹ÐŽÐµÐœÑ, ÐŸÐœÐž ÐŒÐŸÐ³ÑÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐžÐµ ÐŒÐ°ÐºÑÐŸÑÑ Ðž ÑÐŸÑÐŒÐ°Ñ ÑÐžÐœÑÐ°ÐºÑÐžÑÐ°. ÐÑÐž ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÐž ÑÑÐŸ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑÑÑ Ð¿ÐµÑÐµÐºÐ»ÑÑÐµÐœÐžÐŒ ÐœÐ°Ð·Ð°ÐŽ Ðž Ð²Ð¿ÐµÑÐµÐŽ ÐŒÐµÐ¶ÐŽÑ ÑÐžÐœÑÐ°ÐºÑÐžÑÐµÑÐºÐžÐŒ Ð°ÐœÐ°Ð»ÐžÐ·ÐŸÐŒ Ðž ÐŸÑÐµÐœÐºÐŸÐ¹, ÐºÐ°Ðº ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ.</Text>
+</Content>
+</Subsection>
+<Subsection id="macro_language">
+<Title>
+<Text id="1028">ÐÐ°ÐºÑÐŸÑÐ·ÑÐº</Text>
+</Title>
+<Content>
+<Text id="1029">Macro Language, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÑÐ¹ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="greenstone_runtime_system"/>, ÑÐ°Ðº Ð¶Ðµ, ÐºÐ°Ðº Format ÐœÐµ ÑÐ²Ð»ÑÐµÑÑÑ ÑÑÐœÐºÑÐžÐµÐ¹ ÐŸÐŽÐœÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ° C++. Ð ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ - ÑÑÐŸ ÐŸÑÐœÐŸÐ²ÐœÐŸÐ¹ ÐºÐ»Ð°ÑÑ, ÐœÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐºÐ° ÑÐ°ÐºÐ¶Ðµ Ð²ÑÐ·ÑÐ²Ð°ÐµÑ ÑÑÐœÐºÑÐžÐž Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž Ðž ÐºÐ»Ð°ÑÑÑ.</Text>
+<Text id="1030">Ð ÑÐœÐŸÐ²Ð° Ð² ÐŸÐ±ÑÑÑÐœÐµÐœÐžÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒ Ð¿ÑÐžÐŒÐµÑ. Ð¡ÐœÐ°ÑÐ°Ð»Ð° ÐŒÑ ÐŽÐ°ÐµÐŒ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÑÐžÐ¿ÐŸÐ²ÑÐµ ÐŒÐ°ÐºÑÐŸÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ ÐžÐ»Ð»ÑÑÑÑÐžÑÑÑÑ ÐŒÐ°ÐºÑÐŸÑÑÐ°ÑÑÐžÐœÑÑÐ²ÐŸ, Ð·Ð°ÑÐµÐŒ, Ð¿ÑÐž Ð¿ÐŸÐŒÐŸÑÐž ÐŽÐžÐ°Ð³ÑÐ°ÐŒÐŒÑ, ÐŒÑ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÐŒ ÐŸÑÐœÐŸÐ²ÐœÑÐµ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+, ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ, ÑÑÐŸÐ±Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶Ð°ÑÑ ÑÑÑ ÐŽÐµÑÑÐµÐ»ÑÐœÐŸÑÑÑ. ÐÐ°ÐºÐŸÐœÐµÑ, ÐŒÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÐŒ Ðž ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÐŒ ÐŸÑÐºÑÑÑÑÐµ ÑÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÑ displayclass, ÐŒÐ°ÐºÑÐŸÐŸÐ±ÑÐµÐºÑÐ° Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ.</Text>
+<Figure id="illustration_of_macro_precedence">
+<Title>
+<Text id="1031">ÐÐ»Ð»ÑÑÑÑÐ°ÑÐžÑ ÐŒÐ°ÐºÑÐŸ ÑÑÐ°ÑÑÐžÐœÑÑÐ²Ð°</Text>
+</Title>
+<CodeLine>package query</CodeLine>
+<CodeLine>_header_ []         {_querytitle_}</CodeLine>
+<CodeLine>_header_ [l=en]     {Search page}</CodeLine>
+<CodeLine>_header_ [c=demo]   {&lt;table bgcolor=green&gt;&lt;tr&gt;&lt;td&gt;_querytitle_&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;}</CodeLine>
+<CodeLine>_header_ [v=1]      {_textquery_}</CodeLine>
+<CodeLine>_header_ [l=fr,v=1,c=hdl] {HDL Page de recherche}</CodeLine>
+</Figure>
+<Text id="1032">Ð ÑÐžÐ¿ÐžÑÐœÐŸÐ¹ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Greenstone, ÐŒÐ°ÐºÑÐŸÑÑÐ°ÑÑÐžÐœÑÑÐ²ÐŸ ÐŸÐ±ÑÑÐœÐŸ: Ñ (ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž) ÐžÐŒÐµÐµÑ Ð¿ÑÐžÐŸÑÐžÑÐµÑ ÐœÐ°ÐŽ v (ÐŽÐ»Ñ Ð³ÑÐ°ÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÐžÐ»Ðž ÑÐµÐºÑÑÐŸÐ²ÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°), ÐºÐŸÑÐŸÑÑÐ¹ ÐžÐŒÐµÐµÑ Ð¿ÑÐžÐŸÑÐžÑÐµÑ ÐœÐ°ÐŽ / (ÐŽÐ»Ñ ÑÐ·ÑÐºÐ°). Ð­ÑÐŸ ÐŽÐŸÑÑÐžÐ³Ð°ÐµÑÑÑ ÑÑÑÐŸÐºÐŸÐ¹</Text>
+<CodeLine>macroprecedence c,v,l</CodeLine>
+<Text id="1033">Ð² ÐŸÑÐœÐŸÐ²ÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž main.cfg. ÐÐ°ÐºÑÐŸÐžÐœÑÑÑÑÐºÑÐžÐž ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="illustration_of_macro_precedence"/> ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÑÐžÐ¿ÐŸÐ²ÐŸÐ¹ ÐŒÐ°ÐºÑÐŸÑ ÐŽÐ»Ñ _header_ Ð² Ð¿Ð°ÐºÐµÑÐµ Ð·Ð°Ð¿ÑÐŸÑÐ° ÐŽÐ»Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž Ñ, v Ðž /. ÐÑÐ»Ðž CGI -Ð°ÑÐ³ÑÐŒÐµÐœÑ Ð·Ð°ÐŽÐ°Ðœ, ÐºÐŸÐ³ÐŽÐ° Ð²ÑÐ·Ð²Ð°ÐœÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð²ÐºÐ»ÑÑÐ°ÐµÑ c=dls, v=l Ðž 1=ÐµÐ¿, ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÐ° Jieader _ [v=l] Ð±ÑÐ»Ð° Ð±Ñ Ð²ÑÐ±ÑÐ°ÐœÐ° ÐŽÐ»Ñ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ. ÐÐœÐ° Ð±ÑÐ»Ð° Ð±Ñ Ð²ÑÐ±ÑÐ°ÐœÐ° ÑÐ°ÐœÑÑÐµ of _content _ [1=ÐµÐ¿], Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ v ÐžÐŒÐµÐµÑ Ð±ÐŸÐ»ÐµÐµ Ð²ÑÑÐŸÐºÐžÐ¹ Ð¿ÑÐžÐŸÑÐžÑÐµÑ, ÑÐµÐŒ /. Ð ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÐ° _content_[l=fr, v=l, c=dls] ÐœÐµ Ð±ÑÐ»Ð° Ð±Ñ Ð²ÑÐ±ÑÐ°ÐœÐ° Ð²ÐŸÐŸÐ±ÑÐµ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ Ð¿Ð°ÑÐ°ÐŒÐµÑÑ / ÐŽÐ»Ñ ÑÑÑÐ°ÐœÐžÑÑ Ð·Ð°ÐŽÐ°Ðœ ÑÐŸÐ²ÑÐµÐŒ ÐŽÑÑÐ³ÐŸÐ¹.</Text>
+<Figure id="data_structures_representing_the_default_macros">
+<Title>
+<Text id="1034">Ð¡ÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑÑÐžÐµ ÐŒÐ°ÐºÑÐŸÑ, Ð·Ð°ÐŽÐ°ÐœÐœÑÐ¹ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ</Text>
+</Title>
+<File width="382" height="194" url="images/Dev_Fig_094.png"/>
+</Figure>
+<Text id="1035">Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐŸÑÐœÐŸÐ²ÐœÑÑ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+, ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐœÑÑ Ð¿ÑÐž ÑÑÐµÐœÐžÐž ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»ÐŸÐ², ÑÐºÐ°Ð·Ð°ÐœÐœÑÑ
+ Ð² etc/main.cfg. ÐÐŸ ÑÑÑÐµÑÑÐ²Ñ, ÑÑÐŸ -Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÐ¹ ÐŒÐ°ÑÑÐžÐ² Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÑ
+ ÐŒÐ°ÑÑÐžÐ²ÐŸÐ² Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÑ
+ ÐŒÐ°ÑÑÐžÐ²ÐŸÐ². ÐÑÑÑÐžÐ¹ ÑÑÐŸÐ²ÐµÐœÑ (Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÑÐ¹ ÑÐ»ÐµÐ²Ð°) - ÑÑÐŸ ÐžÐœÐŽÐµÐºÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÑÐ¿Ð°ÐºÐŸÐ²ÑÐ²Ð°ÑÑ ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÑ, Ð²ÑÐŸÑÐŸÐ¹ ÑÑÐŸÐ²ÐµÐœÑ ÐžÐœÐŽÐµÐºÑÐžÑÑÐµÑ ÐŒÐ°ÐºÑÐŸÐžÐŒÑ. ÐÐŸÐœÐµÑÐœÑÐ¹ ÑÑÐŸÐ²ÐµÐœÑ ÐžÐœÐŽÐµÐºÑÐžÑÑÐµÑ Ð»ÑÐ±ÑÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ, ÑÐŸÑ
+ÑÐ°ÐœÑÑ ÐºÐ°Ð¶ÐŽÑÐ¹ ÐºÐ°Ðº ÑÐžÐ¿ mvalue, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð·Ð°Ð¿ÐžÑÑ, ÐœÐ°ÑÑÐŽÑ Ñ ÐŒÐ°ÐºÑÐŸÐ·ÐœÐ°ÑÐµÐœÐžÐµÐŒ, ÑÐ°Ð¹Ð»Ð°, ÐžÐ· ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ ÐŸÐœÐŸ ÐžÑÑ
+ÐŸÐŽÐžÐ»ÐŸ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÑÐµÐºÑÑ, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ ÐŽÐ»Ñ Jieader _ [1=ÐµÐ¿] ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="illustration_of_macro_precedence"/> ÐŒÐŸÐ¶ÐœÐŸ ÑÐ²ÐžÐŽÐµÑÑ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÑÐŒ ÐœÐžÐ¶Ðµ ÐŽÐ²ÑÑ
+ Ð·Ð°Ð¿ÐžÑÐµÐ¹ mvalue ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/>.</Text>
+<Figure id="displayclass_api">
+<Title>
+<Text id="1036"><i>Displayclass</i> API (ÑÐŸÐºÑÐ°ÑÐµÐœÐœÑÐ¹ Ð²Ð°ÑÐžÐ°ÐœÑ)</Text>
+</Title>
+<CodeLine>class displayclass</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>public:</CodeLine>
+<CodeLine>   displayclass ();</CodeLine>
+<CodeLine>   ~displayclass ();</CodeLine>
+<CodeLine>   int isdefaultmacro (text_t package, const text_t &amp;macroname);</CodeLine>
+<CodeLine>   int setdefaultmacro (text_t package, const text_t &amp;macroname,  </CodeLine>
+<CodeLine>         text_t params, const text_t &amp;macrovalue);</CodeLine>
+<CodeLine>   int loaddefaultmacros (text_t thisfilename);</CodeLine>
+<CodeLine>   void openpage (const text_t &amp;thispageparams,</CodeLine>
+<CodeLine>         const text_t &amp;thisprecedence);</CodeLine>
+<CodeLine>   void setpageparams (text_t thispageparams,</CodeLine>
+<CodeLine>         text_t thisprecedence);</CodeLine>
+<CodeLine>   int setmacro (const text_t &amp;macroname,</CodeLine>
+<CodeLine>         text_t package,</CodeLine>
+<CodeLine>         const text_t &amp;macrovalue);</CodeLine>
+<CodeLine>   void expandstring (const text_t &amp;inputtext, text_t &amp;outputtext);</CodeLine>
+<CodeLine>   void expandstring (text_t package, const text_t &amp;inputtext,</CodeLine>
+<CodeLine>         text_t &amp;outputtext, int recursiondepth = 0);</CodeLine>
+<CodeLine>   void setconvertclass (outconvertclass *theoutc) {outc = theoutc;}</CodeLine>
+<CodeLine>   outconvertclass *getconvertclass () {return outc;}</CodeLine>
+<CodeLine>   ostream *setlogout (ostream *thelogout);</CodeLine>
+<CodeLine>};</CodeLine>
+</Figure>
+<Text id="1037">ÐŠÐµÐœÑÑÐ°Ð»ÑÐœÑÐ¹ ÐŸÐ±ÑÐµÐºÑ, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐº - displayclass, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ Ð² lib/display, h. ÐÐ³ÐŸ ÐŸÑÐºÑÑÑÑÐµ ÑÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÑ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="displayclass_api"/>. ÐÐ»Ð°ÑÑ ÑÐžÑÐ°ÐµÑ ÑÐºÐ°Ð·Ð°ÐœÐœÑÐµ ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ñ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ loaddefaultmacros (), ÑÐŸÑ
+ÑÐ°ÐœÑÑ Ð² Ð·Ð°ÑÐžÑÐµÐœÐœÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐºÐ»Ð°ÑÑÐ° (ÐœÐµ Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ) ÑÐžÐ¿ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÐŸÐ¹ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="data_structures_representing_the_default_macros"/>. ÐÐ»Ñ ÐŒÐ°ÐºÑÐŸÑÐ° ÑÐ°ÐºÐ¶Ðµ ÐŽÐŸÐ¿ÑÑÑÐžÐŒÐŸ Ð±ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐœÑÐŒ ÑÐžÑÑÐµÐŒÐŸÐ¹ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ setmacro () (Ð² Ð¿ÐŸÑÐ»ÐµÐŽÐœÐµÐŒ Ð¿ÑÐžÐŒÐµÑÐµ Ð Ð°Ð·ÐŽÐµÐ»Ð° <CrossRef target="Section" ref="how_the_conceptual_framework_fits_together"/>, pageaction ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ _homeextra_ ÐºÐ°Ðº ÐŽÐžÐœÐ°ÐŒÐžÑÐµÑÐºÐž ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÑ ÑÐ°Ð±Ð»ÐžÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑÑ ÑÑÐœÐºÑÐžÑ). Ð­ÑÐŸ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑÑÑ ÐœÐ°Ð±ÐŸÑÐŸÐŒ Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÑ
+ ÐŒÐ°ÑÑÐžÐ²ÐŸÐ², Ð¿ÐŸÐŽÐŸÐ±ÐœÑÑ
+ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐŒ ÐŽÐ»Ñ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»ÐŸÐ² (ÐŸÐœÐž ÐœÐµ ÐžÐŽÐµÐœÑÐžÑÐœÑ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ Ð² Ð¿ÐµÑÐ²ÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐœÐµ ÑÑÐµÐ±ÑÐµÑÑÑ ÑÑÐŸÐ²ÐµÐœÑ "Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ°"). Ð displayclass ÑÑÐµÐœÐžÐµ ÐŒÐ°ÐºÑÐŸÑÐ° ÐžÐ· ÑÐ°Ð¹Ð»Ð° ÑÐ¿ÐŸÐŒÐžÐœÐ°ÐµÑÑÑ ÐºÐ°Ðº default macros. ÐÐŸÐºÐ°Ð»ÑÐœÑÐ¹ ÐŒÐ°ÐºÑÐŸÑ, ÑÐºÐ°Ð·Ð°ÐœÐœÑÐ¹ ÑÐµÑÐµÐ· setmacro (), ÑÐ¿ÐŸÐŒÐžÐœÐ°ÐµÑÑÑ ÐºÐ°Ðº current macros Ðž ÑÐŽÐ°Ð»ÑÐµÑÑÑ ÐžÐ· Ð¿Ð°ÐŒÑÑÐž, ÐºÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÑÑÑÐ°ÐœÐžÑÐ° Ð±ÑÐ»Ð° ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐ°.</Text>
+<Text id="1038">ÐÐŸÐ³ÐŽÐ° ÑÑÑÐ°ÐœÐžÑÐ° ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ Ð²ÐŸÑÐ¿ÑÐŸÐžÐ·Ð²ÐµÐŽÐµÐœÐ°, ÑÐœÐ°ÑÐ°Ð»Ð° Ð²ÑÐ·ÑÐ²Ð°ÐµÑÑÑ openpage Ð, ÑÑÐŸÐ±Ñ ÑÐŸÐŸÐ±ÑÐžÑÑ ÑÐµÐºÑÑÐžÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² ÑÑÑÐ°ÐœÐžÑÑ (1=ÐµÐ¿ Ðž ÑÐ°Ðº ÐŽÐ°Ð»ÐµÐµ). Ð¡Ð»ÐµÐŽÐŸÐŒ, ÑÐµÐºÑÑ Ðž ÐŒÐ°ÐºÑÐŸÑ Ð¿ÐŸÑÐŸÐºÐŸÐ²ÐŸ Ð¿ÑÐŸÑ
+ÐŸÐŽÑÑ ÑÐµÑÐµÐ· ÐºÐ»Ð°ÑÑ, ÐŸÐ±ÑÑÐœÐŸ Ñ actionclass, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑÑÐŸÐºÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ:</Text>
+<CodeLine>cout &lt;&lt; text_t2ascii &lt;&lt; display &lt;&lt; "_amacro_ "</CodeLine>
+<CodeLine>         &lt;&lt; "_anothermacro_ ";</CodeLine>
+<Text id="1039">Ð ÐµÐ·ÑÐ»ÑÑÐ°Ñ - ÐŒÐ°ÐºÑÐŸÑ, ÑÐ°ÑÑÐžÑÐµÐœÐœÑÐ¹ ÑÐŸÐ³Ð»Ð°ÑÐœÐŸ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐ°ÐŒ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² ÑÑÑÐ°ÐœÐžÑÑ. ÐÑÐ»Ðž ÑÑÐµÐ±ÑÐµÑÑÑ, ÑÑÐž Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÑÑÐ°ÑÑÐž ÐžÐ·ÐŒÐµÐœÐµÐœÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ setpageparams(). ÐÑÑÐ°ÑÑÐžÐµÑÑ ÐŸÑÐºÑÑÑÑÐµ ÑÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÑÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Ð±ÐŸÐ»ÐµÐµ ÐœÐžÐ·ÐºÐŸÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_receptionist_code">
+<Title>
+<Text id="1040">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐ°</Text>
+</Title>
+<Content>
+<Text id="1041">ÐÑÐœÐŸÐ²ÐœÑÐµ ÐŸÐ±ÑÐµÐºÑÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐ° Ð±ÑÐ»Ðž ÐŸÐ¿ÐžÑÐ°ÐœÑ. ÐÐžÐ¶Ðµ ÐŒÑ ÐŽÐµÑÐ°Ð»ÐžÐ·ÐžÑÑÐµÐŒ ÐºÐ»Ð°ÑÑÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸ ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ Ð² GSDLHOME/SRC/RECPT. ÐÑÐŸÐŒÐµ ÑÐŸÐ³ÐŸ, ÑÐ°ÐŒ Ð³ÐŽÐµ Ð³Ð»Ð°Ð²ÐœÑÐŒ ÑÐ²Ð»ÑÐµÑÑÑ ÑÑÑÐµÐºÑÐžÐ²ÐœÐŸÑÑÑ, ÐºÐŸÐ³ÐŽÐ° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ Ð²ÑÑÑÐŸÐµÐœÑ, Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÑÑÐž Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑÑ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐºÐŸÐ¿ÐžÐž ÑÐ°Ð¹Ð»Ð° Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° .ÑÑÑ. Ð€Ð°Ð¹Ð»Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž ÑÐ°ÑÑÐŸ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÑÐ»ÐŸÐ²ÐŸ tool ÐºÐ°Ðº ÑÐ°ÑÑÑ ÐžÐŒÐµÐœÐž ÑÐ°Ð¹Ð»Ð°, ÐºÐ°Ðº Ð² OIDtools.h nformattools.h.</Text>
+<Text id="1042">ÐÑÐŸÑÐŸÐ¹ ÐœÐ°Ð±ÐŸÑ Ð»ÐµÐºÑÐžÑÐµÑÐºÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð¿ÑÐµÑÐžÐºÑ z3950. Ð€Ð°Ð¹Ð»Ñ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÑÑ ÑÐŽÐ°Ð»ÐµÐœÐœÑÐ¹ ÐŽÐŸÑÑÑÐ¿ Ðº ÐžÐœÑÐµÑÐ°ÐºÑÐžÐ²ÐœÑÐŒ Ð±Ð°Ð·Ð°ÐŒ ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ð°ÐŒ, ÐºÐŸÑÐŸÑÑÐµ ÐŽÐµÐ»Ð°ÑÑ ÐžÑ
+ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÐŸÐ±ÑÐµÐŽÐŸÑÑÑÐ¿ÐœÑÐŒ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» Z39.50 .</Text>
+<Text id="1043">ÐÑÑÐ³Ð°Ñ Ð±ÐŸÐ»ÑÑÐ°Ñ Ð³ÑÑÐ¿Ð¿Ð° ÑÐ°Ð¹Ð»ÐŸÐ² Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÑÐµÑÐŒÐžÐœ browserclass. Ð­ÑÐŸ ÑÐ°Ð¹Ð»Ñ, ÑÐ²ÑÐ·Ð°ÐœÐœÑÐµ ÑÐµÑÐµÐ· Ð²ÐžÑÑÑÐ°Ð»ÑÐœÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑ ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ. ÐÐ°Ðº Ð³ÑÑÐ¿Ð¿Ð°, ÐŸÐœÐž Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑ Ð°Ð±ÑÑÑÐ°ÐºÑÐœÐŸÐµ Ð¿ÐŸÐœÑÑÐžÐµ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°: Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐ°Ñ Ð³ÐµÐœÐµÑÐ°ÑÐžÑ ÑÑÑÐ°ÐœÐžÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐœÐŸÐ³ÐŸ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµÐŒ ÐžÐ»Ðž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž. ÐÑÐŸÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑÐžÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÑÐ¿ÐŸÑÑÐŽÐŸÑÐµÐœÐœÑÑ
+ Ð² Ð°Ð»ÑÐ°Ð²ÐžÑÐœÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐŒ ÐžÐ»Ðž Ñ
+ÑÐŸÐœÐŸÐ»ÐŸÐ³ÐžÑÐµÑÐºÐž Ð¿ÐŸ Ð²ÑÐµÐŒÐµÐœÐž; ÑÐ°Ð·Ð²ÐžÑÐžÐµ ÑÐµÑÐµÐ· Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž, Ð²ÐŸÐ·Ð²ÑÐ°ÑÐµÐœÐœÑÐµ Ð·Ð°Ð¿ÑÐŸÑÐŸÐŒ, - ÐŽÐµÑÑÑÑ Ð²Ñ
+ÐŸÐŽÐŸÐ² ÐŸÐŽÐœÐŸÐ²ÑÐµÐŒÐµÐœÐœÐŸ; ÐŽÐŸÑÑÑÐ¿ Ðº ÐŸÑÐŽÐµÐ»ÑÐœÑÐŒ ÑÑÑÐ°ÐœÐžÑÐ°ÐŒ ÐºÐœÐžÐ³Ðž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒ "go to page" (Ð¿ÐµÑÐµÐ¹ÑÐž Ðº ÑÑÑÐ°ÐœÐžÑÐµ) . ÐÐ°Ð¶ÐŽÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐŸ ÐŸÑ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ° browserclass:</Text>
+<BulletList>
+<Bullet>
+<Text id="1044"><i>datelistbrowserclass</i> ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Ñ
+ÑÐŸÐœÐŸÐ»ÐŸÐ³ÐžÑÐµÑÐºÐžÐŒ ÑÐ¿ÐžÑÐºÐ°ÐŒ;</Text>
+</Bullet>
+<Bullet>
+<Text id="1045"><i>hlistbrowserclass</i> ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Ð³ÐŸÑÐžÐ·ÐŸÐœÑÐ°Ð»ÑÐœÑÐŒ ÑÐ¿ÐžÑÐºÐ°ÐŒ;</Text>
+</Bullet>
+<Bullet>
+<Text id="1046"><i>htmlbrowserclass</i> ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ ÑÑÑÐ°ÐœÐžÑÐ°ÐŒ HTML;</Text>
+</Bullet>
+<Bullet>
+<Text id="1047"><i>invbrowserclass</i> ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ ÐœÐµÐ²ÐžÐŽÐžÐŒÑÐŒ ÑÐ¿ÐžÑÐºÐ°ÐŒ;</Text>
+</Bullet>
+<Bullet>
+<Text id="1048"><i>pagedbrowserclass</i> ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒÐ° "go to page" (Ð¿ÐµÑÐµÐ¹ÑÐž Ðº ÑÑÑÐ°ÐœÐžÑÐµ);</Text>
+</Bullet>
+<Bullet>
+<Text id="1049"><i>vlistbrowserclass</i> ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Ð²ÐµÑÑÐžÐºÐ°Ð»ÑÐœÑÐŒ ÑÐ¿ÐžÑÐºÐ°ÐŒ.</Text>
+</Bullet>
+</BulletList>
+<Text id="1050">ÐÐµÐ¹ÑÑÐ²ÐžÑ ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑ Ðº ÐŸÐ±ÑÐµÐºÑÐ°ÐŒ browserclass ÑÐµÑÐµÐ· <i>browsetools.h</i>.</Text>
+<Table class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="140">
+<Text id="1051"><b>OIDtools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1052">Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° ÐŸÑÐµÐœÐºÐž ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð¿ÐŸ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ñ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1053"><b>action.h</b></Text>
+</th>
+<th width="390">
+<Text id="1054">ÐÐ°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ ÐŽÐ»Ñ ÐŸÐ±ÑÐµÐºÑÐ° Actions , ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐœÐŸÐ³ÐŸ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="greenstone_runtime_system"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1055"><b>authenaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1056">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ ÐŽÐ»Ñ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÐž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1057"><b>browserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1058">ÐÐ°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ ÐŽÐ»Ñ ÑÐµÐ·ÑÐŒÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1059"><b>browsetools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1060">Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ°, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ Ðº ÐžÐµÑÐ°ÑÑ
+ÐžÐž browserclass. Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ð²ÐºÐ»ÑÑÐ°ÑÑ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµ Ðž Ð·Ð°ÐºÐ»ÑÑÐµÐœÐžÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ, Ð²ÑÐ²ÐŸÐŽÐ° ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÑ Ðž ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒÐ° ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ ÑÐžÐ¿Ð° "go to page" (Ð¿ÐµÑÐµÐ¹ÑÐž Ðº ÑÑÑÐ°ÐœÐžÑÐµ).</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1061"><b>cgiargs.h</b></Text>
+</th>
+<th width="390">
+<Text id="1062">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ <i>cgiarginfo</i> ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/>, Ð¿ÑÐž Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐµ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐ².</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1063"><b>cgiutils.h</b></Text>
+</th>
+<th width="390">
+<Text id="1064">Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐ², ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐµ Ð² <i>cgiargs.h</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1065"><b>cgiwrapper.h</b></Text>
+</th>
+<th width="390">
+<Text id="1066">Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ°, ÐºÐŸÑÐŸÑÐ°Ñ ÐŽÐµÐ»Ð°ÐµÑ Ð²ÑÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÐµ ÐŽÐ»Ñ Ð²ÑÐ²ÐŸÐŽÐ° ÑÑÑÐ°ÐœÐžÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ CGI-Ð¿ÑÐŸÑÐŸÐºÐŸÐ». ÐÐŸÑÑÑÐ¿ ÑÐµÑÐµÐ· ÑÑÐœÐºÑÐžÑ</Text>
+<CodeLine>void cgiwrapper (receptionist &amp;recpt, text_t collection);</CodeLine>
+<Text id="1067">ÐºÐŸÑÐŸÑÐ°Ñ ÑÐ²Ð»ÑÐµÑÑÑ ÐµÐŽÐžÐœÑÑÐ²ÐµÐœÐœÐŸÐ¹ ÑÑÐœÐºÑÐžÐµÐ¹, ÐŸÐ±ÑÑÐ²Ð»ÐµÐœÐœÐŸÐ¹ Ð² ÑÐ°Ð¹Ð»Ðµ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ°. ÐÑÐµ ÐŸÑÑÐ°Ð»ÑÐœÑÐµ ÑÑÐœÐºÑÐžÐž - .ÑÑÑ ÐºÐŸÐ¿ÐžÐž, Ð»ÐµÐºÑÐžÑÐµÑÐºÐž ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÐœÑÐµ, ÑÑÐŸÐ±Ñ Ð±ÑÑÑ Ð»ÐŸÐºÐ°Ð»ÑÐœÑÐŒÐž Ð¿ÐŸ ÐŸÑÐœÐŸÑÐµÐœÐžÑ Ðº ÑÐ°Ð¹Ð»Ñ (ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐºÐ»ÑÑÐµÐ²ÐŸÐµ ÑÐ»ÐŸÐ²ÐŸ C++ static). ÐÑÐ»Ðž ÑÑÐœÐºÑÐžÑ Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÐ³ÐŽÐ° collection ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ°, ÐžÐœÐ°ÑÐµ ÑÑÐŸ ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ Ð¿ÑÑÑÐ°Ñ ÑÑÑÐŸÐºÐ° " ". ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Fast-CGI.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1068"><b>collectoraction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1069">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ ÐŸÐ±Ð»ÐµÐ³ÑÐ°ÐµÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐºÐŸÐœÐµÑÐœÐŸÐ³ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐµÑÐµÐ· Collector. Ð¡Ð³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÐ°Ñ ÑÑÑÐ°ÐœÐžÑÐ° ÐžÑÑ
+ÐŸÐŽÐžÑ ÐžÐ· collect.dm Ðž ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑÑÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐŒ CGI -Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° p=page.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1070"><b>comtypes.h</b></Text>
+</th>
+<th width="390">
+<Text id="1071">ÐÑÐœÐŸÐ²ÐœÑÐµ ÑÐžÐ¿Ñ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»ÐŸÐ².</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1072"><b>converter.h</b></Text>
+</th>
+<th width="390">
+<Text id="1073">ÐÐ±ÑÐµÐºÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° Ð¿ÐŸÑÐŸÐºÐŸÐ²ÑÐŒ ÐºÐŸÐœÐ²ÐµÑÑÐµÑÐ°ÐŒ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1074"><b>datelistbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1075">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ browserclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ñ
+ÑÐŸÐœÐŸÐ»ÐŸÐ³ÐžÑÐµÑÐºÐžÑ
+ ÑÐ¿ÐžÑÐºÐŸÐ², ÑÐžÐ¿Ð° Ð²ÐžÐŽÐµÐœÐœÐŸÐ³ÐŸ ÐœÐ°ÐŒÐž ÑÐ°ÐœÐµÐµ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone Archives Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ð¿ÐŸ "ÐŽÐ°ÑÐ°ÐŒ" Ð² ÐœÐ°Ð²ÐžÐ³Ð°ÑÐžÐŸÐœÐœÐŸÐŒ ÐŒÐµÐœÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1076"><b>documentaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1077">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐµ ÐŽÐ»Ñ Ð²ÐŸÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐžÐ»Ðž ÑÐ°ÑÑÐž ÐžÐµÑÐ°ÑÑ
+ÐžÐž ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1078"><b>extlinkaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1079">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ, ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸ Ð»Ðž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐžÐŽÐµÑ Ð¿ÑÑÐŒÐŸ Ð¿ÐŸ Ð²ÐœÐµÑÐœÐµÐ¹ ÑÑÑÐ»ÐºÐµ ÐžÐ»Ðž Ð¿ÑÐŸÑ
+ÐŸÐŽÐžÑ ÑÐµÑÐµÐ· ÑÑÑÐ°ÐœÐžÑÑ Ð¿ÑÐµÐŽÑÐ¿ÑÐµÐ¶ÐŽÐµÐœÐžÑ, ÐŸÐ¿ÐŸÐ²ÐµÑÐ°ÑÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŸ ÑÐŸÐŒ ÑÐ°ÐºÑÐµ, ÑÑÐŸ ÐŸÐœ ÑÐŸÐ±ÐžÑÐ°ÐµÑÑÑ Ð¿ÐŸÐºÐžÐœÑÑÑ ÑÐžÑÑÐŸÐ²ÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÑ ÑÐžÑÑÐµÐŒÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1080"><b>formattools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1081">Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° Ð°ÐœÐ°Ð»ÐžÐ·Ð° Ðž ÐŸÑÐµÐœÐºÐž ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÐ°ÐŒÐž/ormutf. ÐÐŸÐŽÑÐŸÐ±ÐœÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Subsection" ref="formatting"/>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1082"><b>historydb.h</b></Text>
+</th>
+<th width="390">
+<Text id="1083">Ð¡ÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ Ð±Ð°Ð·ÐŸÐ¹ ÐŽÐ°ÐœÐœÑÑ
+ Ð¿ÑÐµÐŽÑÐŽÑÑÐžÑ
+ Ð·Ð°Ð¿ÑÐŸÑÐŸÐ², ÑÐ°Ðº ÑÑÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŒÐŸÐ¶ÐµÑ Ð·Ð°Ð¿ÑÑÑÐžÑÑ ÐœÐŸÐ²ÑÐ¹ Ð·Ð°Ð¿ÑÐŸÑ, ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð¿ÑÐµÐŽÑÐŽÑÑÐžÐµ ÑÑÐ»ÐŸÐ²ÐžÑ Ð·Ð°Ð¿ÑÐŸÑÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1084"><b>hlistbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1085">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ browserclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ð³ÐŸÑÐžÐ·ÐŸÐœÑÐ°Ð»ÑÐœÑÑ
+ ÑÐ¿ÐžÑÐºÐŸÐ².</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1086"><b>htmlbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1087">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ browserclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÑÑÑÐ°ÐœÐžÑ HTML.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1088"><b>htmlgen.h</b></Text>
+</th>
+<th width="390">
+<Text id="1089">Ð€ÑÐœÐºÑÐžÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž Ð¿ÐŸÐŽÑÐ²ÐµÑÐºÐž ÑÐµÑÐŒÐžÐœÐŸÐ² Ð·Ð°Ð¿ÑÐŸÑÐ° Ð² text_t ÑÑÑÐŸÐºÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1090"><b>htmlutils.h</b></Text>
+</th>
+<th width="390">
+<Text id="1091">Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ°, ÐºÐŸÑÐŸÑÐ°Ñ ÐºÐŸÐœÐ²ÐµÑÑÐžÑÑÐµÑ text_t ÑÑÑÐŸÐºÑ Ð² ÑÐºÐ²ÐžÐ²Ð°Ð»ÐµÐœÑÐœÑÐ¹ HTML. Ð¡ÐžÐŒÐ²ÐŸÐ»Ñ ", &amp;, &lt;, Ðž &gt; Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²ÑÐ²Ð°ÑÑÑÑ Ð² &quot;, &amp;Ð°ÑÑ;, &lt; Ðž &gt; ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1092"><b>infodbclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1093">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐŽÐ²Ð° ÐºÐ»Ð°ÑÑÐ°: gdbmclass Ðž infodbclass. ÐÐµÑÐ²ÑÐ¹ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Greenstone API Ðº GDBM; Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐ¹ - ÐŸÐ±ÑÐµÐºÑÐœÑÐ¹ ÐºÐ»Ð°ÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÐŽÐ»Ñ Ñ
+ÑÐ°ÐœÐµÐœÐžÑ Ð·Ð°Ð¿ÐžÑÐµÐ¹ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² ÑÑÐµÐœÐžÑ ÐžÐ· GDBM Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+, Ð° Ð¿ÐŸ ÑÑÑÐµÑÑÐ²Ñ - Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÐ¹ ÐŒÐ°ÑÑÐžÐ² ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐœÑÑ
+ ÑÐµÐ»ÑÐŒ ÑÐžÑÐ»ÐŸÐŒ ÐŒÐ°ÑÑÐžÐ²ÐŸÐ² text_t ÑÑÑÐŸÐº.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1094"><b>invbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1095">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ browserclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÑÐ¿ÐžÑÐºÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐœÐµ Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° (ÐœÐµÐ²ÐžÐŽÐžÐŒÑÐµ).</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1096"><b>nullproto.h</b></Text>
+</th>
+<th width="390">
+<Text id="1097">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ recptproto, ÑÑÐŸÑ ÐºÐ»Ð°ÑÑ Ð¿ÐŸÐœÐžÐŒÐ°ÐµÑ ÐœÑÐ»ÐµÐ²ÐŸÐ¹ Ð¿ÑÐŸÑÐŸÐºÐŸÐ», ÑÐµÐ°Ð»ÐžÐ·ÐŸÐ²Ð°ÐœÐœÑÐ¹ ÑÐµÑÐµÐ· ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐµ Ð·Ð°Ð¿ÑÐŸÑÑ ÐŸÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐ° ÐœÐ° ÑÐµÑÐ²ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1098"><b>pageaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1099">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð²ÐŒÐµÑÑÐµ Ñ ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»ÐŸÐŒ, ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÐŒ sp=page, Ð³ÐµÐœÐµÑÐžÑÑÐµÑ web-ÑÑÑÐ°ÐœÐžÑÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1100"><b>pagedbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1101">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ browserclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒÐ° Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° "go to page" (Ð¿ÐµÑÐµÐ¹ÑÐž Ðº ÑÑÑÐ°ÐœÐžÑÐµ), ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, Ð² Gutenberg ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. </Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1102"><b>pingaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1103">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð²ÑÑÑÐœÑÐµÑ, ÐŸÑÐ²ÐµÑÐ°ÐµÑ Ð»Ðž ÑÐ°ÑÑÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1104"><b>queryaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1105">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð±ÐµÑÐµÑ Ð¿ÑÐµÐŽÑÑÐŒÐŸÑÑÐµÐœÐœÑÐ¹ Ð·Ð°Ð¿ÑÐŸÑ, Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž Ðž Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÑ Ðž ÐžÑÐ¿ÐŸÐ»ÐœÑÐµÑ Ð¿ÐŸÐžÑÐº, Ð³ÐµÐœÐµÑÐžÑÑÑ Ð² ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ Ð¿ÐŸÐŽÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ ÐŸ=Ð¿ÐžÑ, ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ, ÐœÐ°ÑÐžÐœÐ°ÑÑÐžÐŒÑÑ Ð² Ð¿ÐŸÐ·ÐžÑÐžÐž Ð³=Ð¿ÐžÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1106"><b>querytools.h</b></Text>
+</th>
+<th width="390">
+<Text id="1107">Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° Ð·Ð°Ð¿ÑÐŸÑÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1108"><b>receptionist.h</b></Text>
+</th>
+<th width="390">
+<Text id="1109">ÐÐ±ÑÐµÐºÑ Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐ°. ÐÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ Ð·Ð°Ð¿ÐžÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐ°, ÑÐµÐ°Ð»ÐžÐ·Ð°ÑÐžÑ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐ³ÐŸ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ, ÑÐµÐ°Ð»ÐžÐ·Ð°ÑÐžÑ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐ³ÐŸ Ð±ÑÐŸÑÐ·ÐµÑÐ°, ÐŸÑÐœÐŸÐ²ÐœÐŸÐ¹ ÐŒÐ°ÐºÑÐŸÑÐ·ÑÐº ÐŸÐ±ÑÐµÐºÑÐ° displayclass Ðž Ð²ÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÐµ ÐºÐŸÐœÐ²ÐµÑÑÐµÑÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1110"><b>recptconfig.h</b></Text>
+</th>
+<th width="390">
+<Text id="1111">Ð€ÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° ÑÐžÑÐµÐœÐžÑ ÑÐ°Ð¹ÑÐ° Ðž ÐŸÑÐœÐŸÐ²ÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1112"><b>recptproto.h</b></Text>
+</th>
+<th width="390">
+<Text id="1113">ÐÐ°Ð·ÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1114"><b>statusaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1115">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð²ÐŒÐµÑÑÐµ ÑÐŸ status.dm Ð³ÐµÐœÐµÑÐžÑÑÐµÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÑÑÑÐ°ÐœÐžÑÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1116"><b>tipaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1117">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑ Ð²ÐŒÐµÑÑÐµ Ñ tip.dm web-ÑÑÑÐ°ÐœÐžÑÑ, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑÑ ÑÐŸÐ²ÐµÑ, Ð²Ð·ÑÑÑÐ¹ ÐœÐ°ÑÐ³Ð°ÐŽ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° Ð¿ÐŸÐŽÑÐºÐ°Ð·ÐŸÐº, ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÑÑ
+ Ð² <i>tip.dm</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1118"><b>userdb.h</b></Text>
+</th>
+<th width="390">
+<Text id="1119">Ð¡ÑÑÑÐºÑÑÑÐ° ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° GDBM Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐœÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹: ÐžÑ
+ Ð¿Ð°ÑÐŸÐ»Ðž, Ð³ÑÑÐ¿Ð¿Ñ Ðž ÑÐ°Ðº ÐŽÐ°Ð»ÐµÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1120"><b>usersaction.h</b></Text>
+</th>
+<th width="390">
+<Text id="1121">ÐÐµÐ¹ÑÑÐ²ÐžÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑÐ°, ÐœÐ°ÑÐ»ÐµÐŽÑÐµÐŒÑÐµ Ð±Ð°Ð·ÐŸÐ²ÑÐŒ ÐºÐ»Ð°ÑÑÐŸÐŒ, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐµ Ðž ÑÐŽÐ°Ð»ÐµÐœÐžÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹, Ð° ÑÐ°ÐºÐ¶Ðµ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÐµ Ð³ÑÑÐ¿Ð¿, Ð² ÐºÐŸÑÐŸÑÑÑ
+ ÐŸÐœÐž ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1122"><b>vlistbrowserclass.h</b></Text>
+</th>
+<th width="390">
+<Text id="1123">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ browserclass, ÑÑÐŸÑ ÐŸÐ±ÑÐµÐºÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐŽÐ»Ñ Ð²ÐµÑÑÐžÐºÐ°Ð»ÑÐœÑÑ
+ ÑÐ¿ÐžÑÐºÐŸÐ², ÐŸÑÐœÐŸÐ²Ñ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ². ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŽÐŸÑÐµÑÐœÐžÐµ Ð·Ð°Ð¿ÐžÑÐž ÑÐ·Ð»Ð° ÐŽÐ»Ñ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ², ÐœÐ°ÑÐžÐœÐ°ÑÑÐžÑ
+ÑÑ Ñ ÑÐžÐŒÐ²ÐŸÐ»Ð° N Ð¿ÑÐµÐŽÑÑÐŒÐŸÑÑÐµÐœÑ Ð² VList.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1124"><b>z3950cfg.h</b></Text>
+</th>
+<th width="390">
+<Text id="1125">Ð¡ÑÑÑÐºÑÑÑÐ° ÐŽÐ°ÐœÐœÑÑ
+, Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑÐ°Ñ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» Z39.50. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ z3950proto. cpp, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐŸÑÐœÐŸÐ²ÐœÐŸÐ¹ ÐºÐ»Ð°ÑÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° (ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ° recptproto) Ðž ÑÐžÐœÑÐ°ÐºÑÐžÑÐµÑÐºÐžÐ¹ Ð°ÐœÐ°Ð»ÐžÐ·Ð°ÑÐŸÑ ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž zparse.y (Ð¿ÐžÑÑÐŒÐµÐœÐœÐŸÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ YACC).</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1126"><b>z3950proto.h</b></Text>
+</th>
+<th width="390">
+<Text id="1127">Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŸÑ recptproto, ÑÑÐŸÑ ÐºÐ»Ð°ÑÑ ÑÐµÐ°Ð»ÐžÐ·ÑÐµÑ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» Z39.50 ÑÐ°Ðº, ÑÑÐŸÐ±Ñ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ Greenstone ÐŒÐŸÐ³ ÐŸÐ±ÑÐ°ÑÐžÑÑÑÑ Ðº ÐŸÑÐŽÐ°Ð»ÐµÐœÐœÑÐŒ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐŒ ÑÐ°Ð¹ÑÐ°ÐŒ, ÑÐ°Ð±ÐŸÑÐ°ÑÑÐžÐŒ ÐœÐ° ÑÐµÑÐ²ÐµÑÐ°Ñ
+ Z39.50.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="1128"><b>z3950server.h</b></Text>
+</th>
+<th width="390">
+<Text id="1129">ÐÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ° ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð° Z39.50.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="initialisation">
+<Title>
+<Text id="1130">ÐÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÑ</Text>
+</Title>
+<Content>
+<Text id="1131">ÐÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÑ Ð² Greenstone - ÑÐ»ÐŸÐ¶ÐœÐ°Ñ ÐŸÐ¿ÐµÑÐ°ÑÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÑÐ°Ð¹Ð»Ñ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž Ðž Ð¿ÑÐžÑÐ²Ð°ÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐ»ÑÐŒ ÐŽÐ°ÐœÐœÑÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ . Ð ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ Ðº ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ Ðž ÑÑÐœÐºÑÐžÑÐŒ ÐºÐŸÐœÑÑÑÑÐºÑÐŸÑÐ°, ÐŸÑÐœÐŸÐ²ÐœÑÐµ ÐŸÐ±ÑÐµÐºÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÑÑÐœÐºÑÐžÐž init () Ðž conflgure(), ÑÑÐŸÐ±Ñ Ð¿ÐŸÐŒÐŸÑÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐžÐ·ÐŸÐ²Ð°ÑÑ Ð·Ð°ÐŽÐ°ÑÑ. ÐÐ°Ð¶Ðµ Ð² ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ Ð¿ÐŸÑÑÐŽÐŸÐº Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð·Ð°ÑÑÑÐŽÐœÐµÐœ. ÐÐ°ÑÑÐŸÑÑÐžÐ¹ ÑÐ°Ð·ÐŽÐµÐ» ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÐºÐ°Ðº Ð²ÑÐµ ÑÑÐŸ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ.</Text>
+<Text id="1132">Greenstone ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ°Ð¹Ð»ÐŸÐ² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐŽÐ»Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐµÐ»ÐµÐ¹, ÐœÐŸ Ð²ÑÐµ ÐŸÐœÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ ÐŸÐŽÐžÐœ Ðž ÑÐŸÑ Ð¶Ðµ ÑÐžÐœÑÐ°ÐºÑÐžÑ. ÐÑÐ»Ðž ÑÑÑÐŸÐºÐ° ÐœÐµ ÐœÐ°ÑÐžÐœÐ°ÐµÑÑÑ Ñ Ñ
+ÑÑ-ÑÐžÐŒÐ²ÐŸÐ»Ð° (#) ÐžÐ»Ðž ÑÐŸÑÑÐŸÐžÑ Ð¿ÐŸÐ»ÐœÐŸÑÑÑÑ ÐžÐ· Ð¿ÑÑÑÐŸÐ³ÐŸ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ð°, Ð¿ÐµÑÐ²ÐŸÐµ ÑÐ»ÐŸÐ²ÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐºÐ»ÑÑÐµÐ²ÐŸÐµ ÑÐ»ÐŸÐ²ÐŸ, Ð° ÐŸÑÑÐ°ÑÑÐžÐµÑÑ ÑÐ»ÐŸÐ²Ð° Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÑ ÑÐ°ÑÑÐœÐŸÑÑÐž ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ ÐºÐ»ÑÑÐµÐ²ÐŸÐ³ÐŸ ÑÐ»ÐŸÐ²Ð°.</Text>
+<Text id="1133">Ð¡ÑÑÐŸÐºÐž ÑÐ°Ð¹Ð»ÐŸÐ² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž Ð¿ÐµÑÐµÐŽÐ°ÑÑ, Ð¿ÐŸ ÐŸÐŽÐœÐŸÐŒÑ, ÐŽÐ»Ñ conflgure() ÐŽÐ²Ð° Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ°: ÐºÐ»ÑÑÐµÐ²ÐŸÐµ ÑÐ»ÐŸÐ²ÐŸ Ðž ÐŒÐ°ÑÑÐžÐ² ÐŸÑÑÐ°ÑÑÐžÑ
+ÑÑ ÑÐ»ÐŸÐ². ÐÑÐœÐŸÐ²Ð°ÐœÐœÐ°Ñ ÐœÐ° ÐºÐ»ÑÑÐµÐ²ÐŸÐŒ ÑÐ»ÐŸÐ²Ðµ, ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐ°Ñ Ð²ÐµÑÑÐžÑ Ð²ÑÐ±ÐŸÑÐ° configure() ÑÐµÑÐ°ÐµÑ, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑ Ð»Ðž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐžÐœÑÐµÑÐµÑ, Ðž ÐµÑÐ»Ðž ÑÑÐŸ ÑÐ°Ðº ÑÐŸ ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑ ÐµÐµ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, collectserver (ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="greenstone_runtime_system"/>), ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÑ Ð·Ð°ÐŽÐ°ÐœÐžÑ ÑÐŸÑÐŒÐ°ÑÐ° Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÐ³ÐŽÐ° ÑÐŸÑÐŒÐ°Ñ ÐºÐ»ÑÑÐµÐ²ÐŸÐ³ÐŸ ÑÐ»ÐŸÐ²Ð° Ð¿ÐµÑÐµÐŽÐ°ÑÑ configure(), ÐŸÐ¿ÐµÑÐ°ÑÐŸÑ if Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÑÑ Ð² ÐŸÐ±ÑÐµÐºÑÐµ ÐºÐŸÐ¿ÐžÑ Ð²ÑÐŸÑÐŸÐ³ÐŸ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° ÑÑÐœÐºÑÐžÐž.</Text>
+<Text id="1134">ÐÐŸÑÐ»Ðµ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÐºÐ»ÑÑÐµÐ²ÐŸÐ³ÐŸ ÑÐ»ÐŸÐ²Ð° Ðž Ð¿ÑÐµÐ¶ÐŽÐµ, ÑÐµÐŒ ÑÑÐœÐºÑÐžÑ Ð·Ð°ÐºÐŸÐœÑÐžÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ, ÐœÐµÐºÐŸÑÐŸÑÑÐµ Ð²ÐµÑÑÐžÐž conflgure() Ð¿ÐµÑÐµÐŽÐ°ÑÑ ÐŽÐ°ÐœÐœÑÐµ ÑÑÐœÐºÑÐžÐž configure() Ð² ÐŽÑÑÐ³ÐžÑ
+ ÐŸÐ±ÑÐµÐºÑÐ°Ñ
+. ÐÐ±ÑÐµÐºÑ Receptionist (ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ) Ð²ÑÐ·ÑÐ²Ð°ÐµÑ Ð²ÑÐ±ÐŸÑ configureQ ÐŽÐ»Ñ Actions , Protocols Ðž Browsers. ÐÐ±ÑÐµÐºÑ NullProtocol Ð²ÑÐ·ÑÐ²Ð°ÐµÑ conflgure() ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐŸÐ±ÑÐµÐºÑÐ° Collection; Collection Ð²ÑÐ·ÑÐ²Ð°ÐµÑ Filters Ðž Sources.</Text>
+<Text id="1135">Ð C++ Ð¿ÐŸÐ»Ñ ÐŽÐ°ÐœÐœÑÑ
+ ÐŸÐ±ÑÑÐœÐŸ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·ÐžÑÑÑÑÑÑ ÑÑÐœÐºÑÐžÐµÐ¹ ÐºÐŸÐœÑÑÑÑÐºÑÐŸÑÐ° ÐŸÐ±ÑÐµÐºÑÐ°. ÐÐŽÐœÐ°ÐºÐŸ, Ð² Greenstone ÐœÐµÐºÐŸÑÐŸÑÐ°Ñ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÑ Ð·Ð°Ð²ÐžÑÐžÑ ÐŸÑ ÑÑÐµÐœÐžÑ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ ÐžÐ· ÑÐ°Ð¹Ð»ÐŸÐ² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž, ÑÐ°Ðº ÑÑÐŸ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒ Ð²ÑÐŸÑÐŸÐ¹ ÑÐ°ÑÐœÐŽ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž. Ð­ÑÐŸ - ÑÐµÐ»Ñ init () ÑÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÐ°, Ð² ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÑÐ»ÑÑÐ°ÑÑ
+ ÐŸÐœÐ° Ð²ÐµÐŽÐµÑ Ðº Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐµÐŒÑ Ð²ÑÐ·ÐŸÐ²Ñ conflgure().</Text>
+<Figure id="initialising_greenstone_using_the_null_protocol">
+<Title>
+<Text id="1136">ÐÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÑ Greenstone, Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ    , ÐœÑÐ»Ñ-Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°</Text>
+</Title>
+<CodeLine>============</CodeLine>
+<CodeLine>Main program</CodeLine>
+<CodeLine>============</CodeLine>
+<CodeLine>Statically construct Receptionist</CodeLine>
+<CodeLine>Statically construct NullProtocol</CodeLine>
+<CodeLine>Establish the value for 'gsdlhome' by reading gsdlsite.cfg</CodeLine>
+<CodeLine>Foreach directory in GSDLHOME/collect that isn't "modelcol":</CodeLine>
+<CodeLine>   Add directory name (now treated as collection name) to NullProtocol:</CodeLine>
+<CodeLine>       Dynamically construct Collection</CodeLine>
+<CodeLine>       Dynamically construct Gdbm class</CodeLine>
+<CodeLine>       Dynamically construct the Null Filter</CodeLine>
+<CodeLine>       Dynamically construct the Browse Filter</CodeLine>
+<CodeLine>       Dynamically construct MgSearch</CodeLine>
+<CodeLine>       Dynamically construct the QueryFilter</CodeLine>
+<CodeLine>       Dynamically construct the MgGdbmSource</CodeLine>
+<CodeLine>       Configure Collection with 'collection'</CodeLine>
+<CodeLine>           Passing 'collection' value on to Filters and Sources:</CodeLine>
+<CodeLine>       Configure Receptionist with 'collectinfo':</CodeLine>
+<CodeLine>           Passing 'collectinfo' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>Add NullProtocol to Receptionist</CodeLine>
+<CodeLine>Add in UTF-8 converter</CodeLine>
+<CodeLine>Add in GB converter</CodeLine>
+<CodeLine>Add in Arabic converter</CodeLine>
+<CodeLine>Foreach Action:</CodeLine>
+<CodeLine>   Statically construct Action</CodeLine>
+<CodeLine>   Add Action to Receptionist</CodeLine>
+<CodeLine>Foreach Browsers:</CodeLine>
+<CodeLine>   Statically construct Browser</CodeLine>
+<CodeLine>   Add Browser to Receptionist</CodeLine>
+<CodeLine>Call function cgiwrapper:</CodeLine>
+<CodeLine>   =================</CodeLine>
+<CodeLine>   Configure objects</CodeLine>
+<CodeLine>   =================</CodeLine>
+<CodeLine>   Configure Receptionist with 'collection'</CodeLine>
+<CodeLine>       Passing 'collection' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>       NullProtocol not interested in 'collection'</CodeLine>
+<CodeLine>   Configure Receptionist with 'httpimg'</CodeLine>
+<CodeLine>       Passing 'httpimg' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>       NullProtocol passing 'httpimg' on to Collection</CodeLine>
+<CodeLine>       Passing 'httpimg' value on to Filters and Sources:</CodeLine>
+<CodeLine>   Configure Receptionist with 'gwcgi'</CodeLine>
+<CodeLine>       Passing 'gwcgi' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>       NullProtocol passing 'gwcgi' on to Collection</CodeLine>
+<CodeLine>           Passing 'gwcgi' value on to Filters and Sources:</CodeLine>
+<CodeLine>   Reading in site configuration file gsdlsite.cfg</CodeLine>
+<CodeLine>       Configure Recptionist with 'gsdlhome'</CodeLine>
+<CodeLine>           Passing 'gsdlhome' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>           NullProtocol passing 'gsdlhome' on to Collection</CodeLine>
+<CodeLine>               Passing 'gsdlhome' value on to Filters and Sources:</CodeLine>
+<CodeLine>       Configure Recptionist with ...</CodeLine>
+<CodeLine>       ... and so on for all entries in gsdlsite.cfg</CodeLine>
+<CodeLine>   Reading in main configuration file main.cfg</CodeLine>
+<CodeLine>       Confiugre Recptionist with ...</CodeLine>
+<CodeLine>       ... and so on for all entries in main.cfg</CodeLine>
+<CodeLine>   ====================</CodeLine>
+<CodeLine>   Initialising objects</CodeLine>
+<CodeLine>   ====================</CodeLine>
+<CodeLine>   Initialise the Receptionist</CodeLine>
+<CodeLine>       Configure Receptionist with 'collectdir'</CodeLine>
+<CodeLine>           Passing 'collectdir' value on to Actions, Protocols, and Browsers:</CodeLine>
+<CodeLine>           NullProtocol not interested in 'collectdir'</CodeLine>
+<CodeLine>       Read in Macro files</CodeLine>
+<CodeLine>       Foreach Actions</CodeLine>
+<CodeLine>           Initialise Action</CodeLine>
+<CodeLine>       Foreach Protocol</CodeLine>
+<CodeLine>           Initialise Protocol</CodeLine>
+<CodeLine>           When Protocol==NullProtocol:</CodeLine>
+<CodeLine>               Foreach Collection</CodeLine>
+<CodeLine>                   Reading Collection's build.cfg</CodeLine>
+<CodeLine>                   Reading Collection's collect.cfg</CodeLine>
+<CodeLine>                       Configure Collection with 'creator'</CodeLine>
+<CodeLine>                           Passing 'creator' value on to Filters and Sources:</CodeLine>
+<CodeLine>                       Configure Collection with 'maintainer'</CodeLine>
+<CodeLine>                           Passing 'maintainer' value on to Filters and Sources:</CodeLine>
+<CodeLine>                       ... and so on for all entries in collect.cfg</CodeLine>
+<CodeLine>       Foreach Browsers</CodeLine>
+<CodeLine>           Initialise Browser</CodeLine>
+<CodeLine>   =============</CodeLine>
+<CodeLine>   Generate page</CodeLine>
+<CodeLine>   =============</CodeLine>
+<CodeLine>   Parse CGI arguments</CodeLine>
+<CodeLine>   Execute designated Action to produce page</CodeLine>
+<CodeLine>End.</CodeLine>
+</Figure>
+<Text id="1137">ÐÐ° ÑÐžÑÑÐœÐŸÐºÐµ <CrossRef target="Figure" ref="initialising_greenstone_using_the_null_protocol"/> Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ ÐŽÐžÐ°Ð³ÐœÐŸÑÑÐžÑÐµÑÐºÐžÐµ ÐžÐœÑÑÑÑÐºÑÐžÐž, ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ Greenstone, ÑÐ²ÐµÐ»ÐžÑÐµÐœÐœÑÐµ ÑÐ°Ðº, ÑÑÐŸÐ±Ñ Ð²ÑÐŽÐµÐ»ÐžÑÑ Ð¿ÑÐŸÑÐµÑÑ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž. ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐ°ÑÐžÐœÐ°ÐµÑÑÑ Ñ ÑÑÐœÐºÑÐžÐž main() Ð² recpt/librarymain.cpp. ÐÐœÐ° ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐŸÐ±ÑÐµÐºÑ Receptionist Ðž ÐŸÐ±ÑÐµÐºÑ NullProtocol, Ð·Ð°ÑÐµÐŒ Ð¿ÑÐŸÑÐŒÐ°ÑÑÐžÐ²Ð°ÐµÑ gsdlsite.cfg (ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐœÑÐ¹ Ð² ÑÐŸÐŒ Ð¶Ðµ ÑÐ°ÐŒÐŸÐŒ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ðµ, ÑÑÐŸ Ðž Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÐŒÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° library) ÐŽÐ»Ñ gsdlhome Ðž ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑ ÐµÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð² Ð¿ÐµÑÐµÐŒÐµÐœÐœÐŸÐ¹.</Text>
+<Text id="1138">ÐÐ°Ð»ÐµÐµ mainQ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑ ÐŸÐ±ÑÐµÐºÑ NullProtocol Ðº Receptionist (Ð ÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÑ), ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑ ÐŒÐ°ÑÑÐžÐ² Ð¿ÑÐŸÑÐŸÐºÐŸÐ»ÐŸÐ² Ð±Ð°Ð·ÐŸÐ²ÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐ° Ð² Ð·Ð°ÑÐžÑÐµÐœÐœÐŸÐŒ Ð¿ÐŸÐ»Ðµ ÐŽÐ°ÐœÐœÑÑ
+, Ð° Ð·Ð°ÑÐµÐŒ ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐºÐŸÐœÐ²ÐµÑÑÐµÑÐŸÐ². main() ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð²ÑÐµ Actions Ðž Browsers, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ Ð² Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÐŒÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ, Ðž ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑ ÐžÑ
+ Ðº Ð ÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÑ. Ð Ð·Ð°Ð²ÐµÑÑÐµÐœÐžÐµ ÑÑÐœÐºÑÐžÑ Ð²ÑÐ·ÑÐ²Ð°ÐµÑ cgiwrapper () Ð² cgiwrapper.cpp, ÐºÐŸÑÐŸÑÑÐ¹ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÑÑÑÐµÑÑÐ²ÐµÐœÐœÑÑ ÐŸÐ±ÑÐµÐºÑÐœÑÑ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÑ.</Text>
+<Text id="1139">Ð¡ÑÑÐµÑÑÐ²ÑÑÑ ÑÑÐž ÑÑÐ°Ð¿Ð° cgiwrapper(): ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÑ, ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÑ Ðž Ð³ÐµÐœÐµÑÐ°ÑÐžÑ ÑÑÑÐ°ÐœÐžÑÑ. Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÑÑÑÑ Ð°Ð¿Ð¿Ð°ÑÐ°ÑÐœÑÐµ Ð·Ð°Ð¿ÑÐŸÑÑ conflgure(). ÐÐ°ÑÐµÐŒ ÑÐžÑÐ°ÐµÑÑÑ gsdlsite.cfg Ðž Ð²ÑÐ·ÑÐ²Ð°ÐµÑÑÑ configure() ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÑÑÑÐŸÐºÐž. Ð¢ÐŸ Ð¶Ðµ ÑÐ°ÐŒÐŸÐµ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ ÐŽÐ»Ñ etc/main.cfg.</Text>
+<Text id="1140">ÐÑÐŸÑÐŸÐ¹ ÑÑÐ°Ð¿ cgiwrapper () ÐŽÐµÐ»Ð°ÐµÑ Ð·Ð°Ð¿ÑÐŸÑÑ Ðº init (). Ð ÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ ÐŽÐµÐ»Ð°ÐµÑ ÑÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐžÐœ Ð·Ð°Ð¿ÑÐŸÑ Ðº ÑÐ²ÐŸÐµÐ¹ ÑÑÐœÐºÑÐžÐž init (), ÐœÐŸ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµÐŒ Ð²ÑÐ·ÐŸÐ²Ð° Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑ ÑÑÐœÐºÑÐžÐž init () Ð² ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐŸÐ±ÑÐµÐºÑÐ°Ñ
+, ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÑÑ
+ Ð² ÐµÐ³ÐŸ Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+. Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ Ð°Ð¿Ð¿Ð°ÑÐ°ÑÐœÑÐ¹ Ð·Ð°Ð¿ÑÐŸÑ conflgure(), ÑÑÐŸÐ±Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ collectdir, Ð¿ÐŸÑÐ»Ðµ ÑÐµÐ³ÐŸ ÑÐžÑÐ°ÑÑÑÑ ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ñ. ÐÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ Ð²ÑÐ·ÑÐ²Ð°ÑÑ ÐµÐ³ÐŸ init () ÑÑÐœÐºÑÐžÑ. Ð¢ÐŸ Ð¶Ðµ ÑÐ°ÐŒÐŸÐµ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°, ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÐŸÐ³ÐŸ Ð² ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐµ, ÐœÐŸ Ð² ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÐŒÐŸÐ¹ ÑÐžÑÑÐµÐŒÐµ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœ ÑÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐžÐœ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» - NullProtocol. ÐÐ°Ð¿ÑÐŸÑ init () ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ ÐŸÐ±ÑÐµÐºÑÐ° Ð²ÑÐ·ÑÐ²Ð°ÐµÑ ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÑÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÑ: ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð² NullProtocol ÑÐžÑÐ°ÑÑÑÑ Ðž ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÑÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹ build.cfg Ðž collect.cfg, Ñ Ð·Ð°Ð¿ÑÐŸÑÐŸÐŒ configure() ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÑÑÑÐŸÐºÐž.</Text>
+<Text id="1141">ÐÐ° Ð·Ð°ÐºÐ»ÑÑÐžÑÐµÐ»ÑÐœÐŸÐŒ ÑÑÐ°Ð¿Ðµ cgiwrapper () ÐŽÐŸÐ»Ð¶ÐµÐœ Ð¿ÑÐŸÐ°ÐœÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÑÑ CGI -Ð°ÑÐ³ÑÐŒÐµÐœÑÑ Ðž Ð·Ð°ÑÐµÐŒ Ð²ÑÐ·Ð²Ð°ÑÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ. ÐÐ±Ð° ÑÑÐžÑ
+ Ð·Ð°Ð¿ÑÐŸÑÐ° Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÑÑÑÑ Ð¿ÑÐž Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐµ ÐŸÐ±ÑÐµÐºÑÐ° Receptionist.</Text>
+<Text id="1142">ÐÑÐžÑÐžÐœÐ° ÐŽÐ»Ñ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž, ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž Ðž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð³ÐµÐœÐµÑÐ°ÑÐžÐž ÑÑÑÐ°ÐœÐžÑÑ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ Greenstone ÐŸÐ¿ÑÐžÐŒÐžÐ·ÐžÑÐŸÐ²Ð°Ðœ ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÐµÑÐ²ÐµÑÐ° (ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Fast-cgi, ÐžÐ»Ðž Ð¿ÑÐŸÑÐŸÐºÐŸÐ» Corba, ÐžÐ»Ðž Windows Local Library). Ð ÑÑÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ ÑÐ°Ð±ÐŸÑÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÑ Ðž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž Ð·Ð°Ð¿ÑÑÐºÐ°ÑÑÑÑ ÐŸÐŽÐœÐ°Ð¶ÐŽÑ, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐŸÑÑÐ°ÐµÑÑÑ Ð² Ð¿Ð°ÐŒÑÑÐž Ðž Ð³ÐµÐœÐµÑÐžÑÑÐµÑ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ web-ÑÑÑÐ°ÐœÐžÑ Ð² ÐŸÑÐ²ÐµÑ ÐœÐ° Ð·Ð°Ð¿ÑÐŸÑÑ ÐŸÑ ÐºÐ»ÐžÐµÐœÑÐŸÐ², ÐœÐµ ÑÑÐµÐ±ÑÑ Ð¿ÐµÑÐµÑÑÑÐ°ÐœÐŸÐ²ÐºÐž.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="configuring_your_greenstone_site">
+<Title>
+<Text id="1143">ÐÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð²Ð°ÑÐµÐ³ÐŸ Greenstone - ÑÐ°Ð¹ÑÐ°</Text>
+</Title>
+<Content>
+<Text id="1144">Ð ÑÐžÑÑÐµÐŒÐµ Greenstone ÐžÐŒÐµÐµÑÑÑ ÐŽÐ²Ð° ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ Ð°ÑÐ¿ÐµÐºÑÑ Ð²Ð°ÑÐµÐ³ÐŸ Greenstone-ÑÐ°Ð¹ÑÐ°. "ÐÑÐœÐŸÐ²ÐœÐŸÐ¹" ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž main.cfg ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² GSDLHOME/ETC, Ðž ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž "ÑÐ°Ð¹ÑÐ°" gsdlsite.cfg ÐŸÐœ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² GSDLHOME/CGI-BIN. ÐÐ°Ð¶ÐŽÑÐ¹ ÐžÐ· ÑÑÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐŒÐž Ð°ÑÐ¿ÐµÐºÑÐ°ÐŒÐž ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž Ð²ÑÐµÐ³ÐŸ ÑÐ°Ð¹ÑÐ°. ÐÐ±Ð° ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÐœÑ ÑÐŸ ÑÑÑÐ°ÐœÐžÑÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ Greenstone.</Text>
+<Section id="main_configuration_file">
+<Title>
+<Text id="1145">ÐÑÐœÐŸÐ²ÐœÐŸÐ¹ ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="1146">ÐÑÐœÐŸÐ²ÐœÐŸÐ¹ ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž main, cfg ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÐºÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑÐ° ÐºÐ°Ðº ÑÐ°ÑÑÐž Greenstone ÐŽÐ»Ñ Ð¿ÐŸÐ»Ñ Ð·Ð°Ð¿ÑÐŸÑÐŸÐ² Ðž ÐŽÐ»Ñ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÑÑÐ°ÐœÐžÑ. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑ Ð²ÑÐµÐŒ, ÐœÐ°ÑÐžÐœÐ°Ñ ÐŸÑ ÑÐ·ÑÐºÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐžÐœÑÐµÑÑÐµÐ¹Ñ, Ðž Ð·Ð°ÐºÐ°ÐœÑÐžÐ²Ð°Ñ Ñ
+ÑÐ°ÐœÐµÐœÐžÐµÐŒ ÐŽÐ°ÐœÐœÑÑ
+ ÐŸ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐž.</Text>
+<Subsection id="site_maintenance_and_logging">
+<Title>
+<Text id="1147">ÐÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐœÐžÐµ ÑÐ°Ð¹ÑÐ° Ðž ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÑ</Text>
+</Title>
+<Content>
+<Text id="1148">Ð¡ÑÑÐŸÐºÐž Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÑÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÐœÐ° ÑÐŸ, ÐºÐ°Ðº ÐŽÐŸÐ»Ð¶ÐµÐœ ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÑÑÑÑ Ð²Ð°Ñ Greenstone-ÑÐ°Ð¹Ñ, ÐºÐ°ÐºÐžÐµ ÑÑÐµÐŽÑÑÐ²Ð° ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÑÑÑÑ, ÐºÐ°ÐºÐžÐµ ÑÐµÐ³ÐžÑÑÑÐžÑÑÑÑÑÑ ÑÐŸÐ±ÑÑÐžÑ Ðž ÐºÐ°ÐºÐžÐµ ÑÐŸÐŸÐ±ÑÐµÐœÐžÑ Ð¿ÐŸÐ»ÑÑÐ°ÐµÑ ÑÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="configuration_options_for_site_maintenance_and_logging"/> Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÑÑÑÐ¿ÐœÑÐµ ÐŸÐ¿ÑÐžÐž; ÐŸÑÑÐ°Ð»ÑÐœÑÐµ ÐŸÐ¿ÐžÑÐ°ÐœÑ Ð² ÑÐ»ÐµÐŽÑÑÑÐžÑ
+ ÑÐ°Ð·ÐŽÐµÐ»Ð°Ñ
+.</Text>
+<Table id="configuration_options_for_site_maintenance_and_logging">
+<Title>
+<Text id="1149">Ð¯Ð·ÑÐºÐŸÐ²Ð°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ°</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132"/>
+<th width="151">
+<Text id="1150"><b>ÐÐœÐ°ÑÐµÐœÐžÐµ</b></Text>
+</th>
+<th width="246">
+<Text id="1151"><b>ÐŠÐµÐ»Ñ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1152"><i>maintainer</i></Text>
+</th>
+<th width="151">
+<Text id="1153">NULL ÐžÐ»Ðž E-mail Ð°ÐŽÑÐµÑ</Text>
+</th>
+<th width="246">
+<Text id="1154">ÐÐŽÑÐµÑ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ Ð»ÐžÑÐ°, ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÑÑÐµÐ³ÐŸ ÑÐ°Ð¹Ñ, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ñ ÑÐµÐ»ÑÑ ÑÐ²ÐµÐŽÐŸÐŒÐ»ÐµÐœÐžÑ. ÐÑÐ»Ðž NULL, E-mail ÑÐŸÐ±ÑÑÐžÑ Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1155"><i>MailServer</i></Text>
+</th>
+<th width="151">
+<Text id="1156">NULL ÐžÐ»Ðž ÐžÐŒÑ ÑÐµÑÐ²ÐµÑÐ°</Text>
+</th>
+<th width="246">
+<Text id="1157">Ð¡ÐµÑÐ²ÐµÑ ÐžÑÑ
+ÐŸÐŽÑÑÐµÐ¹ Ð¿ÐŸÑÑÑ ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ ÑÐ°Ð¹ÑÐ°. ÐÑÐ»ÐžNULL,       ÑÐŸ       ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ       mail. ÐŽÐŸÐŒÐµÐœ-ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÑÑÐµÐ³ÐŸ ÑÐ°Ð¹Ñ Ð»ÐžÑÐ° (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐµÑÐ»Ðž ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐµÑ ÑÐ°Ð¹Ñ - help@example.com, ÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ - mail.example.com). ÐÑÐ»Ðž ÑÑÐŸ ÐœÐµ ÑÐ°Ð·ÑÐµÑÐµÐœÐŸ ÐŽÐŸÐ¿ÑÑÑÐžÐŒÑÐŒ SMTP-ÑÐµÑÐ²ÐµÑÐŸÐŒ, ÑÐŸ E-mail ÑÐŸÐ±ÑÑÐžÑ ÐœÐµ Ð±ÑÐŽÑÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1158"><i>status</i></Text>
+</th>
+<th width="151">
+<Text id="1159"><i>enabled</i> ÐžÐ»Ðž <i>disabled</i></Text>
+</th>
+<th width="246">
+<Text id="1160">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ, ÐŽÐŸÐ»Ð¶ÐœÐ° Ð»Ðž ÑÑÑÐ°ÐœÐžÑÐ° "ÐÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐœÐžÐµ Ðž Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ" Ð±ÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÐŸÐ¹</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1161"><i>collector</i></Text>
+</th>
+<th width="151">
+<Text id="1162"><i>enabled</i> ÐžÐ»Ðž <i>disabled</i></Text>
+</th>
+<th width="246">
+<Text id="1163">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ, ÐŽÐŸÑÑÑÐ¿ÐœÐ° Ð»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐºÐŸÐœÐµÑÐœÐŸÐ³ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ, ÑÐŸÑÐŒÐžÑÑÑÑÐ°Ñ ÑÑÐµÐŽÑÑÐ²ÐŸ "ÐºÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ°"</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1164"><i>logcgiargs</i></Text>
+</th>
+<th width="151">
+<Text id="1165"><i>true</i> ÐžÐ»Ðž <i>false</i></Text>
+</th>
+<th width="246">
+<Text id="1166">ÐÑÐ»Ðž true, ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ Ñ
+ÑÐ°ÐœÐžÑÑÑ Ð² usage.txt. ÐÑÐ»Ðž true, ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑ
+ ÑÐ°Ð¹ÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1167"><i>usecookies</i></Text>
+</th>
+<th width="151">
+<Text id="1168"><i>true</i> ÐžÐ»Ðž <i>false</i></Text>
+</th>
+<th width="246">
+<Text id="1169">ÑÐŸÐ±ÑÐ°ÐœÐ° (ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ cookies) Ðž Ð·Ð°Ð¿ÐžÑÐ°ÐœÐ° Ð² usage.txt(ÑÑÐŸ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÑÐŸÐ»ÑÐºÐŸ Ð² ÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž logcgiargs Ð¿ÑÐžÐœÐžÐŒÐ°ÐµÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµ true)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1170"><i>LogDateFormat</i></Text>
+</th>
+<th width="151">
+<Text id="1171"><i>LocalTime</i> ÐžÐ»Ðž <br/><i>UTCTime</i> ÐžÐ»Ðž <br/><i>Absolute</i></Text>
+</th>
+<th width="246">
+<Text id="1172">Ð€ÐŸÑÐŒÐ°Ñ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ Ð²ÑÐµÐŒÐµÐœÐž Ð¿ÑÐžÐ¿ÐžÑÐ°ÐœÐ° Ðº ÑÐ°Ð¹Ð»Ñ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐž. LocalTimeÐ¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑ ÑÐŸÑÐŒÐ°Ñ "ÑÐµÑÐ²ÐµÑÐ³ 07 ÐŽÐµÐºÐ°Ð±ÑÑ 12:34 NZDT 2000 ", UTCTIME - ÑÐŸÑ Ð¶Ðµ ÑÐ°ÐŒÑÐ¹ ÑÐŸÑÐŒÐ°Ñ, ÐœÐŸ Ð² GMT (ÑÑÐµÐŽÐœÐµÐŒ Ð²ÑÐµÐŒÐµÐœÐž Ð¿ÐŸ ÐÑÐžÐœÐ²ÐžÑÑ), Ðž absolute- ÑÐµÐ»ÐŸÐµ ÑÐžÑÐ»ÐŸ, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑÑÐµÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÑÐµÐºÑÐœÐŽ Ñ ÐŒÐŸÐŒÐµÐœÑÐ° 00:00:00 01/01/1970 GMT</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1173"><i>LogEvents</i></Text>
+</th>
+<th width="151">
+<Text id="1174"><i>AllEvents</i> ÐžÐ»Ðž <br/><i>CollectorEvents</i><br/> ÐžÐ»Ðž <i>disabled</i></Text>
+</th>
+<th width="246">
+<Text id="1175">Ð ÐµÐ³ÐžÑÑÑÐ°ÑÐžÑ ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÑÐŸÐ±ÑÑÐžÐ¹ Ð² events.txt. AllEvents ÑÐµÐ³ÐžÑÑÑÐžÑÑÐµÑ Ð²ÑÐµ ÑÐŸÐ±ÑÑÐžÑ Greenstone, CollectorEvents ÑÐµÐ³ÐžÑÑÑÐžÑÑÐµÑ ÑÐŸÐ»ÑÐºÐŸ ÑÐŸÐ±ÑÑÐžÑ, ÑÐ²ÑÐ·Ð°ÐœÐœÑÐµ Ñ Collector (ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐŸÐŒ), a disabled ÐœÐµ ÑÐµÐ³ÐžÑÑÑÐžÑÑÐµÑ ÐœÐžÐºÐ°ÐºÐžÑ
+ ÑÐŸÐ±ÑÑÐžÐ¹.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1176"><i>EmailEvents</i></Text>
+</th>
+<th width="151">
+<Text id="1177"><i>enabled</i> ÐžÐ»Ðž <i>disabled</i></Text>
+</th>
+<th width="246">
+<Text id="1178">ÐÑÐ¿ÑÐ°Ð²ÐºÐ° ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ Ð»ÐžÑÑ, ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÑÑÐµÐŒÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ (ÐµÑÐ»Ðž ÐŸÐœ ÐŸÐŽÐžÐœ - ÑÐŒ. ÐµÐ³ÐŸ ÐŸÐ¿ÑÐžÑ), ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐ°Ð·, ÐºÐŸÐ³ÐŽÐ° ÑÑÐŸ-ÑÐŸ ÑÐ»ÑÑÐ°ÐµÑÑÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1179"><i>EmailUserEvents</i></Text>
+</th>
+<th width="151">
+<Text id="1180"><i>enabled</i> ÐžÐ»Ðž <i>disabled</i></Text>
+</th>
+<th width="246">
+<Text id="1181">ÐÑÐ¿ÑÐ°Ð²ÐºÐ° ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð² ÐŸÑÐ²ÐµÑ ÐœÐ° ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐ±ÑÑÐžÑ - ÐœÐ°Ð¿ÑÐžÐŒÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ°, Ð·Ð°ÐºÐ°ÐœÑÐžÐ²Ð°ÑÑÐµÐ³ÐŸ ÐºÐŸÐŒÐ¿ÐŸÐœÐŸÐ²ÐºÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1182"><i>macrofiles</i></Text>
+</th>
+<th width="151">
+<Text id="1183">ÑÐ¿ÐžÑÐŸÐº ÐŒÐ°ÐºÑÐŸ ÐžÐŒÐµÐœ ÑÐ°Ð¹Ð»ÐŸÐ²</Text>
+</th>
+<th width="246">
+<Text id="1184">ÐÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ, ÐºÐ°ÐºÐŸÐ¹ ÐŒÐ°ÐºÑÐŸÑ ÑÐ²Ð»ÑÐµÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒ ÐŽÐ»Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Greenstone</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+<Subsection id="language_support">
+<Title>
+<Text id="1185">Ð¯Ð·ÑÐºÐŸÐ²Ð°Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐ°</Text>
+</Title>
+<Content>
+<Text id="1186">ÐÐ²Ð° Ð²ÐžÐŽÐ° Ð²Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÐ¹ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž main.cfg Ð·Ð°ÑÑÐ°Ð³ÐžÐ²Ð°ÑÑ Ð¿ÑÑÐž ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐ·ÑÐºÐŸÐ². ÐÐœÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ, ÐºÐ°ÐºÐžÐµ ÑÐ·ÑÐºÐž Ðž ÐºÐŸÐŽÐžÑÐŸÐ²ÐºÐž ÑÐ²Ð»ÑÑÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ Preferences page. Ð¡ÑÑÐŸÐºÐž Encoding ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÑÐžÐ¿Ñ ÐºÐŸÐŽÐžÑÐŸÐ²ÐºÐž ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð²ÑÐ±ÑÐ°ÐœÑ. Ð¡ÑÑÐŸÐºÐž Language ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ, ÐºÐ°ÐºÐžÐµ ÑÐ·ÑÐºÐž ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð²ÑÐ±ÑÐ°ÐœÑ (ÐºÐŸÐœÐµÑÐœÐŸ, ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÐ³ÐŸ ÑÐ·ÑÐºÐ° ÐŽÐŸÐ»Ð¶ÐœÐ° ÑÑÑÐµÑÑÐ²ÐŸÐ²Ð°ÑÑ ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÐ° ÑÐ·ÑÐºÐ°).</Text>
+<Text id="1187">Ð¡ÑÑÐŸÐºÐ° Encoding ÐŒÐŸÐ¶ÐµÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÑÐµÑÑÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÑ: shortname, longname, map Ðž multibyte. Shortname - ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ ÐŒÐµÑÐºÐ° ÐœÐ°Ð±ÐŸÑÐ° ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ², Ðž ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐœÐ° ÐŽÐ»Ñ Ð²ÑÐµÐ³ÐŸ ÐºÐŸÐŽÐžÑÐŸÐ²Ð°ÐœÐžÑ. Longname ÐŽÐ°ÐµÑ ÐžÐŒÑ ÐºÐŸÐŽÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐºÐŸÑÐŸÑÐŸÐµ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐŸ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ Ð²ÑÐ±ÐŸÑÐ° Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÐ¹ -Preferences page. ÐÑÐ»Ðž ÑÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŸÑÑÑÑÑÑÐ²ÑÐµÑ, ÑÐŸ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ shortname. ÐÐœÐ°ÑÐµÐœÐžÐµ ÑÐ°Ñ Ð¿ÑÐžÐœÑÐŽÐžÑÐµÐ»ÑÐœÐŸ ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÐºÐŸÐŽÐžÑÐŸÐ²ÐŸÐº, ÐºÑÐŸÐŒÐµ utf8, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÐœÐ° Ð²ÐœÑÑÑÐµÐœÐœÐµ (Ðž Ð²ÑÐµÐ³ÐŽÐ° ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ ÐŽÐŸÐ¿ÑÑÑÐžÐŒÐ°). ÐÐœÐ°ÑÐµÐœÐžÐµ multibyte ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð±ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐŸ ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÐœÐ°Ð±ÐŸÑÐŸÐ² ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÑÑÐµÐ±ÑÑÑ Ð±ÐŸÐ»ÑÑÐµ, ÑÐµÐŒ ÐŸÐŽÐžÐœ Ð±Ð°Ð¹Ñ ÐœÐ° ÑÐžÐŒÐ²ÐŸÐ». Ð€Ð°Ð¹Ð» main.cfg ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ ÐºÐŸÐŽÐžÑÐŸÐ²ÐŸÐº, Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ Ð±ÑÐ»ÐŸ Ð¿ÑÐŸÐºÐŸÐŒÐŒÐµÐœÑÐžÑÐŸÐ²Ð°ÐœÐŸ. Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ¿ÑÑÑÐžÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐºÐŸÐŽÐžÑÐŸÐ²ÐŸÐº, ÑÐŽÐ°Ð»ÐžÑÐµ ÑÐžÐŒÐ²ÐŸÐ» ÐºÐŸÐŒÐŒÐµÐœÑÐ°ÑÐžÑ "#".</Text>
+<Text id="1188">ÐÐ°Ð¶ÐŽÐ°Ñ ÑÑÑÐŸÐºÐ° Language ÐŒÐŸÐ¶ÐµÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÑÑÐž Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÑ, shortname, longname, Ðž default_encoding. Shortname - ÐŽÐ²ÑÑ
+Ð±ÑÐºÐ²ÐµÐœÐœÐŸÐµ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐžÐµ ÑÐ·ÑÐºÐ° Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ ÑÑÐµÐ±ÐŸÐ²Ð°ÐœÐžÑÐŒÐž ISO 639. Longname -ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐ·ÑÐºÐ° ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ Ð²ÑÐ±ÐŸÑÐ° Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÐ¹ - Preferences page. ÐÑÐž ÐŸÑÑÑÑÑÑÐ²ÐžÐž ÑÑÐŸÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑ, Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ shortname. ÐÐ¿ÑÐžÑ default_encoding ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ, ÑÑÐŸÐ±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐžÑÐµÐ»ÑÐœÑÑ ÐºÐŸÐŽÐžÑÐŸÐ²ÐºÑ ÐŽÐ»Ñ Ð²ÑÐ±ÑÐ°ÐœÐœÐŸÐ³ÐŸ ÑÐ·ÑÐºÐ°.</Text>
+</Content>
+</Subsection>
+<Subsection id="page_parameters_and_cgi_arguments">
+<Title>
+<Text id="1189">ÐÐ°ÑÐ°ÐŒÐµÑÑÑ ÑÑÑÐ°ÐœÐžÑ Ðž  CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="1190">ÐÐ°ÑÐ°ÐŒÐµÑÑÑ ÑÑÑÐ°ÐœÐžÑÑ Ðž CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐ² ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ Ð²ÐœÑÑÑÐž ÑÐ°Ð¹Ð»Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž main.cfg. ÐÐµÑÐœÐµÐŒÑÑ Ðº ÑÐžÑÑÐœÐºÑ <CrossRef target="Figure" ref="using_the_cgiargsinfoclass_from_pageactioncpp"/>, ÐžÐ· ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ Ð²ÐžÐŽÐœÐŸ, ÑÑÐŸ Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ CGI -Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐ² ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž C++. ÐÐŽÐœÐ°ÐºÐŸ, ÐžÐœÐŸÐ³ÐŽÐ° Ð¿ÐŸÐ»ÐµÐ·ÐœÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÐœÐŸÐ²ÑÐµ Ð°ÑÐ³ÑÐŒÐµÐœÑÑ ÐžÐ»Ðž ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ Ð²ÐŸ Ð²ÑÐµÐŒÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž, ÑÐ°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ ÐžÐ·Ð±ÐµÐ³Ð°Ñ Ð¿ÐŸÑÑÐµÐ±ÐœÐŸÑÑÐž Ð¿ÐµÑÐµÑÑÐ°ÐœÑÐ»ÐžÑÐŸÐ²Ð°ÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ.</Text>
+<Text id="1191">Ð§ÑÐŸÐ±Ñ ÑÐŽÐµÐ»Ð°ÑÑ ÑÑÐŸ, Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŸÐ¿ÑÐžÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž cgiarg. Cgiarg ÐŒÐŸÐ¶ÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÐŸ ÑÐµÑÑÐž Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ²; shortname, longname, multiplechar, argdefault, defaultstatus Ðž savedarginfo. Ð­ÑÐž Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑ Ð²Ð°ÑÐžÐ°ÐœÑÐ°ÐŒ CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐ°, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐŒ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Section" ref="receptionist"/>. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð² Ð·ÐœÐ°ÑÐµÐœÐžÐž Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ main.cfg ÐŸÐ¿ÑÐžÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž cgiarg ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ, ÑÑÐŸÐ±Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÑ
+ Ð° Ðž Ñ CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐ² ÐŽÐ»ÑÑ Ðž home ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸ.</Text>
+<Text id="1192">ÐÐ°ÑÐ°ÐŒÐµÑÑÑ ÑÑÑÐ°ÐœÐžÑÑ - ÑÐ°ÑÑÐœÑÐµ ÑÐ»ÑÑÐ°Ðž CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ°ÐŒ Ð² ÑÐ°Ð¹Ð»Ð°Ñ
+ ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÑ Greenstone. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑ /ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÐµÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ / = Ð² ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ð°Ñ
+. Ð§ÑÐŸÐ±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ CGI-Ð°ÑÐ³ÑÐŒÐµÐœÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ°ÐºÐ¶Ðµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐŒ ÑÑÑÐ°ÐœÐžÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐŸÐ¿ÑÐžÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž pageparam.</Text>
+<Text id="1193">ÐÑÑÑÐžÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÑÐ·ÐœÐ°ÑÑ ÐŸ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð²Ð°ÑÐžÐ°ÐœÑÐ°Ñ
+ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž, Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÑ
+ Ð² ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž main-cfg, ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ ÑÐºÑÐ¿ÐµÑÐžÐŒÐµÐœÑÐžÑÐŸÐ²Ð°ÑÑ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ Ñ ÑÑÐžÐŒ ÑÐ°Ð¹Ð»ÐŸÐŒ. ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÑÐŸ, ÑÑÐŸ ÐµÑÐ»Ðž Ð²Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ Ð»ÐŸÐºÐ°Ð»ÑÐœÑÑ Windows-Ð²ÐµÑÑÐžÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone, ÑÐŸ Ð¿ÑÐµÐ¶ÐŽÐµ ÑÐµÐŒ Ð»ÑÐ±ÑÐµ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ ÑÐ°Ð¹Ð»ÐŸÐ² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž Ð²ÑÑÑÐ¿ÑÑ Ð² ÑÐžÐ»Ñ, Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð±ÑÐŽÐµÑ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÐžÑÑ ÑÐµÑÐ²ÐµÑ.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="site_configuration_file">
+<Title>
+<Text id="1194"> Ð€Ð°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÑÐ°Ð¹ÑÐ°</Text>
+</Title>
+<Content>
+<Table id="lines_in_gsdlsitecfg">
+<Title>
+<Text id="1195">Lines in <i>gsdlsite.cfg</i></Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="1196"><b>Line</b></Text>
+</th>
+<th width="397">
+<Text id="1197"><b>Function</b></Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1198"><i>gsdlhome</i></Text>
+</th>
+<th width="397">
+<Text id="1199">A path to the <i>GSDLHOME</i> directory.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1200"><i>httpprefix</i></Text>
+</th>
+<th width="397">
+<Text id="1201">The web address of <i>GSDLHOME</i>. If the document root on your web server is set to <i>GSDLHOME</i> you do not need this line.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1202"><i>httpimage</i></Text>
+</th>
+<th width="397">
+<Text id="1203">The web address of the directory containing the images for the user interface. If your web-server's document root is set to <i>GSDLHOME</i> this will be <i>/images</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1204"><i>gwcgi</i></Text>
+</th>
+<th width="397">
+<Text id="1205">The web address of this cgi script (usually ends in <i>library</i>). This is not needed if your web server sets the environment variable <i>SCRIPT_NAME</i>.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="1206"><i>maxrequests</i></Text>
+</th>
+<th width="397">
+<Text id="1207">(Only applies if <i>fast-cgi</i> is in use.) The number of requests fast-cgi should process before it exits. When debugging the library this should be set to a small number, otherwise it should be a large number.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="1208">Ð€Ð°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÑÐ°Ð¹ÑÐ° gsdlsite.cfg ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÐµ, ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐŒ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµÐŒ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ðž Ð²ÐµÐ±-ÑÐµÑÐ²ÐµÑÐŸÐŒ Ð²ÐŸ Ð²ÑÐµÐŒÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ Ðž Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÑÐŸÐŒ Ð¶Ðµ ÑÐ°ÐŒÐŸÐŒ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ðµ, ÑÑÐŸ Ðž Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°. Ð¢Ð°Ð±Ð»ÐžÑÐ° <CrossRef target="Table" ref="lines_in_gsdlsitecfg"/> ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÑÑÑÐŸÐºÐž Ð² ÑÑÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ; Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐµÐµ ÐŸÐœÐž ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑÑÑ Ð² Ð Ð°Ð·ÐŽÐµÐ»Ðµ 5 ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÐž - ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð¿ÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_a_stl">
+<Title>
+<Text id="1209">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ Ð: Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° ÑÐ°Ð±Ð»ÐŸÐœÐŸÐ² C++</Text>
+</Title>
+<Content>
+<Text id="1210">Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° ÐšÐ°Ð±Ð»ÐŸÐœÐŸÐ² (STL) - ÑÐžÑÐŸÐºÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° C++ ÐŸÑ Silicon Graphics (www.sgi.com). Ð ÐŽÐ°ÐœÐœÐŸÐŒ ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ ÐºÑÐ°ÑÐºÐžÐ¹ ÐŸÐ±Ð·ÐŸÑ ÐºÐ»ÑÑÐµÐ²ÑÑ
+ ÑÐ°ÑÑÐµÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð²ÑÑÐŽÑ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ Greenstone. ÐÐ»Ñ ÐŸÐ·ÐœÐ°ÐºÐ»ÐŒÐ»ÐµÐœÐžÑ Ñ Ð±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐ»ÐœÑÐŒ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµÐŒ ÐŸÐ·ÐœÐ°ÐºÐŸÐŒÑÑÐµÑÑ Ñ ÐŸÑÐžÑÐžÐ°Ð»ÑÐœÑÐŒ ÑÐ¿ÑÐ°Ð²ÐŸÑÐœÑÐŒ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµÐŒ STL, ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒ Ð² ÑÐµÐ¶ÐžÐŒÐµ on-line ÐœÐ° ÑÐ°Ð¹ÑÐµ www.sgi.com, ÐžÐ»Ðž Ñ ÐŸÐŽÐœÐžÐŒ ÐžÐ· ÐŒÐœÐŸÐ³ÐžÑ
+ STL-ÑÑÐµÐ±ÐœÐžÐºÐŸÐ², ÐœÐ°Ð¿ÑÐžÐŒÐµÑ Josuttis (1999). </Text>
+<Text id="1211">ÐÐ°Ðº Ð¿ÑÐµÐŽÐ¿ÐŸÐ»Ð°Ð³Ð°ÐµÑ ÑÐ»ÐŸÐ²ÐŸ "ÑÐ°Ð±Ð»ÐŸÐœ", STL - ÐœÐµ ÑÐŸÐ»ÑÐºÐŸ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° ÐŸÐ±ÑÐµÐºÑÐœÑÑ
+ ÐŒÐŸÐŽÑÐ»ÐµÐ¹ plug-and-use (Ð¿ÐŸÐŽÐºÐ»ÑÑÐ°Ð¹-Ðž-ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹). ÐÐŒÐµÑÑÐµ Ñ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒÐŸÐŒ ÑÐ°Ð±Ð»ÐŸÐœÐŸÐ² Ð² C++, ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑÑÑ ÑÐŸÑÑÐŒ ÐŽÐ»Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÑÐŸÐ², ÑÑÐŸÐ±Ñ ÑÐ°Ð·ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÑÑ ÐžÑ
+ ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÑÐµ ÐŸÐ±ÑÐµÐºÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ Ð°Ð»Ð³ÐŸÑÐžÑÐŒÐžÑÐµÑÐºÐžÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž, ÑÐµÐ°Ð»ÐžÐ·ÐŸÐ²Ð°ÐœÐœÑÐµ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ STL. Ð ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐµ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑÑÑ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÐ¹ ÑÑÐŸÐ²ÐµÐœÑ ÑÐ»ÐŸÐ¶ÐœÐŸÑÑÐž, ÐœÐŸ ÑÑÐŸ ÑÑÐŸÐžÑ ÑÐŸÐ³ÐŸ.</Text>
+<Text id="1212">ÐÐŸÐŒÐŸÑÑ Ð¿ÐŸÐœÑÑÑ Ð¿ÑÐ³ÑÐ°ÐŒÐŒÑ Greenstone Ð²Ð°ÐŒ Ð¿ÐŸÐŒÐŸÐ³ÑÑ Ð¿ÐŸÐŽÐ±ÐŸÑÐºÐž, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÑÐµ Ð² ÑÑÐŸÐŒ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ, ÐºÐŸÑÐŸÑÑÐµ ÐŒÑ ÑÐœÐ°Ð±ÐŽÐžÐ»Ðž ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÐŒ Ð¿ÑÐžÐŒÐµÑÐ°ÐŒ ÐŸÐ±ÑÑÐ°ÑÑÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ Ð¿ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ STL.</Text>
+<Section id="lists">
+<Title>
+<Text id="1213">Ð¡Ð¿ÐžÑÐºÐž (Lists)</Text>
+</Title>
+<Content>
+<Figure id="programming_a_list_of_integers" class="withLineNumber">
+<Title>
+<Text id="1214">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐ¿ÐžÑÐºÐ° ÑÐµÐ»ÑÑ
+ ÑÐžÑÐµÐ»</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>#define nil 0</CodeLine>
+<CodeLine/>
+<CodeLine>struct intlist {</CodeLine>
+<CodeLine>   int val;</CodeLine>
+<CodeLine>   struct intlist* next;</CodeLine>
+<CodeLine>};</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_list(intlist* head)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   int total = 0;</CodeLine>
+<CodeLine>   intlist* curr = head;</CodeLine>
+<CodeLine>   while (curr!=nil)</CodeLine>
+<CodeLine>   {</CodeLine>
+<CodeLine>       total += curr-&gt;val;</CodeLine>
+<CodeLine>       curr = curr-&gt;next;</CodeLine>
+<CodeLine>   }</CodeLine>
+<CodeLine/>
+<CodeLine>   return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>void main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   intlist node1 = { 5, nil };</CodeLine>
+<CodeLine>   intlist node2 = { 4, nil };</CodeLine>
+<CodeLine>   node2.next = &amp;node1;</CodeLine>
+<CodeLine/>
+<CodeLine>   int total = total_int_list(&amp;node2);</CodeLine>
+<CodeLine>  cout &lt;&lt; " List items total to: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="1215">Ð¡ÐœÐ°ÑÐ°Ð»Ð° ÐŒÑ ÐžÐ·ÑÑÐžÐŒ ÐŽÐ²Ðµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÐºÐŸÑÐŸÑÑÐµ ÑÐµÐ°Ð»ÐžÐ·ÑÑÑ ÑÐµÐ»ÐŸÑÐžÑÐ»ÐµÐœÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº. ÐÑÐµÐ²ÐŸÐœÐ°ÑÐ°Ð»ÑÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐŸÑÐœÐŸÐ²ÐœÑÐµ ÑÐžÐ¿Ñ C++ (Ð¿ÑÑÑ "Ð¿ÐŸ Ð¿ÑÐŸÑÐŸÑÐµÐœÐœÐŸÐ¹ ÐŽÐŸÑÐŸÐ¶ÐºÐµ"), ÐŽÐ°Ð»ÐµÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ STL. Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="programming_a_list_of_integers"/> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÐºÐŸÑÐŸÑÐŸÐµ ÐœÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ STL. Ð¡ÑÑÐŸÐºÐž 5-8 ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÐŸÑÐœÐŸÐ²ÐœÑÑ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+, ÐºÐŸÑÐŸÑÑÑ ÐŒÑ ÑÐŸÐ±ÐžÑÐ°ÐµÐŒÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ: Ð¿ÐŸÐ»Ðµ val ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑ ÑÐµÐ»ÐŸÑÐžÑÐ»ÐµÐœÐœÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ, a next ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÑÐ»ÐµÐŽÑÑÑÐžÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ Ð² ÑÐ¿ÐžÑÐºÐµ - ÐºÐ»Ð°ÑÑÐžÑÐµÑÐºÐŸÐµ Ð²ÐŸÐ¿Ð»ÐŸÑÐµÐœÐžÐµ ÑÐ¿ÐžÑÐºÐ° ÑÐ²ÑÐ·ÐµÐ¹.</Text>
+<Text id="1216">Ð§ÑÐŸÐ±Ñ Ð¿ÑÐŸÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+, ÐŸÑÐœÐŸÐ²ÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° (ÑÑÑÐŸÐºÐž 23-32), ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ ÑÐµÐ»ÐŸÑÐžÑÐ»ÐµÐœÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº Ñ ÑÐ»ÐµÐŒÐµÐœÑÐ°ÐŒÐž [5, 4]. Ð¢ÐŸÐ³ÐŽÐ° Ð²ÑÐ·ÑÐ²Ð°ÐµÑÑÑ ÑÑÐœÐºÑÐžÑ total_int_list (ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐ°Ñ Ð² ÑÑÑÐŸÐºÐ°Ñ
+ 10-21), ÐºÐŸÑÐŸÑÐ°Ñ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐµÐµ ÐµÐŽÐžÐœÑÑÐ²ÐµÐœÐœÐŸÐ³ÐŸ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ° Ð±ÐµÑÐµÑ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ñ ÐœÐ° Ð²ÐµÑÑÐžÐœÑ ÑÐ¿ÐžÑÐºÐ° Ðž ÑÑÐŒÐŒÐžÑÑÐµÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ Ð² ÐœÐµÐŒ. ÐÐŸÐ·Ð²ÑÐ°ÑÐµÐœÐœÑÐ¹ ÐŸÑÐ²ÐµÑ (Ð² ÐœÐ°ÑÐµÐŒ Ð¿ÑÐžÐŒÐµÑÐµ 9) Ð²ÑÐ²ÐŸÐŽÐžÑÑÑ ÐœÐ° ÑÐºÑÐ°Ðœ.</Text>
+<Text id="1217">ÐÑÐœÐŸÐ²ÐœÐ°Ñ ÑÐ°Ð±ÐŸÑÐ° ÐŽÐŸÑÑÐžÐ³Ð°ÐµÑÑÑ ÑÑÑÐŸÐºÐ°ÐŒÐž 12-18. Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ ÐœÐµÐ±ÐŸÐ»ÑÑÐ°Ñ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÑ: Ð»ÐŸÐºÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐµÑÐµÐŒÐµÐœÐœÐ°Ñ total ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐžÐ²Ð°ÐµÑ nil Ðž ÑÐžÐ³Ð³, ÑÑÐŸÐ±Ñ ÑÐºÐ°Ð·Ð°ÑÑ ÐœÐ° ÐœÐ°ÑÐ°Ð»ÐŸ ÑÐ¿ÐžÑÐºÐ°. Ð¢ÐŸÐ³ÐŽÐ° ÑÐžÐºÐ» Ñ ÑÑÐ»ÐŸÐ²ÐžÐµÐŒ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑ ÑÐµÐºÑÑÐžÐ¹ ÑÐµÐ»ÐŸÑÐžÑÐ»ÐµÐœÐœÑÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ Ð² ÑÐ¿ÐžÑÐŸÐº ÐŽÐ»Ñ ÐŸÐ±ÑÐµÐ³ÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ (total += curr. >val;) Ð¿ÐµÑÐµÐŽ Ð¿ÐµÑÐµÑ
+ÐŸÐŽÐŸÐŒ Ðº ÑÐ»ÐµÐŽÑÑÑÐµÐŒÑ ÑÐ»ÐµÐŒÐµÐœÑÑ (curr = curr. >next;). ÐŠÐžÐºÐ» Ñ ÑÑÐ»ÐŸÐ²ÐžÐµÐŒ Ð·Ð°ÐºÐ°ÐœÑÐžÐ²Ð°ÐµÑÑÑ, ÐºÐŸÐ³ÐŽÐ° curr ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ ÑÐ°Ð²ÐœÑÐŒ nil, Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°Ñ, ÑÑÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² ÐŽÐ»Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž Ð±ÐŸÐ»ÑÑÐµ ÐœÐµ ÐŸÑÑÐ°Ð»ÐŸÑÑ.</Text>
+<Figure id="programming_a_list_of_integers_using_stl">
+<Title>
+<Text id="1218">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐ¿ÐžÑÐºÐ° ÑÐµÐ»ÑÑ
+ ÑÐžÑÐµÐ» Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ STL</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine>#include &lt;list&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_list(list&lt;int&gt;* head)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   int total = 0;</CodeLine>
+<CodeLine>   list&lt;int&gt;::iterator curr = head-&gt;begin();</CodeLine>
+<CodeLine>   while (curr!=head-&gt;end())</CodeLine>
+<CodeLine>   {</CodeLine>
+<CodeLine>       total += *curr;</CodeLine>
+<CodeLine>       curr++;</CodeLine>
+<CodeLine>   }</CodeLine>
+<CodeLine/>
+<CodeLine>   return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>void main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   list&lt;int&gt; vals;</CodeLine>
+<CodeLine>   vals.push_back(5);</CodeLine>
+<CodeLine>   vals.push_back(4);</CodeLine>
+<CodeLine/>
+<CodeLine>   int total = total_int_list(&amp;vals);</CodeLine>
+<CodeLine>   cout &lt;&lt; " List items total to: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>}</CodeLine>
+</Figure>
+<Text id="1219">Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="programming_a_list_of_integers_using_stl"/> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÐºÐ²ÐžÐ²Ð°Ð»ÐµÐœÑÐœÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÑ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ STL. ÐÐŸÐ»ÑÑÐµ ÐœÐµÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÑÑ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ°ÐœÐœÑÑ
+ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ; Ð²ÑÐµ, ÑÑÐŸ ÑÐ²Ð»ÑÐµÑÑÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÐŒ - ÑÑÐŸ ffinclude &lt;list&gt; ÑÐºÐ°Ð·Ð°ÐœÐžÐµ Ð² ÑÑÑÐŸÐºÐµ 2, ÐºÐŸÑÐŸÑÐŸÐµ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð²ÐµÑÑÐžÑ ÑÐ°Ð±Ð»ÐŸÐœÐ° ÐŽÐ»Ñ ÑÐ¿ÐžÑÐºÐ°, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐ³ÐŸ Ð² STL. ÐÐ±ÑÐµÐºÑ ÐœÐ°Ð·ÑÐ²Ð°ÑÑ "ÐºÐ»Ð°ÑÑ-ÐºÐŸÐœÑÐµÐ¹ÐœÐµÑ", Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ, ÐºÐŸÐ³ÐŽÐ° ÐŒÑ ÐŸÐ±ÑÑÐ²Ð»ÑÐµÐŒ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÑ ÑÑÐŸÐ³ÐŸ ÑÐžÐ¿Ð°, ÐŒÑ ÑÐ°ÐºÐ¶Ðµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÐŒ ÑÐžÐ¿, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐŒÑ Ñ
+ÐŸÑÐžÐŒ ÐµÐµ ÑÐŸÑ
+ÑÐ°ÐœÐžÑÑ. Ð ÑÑÑÐŸÐºÐµ 19 ÑÐµÐ»ÐŸÑÐžÑÐ»ÐµÐœÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº ÑÐµÐ°Ð»ÐžÐ·ÐŸÐ²Ð°Ðœ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÐ° list&lt;int&gt; vals;. Ð­Ð»ÐµÐŒÐµÐœÑÑ ÐŒÐŸÐ¶ÐœÐŸ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ Ðº ÐŸÐ±ÑÐµÐºÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑÐœÐºÑÐžÑ-ÑÐ»ÐµÐœ push_back(), ÐºÐ°Ðº ÑÑÐŸ ÑÐŽÐµÐ»Ð°ÐœÐŸ Ð² ÑÑÑÐŸÐºÐ°Ñ
+ 20-21.</Text>
+<Text id="1220">ÐÑÐœÐŸÐ²ÐœÐ°Ñ ÑÐ°Ð±ÐŸÑÐ° Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐ° ÑÑÑÐŸÐºÐ°ÐŒÐž 6-12. ÐÑÑÑ Ð²ÑÐµ ÐµÑÐµ ÐŽÐ²Ðµ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž Ðž ÑÐžÐºÐ» Ñ ÑÑÐ»ÐŸÐ²ÐžÐµÐŒ, ÐœÐŸ ÐŸÑÐ»ÐžÑÐ°ÑÑÐžÐ¹ÑÑ ÐŸÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÐŸÐ³ÐŸ Ð² Ð¿ÑÐµÐŽÑÐŽÑÑÐµÐŒ ÑÐ»ÑÑÐ°Ðµ. ÐÐŸÐ²ÑÐ¹ ÑÐžÐœÑÐ°ÐºÑÐžÑ ÐžÐŒÐµÐµÑ ÐœÐµÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÑÐµÐ³ÐŸ ÑÐŸ ÑÑÐ°ÑÑÐŒ. ÐÐ»ÑÑÐµÐ²ÑÐŒ ÐŒÐŸÐŒÐµÐœÑÐŸÐŒ ÑÑÐŸÐ³ÐŸ ÐœÐŸÐ²ÐŸÐ³ÐŸ ÑÐ¿ÐŸÑÐŸÐ±Ð° ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÐµÑÐµÐŒÐµÐœÐœÐ°Ñ ÑÐžÐ¿Ð° iterator (ÑÑÑÐŸÐºÐ° 7). Ð STL ÐŒÐœÐŸÐ³ÐŸ ÐºÐ»Ð°ÑÑÐŸÐ² Ð²ÐºÐ»ÑÑÐ°ÑÑ ÑÐžÐ¿Ñ iterator, ÑÑÐŸÐ±Ñ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÑÑ ÐŸÐŽÐœÐŸÑÐŸÐŽÐœÑÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÑÐ°Ð±ÐŸÑÑ ÑÐµÑÐµÐ· Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸÑÑÑ ÐºÐŸÐœÑÐµÐ¹ÐœÐµÑÐœÑÑ
+ ÐŸÐ±ÑÐµÐºÑÐŸÐ². ÐÐµÑÐ²ÑÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐµÐœ Ñ begin(), Ðž ÑÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐžÐœ - Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ Ñ end(). ÐÐµÑÐµÐŒÐµÑÐµÐœÐžÐµ Ðº ÑÐ»ÐµÐŽÑÑÑÐµÐŒÑ ÑÐ»ÐµÐŒÐµÐœÑÑ ÐŽÐŸÑÑÐžÐ³ÐœÑÑÐŸ ÐŸÐ¿ÐµÑÐ°ÑÐžÐµÐ¹ Ð¿ÑÐžÑÐ°ÑÐµÐœÐžÑ ++, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐµÑÐµÐ³ÑÑÐ¶ÐµÐœÐ° ÐºÐ»Ð°ÑÑÐŸÐŒ iterator, ÑÑÐŸÐ±Ñ ÐŸÑÑÑÐµÑÑÐ²ÐžÑÑ ÑÑÑ Ð·Ð°ÐŽÐ°ÑÑ, Ðž Ðº Ð·ÐœÐ°ÑÐµÐœÐžÑ, ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÐŸÐŒÑ ÑÐ°ÐŒ, ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑÑ ÑÐµÑÐµÐ· ÑÐ°Ð·ÑÐŒÐµÐœÐŸÐ²Ð°ÐœÐžÐµ (*ÑÐžÐ³Ð³ ÐœÐ° ÑÑÑÐŸÐºÐµ 10), ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ°ÐºÐ¶Ðµ ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÐµÑÐµÐ³ÑÑÐ¶ÐµÐœÐœÑÐŒ.</Text>
+<Text id="1221">STL-ÑÐµÐ°Ð»ÐžÐ·Ð°ÑÐžÑ ÑÑÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐœÐµÐŒÐœÐŸÐ³ÐŸ ÐŒÐµÐœÑÑÐµ, ÑÐµÐŒ ÐŸÐ±ÑÑÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° (25 ÑÑÑÐŸÐº Ð¿ÑÐŸÑÐžÐ² 31). Ð­ÑÐŸ ÐŽÐŸÑÑÐžÐ¶ÐµÐœÐžÐµ ÐœÐ°ÐžÐ±ÐŸÐ»ÐµÐµ Ð²Ð°Ð¶ÐœÐŸ ÐŽÐ»Ñ Ð±ÐŸÐ»ÑÑÐžÑ
+ Ð¿ÑÐŸÐµÐºÑÐŸÐ², Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŸÐ±ÑÐµÐºÑ list STL Ð±ÐŸÐ»ÐµÐµ ÐŒÐŸÑÐœÑÐ¹, ÑÐµÐŒ ÐžÐ»Ð»ÑÑÑÑÐžÑÑÐµÐŒÑÐ¹ ÐœÐ°ÐŒÐž Ð¿ÑÐžÐŒÐµÑ. ÐÐŸÐ·ÑÐŒÐµÐŒ Ðº Ð¿ÑÐžÐŒÐµÑÑ, ÐŽÐ²ÐŸÐ¹ÐœÐŸÐ¹ ÑÐ²ÑÐ·Ð°ÐœÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐŸÑÐŒ Ð²ÑÑÐ°Ð²ÐºÐž Ðž ÑÐŽÐ°Ð»ÐµÐœÐžÑ - ÐºÐŸÐµ-ÑÑÐŸ, ÑÑÐŸ ÑÑÐµÐ±ÐŸÐ²Ð°Ð»ÐŸ Ð±Ñ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÑ
+ ÑÑÐžÐ»ÐžÐ¹ Ð¿ÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŽÐŸÐ¿ÐŸÐ»ÐµÐœÐžÐ¹ Ðº ÐŸÑÐœÐŸÐ²ÐœÐŸÐ¹ ÑÐµÐ»ÐŸÑÐžÑÐ»ÐµÐœÐœÐŸÐ¹ Ð²ÐµÑÑÐžÐž ÑÐ¿ÐžÑÐºÐ°.</Text>
+<Text id="1222">ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ, ÑÑÐŸ Ð¿Ð°ÑÐ°ÐŒÐµÑÑ ÐŽÐ»Ñ total_int_list ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="programming_a_list_of_integers_using_stl"/> Ð±ÑÐ» ÑÐµÐ°Ð»ÐžÐ·ÐŸÐ²Ð°Ðœ ÐºÐ°Ðº ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ñ, ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐŸÐ²Ð°Ð²ÑÐžÐ¹ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ñ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐŒÑ Ð² total_int_list ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="programming_a_list_of_integers"/>. Ð STL Ð·Ð°ÑÐ°ÑÑÑÑ Ð±ÐŸÐ»ÐµÐµ ÐµÑÑÐµÑÑÐ²ÐµÐœÐœÐŸ (Ðž Ð±ÐŸÐ»ÐµÐµ Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÐŸ) ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÑÑÐ»ÐºÐž, Ð° ÐœÐµ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ðž. Ð¢ÐŸÐ³ÐŽÐ° Ð¿Ð°ÑÐ°ÐŒÐµÑÑ ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ list&lt;int&gt;&amp; head, Ðž ÐµÐ³ÐŸ ÑÑÐœÐºÑÐžÐž-ÑÐ»ÐµÐœÑ Ð²ÑÐ·ÑÐ²Ð°ÑÑÑÑ ÑÐžÐœÑÐ°ÐºÑÐžÑÐŸÐŒ head, begin 0; Ðž ÑÐ°Ðº ÐŽÐ°Ð»ÐµÐµ.</Text>
+</Content>
+</Section>
+<Section id="maps">
+<Title>
+<Text id="1223">Maps</Text>
+</Title>
+<Content>
+<Text id="1224">ÐÑÐž ÑÐµÐ°Ð»ÐžÐ·Ð°ÑÐžÐž ÑÐžÑÑÐµÐŒÑ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐºÐž, Ð¿ÐŸÐ»ÐµÐ·ÐœÐŸ ÐžÐŒÐµÑÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐžÑ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² Ð² ÐŒÐ°ÑÑÐžÐ²Ðµ, ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐŒ ÑÐµÐºÑÑÐŸÐ²ÑÐŒÐž ÑÑÑÐŸÐºÐ°ÐŒÐž, Ð° ÐœÐµ ÑÐžÑÐ»ÐŸÐ²ÑÐŒÐž ÐžÐœÐŽÐµÐºÑÐ°ÐŒÐž. Ð Greenstone, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÑÑÐŸ ÐŸÑÐµÐœÑ ÑÐ¿ÑÐŸÑÐ°ÐµÑ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐžÐµ ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»ÐŸÐ², ÐºÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐŸÐœÐž ÑÑÐžÑÐ°Ð»ÐžÑÑ, Ðž ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž. Ð¢ÐžÐ¿ ÐŽÐ°ÐœÐœÑÑ
+, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ ÑÐ°ÐºÐŸÐ¹ ÐŽÐŸÑÑÑÐ¿, ÐœÐ°Ð·ÑÐ²Ð°ÑÑ associative array (Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÐŒ ÐŒÐ°ÑÑÐžÐ²ÐŸÐŒ), Ðž ÐŸÐœ ÑÐ°ÑÑÐŸ Ð²ÑÑÑÐ°ÐžÐ²Ð°ÐµÑÑÑ Ð² ÑÐŸÐ²ÑÐµÐŒÐµÐœÐœÑÐµ ÑÐ·ÑÐºÐž Ð²ÑÑÐŸÐºÐŸÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ. ÐÐœ ÑÐ°ÐºÐ¶Ðµ ÐžÐ·Ð²ÐµÑÑÐµÐœ Ð¿ÐŸÐŽ ÐžÐŒÐµÐœÐµÐŒ hash array (ÐŸÑÐŸÐ±ÐµÐœÐœÐŸ Ð² Perl), ÑÐ°Ðº ÐºÐ°Ðº Ñ
+ÐµÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ - ÐœÐŸÑÐŒÐ°Ð»ÑÐœÐ°Ñ ÐŒÐµÑÐŸÐŽÐžÐºÐ°, Ð¿ÐŸ ÐŸÐ±ÑÐºÐœÐŸÐ²ÐµÐœÐžÑ ÑÐµÐ°Ð»ÐžÐ·ÑÑÑÐ°Ñ ÑÐµÐºÑÑÐŸÐ²ÑÐ¹ ÐžÐœÐŽÐµÐºÑ.</Text>
+<Figure id="using_associative_arrays_in_stl" class="withLineNumber">
+<Title>
+<Text id="1225">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÑ
+ ÐŒÐ°ÑÑÐžÐ²ÐŸÐ² Ð² STL</Text>
+</Title>
+<CodeLine>#include &lt;iostream.h&gt;</CodeLine>
+<CodeLine>#include &lt;map&gt;</CodeLine>
+<CodeLine/>
+<CodeLine>int total_int_table(map&lt;char*, int&gt;&amp; table)</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   int total = 0;</CodeLine>
+<CodeLine>   map&lt;char*, int&gt;::iterator curr = table.begin();</CodeLine>
+<CodeLine>   while (curr!=table.end())</CodeLine>
+<CodeLine>   {</CodeLine>
+<CodeLine>       total += (curr-&gt;second);</CodeLine>
+<CodeLine>       curr++;</CodeLine>
+<CodeLine>   }</CodeLine>
+<CodeLine/>
+<CodeLine>   return total;</CodeLine>
+<CodeLine>}</CodeLine>
+<CodeLine/>
+<CodeLine>int main()</CodeLine>
+<CodeLine>{</CodeLine>
+<CodeLine>   map&lt;char*, int&gt; table;</CodeLine>
+<CodeLine>   table["Alice"] = 31;</CodeLine>
+<CodeLine>   table["Peter"] = 24;</CodeLine>
+<CodeLine>   table["Mary"]   = 47;</CodeLine>
+<CodeLine/>
+<CodeLine>   int total = total_int_table(table);</CodeLine>
+<CodeLine>   cout &lt;&lt; " Age total: " &lt;&lt; total &lt;&lt; endl;</CodeLine>
+<CodeLine>  }</CodeLine>
+</Figure>
+<Text id="1226">Ð STL Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÐµ ÐŒÐ°ÑÑÐžÐ²Ñ ÐŽÐŸÑÑÐžÐ³Ð°ÑÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÐŸÐ±ÑÐµÐºÑÐ° ÑÐ°Ñ. Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="using_associative_arrays_in_stl"/> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð¿ÑÐžÐŽÑÐŒÐ°ÐœÐœÑÐ¹ Ð¿ÑÐžÐŒÐµÑ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ Ð²ÐŸÐ·ÑÐ°ÑÑ ÑÑÐµÑ
+ ÑÐµÐ»ÐŸÐ²ÐµÐº (ÐÐ»ÐžÑÐ°, ÐÐžÑÐµÑ Ðž ÐÑÑÐž) Ñ
+ÑÐ°ÐœÐžÑÑÑ Ð² Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÐŸÐŒ ÐŒÐ°ÑÑÐžÐ²Ðµ Ð¿ÐŸÐŽ ÐžÑ
+ ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÑÐŒÐž ÐžÐŒÐµÐœÐ°ÐŒÐž (ÑÑÑÐŸÐºÐž 19-22). ÐÑÐŸÐ±Ð»ÐµÐŒÐ° ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ Ð·Ð°Ð¿ÐžÑÐ°ÑÑ ÑÑÐœÐºÑÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð²ÑÑÐžÑÐ»ÑÐµÑ Ð¿ÐŸÐ»ÐœÑÐ¹ Ð²ÐŸÐ·ÑÐ°ÑÑ Ð»ÑÐŽÐµÐ¹, ÐœÐµ Ð·ÐœÐ°Ñ, ÑÐºÐŸÐ»ÑÐºÐŸ ÐžÑ
+ ÐžÐŒÐµÐµÑÑÑ ÐžÐ»Ðž ÐºÐ°ÐºÐŸÐ²Ñ ÐžÑ
+ ÐžÐŒÐµÐœÐ°. ÐÐŸÐœÐµÑÐœÐŸ, ÑÑÐŸ ÐŒÐŸÐ³Ð»ÐŸ Ð±Ñ Ð±ÑÑÑ ÑÐµÑÐµÐœÐŸ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ
+ ÑÐžÑÐ»ÐŸÐ²ÑÑ
+ ÐŒÐ°ÑÑÐžÐ²ÐŸÐ² ÑÐµÐ»ÑÑ
+ ÑÐžÑÐµÐ». ÐÐ°ÐœÐœÑÐ¹ Ð¿ÑÐžÐŒÐµÑ Ð±ÑÐ» Ð¿ÑÐžÐŽÑÐŒÐ°Ðœ, ÑÑÐŸÐ±Ñ Ð¿ÑÐŸÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÐŸÐ²Ð°ÑÑ, ÑÑÐŸ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž ÑÐ°Ñ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÑÑ Ð¿ÐŸÐŽÐŸÐ±ÐžÐµ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž Ñ ÐŸÐ±ÑÐµÐºÑÐŸÐŒ list ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸ Ñ iterator.</Text>
+<Text id="1227">ÐÐŸÐŽÐŸÐ±ÐœÐŸ list, map ÐŸÑÐœÐŸÑÐžÑÑÑ Ðº ÐºÐ»Ð°ÑÑÑ-ÐºÐŸÐœÑÐµÐ¹ÐœÐµÑÑ. ÐÐŽÐœÐ°ÐºÐŸ, Ð¿ÑÐž ÐŸÐ±ÑÑÐ²Ð»ÐµÐœÐžÐž Ð¿ÐµÑÐµÐŒÐµÐœÐœÐŸÐ¹ ÑÑÐŸÐ³ÐŸ ÑÐžÐ¿Ð° ÐŒÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÐŽÐ²Ðµ<FootnoteRef id="5"/> Ð²ÐµÑÐž: ÐžÐœÐŽÐµÐºÑÐœÑÐ¹ ÑÐžÐ¿, Ðž ÑÐžÐ¿ ÑÐ»ÐµÐŒÐµÐœÑÐ°. ÐÐ°Ðº Ð²Ñ ÐŒÐŸÐ³Ð»Ðž Ð·Ð°ÐŒÐµÑÐžÑÑ Ð² ÑÑÑÐŸÐºÐµ 19, ÐŒÑ Ð¿ÐŸÐ»ÑÑÐ°ÐµÐŒ Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÐ¹ ÐŒÐ°ÑÑÐžÐ², ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑ ÑÐµÐ»ÑÐµ ÑÐžÑÐ»Ð°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ char* (ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ²Ð»ÑÐµÑÑÑ ÑÑÑÐŸÐºÐŸÐ¹, ÐŸÐ±ÑÑÐ²Ð»ÐµÐœÐœÐŸÐ¹ Ð² C++) ÐºÐ°Ðº ÐžÐœÐŽÐµÐºÑÐœÑÐ¹ ÑÐžÐ¿, ÑÐŸÐ¿ÑÐŸÐ²ÐŸÐ¶ÐŽÐ°ÐµÐŒÑÐ¹ int Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÐžÐ¿Ð° ÑÐ»ÐµÐŒÐµÐœÑÐ°.</Text>
+<Text id="1228">ÐÑÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐ² ÑÐŸÑ
+ÑÐ°ÐœÐžÑÑ ÑÐ»ÐµÐŒÐµÐœÑÑ Ð² Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÐŸÐŒ ÐŒÐ°ÑÑÐžÐ²Ðµ. Ð ÐŽÐ°ÐœÐœÐŸÐŒ Ð¿ÑÐžÐŒÐµÑÐµ Ð² ÑÑÑÐŸÐºÐ°Ñ
+ 20-22 Ð¿ÐµÑÐµÐ³ÑÑÐ¶ÐµÐœÐœÑÐ¹ ÐŒÐ°ÑÑÐžÐ² ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ [], ÑÑÐŸÐ±Ñ ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÑÑ ÑÐ°Ð±Ð»ÐžÑÑ Ñ Ð²ÐŸÐ·ÑÐ°ÑÑÐ°ÐŒÐž ÑÑÐžÑ
+ ÑÑÐµÑ
+ ÑÐµÐ»ÐŸÐ²ÐµÐº. ÐÐŸÐŽÐŸÐ±ÐœÐŸ total_int_table, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÐœÑÐµÑ ÐŸÑÐœÐŸÐ²ÐœÐŸÐµ Ð²ÑÑÐžÑÐ»ÐµÐœÐžÐµ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ, ÐœÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="programming_a_list_of_integers"/> ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ total_int_list Ð€Ð°ÐºÑÐžÑÐµÑÐºÐž, ÐŸÐœÐž Ð¿ÐŸÑÑÐž ÐžÐŽÐµÐœÑÐžÑÐœÑ, Ðž ÑÑÐŸ ÐœÐµ ÐœÐžÐºÐ°ÐºÐŸÐµ ÑÐŸÐ²Ð¿Ð°ÐŽÐµÐœÐžÐµ. STL ÑÑÑÐŽÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÐµ ÑÐ°Ðº, ÑÑÐŸÐ±Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÐŸÐ±ÑÐµÐºÑÑ Ð²ÑÐµ ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ð»Ðž ÑÐµ Ð¶Ðµ ÑÐ°ÐŒÑÐµ ÑÑÐœÐŽÐ°ÐŒÐµÐœÑÐ°Ð»ÑÐœÑÐµ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž. Ð­ÑÐŸ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸ ÑÐŸÑÐœÐŸ Ð² ÐŸÑÐœÐŸÑÐµÐœÐžÐž ÐžÑÐµÑÐ°ÑÐŸÑÐŸÐ². ÐÐµÐ±ÐŸÐ»ÑÑÐžÐµ ÑÐ°Ð·Ð»ÐžÑÐžÑ ÐŒÐµÐ¶ÐŽÑ ÐŽÐ²ÑÐŒÑ ÑÑÐœÐºÑÐžÑÐŒÐž ÑÐŸÑÑÐŸÑÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ ÐžÑÐµÑÐ°ÑÐŸÑ ÑÐµÐ¿ÐµÑÑ Ð¿ÐŸÐ»ÑÑÐµÐœ ÐžÐ· map&lt;char*, int&gt; Ðž ÐŽÐŸÑÑÑÐ¿ Ðº ÐµÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐ°ÐŒ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸ Ñ curr .&gt;second(), Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÑÐ°Ð·ÑÐŒÐµÐœÐŸÐ²Ð°ÐœÐžÐµ Ð¿ÐµÑÐµÐŒÐµÐœÐœÐŸÐ¹ (*ÑÐžÐ³Ð³) ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ, ÑÑÐŸÐ±Ñ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐžÑÑ ÐŸÐ±ÑÐµÐºÑ ÑÐžÐ¿Ð°ÑÑÐ³. ÐÐœ ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð·Ð°Ð¿ÐžÑÑ Ðž ÐžÐœÐŽÐµÐºÑÐœÐŸÐ³ÐŸ ÐžÐŒÐµÐœÐž (first), Ðž Ð·ÐœÐ°ÑÐµÐœÐžÑ ÑÐ»ÐµÐŒÐµÐœÑÐ° (second), ÐœÐŸ ÐŒÑ Ñ
+ÐŸÑÐžÐŒ ÐžÐŒÐµÑÑ ÑÐŸÐ»ÑÐºÐŸ Ð¿ÐŸÑÐ»ÐµÐŽÐœÐµÐµ. ÐÑÐŸÐŒÐµ ÑÑÐŸÐ³ÐŸ, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐŸÑÑÐ°ÐµÑÑÑ ÑÐŸÐ¹Ð¶Ðµ ÑÐ°ÐŒÐŸÐ¹. ÐÐŽÐžÐœÑÑÐ²ÐµÐœÐœÐŸÐµ ÐŸÑÑÐ°ÑÑÐµÐµÑÑ ÐŸÑÐ»ÐžÑÐžÐµ - ÑÑÐŸ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÐµ ÐµÐŽÐžÐœÑÑÐ²ÐµÐœÐœÐŸÐ³ÐŸ Ð°ÑÐ³ÑÐŒÐµÐœÑÐ° ÑÑÐœÐºÑÐžÐž Ñ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ñ ÐœÐ° ÑÑÑÐ»ÐºÑ - ÑÐ²Ð»ÑÐµÑÑÑ ÐœÐµÐ·ÐœÐ°ÑÐžÑÐµÐ»ÑÐœÑÐŒ.</Text>
+<Text id="1229">ÐÐ²Ð° ÐŽÑÑÐ³ÐžÑ
+ ÑÐžÐ¿Ð° STL, ÑÐžÑÐŸÐºÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ Greenstone - ÑÑÐŸ vector Ðž set. ÐÐµÑÐ²ÑÐ¹ ÐŸÐ±Ð»ÐµÐ³ÑÐ°ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÐŽÐžÐœÐ°ÐŒÐžÑÐµÑÐºÐžÑ
+ ÐŒÐ°ÑÑÐžÐ²ÐŸÐ², Ð° Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐ¹ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ ÐŒÐ°ÑÐµÐŒÐ°ÑÐžÑÐµÑÐºÐžÐµ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÑÐžÐ¿Ð° ÐŸÐ±ÑÐµÐŽÐžÐœÐµÐœÐžÑ, Ð¿ÐµÑÐµÑÐµÑÐµÐœÐžÑ Ðž ÑÐ°Ð·Ð»ÐžÑÐžÑ.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="bibliography">
+<Title>
+<Text id="1230">ÐÐžÑÐµÑÐ°ÑÑÑÐ°</Text>
+</Title>
+<Content>
+<Text id="1231">Aulds, C. (2000) <i>Linux Apache Web Server Administration</i>. Sybex.</Text>
+<Text id="1232">Bainbridge, D., Buchanan, G., McPherson, J., Jones, S., Mahoui, A. and Witten, I.H. (2001) âGreenstone: A platform for distributed digital library development.â Research Report, Computer Science Department, University of Waikato, New Zealand.</Text>
+<Text id="1233">Christiansen, T. Torkington, N. and Wall, L. (1998) <i>Perl Cookbook.</i> O'Reilly and Associates.</Text>
+<Text id="1234">Coar, K.A.L. (1998) <i>Apache Server For Dummies</i>. IDG Books.</Text>
+<Text id="1235">Deitel, H.M. and Deitel, P.J. (1994) <i>C++: How to Program</i>. Prentice Hall, Englewood Cliffs, New Jersey.</Text>
+<Text id="1236">Dublin Core (2001) âThe Dublin Core Metadata Initiativeâ at http://purl.org/dc/, accessed 16 January 2001.</Text>
+<Text id="1237">Josuttis, N.M. (1999) <i>The C++ standard library: a tutorial and reference.</i> Addison-Wesley, 1999.</Text>
+<Text id="1238">Keller, M. and Holden, G. (1999) <i>Apache Server for Windows Little Black Book</i>. Coriolis Group.</Text>
+<Text id="1239">Schwartz, R.L. and Christiansen, T. (1997) <i>Learning Perl</i>(2nd Edition). O'Reilly and Associates.</Text>
+<Text id="1240">Slama, D., Garbis, J. and Russell, P. (1999) <i>Enterprise CORBA</i>. Prentice Hall, Englewood Cliffs, New Jersey.</Text>
+<Text id="1241">Stroustroup, B. (1997) <i>The C++ Programming Language</i>. Addison-Wesley.</Text>
+<Text id="1242">Thiele, H. (1997) âThe Dublin Core and Warwick Framework: A Review of the Literature, March 1995âSeptember 1997.â <i>D-Lib Magazine</i>, January. &lt;http://www.dlib.org/dlib/january98/01thiele.html&gt;</Text>
+<Text id="1243">Wall, L., Christiansen, T. and Orwant, J. (2000) <i>Programming Perl</i>(3rd Edition). O'Reilly and Associates.</Text>
+<Text id="1244">Weibel, S. (1999) âThe State of the Dublin Core Metadata Initiative.â <i>D-Lib Magazine</i>, Volume 5 Number 4; April. &lt;http://www.dlib.org/dlib/april99/04weibel.html&gt;</Text>
+<Text id="1245">Witten, I.H., Moffat, A. and Bell, T.C. (1999) <i>Managing gigabytes: compressing and indexing documents and images</i>. Morgan Kaufmann, San Francisco.</Text>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="1246">ÐÐ»Ñ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÑÑ
+ ÑÐžÑÑÐµÐŒ Windows 95/98 Ð·Ð°Ð¿ÑÑÐº setup.bat ÐŒÐŸÐ¶ÐµÑ Ð·Ð°ÐºÐŸÐœÑÐžÑÑÑÑ ÐœÐµÑÐŽÐ°ÑÐœÐŸ, Ðž ÑÐžÑÑÐµÐŒÐ° Ð²ÑÐŽÐ°ÑÑ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐµ ÐŸÐ± ÐŸÑÐžÐ±ÐºÐµ "Out of environment space". ÐÑÐ»Ðž ÑÑÐŸ Ð¿ÑÐžÐ·ÐŸÑÐ»ÐŸ, ÑÐŸ Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÑÐžÑÑÐµÐŒÐœÑÐ¹ ÑÐ°Ð¹Ð» config.sys (ÐŸÐ±ÑÑÐœÐŸ ÐŸÐœ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² C:\config.sys) Ðž ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ Ð² ÐœÐµÐ³ÐŸ ÑÑÑÐŸÐºÑ shell=C:\command.com /e:4096 /p (Ð³ÐŽÐµ Ð¡: ÐžÐŒÑ Ð²Ð°ÑÐµÐ³ÐŸ ÑÐžÑÑÐµÐŒÐœÐŸÐ³ÐŸ ÐŽÐžÑÐºÐ°). ÐÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÑÑÐž ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð²ÑÑÑÐ¿ÐžÐ»Ðž Ð² ÑÐžÐ»Ñ, ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð¿ÐµÑÐµÐ·Ð°Ð³ÑÑÐ·ÐžÑÑ Ð²Ð°Ñ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑ Ðž Ð¿ÐŸÐ²ÑÐŸÑÐžÑÑ Ð²ÑÐµ ÑÐ°Ð³Ðž ÐŽÐ»Ñ Ð·Ð°Ð¿ÑÑÐºÐ° Greenstone.</Text>
+</Footnote>
+<Footnote id="2">
+<Text id="1247">ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ, ÑÑÐŸ Ð² ÑÐžÑÑÐµÐŒÐµ Greenstone ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐµ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÑ ÐžÐœÑÐµÑÐ¿ÑÐµÑÐžÑÑÑÑÑÑ ÑÐ·ÑÐºÐŸÐŒ Perl, ÐºÐŸÑÐŸÑÑÐ¹ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŸÑÐ»ÐžÑÐ°ÐµÑÑÑ ÐŸÑ ÐŽÑÑÐ³ÐžÑ
+. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, "*" ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÐµÑ ÐœÑÐ»Ñ ÐžÐ»Ðž Ð±ÐŸÐ»ÑÑÐµÐŒÑ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²Ñ Ð¿ÐŸÐ²ÑÐŸÑÐµÐœÐžÐ¹ Ð¿ÑÐµÐŽÑÐŽÑÑÐµÐ³ÐŸ ÑÐžÐŒÐ²ÐŸÐ»Ð°, Ð² ÑÐŸ Ð²ÑÐµÐŒÑ ÐºÐ°Ðº "."-Ð¿Ð°ÑÐµ Ð»ÑÐ±ÑÑ
+ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ². Ð¢Ð°Ðº, nugget.* ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÐµÑ Ð»ÑÐ±ÐŸÐ¹ ÑÑÑÐŸÐºÐµ Ñ Ð¿ÑÐµÑÐžÐºÑÐŸÐŒ "nugget," ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð»Ðž ÐŸÐœÐ° ÐžÐ»Ðž ÐœÐµÑ Ð¿ÑÐŸÐ±ÐµÐ» Ð¿ÐŸÑÐ»Ðµ Ð¿ÑÐµÑÐžÐºÑÐ°. Ð§ÑÐŸÐ±Ñ ÑÑÐµÑÑÑ ÑÑÐŸÑ Ð¿ÑÐŸÐ±ÐµÐ», ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐµÐ³ÐŸ ÐŸÐ±ÐŸÐ¹ÑÐž, ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ ÐœÑÐ¶ÐœÐŸ ÐœÐ°Ð¿ÐžÑÐ°ÑÑ nugget\.. *.</Text>
+</Footnote>
+<Footnote id="3">
+<Text id="1248">Note that more recent versions of the Demo collection use a Hierarchy classifier to display the how to metadata. In this case they will be displayed slightly differently to what is shown in Figure <CrossRef target="Figure" ref="list_classifier"/>.</Text>
+</Footnote>
+<Footnote id="4">
+<Text id="1249">ÐœÐ°ÑÐµÐœÐžÐµ ÐŽÐ»Ñ gsdlhome ÐžÑÑ
+ÐŸÐŽÐžÑ ÐžÐ· gsdlsite.cfg, ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐœÐŸÐ³ÐŸ Ð² ÑÐŸÐŒ Ð¶Ðµ ÑÐ°ÐŒÐŸÐŒ ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ðµ, ÑÑÐŸ Ðž CGI-Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÐŒÐ°Ñ library, ÑÐŸÐ³ÐŽÐ° ÐºÐ°Ðº GSDLHOME ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ Ð·Ð°Ð¿ÑÑÐºÐŸÐŒ ÑÐºÑÐžÐ¿ÑÐ° setup, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ Ðº ÐŽÑÑÐ³ÐŸÐŒÑ ÑÐ°Ð¹Ð»Ñ, ÑÐ°Ðº ÐºÐ°Ðº ÑÐµÑ
+ÐœÐžÑÐµÑÐºÐž ÑÑÐŸ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ ÐŽÐ»Ñ ÐŽÐ²ÑÑ
+ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹. Ð¥ÐŸÑÑ ÑÑÐŸ Ðž Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ, ÐœÐŸ Ð²ÑÐµ Ð¶Ðµ ÐœÐµ Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÐŸ, Ðž Ð²ÑÐµ Ð²ÑÑÐµÑÐºÐ°Ð·Ð°ÐœÐœÐŸÐµ ÐœÐ°Ð¿ÐžÑÐ°ÐœÐŸ Ð² Ð¿ÑÐµÐŽÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐž, ÑÑÐŸ ÑÐ°Ð¹Ð»Ñ ÑÐµ Ð¶Ðµ ÑÐ°ÐŒÑÐµ.</Text>
+</Footnote>
+<Footnote id="5">
+<Text id="1250">Ð¢ÐµÑ
+ÐœÐžÑÐµÑÐºÐž ÐµÑÑÑ ÑÐµÑÑÑÐµ ÑÐžÐ¿Ð°, ÐœÐŸ Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐµ ÐŽÐ²Ð° ÑÐ²Ð»ÑÑÑÑÑ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÐŒÐž. Ð¢Ð°Ðº ÐºÐ°Ðº ÐŒÑ ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ°ÐµÐŒ ÐŸÑÐœÐŸÐ²ÐœÐŸÐµ Ð²Ð²ÐµÐŽÐµÐœÐžÐµ Ð² ÑÑÐŸÑ ÐºÐ»Ð°ÑÑ STL, Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÑÑÐž ÐŸÐ± ÑÑÐžÑ
+ Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÑ
+ ÐŽÐ²ÑÑ
+ ÑÐžÐ¿Ð°Ñ
+ ÐŸÐ¿ÑÑÐµÐœÑ.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/ru/Install_ru.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/ru/Install_ru.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/ru/Install_ru.xml	(revision 13632)
@@ -0,0 +1,1198 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">ÐŠÐÐ€Ð ÐÐÐÐ¯ ÐÐÐÐÐÐÐ¢ÐÐÐ GREENSTONE</Text>
+</Heading>
+<Title>
+<Text id="2">ÐÐÐ¡Ð¢Ð Ð£ÐÐŠÐÐ¯ ÐÐ Ð£Ð¡Ð¢ÐÐÐÐÐÐ</Text>
+</Title>
+<Author>
+<Text id="3">Dr Michel Loots, Dan Camarzan and lan H. Witten</Text>
+</Author>
+<Affiliation>
+<Text id="4">Department of Computer ScienceÂ <br/>University of Waikato, New Zealand</Text>
+</Affiliation>
+<Text id="5">Greenstone ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐŸÐ¹, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐ¹ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ðž ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœÐžÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÑ
+ÑÑ Ð² ÑÐžÑÑÐŸÐ²ÐŸÐŒ ÑÐŸÑÐŒÐ°ÑÐµ. ÐÐœÐ° Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐœÐŸÐ²ÑÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž Ðž Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž Ð² ÐÐœÑÐµÑÐœÐµÑÐµ ÐžÐ»Ðž ÐœÐ° ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐºÐ°Ñ
+ CD-ROM. Greenstone Ð±ÑÐ» ÑÐŸÐ·ÐŽÐ°Ðœ Ð¿ÐŸ Ð¿ÑÐŸÐµÐºÑÑ New Zealand Digital Library Project Ð¿ÑÐž ÑÐœÐžÐ²ÐµÑÑÐžÑÐµÑÐµ ÐÐ°Ð¹ÐºÐ°ÑÐŸ, ÐŽÐŸÑÐ°Ð±ÐŸÑÐ°Ðœ Ðž ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœ Ð¿ÑÐž ÑÐŸÐŽÐµÐ¹ÑÑÐ²ÐžÐž Ð®ÐÐÐ¡ÐÐ Ðž ÐœÐµÐ¿ÑÐ°Ð²ÐžÑÐµÐ»ÑÑÑÐ²ÐµÐœÐœÐŸÐ¹ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐžÂ Â  Human info. Ð­ÑÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐŽÐŸÑÑÑÐ¿ÐœÐ° Ð²ÑÐµÐŒ ÐœÐ° ÑÐ°Ð¹ÑÐµ http://greenstone.org Ðž ÑÐŸÐŸÑÐ²ÐµÑÑÑÑÐµÑ ÑÑÐ»ÐŸÐ²ÐžÑÐŒ GNU General Public License.</Text>
+<Comment>
+<Text id="6">ÐÑ ÐœÐ°ÐŽÐµÐµÐŒÑÑ, ÑÑÐŸ ÑÑÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ñ
+ÐŸÑÐŸÑÐŸ. ÐÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, ÑÐŸÐŸÐ±ÑÐžÑÐµ ÐŸ Ð»ÑÐ±ÑÑ
+ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ°Ñ
+ Ð¿ÐŸ Ð°ÐŽÑÐµÑÑ:greenstone@cs.waikato.ac.nz</Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">ÐÐ°ÑÑ 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">ÐÐ± ÑÑÐŸÐ¹ ÐžÐœÑÑÑÑÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="10">Ð­ÑÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐŸÐ±ÑÑÑÐœÑÐµÑ, ÐºÐ°Ðº ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Greenstone ÑÐ°Ðº ÑÑÐŸÐ±Ñ Ð²Ñ ÐŒÐŸÐ³Ð»Ðž Ð·Ð°Ð¿ÑÑÐºÐ°ÑÑ ÐžÐ· ÑÐ²ÐŸÐµÐ³ÐŸ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°. ÐÐŽÐµÑÑ ÑÐ°ÐºÐ¶Ðµ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑÑÑ Ð±ÐµÑÐ¿Ð»Ð°ÑÐœÐŸ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÐŒÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐœÐ° Ð²ÐµÐ±-ÑÐµÑÐ²ÐµÑÐµ Apache Ðž Perl. ÐÑ ÐŽÐ°ÐŽÐžÐŒ Ð¿ÑÐŸÑÑÑÐµ Ð¿ÑÐžÐŒÐµÑÑ Ð¿ÑÐŸÑÐµÐŽÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž.</Text>
+<Text id="11">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÐŒÐŸÐ¶ÐµÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐœÐ° ÑÐ°Ð·ÐœÑÑ
+ Ð¿Ð»Ð°ÑÑÐŸÑÐŒÐ°Ñ
+ Ðž Ð² ÑÐ°Ð·ÐœÑÑ
+ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÑÑ
+. Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Chapter" ref="versions_of_greenstone"/> ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ Ð²ÐŸÐ¿ÑÐŸÑÐŸÐ² Ð²ÐŸÐ·ÐœÐžÐºÐ°ÑÑÐžÑ
+ Ð¿ÑÐž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Greenstone. Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Chapter" ref="installation_procedure"/> ÐŽÐµÑÐ°Ð»ÑÐœÐŸ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ Ð¿ÑÐŸÑÐµÐŽÑÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐ¹ ÐŽÐ»Ñ Ð²ÑÐµÑ
+ Ð²ÐµÑÑÐžÐž, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÑÐžÑÐ°ÑÑ ÑÑ ÑÐ°ÑÑÑ ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÑÐœÐŸÑÐžÑÑÑ Ðº Ð²Ð°ÑÐµÐ¹ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÐµ. Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Chapter" ref="greenstone_collections"/> ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÐŽÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ð²ÐºÐ»ÑÑÐµÐœÐœÑÐµ Ð² ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²Ñ. Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Chapter" ref="setting_up_webserver"/> ÐŸÐ±ÑÑÑÐœÑÐµÑ ÐºÐ°Ðº ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑ ÐŸÐ±ÑÐžÐµ Ð²ÐµÐ±-ÑÐµÑÐ²ÐµÑÑ, Apache Ðž Microsoft PWS/IIS Ð¿ÑÐž ÑÐ°Ð±ÐŸÑÐµ Ñ Greenstone. Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Chapter" ref="configuring_your_site"/> ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÐŸÐ¿ÑÐžÐž Greenstone Ðž Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Chapter" ref="personalizing"/> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐºÐ°Ðº ÐŽÐµÐ»Ð°ÑÑ Ð¿ÐµÑÑÐŸÐœÐ°Ð»ÑÐœÑÑ ÐŽÐŸÐŒÐ°ÑÐœÐžÑ ÑÑÑÐ°ÐœÐžÑÑ ÐŽÐ»Ñ ÑÐŸÐµÐŽÐžÐœÐµÐœÐžÑ Ñ Ð²Ð°ÑÐµÐ¹ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐŸÐ¹.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="12">Ð¡ÐŸÐ¿ÑÑÑÑÐ²ÑÑÑÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ</Text>
+</Title>
+<Content>
+<Text id="13">ÐÐŸÐ»ÐœÑÐ¹ ÐºÐŸÐŒÐ¿Ð»ÐµÐºÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÐž Ðº Greenstone ÑÐŸÑÑÐŸÐžÑ ÐžÐ· Ð¿ÑÑÐž ÑÐŸÐŒÐŸÐ²:</Text>
+<BulletList>
+<Bullet>
+<Text id="14">Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð¿ÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone (ÑÑÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ)</Text>
+</Bullet>
+<Bullet>
+<Text id="15">ÐÐœÑÑÑÑÐºÑÐžÑ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐº Ð° ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="17">ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: ÐŸÑ ÐÑÐŒÐ°Ð³Ðž ÐŽÐŸ ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Bullet>
+<Bullet>
+<Text id="18">ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÑÐ³Ð°ÐœÐ°Ð¹Ð·ÐµÑÐ°</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">ÐÐ»Ð°Ð³ÐŸÐŽÐ°ÑÐœÐŸÑÑÑ</Text>
+</Title>
+<Content>
+<Text id="20">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone - Ð¿ÑÐŸÐŽÑÐºÑ ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸÐ³ÐŸ ÑÑÑÐŽÐ° ÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ð° Ð»ÑÐŽÐµÐ¹. Rodger McNab Ðž Stefan Boddie Ð¿ÑÐžÐœÑÐžÐ¿ÐžÐ°Ð»ÑÐœÑÐµ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐž ÑÐžÑÑÐµÐŒÑ. ÐÐµÐŸÑÐµÐœÐžÐŒÑÐ¹ Ð²ÐºÐ»Ð°ÐŽ Ð²ÐœÐµÑÐ»Ðž David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, Ðž Stuart Yeates. ÐÑÑÐ°Ð»ÑÐœÑÐµ ÑÐ»ÐµÐœÑ ÐÑÐŸÐµÐºÑÐ° ÐÐŸÐ²ÐŸÐ·ÐµÐ»Ð°ÐœÐŽÑÐºÐŸÐ¹ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐžÂ  ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°Ð»Ðž Ð²ÐŽÐŸÑ
+ÐœÐŸÐ²ÐµÐœÐœÑÐ¹ ÐŽÐžÐ·Ð°Ð¹Ðœ Ð²ÑÐµÐ¹ ÑÐžÑÑÐµÐŒÑ: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols Ðž Lloyd Smith. ÐÑ ÑÐ°ÐºÐ¶Ðµ Ð²ÑÑÐ°Ð¶Ð°ÐµÐŒ ÑÐ²ÐŸÑ Ð¿ÑÐžÐ·ÐœÐ°ÑÐµÐ»ÑÐœÐŸÑÑÑ Ð²ÑÐµÐŒ ÑÐµÐŒ, ÐºÑÐŸ ÑÑÑÐŽÐžÐ»ÑÑ ÐœÐ°ÐŽ ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµÐŒ Ð¿Ð°ÐºÐµÑÐŸÐ², Ð¿ÐŸÐ¿Ð°ÐŽÐ°ÑÑÐžÑ
+ Ð¿ÐŸÐŽ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð»ÐžÑÐµÐœÐ·ÐžÐžÂ  GNU, Ðž Ð²ÐºÐ»ÑÑÐµÐœÐœÑÑ
+ Ð² ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE Ðž XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="versions_of_greenstone">
+<Title>
+<Text id="21">ÐÐµÑÑÐžÐž Greenstone</Text>
+</Title>
+<Content>
+<Text id="22">Greenstone ÐŒÐŸÐ¶ÐµÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐœÐ° ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð¿Ð»Ð°ÑÑÐŸÑÐŒÐ°Ñ
+ Ðž ÐžÐŒÐµÐµÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ Ð²ÐµÑÑÐžÐž, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐµ ÐœÐ° Ð ÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="different_options"/>.</Text>
+<Figure id="different_options">
+<Title>
+<Text id="23"/>
+</Title>
+<File width="550" height="297" url="images/Install_Fig_1.png"/>
+</Figure>
+<Text id="24">Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÑÑÐŸÑÑÐµÐ»ÑÑÑÐ², ÑÐ¿ÐŸÑÐŸÐ±ÐœÑÑ
+ Ð¿ÐŸÐ²Ð»ÐžÑÑÑ ÐœÐ° Ð¿ÑÐŸÑÐµÑÑÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž. ÐÐµÑÐµÐŽ ÑÐµÐŒ, ÐºÐ°Ðº Ð¿ÑÐŸÐŽÐŸÐ»Ð¶ÐžÑÑ, ÐŒÑ ÑÐŸÐ²ÐµÑÑÐµÐŒ Ð²Ð°ÐŒ ÐŸÑÐ²ÐµÑÐžÑÑ ÐœÐ°ÑÐ»ÐµÐŽÑÑÑÐžÐµ Ð²ÐŸÐ¿ÑÐŸÑÑ:</Text>
+<BulletList>
+<Bullet>
+<Text id="25">Ð ÐºÐ°ÐºÐŸÐ¹ ÑÐžÑÑÐµÐŒÐµ Ð²Ñ ÑÐ°Ð±ÐŸÑÐ°ÐµÑÐµ - Windows ÐžÐ»Ðž Unix?</Text>
+</Bullet>
+<Bullet>
+<Text id="26">ÐÑÐ»Ðž Windows, ÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ Ð»Ðž Ð²Ñ Windows 3.1/3.11 ÐžÐ»Ðž Ð±ÐŸÐ»ÐµÐµ ÐœÐŸÐ²ÑÐµÐ²ÐµÑÑÐžÐž? Ð¥ÐŸÑÑ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÑÐŸÐ¹ Ð²ÐµÑÑÐžÐž,Ð²Ñ ÐœÐµ ÑÐŒÐŸÐ¶ÐµÑÐµ ÐžÑ
+ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ. ÐÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŒÐŸÐ¶ÐœÐŸ ÑÐµÐ°Ð»ÐžÐ·ÐŸÐ²Ð°ÑÑÐ² Ð²ÐµÑÑÐžÑÑ
+ 95/98/ÐÐµ,ÐÐ¢/2000.</Text>
+</Bullet>
+<Bullet>
+<Text id="27">ÐÑÐ»Ðž Ð²Ñ ÑÐ°Ð±ÐŸÑÐ°ÐµÑÐµ Ñ Unix, ÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ Ð»Ðž Ð²Ñ Linux ÐžÐ»Ðž ÐŽÑÑÐ³ÐžÐµ Ð²ÐµÑÑÐžÐž?ÐÐ»Ñ Linux ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð±ÐžÐœÐ°ÑÐœÐ°Ñ Ð²ÐµÑÑÐžÑ ÑÐžÑÑÐµÐŒÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð»ÐµÐ³ÐºÐ° Ð² ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ. ÐÐ»Ñ ÐŽÑÑÐ³ÐžÑ
+ Ð²ÐµÑÑÐžÐ¹ Linux Ð²Ð°ÐŒ Ð¿ÑÐžÐŽÐµÑÑÑ ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑ ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐºÐŸÐŽ (source code) Ðž ÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÑÑ ÐµÐ³ÐŸ. Ð­ÑÐŸ ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÑÑÐµÐ±ÐŸÐ²Ð°ÑÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="28">ÐÑÐ»Ðž ÑÑÐŸ Windows NT/2000 ÐžÐ»Ðž Unix, ÑÐŸ ÐºÐ°Ðº Ð²Ñ Ð²Ñ
+ÐŸÐŽÐžÑÐµ Ð² ÑÐžÑÑÐµÐŒÑ - ÐºÐ°Ðº "Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑ" ÐžÐ»Ðž "root"? Ð­ÑÐŸ ÑÐ°Ð·Ð»ÐžÑÐžÐµ ÐŒÐŸÐ¶ÐµÑ ÑÑÐ³ÑÐ°ÑÑ ÑÐŸÐ»Ñ Ð¿ÑÐž ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐµ ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ° Greenstone.</Text>
+</Bullet>
+<Bullet>
+<Text id="29">ÐÑÐ¶ÐµÐœ Ð»Ðž Ð²Ð°ÐŒ ÐžÑÑ
+ÐŸÐŽÐœÐ¹ ÐºÐŸÐŽ? ÐÑÐ»Ðž Ð²Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ Windows ÐžÐ»Ðž Linux, ÑÐŸ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÑÑÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ð±ÐžÐœÐ°ÑÑ. ÐÐŸ Ð² ÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž Ð²Ð°ÐŒ Ð¿ÐŸÐœÐ°ÐŽÐŸÐ±ÐžÑÑÑ ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐºÐŸÐŽ, ÐŸÐœ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²Ðµ Greenstone.</Text>
+</Bullet>
+<Bullet>
+<Text id="30">ÐÑÐŽÐµÑÐµ Ð»Ðž Ð²Ñ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐœÐŸÐ²ÑÐµ ÑÐžÑÑÐŸÐ²ÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž? ÐÑÐ»Ðž ÐŽÐ°, ÑÐŸ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Perl, ÐºÐŸÑÐŸÑÑÐ¹ ÐŽÐŸÑÑÑÐ¿ÐµÐœ ÐºÐ°Ðº ÐŽÐ»Ñ Windows, ÑÐ°Ðº Ðž ÐŽÐ»Ñ Unix.</Text>
+</Bullet>
+<Bullet>
+<Text id="31">ÐÑÑÑ Ð»Ðž ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ? ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐ¹ Ð¿Ð°ÐºÐµÑ Greenstone ÐžÐŽÐµÑ Ð²ÐŒÐµÑÑÐµ Ñ ÑÐµÑÐµÐ²ÑÐŒ ÑÐµÑÐ²ÐµÑÐŸÐŒ Windows. ÐÐŸ ÐµÑÐ»Ðž ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÐŸÐœ ÑÐ¶Ðµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ, ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ðž ÐµÐ³ÐŸ. ÐÐ»Ñ Linux Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="32">ÐÐœÐ°ÐµÑÐµ Ð»Ðž Ð²Ñ, ÐºÐ°Ðº ÐœÐ°Ð»Ð°Ð¶ÐžÐ²Ð°ÑÑ ÑÐµÑÐ²ÐµÑ, ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐœÑÐ¹ ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ? ÐÑÐ»Ðž ÐœÐµÑ, ÑÐŸ Ð»ÑÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÑÐµÑÐ²ÐµÑ Greenstone, ÑÐ°Ðº ÐºÐ°Ðº Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ ÐœÐ°ÑÑÑÐŸÐžÑÑ Ð²Ð°Ñ ÑÐµÑÐ²ÐµÑ ÑÐ°Ðº, ÑÑÐŸÐ±Ñ ÐŸÐœ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°Ð» Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Chapter>
+<Chapter id="installation_procedure">
+<Title>
+<Text id="33">ÐÑÐŸÑÐµÑÑ ÐÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="34">Ð¡ÑÑÐµÑÑÐ²ÑÑÑ ÑÐ°Ð·ÐœÑÐµ Ð²ÐµÑÑÐžÐž Greenstone, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÐµ ÐŽÐ»Ñ Windows Ðž Unix, Ðž ÐŸÐœÐž ÐŽÐŸÑÑÑÐ¿ÐœÑ Ð² ÐŽÐ²ÑÑ
+ ÑÐŸÑÐŒÐ°Ñ
+: Ð±ÐžÐœÐ°ÑÐœÐ°Ñ ÑÐŸÑÐŒÐ° Ðž ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐºÐŸÐŽ. ÐÐ»Ñ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐÐœÑÐµÑÐœÐµÑ-Ð±ÑÐ°ÑÐ·ÐµÑ: Netscape Navigator ÐžÐ»Ðž Internet Explorer (Ð²ÐµÑÑÐžÐž 4.0 ÐžÐ»Ðž Ð²ÑÑÐµ Ð² ÐŸÐ±ÐŸÐžÑ
+ ÑÐ»ÑÑÐ°ÑÑ
+). ÐÑÐ»Ðž ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÐµÑÐµ ÐœÐµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ ÐÐœÑÐµÑÐœÐµÑ-Ð±ÑÐ°ÑÐ·ÐµÑ, ÑÐŸ ÐœÐ° ÑÑÐŸÐŒ CD-ROM ÐµÑÑÑ Windows - Ð²ÐµÑÑÐžÑ Netscape Navigator.</Text>
+<Section id="windows">
+<Title>
+<Text id="35">Windows</Text>
+</Title>
+<Content>
+<Text id="36">ÐÑÐ»Ðž Ð²Ñ ÑÐ²Ð»ÑÐµÑÐµÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐŒ Unix, ÑÐŸ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÐ¿ÑÑÑÐžÑÑ ÑÑÑ ÑÐ°ÑÑÑ Ðž ÐœÐ°ÑÐ°ÑÑ Ñ ÑÐ°ÑÑÐž 2.2. ÐÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Windows, Ð¶ÐµÐ»Ð°ÑÑÐžÑ
+ Ð²ÑÐ¿ÐŸÐ»ÐœÐžÑÑ "ÐŸÐ±ÑÑÐœÑÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÑ" (simple installation), ÐœÐ°ÐŽÐŸ Ð·ÐœÐ°ÑÑ, ÑÑÐŸ Ð²ÐµÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐ¹ Ð¿Ð°ÐºÐµÑ Greenstone Ð·Ð°Ð¹ÐŒÐµÑ ÐŸÐºÐŸÐ»ÐŸ 40 Mb ÐœÐ° Ð¶ÐµÑÑÐºÐŸÐŒ ÐŽÐžÑÐºÐµ.</Text>
+<Text id="37">ÐÑÐ»Ðž Ð²Ñ Ð²ÑÐ±ÐµÑÐµÑÐµ ÐŽÑÑÐ³ÑÑ ÑÐŸÑÐŒÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž, ÑÐŸ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ ÑÐµÑÐžÑÑ, ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑ Ð»Ðž Ð²Ð°ÐŒ Ð±ÐžÐœÐ°ÑÐœÑÐ¹ ÐºÐŸÐŽ ÐžÐ»Ðž ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐºÐŸÐŽ. ÐÑÐ»Ðž ÑÐŸÐŒÐœÐµÐ²Ð°ÐµÑÐµÑÑ, ÑÐŸ Ð»ÑÑÑÐµ Ð²ÑÐ±ÐµÑÐžÑÐµ Ð±ÐžÐœÐ°ÑÐœÑÐ¹ ÐºÐŸÐŽ. ÐÑÐŸÑÐµÑÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐžÐŽÐµÐœÑÐžÑÐµÐœ ÐŽÐ»Ñ ÐŸÐ±ÐŸÐžÑ
+ÑÐžÐ¿ÐŸÐ². ÐÐžÐ¶Ðµ ÐŸÐ¿ÐžÑÐ°ÐœÑ ÐŸÐ¿ÑÐžÐž, Ñ ÐºÐŸÑÐŸÑÑÐŒÐž Ð²Ñ ÑÑÐŸÐ»ÐºÐœÐµÑÐµÑÑ Ð¿ÑÐž Ð²ÑÐ±ÐŸÑÐµ ÑÐžÐ¿Ð° ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž.</Text>
+<Text id="38">ÐÐŸÑÐ»Ðµ Ð·Ð°Ð²ÐµÑÑÐµÐœÐžÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÑÐ°Ð·Ñ Ð¶Ðµ Ð¿ÐµÑÐµÐ¹ÑÐž Ðº ÑÐ°ÑÑÐž 2.3.</Text>
+<Subsection id="simple_installation">
+<Title>
+<Text id="39">ÐÐ±ÑÑÐœÐ°Ñ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÑ</Text>
+</Title>
+<Content>
+<Text id="40">ÐÐ»Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ð²ÐµÑÑÐžÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð¿ÐŸÐŽ Windows Ð²ÑÑÐ°Ð²ÑÑÐµ CD-ROM Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐ¹ ÐŽÐžÑÐºÐŸÐ²ÐŸÐŽ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ D:). ÐÑÐ»Ðž Ð¿ÑÐŸÑÐµÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž ÐœÐµ ÐœÐ°ÑÐœÐµÑÑÑ ÑÐµÑÐµÐ· 20 ÑÐµÐºÑÐœÐŽ, ÑÐŸ ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐŒÐµÐœÑ ÐÑÑÐº, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐÑÐ¿ÐŸÐ»ÐœÐžÑÑ Ðž ÐœÐ°Ð¿ÐžÑÐžÑÐµ D:\setup.exe Ð³ÐŽÐµ D: ÑÑÐŸ ÐŽÐžÑÐºÐŸÐ²ÐŸÐŽ ÐŽÐ»Ñ CD-ROM. Ð Ð²ÐµÑÑÐžÐž Windows 3.1,Â Â  Ð²ÑÐ±ÐµÑÐžÑÐµÂ Â Â Â  ÐÑÐ¿ÐŸÐ»ÐœÐžÑÑÂ Â  ÐÐÂ Â  Ð€Ð°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸÂ  ÐŒÐµÐœÐµÐŽÐ¶ÐµÑÐ° ÐÂ Â  Ð²Ð²ÐµÐŽÐžÑÐµ D:\Windows\win3.1\setup.exe.</Text>
+<Text id="41">ÐÐ»Ñ Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ð²ÑÐ±ÐžÑÐ°Ð¹ÑÐµ Ð²ÑÐµ ÑÑÐ»ÐŸÐ²ÐžÑ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÑÑÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, ÐœÐ°Ð¶ÐžÐŒÐ°Ñ ÐœÐ° ÐºÐœÐŸÐ¿ÐºÑ ÐÐ°Ð»ÐµÐµ(Next) . Ð­ÑÐŸ Ð²ÑÐµ, ÑÑÐŸ Ð²Ð°ÐŒ ÐœÐ°ÐŽÐŸ ÑÐŽÐµÐ»Ð°ÑÑ! Greenstone Ð±ÑÐŽÐµÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž C:\Program Files\gsdl.</Text>
+<Text id="42">ÐÐŸÑÐ»Ðµ Ð·Ð°Ð²ÐµÑÑÐœÐžÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐŽÐ»Ñ Ð·Ð°Ð¿ÑÑÐºÐ° ÑÐžÑÑÐµÐŒÑ ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐºÐœÐŸÐ¿ÐºÑ ÐÑÑÐº, Ð²ÑÐ±ÐµÑÐžÑÐµÐÐµÐœÑ ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, Ð·Ð°ÑÐµÐŒÂ  Greenstone Digital Library, Ð·Ð°Ð¿ÑÑÐ³ÐžÐ² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ. ÐÐ»Ñ Ð²Ñ
+ÐŸÐŽÐ° Ð² ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ ÐžÐºÐŸÐœÐºÑ Ð² ÐÐ»Ð°Ð²ÐœÐŸÐŒ ÐŒÐµÐœÑ Greenstone</Text>
+<Figure id="your_greenstone_home_page">
+<Title>
+<Text id="43">ÐÐŸÐŒÐ°ÑÐœÑÑ ÑÑÑÐ°ÐœÐžÑÐ°</Text>
+</Title>
+<File width="407" height="341" url="images/Install_Fig_2.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="windows_binaries">
+<Title>
+<Text id="44">ÐÐžÐœÐ°ÑÐœÑÐµ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ð¿ÐŸÐŽ Windows</Text>
+</Title>
+<Content>
+<Text id="45">ÐÐ° CD-ROM ÐµÑÑÑ ÐŽÐ²Ðµ ÐŸÑÐŽÐµÐ»ÑÐœÑÐµ Ð±ÐžÐœÐ°ÑÐœÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð¿ÐŸÐŽ Wmdows:Local Library (ÐÐŸÐºÐ°Ð»ÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°)Â  Ð Web Library (ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°). ÐÑÐž ÐŸÐ±ÑÑÐœÐŸÐ¹ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž, ÐŸÐ¿ÐžÑÐ°ÐœÐŸÐ¹ Ð²ÑÑÐµ, ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ ÐÐŸÐºÐ°Ð»ÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°. ÐÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ Ð²Ð°ÐŒ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐžÐŒÐµÐœÐœÐŸ ÐµÑ, ÑÐ°Ðº ÐºÐ°Ðº ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ ÑÑÑÐŽÐœÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ, Ðž ÐŸÐœÐ° ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐ° ÑÐŸÐ»ÑÐºÐŸ Ð² ÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž Ñ Ð²Ð°Ñ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Ðž Ð²Ñ ÐœÐ°ÐŒÐµÑÐµÐ²Ð°ÐµÑÐµÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐµÐ³ÐŸ ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ»Ñ Greenstone. ÐÐµÑÐŒÐŸÑÑÑ ÐœÐ° ÑÐ²ÐŸÑ ÑÐºÑÐŸÐŒÐœÐŸÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÐÐŸÐºÐ°Ð»ÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ Ð¿ÐŸÐ»ÐœÑÐŒ, Ð°Ð²ÑÐŸÐœÐŸÐŒÐœÑÐŒ, ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐŒ Ð¿ÐŸÑÐµÐœÑÐžÐ°Ð»ÐŸÐŒ ÑÐ°Ð±ÐŸÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°.</Text>
+<Text id="46">ÐÐŸÐºÐ°Ð»ÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°. Ð¡ Ð¿ÐŸÐŒÐŸÑÑÑ ÐÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÐŒÐŸÐ¶ÐœÐŸ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ Ð³ÐŸÑÐŸÐ²ÑÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž Greenstone Ð² Ð»ÑÐ±ÐŸÐ¹ Ð²ÐµÑÑÐžÐž Windows. ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž. ÐÑ ÑÐ°ÐºÐ¶Ðµ ÐŒÐŸÐ¶ÐµÑÐµ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ ÐœÐŸÐ²ÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ñ ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐºÐ° (ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐµ Ð² Ð§Ð°ÑÑÐž <CrossRef target="Chapter" ref="greenstone_collections"/>).</Text>
+<Text id="47">ÐÐŸÐºÐ°Ð»ÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐ° ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ ÐœÐ° ÐŸÑÐŽÐµÐ»ÑÐœÑÑ
+ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°Ñ
+ ÐžÐ»Ðž ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°Ñ
+, ÐœÐ° ÐºÐŸÑÐŸÑÑÑ
+ ÐµÑÐµ ÐœÐµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÑÐµÑÐµÐ²ÑÐµ ÑÐµÑÐ²ÐµÑÑ. ÐÐœÐ° ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐœÐµÐ±ÐŸÐ»ÑÑÐŸÐ¹ Ð²ÑÑÑÐŸÐµÐœÐœÑÐ¹ ÑÐµÑÐ²ÐµÑ, ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ ÐŽÑÑÐ³ÐžÐµ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÑ, Ð¿ÐŸÐŽÐºÐ»ÑÑÐµÐœÐœÑÐµ Ðº ÑÐŸÐ¹ Ð¶Ðµ ÑÐµÑÐž, ÐŒÐŸÐ³Ð»Ðž ÐžÐŒÐµÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐµ (ÐœÐŸ ÑÑÐŸÑ ÑÐµÑÐ²ÐµÑ ÐžÐŒÐµÐµÑ ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž).</Text>
+<Text id="48">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐ¹ Ð¿Ð°ÐºÐµÑ Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÐœÐ°Ð»ÐžÑÐžÐµÂ  Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÐŸÑÐ²ÐµÑÐ°ÑÑÐµÐ¹ Ð·Ð° ÑÐµÑÐµÐ²ÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ, Ðž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ, Ð¿ÐŸÐŽÐºÐ»ÑÑÐµÐœÑ Ð»Ðž Ð²Ñ Ðº ÑÐµÑÐž. ÐÐŸ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑ ÐŽÐ²Ðµ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ Ñ ÑÑÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐŸÐ¹:</Text>
+<BulletList>
+<Bullet>
+<Text id="49">ÐÑÐµÐŒÑ ÐŸÑ Ð²ÑÐµÐŒÐµÐœÐž ÐŒÐŸÐ¶ÐµÑ ÑÐŸÐ²ÐµÑÑÐ°ÑÑÑÑ ÐœÐµÐ·Ð°Ð¿Ð»Ð°ÐœÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ dial-up</Text>
+</Bullet>
+<Bullet>
+<Text id="50">ÐÐœÐ° ÐŒÐŸÐ¶ÐµÑ ÐœÐµ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐžÐ·-Ð·Ð° ÐœÐµÐ¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸÐ¹ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ.</Text>
+</Bullet>
+</BulletList>
+<Text id="51">ÐÐ»Ñ ÐžÐ·Ð±ÐµÐ¶Ð°ÐœÐžÑ ÑÐ°ÐºÐžÑ
+ Ð¿ÑÐŸÐ±Ð»ÐµÐŒ ÐŽÐžÑÐº ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÐœÑÑ Ð²ÐµÑÑÐžÑ ÐÐŸÐºÐ°Ð»ÑÐœÐŸÑÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž, ÐºÐŸÑÐŸÑÑÑ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð²ÐŒÐµÑÑÐŸ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐ¹. Ð­ÑÐ° Ð²ÐµÑÑÐžÑ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÑÐŸÐ»ÑÐºÐŸ Ð² Netscape- ÐÑÐž Ð·Ð°Ð¿ÑÑÐºÐµ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ð²Ñ ÑÐ²ÐžÐŽÐžÑÐµ ÐžÐºÐŸÐœÐºÑ, Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑÑÑ Ð²ÐŸÐ¹ÑÐž Ð² ÑÑÑ Ð²ÐµÑÑÐžÑ. ÐÑÐµÐŽÐ¿ÐŸÑÑÐžÑÐµÐ»ÑÐœÐµÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ Ð²ÐµÑÑÐžÑ, ÐœÐµ Ð²ÑÐ·ÑÐ²Ð°ÑÑÑÑ ÑÑÐžÑ
+ Ð¿ÑÐŸÐ±Ð»ÐµÐŒ.</Text>
+<Text id="52">ÐÐœÑÐµÑÐœÐµÑ - Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° (Web Library). Ð¡ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÑÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ðž Ð¿ÑÐž ÐœÐ°Ð»ÐžÑÐžÐž ÑÐµÑÐµÐ²ÐŸÐ³ÐŸÂ Â  ÑÐµÑÐ²ÐµÑÐ° ÐŒÐŸÐ¶ÐœÐŸÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ Ð³ÐŸÑÐŸÐ²ÑÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž.Ð­ÑÐ° Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÑ Ñ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐŒ ÑÐµÑÐµÐ²ÑÐŒ ÑÐµÑÐ²ÐµÑÐŸÐŒ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ Ð³ÐŸÑÐŸÐ²ÑÐŒÐž Greenstone ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž. ÐÐ°Ðº Ðž Ð² ÑÐ»ÑÑÐ°Ðµ Ñ Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐŸÐ¹, ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐ°ÐºÐ¶Ðµ Ð±ÑÐŽÐµÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž. ÐÑ ÑÐ°ÐºÐ¶Ðµ ÐŒÐŸÐ¶ÐµÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ðž ÐŽÑÑÐ³ÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÐµÑÑ ÐœÐ° CD-ROM, (ÑÐŒÐŸÑÑÐžÑÐµ Ð§Ð°ÑÑÑ <CrossRef target="Chapter" ref="greenstone_collections"/>).</Text>
+<Text id="53">ÐÑÐ»ÐžÑÐžÐµ ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÐŸÑ ÐÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ ÐŸÐœÐ° Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐ° ÐŽÐ»Ñ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÑÐ¶Ðµ ÐžÐŒÐµÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐ¹ Ð¿Ð°ÐºÐµÑ ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°.</Text>
+<Text id="54">ÐÐ»Ñ Ð·Ð°Ð¿ÑÑÐºÐ° ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒ:</Text>
+<BulletList>
+<Bullet>
+<Text id="55">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐ¹ Ð¿Ð°ÐºÐµÑ ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°. ÐÐ»Ñ ÑÑÐŸÐ³ÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Apache (ÑÐŒÐŸÑÑÐžÑÐµ ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ <CrossRef target="Chapter" ref="appendix_associated_software"/>)</Text>
+</Bullet>
+<Bullet>
+<Text id="56">ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ. Ð­ÑÐŸÑ ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑ Ð²ÐºÐ»ÑÑÐµÐœ ÐºÐ°Ðº Ð² ÐÐŸÐºÐ°Ð»ÑÐœÑÑ, ÑÐ°Ðº Ðž Ð² ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ Ðž Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð²Ð°ÐŒ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð²Ð°ÑÐµÐŒÑ ÑÑÐŒÐŸÑÑÐµÐœÐžÑ. (Ð Windows 3.1/3.11 ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ ÐœÐµ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ).</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="windows_webserver_configuration">
+<Title>
+<Text id="57">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐ° ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ° Windows (Ð¢ÐŸÐ»ÑÐºÐŸ ÐŽÐ»Ñ Ð²ÐµÑÑÐžÐž ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž)</Text>
+</Title>
+<Content>
+<Text id="58">ÐÑÐµÐžÐŒÑÑÐµÑÑÐ²ÐŸÐŒ ÐÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÑÐ²Ð»ÑÐµÑÑÑ ÑÐŸ, ÑÑÐŸ ÐµÐµ ÐŒÐŸÐ¶ÐœÐŸ Ð·Ð°Ð¿ÑÑÑÐžÑÑ ÑÑÐ°Ð·Ñ Ð¶Ðµ Ð¿ÐŸÑÐ»Ðµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž, Ðž ÐŸÐœÐ° ÐœÐµ ÐœÑÐ¶ÐŽÐ°ÐµÑÑÑ Ð² ÐºÐ°ÐºÐŸÐ¹-Ð»ÐžÐ±ÐŸ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐµ. Ð ÑÐ»ÑÑÐ°Ðµ Ñ ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐŸÐ¹ Ð²Ð°ÐŒ Ð¿ÑÐµÐŽÑÑÐŸÐžÑ ÐœÐ°ÑÑÑÐŸÐžÑÑ Ð²Ð°Ñ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ. ÐÑÐ»Ðž ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ ÑÐ¶Ðµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ, ÑÐŸ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð²Ð²ÐµÑÑÐž ÐœÐµÐ±ÐŸÐ»ÑÑÐžÐµ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð² ÐµÐ³ÐŸ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ñ Greenstone.</Text>
+<Text id="59">Ð¡Ð¿ÐµÑÐžÐ°Ð»ÑÐœÑÐ¹ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐŸÐœÐœÑÐ¹ ÑÐºÑÐžÐ¿Ñ Apache Ð³ÐŸÐ²ÐŸÑÐžÑ ÐŸ ÑÐŸÐŒ, ÑÑÐŸ ÐžÐŒÐµÐœÐœÐŸ ÐœÐ°ÐŽÐŸ ÑÐŽÐµÐ»Ð°ÑÑ-ÑÐŒÐŸÑÑÐžÑÐµ ÑÐ°ÑÑÑ <CrossRef target="Section" ref="pws_and_iis_webservers"/> ÐžÐœÑÑÑÑÐºÑÐžÐž Ð¿ÐŸ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐµ ÑÐµÑÐµÐ²ÑÑ
+ ÑÐµÑÐ²ÐµÑÐŸÐ² PWS, MS. ÐÐ°ÐŒ, Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ, Ð¿ÐŸÐœÐ°ÐŽÐŸÐ±ÐžÑÑÑ Ð¿ÐŸÐŒÐŸÑÑ ÑÐžÑÑÐµÐŒÐœÐŸÐ³ÐŸ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑÐ° ÐŽÐ»Ñ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°.</Text>
+<Text id="60">ÐÑÐ»Ðž Ñ Ð²Ð°Ñ ÐµÑÐµ ÐœÐµÑ ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°, ÑÐŸ Ð²Ð°ÐŒ ÐµÐ³ÐŸ ÐœÑÐ¶ÐœÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ (ÑÐŒÐŸÑÑÐžÑÐµ Ð² ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐž <CrossRef target="Chapter" ref="appendix_associated_software"/> ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸÐ± Apache). ÐÐ°ÑÐµÐŒ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ ÐµÐ³ÐŸ Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ ÐœÐ°ÑÑÑÐŸÐžÑÑ. Ð <CrossRef target="Chapter" ref="setting_up_webserver"/> ÑÐ°ÑÑÐž ÐŽÐ°ÐœÐŸ ÐŽÐµÑÐ°Ð»ÑÐœÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐŸÑÐŽÐµÐ»ÑÐœÑÐµ ÑÐ°ÑÑÐž Ð²ÐµÐ±-ÑÐµÑÐ²ÐµÑÐ° Ð²Ð»ÐžÑÑÑ ÐœÐ° Greenstone Ðž ÐºÐ°Ðº ÐœÑÐ¶ÐœÐŸ ÐžÑ
+ ÐžÐ·ÐŒÐµÐœÐžÑÑ. ÐÑÐµ ÑÑÐŸ ÑÐ²ÐŸÐŽÐžÑÑÑ Ðº ÑÐŸÐŒÑ, ÑÑÐŸ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ Ð²Ð²ÐµÑÑÐž ÐŸÐºÐŸÐ»ÐŸ ÑÐµÑÑÐž ÑÑÑÐŸÐº Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð».</Text>
+</Content>
+</Subsection>
+<Subsection id="windows_source">
+<Title>
+<Text id="61">ÐÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐºÐŸÐŽ ÐŽÐ»Ñ Windows</Text>
+</Title>
+<Content>
+<Text id="62">ÐÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐºÐŸÐŽ Greenstone Ð·Ð°ÐœÐžÐŒÐ°ÐµÑ 50 Mb Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ð°, ÐœÐŸ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ ÐµÐ³ÐŸ ÑÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÑÑ Ð²Ð°ÐŒ Ð¿ÐŸÑÑÐµÐ±ÑÐµÑÑÑ ÐŸÐºÐŸÐ»ÐŸ 90Mb. ÐÐ»Ñ ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐžÐž Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒ:</Text>
+<BulletList>
+<Bullet>
+<Text id="63">The Microsoft Visual C++ compiler (ÐœÐ° ÐŽÐ°ÐœÐœÑÐ¹ ÐŒÐŸÐŒÐµÐœÑ ÐŒÑ ÑÐµÑÐ°ÐµÐŒ ÐœÐµÐ±ÐŸÐ»ÑÑÐžÐµ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ Ð¿ÐŸ Ð¿ÐŸÐ²ÐŸÐŽÑ ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐžÐž Greenstone Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÐ°Ð·ÐœÑÑ
+Ñ Ð¿ÐŸÑÑÐŸÐ² GNU GCC.)</Text>
+</Bullet>
+</BulletList>
+<Text id="64">(ÐÐ°ÐŒ ÐœÐµ ÐœÑÐ¶ÐµÐœ GDBM, Ð¡Ð£ÐÐ Gnu database manager, ÑÐ°Ðº ÐºÐ°Ðº ÐŸÐœ Ð²ÐºÐ»ÑÑÐµÐœ Ð²Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐ¹ Ð¿Ð°ÐºÐµÑ Greenstone).</Text>
+<Text id="65">ÐÐ°Ð»ÐŸÐ²ÐµÑÐŸÑÑÐœÐŸ, ÑÑÐŸ Ð²Ñ ÑÐŒÐŸÐ¶ÐµÑÐµ ÑÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð² Windows 3.1/3.11.</Text>
+<Text id="66">ÐÑÐ»Ðž Ð²Ñ Ð¿ÐµÑÐµÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÑÐµÑÐµ Greenstone Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ ÑÑÑ Ð²ÐµÑÑÐžÑ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ CD-ROM, Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ Ð·Ð°Ð¿ÐŸÐŒÐœÐžÑÑ, ÑÑÐŸ ÐºÐŸÐŽ, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÐ¹ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÑ
+ÐÐµÑÑÐžÐ¹ ÐTPP/ C++ compiler, ÐœÐµ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ð² Windows 3.1/3.11, ÑÐŸÐ³ÐŽÐ° ÐºÐ°Ðº ÐœÐ°ÐŽÑÑÐ³ÐžÑ
+ Ð±ÐŸÐ»ÐµÐµ ÐœÐŸÐ²ÑÑ
+ Ð²ÐµÑÑÐžÑÑ
+ (95,98,Me,N7,2000) ÐŸÐœ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ. ÐÑÐ»Ðž Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ,ÑÑÐŸÐ±Ñ Ð¿ÐµÑÐµÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÐœÐœÐ°Ñ Ð²ÐµÑÑÐžÑ ÑÐ°Ð±ÐŸÑÐ°Ð»Ð° ÐœÐ° Ð±ÐŸÐ»ÐµÐµ ÑÐ°ÐœÐœÐžÑ
+ Ð²ÐµÑÑÐžÑÑ
+Windows, ÑÐŸ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÑÑÐ³ÑÑ Ð²ÐµÑÑÐžÑ ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐŸÑÐ°.ÐÐŸÐ»ÐµÐµ ÑÐŸÐ³ÐŸ,Â  GreenstoneÂ  ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ STL,Â  C++ standard templatelibrary(ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ ÑÐ°Ð±Ð»ÐŸÐœÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°), Ð Ð¥ÐÐ¢Ð¯ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐÐÐÐÐÐÐ¯Ð¢ÐÐ Ð«ÑÐŸÐŽÐµÑÐ¶Ð°Ñ STL, ÑÑÐ° Ð²ÐµÑÑÐžÑ ÐœÐµ Ð±ÑÐŽÐµÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐœÐŸÑÐŒÐ°Ð»ÑÐœÐŸ. ÐÐŸÑÑÐŸÐŒÑ ÐŽÐ»ÑÐ¿ÐµÑÐµÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐžÐž Greenstone, ÑÑÐŸÐ±Ñ ÐŸÐœ ÑÐ°Ð±ÐŸÑÐ°Ð» ÐœÐ° ÑÐ°ÐœÐœÐžÑ
+ Ð²ÐµÑÑÐžÑÑ
+ Windows,Ð²Ð°ÐŒ ÐœÑÐ¶ÐµÐœ:</Text>
+<BulletList>
+<Bullet>
+<Text id="67">The Microsoft Visual C++ compiler, ÐÐµÑÑÐžÑ 4.0 ÐžÐ»Ðž 4.2</Text>
+</Bullet>
+<Bullet>
+<Text id="68">ÐÐœÐµÑÐœÑÑ Ð²ÐµÑÑÐžÑ STL, C++Â  STL Ð²Ñ
+ÐŸÐŽÐžÑ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÐŸ ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ñ ÑÑÐžÐŒÐž Ð²ÐµÑÑÐžÑÐŒÐž ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐŸÑÐŸÐ².</Text>
+</Bullet>
+</BulletList>
+<Text id="69">ÐÑÐ¶ÐœÐŸ Ð·Ð°ÐŒÐµÑÐžÑÑ, ÑÑÐŸ Ð¿ÑÐž Ð²ÑÐ±ÐŸÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ³ÐŸ ÐºÐŸÐŽÐ° Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Greenstone, ÐºÐŸÐŽ ÐœÐµ Ð±ÑÐŽÐµÑ ÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÑÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž. ÐÐœÑÑÑÑÐºÑÐžÐž, ÑÐ²ÑÐ·Ð°ÐœÐœÑÐµ Ñ ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐžÐµÐ¹ Greenstone, ÑÐŒÐŸÑÑÐžÑÐµ Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐµ lnstall.txt, ÐºÐŸÑÐŸÑÑÐ¹ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž (C:\Program Files\gsdl Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ).</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="unix">
+<Title>
+<Text id="70">Â  Unix</Text>
+</Title>
+<Content>
+<Text id="71">Ð­ÑÐ° ÑÐ°ÑÑÑ ÐœÐ°Ð¿ÐžÑÐ°ÐœÐ° ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ UnixÂ  (ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ðž Windows ÐŒÐŸÐ³ÑÑ ÑÑÐ°Ð·Ñ Ð¿ÐµÑÐµÐ¹ÑÐž Ðº ÑÐ°ÑÑÐž <CrossRef target="Section" ref="how_to_find_greenstone"/>).ÐÐ»Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ Ð²ÑÐ±ÑÐ°ÑÑ ÐŒÐµÐ¶ÐŽÑ Ð±ÐžÐœÐ°ÑÐœÑÐŒ Ðž ÐžÑÑ
+ÐŸÐŽÐœÑÐŒ ÐºÐŸÐŽÐ°ÐŒÐž. ÐÐžÐœÐ°ÑÐœÑÐ¹ ÐºÐŸÐŽ Ð·Ð°ÐœÐžÐŒÐ°ÐµÑ ÐŸÐºÐŸÐ»ÐŸ 50 Mb; ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐºÐŸÐŽ ÑÑÐµÐ±ÑÐµÑ 160ÐÐ¬ ÐŽÐ»Ñ ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐžÐž.</Text>
+<Subsection id="unix_binaries">
+<Title>
+<Text id="72">ÐÐžÐœÐ°ÑÐœÑÐ¹ ÐºÐŸÐŽ ÐŽÐ»Ñ Unix</Text>
+</Title>
+<Content>
+<Text id="73">ÐÐžÐœÐ°ÑÐœÑÐ¹ ÐºÐŸÐŽ ÐœÑÐ¶ÐŽÐ°ÐµÑÑÑ Ð²Â  Linux ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²Ðµ, ÐŸÑÐœÐŸÐ²Ð°ÐœÐœÐŸÐŒ ÐœÐ° IntelÑ
+8Ð±, ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð² ÑÐµÐ±Ñ ELF binary support. ÐÐžÐ¶Ðµ Ð¿ÐµÑÐµÑÐžÑÐ»ÐµÐœÑ ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²Ñ, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑ ÑÑÐžÐŒ ÑÑÐµÐ±ÐŸÐ²Ð°ÐœÐžÑÐŒ:</Text>
+<BulletList>
+<Bullet>
+<Text id="74">RedHat 5.1</Text>
+</Bullet>
+<Bullet>
+<Text id="75">SuSe Linux 6.1</Text>
+</Bullet>
+<Bullet>
+<Text id="76">Debian 2.1</Text>
+</Bullet>
+<Bullet>
+<Text id="77">Slackware 4.0</Text>
+</Bullet>
+</BulletList>
+<Text id="78">ÐÐŸÐ»ÐµÐµ ÑÐ°ÐœÐœÐžÐµ Ð²ÐµÑÑÐžÐž ÑÑÐžÑ
+ ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²ÐŸÐ² ÑÐ°ÐºÐ¶Ðµ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ.</Text>
+<Text id="79">ÐÐ°ÐŒ Ð¿ÐŸÑÑÐµÐ±ÑÐµÑÑÑ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ: ÐŒÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ Apache. ÐÑ ÑÐ°ÐºÐ¶Ðµ ÐœÐ°ÑÑÐŸÑÑÐµÐ»ÑÐœÐŸ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ Ð²Ð°ÐŒ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ ÐŽÐŸ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº Ð²Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÐµ Greenstone - ÑÑÐŸ Ð·ÐœÐ°ÑÐžÑÐµÐ»ÑÐœÐŸ ÐŸÐ±Ð»ÐµÐ³ÑÐžÑ Ð¿ÑÐŸÑÐµÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž. ÐÑÐ»Ðž Ð²Ñ Ð¿Ð»Ð°ÐœÐžÑÑÐµÑÐµ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÑÐžÑÑÐŸÐ²ÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸ Ð²Ð°ÐŒ ÑÐ°ÐºÐ¶Ðµ Ð¿ÐŸÐœÐ°ÐŽÐŸÐ±ÐžÑÑÑ Perl, ÐµÑÐ»Ðž ÐŸÐœ ÐµÑÐµ ÐœÐµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ ÐœÐ° Ð²Ð°ÑÐµÐ¹ ÑÐžÑÑÐµÐŒÐµ. ÐÐŸ ÐŒÐœÐŸÐ³ÐžÑ
+ Ð²ÐµÑÑÐžÑÑ
+ Linux Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Perl ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ. Ð ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐž <CrossRef target="Chapter" ref="appendix_associated_software"/> Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ·ÐœÐ°ÑÑ, Ð³ÐŽÐµ Ðž ÐºÐ°Ðº Ð¿ÑÐžÐŸÐ±ÑÐµÑÑÐž Apache Ðž Perl.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_source">
+<Title>
+<Text id="80">ÐÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐºÐŸÐŽ ÐŽÐ»Ñ Unix</Text>
+</Title>
+<Content>
+<Text id="81">ÐÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐºÐŸÐŽ ÐŽÐ»Ñ Unix ÑÐ²Ð»ÑÐµÑÑÑ ÑÐ°ÐºÐžÐŒ Ð¶Ðµ, ÐºÐ°Ðº Ðž ÐŽÐ»Ñ Windows. ÐÐœ Ð±ÑÐ» ÑÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°Ðœ Ðž Ð¿ÑÐŸÐ²ÐµÑÐµÐœ ÐœÐ° Linux, Solaris, Macintosh OS/X. ÐÐ°ÑÑÑÐŸÐžÑÑ ÑÑÐŸÑ ÐºÐŸÐŽ Ð¿ÐŸÐŽ ÐŽÑÑÐ³ÐžÐµ Ð²ÐµÑÑÐžÐž Unix Ð±ÑÐŽÐµÑ ÐœÐµ ÑÐ»ÐŸÐ¶ÐœÐŸ.</Text>
+<Text id="82">ÐÐ»Ñ ÐºÐŸÐŒÐ¿ÐžÐ»ÑÑÐžÐž ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ³ÐŸ ÐºÐŸÐŽÐ° ÐœÐ° Unix Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ ÐžÐŒÐµÑÑ</Text>
+<BulletList>
+<Bullet>
+<Text id="83">GCC, Gnu C++ compiler</Text>
+</Bullet>
+<Bullet>
+<Text id="84">GDBM, Gnu database manager.</Text>
+</Bullet>
+</BulletList>
+<Text id="85">ÐÐ»Ñ Ð·Ð°Ð¿ÑÑÐºÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Greenstone Ð²Ð°ÐŒ ÑÐ°ÐºÐ¶Ðµ Ð¿ÐŸÐœÐ°ÐŽÐŸÐ±ÐžÑÑÑ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Ðž Perl, ÐºÐ°Ðº Ð±ÑÐ»ÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐŸ Ð²ÑÑÐµ.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_installation">
+<Title>
+<Text id="86">Ð£ÑÑÐ°ÐœÐŸÐ²ÐºÐ° Unix</Text>
+</Title>
+<Content>
+<Text id="87">ÐÐ»Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ð²ÐµÑÑÐžÐž Unix Ñ ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐºÐ° Ð²ÑÑÐ°Ð²ÑÑÐµ ÐŽÐžÑÐº Ð² ÐŽÐžÑÐºÐŸÐ²ÐŸÐŽ ÐžÐÐ²ÐµÐŽÐžÑÐµ ÑÐ»ÐµÐŽÑÑÑÐžÐµ ÐºÐŸÐŒÐ°ÐœÐŽÑ:</Text>
+<Table class="hidden" id="table_commands">
+<Title/>
+<TableContent>
+<tr>
+<th width="126">
+<CodeLine>mount /cdrom</CodeLine>
+</th>
+<th width="281">
+<Text id="88">Â (ÑÑÐ° ÐºÐŸÐŒÐ°ÐœÐŽÐ° ÐŒÐŸÐ¶ÐµÑ ÐŸÑÐ»ÐžÑÐ°ÑÑÑ ÐŸÑ ÐŸÐŽÐœÐŸÐ¹ Ð²ÐµÑÑÐžÐž Ðº ÐŽÑÑÐ³ÐŸÐ¹; ÐœÐ°Ð¿ÑÐžÐŒÐµÑ ÐœÐ° OS/X Ð²Ñ Ð²Ð²ÐŸÐŽÐžÐ³Ð³ÐµÐŽÐžÑÐµÐºÑÐŸÑÐžÑÂ <i>/VolumesÂ </i>Â a Ð·Ð°ÑÐµÐŒÂ <i>Ð²</i>Â ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐŽÐ»Ñ CD-ROM)</Text>
+</th>
+</tr>
+<tr>
+<th width="126">
+<CodeLine>cd /cdrom</CodeLine>
+</th>
+<th width="281">
+<Text id="89">change directory to the CD-ROM's top level</Text>
+</th>
+</tr>
+<tr>
+<th width="126">
+<CodeLine>cd Unix</CodeLine>
+</th>
+<th width="281">
+<Text id="90">ÐÐ·ÐŒÐµÐœÐžÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÑÑÐŽÐ°, Ð³ÐŽÐµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÂ <br/>ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐŸÐœÐœÑÐ¹ ÑÐºÑÐžÐ¿Ñ Unix .</Text>
+</th>
+</tr>
+<tr>
+<th width="126">
+<CodeLine>sh Install.sh</CodeLine>
+</th>
+<th width="281">
+<Text id="91">ÐÐ°ÑÐ°ÑÑ Ð¿ÑÐŸÑÐµÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž (Ð±ÑÐºÐ²ÐµÐœÐœÐŸÐµ ÑÐŸÑÐµÑÐ°ÐœÐžÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÑÐ°Ðº ÐºÐ°Ðº Ð²ÐŸ ÐŒÐœÐŸÐ³ÐžÑ
+ ÑÐ»ÑÑÐ°ÑÑ
+ Ð²Ñ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ ÐœÐ°ÑÐ°ÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ Ð¿ÑÑÐŒÐŸ Ñ ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐºÐ°).</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="92">ÐÐ°ÑÐ°ÑÑ Ð¿ÑÐŸÑÐµÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž (Ð±ÑÐºÐ²ÐµÐœÐŸÐµ ÑÐŸÑÐµÑÐ°ÐœÐžÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÑÐ°Ðº ÐºÐ°Ðº Ð²ÐŸ ÐŒÐœÐŸÐ³ÐžÑ
+ ÑÐ»ÑÑÐ°ÑÑ
+ Ð²Ñ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ ÐœÐ°ÑÐ°ÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ Ð¿ÑÑÐŒÐŸ Ñ ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐºÐ°).</Text>
+<Text id="93">ÐÐŸÑÐ»ÐµÐŽÐœÑÑ ÐºÐŸÐŒÐ°ÐœÐŽÐ° Ð²ÑÐ·ÑÐ²Ð°ÐµÑ ÐžÐœÑÐµÑÐ°ÐºÑÐžÐ²ÐœÐŸÐµ ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÐŸÐµ ÐŸÐºÐœÐŸ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ Ð·Ð°Ð¿ÑÐ°ÑÐžÐ²Ð°ÐµÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐ°Ñ ÐŽÐ»Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Greenstone. Ð ÑÑÐŸÐŒ ÐŸÐºÐœÐµ Ð¿ÐŸÐŒÐµÑÐ°ÐµÑÑÑ ÐŽÐµÑÐ°Ð»ÑÐœÑÐ¹ ÐŸÑÑÐµÑ ÐŸ ÑÐŸÐŒ, ÑÑÐŸ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ. ÐÑÐŸÑÐµÑÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐœÐ°ÑÐžÐœÐ°ÐµÑÑÑ Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸ Ñ Ð²Ð°Ñ Ð·Ð°Ð¿ÑÐ°ÑÐžÐ²Ð°ÐµÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ, Ð² ÐºÐŸÑÐŸÑÑÑ Ð²Ñ Ð¶ÐµÐ»Ð°ÐµÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ. ÐÐµÑÐ²ÑÐ¹ ÑÐ°Ð¹Ð», ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐŒÐµÑÐ°ÐµÑÑÑ Ð² ÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ, - ÑÑÐŸ ÑÐ°Ð¹Ð» "ÑÐŽÐ°Ð»ÐžÑÑ" (uninstall), ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÑÐžÑÐ°ÐµÑ ÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐŸÑ ÑÐ°Ð¹Ð»ÐŸÐ² ÐœÐµÐ·Ð°Ð²ÐµÑÑÐµÐœÐœÐŸÐ¹ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž, Ð² ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž Ñ Ð²Ð°Ñ Ð²ÐŸÐ·ÐœÐžÐºÐœÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ ÐžÐ»Ðž Ð²Ñ Ð¿ÑÐžÐŸÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÑ. Ð¡Ð»ÐµÐŽÑÑÑÐžÐ¹ - ÑÐ°Ð³ Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ Ð²ÑÐ±ÑÐ°ÑÑ ÐŒÐµÐ¶ÐŽÑ Ð±ÐžÐœÐ°ÑÐœÑÐŒ Ðž ÐžÑÑ
+ÐŸÐŽÐœÑÐŒ ÐºÐŸÐŽÐ°ÐŒÐž. ÐÐ°ÑÐµÐŒ Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ Ð²ÐŸÐ¿ÑÐŸÑÑ ÐŸ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ°Ñ
+ Ð²Ð°ÑÐµÐ³ÐŸ WWW-Ð±ÑÐ°ÑÐ·ÐµÑÐ°. ÐÐ°ÐŒ ÐœÑÐ¶ÐœÐŸ ÐžÐŒÐµÑÑ ÐžÑÐ¿ÑÐ°Ð²ÐœÑÑ cgi executable directory (ÐŸÐ±ÑÑÐœÐŸ ÐœÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ "cgi-bin" Ð² ÑÐžÑÑÐµÐŒÐ°Ñ
+ Unix); Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐœÐŸÐ²ÑÑ Ð»ÐžÐ±ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÑÐ°ÑÑÑ. ÐÑÐ»Ðž Ð²Ñ ÑÐŸÐ·ÐŽÐ°ÐŽÐžÑÐµ ÐœÐŸÐ²ÑÑ, ÑÐŸ Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð²Ð²ÐµÑÑÐž ÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð»Â  ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°. Ð Ð»ÑÐ±ÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ Ð²Ð²ÐµÑÑÐž WWW-Ð°ÐŽÑÐµÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž cgi. ÐÐœÑÐµÑÐ°ÐºÑÐžÐ²ÐœÑÐµ ÐŸÐºÐœÐ° Ð¿ÑÐŸÐ²ÐµÐŽÑÑ Ð²Ð°Ñ ÑÐµÑÐµÐ· Ð²ÐµÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐŸÐœÐœÑÐ¹ Ð¿ÑÐŸÑÐµÑÑ. ÐÑÐµÐœÑ Ð²Ð°Ð¶ÐœÐŸ Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð²Ð²ÐŸÐŽÐžÑÑÂ Â  file permissionsÂ Â Â Â Â Â  Ð² ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑÑ
+, Ð³ÐŽÐµ Ñ Ð²Ð°Ñ Ð¿ÐŸÑÑÐµÐ±ÑÑÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ. Ð ÐœÐ°ÐºÐŸÐœÐµÑ Ñ Ð²Ð°Ñ Ð¿ÐŸÑÑÐµÐ±ÑÑÑ Ð¿Ð°ÑÐŸÐ»Ñ. ÐÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ "Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑ" Ð²Ð²ÐµÐŽÐžÑÐµ "admin".</Text>
+<Text id="94">ÐÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, Greenstone ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž /usr/local/gsdl, ÐµÑÐ»Ðž ÑÑÑÐ°ÐœÐŸÐ²ÐºÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑ "ÐºÐŸÑÐœÐµÐ²ÐŸÐ¹"(Ð³ÐŸÐŸ1) Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ, Ð° Ð² ÐžÐœÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ - Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ~/gsdl (Ð³ÐŽÐµ "~" ÑÐ²Ð»ÑÐµÑÑÑ Ð³Ð»Ð°Ð²ÐœÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐµÐ¹ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ).</Text>
+<Text id="95">Ð£ÑÑÐ°ÐœÐŸÐ²ÐºÐ° Ð±ÐžÐœÐ°ÑÐœÐŸÐ³ÐŸ ÐºÐŸÐŽÐ° Ð·Ð°ÐœÐžÐŒÐ°ÐµÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŒÐžÐœÑÑ. ÐÑÐ»Ðž Ð²Ñ ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÐµ ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐºÐŸÐŽ, ÑÐŸ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐŸÐœÐœÑÐ¹ ÑÐºÑÐžÐ¿Ñ Ð±ÑÐŽÐµÑ ÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÑÑ ÐµÐ³ÐŸ, ÑÑÐŸ Ð·Ð°Ð¹ÐŒÐµÑ ÐŸÑ 10 ÐŒÐžÐœÑÑ ÐŽÐŸ ÑÐ°ÑÐ°, Ð² Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÑÐºÐŸÑÐŸÑÑÐž Ð²Ð°ÑÐµÐ³ÐŸ Ð¿ÑÐŸÑÐµÑÑÐŸÑÐ°.</Text>
+<Text id="96">ÐÐ»Ñ ÑÐŽÐ°Ð»ÐµÐœÐžÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð²Ð²ÐµÐŽÐžÑÐµ</Text>
+<CodeLine>cd ~/gsdlÂ Â Â </CodeLine>
+<Text id="97">Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ÐžÐ»Ðž /user/local/gsdl, Ð° "ÐºÐŸÑÐœÐµÐ²ÐŸÐ¹" Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ÐŒÐŸÐ¶ÐµÑ Ð²Ð²ÐµÑÑÐž ÐºÐŸÐŒÐ°ÐœÐŽÑ</Text>
+<CodeLine>sh Uninstall.sh</CodeLine>
+<Text id="98">Ð Ð¿ÑÐŸÑÐµÑÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ð¿ÐŸÐŒÐžÐŒÐŸ ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ðž ÐŽÑÑÐ³ÐžÐµÂ  ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Greenstone ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž; ÑÐ²ÐµÐŽÐµÐœÐžÑ ÐŸÐ± ÐŸÑÑÐ°Ð»ÑÐœÑÑ
+ Ð²Ñ ÐœÐ°Ð¹ÐŽÐµÑÐµ Ð² <CrossRef target="Chapter" ref="greenstone_collections"/> ÑÐ°ÑÑÐž.</Text>
+</Content>
+</Subsection>
+<Subsection id="unix_webserver_configuration">
+<Title>
+<Text id="99">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐ° ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ° Unix</Text>
+</Title>
+<Content>
+<Text id="100">ÐÑÐ»Ðž ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÑÐ¶Ðµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ, ÑÐŸ Ð² ÐµÐ³ÐŸ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ Ð²ÐœÐµÑÑÐž ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ, ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ ÐŸÐœ Ð±ÑÐ» ÑÐŸÐ²ÐŒÐµÑÑÐžÐŒ Ñ Greenstone. Ð ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐŸÐœÐœÐŸÐŒ ÑÐºÑÐžÐ¿ÑÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐŸ, ÐºÐ°Ðº ÑÑÐŸ ÐœÐ°ÐŽÐŸ ÑÐŽÐµÐ»Ð°ÑÑ. ÐÐ»Ñ Ð²Ð°ÑÐµÐ³ÐŸ ÑÐŽÐŸÐ±ÑÑÐ²Ð° ÑÑÐŸÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐŸÐœÐœÑÐ¹ ÑÐºÑÐžÐ¿Ñ Ð·Ð°Ð¿ÐžÑÐ°Ðœ Ð² ÑÐ°Ð¹Ð»Ðµ INSTALL RECORD Ð² ÑÐŸÐ¹ Ð¶Ðµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, Ð² ÐºÐŸÑÐŸÑÑÑ Ð²Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÐ»Ðž Greenstone</Text>
+<Text id="101">ÐÑÐ»Ðž Ñ Ð²Ð°Ñ ÐµÑÐµ ÐœÐµÑ ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°, ÑÐŸ ÐµÐ³ÐŸ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ. Ð ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐž <CrossRef target="Chapter" ref="appendix_associated_software"/> ÐµÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸÐ± Apache. ÐÐ°ÑÐµÐŒ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ ÐµÐ³ÐŸ ÐœÐ°ÑÑÑÐŸÐžÑÑ. Ð <CrossRef target="Chapter" ref="setting_up_webserver"/> ÑÐ°ÑÑÐž ÐŸÐ¿ÐžÑÐ°ÐœÑ ÑÐ°ÑÑÐž WWW-ÑÐµÑÐ²ÐµÑÐ° Apache, ÐºÐŸÑÐŸÑÑÐµ Ð²Ð·Ð°ÐžÐŒÐŸÑÐ²ÑÐ·Ð°ÐœÑ Ñ Greenstone, Ðž ÑÐŸ, ÐºÐ°Ðº ÐžÑ
+ ÐœÑÐ¶ÐœÐŸ ÐžÐ·ÐŒÐµÐœÐžÑÑ. ÐÑÐµ ÑÐ²ÐŸÐŽÐžÑÑÑ Ðº ÑÐŸÐŒÑ, ÑÑÐŸ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ Ð²Ð²ÐµÑÑÐž Ð¿ÐŸÐ»ÐŽÑÐ¶ÐžÐœÑ ÑÑÑÐŸÐº Ð² ÐµÐ³ÐŸ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð».</Text>
+<Text id="102">ÐÐ°ÐŒ ÐœÐµ ÐŸÐ±ÑÐ·Ð°ÑÐµÐ»ÑÐœÐŸ Ð±ÑÑÑ ÐºÐŸÑÐœÐµÐ²ÑÐŒ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐŒ Unix ÐŽÐ»Ñ ÑÐŸÐ²ÐµÑÑÐµÐœÐžÑ ÐŸÐ¿ÐžÑÐ°ÐœÐœÐŸÐ³ÐŸ Ð²ÑÑÐµ Ð¿ÑÐŸÑÐµÑÑÐ° ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž. ÐÐŸ ÐºÐŸÐ³ÐŽÐ° ÐŽÐµÐ»ÐŸ ÐŽÐŸÑ
+ÐŸÐŽÐžÑ ÐŽÐŸ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ° Apache, ÑÐŸÐ³ÐŽÐ° Ð²Ð°ÐŒÂ Â  Ð¿ÐŸÐœÐ°ÐŽÐŸÐ±ÑÑÑÑ Ð¿ÑÐžÐ²ÐžÐ»ÐµÐ³ÐžÐž ÐºÐŸÑÐœÐµÐ²ÐŸÐ³ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ. ÐÑÐ»Ðž Ð²Ñ Ð¶ÐµÐ»Ð°ÐµÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ð²ÑÐŸÑÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Apache, ÑÐŸ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÑÐŸ ÑÐŽÐµÐ»Ð°ÑÑ, ÐŽÐ°Ð¶Ðµ ÐµÑÐ»Ðž ÐœÐ°Â  Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÑÐ¶Ðµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ ÐŸÐŽÐžÐœ.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="how_to_find_greenstone">
+<Title>
+<Text id="103">Ð Ð°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐµ Greenstone</Text>
+</Title>
+<Content>
+<Subsection id="local_library_windows_only">
+<Title>
+<Text id="104">ÐÐŸÐºÐ°Ð»ÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° (ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ»Ñ Windows)</Text>
+</Title>
+<Content>
+<Text id="105">ÐÑÐ»Ðž Ð²Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ ÐÐŸÐºÐ°Ð»ÑÐœÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ, ÑÐŸ Ð¿ÑÐŸÑÑÐŸ Ð·Ð°Ð¿ÑÑÑÐžÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Greenstone ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ ÐÑÑÐºÂ  Ð² ÐŒÐµÐœÑ. Ð­ÑÐŸ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð·Ð°Ð³ÑÑÐ¶Ð°ÐµÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, Ðž ÐœÐ° ÑÐºÑÐ°ÐœÐµ Ð² ÐŸÐºÐœÐµ Ð²Ð°ÑÐµÐ³ÐŸ Ð±ÑÐ°ÑÐ·ÐµÑÐ° Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ ÑÑÐ°ÑÑÐŸÐ²Ð°Ñ ÑÑÑÐ°ÐœÐžÑÐ°. Ð¡ ÑÑÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ ÑÐ°ÐºÐ¶Ðµ ÐŽÐŸÑÑÑÐ¿ÐœÐ° ÐÐµÐ»Ñ-Â Â Â  ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. Ð ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÐŸÐŒ&lt;*&gt;ÐºÐÐµ ÐŒÐµÐœÑ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÐ·ÐŒÐµÐœÐžÑÑ Ð²Ð°Ñ Ð±ÑÐ°ÑÐ·ÐµÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ. ÐÐµÑ ÐœÐžÐºÐ°ÐºÐŸÐ¹ ÑÐ°Ð·ÐœÐžÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ Ð»Ðž Ð²Ñ Internet Explorer ÐžÐ»Ðž Netscape Navigator, Ð·Ð° ÐžÑÐºÐ»ÑÑÐµÐœÐžÐµÐŒ ÑÐŸÐ³ÐŸ, ÑÑÐŸ ÐµÑÐ»Ðž Ñ Ð²Ð°Ñ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ Windows 2000, ÑÐŸ ÐŒÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Internet Explorer.</Text>
+</Content>
+</Subsection>
+<Subsection id="web_library_windows_and_unix">
+<Title>
+<Text id="106">ÐÐœÑÐµÑÐœÐµÑ-ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° (Windows Ðž Unix)</Text>
+</Title>
+<Content>
+<Text id="107">ÐÑÐ»Ðž Ð²Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ, ÑÐŸ Ð¿ÐŸÑÐ»Ðµ Ð·Ð°Ð²ÐµÑÑÐµÐœÐžÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ðž ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÑÐ»ÐµÐŽÑÑÑÐžÐ¹ WWW-Ð°ÐŽÑÐµÑ ÐŽÐ»Ñ Ð²Ñ
+ÐŸÐŽÐ° Ð² Ð²Ð°ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ:</Text>
+<Text id="108"><i>http://localhost/gsdl/cgi-bin/library</i></Text>
+<Text id="109">ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Greenstone ÑÐ°ÐºÐ¶Ðµ ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÐ° Ñ ÑÑÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="the_collector">
+<Title>
+<Text id="110">ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ</Text>
+</Title>
+<Content>
+<Text id="111">Ð ÑÑÐ°ÑÑÐŸÐ²ÐŸÐŒ ÐŸÐºÐœÐµ Greenstone ÐµÑÑÑ ÑÑÑÐ»ÐºÐ° Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐŸÑÑ (Collector).</Text>
+</Content>
+</Subsection>
+<Subsection id="administration">
+<Title>
+<Text id="112">ÐÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</Title>
+<Content>
+<Text id="113">Ð¢Ð°ÐŒ ÑÐ°ÐºÐ¶Ðµ ÐµÑÑÑ ÑÑÑÐ»ÐºÐ° Ðº ÑÑÑÐ°ÐœÐžÑÐµ ÐÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ. ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ "Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑ" ÐœÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ admin, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Ð¿Ð°ÑÐŸÐ»Ñ, ÑÐºÐ°Ð·Ð°ÐœÐœÑÐ¹ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÐÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž. ÐÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑ ÐŒÐŸÐ¶ÐµÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ ÐœÐŸÐ²ÑÑ
+ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Ðž ÑÐ°Ð·ÑÐµÑÐ°ÐµÑ ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐœÐŸÐ²ÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="the_greenstone_librarian_interface_(gli)">
+<Title>
+<Text id="114">Â  ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Greenstone (GLI)</Text>
+</Title>
+<Content>
+<Text id="115">ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Greenstone (GLI) â ÑÑÐŸ ÐžÐœÑÑÑÑÐŒÐµÐœÑ ÐŽÐ»Ñ Ð¿ÐŸÐŒÐŸÑÐž ÐÐ°ÐŒ Ð¿ÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÑÐžÑÑÐŸÐ²ÑÑ
+ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐº Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ Greenstone. ÐÐœ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐµÑ ÐÐ°ÐŒ ÐŽÐŸÑÑÑÐ¿ Ðº ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐŒ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑÐŒ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž ÑÐŽÐŸÐ±ÐœÐŸÐŒÑ Ð² ÑÐ°Ð±ÐŸÑÐµ ÐžÐœÑÐµÑÑÐµÐ¹ÑÑ Â«Ð¿ÑÐœÐºÑ Ðž ÑÐµÐ»ÑÐŸÐºÂ».</Text>
+<Text id="116">GLI ÐžÐœÑÑÐ°Ð»Ð»ÐžÑÑÐµÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð²ÐŸ Ð²ÑÐµÑ
+ ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²Ð°Ñ
+ Greenstone. ÐÐœ Ð¿ÐŸÐŒÐµÑÐµÐœ Ð² Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÐž gli Ð³Ð»Ð°Ð²ÐœÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Greenstone (C:\Program Files\gsdl\gli Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ). ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÑÐŸ, ÑÑÐŸ ÐŸÐœ Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑÑÑÂ  Ð² ÑÐŸÑÐµÑÐ°ÐœÐžÐž Ñ Greenstone Ðž ÐœÐµ Ð±ÑÐŽÐµÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐºÐŸÑÑÐµÐºÑÐœÐŸ, ÐµÑÐ»Ðž ÐœÐµ Ð¿ÐŸÐŒÐµÑÐµÐœ Ð² Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÑ Ð¿ÑÐž ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Greenstone. ÐÑÐ»Ðž ÐÑ Ð·Ð°Ð³ÑÑÐ·ÐžÐ»Ðž ÐŸÐŽÐžÐœ ÐžÐ· ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²ÐŸÐ² Greenstone, ÑÐŸ ÑÑÐµÐ±ÑÐµÐŒÐŸÐµ ÐŽÐŸÐ»Ð¶ÐœÐŸ ÐžÐŒÐµÑÑ ÐŒÐµÑÑÐŸ.</Text>
+<Text id="117">Ð§ÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ GLI, ÐœÐ° ÐÐ°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÐŽÐŸÐ»Ð¶ÐœÐ° ÐžÐŒÐµÑÑÑÑ Java Runtime Environment (JRE). ÐÑÐ»Ðž ÑÑÐŸ ÐœÐµ ÑÐŽÐµÐ»Ð°ÐœÐŸ, ÑÐŸ Ð¿ÑÐž ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž ÐÐ°ÐŒ Ð±ÑÐŽÐµÑ Ð¿ÑÐµÐŽÐ»ÐŸÐ¶ÐµÐœÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ð²ÐµÑÑÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐœÐ° CD-ROM. ÐÑÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž Unix ÐÑ Ð±ÑÐŽÐµÑÐµ ÐœÑÐ¶ÐŽÐ°ÑÑÑÑ ÑÐ°ÐºÐ¶Ðµ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ Ð±ÑÐ» ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ PerlÂ  (ÐŽÐ»Ñ Windows Perl ÑÐ¶Ðµ Ð²ÐºÐ»ÑÑÐµÐœ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone). ÐÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, ÑÐŸÐŸÐ±ÑÐžÑÐµ ÐŸ Ð»ÑÐ±ÑÑ
+ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ°Ñ
+, ÐºÐŸÑÐŸÑÑÐµ Ð²ÐŸÐ·ÐœÐžÐºÐ°ÑÑ Ñ ÐÐ°Ñ Ð¿ÑÐž Ð·Ð°Ð¿ÑÑÐºÐµ ÐžÐ»Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Ð¿ÐŸ Ð°ÐŽÑÐµÑÑ:greenstone@cs.waikato.ac.nz.</Text>
+<Subsection id="running_under_windows">
+<Title>
+<Text id="118">ÐÐ°Ð¿ÑÑÐº Ð¿ÐŸÐŽ Windows</Text>
+</Title>
+<Content>
+<Text id="119">Ð§ÑÐŸÐ±Ñ Ð·Ð°Ð¿ÑÑÑÐžÑÑ GLI Ð¿ÐŸÐŽ Windows, ÐŸÐ±ÑÐ°ÑÐžÑÐµÑÑ Ðº Ð¿Ð°Ð¿ÐºÐµ gli Ð² ÐÐ°ÑÐµÐ¹ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Greenstone, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, Windows Explorer, Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ ÐŽÐ²Ð°Ð¶ÐŽÑ ÐœÐ° ÑÐ°Ð¹Ð»Ðµ Ñ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµÐŒ gli.bat. Ð­ÑÐŸÑ ÑÐ°Ð¹Ð» Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ ÐœÐ°Ð»ÐžÑÐžÐµ Greenstone, JRE Ðž Perl Ðž Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑ GLI.</Text>
+</Content>
+</Subsection>
+<Subsection id="running_under_unix">
+<Title>
+<Text id="120">ÐÐ°Ð¿ÑÑÐº Ð¿ÐŸÐŽ Unix</Text>
+</Title>
+<Content>
+<Text id="121">Ð§ÑÐŸÐ±Ñ Ð·Ð°Ð¿ÑÑÑÐžÑÑ GLI Ð¿ÐŸÐŽ Unix, ÐžÐ·ÐŒÐµÐœÐžÑÐµ ÐœÐ° gli ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ Ð² ÐÐ°ÑÐµÐ¹ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ Greenstone, Ð° Ð·Ð°ÑÐµÐŒ Ð·Ð°Ð¿ÑÑÑÐžÑÐµ ÑÐºÑÐžÐ¿ÑÂ  gli.sh. Ð­ÑÐŸÑ ÑÐºÑÐžÐ¿Ñ Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ ÐœÐ°Ð»ÐžÑÐžÐµ Greenstone, JRE Ðž Perl ÐœÐ° Ð¿ÐŸÐžÑÐºÐŸÐ²ÐŸÐŒ Ð¿ÑÑÐž Ðž Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑ GLI.</Text>
+</Content>
+</Subsection>
+<Subsection id="getting_help">
+<Title>
+<Text id="122">ÐÐŸÐ»ÑÑÐµÐœÐžÐµ Ð¿ÐŸÐŒÐŸÑÐž</Text>
+</Title>
+<Content>
+<Text id="123">GLI Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐµÑ ÐŸÐ±ÑÐžÑÐœÑÐµ ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÑÐµ ÑÑÐµÐŽÑÑÐ²Ð° Ð¿ÐŸÐŒÐŸÑÐž. Ð§ÑÐŸÐ±Ñ Ð¿ÐŸÐ»ÑÑÐžÑÑ Ð¿ÐŸÐŒÐŸÑÑ, ÑÐµÐ»ÐºÐœÐžÑÐµ ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ Help Ð² Ð²ÐµÑÑ
+ÐœÐµÐ¹ Ð¿ÑÐ°Ð²ÐŸÐ¹ ÑÐ°ÑÑÐž ÑÐºÑÐ°ÐœÐ°. Ð­ÑÐŸ ÐŸÑÐºÑÐŸÐµÑ ÑÐµÐºÑÑ ÑÐ°Ð·ÐŽÐµÐ»Ð°, ÐºÐŸÑÐŸÑÑÐ¹ ÐºÐ°ÑÐ°ÐµÑÑÑ ÑÐŸÐ³ÐŸ, ÑÑÐŸ ÐÑ ÐŽÐµÐ»Ð°ÐµÑÐµ â ÐºÐ°ÐºÐ°Ñ ÐžÐ· Ð¿Ð°ÐœÐµÐ»ÐµÐ¹ GLI Ð² ÐœÐ°ÑÑÐŸÑÑÐµÐµ Ð²ÑÐµÐŒÑ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐµÐ»ÐºÐœÑÑÑ Ð¿ÐŸ ÑÐµÐºÑÑÑ Ð¿ÐŸÐŒÐŸÑÐž, ÑÑÐŸÐ±Ñ ÐžÐ·ÑÑÐžÑÑ ÑÐŸ, ÑÑÐŸ ÐÐ°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð·ÐœÐ°ÑÑ. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÑÑÐŸ.</Text>
+</Content>
+</Subsection>
+<Subsection id="compiling_gli">
+<Title>
+<Text id="124">ÐÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÐœÐžÐµ GLI</Text>
+</Title>
+<Content>
+<Text id="125">ÐÑÐ»Ðž ÐÑ Ð·Ð°Ð¿ÑÑÑÐžÐ»Ðž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²Ð° Greenstone, ÑÐŸ ÐÑ Ð±ÑÐŽÐµÑÐµ ÐžÐŒÐµÑÑ ÐžÑÑ
+ÐŸÐŽÐœÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑÂ  Java ÐžÐ· GLI. Ð§ÑÐŸÐ±Ñ Ð²ÑÐ¿ÐŸÐ»ÐœÐžÑÑ ÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÐœÐžÐµ, ÐÐ°Ñ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑ ÐŽÐŸÐ»Ð¶ÐµÐœ ÐžÐŒÐµÑÑÂ <i>Java Development Kit</i>. Ð Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐž <CrossRef target="Chapter" ref="appendix_associated_software"/> ÐŽÐ°ÐµÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸÑÐœÐŸÑÐžÑÐµÐ»ÑÐœÐŸ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐµÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ. Ð§ÑÐŸÐ±Ñ ÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÑÑ ÐžÑÑ
+ÐŸÐŽÐœÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, Ð²Ð²ÐµÐŽÐžÑÐµ ÑÐ°Ð¹Ð»ÑÂ <i>makegli.bat (</i>Â Windows)Â  ÐžÐ»ÐžÂ Â <i>makegli.sh</i>Â (Unix). ÐÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð·Ð°Ð²ÐµÑÑÐµÐœÐŸ, ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð·Ð°Ð¿ÑÑÑÐžÑÑ GLI, ÐºÐ°Ðº Ð±ÑÐ»ÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐŸ Ð²ÑÑÐµ.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="testing_and_troubleshooting">
+<Title>
+<Text id="126">ÐÑÐŸÐ²ÐµÑÐºÐ° Ðž Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÐµ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ</Text>
+</Title>
+<Content>
+<Text id="127">ÐÐ»Ñ Ð¿ÑÐŸÐ²ÐµÑÐºÐž Ðž ÐŸÐ±Ð·ÐŸÑÐ°Â <i>Greenstone</i>, Ð¿ÑÐŸÑÑÐŸ ÐœÐ°ÑÐœÐžÑÐµ Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž ÐŽÑÑÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ Ð²Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÐ»Ðž. ÐÐ°Ð¶ÐžÐŒÐ°Ð¹ÑÐµ ÐœÐ° Ð²ÑÐµ ÐºÐœÐŸÐ¿ÐºÐž Ð±ÐµÐ· ÐŸÐ¿Ð°ÑÐµÐœÐžÑ -Ð²Ñ ÐœÐžÑÐµÐ³ÐŸ ÐœÐµ Ð¿ÐŸÐ²ÑÐµÐŽÐžÑÐµ. ÐÑÐ»Ðž Ð·Ð°ÐŽÐµÑÐ¶Ð°ÑÑ ÐºÑÑÑÐŸÑ ÐŒÑÑÐž ÐœÐ° ÐºÐ°ÐºÐŸÐŒ-Ð»ÐžÐ±ÐŸ ÑÐžÑÑÐœÐºÐµÐ»Ð³ÐŸÑÐžÑÑÑ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐµ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐœÐ°Ð¿ÐžÑÐ°ÐœÐŸ ÑÐŸ, ÑÑÐŸ Ð¿ÑÐŸÐžÐ·ÐŸÐ¹ÐŽÐµÑ, ÐµÑÐ»Ðž Ð²Ñ ÐœÐ°Ð¶ÐŒÐµÑÐµ ÐœÐ° ÐœÐµÐ³ÐŸ. Ð­ÐºÑÐ¿ÐµÑÐžÐŒÐµÐœÑÐžÑÑÐ¹ÑÐµ! ÐÐ»Ñ Ð±ÐŸÐ»ÑÑÐµÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÑÐŒÐŸÑÑÐžÑÐµÂ <i>Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ.</i>
+</Text>
+<Subsection id="troubleshooting">
+<Title>
+<Text id="128">Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÐµ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ</Text>
+</Title>
+<Content>
+<Table id="table_troubleshooting">
+<Title/>
+<TableContent>
+<tr>
+<th width="140">Â </th>
+<th width="161">
+<Text id="129"><b>ÐÑÐŸÐ±Ð»ÐµÐŒÐ°</b></Text>
+</th>
+<th width="242">
+<Text id="130"><b>ÐÐŸÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="131">
+<b>ÐÐŸÐºÐ°Ð»ÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° (ÑÐŸÐ»ÑÐºÐŸ Windows)</b>
+</Text>
+</th>
+<th width="161">
+<Text id="132">ÐÐŸÐ³ÐŽÐ° Ñ Ð·Ð°Ð¿ÑÑÐºÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÐºÐŸÐŒÐ¿ÑÑÑÐµÑ Ð¿ÑÐŸÑÐžÑ ÐŒÐµÐœÑ ÐœÐ°Ð±ÑÐ°ÑÑ ÐœÐŸÐŒÐµÑ ÐžÐœÑÐµÑÐœÐµÑ-Ð¿ÑÐŸÐ²Ð°Ð¹ÐŽÐµÑÐ°.</Text>
+</th>
+<th width="242">
+<Text id="133">ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐºÐœÐŸÐ¿ÐºÑ ÐÑÐŒÐµÐœÐ°.. ÐÐ±ÑÑÐœÐŸ ÑÑÐŸÐ³ÐŸ ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ, ÑÑÐŸÐ±Ñ ÑÐµÑÐžÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">Â </th>
+<th width="161">
+<Text id="134">ÐÐŸÐ³ÐŽÐ° Ñ Ð·Ð°Ð¿ÑÑÐºÐ°Ñ Greenstone, ÐºÐŸÐŒÐ¿ÑÑÑÐµÑ Ð¿ÑÐŸÐŽÐŸÐ»Ð¶Ð°ÐµÑ Ð·Ð°Ð¿ÑÐ°ÑÐžÐ²Ð°ÑÑ Ð¿ÐŸÐŽÐºÐ»ÑÑÐµÐœÐžÐµ Ðº ÐžÐœÑÐµÑÐœÐµÑ-Ð¿ÑÐŸÐ²Ð°Ð¹ÐŽÐµÑÑÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â </Text>
+</th>
+<th width="242">
+<Text id="135">ÐÑÐ±ÐµÑÐžÑÐµ "Restricted version"(ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÐœÐ°Ñ Ð²ÐµÑÑÐžÑ) Ð¿ÑÐž Ð·Ð°Ð¿ÑÑÐºÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ. ÐÐœÐ° ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ð»ÐžÑÑ Ð² Netscape.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">Â </th>
+<th width="161">
+<Text id="136">ÐÐŸÐ³ÐŽÐ° Ñ Ð¿ÑÑÐ°ÑÑÑ Ð¿ÐŸÐ¿Ð°ÑÑÑ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÑ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž, ÐŸÐœÐ° ÐœÐµ ÐŒÐŸÐ¶ÐµÑÂ Â Â Â Â Â Â Â Â Â </Text>
+</th>
+<th width="242">
+<Text id="137">ÐÑÐŸÐ²ÐµÑÑÑÐµ Ð²Ð°ÑÐž ÐÐœÑÐµÑÐœÐµÑ proxy - ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž Edit preferences Ð² Netscape Ðž Internet options (ÑÐ²ÐŸÐ¹ÑÑÐ²Ð° ÐŸÐ±ÐŸÐ·ÑÐµÐ²Ð°ÑÐµÐ»Ñ) Ð² Explorer</Text>
+</th>
+</tr>
+<tr>
+<th width="140">Â </th>
+<th width="161">
+<Text id="138">ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÐŸÑÐµÐœÑ ÐŒÐµÐŽÐ»ÐµÐœÐœÐŸ!</Text>
+</th>
+<th width="242">
+<Text id="139">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ Ð»Ðž Ð²Ñ Netscape Ð² Windows 2000? ÐÑÐ»Ðž ÑÑÐŸ ÑÐ°Ðº, ÑÐŸ Ð¿ÐŸÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Internet Explorer Ð² Windows 2000. Ð£ Windows 2000 ÑÑÑÐµÑÑÐ²ÑÐµÑ ÐºÐ°ÐºÐ°Ñ- ÑÐŸ ÐœÐµÑÐŸÐ²ÐŒÐµÑÑÐžÐŒÐŸÑÑÑ Ñ Netscape.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="142"><b>ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° (Windows Ðž Unix)</b></Text>
+</th>
+<th width="161">
+<Text id="143">ÐÐŸÑÐ»Ðµ Ð·Ð°Ð¿ÑÑÐºÐ° Apache, ÐŸÐœ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð·Ð°ÐºÑÑÐ²Ð°ÐµÑÑÑ.</Text>
+</th>
+<th width="242">
+<Text id="144">ÐÐŸÐ±Ð°Ð²ÑÑÐµ ÑÐºÐ°Ð·Ð°ÐœÐžÐµ ServerName localhost Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» Apache (<CrossRef target="Section" ref="apache_web_server"/>).</Text>
+</th>
+</tr>
+<tr>
+<th width="140">Â </th>
+<th width="161">
+<Text id="145">ÐÐŸÐ³ÐŽÐ° Ñ Ð¿ÑÑÐ°ÑÑÑ Ð¿ÐŸÐ¿Ð°ÑÑÑ Ð² ÑÐžÑÑÐŸÐ²ÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ, ÐžÐ·ÐŸÐ±ÑÐ°Ð¶Ð°ÐµÑÑÑ ÐŒÑÑÐŸÑ - Ð±ÐžÐœÐ°ÑÐœÑÐ¹ ÑÐ°Ð¹Ð»</Text>
+</th>
+<th width="242">
+<Text id="146">ÐÑÐŸÐ²ÐµÑÑÑÐµ ÐŽÐžÑÐµÐºÑÐžÐ²ÑÂ Â Â Â  ScriptAliasÂ Â Â Â Â  Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ Apache, ÑÐŽÐŸÑÑÐŸÐ²ÐµÑÑÑÐµÑÑ, ÑÑÐŸ ÐŸÐœÐ° ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐŽÐŸ ÐŽÐžÑÐµÐºÑÐžÐ²Ñ Alias (ÑÐŒÐŸÑÑÐžÑÐµ ÑÐ°ÑÑÑ 4.2 Ðž 4.3).</Text>
+</th>
+</tr>
+<tr>
+<th width="140">Â </th>
+<th width="161">
+<Text id="147">Ð¯ Ð¿ÐŸÐ¿Ð°ÐŽÐ°Ñ ÐœÐ° ÑÑÐ°ÑÑÐŸÐ²ÑÑ ÑÑÑÐ°ÐœÐžÑÑ Greenstone(<CrossRef target="Figure" ref="your_greenstone_home_page"/>), ÐœÐŸ ÐžÐºÐŸÐœÐºÐ° ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐµ Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ.</Text>
+</th>
+<th width="242">
+<Text id="148">ÐÐ°Ð¿ÑÑÑÐžÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ library (Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž cgi-bin) ÐžÐ· DOS ÐŽÐ»Ñ Ð·Ð°Ð¿ÑÑÐºÐ° ÐŸÑÐ»Ð°ÐŽÐºÐž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐžÂ Â  (debugging information) ÐŽÐ»Ñ ÐŸÐ±ÐœÐ°ÑÑÐ¶ÐµÐœÐžÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="140">
+<Text id="149"><b>ÐÐ±Ðµ Ð²ÐµÑÑÐžÐž</b></Text>
+</th>
+<th width="161">
+<Text id="150">ÐÐŸÐ³ÐŽÐ° Ñ Ð¿ÑÑÐ°ÑÑÑ Ð¿ÐŸÐ¿Ð°ÑÑÑ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÑÂ  ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐµ ÐŒÐŸÐ¶ÐµÑ ÐµÐµ ÐœÐ°Ð¹ÑÐž.Â Â Â Â Â Â Â Â Â Â Â Â Â Â </Text>
+</th>
+<th width="242">
+<Text id="151">ÐÐŸÐ¿ÑÑÐ°Ð¹ÑÐµÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ 127.0.0.1 Ð²ÐŒÐµÑÑÐŸ localhost . Ð­ÑÐŸ Ð·Ð°ÑÐµÐ·ÐµÑÐ²ÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐœÐŸÐŒÐµÑ IP Ð°ÐŽÑÐµÑÐ° Ðž Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœ ÑÐ»ÑÐ¶ÐžÑÑ, ÐºÐ°Ðº "loopback" ÐŽÐ»Ñ Ð²Ð°ÑÐµÐ³ÐŸ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="140">Â </th>
+<th width="161">
+<Text id="152">ÐÑÐ°ÑÐ·ÐµÑ ÐœÐµ ÐŒÐŸÐ¶ÐµÑ ÐœÐ°Ð¹ÑÐž main.cfgÂ Â Â Â Â </Text>
+</th>
+<th width="242">
+<Text id="153">ÐÑÐŸÐ²ÐµÑÑÑÐµ, ÑÑÑÐµÑÑÐ²ÑÑÑ Ð»Ðž ÑÐ°Ð¹Ð»Ñ Greenstone Ðž ÐŽÐŸÑÑÑÐ¿ÐœÑ Ð»Ðž ÐŸÐœÐž ÐŽÐ»Ñ ÑÑÐžÑÑÐ²Ð°ÐœÐžÑ. ÐÑÐ»Ðž Ð²Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ Ð¿ÐŸÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð·Ð°Ð¿ÑÑÑÐžÑÑÂ Â  Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑÂ Â  libraryÂ Â  Ñ ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž. ÐÑÐ»Ðž ÐŸÐœÐ° Ð·Ð°Ð¿ÑÑÑÐžÑÑÑ, ÑÐŸ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ° ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² file permissionsÂ Â  (ÑÐŒÐŸÑÑÐžÑÐµ ÑÐ°ÑÑÑ <CrossRef target="Section" ref="file_permissions"/>). ÐÑÐ»Ðž ÐœÐµÑ,Â Â  ÑÐŸÂ Â  Ð¿ÐµÑÐµÐŒÐµÐœÐœÐ°Ñ Ð² gsdlhome ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»ÐµÂ Â  gsdlsite.cfg ÐœÐ°Ð²ÐµÑÐœÑÐºÐ° ÐœÐ°ÑÑÑÐŸÐµÐœÐ° ÐœÐµÐ¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ (ÑÐŒÐŸÑÑÐžÑÐµ Ð§Ð°ÑÑÑ <CrossRef target="Section" ref="gsdlsite_configuration_file"/>)</Text>
+</th>
+</tr>
+<tr>
+<th width="140">Â </th>
+<th width="161">
+<Text id="154">Ð¯ ÐžÐŒÐµÑ ÐœÐµÐ¿ÑÐžÑÑÐœÐŸÑÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ</Text>
+</th>
+<th width="242">
+<Text id="155">ÐÑÐŸÑÑÐžÑÐµ Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ. Ð§Ð°ÑÑÑ <CrossRef external="User" lang="ru" target="Chapter" ref="making_greenstone_collections"/></Text>
+</th>
+</tr>
+<tr>
+<th width="140">Â </th>
+<th width="161">
+<Text id="156">Ð¯ ÐŽÐŸÐ±Ð°Ð²ÐžÐ» ÐœÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ, ÐœÐŸ ÐŸÐœÐ° ÐœÐµ ÐŒÐŸÐ¶ÐµÑ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑÑÑ.</Text>
+</th>
+<th width="242">
+<Text id="157">Ð£ÐŽÐŸÑÑÐŸÐ²ÐµÑÑÑÐµÑÑ, ÑÑÐŸ Ð²ÑÐµ, ÑÑÐŸ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž C:\Program Files\gsdl\etc, ÐŽÐŸÑÑÑÐ¿ÐœÐŸ ÐŽÐ»Ñ ÐŸÐ±ÑÐµÐ³ÐŸ ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ (ÑÐ°ÑÑÑ <CrossRef target="Section" ref="file_permissions"/>)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="learn_more">
+<Title>
+<Text id="158">Ð£Ð·ÐœÐ°ÑÑ Ð±ÐŸÐ»ÑÑÐµ</Text>
+</Title>
+<Content>
+<Text id="159">Ð§ÑÐŸÐ±Ñ ÑÐ·ÐœÐ°ÑÑ Ð±ÐŸÐ»ÑÑÐµ ÐŸ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÑÑÑÑ
+ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐÑÐžÐœÑÑÐŸÑÐœ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµÂ <i>Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÐÑÐžÐœÑÑÐŸÑÐœ</i>, Ð²ÐºÐ»ÑÑÐ°ÑÑÐµÐµ ÑÐ°ÐºÐžÐµ ÐŽÐµÑÐ°Ð»Ðž ÐºÐ°Ðº - ÑÑÑÑÐºÑÑÑÐ° ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹ Ðž ÐºÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð²ÐµÐ± ÑÐ°Ð¹ÑÐ° ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ³ÐŸ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐÑÐžÐœÑÑÐŸÑÐœ.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="greenstone_collections">
+<Title>
+<Text id="160">ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone</Text>
+</Title>
+<Content>
+<Text id="161">ÐÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Greenstone Ð²ÐºÐ»ÑÑÐµÐœÐŸ Ð² CD-ROM. ÐÑÐ»Ðž ÐÑ ÐžÐŒÐµÐµÑÐµ ÐŽÐŸÑÑÑÐ¿ Ðº ÐÐœÑÐµÑÐœÐµÑÑ, ÑÐŸ ÐŒÐœÐŸÐ³ÐŸ ÐŽÑÑÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð·Ð°Ð³ÑÑÐ¶ÐµÐœÐŸ Ñ Ð²ÐµÐ±-ÑÐ°Ð¹ÑÐ° ÐÐŸÐ²ÐŸÐ·ÐµÐ»Ð°ÐœÐŽÑÐºÐŸÐ³ÐŸ Ð¿ÑÐŸÐµÐºÑÐ° ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž (nzdl.org) Ð² Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð¿ÐŸÑÑÑÐŸÐµÐœÐœÐŸÐŒ ÐžÐ»Ðž ÐœÐµ Ð¿ÐŸÑÑÑÐŸÐµÐœÐœÐŸÐŒÂ  Ð²ÐžÐŽÐµ.</Text>
+<Text id="162">ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Greenstone â ÑÑÐŸ ÐœÐµÐ±ÐŸÐ»ÑÑÐ°Ñ, ÐŽÐŸÐ²ÐµÐŽÐµÐœÐœÐ°Ñ ÐŽÐŸ ÑÐŸÐ²ÐµÑÑÐµÐœÑÑÐ²Ð°, ÑÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐÑÐŒÐ°ÐœÐžÑÐ°ÑÐœÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÑÐ°Ð·Ð²ÐžÑÐžÑ (HDL). ÐÐœÐ° ÐžÐ»Ð»ÑÑÑÑÐžÑÑÐµÑ, ÐºÐ°ÐºÐžÐµ Ð±ÐŸÐ»ÑÑÐžÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÑ, ÐµÑÐ»Ðž ÐŽÐŸÑÑÑÐ¿ÐœÑ Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ. ÐÐœÐ° Ð²ÐºÐ»ÑÑÐ°ÐµÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð¿ÑÐž ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ.</Text>
+<Text id="163">Greenstone ÑÐ°ÐºÐ¶Ðµ ÐžÐŽÐµÑ Ñ ÐœÐµÐºÐŸÑÐŸÑÑÐŒÐž Ñ
+ÐŸÑÐŸÑÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž, ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐ°Ñ
+ ÐºÐŸÑÐŸÑÑÑ
+ Â«Ð ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐžÂ» ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑÑÑ, ÐºÐ°Ðº ÐŸÐœÐž Ð¿ÐŸÑÑÑÐŸÐµÐœÑ. ÐÐœÐž ÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÑÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Greenstone. Ð£ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐœÑÐµ ÐŽÐžÐ°Ð»ÐŸÐ³Ðž ÐŸÐ¿ÑÐŸÑÑÑ, Ñ
+ÐŸÑÐžÑÐµ Ð»Ðž ÐÑ Ð²ÐºÐ»ÑÑÐžÑÑ ÐžÑ
+ Ð² ÐžÐœÑÑÐ°Ð»Ð»ÐžÑÑÐµÐŒÑÑ ÐÐ°ÐŒÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Greenstone, ÑÐºÐ°Ð¶ÑÑ Ð¿ÑÐžÐ±Ð»ÐžÐ·ÐžÑÐµÐ»ÑÐœÑÐ¹ ÐŸÐ±ÑÐµÐŒ ÐœÐ° ÐŽÐžÑÐºÐµ, ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÐ¹ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Table class="hidden" id="table_collections">
+<Title/>
+<TableContent>
+<tr>
+<th width="123">
+<Text id="164"><i>demo</i></Text>
+</th>
+<th width="127">
+<Text id="165">ÐÐµÐŒÐŸÐœÑÑÑÐ°-ÑÐžÐŸÐœÐœÑÐ¹ Ð¿ÑÐžÐŒÐµÑ GreenstoneÂ <br/>(7 MÐ±)</Text>
+</th>
+<th width="298">
+<Text id="166">ÐÐµÐ±ÐŸÐ»ÑÑÐ°Ñ ÑÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ HDL. ÐÑÐ»Ðž ÐÑ ÐºÐ»ÐŸÐœÐžÑÑÐµÑÐµ ÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÑÐŸ Ð¿ÐŸÐ»ÐœÑÐ¹ ÐœÐ°Ð±ÐŸÑ ÑÑÐµÐŽÑÑÐ² ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐœÐžÑ Ð¿ÐŸÑÐ²ÐžÑÑÑ ÑÐŸÐ»ÑÐºÐŸ Ð² ÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž ÐÐ°ÑÐž ÐœÐŸÐ²ÑÐµ ÑÐ°Ð¹Ð»Ñ ÑÐŸÐ¿ÑÐŸÐ²ÐŸÐ¶ÐŽÐ°ÑÑÑÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹ ÐŸ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="167"><i>dls-e</i></Text>
+</th>
+<th width="127">
+<Text id="168">Ð¡ÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÑÐ°Ð·Ð²ÐžÑÐžÑÂ <br/>(150 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="169">ÐÐŸÐŽÐŸÐ±ÐœÐŸ ÐŽÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒÑ Ð¿ÑÐžÐŒÐµÑÑ Greenstone, ÑÑÐŸ - ÑÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÂ  HDL, ÐœÐŸ ÐœÐ°ÐŒÐœÐŸÐ³ÐŸ Ð±ÐŸÐ»ÑÑÐµÐ³ÐŸ ÐŸÐ±ÑÐµÐŒÐ°. ÐÐœÐ° ÑÐŸÐŽÐµÑÐ¶ÐžÑ 250 Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐ¹ - ÐºÐœÐžÐ³, ÑÐŸÐŸÐ±ÑÐµÐœÐžÐ¹ Ðž Ð¶ÑÑÐœÐ°Ð»ÐŸÐ² - Ð² ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐŸÐ±Ð»Ð°ÑÑÑÑ
+ ÑÐ°Ð·Ð²ÐžÑÐžÑ ÑÐµÐ»ÐŸÐ²ÐµÑÐµÑÑÐ²Ð° (Ð¿ÐŸÐ»ÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ HDL ÑÐŸÐŽÐµÑÐ¶ÐžÑ 1230 Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐ¹). ÐÐœÐ° ÐžÐŒÐµÐµÑ ÑÑ Ð¶Ðµ ÑÐ°ÐŒÑÑ ÑÑÑÑÐºÑÑÑÑ, ÑÑÐŸ Ðž ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Greenstone. ÐÐœÐ° ÐŽÐŸÐ²ÐŸÐ»ÑÐœÐŸ ÑÐ»ÐŸÐ¶ÐœÐ°. ÐÐŸÑÑÐŸÐŒÑ, ÐµÑÐ»Ðž ÐÑ ÑÐŸÐ»ÑÐºÐŸ ÐœÐ°ÑÐžÐœÐ°ÐµÑÐµ ÑÐ°Ð±ÐŸÑÐ°ÑÑ, ÑÐŸ Ð»ÑÑÑÐµ ÐœÐ°ÑÐ°ÑÑ Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÐŽÑÑÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŽÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐ¹ MSWord, PDF, Ð°ÑÑ
+ÐžÐ²Ð° Greenstone ÐžÐ»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÐŸÑÑÑÑ
+ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐ¹).</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="170"><i>wrdpdf-e</i></Text>
+</th>
+<th width="127">
+<Text id="171">ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÑ MSWord Ðž PDFÂ <br/>(4 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="172">ÐÐœÐ° ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÑÐŸÑÐŒÐ°ÑÐµ PDF, MSWord, RTF, PostScript, ÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÑÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐ°Ñ
+. ÐÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŸÑÐµÐœÑ Ð¿ÑÐŸÑÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="173"><i>gsarch-e</i></Text>
+</th>
+<th width="127">
+<Text id="174">ÐÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð°ÑÑ
+ÐžÐ²ÐŸÐ² GreenstoneÂ <br/>(5 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="175">ÐÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐ¹ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ ÐžÐ· Ð°ÑÑ
+ÐžÐ²Ð° ÑÐ¿ÐžÑÐºÐŸÐ² Ð°ÐŽÑÐµÑÐ°ÑÐŸÐ² Greenstone, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÐ°Ñ Ð¿Ð»Ð°Ð³ÐžÐœ Email, ÐºÐŸÑÐŸÑÑÐ¹ Ð°ÐœÐ°Ð»ÐžÐ·ÐžÑÑÐµÑ ÑÐ°Ð¹Ð»Ñ Ð² ÑÐŸÑÐŒÐ°ÑÐ°Ñ
+ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ. ÐÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŸÑÐµÐœÑ Ð¿ÑÐŸÑÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="176"><i>Ñltbib-e</i></Text>
+</th>
+<th width="127">
+<Text id="177">ÐÐžÐ±Ð»ÐžÐŸÐ³ÑÐ°ÑÐžÑÐµÑÐºÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÂ <br/>(7 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="178">Ð­ÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð¿ÑÐžÐ±Ð»ÐžÐ·ÐžÑÐµÐ»ÑÐœÐŸ 4000 Ð±ÐžÐ±Ð»ÐžÐŸÐ³ÑÐ°ÑÐžÑÐµÑÐºÐžÑ
+ Ð·Ð°Ð¿ÐžÑÐµÐ¹. ÐÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐžÑÐºÐ° ÑÐŸÐ·ÐŽÐ°Ðœ ÐœÐ° ÐŸÑÐœÐŸÐ²Ðµ Ð±Ð»Ð°ÐœÐºÐ°, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ Ð¿ÐŸÐ»ÑÐŒ Ð·Ð°Ð¿ÐžÑÐž. Ð­ÑÐŸ ÐŽÐŸÐ²ÐŸÐ»ÑÐœÐŸ ÑÐ»ÐŸÐ¶ÐœÑÐ¹ ÐºÐŸÐŒÐ¿Ð»ÐµÐºÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="179"><i>cltext-c</i></Text>
+</th>
+<th width="127">
+<Text id="180">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ Ð±ÐžÐ±Ð»ÐžÐŸÐ³ÑÐ°ÑÐžÐž (1 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="181">Ð­ÑÐŸ ÐºÑÐŸÑÐµÑÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ñ Ð±ÐžÐ±Ð»ÐžÐŸÐ³ÑÐ°ÑÐžÑÐµÑÐºÐžÐŒÐž Ð·Ð°Ð¿ÐžÑÑÐŒÐž ÐžÐ»Ð»ÑÑÑÑÐžÑÑÐµÑ ÑÑÐµÐŽÑÑÐ²ÐŸ Â«ÑÑÐ¿ÐµÑÐºÐŸÐ»Ð»ÐµÐºÑÐžÐžÂ», ÐºÐŸÑÐŸÑÐŸÐµ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑ Ð¿ÐŸÐžÑÐº Ð² Ð¿ÐµÑÐµÑÐµÐºÐ°ÑÑÐžÑ
+ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+. ÐÐœÐ° ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ð²ÐŒÐµÑÑÐµ Ñ ÐÐžÐ±Ð»ÐžÐŸÐ³ÑÐ°ÑÐžÑÐµÑÐºÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹. ÐÐµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» Ð¿ÐŸÑÑÐž ÑÐ°ÐºÐŸÐ¹ Ð¶Ðµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="182"><i>MARC-e</i></Text>
+</th>
+<th width="127">
+<Text id="183">ÐÑÐžÐŒÐµÑ MARC (1 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="184">ÐÑÐœÐŸÐ²Ð°ÐœÐœÐ°Ñ ÐœÐ° ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ Ð·Ð°Ð¿ÐžÑÑÑ
+ MARC ÐžÐ· ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÐÐŸÐœÐ³ÑÐµÑÑÐ°, ÑÑÐŸ Ð¿ÑÐŸÑÑÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐœÐµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑÐ°Ñ Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐžÐµ Ð¿ÐŸÐžÑÐºÐ° ÐœÐ° ÐŸÑÐœÐŸÐ²Ðµ Ð·Ð°ÐŽÐ°ÐœÐœÐŸÐ¹ ÑÐŸÑÐŒÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="185"><i>oai-e</i></Text>
+</th>
+<th width="127">
+<Text id="186">ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐž-ÐŸÐœÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ OAI (18 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="187">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŸÑÐºÑÑÑÑÐ¹ Ð°ÑÑ
+ÐžÐ²ÐœÑÐ¹ Ð¿ÑÐŸÑÐŸÐºÐŸÐ» Ðž ÑÑÐµÐŽÑÑÐ²Ð° ÐÐŒÐ¿ÐŸÑÑÐ°, ÐŸÐœÐ° Ð²ÐŸÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐžÐ· Ð°ÑÑ
+ÐžÐ²Ð° Ðž ÑÑÑÐŸÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐ· Ð·Ð°Ð¿ÐžÑÐµÐ¹. Ð ÐŽÐ°ÐœÐœÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐŸÐœÐž ÑÐ²Ð»ÑÑÑÑÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑÐŒÐž, ÑÐ°Ðº ÑÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŸÐ±Ð° Ð¿Ð»Ð°Ð³ÐžÐœÐ° OAI Ðž Image.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="188"><i>image-e</i></Text>
+</th>
+<th width="127">
+<Text id="189">ÐÑÐŸÑÑÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐ¹ (1 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="190">Ð­ÑÐŸ ÐŸÑÐµÐœÑ ÐŸÑÐœÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐ¹ ÐœÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐœÐžÐºÐ°ÐºÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ° Ðž ÐœÐžÐºÐ°ÐºÐžÑ
+ ÑÐ²ÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÑÐŸ ÐŽÐµÐ»Ð°ÐµÑ ÐµÐµ ÐŽÐŸÐ²ÐŸÐ»ÑÐœÐŸ ÐœÐµÑÐµÐ°Ð»ÐžÑÑÐžÑÐœÐŸÐ¹. ÐÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÐŸÑÑÑÐŒ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="191"><i>authen-e</i></Text>
+</th>
+<th width="127">
+<Text id="192">ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÑ ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°-ÐœÐžÑ Ðž Ð°ÑÑÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÐž (8 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="193">ÐÐ° ÑÐŸÐŒ Ð¶Ðµ ÑÐ°ÐŒÐŸÐŒ ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ðµ, ÑÑÐŸ Ðž Ð¿ÐµÑÐ²ÐŸÐœÐ°ÑÐ°Ð»ÑÐœÐ°Ñ ÐŽÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Greenstone, ÐŸÐœÐ° ÐŸÑÐ»ÐžÑÐ°ÐµÑÑÑ ÐŽÐ²ÑÐŒÑ ÐœÐµÐ·Ð°Ð²ÐžÑÐžÐŒÑÐŒÐž ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÑÐŒÐž: ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐœÐµÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ðž ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÐŒÑÐ¹ ÐŽÐŸÑÑÑÐ¿ Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ Ð¿ÐŸÑÐ»Ðµ Ð°ÑÑÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÐž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="194"><i>garish</i></Text>
+</th>
+<th width="127">
+<Text id="195">Ð ÐµÐ·ÐºÐ°Ñ Ð²ÐµÑÑÐžÑ ÐŽÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœ-ÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (8 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="196">Ð­ÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐ°ÐºÐ¶Ðµ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÐŸÑ Ð¶Ðµ ÑÐ°ÐŒÑÐ¹ ÐŒÐ°ÑÐµÑÐžÐ°Ð», ÑÑÐŸ Ðž ÐŽÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ Ð¿ÑÐžÐŒÐµÑ Greenstone. ÐÐµ Ð²ÐžÐŽ Ð±ÑÐ» ÐžÐ·ÐŒÐµÐœÐµÐœ, ÑÑÐŸÐ±Ñ Ð¿ÐŸÐºÐ°Ð·Ð°ÑÑ, ÐºÐ°Ðº Ð³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÑÑÑÐ°ÐœÐžÑÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐžÐ·Ð»ÐŸÐ¶ÐµÐœÑ Ð¿ÐŸ-ÐŽÑÑÐ³ÐŸÐŒÑ. ÐÐœÐ° ÑÐµÐ°Ð»ÐžÐ·ÐŸÐ²Ð°ÐœÐ° Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐ³ÐŸ ÐŒÐ°ÐºÑÐŸ-ÑÐ°Ð¹Ð»Ð°, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐµÑÑÑ Ð²ÐŒÐµÑÑÐµ Ñ Greenstone.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="197"><i>isis-e</i></Text>
+</th>
+<th width="127">
+<Text id="198">ÐÑÐžÐŒÐµÑ CDS/ISIS (1 ÐÐ±)</Text>
+</th>
+<th width="298">
+<Text id="199">Ð­ÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐŸÐ·ÐŽÐ°ÐœÐ° ÐžÐ· Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ CDS/ISIS, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐµÐ¹ ÐŸÐºÐŸÐ»ÐŸ 150 Ð±ÐžÐ±Ð»ÐžÐŸÐ³ÑÐ°ÑÐžÑÐµÑÐºÐžÑ
+ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ². ÐÐ»Ñ ÑÑÐµÐœÐžÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ
+ ÐŽÐ»Ñ ISIS ÑÐ°Ð¹Ð»ÐŸÐ² .mst Ðž .ftd Ðž Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ ÐžÑ
+ Ð² ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÐµ Greenstone ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð¿Ð»Ð°Ð³ÐžÐœ ISISPlug.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<Chapter id="setting_up_webserver">
+<Title>
+<Text id="200">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐ° ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°</Text>
+</Title>
+<Content>
+<Text id="201">Ð ÑÑÐŸÐ¹ ÑÐ°ÑÑÐž ÐŸÐ¿ÐžÑÐ°Ðœ Ð¿ÑÐŸÑÐµÑÑ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ° ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ñ Greenstone. ÐÑÐµ ÑÐŸ, ÑÑÐŸ Ð±ÑÐŽÐµÑ ÐŸÐ¿ÐžÑÐ°ÐœÐŸ ÐœÐžÐ¶Ðµ, ÐžÐŒÐµÐµÑ ÐŸÑÐœÐŸÑÐµÐœÐžÐµ ÑÐŸÐ»ÑÐºÐŸ Ðº ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐµ, Ðž Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÐ¿ÑÑÑÐžÑÑ ÑÑÑ ÑÐ°ÑÑÑ, ÐµÑÐ»Ðž Ñ Ð²Ð°Ñ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° Ð»ÐŸÐºÐ°Ð»ÑÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°.</Text>
+<Text id="202">ÐÑ Ð±ÑÐŽÐµÐŒ ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Apache, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÐºÐ°Ðº Ð² Windows, ÑÐ°Ðº Ðž Ð² Unix (ÑÐŒÐŸÑÑÐžÑÐµ ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ <CrossRef target="Chapter" ref="appendix_associated_software"/> ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ Ð±ÐŸÐ»ÑÑÐµÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž),Microsoft's Personal Web Server (Ð \Ð/8)(Ð¡ÐµÑÐµÐ²Ð ÑÐµÑÐ²ÐµÑ Microsoft) Ðž ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Internet Information Services (US). PWS ÑÐ²Ð»ÑÐµÑÑÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐŒ ÑÐµÑÐµÐ²ÑÐŒ Ð¿ÑÐŸÐŽÑÐºÑÐŸÐŒ Microsoft Ð¿ÐŸÐŽ Windows 95/98; US ÑÐŸÐ·ÐŽÐ°Ðœ Ð¿ÐŸÐŽ Windows 2000 Ðž Windows XP; Windows NT ÑÐ°ÐºÐ¶Ðµ ÐŒÐŸÐ¶ÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÑÐŸÑ ÑÐµÑÐ²ÐµÑ. Apache ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÐºÐ°Ðº Ñ Ð²ÐµÑÑÐžÐµÐ¹ ÑÐµÑÐµÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÐŽÐ»Ñ Windows, ÑÐ°Ðº Ðž ÐŽÐ»Ñ Unix (ÐœÐŸ ÐŒÑ Ð±ÑÐŽÐµÐŒ ÑÐ¿ÐŸÑÑÐµÐ±Ð»ÑÑÑ ÑÐµÑÐŒÐžÐœÐŸÐ»ÐŸÐ³ÐžÑ Windows); ÑÐ°ÑÑÑ, ÐºÐ°ÑÐ°ÑÑÐ°ÑÑÑ PWI/IIS, Ð¿ÑÐžÐ²ÐµÐŽÐµÐœÐ° ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Windows.</Text>
+<Text id="203">ÐÐŸÑÐ»Ðµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ° ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÑÐ°ÐŒ Greenstone. ÐÑÐ»Ðž Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ð±ÑÐŽÐµÑÐµ ÐœÐ°Ð¶ÐžÐŒÐ°ÑÑ ÐºÐœÐŸÐ¿ÐºÐž, Ð²ÑÐ±ÑÐ°ÐœÐœÑÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, ÑÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð±ÑÐŽÐµÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ C:\Program Files\gsdl Ð²ÐŒÐµÑÑÐµ ÑÐŸ Ð²ÑÐµÐŒÐž ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÐŒÐž ÑÐ°Ð¹Ð»Ð°ÐŒÐž.</Text>
+<Text id="204">ÐÑÐµ ÑÐµÑÐµÐ²ÑÐµ ÑÐµÑÐ²ÐµÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÐ¹ URL Ð°ÐŽÑÐµÑ "localhost" ÐŽÐ»Ñ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐžÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°, ÐœÐ° ÐºÐŸÑÐŸÑÐŸÐŒ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, Ð¿ÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº Ð²Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÐµ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº Ð²Ð°ÑÐžÐŒ HTML-ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ, Ð²Ð²ÐµÐŽÑ URL http://localhost Ð² ÐŸÐºÐœÐµ Ð±ÑÐ°ÑÐ·ÐµÑÐ°. ÐÑÐ»Ðž ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐŽÐŸÐŒÐµÐœÐ°, ÑÐŸ ÐŸÐœ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð²ÐŒÐµÑÑÐŸ localhost ÐŽÐ»Ñ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐžÑ Ð²Ð°ÑÐµÐ³ÐŸ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ° Ð² ÑÐµÑÐž. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, ÐŽÐ»Ñ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ° ÑÐµÑÐ²ÐµÑÐ° New Zealand Digital Library Ð°ÐŽÑÐµÑÐ° http://nzdl.org ÐžÂ  http://locahost ÐŸÐŽÐžÐœÐ°ÐºÐŸÐ²Ñ. ÐÑÐ»Ðž Ð²Ñ Ð²Ð²ÐµÐŽÐµÑÐµÂ Â  http://nzdl.org Ð² Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ, Ð²Ñ ÑÐŸÐµÐŽÐžÐœÐžÑÐµÑÑ Ñ ÑÐµÑÐ²ÐµÑÐŸÐŒ New Zealand Digital Library, Ð² ÑÐŸ Ð²ÑÐµÐŒÑ ÐºÐ°Ðº ÐµÑÐ»Ðž Ð²Ñ Ð²Ð²ÐµÐŽÐµÑÐµ http://localhost, Ð²Ñ Ð²ÑÐ¹ÐŽÐµÑÐµ ÐœÐ° Ð²Ð°Ñ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ.</Text>
+<Section id="apache_web_server">
+<Title>
+<Text id="205">Ð¡ÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Apache</Text>
+</Title>
+<Content>
+<Text id="206">ÐÐ±ÑÑÐœÐŸ ÑÑÐŸÑ ÑÐµÑÐ²ÐµÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ Ð² C:\Program Files\Apache Group\Apache Ðž ÐœÐ°ÑÑÑÐŸÐµÐœ ÑÐ°Ðº, ÑÑÐŸÐ±Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ cgi-bin ÐœÐ°Ñ
+ÐŸÐŽÐžÐ»Ð°ÑÑ Ð² Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÐž \cgi-bin Ðž ÐºÐŸÑÐœÐµÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° (document root) ÑÐ²Ð»ÑÐ»Ð°ÑÑ Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÑ \htdocs. ÐÐ°ÑÑÑÐŸÐ¹ÐºÐž ÐŒÐŸÐ¶ÐœÐŸ ÐžÐ·ÐŒÐµÐœÐžÑÑ Ð¿ÑÑÐµÐŒÂ  ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð° C:\Program Files\Apache Group\conf\httpd.conf. ÐÐœ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐµÐºÑÑÐŸÐ²ÑÐŒ ÑÐ°Ð¹Ð»ÐŸÐŒ Ðž Ð»ÐµÐ³ÐºÐŸ ÑÐžÑÐ°ÐµÐŒ.</Text>
+<Text id="207">Ð Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµÂ  ÐœÐ°ÑÑÑÐŸÐµÐœÐŸ ÑÐµÑÐµÐ²ÐŸÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ, Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÑÑÑÐŸÐºÑ Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» Apache, httpd.conf:</Text>
+<CodeLine>ServerName localhost</CodeLine>
+<Text id="208">ÐÑÐ»Ðž ÑÑÐ° ÑÑÑÐŸÐºÐ° ÐœÐµ Ð²ÐºÐ»ÑÑÐµÐœÐ°, ÑÐŸ ÑÐžÑÑÐµÐŒÐ° Ð¿ÐŸÐ¿ÑÑÐ°ÐµÑÑÑ ÐœÐ°Ð¹ÑÐž ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ Ð²Ð°ÑÐµÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°. Ð¢ÐµÐŒ ÐœÐµ ÐŒÐµÐœÐµÐµ, Ð² ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ Ð²ÐµÑÑÐžÑÑ
+ Windows ÑÑÑÐµÑÑÐ²ÑÑÑ ÐŸÑÐžÐ±ÐºÐž, ÐºÐŸÑÐŸÑÑÐµ ÐœÐµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ ÑÐžÑÑÐµÐŒÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÐµÐ³ÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ. Ð ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ Ð¿ÐŸÑÐ»Ðµ Ð·Ð°Ð¿ÑÑÐºÐ° Apache ÐœÐµÐŒÐµÐŽÐ»ÐµÐœÐœÐŸ Ð·Ð°ÐºÑÐŸÐµÑÑÑ. ÐÐŸÑÐ²Ð»ÑÐµÑÑÑ ÐŸÐºÐœÐŸ Ñ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐµÐŒ ÐŸÐ± ÐŸÑÐžÐ±ÐºÐµ, ÐœÐŸ ÐŸÐœÐŸ ÐŒÐŸÐŒÐµÐœÑÐ°Ð»ÑÐœÐŸ ÐžÑÑÐµÐ·Ð°ÐµÑ, Ðž Ð²Ñ ÑÐºÐŸÑÐµÐµ Ð²ÑÐµÐ³ÐŸ ÐµÐ³ÐŸ ÐœÐµ ÑÐ²ÐžÐŽÐžÑÐµ Ð²ÐŸÐŸÐ±ÑÐµ.</Text>
+<Subsection id="setting_up_cgi-bin_directory">
+<Title>
+<Text id="209">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐ° Greenstone ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž cgi-bin</Text>
+</Title>
+<Content>
+<Text id="210">Ð¡ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Cgi-bin ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒÐž, ÐºÐ°Ðº Ñ Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÐŒÑÐŒÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°ÐŒÐž (executable programs). ÐÐžÑÐµÐºÑÐžÐ²Ð° ScriptAlias ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž cgi-bin. ÐÐ°ÐŒÐµÑÑÑÐµ, ÑÑÐŸ ÑÑÐ° ÐŽÐžÑÐµÐºÑÐžÐ²Ð° ÑÐ¿ÐŸÑÐŸÐ±ÐœÐ° Ð¿ÑÐµÐ²ÑÐ°ÑÐžÑÑ Ð»ÑÐ±ÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ Ð² cgi-ÐžÑÐ¿ÐŸÐ»ÐœÐžÐŒÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ -ÐœÐµ ÐŸÐ±ÑÐ·Ð°ÑÐµÐ»ÑÐœÐŸ, ÑÑÐŸÐ±Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐœÐ°Ð·ÑÐ²Ð°Ð»Ð°ÑÑ cgi-bin! Ð ÐœÐ°ÐŸÐ±ÐŸÑÐŸÑ, ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ cgi-bin ÐœÐµ ÑÐ²Ð»ÑÐµÑÑÑ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÐ¹ ÐŽÐŸ ÑÐŸÐ³ÐŸ ÐŒÐŸÐŒÐµÐœÑÐ°, ÐºÐ°Ðº Ðº ÐœÐµÐ¹ ÐœÐµ Ð¿ÑÐžÐŒÐµÐœÐžÑÑ ScriptAlias.</Text>
+<Text id="211">ÐÐŸÑÐ»Ðµ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Apache ÐžÐŒÐµÐµÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑÂ <i>cgi-bin</i>Â Ð²Â <i>C:\Program Files\Apache</i>
+<i>Group\Apache\cgi-bin</i>. Ð­ÑÐŸ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ ÐµÑÐ»Ðž Ð²Ð²ÐµÑÑÐž Ð°ÐŽÑÐµÑ URLÂ <i>http://localhost/cgi-bin/hello</i>, ÑÐŸ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Ð¿ÐŸÐ¿ÑÐŸÐ±ÑÐµÑ Ð·Ð°Ð¿ÑÑÑÐžÑÑ ÑÐ°Ð¹Ð», ÐœÐ°Ð·ÑÐ²Ð°ÑÑÐžÐ¹ÑÑ hello, ÐžÐ· ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž.</Text>
+<Text id="212">ÐÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone, ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÐ°Ñ libmry.exe,Â  ÐºÐŸÑÐŸÑÑÑ ÐœÑÐ¶ÐœÐŸ Ð·Ð°Ð¿ÑÑÑÐžÑÑ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°; Ð² ÑÐ²ÐŸÑ ÐŸÑÐµÑÐµÐŽÑ ÐŸÐœÐ°Â Â  ÑÑÐžÑÑÐ²Ð°ÐµÑ ÑÐ°Ð¹Ð», ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÑÐ¹ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÑ Greenstone, ÐžÐ»Ðž "Â <i>gsdlsite.cfg</i>Â ", ÐºÐŸÑÐŸÑÑÐ¹ ÐŽÐŸÐ»Ð¶ÐµÐœ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÑÐŸÐ¹ Ð¶Ðµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž.</Text>
+<Text id="213">ÐÑÑÑÐžÐ¹ ÑÐ¿ÐŸÑÐŸÐ±, ÑÑÐŸÐ±Ñ Ð²ÑÐ¿ÐŸÐ»ÐœÐžÑÑ ÑÑÐŸ, ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÐžÑÐµÐºÑÐžÐ²Ñ ScriptAlias ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐžÂ Â  cgi-bin. ÐÐŸÑ ÑÐ°ÑÑÑ ÐžÐ· ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð° Apache httpd.conf, ÐºÐŸÑÐŸÑÐ°Ñ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑÂ <i>C:\Program Files\gsdl\cgi-bin</i>Â Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸÐ¹Â <i>cgi-bin</i>Â ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž:</Text>
+<CodeLine>ScriptAlias /gsdl/cgi-bin/ "C:/Program Files/gsdl/cgi-bin/"</CodeLine>
+<CodeLine>Â  &lt;Directory C:/Program Files/gsdl/cgi-bin&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â Â  Options None</CodeLine>
+<CodeLine>Â Â Â Â Â Â  AllowOverride None</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="214">(ÐÐœÑÐµÑÐµÑÐœÑÐ¹ ÑÐ°ÐºÑ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» Apache ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ / Ð²ÐŒÐµÑÑÐŸ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ
+ ÐŽÐ»Ñ Windows \).</Text>
+<Text id="215">Ð­ÑÐŸ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ Ð»ÑÐ±ÐŸÐ¹ URLÐ°ÐŽÑÐµÑ Ð²ÑÐŸÐŽÐµ http://localhost/gsdl/cgi-bin...Ð±ÑÐŽÐµÑ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž C:\Program Files\gsdl\cgi-bin Ðž Ð·Ð°Ð¿ÑÑÐµÐœ ÑÐµÑÐµÐ²ÑÐŒ ÑÐµÑÐ²ÐµÑÐŸÐŒ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð¿ÑÐž Ð²ÑÑÑÐµÑÐµ Ñ URL http://localhost/gsdl/cgi-bin/hello ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Ð¿ÐŸÐ¿ÑÑÐ°ÐµÑÑÑ ÐžÐ·Ð²Ð»ÐµÑÑ ÑÐ°Ð¹Ð» C:\Program Files\gsdl\cgi-bin\hello Ðž Ð·Ð°Ð¿ÑÑÑÐžÑÑ ÐµÐ³ÐŸ. Ð¢ÐµÐŒ ÐœÐµ ÐŒÐµÐœÐµÐµ, URLÂ  http://localhost/cgi-bin/helloÂ  Ð±ÑÐŽÐµÑ ÐžÑÐºÐ°ÑÑ Ð² ÐŸÐ±ÑÑÐœÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž cgi-bin ApacheÂ  ÑÐ°Ð¹Ð»Â Â  C:\Program Files\Apache Group\Apache\cgi-bin\hello Ðž Ð¿ÑÑÐ°ÑÑÑÑ Ð·Ð°Ð¿ÑÑÑÐžÑÑ ÐµÐ³ÐŸ, ÑÐ°Ðº Ð¶Ðµ, ÐºÐ°Ðº Ðž Ð¿ÑÐµÐ¶ÐŽÐµ.</Text>
+</Content>
+</Subsection>
+<Subsection id="document_root_directory">
+<Title>
+<Text id="216">ÐÐŸÑÐœÐµÐ²Ð°Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°</Text>
+</Title>
+<Content>
+<Text id="217">ÐÐŸÑÐœÐµÐ²Ð°Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÑÐ²Ð»ÑÐµÑÑÑ ÐºÐŸÑÐœÐµÐŒ ÑÑÑÑÐºÑÑÑÑ Ð²Ð°ÑÐµÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž. ÐÐŸÑÐ»Ðµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Apache ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐºÐŸÑÐœÐµÐ²ÐŸÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð² C:\Program Files\Apache Group\Apache\htdocs. Ð­ÑÐŸ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ ÐµÑÐ»Ðž Ð² ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Ð²Ð²ÐµÑÑÐž URL http://localhost/hello.html, ÑÐŸ ÐŸÐœ Ð¿ÐŸÐ¿ÑÑÐ°ÐµÑÑÑ ÐžÐ·Ð²Ð»ÐµÑÑ ÑÐ°Ð¹Ð», ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÑÐ¹ hello.html, ÐžÐ· ÑÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž.</Text>
+<Text id="218">ÐÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ°Ð¹Ð»ÐŸÐ² Ð² Greenstone ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÑÑÐžÑÑÐ²Ð°ÐµÐŒÑ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°. Ð¡Ð°ÐŒÑÐ¹ Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐ¿ÐŸÑÐŸÐ± Ð²ÑÐ¿ÐŸÐ»ÐœÐžÑÑ ÑÑÑ Ð·Ð°ÐŽÐ°ÑÑ ÑÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÐžÑÐµÐºÑÐžÐ²Ñ Alias, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐŸÑÑÐž ÑÐ°ÐºÐ°Ñ Ð¶Ðµ, ÐºÐ°ÐºÂ Â  ScriptAlias, Ð·Ð° ÐžÑÐºÐ»ÑÑÐµÐœÐžÐµÐŒ ÑÐŸÐ³ÐŸ, ÑÑÐŸ ÐŸÐœÐ° ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ñ Ð¿ÑÐŸÑÑÑÐŒÐž WWW-ÑÑÑÐ°ÐœÐžÑÐ°ÐŒÐž, Ð° ÐœÐµ ÑÐŸ ÑÐºÑÐžÐ¿ÑÐ°ÐŒÐž cgi. ÐÐ²ÐµÐŽÐžÑÐµ ÑÑÐž ÑÑÑÐŸÐºÐž Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» Apache Ð¿ÐŸÑÐ»Ðµ ÐŽÐžÑÐµÐºÑÐžÐ²Ñ ScriptAlias, ÑÑÐŸ ÑÐŽÐµÐ»Ð°ÐµÑ C:\Program Files\gsdl ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÐŒ ÐŒÐµÑÑÐŸÐŒ Ð¿ÐŸÐžÑÐºÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+<CodeLine>Alias /gsdl/ "C:/Program Files/gsdl/"</CodeLine>
+<CodeLine>Â  &lt;Directory C:/Program Files/gsdl&gt;</CodeLine>
+<CodeLine>Â Â Â Â Â  Options Indexes MultiViews FollowSymLinks</CodeLine>
+<CodeLine>Â Â Â  Â Â Â AllowOverride None</CodeLine>
+<CodeLine>Â  Â Order allow,deny</CodeLine>
+<CodeLine>Â  Allow from all</CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="219">Ð­ÑÐŸ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ Ð»ÑÐ±ÑÐµ URL, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐ²Ð¿Ð°ÐŽÐ°ÑÑ Ñ Ð¿ÐµÑÐ²ÑÐŒ Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐŒ Alias (gsdl), Ð±ÑÐŽÑÑ ÑÐ°Ð·ÑÑÐºÐžÐ²Ð°ÑÑÑÑ Ð² ÑÐŸÐ»Ðž ÑÐ°Ð¹Ð»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑ Ð²ÑÐŸÑÐŸÐŒÑ Ð°ÑÐ³ÑÐŒÐµÐœÑÑ.Â  ÐÑÑÐ³ÐžÐŒÐž ÑÐ»ÐŸÐ²Ð°ÐŒÐž, URL Ð²ÐžÐŽÐŸÐ² http://localhost/gsdl...Ð±ÑÐŽÑÑ ÑÐ°Ð·ÑÑÐºÐžÐ²Ð°ÑÑÑÑ, ÐºÐ°Ðº ÑÐ°Ð¹Ð»Ñ ÐžÐ· ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž C:\Program Files\gsdl. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð¿ÑÐž Ð²ÑÑÑÐµÑÐµ Ñ URL http://localhost/gsdl/hello.html, ÑÐµÑÐ²ÐµÑ Ð¿ÐŸÐ¿ÑÑÐ°ÐµÑÑÑ ÐžÐ·Ð²Ð»ÐµÑÑ ÑÐ°Ð¹Ð» C:\Program Files\gsdl\hello.html. Ð¢ÐµÐŒ ÐœÐµ ÐŒÐµÐœÐµÐµ,Â  URL http://localhost/ hello.htmlÂ Â  ÐžÑÐµÑ ÑÐ°Ð¹Ð» Ð² Ð¿ÑÐŸÑÑÐŸÐ¹ htdocs ÐŽÐžÑÐµÐºÑÐŸÑÐžÐžC:\Program Files\Apache Group\Apache\htdocs\hello.html ÑÐ°ÐºÐ¶Ðµ, ÐºÐ°Ðº Ðž Ð¿ÑÐµÐ¶ÐŽÐµ.</Text>
+<Text id="220">ÐÐµ Ð·Ð°Ð±ÑÐŽÑÑÐµ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐŽÐžÑÐµÐºÑÐžÐ²Ñ Alias Ð¿ÐŸÑÐ»Ðµ ÐŽÐžÑÐµÐºÑÐžÐ²Ñ ScriptAlias.Â  ÐÑÐž ÑÐºÐ°Ð·Ð°ÐœÐžÐž Apache ÐŽÐ»Ñ alias /gsdl ÐŽÐŸ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº /gsdl/cgi-bin ÑÐŸÐ²Ð¿Ð°ÐŽÐµÑ Ñ URL / gsdl/cgi-bin/library, ÐŽÐŸ ÐŽÐžÑÐµÐºÑÐžÐ²Ñ Alias ÐœÐµÐ¶ÐµÐ»Ðž ScriptAlias, ÐŸÐœ Ð±ÑÐŽÐµÑ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ðœ, ÐºÐ°Ðº Ð·Ð°Ð¿ÑÐŸÑ Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÑÐµÐŒ ÐŽÐ»Ñ Ð·Ð°Ð¿ÑÑÐºÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ. Ð ÐžÑÐŸÐ³Ðµ Ð±ÐžÐœÐ°ÑÐœÑÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐŽÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ "Ð²ÑÐ²ÐµÐŽÐµÐœ, Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ" Ð² ÐŸÐºÐœÐµ ÐÐœÑÐµÑÐœÐµÑ-Ð±ÑÐ°ÑÐ·ÐµÑÐ° Ð²ÐŒÐµÑÑÐŸ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐµÐ³ÐŸ Ð·Ð°Ð¿ÑÑÑÐžÑÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="security">
+<Title>
+<Text id="221">ÐÐµÐ·ÐŸÐ¿Ð°ÑÐœÐŸÑÑÑ</Text>
+</Title>
+<Content>
+<Text id="222">ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ Ð·ÐœÐ°ÑÑ, ÑÑÐŸ ÐµÑÐ»ÐžÂ  ÐÐœÑÐµÑÐœÐµÑ-Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Ð±ÑÐŽÐµÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÑÐ°Ðº, ÐºÐ°Ðº ÐŸÐ¿ÐžÑÐ°ÐœÐŸ Ð²ÑÑÐµ, ÑÐŸ ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐŒÐŸÐ¶ÐµÑ Ð·Ð°Ð³ÑÑÐ¶Ð°ÑÑ Ð»ÑÐ±ÐŸÐ¹ ÑÐ°Ð¹Ð» ÐžÐ· ÑÑÑÑÐºÑÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž gsdl. Ð­ÑÐŸ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐžÐœÐŽÐµÐºÑÐœÑÐµ ÑÐ°Ð¹Ð»Ñ, ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð»ÑÐ±ÐŸÐ¹ Ð³ÐŸÑÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐ°Ñ Ð±Ð°Ð·Ð° ÐŽÐ°ÐœÐœÑÑ
+, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÑÐ°Ð¹Ð»Ñ (logs) Ðž Ñ.ÐŽ.</Text>
+<Text id="223">ÐÑÐ»Ðž ÐŽÐ°ÐœÐœÐ°Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ Ð²Ð°Ð¶ÐœÐ°, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð° ÑÐµÑÐ²ÐµÑÐ° ÐŽÐ»Ñ ÑÐ¶ÐµÑÑÐŸÑÐµÐœÐžÑ Ð±ÐµÐ·ÐŸÐ¿Ð°ÑÐœÐŸÑÑÐž. Ð ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ ÑÐµÑÐµÐ²ÐŸÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ° Apache Ð²Ð²ÐµÐŽÐžÑÐµ ÑÐ»ÐµÐŽÑÑÑÐžÐµ ÑÑÑÐŸÐºÐž Ð²ÐŒÐµÑÑÐŸ Ð²ÑÑÐµÐ¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÑÑ
+</Text>
+<CodeLine>Alias /gsdl/ "C:/Program Files/gsdl/"</CodeLine>
+<CodeLine>Â  &lt;Directory "C:/Program Files/gsdl"&gt;</CodeLine>
+<CodeLine>Â Â Â  Order allow,deny</CodeLine>
+<CodeLine>Â Â Â  Deny from all</CodeLine>
+<CodeLine>Â Â Â  &lt;FilesMatch</CodeLine>
+<CodeLine>"\.(gif|jpe?g|png|css|mov|mpeg|ps|pdf|doc|rtf|jar|class)$"&gt;</CodeLine>
+<CodeLine>Â Â  Order allow,deny</CodeLine>
+<CodeLine>Â Â  Allow from all</CodeLine>
+<CodeLine>Â  &lt;/FilesMatch&gt; </CodeLine>
+<CodeLine>&lt;/Directory&gt;</CodeLine>
+<Text id="224">Ð­ÑÐŸ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ ÑÐŸÐ»ÑÐºÐŸ ÑÐµ ÑÐ°Ð¹Ð»Ñ, ÑÑÐµ ÑÐ°Ð·ÑÐµÑÐµÐœÐžÐµ ÑÐŸÐ²Ð¿Ð°ÐŽÐ°ÐµÑ Ñ regular expression Ð² ÑÑÑÐŸÐºÐµ FilesMatch, ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð·Ð°Ð³ÑÑÐ¶ÐµÐœÑ.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="pws_and_iis_webservers">
+<Title>
+<Text id="225">Ð¡ÐµÑÐµÐ²ÑÐµ ÑÐµÑÐ²ÐµÑÑ PWS, MS</Text>
+</Title>
+<Content>
+<Text id="226">Ð¥ÐŸÑÑ ÐœÐž PWS ÐœÐž MS Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐœÐµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ Ð² ÑÐžÑÑÐµÐŒÐ°Ñ
+ Windows, ÐžÑ
+ ÐŒÐŸÐ¶ÐœÐŸ Ð»ÐµÐ³ÐºÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ, Ð¿ÐŸÐ»ÑÐ·ÑÑÑÑ ÐŒÐµÐœÑ Ð¿Ð°ÐœÐµÐ»Ðž ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ "Ð£ÐŽÐ°Ð»ÐžÑÑ/ ÐÐŸÐ±Ð°Ð²ÐžÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ". ÐÑÐ»Ðž ÐžÑ
+ ÐœÐµÑ ÐœÐ° ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐºÐµ, ÑÐŸ ÐžÑ
+ ÐŒÐŸÐ¶ÐœÐŸ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ Ñ ÑÐ°Ð¹ÑÐ° Microsoft (www.mircosoft.com) ÐÑÐŸÑÐµÑÑ ÐžÐœÑÑÐ°Ð»ÑÑÐžÐž ÐŽÐ»Ñ ÐŸÐ±ÐµÐžÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ ÐŸÐŽÐžÐœÐ°ÐºÐŸÐ².</Text>
+<Text id="227">ÐÐ°Ð¿ÑÑÑÐžÑÐµ Personal Web Manager Ðž ÑÐŸÐ²ÐµÑÑÐžÑÐµ ÑÐ»ÐµÐŽÑÑÑÐžÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="228">ÐÑÐ±ÐµÑÐžÑÐµ Advanced (ÑÐ°ÑÑÐžÑÐµÐœÐœÑÐ¹) ÐŽÐ»Ñ Ð²ÑÐ²ÐŸÐŽÐ° ÐŸÐºÐœÐ° Advanced Options (Ð Ð°ÑÑÐžÑÐµÐœÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž).</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="229">ÐÑÐ±ÐµÑÐžÑÐµ ÐÐŸÑÐµ(ÐÐ°ÑÐ°Ð»ÐŸ) Ðž ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐÑÐ(ÐÐŸÐ±Ð°Ð²ÐžÑÑ). ÐÐ°Ð¿ÐŸÐ»ÐœÐžÑÐµ Ð¿ÐŸÐ»Ñ ÑÐ»ÐµÐŽÑÑÑÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ:</Text>
+<Text id="230">Ð Ð¿ÐŸÐ»Ðµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ: C:\Program Files\gsdl</Text>
+<Text id="231">Ð Ð¿ÐŸÐ»Ðµ Alias :Â <i>gsdl</i>
+</Text>
+<Text id="232">Ð Ð¿ÐŸÐ»Ðµ Access permissions (ÑÐ°Ð·ÑÐµÑÐµÐœÐœÑÐ¹ ÐŽÐŸÑÑÑÐ¿): Read (ÑÑÐµÐœÐžÐµ)</Text>
+<Text id="233">Ð Ð¿ÐŸÐ»Ðµ Application permissions: None</Text>
+<Text id="234">ÐÐ°Ð¶ÐŒÐžÑÐµ OK</Text>
+<Text id="235">Ð¡ ÑÑÐžÐŒÐž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐ°ÐŒÐž ÑÐ°Ð¹Ð»Ñ Greenstone Ð±ÑÐŽÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑ ÐŽÐ»Ñ ÑÐµÑÐ²ÐµÑÐ°.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="236">ÐÐµÑÐœÐžÑÐµÑÑ Ð² Advanced Options, Ð²ÑÐ±ÐµÑÐžÑÐµ^/ Ðž ÐºÐ»ÐžÐºÐœÐžÑÐµ Add ÐÐ°Ð¿ÐŸÐ»ÐœÐžÑÐµ ÑÐ»ÐµÐŽÑÑÑÐžÐµ Ð¿ÐŸÐ»Ñ:</Text>
+<Text id="237">Directory field:.C:\Program Files\gsdl\cgi-bin</Text>
+<Text id="238">Alias field: cgi-bin</Text>
+<Text id="239">Access permissions:Â <i>None</i></Text>
+<Text id="240">Application permissions:Â <i>Execute</i></Text>
+<Text id="241">ÐÐ°Ð¶ÐŒÐžÑÐµ OK</Text>
+<Text id="242">ÐÐŸÑÐ»Ðµ ÑÑÐŸÐ³ÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone library.exe to be executed by the Webserver.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="243">ÐÐ²ÐµÐŽÐžÑÐµ Ð°ÐŽÑÐµÑ URLÂ <i>http://localhost/gsdl/cgi-bin/library.exe</i></Text>
+<Text id="244">ÐÑÐžÐŒÐµÑÐ°ÐœÐžÐµ: Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ ÐŽÐŸÐ¿ÐžÑÑÐ²Ð°ÑÑ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµ .ÐµÑ
+Ðµ Ð¿ÑÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž PWS, MS.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="configuring_your_site">
+<Title>
+<Text id="245">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐ° ÑÐ°Ð¹ÑÐ°</Text>
+</Title>
+<Content>
+<Text id="246">ÐÐ»Ñ Ð¿ÐŸÐ»ÐœÐŸÑÐµÐœÐœÐŸÐ³ÐŸ ÑÑÐœÐºÑÐžÐŸÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Greenstone ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐœÐ°ÑÑÑÐŸÐžÑÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÐŽÐŸÑÑÑÐ¿Ð° ÐŽÐ»Ñ ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ². ÐÐŽÐŸÐ±Ð°Ð²ÐŸÐº ÑÑÑÐµÑÑÐ²ÑÐµÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð», ÑÐ²ÑÐ·Ð°ÐœÐœÑÐ¹ Ñ ÐºÐ°Ð¶ÐŽÑÐŒ ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐµÐŒ Greenstone. Ð Ð¿ÑÐŸÑÐµÑÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÑÐŸÐ·ÐŽÐ°ÐµÑÑÑ Ð±Ð°Ð·ÐŸÐ²ÑÐ¹ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð», ÐŸÑÐœÐŸÐ²ÑÐ²Ð°ÑÑÐžÐ¹ÑÑ ÐœÐ° Ð²Ð°ÑÐžÑ
+ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐ°Ñ
+ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÑÑÐŸÐ¹ Ð¿ÑÐŸÑÐµÐŽÑÑÑ; ÑÐµÐŒ ÐœÐµ ÐŒÐµÐœÐµÐµ, ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÑÑÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð° ÐŒÐŸÐ¶ÐœÐŸ ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐŽÐ»Ñ ÐŸÐ¿ÑÐžÐŒÐžÐ·Ð°ÑÐžÐž</Text>
+<Section id="file_permissions">
+<Title>
+<Text id="247">Ð€Ð°Ð¹Ð»Ñ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="248">ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ðž Windows 95/98 ÐŒÐŸÐ³ÑÑ Ð¿ÑÐŸÐ¿ÑÑÑÐžÑÑ ÑÑÑ ÑÐ°ÑÑÑ, ÑÐ°Ðº ÐºÐ°Ðº ÑÑÐž Ð²ÐµÑÑÐžÐž ÐœÐµ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°ÑÑ Ð²Ð»Ð°ÐŽÐµÐ»ÑÑÐµÐ² ÑÐ°Ð¹Ð»ÐŸÐ².</Text>
+<Text id="249">Ð Windows NT, 2000, Unix cgi ÑÐºÑÐžÐ¿ÑÑ ÐœÐµ ÐŒÐŸÐ³ÑÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐœÐŸÑÐŒÐ°Ð»ÑÐœÑÑ
+ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹, ÑÐ°Ðº ÐºÐ°Ðº Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ ÐœÐµÐ»ÑÐ·Ñ ÐžÐŽÐµÐœÑÐžÑÐžÑÐžÑÐŸÐ²Ð°ÑÑ ÑÐµÑÐµÐ· WWW.Â  ÐÐŒÐµÑÑÐŸ ÑÑÐŸÐ³ÐŸ cgi scriptÂ Â  ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÐºÐ°Ðº Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ, ÐºÐŸÑÐŸÑÑÐ¹ Ð·Ð°Ð¿ÑÑÑÐžÐ» ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ ( Ð² Windows), ÐžÐ»Ðž ÐºÐ°Ðº ÑÐ°ÑÑÐœÑÐ¹ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ (Ð² Unix ÑÐ°ÑÑÐŸ ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÑÐ¹Â Â Â  nobodyÂ Â  (ÐœÐžÐºÑÐŸ)). Ð ÑÐ²ÑÐ·Ðž Ñ ÑÑÐžÐŒ Ð²ÑÐµ ÑÐ°Ð¹Ð»Ñ Ðž ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Ð² C:\Program Files\gsdl ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑ ÐŽÐ»Ñ Ð²ÑÐµÐŸÐ±ÑÐµÐ³ÐŸ ÑÑÐµÐœÐžÑ (ÐžÐ»Ðž, Ð¿ÐŸ ÐºÑÐ°Ð¹ÐœÐµÐ¹ ÐŒÐµÑÐµ, ÐŽÐŸÑÑÑÐ¿ÐœÑ ÐŽÐ»Ñ ÑÑÐµÐœÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ cgi-script, ÑÐ°ÐºÐžÐŒ ÐºÐ°Ðº "nobody"). ÐÐ»Ñ Ð¿ÑÐŸÐ²ÐµÑÐºÐž ÑÐŸÐ³ÐŸ, Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð»Ðž ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÑÐ°Ð¹Ð»Ñ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ, Ð·Ð°Ð¿ÑÑÑÐžÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ library.exe ÐžÐ· ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž. ÐÑÐ»Ðž ÑÐ°Ð¹Ð»Ñ ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ Ð² ÐœÑÐ¶ÐœÐŸÐŒ ÐŒÐµÑÑÐµ, ÐœÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ ÐŽÐŸÑÑÑÐ¿Ð° ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÐœÐµÐ¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð·Ð°Ð¿ÑÑÑÐžÑÑÑ Ñ ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž, ÐºÐŸÐ³ÐŽÐ°Â Â Â  ';ÑÂ Â  Ð·Ð°Ð¿ÑÑÑÐžÑÐµ ÐµÑ - ÐœÐŸ ÐœÐµ Ñ Ð±ÑÐ°ÑÐ·ÐµÑÐ°, Ñ.Ðµ. ÐºÐŸÐ³ÐŽÐ° nobody Ð¿ÐŸÐ¿ÑÑÐ°ÐµÑÑÑ Ð·Ð°Ð¿ÑÑÑÐžÑÑ ÐµÑ.</Text>
+<Text id="250">ÐÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ð²ÐœÐµÑÐœÐžÑ
+ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ ÑÐµÑÐµÐ· Ð±ÑÐ°ÑÐ·ÐµÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ, ÑÑÐŸÐ±Ñ Ð²ÑÐµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Greenstone Ð±ÑÐ»Ðž ÐŸÐ±ÑÐµÐŽÐŸÑÑÑÐ¿ÐœÑ ÐŽÐ»Ñ ÑÑÐžÑÑÐ²Ð°ÐœÐžÑ. ÐÐžÑÐµÐºÑÐŸÑÐžÑ C:\Program Files\gsdl\etc Ðž Ð²ÑÑ ÐµÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ ÑÐ°ÐºÐ¶Ðµ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑ ÐŽÐ»Ñ ÐŸÐ±ÑÐµÐ³ÐŸÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð·ÑÐžÐŒÑÐŒ.Ð­ÑÐ° ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ, Ð² ÐºÐŸÑÐŸÑÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð·Ð°Ð¿ÐžÑÑÐ²Ð°ÐµÑ Ð²ÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ Ð»ÐŸÐ³Ðž, ÐŸÑÐžÐ±ÐºÐž Ðž ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐŸÐœÐœÑÐµ Ð»ÐŸÐ³Ðž Ðž ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹. ÐÐŸ ÐµÑÐ»Ðž Ð²Ñ Ð²ÑÑ Ð¶Ðµ Ð¶ÐµÐ»Ð°ÐµÑÐµ ÐŸÐ³ÑÐ°ÐœÐžÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ ÐŒÐœÐŸÐ³ÐžÑ
+ Ðº Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ°Ð·ÑÐµÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ ÑÐŸÐ»ÑÐºÐŸ Ðº initout.txt, key.db, users.db, history.db, usage.txt ÐŽÐ»Ñ Ð²ÐœÐµÑÐµÐœÐžÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÐ¹ eg [-Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ.</Text>
+<Text id="251">ÐÑÐ»Ðž ÑÐ°Ð¹Ð»Ñ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐž ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÐœÐµÐ¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ ÐŽÐ»Ñ C:\Program Files\gsdl\etc, Ð²Ñ Ð·Ð°ÐŒÐµÑÐžÑÐµ, ÑÑÐŸ ÑÑÐœÐºÑÐžÑ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÐž Ðž search history ÐœÐµ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ðž ÑÑÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐµ ÑÐŸÐ·ÐŽÐ°ÐµÑ usage log (usage.txt).</Text>
+</Content>
+</Section>
+<Section id="gsdlsite_configuration_file">
+<Title>
+<Text id="252">ÐÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» gsdlsite.cfg</Text>
+</Title>
+<Content>
+<Text id="253">Ð Ð¿ÑÐŸÑÐµÑÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÑÐŸÐ·ÐŽÐ°ÐµÑÑÑ Ð±Ð°Ð·ÐŸÐ²ÑÐ¹ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð», ÐŸÑÐœÐŸÐ²ÑÐ²Ð°ÑÑÐžÐ¹ÑÑ ÐœÐ° Ð²Ð°ÑÐžÑ
+ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐ°Ñ
+ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÑÑÐŸÐ¹ Ð¿ÑÐŸÑÐµÐŽÑÑÑ. Ð­ÑÐŸ ÑÐ°Ð¹Ð» C:\Program Files\gsdl\cgi-bin\gsdlsite.cfg Ðž Ð²ÐŸÑ ÐµÐ³ÐŸ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ:</Text>
+<CodeLine># Site configuration file for Greenstone.</CodeLine>
+<CodeLine># Lines begining with</CodeLine>
+<CodeLine># are comments.</CodeLine>
+<CodeLine># This file should be placed in the same directory as your library</CodeLine>
+<CodeLine># executable file. it should be edited to suit your site.</CodeLine>
+<CodeLine># points to the GSDLHOME directory</CodeLine>
+<CodeLine>gsdlhome âC:/Program Files/gsdlâ</CodeLine>
+<CodeLine># this is the http address of GSDLHOME</CodeLine>
+<CodeLine># if your webservers DocumentRoot is set to $GSDLHOME </CodeLine>
+<CodeLine># then httpprefix can be commented out</CodeLine>
+<CodeLine>httpprefix /gsdl</CodeLine>
+<CodeLine># this is the http address of the directory which</CodeLine>
+<CodeLine># contains the images for the interface.</CodeLine>
+<CodeLine>httpimg /gsdl/images</CodeLine>
+<CodeLine># should contain the http address of this cgi script. This</CodeLine>
+<CodeLine># is not needed if the http server sets the environment variable</CodeLine>
+<CodeLine># SCRIPT_NAME</CodeLine>
+<CodeLine>#gwcgi /cgi-bin/library</CodeLine>
+<CodeLine># maxrequests is the most requests a fastcgi process</CodeLine>
+<CodeLine># will serve before it exits. This can be set to a</CodeLine>
+<CodeLine># low figure (like 1) while debugging and then set</CodeLine>
+<CodeLine># to a high figure (like 10000) when everything is</CodeLine>
+<CodeLine># working well.</CodeLine>
+<CodeLine>#maxrequests 10000</CodeLine>
+<Text id="254">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐœÐ°ÑÑÑÐŸÐžÑÑ Ð²ÑÐµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž Ð¿ÑÑÐµÐŒ ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÑÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð°, Ñ
+ÐŸÑÑ ÑÐºÐŸÑÐµÐµ Ð²ÑÐµÐ³ÐŸ Ð²Ð°ÐŒ ÑÑÐŸ ÐœÐµ Ð¿ÐŸÐœÐ°ÐŽÐŸÐ±ÐžÑÑÑ.</Text>
+<Text id="255">Ð¡ÑÑÐŸÐºÐ°Â <i>gsdlhome</i>Â ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÐŽÐžÑÐµÐºÑÐŸÑÐžÑÂ <i>C:\Program Files\gsdl</i></Text>
+<Text id="256"><i>httpprefix</i>Â ÑÐ²Ð»ÑÐµÑÑÑ WWW-Ð°ÐŽÑÐµÑÐŸÐŒ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, Ð² ÐºÐŸÑÐŸÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ Greenstone. ÐÑÐµÐ¶ÐŽÐµ ÐŒÑ ÐŸÐ¿ÐžÑÑÐ²Ð°Ð»Ðž, ÐºÐ°Ðº ÑÐŸÐ·ÐŽÐ°ÑÑ alias ÑÐ°Ðº, ÑÑÐŸÐ±Ñ Ð¿ÐŸÐžÑÐº ÐÐœÑÐµÑÐœÐµÑ-Ð°ÐŽÑÐµÑÐŸÐ² ÑÐžÐ¿Ð°http://localhost/gsdl/... ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÐ»ÑÑ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐžÂ <i>C:\Program Files\gsdl</i>.Â  ÐÐ²ÐµÐŽÐµÐœÐžÐµ ÑÑÑÐŸÐºÐžÂ Â <i>httpprefix /gsdl</i>Â Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» gsdlsite ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ ÑÐµ Ð¶Ðµ ÑÐ°ÐŒÑÐµ ÑÑÐ»ÐŸÐ²ÐžÑ ÐŽÐ»Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ Greenstone.</Text>
+<Text id="257"><i>httpimg</i>Â ÑÐ²Ð»ÑÐµÑÑÑ ÐÐœÑÐµÑÐœÐµÑ-Ð°ÐŽÑÐµÑÐŸÐŒ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐžÂ <i>C:\Program Files\gsdl\images</i>, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð²ÑÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÐŸÑÐŒÐ°ÑÐŸÐ² gif, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ Ð² ÐžÐœÑÐµÑÑÐµÐ¹ÑÐµ. Ð Ð»ÑÐ±ÐŸÐ¹ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐ¹ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Greenstone ÑÑÐŸ Ð²ÑÐµÐ³ÐŽÐ° Ð±ÑÐŽÐµÑÂ <i>httpprefix/images</i>, Ðž ÑÑÑÐŸÐºÑ Ð² ÑÐ°Ð¹Ð»Ðµ Ð²ÑÑÐµ ÐŒÐŸÐ¶ÐœÐŸ ÐœÐµ ÐžÐ·ÐŒÐµÐœÑÑÑ.</Text>
+<Text id="258"><i>gwcgi</i>Â ÑÐ²Ð»ÑÐµÑÑÑ ÐÐœÑÐµÑÐœÐµÑ-Ð°ÐŽÑÐµÑÐŸÐŒ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ cgi. Ð­ÑÐ° ÑÑÑÐŸÐºÐ° ÐœÐµ ÐœÑÐ¶ÐœÐ° Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²Ñ ÑÐµÑÐ²ÐµÑÐŸÐ² (Ð²ÐºÐ»ÑÑÐ°Ñ Apache), Ðž ÐµÑ ÐœÑÐ¶ÐœÐŸ ÐŸÑÑÐ°Ð²ÐžÑÑ Ð² ÐœÐ°ÑÐ°Ð»ÑÐœÐŸÐŒ Ð²ÐžÐŽÐµ.</Text>
+<Text id="259"><i>maxrequests</i>Â ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð²ÐµÑÑÐžÑÐŒÐž Greenstone, ÐºÐŸÑÐŸÑÑÐµ ÑÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÐœÑ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÐŸÐ¿ÑÐžÐž "fast-cgi". Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐ¹ Ð±ÐžÐœÐ°ÑÐœÑÐ¹ ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ² ÐœÐµ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÑÑÑ ÐŸÐ¿ÑÐžÑ, ÑÐ°Ðº ÐºÐ°Ðº ÐœÐµ Ð²ÑÐµ ÑÐµÑÐµÐ²ÑÐµ ÑÐµÑÐ²ÐµÑÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑ ÑÑÑ ÐŸÐ¿ÑÐžÑ. Fastcgi ÑÑÐºÐŸÑÑÐµÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ cgi Ð·Ð° ÑÑÐµÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ main executable Ð² Ð¿Ð°ÐŒÑÑÐž ÐŒÐµÐ¶ÐŽÑ invocations Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, Ðž ÐŸÑÑÑÑÑÑÐ²ÐžÑ Ð¿ÐŸÑÑÐµÐ±ÐœÐŸÑÑÐž Ð² Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸÐ¹ Ð·Ð°Ð³ÑÑÐ·ÐºÐµ Ñ ÐŽÐžÑÐºÐ° ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐ°Ð·, ÐºÐŸÐ³ÐŽÐ° Ð·Ð°Ð¿ÑÐ°ÑÐžÐ²Ð°ÐµÑÑÑ Ð²ÐµÐ±-ÑÑÑÐ°ÐœÐžÑÐ°. Trade off ÑÐ²Ð»ÑÐµÑÑÑ ÐŸÐ±ÑÐµÐŒ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐ¹ Ð¿Ð°ÐŒÑÑÐž, ÐºÐŸÑÐŸÑÑÐ¹ ÐŒÐŸÐ¶ÐµÑ ÑÐ²ÐµÐ»ÐžÑÐžÐ²Ð°ÑÑÑÑ ÑÐŸ Ð²ÑÐµ Ð±ÐŸÐ»ÑÑÐžÐŒ ÐºÐŸÐœÑÐŸÐŒ.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="personalizing">
+<Title>
+<Text id="260">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐ° Ð±Ð°Ð·ÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ</Text>
+</Title>
+<Content>
+<Text id="261">ÐÐ°Ð²ÐµÑÐœÑÐºÐ° Ð¿ÐµÑÐ²ÑÐŒ ÐŽÐµÐ»ÐŸÐŒ Ð¿ÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº Ð²Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÐµ Ðž ÐœÐ°Ð»Ð°ÐŽÐžÑÐµ Greenstone, Ð²Ñ Ð·Ð°Ñ
+ÐŸÑÐžÑÐµ ÐœÐ°ÑÑÑÐŸÐžÑÑ Ð±Ð°Ð·ÐŸÐ²ÑÑ ÑÑÑÐ°ÐœÐžÑÑ Greenstone. Ð€Ð°Ð¹Ð», ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÑÐ²ÐµÑÐ°ÐµÑ Ð·Ð° ÑÑÑ ÑÑÑÐ°ÐœÐžÑÑ ÐœÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ home.dm Ðž ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÐž macros Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, ÐºÑÐŽÐ° Ð±ÑÐ» ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ Greenstone (ÐÑÐž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑÂ Â  ÑÑÐŸ C:\Program Files\gsdl). Ð­ÑÐŸÑ ÑÐ°Ð¹Ð» ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÑÑÑÐŒ ÑÐµÐºÑÑÐŸÐ²ÑÐŒ ÑÐ°Ð¹Ð»ÐŸÐŒ, ÐºÐŸÑÐŸÑÑÐ¹ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ. ÐÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐœÐŸÐ²ÑÐ¹ ÑÐ°Ð¹Ð», ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, yourhome.dm Ð²ÐŒÐµÑÑÐŸ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ home.dm. ÐÐœ Ð±ÑÐŽÐµÑ Ð¿ÐŸÑ
+ÐŸÐ¶ ÐœÐ° home.dm, ÐœÐŸ Ð±ÑÐŽÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ "package home". Ð­ÑÐ° ÑÐ°ÑÑÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÑÐ²ÐµÑÐ°ÐµÑ Ð·Ð° Ð²ÑÑ ÑÐ°Ð±ÐŸÑÑ ÐœÐµÐŒÐœÐŸÐ³ÐŸ Ð¿ÐŸ-ÐŽÑÑÐ³ÐŸÐŒÑ.</Text>
+<Text id="262">ÐÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÐŸÑÐŽÐµÐ»ÑÐœÐŸÐ¹ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ ÐœÑÐ¶ÐœÐŸ ÑÐŸÐµÐŽÐžÐœÐžÑÑ ÐµÑ Ñ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐŸÐ¹. Ð ÐµÑÐµÐœÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÐµÑ Greenstone, ÑÐŸÑÐŸÐžÑ Ð² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž "ÐŒÐ°ÐºÑÐŸÑÐŸÐ²"(ÐŒÐ°ÐºÑÐŸÑÐ»ÐµÐŒÐµÐœÑÑ, ÐŒÐ°ÐºÑÐŸÐºÐŸÐŒÐ°ÐœÐŽÑ).ÐÐŸÑÑÐŸÐŒÑ ÐœÐ°ÑÐ°Ð»ÑÐœÐ°Ñ Ð±Ð°Ð·ÐŸÐ²Ð°Ñ ÑÑÑÐ°ÐœÐžÑÐ° ÐžÐŒÐµÐµÑ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµ ".dm", Ð° ÐœÐµ ".html". Ð€Ð°Ð¹Ð» macro Ð±ÐŸÐ»ÑÑÐµ ÐœÐµÐ¶ÐµÐ»Ðž Ð¿ÑÐŸÑÑÐŸÐ¹ HTML. ÐÐŸ ÐœÐµ Ð±ÐµÑÐ¿ÐŸÐºÐŸÐ¹ÑÐµÑÑ: ÐŒÐ°ÐºÑÐŸ-ÑÐ°Ð¹Ð» ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð¿ÑÐŸÑÑÐŸÐ¹ HTML Ðž ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÐ¹, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÑ
+ ÐœÐžÐ¶Ðµ. ÐÐ°ÐºÑÐŸÑÐ·ÑÐº ÑÐ²Ð»ÑÐµÑÑÑ ÐŒÐŸÑÐœÑÐŒ ÑÑÐµÐŽÑÑÐ²ÐŸÐŒ, Ðž ÑÐŸÐ»ÑÐºÐŸ ÐŒÐ°Ð»Ð°Ñ ÐµÐ³ÐŸ ÑÐ°ÑÑÑ ÐŸÐ¿ÐžÑÐ°ÐœÐ° ÐœÐžÐ¶Ðµ - ÑÐŒÐŸÑÑÐžÑÐµ Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° ÐŽÐ»Ñ Ð±ÐŸÐ»ÑÑÐµÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž.</Text>
+<Section id="example">
+<Title>
+<Text id="263">ÐÑÐžÐŒÐµÑ</Text>
+</Title>
+<Content>
+<Figure id="your_own_greenstone_home_page">
+<Title>
+<Text id="264">Ð ÐžÑÑÐœÐŸÐº 3 ÐÐ°ÑÐ° ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÐ°Ñ ÐŽÐŸÐŒÐ°ÑÐœÑÑ ÑÑÑÐ°ÐœÐžÑÐ°</Text>
+</Title>
+<File width="407" height="242" url="images/Install_Fig_3.png"/>
+</Figure>
+<Text id="265">ÐÐ° ÑÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="your_own_greenstone_home_page"/> Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ Ð¿ÑÐžÐŒÐµÑ ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ¹ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž. ÐÐ°Ð¶ÐŽÐ°Ñ ÐžÐ· ÑÑÑÐ»ÐŸÐº "click here" (ÐœÐ°Ð¶ÐŒÐžÑÐµ) Ð¿ÑÐžÐ²ÐµÐŽÐµÑ Ð²Ð°Ñ Ðº ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐŒ ÑÑÐµÐŽÑÑÐ²Ð°ÐŒ Greenstone. Ð­ÑÐ° ÑÑÑÐ°ÐœÐžÑÐ° Ð±ÑÐ»Ð° ÑÐŸÐ·ÐŽÐ°ÐœÐ° ÑÐ°Ð¹Ð»ÐŸÐŒ yourhome.dm, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÑÐŒ ÐœÐ° Ð ÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="yourhome_dm"/>.</Text>
+<Figure id="yourhome_dm">
+<Title>
+<Text id="266"><i>yourhome.dm</i>, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ð ÐžÑÑÐœÐºÐ° <CrossRef target="Figure" ref="your_own_greenstone_home_page"/></Text>
+</Title>
+<File width="407" height="388" url="Install_files/image011.jpg"/>
+</Figure>
+<Text id="267">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð ÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="yourhome_dm"/> ÐºÐ°Ðº ÐŸÑÐœÐŸÐ²Ñ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ð²Ð°ÑÐžÑ
+ Ð±Ð°Ð·ÐŸÐ²ÑÑ
+ ÑÑÑÐ°ÐœÐžÑ Ð² Greenstone. Ð ÑÑÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ Ð²ÑÐµ ÑÐ²ÐŸÐŽÐžÑÑÑ Ðº ÑÐŸÐŒÑ, ÑÑÐŸÐ±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÐŒÐ°ÐºÑÐŸÑ, ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÑÐ¹ content (ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ). ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÑÐµÐºÑÑ, ÑÐ°ÐºÐ¶Ðµ Ð»ÑÐ±ÑÐµ ÑÐŸÑÐŒÐ°ÑÐœÑÐµ ÐºÐŸÐŒÐ°ÐœÐŽÑ HTML, ÐŽÐ»Ñ Ð¿ÐŸÐŒÐµÑÐµÐœÐžÑ Ð²ÑÐµÐ³ÐŸ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÐ³ÐŸ Ð²Ð°ÐŒ ÐœÐ° ÑÑÑ ÑÑÑÐ°ÐœÐžÑÑ Ð¢ÐµÐºÑ Ñ, ÐºÐŸÑÐŸÑÑÐ¹ Ð²Ñ Ð²Ð²ÐŸÐŽÐžÑÐµ, ÑÑÐŸ Ð¿ÑÐŸÑÑÐŸÐ¹ HTML; ÐµÑÐ»Ðž Ð²Ñ Ð¶ÐµÐ»Ð°ÐµÑÐµ, ÐŒÐŸÐ¶ÐœÐŸ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ Ð³ÐžÐ¿ÐµÑÑÑÑÐ»ÐºÐž Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÑÑÐ³ÐžÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž, Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐµÐŒÑÐµ HTML.</Text>
+<Text id="268">ÐÐ»Ñ ÑÐŸÐµÐŽÐžÐœÐµÐœÐžÑ Ð²Ð°ÑÐµÐ¹ ÐœÐŸÐ²ÐŸÐ¹ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ Ñ ÐŽÑÑÐ³ÐžÐŒÐž ÑÑÑÐ°ÐœÐžÑÐ°ÐŒÐž Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐµ "ÑÐºÐ°Ð·Ð°ÐœÐžÐµ". Ð ÑÐ·ÑÐºÐµ ÐŒÐ°ÐºÑÐŸÑ ÐžÐŒÐž ÑÐ²Ð»ÑÑÑÑÑ ÑÐµ ÑÐ»ÐŸÐ²Ð°, ÐºÐŸÑÐŸÑÑÐµ Ñ ÐŽÐ²ÑÑ
+ ÑÑÐŸÑÐŸÐœ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÑ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÐŒÐž Ð·ÐœÐ°ÐºÐ°ÐŒÐž .ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑ
+ ÑÐ²ÐžÐŽÐµÑÑ ÐœÐ° Ð ÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="yourhome_dm"/>.Â ÐÐ°Ð¿ÑÐžÐŒÐµÑ, _httppagehome_ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ ÐœÐ° Ð±Ð°Ð·ÐŸÐ²ÑÑ ÑÑÑÐ°ÐœÐžÑÑ, httppagehelp_ Ð¿ÑÐžÐ²ÐŸÐŽÐžÑ Ðº ÑÑÑÐ°ÐœÐžÑÐµ Ð¡Ð¿ÑÐ°Ð²ÐºÐž Ðž Ñ.ÐŽ. Ð ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÑÐ»ÑÑÐ°ÑÑ
+ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ ÑÐºÐ°Ð·Ð°ÑÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, httpquery_&amp;c=demo ÐœÐ°ÑÑÑÐ°ÐžÐ²Ð°ÐµÑ ÑÑÑÐ°ÐœÐžÑÑ Ð¿ÐŸÐžÑÐºÐ° ÐœÐ° ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ; ÐŽÐ»Ñ ÐŽÑÑÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÐŽÐµÑÐµ Ð·Ð°ÐŒÐµÐœÐžÑÑ demo ÐœÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="269">ÐÐ°ÐºÑÐŸÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ, ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÐŸÐµ _content_,Â Â  ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÐŸÑÑÑÐŒ HTML ÐÑÐ±ÐŸÐ¹ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐ¹ ÐºÐŸÐŽ HTML ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð·Ð°ÐŒÐµÐœÐµÐœ ÐŒÐ°ÐºÑÐŸÂ­ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑÐŒÐž. ÐÐŽÐœÐ°ÐºÐŸ, ÑÐ°ÐºÐžÐµ ÑÐžÐŒÐ²ÐŸÐ»Ñ, ÐºÐ°Ðº '{', '}', 'V, Ðž '_' ÐœÑÐ¶ÐœÐŸ Ð²ÑÐŽÐµÐ»ÑÑÑ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ backslash, ÑÑÐŸÐ±Ñ ÐžÐ·Ð±ÐµÐ¶Ð°ÑÑ ÐžÑ
+ Ð¿ÐµÑÐµÑÐµÑÐ°Ð±ÐŸÑÐºÐž ÐŒÐ°ÐºÑÐŸ ÑÐ·ÑÐºÐŸÐ²ÐŸÐ¹ ÐžÐœÑÐµÑÐ¿ÑÐµÑÐ°ÑÐŸÑ.</Text>
+<Text id="270">ÐÐ°ÐŒÐµÑÑÑÐµ, ÑÑÐŸ ÐŒÐ°ÐºÑÐŸÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ _content_ ÐœÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐœÐžÐºÐ°ÐºÐžÑ
+ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ² Ðž footer. ÐÑÐ»Ðž Ð²Ñ Ð¶ÐµÐ»Ð°ÐµÑÐµ ÐžÐ·ÐŒÐµÐœÐžÑÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž ÐžÐ»Ðž footer Ð²Ð°ÑÐµÐ¹ Ð±Ð°Ð·ÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ, ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐžÑÑ ÐŒÐ°ÐºÑÐŸÑÑ header_ Ðž/ÐžÐ»Ðž Jooter_, ÐŽÐŸÐ±Ð°Ð²ÐžÐ² ÐžÑ
+ Ð² ÑÐ°Ð¹Ð» yourhome.dm Ð² Ð²ÐžÐŽÐµ:</Text>
+<CodeLine>_macroname_ {</CodeLine>
+<CodeLine>...</CodeLine>
+<CodeLine>}</CodeLine>
+<Text id="271">ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð¿ÑÐŸÑÑÐ¶ÐµÐœÐœÑÐ¹ Ð·ÐµÐ»ÐµÐœÑÐ¹ ÑÐžÑÑÐœÐŸÐº, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÐ¹ÑÑ Ð² Ð»ÐµÐ²ÐŸÐ¹ ÑÐ°ÑÑÐž ÑÑÑÐ°ÐœÐžÑÑ, ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœ Ð² ÐŒÐ°ÐºÑÐŸÑÐµ _header_, Ðž Ð¿ÑÐž ÑÐŽÐ°Ð»ÐµÐœÐžÐž ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ ÑÑÐŸÐ³ÐŸ ÐŒÐ°ÐºÑÐŸÑÐ° ÑÐžÑÑÐœÐŸÐº <CrossRef target="Figure" ref="yourhome_dm"/> ÑÐ±ÐµÑÐµÑÑÑ.</Text>
+</Content>
+</Section>
+<Section id="how_to_make_it_work">
+<Title>
+<Text id="272">Â  Ð§ÑÐŸ ÐœÑÐ¶ÐœÐŸ ÑÐŽÐµÐ»Ð°ÑÑ, ÑÑÐŸÐ±Ñ Ð²ÑÑ Ð·Ð°ÑÐ°Ð±ÐŸÑÐ°Ð»ÐŸ</Text>
+</Title>
+<Content>
+<Text id="273">ÐÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ Ð²Ð°Ñ ÑÐ°Ð¹Ð» yourhome.dm ÐœÐ°ÑÐ°Ð» ÑÐ°Ð±ÐŸÑÐ°ÑÑ, Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐºÐ°Ð·Ð°ÑÑ ÐµÐ³ÐŸ Ð² Ð³Ð»Ð°Ð²ÐœÐŸÐŒ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ main.cfg, ÑÐ°Ðº ÐºÐ°Ðº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÑÑÐžÑÑÐ²ÐµÑ ÐŒÐ°ÐºÑÐŸÑÐ°Ð¹Ð»Ñ, ÑÐºÐ°Ð·Ð°ÐœÐœÑÐµ Ð² ÐœÐµÐŒ.</Text>
+<Text id="274">Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, ÑÑÐŸÐ±Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐ°ÑÐ°Ð»Ð° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð±Ð°Ð·ÐŸÐ²ÑÑ ÑÑÑÐ°ÐœÐžÑÑ, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÑ Ð²Ð°ÐŒÐž Ð²ÐŒÐµÑÑÐŸ ÐœÐ°ÑÐ°Ð»ÑÐœÐŸÐ¹, Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ Ð¿ÐŸÐŒÐµÑÑÐžÑÑ yourhome.dm Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ macros ÐœÐ° Ð ÐžÑÑÐœÐºÐµ <CrossRef target="Figure" ref="yourhome_dm"/>. ÐÐ°ÑÐµÐŒ Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ main.cfg Ð·Ð°ÐŒÐµÐœÐžÑÐµÂ Â  home.dmÂ Â  ÐœÐ° yourhome.dm Ð² ÑÐ¿ÐžÑÐºÐµ ÐŒÐ°ÐºÑÐŸÑ ÑÐ°Ð¹Ð»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÐ»Ð¶ÐœÑ Ð·Ð°Ð³ÑÑÐ¶Ð°ÑÑÑÑ Ð¿ÑÐž Ð·Ð°Ð¿ÑÑÐºÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ.</Text>
+</Content>
+</Section>
+<Section id="redirecting_a_url_to_greenstone">
+<Title>
+<Text id="275">ÐÐµÑÐµÐ°ÐŽÑÐµÑÐ°ÑÐžÑ URL Ðº Greenstone</Text>
+</Title>
+<Content>
+<Text id="276">ÐÐ»Ñ Ð°ÐŽÑÐµÑÐŸÐ² Ðº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ cgi Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŸÐ·ÐŽÐ°ÑÑ Ð±ÐŸÐ»ÐµÐµ ÑÐŽÐŸÐ±ÐœÑÑ Ð¿ÐµÑÐµÐ°ÐŽÑÐµÑÐŸÐ²ÐºÑ(Ð±ÐŸÐ»ÐµÐµ ÐºÐŸÑÐŸÑÐºÐ°Ñ Ðž ÑÐ¶Ð°ÑÐ°Ñ ÑÐŸÑÐŒÐ°). ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð°ÐŽÑÐµÑ URL http://nzdl.org (ÑÐŸÐºÑÐ°ÑÐµÐœÐ°ÑÂ Â  ÑÐŸÑÐŒÐ°Â Â  http://nzdl.org/index.html) Ð¿ÐµÑÐµÐ°ÐŽÑÐµÑÐŸÐ²ÑÐ²Ð°ÐµÑÑÑ ÐœÐ° Ð°ÐŽÑÐµÑÂ  http://nzdl.org/cgi-bin/library. Ð¡ÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Apache Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÑ ÑÑÐŸ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐŽÐžÑÐµÐºÑÐžÐ²ÑÂ Â  Redirect. ÐÐ°Ðº Ðž ÐŽÑÑÐ³ÐžÐµ ÐŽÐžÑÐµÐºÑÐžÐ²Ñ, ÐŸÐœÐ° ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² C:\Program Files\Apache Group\Apache\conf\httpd.conf. ÐÐ»Ñ Ð¿ÐµÑÐµÐ°ÐŽÑÐµÑÐ°ÑÐžÐžÂ Â Â  URLÂ  http://www.yourserver.com ÐÐ° http:// www.yourserver.com/cgi-bin/libraryÂ Â  Ð²Ð²ÐµÐŽÐžÑÐµ ÑÑÐŸ Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» httpd.conf:</Text>
+<CodeLine>Redirect /index.html http://www.yourserver.com/cgi-bin/library</CodeLine>
+<Text id="277">Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ Ð²Ñ Ð¿ÐŸÐ»ÑÑÐžÑÐµ Ð¿ÑÑÐŒÐŸÐ¹ ÐŽÐŸÑÑÑÐ¿ Ðº Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐµ ÑÐµÑÐµÐ· Ð°ÐŽÑÐµÑ http://www.yourserver.com . ÐÑÐ»Ðž Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ, ÑÑÐŸÐ±Ñ Ð°ÐŽÑÐµÑ http:// www.yourserver .com/greenstone Ð¿ÑÐžÐ²ÐŸÐŽÐžÐ» Ð²Ð°Ñ Ðº Â http://www.yourserver.com/ cgi-bin/library Ð²Ð²ÐµÐŽÐžÑÐµ Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ:</Text>
+<CodeLine>Redirect /greenstone http://www.yourserver.com/cgi-bin/library</CodeLine>
+<Text id="278">ÐÑÐ»Ðž Ñ Ð²Ð°ÑÐµÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ° ÐœÐµÑ ÐŽÐŸÐŒÐµÐœÐœÐŸÐ³ÐŸ ÐžÐŒÐµÐœÐž (ÐºÐ°Ðº www.yourserver.com Ð²ÑÑÐµ), Ð¿ÑÐŸÑÑÐŸ Ð·Ð°ÐŒÐµÐœÐžÑÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ www.yourserver.com ÐœÐ° localhost Ð² ÑÑÑÐŸÐºÐ°Ñ
+, ÑÐºÐ°Ð·Ð°ÐœÐœÑÑ
+ Ð²ÑÑÐµ. Ð­ÑÐŸ Ð¿ÑÐžÐ²ÐµÐŽÐµÑ Ðº ÑÐ°ÐºÐŸÐŒÑ Ð¶Ðµ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÑ.</Text>
+<Text id="279">ÐÐŒÐµÑÑÐŸ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ Ð¿ÐŸÐŒÐµÑÐ°ÑÑ ÐŽÐžÑÐµÐºÑÐžÐ²Ñ Ð¿ÐµÑÐµÐ°ÐŽÑÐµÑÐ°ÑÐžÐž Ð² ÑÐ°Ð¹Ð» http.conf, Ð²Ñ ÑÐ°ÐºÐ¶Ðµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐŒÐµÑÑÐžÑÑ ÐžÑ
+ Ð² ÑÐ°Ð¹Ð» .htaccess, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÐ¹ÑÑ Ð² ÐºÐŸÑÐœÐµÐ²ÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Ð²Ð°ÑÐµÐ³ÐŸ ÑÐµÑÐ²ÐµÑÐ°. ÐÑÐžÂ  Ð²ÐœÐµÑÐµÐœÐžÐž ÐžÐ·ÐŒÐµÐœÐµÐœÐžÐ¹ Ð² ÑÐ°Ð¹Ð» .htaccess ÐŸÐœÐž Ð²ÑÑÑÐ¿ÑÑ Ð² ÑÐžÐ»Ñ ÐœÐµÐŒÐµÐŽÐ»ÐµÐœÐœÐŸ, ÑÐŸÐ³ÐŽÐ°Â  ÐºÐ°Ðº ÐŽÐ»Ñ ÐœÐ°ÑÐ°Ð»Ð° ÑÐ°Ð±ÐŸÑÑ Ñ ÐžÐ·ÐŒÐµÐœÐµÐœÐœÑÐŒ ÑÐ°Ð¹Ð»ÐŸÐŒ httpd.conf ÐœÑÐ¶ÐœÐŸ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÐžÑÑ Apache. ÐÐŸ- Ð²ÑÐŸÑÑÑ
+, ÑÐ°ÑÑÐŸ Ð² ÑÐžÑÑÐµÐŒÐµ Unix Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÑÑÑ "ÐºÐŸÑÐœÐµÐ²ÑÐŒ" Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐŒ ÐŽÐ»Ñ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ httpd.conf, Ð² ÑÐŸ Ð²ÑÐµÐŒÑ ÐºÐ°Ðº Ð»ÑÐ±ÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ðž ÐŒÐŸÐ³ÑÑ ÐžÐ·ÐŒÐµÐœÐžÑÑ .htaccess.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_associated_software">
+<Title>
+<Text id="280">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ</Text>
+</Title>
+<Content>
+<Text id="281">Here is how to obtain the software packages mentioned above.</Text>
+<Section id="apache_webserver">
+<Title>
+<Text id="282">Ð¡ÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Apache</Text>
+</Title>
+<Content>
+<Text id="283">ÐÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ñ Ð»ÑÐ±ÐŸÐ¹ Ð²ÐµÑÑÐžÐµÐ¹ Greenstone, Ð·Ð° ÐžÑÐºÐ»ÑÑÐµÐœÐžÐµÐŒ ÐÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž, Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ. ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÑÐžÑÑÐŸÐ²ÑÑ
+ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐº, Ð² ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž ÐŸÐ±ÑÐµÐŒÐœÑÐµ, ÑÐ¶Ðµ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ Ð² ÑÐµÐ±Ðµ Ð²ÑÑÑÐŸÐµÐœÐœÑÐµ ÑÐµÑÐ²ÐµÑÑ. Ð¡ ÑÐ°Ð¹ÑÐ° Www.apache.orgÂ Â  ÐŒÐŸÐ¶ÐœÐŸ Ð±ÑÑÑÑÐŸ Ðž Ð±ÐµÑÐ¿Ð»Ð°ÑÐœÐŸ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ ÑÐµÑÐµÐ²ÐŸÐ¹ ÑÐµÑÐ²ÐµÑ Apache.</Text>
+</Content>
+</Section>
+<Section id="perl">
+<Title>
+<Text id="284">Perl</Text>
+</Title>
+<Content>
+<Text id="285">ÐÐ»ÑÂ Â Â  Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑÂ Â Â  ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹Â Â Â  GreenstoneÂ Â Â  ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÂ Â  ÑÐ·ÑÐº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ Perl.Â Â  ÐÐµÑÑÐžÑ Greenstone, Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÐ°Ñ ÐŽÐ»Ñ Windows, ÑÐ¶Ðµ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð² ÑÐµÐ±Ñ Perl. ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÑÐžÑÑÐµÐŒ Unix ÑÐ°ÐºÐ¶Ðµ ÐžÐŒÐµÑÑ Perl, ÐœÐŸ ÐµÑÐ»Ðž ÐŸÐœ ÐœÐµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ, ÑÐŸ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð±ÐµÑÐ¿Ð»Ð°ÑÐœÐŸ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ Ðž Ð±ÐžÐœÐ°ÑÐœÑÐ¹ ÐºÐŸÐŽ ÑÑÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŽÐ»Ñ ÑÐ°Ð·ÐœÑÑ
+ Ð²ÐµÑÑÐžÐ¹ Unix Ñ ÑÐ°Ð¹ÑÐ° www.perl.com. ÐÐ°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐ° Ð²ÐµÑÑÐžÑ Perl 5.0 ÐžÐ»Ðž Ð²ÑÑÐµ.</Text>
+</Content>
+</Section>
+<Section id="gcc">
+<Title>
+<Text id="286">GCC</Text>
+</Title>
+<Content>
+<Text id="287">ÐÐµÑÑÐžÑ Greenstone ÐŽÐ»Ñ Unix ÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÑÐµÑÑÑ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ Gnu C++ compiler (GCC). Greenstone ÑÐ°ÑÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ ÑÐ°Ð±Ð»ÐŸÐœÐœÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ C++ (ÐŒÑ ÐŸÐ±ÐœÐ°ÑÑÐ¶ÐžÐ»Ðž, ÑÑÐŸ ÐŸÐœÐ° ÐœÐµ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÑÐŸ ÑÑÐ°ÑÑÐŒÐž Ð²ÐµÑÑÐžÑÐŒÐž GCC; Ð¿ÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, ÑÐŸÐŸÐ±ÑÐžÑÐµ ÐœÐ°ÐŒ, ÐµÑÐ»Ðž Ñ Ð²Ð°Ñ Ñ ÑÑÐžÐŒ Ð²ÐŸÐ·ÐœÐžÐºÐœÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ). ÐÐ°ÐŒÐµÑÑÑÐµ, ÑÑÐŸ ÑÑÐ° Ð²ÐµÑÑÐžÑ Greenstone ÐœÐµ ÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÑÐµÑÑÑ Ð² GCC 3.0.</Text>
+</Content>
+</Section>
+<Section id="gdbm">
+<Title>
+<Text id="288">GDBM</Text>
+</Title>
+<Content>
+<Text id="289">ÐÑÐµ Ð²ÐµÑÑÐžÐž Greenstone ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ Gnu Database Manager, GDBM. ÐÐœÐ° ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÐµÑÑÑ Ð²ÐŒÐµÑÑÐµ ÑÐŸ Ð²ÑÐµÐŒÐž Ð²ÐµÑÑÐžÑÐŒÐž Greenstone Ð¿ÐŸÐŽ Windows Ðž ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð²ÐŸ Ð²ÑÐµÐŒÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž. ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ Ð²ÐµÑÑÐžÐ¹ Linux ÑÐ¶Ðµ ÐžÐŒÐµÑÑ GDBM, Ð¿ÐŸÑÑÐŸÐŒÑ ÐŸÐœ ÐœÐµ Ð²ÐºÐ»ÑÑÐµÐœ Ð² ÐŽÐžÑÐº ÐŽÐ»Ñ Greenstone Ð¿ÐŸÐŽ Linux. ÐÐŸ ÐµÑÐ»Ðž Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒ GDBM, ÑÐŸ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐµÐ³ÐŸ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ Ñ ÑÐ°Ð¹ÑÐ° Www.gnu.org.</Text>
+</Content>
+</Section>
+<Section id="java_runtime_environment">
+<Title>
+<Text id="290">Java Runtime Environment</Text>
+</Title>
+<Content>
+<Text id="291">Ð§ÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Greenstone, ÐÐ°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐ° Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÐ°Ñ Ð²ÐµÑÑÐžÑ JRE. ÐÑÐ»Ðž ÐÑ ÐµÑÐµ ÐœÐµ ÑÐ°ÑÐ¿ÐŸÐ»Ð°Ð³Ð°ÐµÑÐµ ÐµÑ, Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÐ°Ñ Ð²ÐµÑÑÐžÑ Ð²ÐºÐ»ÑÑÐµÐœÐ° Ð² CD-ROM. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ Ð¿ÐŸÑÐ»ÐµÐŽÐœÑÑ Ð²ÐµÑÑÐžÑ Ñ ÑÐ°Ð¹ÑÐ°http://java.sun.com/j2se/downloads.html. ÐÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐ° Ð²ÐµÑÑÐžÑ 1.4.0 ÐžÐ»Ðž Ð²ÑÑÐµ.</Text>
+</Content>
+</Section>
+<Section id="java_compiler">
+<Title>
+<Text id="292">ÐÐŸÐŒÐ¿ÐžÐ»ÑÑÐŸÑ Java</Text>
+</Title>
+<Content>
+<Text id="293">ÐÐ»Ñ ÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Greenstone ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐœÐ°ÑÐ°Ð»Ð° ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Java Development Kit. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ J2SE c cÐ°Ð¹ÑÐ°http://java.sun.com/j2se/downloads.html. Ð¢ÑÐµÐ±ÑÐµÑÑÑ Ð²ÐµÑÑÐžÑ 1.4.0 ÐžÐ»Ðž Ð²ÑÑÐµ.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/ru/Paper_ru.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/ru/Paper_ru.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/ru/Paper_ru.xml	(revision 13632)
@@ -0,0 +1,1135 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">ÐŠÐÐ€Ð ÐÐÐÐ¯ ÐÐÐÐÐÐÐ¢ÐÐÐ GREENSTONE</Text>
+</Heading>
+<Title>
+<Text id="2">ÐÐ¢ ÐÐ£ÐÐÐÐ Ð ÐÐÐÐÐÐÐŠÐÐ</Text>
+</Title>
+<Author>
+<Text id="3">Dr Michel Loots, Dan Camarzan and Ian H. Witten</Text>
+</Author>
+<Affiliation>
+<Text id="4">Human Info NGO, BelgiumÂ <br/>Simple Words, RomaniaÂ <br/>Â University of Waikato, New Zealand</Text>
+</Affiliation>
+<Text id="5">ÐÑÐ³Ð°ÐœÐ°Ð¹Ð·ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð¿ÑÐŸÑÐµ ÐÑÐ³Ð°ÐœÐ°Ð¹Ð·ÐµÑ, ÑÐ²Ð»ÑÐµÑÑÑ ÑÐ²ÐŸÐ±ÐŸÐŽÐœÐŸ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒ Ð¿Ð°ÐºÐµÑÐŸÐŒ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ, Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐŒ ÐŽÐ»Ñ Ð¿ÐŸÐŒÐŸÑÐž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ Ðž ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐŒÐ°ÑÐµÑÐžÐ°Ð», ÑÐ²ÑÐ·Ð°ÐœÐœÑÐ¹ Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹. ÐÐœ ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÐ»ÑÑ Ñ Ð±ÐŸÐ»ÐµÐµ ÑÐ°ÐœÐœÐžÐŒÐž Ð²ÐµÑÑÐžÑÐŒÐž Greenstone. ÐÐ³ÐŸ ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ð±ÑÐ»Ðž Ð·Ð°ÐŒÐµÐœÐµÐœÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐŒ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐŸÐŒ, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐŒ Ð²Â <i>Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</i>. Ð­ÑÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ ÐŸÐ±ÑÐ°ÑÐœÑÑ ÑÐŸÐ²ÐŒÐµÑÑÐžÐŒÐŸÑÑÑ, ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ, ÐºÐ°Ðº ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐÑÐ³Ð°ÐœÐ°Ð¹Ð·ÐµÑ.</Text>
+<Comment>
+<Text id="6">ÐÑ ÐœÐ°ÐŽÐµÐµÐŒÑÑ, ÑÑÐŸ ÑÑÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ñ
+ÐŸÑÐŸÑÐŸ. ÐÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, ÑÐŸÐŸÐ±ÑÐžÑÐµ ÐŸ Ð»ÑÐ±ÑÑ
+ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ°Ñ
+ Ð¿ÐŸ Ð°ÐŽÑÐµÑÑ:Â <i>greenstone@cs.waikato.ac.nz</i></Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.50</Text>
+</Version>
+<Date>
+<Text id="8">ÐÐ°ÑÑ 2004</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">ÐÐ± ÑÑÐŸÐ¹ ÐžÐœÑÑÑÑÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="10">Ð­ÑÐ° ÐžÐœÑÑÑÑÐºÑÐžÑ ÐŽÐµÑÐ°Ð»ÑÐœÐŸ ÐŸÐ±ÑÑÑÐœÑÐµÑ, ÐºÐ°Ðº ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ CD-ROM ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐ· Ð±ÑÐŒÐ°Ð¶ÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÐŽÐµÑÑ ÐŽÐµÑÐ°Ð»ÑÐœÐŸ ÐŸÐ¿ÐžÑÑÐ²Ð°ÑÑÑÑ Ð¿ÑÐŸÑÐµÐŽÑÑÑ Ðž ÑÐºÐŸÐœÐŸÐŒÐžÑÐµÑÐºÐžÐµ ÑÑÐŸÑÐŸÐœÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž ÐŸÐ¿ÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐœÐžÑ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² (ÐÐ Ð¡), ÑÐ°Ðº ÑÑÐŸ Ð²Ñ Ð¿ÐµÑÐµÐ²ÐµÐŽÐµÑÐµ ÑÐµÐºÑÑ Ð² Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÑÐ¹ ÑÐŸÑÐŒÐ°Ñ, Ð¿ÑÐžÐŒÐµÐœÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone. Ð­ÑÐŸ ÑÐ°ÐºÐ¶Ðµ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ, ÐºÐ°Ðº ÑÐŸÐ·ÐŽÐ°ÑÑ Ðž ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐŒÐ°ÑÐµÑÐžÐ°Ð», ÑÐ²ÑÐ·Ð°ÐœÐœÑÐ¹ Ñ ÑÐŸÐ±ÑÐ°ÐœÐžÐµÐŒ.</Text>
+<Text id="11">Ð ÐœÐ°ÑÐµÐŒ ÐŸÐ±ÑÑÑÐœÐµÐœÐžÐž ÐŒÑ ÑÑÐ°ÑÐ°Ð»ÐžÑÑ Ð±ÑÑÑ ÑÑÐœÑÐŒÐž ÐœÐ°ÑÐºÐŸÐ»ÑÐºÐŸ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ. Ð¡ÑÑÐ»ÐºÐ° ÐœÐ° Ð»ÑÐ±ÑÐµ ÑÐŸÑÐ³ÐŸÐ²ÑÐµ ÐŒÐ°ÑÐºÐž ÐžÐ»Ðž Ð¿ÑÐŸÐŽÑÐºÑÑ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÐž â ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ð»ÐžÑÑ ÐŽÐ»Ñ ÐžÐ»Ð»ÑÑÑÑÐ°ÑÐžÐ²ÐœÑÑ
+ ÑÐµÐ»ÐµÐ¹, Ðž ÐœÐµ Ð¿ÐŸÐŽÑÐ°Ð·ÑÐŒÐµÐ²Ð°ÑÑ, ÑÑÐŸ Ð² ÑÑÐ°Ð²ÐœÐµÐœÐžÐž Ñ Ð»ÑÐ±ÑÐŒ ÐŽÑÑÐ³ÐžÐŒ , ÐŒÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ ÐžÐ»Ðž ÐŸÐŽÐŸÐ±ÑÑÐµÐŒ ÑÑÐŸ ÐžÐ·ÐŽÐµÐ»ÐžÐµ.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="12">Ð¡ÐŸÐ¿ÑÑÑÑÐ²ÑÑÑÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ</Text>
+</Title>
+<Content>
+<Text id="13">ÐÐŸÐ»ÐœÑÐ¹ ÐºÐŸÐŒÐ¿Ð»ÐµÐºÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÐž Ðº Greenstone ÑÐŸÑÑÐŸÐžÑ ÐžÐ· Ð¿ÑÑÐž ÑÐŸÐŒÐŸÐ²:</Text>
+<BulletList>
+<Bullet>
+<Text id="14">Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð¿ÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="15">ÐÐœÑÑÑÑÐºÑÐžÑ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐº Ð° ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="17">ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: ÐŸÑ ÐÑÐŒÐ°Ð³Ðž ÐŽÐŸ ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÑÑÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ)</Text>
+</Bullet>
+<Bullet>
+<Text id="18">ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÑÐ³Ð°ÐœÐ°Ð¹Ð·ÐµÑÐ°</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">ÐÐ»Ð°Ð³ÐŸÐŽÐ°ÑÐœÐŸÑÑÑ</Text>
+</Title>
+<Content>
+<Text id="20">ÐÐ¿ÐµÑÐ°ÑÐžÐž ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž ÐŽÑÑÐ³ÐžÐµ ÐœÐŸÑ-Ñ
+Ð°Ñ ÑÐ²ÑÐ·Ð°ÐœÐœÑÐµ Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµÐŒ ÑÐŸÐ²ÐŒÐµÑÑÐœÑÑ
+ ÐœÐµ ÐºÐŸÐŒÐŒÐµÑÑÐµÑÐºÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð±ÑÐ»Ðž ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°ÐœÑ ÐÐ°Ð¹ÐºÐ»ÐŸÐŒ ÐÐŸÑÑÐŸÐŒ, ÐÐ ÐÐÐ Ð¥ÑÑÐŒÐ°Ðœ ÐÐœÑÐŸ Ðž Ð¥ÑÑÐŒÐ°ÐœÐ¡Ð, ÐÑÐœÐŸÐŒ ÐÐ°ÐŒÐ°ÑÐ·Ð°ÐœÐŸÐŒ ÐžÐ· Ð¡ÐžÐŒÐ» ÐÐŸÐ»ÐŽ Ðž ÐµÐ³ÐŸ Ð³ÑÑÐ¿Ð¿ÐŸÐ¹ Ð² ÑÐŸÑÑÑÐŽÐœÐžÑÐµÑÑÐ²Ðµ Ñ ÐÑÐ°ÑÐŸÐ², Ð ÑÐŒÑÐœÐžÑ.</Text>
+<Text id="21">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone - Ð¿ÑÐŸÐŽÑÐºÑ ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸÐ³ÐŸ ÑÑÑÐŽÐ° ÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ð° Ð»ÑÐŽÐµÐ¹. Rodger McNab Ðž Stefan Boddie Ð¿ÑÐžÐœÑÐžÐ¿ÐžÐ°Ð»ÑÐœÑÐµ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐž ÑÐžÑÑÐµÐŒÑ. ÐÐµÐŸÑÐµÐœÐžÐŒÑÐ¹ Ð²ÐºÐ»Ð°ÐŽ Ð²ÐœÐµÑÐ»Ðž David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, Ðž Stuart Yeates. ÐÑÑÐ°Ð»ÑÐœÑÐµ ÑÐ»ÐµÐœÑ ÐÑÐŸÐµÐºÑÐ° ÐÐŸÐ²ÐŸÐ·ÐµÐ»Ð°ÐœÐŽÑÐºÐŸÐ¹ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐžÂ  ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°Ð»Ðž Ð²ÐŽÐŸÑ
+ÐœÐŸÐ²ÐµÐœÐœÑÐ¹ ÐŽÐžÐ·Ð°Ð¹Ðœ Ð²ÑÐµÐ¹ ÑÐžÑÑÐµÐŒÑ: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols Ðž Lloyd Smith. ÐÑ ÑÐ°ÐºÐ¶Ðµ Ð²ÑÑÐ°Ð¶Ð°ÐµÐŒ ÑÐ²ÐŸÑ Ð¿ÑÐžÐ·ÐœÐ°ÑÐµÐ»ÑÐœÐŸÑÑÑ Ð²ÑÐµÐŒ ÑÐµÐŒ, ÐºÑÐŸ ÑÑÑÐŽÐžÐ»ÑÑ ÐœÐ°ÐŽ ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµÐŒ Ð¿Ð°ÐºÐµÑÐŸÐ², Ð¿ÐŸÐ¿Ð°ÐŽÐ°ÑÑÐžÑ
+ Ð¿ÐŸÐŽ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð»ÐžÑÐµÐœÐ·ÐžÐžÂ  GNU, Ðž Ð²ÐºÐ»ÑÑÐµÐœÐœÑÑ
+ Ð² ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE Ðž XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="introduction">
+<Title>
+<Text id="22">ÐÐ²ÐµÐŽÐµÐœÐžÐµ</Text>
+</Title>
+<Content>
+<Text id="23">ÐÐŽÐœÐ° ÐžÐ· ÑÐµÐ»ÐµÐ¹ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ Greenstone ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ Ð¿ÑÐµÐŽÑÑÐ°Ð²ÐžÑÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒ ÐžÐœÑÑÐžÑÑÑÐ°ÐŒ, ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑÐŒ, Ð°Ð³ÐµÐœÑÑÑÐ²Ð°ÐŒ ÐÐÐ, ÐœÐµÐ¿ÑÐ°Ð²ÐžÑÐµÐ»ÑÑÑÐ²ÐµÐœÐœÑÐŒ Ðž ÐœÐµÐºÐŸÐŒÐŒÐµÑÑÐµÑÐºÐžÐŒ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑÐŒ, Ð° ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐ°Ð²ÐžÑÐµÐ»ÑÑÑÐ²Ð°ÐŒ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ¶ÐœÐŸ ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐžÑÑ ÐºÐ°Ðº Ð² ÐÐœÑÐµÑÐœÐµÑÐµ, ÑÐ°Ðº Ðž ÑÐŸÑ
+ÑÐ°ÐœÐžÑÑ ÐœÐ° CD-ROM.</Text>
+<Text id="24">ÐÐžÐ¶Ðµ ÐŸÐ¿ÐžÑÐ°ÐœÐ° ÐŸÐ±ÑÑÐœÐ°Ñ Ð¿ÑÐŸÑÐµÐŽÑÑÐ° Ð¿ÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹: </Text>
+<NumberedList>
+<NumberedItem>
+<Text id="25">ÐÐŸÐŽÐ±ÐŸÑ ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="26">ÐÐŸÐ»ÑÑÐµÐœÐžÐµ ÑÐ°Ð·ÑÐµÑÐµÐœÐžÑ Ð²Ð»Ð°ÐŽÐµÐ»ÑÑÐµÐ² Ð°Ð²ÑÐŸÑÑÐºÐžÑ
+ Ð¿ÑÐ°Ð² ÐœÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÑÑÐžÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="27">Ð¡ÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ðž ÐŸÐ¿ÑÐžÑÐµÑÐºÐŸÐµ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐœÐžÐµ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² (ÐÐ Ð¡) ÐŒÐ°ÑÐµÑÐžÐ°Ð»ÑÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐŽÐ»Ñ ÐžÑ
+ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ Ð² ÑÐžÑÑÐŸÐ²ÐŸÐ¹ ÑÐŸÑÐŒÐ°Ñ</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="28">ÐÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÐµ Ð²ÑÐµÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÐµÐŽÐžÐœÑÐ¹ ÑÐŸÑÐŒÐ°Ñ, ÐºÐŸÑÐŸÑÑÐ¹ ÐŒÐŸÐ¶ÐœÐŸ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ Ð² Greenstone (Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÐŸ HTML Ðž Microsoft Word, ÐœÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÑÐ°ÐºÐ¶Ðµ Ðž Ð² ÐŽÑÑÐ³ÐžÐµ ÑÐŸÑÐŒÐ°ÑÑ) Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÐ¹ Ðº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ "plugin" (ÑÐŒÐŸÑÑÐžÑÐµ ÐÐœÑÑÑÑÐºÑÐžÑ ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ).</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="29">ÐÐ°ÑÐºÐžÑÐŸÐ²ÐºÐ° Ð³Ð»Ð°Ð², Ð¿Ð°ÑÐ°Ð³ÑÐ°ÑÐŸÐ² Ðž ÑÐžÑÑÐœÐºÐŸÐ² Ð² ÑÐžÑÑÐŸÐ²ÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°Ñ
+.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="30">ÐÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð² ÐŸÐ¿ÑÐžÐŒÐ°Ð»ÑÐœÐŸ ÑÑÑÑÐºÑÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÑ ÑÐžÑÑÐŸÐ²ÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="31">ÐÐŸÑÑÑÐŸÐµÐœÐžÐµ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="32">ÐÐ°Ð¿ÐžÑÑ Ðž ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐœÐ° CD-ROM Ðž/ÐžÐ»Ðž ÐžÑ
+ Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÑ Ð² ÐÐœÑÐµÑÐœÐµÑÐµ.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="33">ÐÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÑÐŸÐ·ÐŽÐ°ÑÑ ÑÐžÑÑÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, Ð²ÑÐµ Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐž ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸ ÐœÑÐ¶ÐœÐŸ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÑÑ Ð² ÑÐžÑÑÐŸÐ²ÐŸÐ¹ ÑÐŸÑÐŒÐ°Ñ. ÐÑÐ»Ðž ÐŽÐŸÑÑÑÐ¿ÐœÑ ÑÐŸÐ»ÑÐºÐŸ ÑÐ²ÐµÑÐŽÑÐµ ÐºÐŸÐ¿ÐžÐž ÐºÐœÐžÐ³, ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÑÐŸ ÐžÑ
+ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ Ðž Ð¿ÐµÑÐµÐ²ÐµÑÑÐž Ð² ÑÐŸÑÐŒÑ, ÑÑÐžÑÑÐ²Ð°ÐµÐŒÑÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐŸÐŒ (Ñ ÑÐ°Ð³). ÐÐ±ÑÑÐœÐŸ ÑÑÐŸ ÐŽÐµÐ»Ð°ÐµÑÑÑ Ð¿ÑÑÐµÐŒ Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐžÑ ÐŸÐ¿ÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐœÐžÑ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ², Ð² ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÑÐ»ÑÑÐ°ÑÑ
+ - Ð¿ÑÐŸÑÑÑÐŒ Ð¿ÐµÑÐµÐ¿ÐµÑÐ°ÑÑÐ²Ð°ÐœÐžÐµÐŒ. Ð­ÑÐŸÑ Ð¿ÑÐŸÑÐµÑÑ ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÐµÑÑÑ Ð² 2-4 Ð³Ð»Ð°Ð²Ð°Ñ
+.</Text>
+<Text id="34">v. ÑÐ°Ð³ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð²ÑÐ±ÐžÑÐ°ÑÑ ÐŸÑÐŽÐµÐ»ÑÐœÑÐµ ÑÐ°ÑÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ðž ÑÐ°ÑÐ¿ÐŸÐ»Ð°Ð³Ð°ÑÑ ÐžÑ
+ Ð² ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ Ð² Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐµ, vi ÑÐ°Ð³ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð² ÑÐµÐ±Ñ Ð¿ÑÐžÑÐ²ÐŸÐµÐœÐžÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ Ð°ÑÑÐžÐ±ÑÑÐŸÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ, ÑÐ°ÐºÐžÑ
+ ÐºÐ°Ðº ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ðž ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹, ÐºÐ»ÑÑÐµÐ²ÑÐµ ÑÐ»ÐŸÐ²Ð° Ðž Ð±ÐžÐ±Ð»ÐžÐŸÐ³ÑÐ°ÑÐžÑÐµÑÐºÐžÐµ ÐŽÐ°ÐœÐœÑÐµ ÐŽÐ»Ñ ÐŸÑÑÑÐµÑÑÐ²Ð»ÐµÐœÐžÑ Ð·Ð°Ð¿ÑÐŸÑÐ° Ðž Ð¿ÐŸÐžÑÐºÐ° Ð¿ÐŸ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐµ. Ð­ÑÐž ÑÐ°Ð³Ðž ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑÑÑ Ð² Ð¿ÑÑÐŸÐ¹ Ð³Ð»Ð°Ð²Ðµ.</Text>
+<Text id="35">Ð­ÑÐ° ÐžÐœÑÑÑÑÐºÑÐžÑ ÑÐ°ÐºÐ¶Ðµ ÐŸÐ±ÑÑÐ¶ÐŽÐ°ÐµÑ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ Ð²ÐŸÐ¿ÑÐŸÑÐŸÐ², ÐºÐ°ÑÐ°ÑÑÐžÑ
+ÑÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð¿ÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÑÐžÑÑÐŸÐ²ÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐžÐ· ÑÐ²ÐµÑÐŽÐŸÐ¹ ÐºÐŸÐ¿ÐžÐž. ÐÐµÑÐµÐŽ ÑÐµÐŒ, ÐºÐ°Ðº Ð¿ÑÐŸÐŽÐŸÐ»Ð¶ÐžÑÑ ÑÑÐµÐœÐžÐµ, ÐŒÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ Ð²Ð°ÐŒ ÐŸÑÐ²ÐµÑÐžÑÑ ÐœÐ° ÑÐ»ÐµÐŽÑÑÑÐžÐµ Ð²ÐŸÐ¿ÑÐŸÑÑ:</Text>
+<BulletList>
+<Bullet>
+<Text id="36">ÐÐ°ÐºÐŸÐ²Ð° ÑÐµÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ð²Ð°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž?</Text>
+</Bullet>
+<Bullet>
+<Text id="37">ÐÐ° ÐºÐ°ÐºÑÑ Ð³ÑÑÐ¿Ð¿Ñ Ð»ÑÐŽÐµÐ¹ ÐŸÐœÐ° ÐŸÑÐžÐµÐœÑÐžÑÐŸÐ²Ð°ÐœÐ°?</Text>
+</Bullet>
+<Bullet>
+<Text id="38">ÐÐ°ÑÐºÐŸÐ»ÑÐºÐŸ ÐŸÐœÐ° ÐŒÐ°ÑÑÑÐ°Ð±ÐœÐ° â Ð»ÐŸÐºÐ°Ð»ÑÐœÐ°, ÑÐµÐ³ÐžÐŸÐœÐ°Ð»ÑÐœÐ° ÐžÐ»Ðž Ð³Ð»ÐŸÐ±Ð°Ð»ÑÐœÐ°?</Text>
+</Bullet>
+<Bullet>
+<Text id="39">Ð¡ÐºÐŸÐ»ÑÐºÐŸ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²?</Text>
+</Bullet>
+<Bullet>
+<Text id="40">Ð¡ÐºÐŸÐ»ÑÐºÐŸ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÑÑÐ°ÐœÐžÑ?</Text>
+</Bullet>
+<Bullet>
+<Text id="41">Ð¡ÐºÐŸÐ»ÑÐºÐŸ ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð³ÑÐ°ÑÐžÑÐµÑÐºÐžÑ
+ ÐŸÐ±ÑÐµÐºÑÐŸÐ²?</Text>
+</Bullet>
+<Bullet>
+<Text id="42">ÐÐŒÐµÐµÑ Ð»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐ°ÑÑÐž, Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐµ ÐŽÐ»Ñ ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÐœÐŸÐ³ÐŸ ÐºÑÑÐ³Ð° Ð»ÑÐŽÐµÐ¹, Ð° ÐŽÑÑÐ³ÐžÐµ - ÐŽÐ»Ñ Ð²ÑÐµÑ
+ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹?</Text>
+</Bullet>
+<Bullet>
+<Text id="43">ÐÐŸÑÑÑÐ¿ÐœÑ Ð»Ðž ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐŒ ÑÐŸÑÐŒÐ°ÑÐµ?</Text>
+</Bullet>
+<Bullet>
+<Text id="44">ÐÑÐ»Ðž ÐŽÐ°, ÑÐŸ Ð² ÐºÐ°ÐºÐŸÐŒ? (ÐœÑÐ¶ÐœÐŸ ÐŸÑÐŒÐµÑÐžÑÑ, ÑÑÐŸ PDF-ÑÐ°Ð¹Ð»Ñ ÐœÐµ ÑÐ²Ð»ÑÑÑÑÑ ÑÐºÐ²ÐžÐ²Ð°Ð»ÐµÐœÑÐ°ÐŒÐž Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÐŸÐ³ÐŸ ÑÐžÑÑÐŸÐ²ÐŸÐ³ÐŸ ÑÐŸÑÐŒÐ°ÑÐ°, ÑÐ°Ðº ÐºÐ°Ðº ÑÐ²Ð»ÑÑÑÑÑ Ð»ÐžÑÑ ÐºÐŸÐ¿ÐžÑÐŒÐž ÑÑÑÐ°ÐœÐžÑ)</Text>
+</Bullet>
+<Bullet>
+<Text id="45">ÐÐ°ÐºÐŸÐ² ÑÑÐ°ÑÑÑ Ð°Ð²ÑÐŸÑÑÐºÐžÑ
+ Ð¿ÑÐ°Ð² ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²?</Text>
+</Bullet>
+<Bullet>
+<Text id="46">ÐÑÐŸ Ð²Ð»Ð°ÐŽÐµÐµÑ Ð°Ð²ÑÐŸÑÑÐºÐžÐŒÐž Ð¿ÑÐ°Ð²Ð°ÐŒÐž?</Text>
+</Bullet>
+<Bullet>
+<Text id="47">Ð¡ÑÑÐµÑÑÐ²ÑÑÑ Ð»Ðž ÐŽÑÑÐ³ÐžÐµ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž, ÑÐ°ÑÐ¿ÐŸÐ»Ð°Ð³Ð°ÑÑÐžÐµ Ð¿ÑÐŸÐŽÑÐºÑÐŸÐŒ, ÐŸÑÐžÐµÐœÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐŒ ÐœÐ° ÑÑ Ð¶Ðµ ÑÐ°ÐŒÑÑ Ð³ÑÑÐ¿Ð¿Ñ Ð»ÑÐŽÐµÐ¹?</Text>
+</Bullet>
+<Bullet>
+<Text id="48">ÐÐµÐ»Ð°ÐµÑÐµ Ð»Ðž Ð²Ñ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ð²ÐŒÐµÑÑÐµ Ñ ÐŽÑÑÐ³ÐžÐŒÐž Ð³ÑÑÐ¿Ð¿Ð°ÐŒÐž?</Text>
+</Bullet>
+<Bullet>
+<Text id="49">ÐÐ°ÐºÐŸÐ² Ð±ÑÐŽÐ¶ÐµÑ, Ð²ÑÐŽÐµÐ»ÐµÐœÐœÑÐ¹ ÐœÐ° ÑÑÐŸÑ Ð¿ÑÐŸÐµÐºÑ?</Text>
+</Bullet>
+<Bullet>
+<Text id="50">ÐÐ°ÐºÐžÐµ ÐŽÐŸÑÑÑÐ¿ÐœÑ ÑÐµÐ»ÐŸÐ²ÐµÑÐµÑÐºÐžÐµ ÑÐµÑÑÑÑÑ(Ð² ÑÐµÐ»ÐŸÐ²ÐµÐºÐŸ-ÐŒÐµÑÑÑÐ°Ñ
+) ÐŽÐ»Ñ ÐºÐŸÐŸÑÐŽÐžÐœÐ°ÑÐžÐž, ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ?</Text>
+</Bullet>
+<Bullet>
+<Text id="51">Ð¡ÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÑÑÑÐ¿ÐœÐŸ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐŸÐ²?</Text>
+</Bullet>
+<Bullet>
+<Text id="52">Ð¡ÐºÐŸÐ»ÑÐºÐŸ CD-ROM Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ ÑÐŸÐ·ÐŽÐ°ÑÑ?</Text>
+</Bullet>
+<Bullet>
+<Text id="53">ÐÑÐŽÑÑ Ð»Ðž ÐŸÐœÐž Ð±ÐµÑÐ¿Ð»Ð°ÑÐœÑÐŒÐž ÐžÐ»Ðž Ð¿Ð»Ð°ÑÐœÑÐŒÐž?</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Chapter>
+<Chapter id="scanners_and_scanning">
+<Title>
+<Text id="54">Ð¡ÐºÐ°ÐœÐµÑÑ Ðž ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</Title>
+<Content>
+<Text id="55">ÐÐµÑÐ²ÑÐ¹ ÑÐ°Ð³ ÐŽÐ»Ñ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ Ð±ÑÐŒÐ°Ð¶ÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÑÐžÑÑÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐž Ð²ÑÐµÑ
+ ÑÑÑÐ°ÐœÐžÑ ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². Ð¡Ð»ÐµÐŽÑÑÑÐžÐ¹ ÑÐ°Ð³ - ÑÑÐŸ Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐžÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÐŸÐ¿ÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐœÐžÑ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² (ÐÐ Ð¡), ÐŽÐ»Ñ ÑÐµÐ³ÐŸ ÐŸÑÐµÐœÑ Ð²Ð°Ð¶ÐœÑ Ð²ÑÑÐŸÐºÐŸÐºÐ°ÑÐµÑÑÐ²ÐµÐœÐœÑÐµ Ðž ÑÐµÑÐºÐžÐµ ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ. ÐÑÐŸÑÐµÑÑ Ð¿ÐµÑÐµÐ²ÐŸÐŽÐ° Ð² ÑÐžÑÑÐŸÐ²ÐŸÐ¹ ÑÐŸÑÐŒÐ°Ñ ÐœÑÐ¶ÐŽÐ°ÐµÑÑÑ Ð² ÑÐºÐ°ÐœÐµÑÐµ, ÑÐ¿ÐŸÑÐŸÐ±ÐœÐŸÐŒ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ð¿ÑÐž ÑÐ°Ð·ÑÐµÑÐµÐœÐžÐž 300 dpi (ÑÐŸÑÐµÐº ÐœÐ° ÐŽÑÐ¹ÐŒ). ÐÐŸÐ»ÑÑÑÑ ÑÐ°ÑÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÑÐŸÐžÐ·Ð²ÐµÑÑÐž Ð² ÑÐµÑÐœÐŸ-Ð±ÐµÐ»ÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ, ÐœÐŸ Ð¿ÑÐž Ð²ÐºÐ»ÑÑÐµÐœÐžÐž ÑÐ²ÐµÑÐœÑÑ
+ ÐžÐ»Ð»ÑÑÑÑÐ°ÑÐžÐ¹ ÐžÑ
+ ÑÐ»ÐµÐŽÑÐµÑ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ ÑÐ²ÐµÑÐœÑÐŒ ÑÐºÐ°ÐœÐµÑÐŸÐŒ. Ð Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²Ðµ ÑÐ»ÑÑÐ°ÐµÐ² ÐŸÐ±Ð»ÐŸÐ¶ÐºÐž ÐºÐœÐžÐ³ ÑÐ²Ð»ÑÑÑÑÑ ÐºÑÐ°ÑÐŸÑÐœÑÐŒÐž Ðž ÐžÑ
+ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ Ð² ÑÐµÐ¶ÐžÐŒÐµ ÑÐ²ÐµÑÐœÐŸÐ³ÐŸ ÑÐžÑÑÐœÐºÐ°.</Text>
+<Section id="scanners">
+<Title>
+<Text id="56">Ð¡ÐºÐ°ÐœÐµÑÑ</Text>
+</Title>
+<Content>
+<Text id="57">Ð¡ÐºÐ°ÐœÐµÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑ Ð¿ÐŸ ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒ ÑÐµÐœÐ°ÐŒ Ðž ÐžÐŒÐµÑÑÑÑ Ð²ÑÐµÐ²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÑ
+ ÑÐ°Ð·ÐŒÐµÑÐŸÐ² Ðž ÑÐŸÑÐŒ. ÐÑ
+ ÑÐµÐœÐ° ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐŸÑ $ 100 Ð·Ð° ÐŸÐ±ÑÑÐœÑÐ¹ ÐœÐ°ÑÑÐŸÐ»ÑÐœÑÐ¹ ÑÐºÐ°ÐœÐµÑ ÐŽÐŸ $50000 Ð·Ð° ÐŸÐ³ÑÐŸÐŒÐœÑÐµ ÐžÐœÐŽÑÑÑÑÐžÐ°Ð»ÑÐœÑÐµ ÑÐºÐ°ÐœÐµÑÑ ÑÐ°ÐºÐžÑ
+ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÐµÐ¹ ÐºÐ°Ðº Bell &amp; Howell<FootnoteRef id="1"/>. Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐŒÐœÐŸÐ³ÐŸ ÑÐ°Ð·ÐœÑÑ
+ ÑÐŸÑÐ³ÐŸÐ²ÑÑ
+ ÐÐœÑÐµÑÐœÐµÑ-ÑÑÑÐ°ÐœÐžÑ, Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÑÑÐžÑ
+ Ð²ÑÐµÐ²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÐµ ÑÐºÐ°ÐœÐµÑÑ. ÐÐ»Ñ Ð¿ÐŸÐžÑÐºÐ° ÑÐºÐ°ÐœÐµÑÐŸÐ² Ð¿ÑÐŸÑÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÑÐ°ÐºÐžÐµ Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÐµ ÑÐžÑÑÐµÐŒÑ, ÐºÐ°Ðº Google, Altavista, Yahoo.</Text>
+<Text id="58">ÐÐ±ÑÑÐœÑÐ¹ ÑÐŸÑÐŒÐ°Ñ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑÑÑ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ, ÑÑÐŸ TIFF ÐžÐ»Ðž BMP (Bitmap image). Ð¡Ð¶Ð°ÑÐ°Ñ ÑÐŸÑÐŒÐ° TIFF IV ÑÐ²Ð»ÑÐµÑÑÑ Ð»ÑÑÑÐžÐŒ ÑÐŸÑÐŒÐ°ÑÐŸÐŒ ÐŽÐ»Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ. Ð¡ÑÐµÐŽÐœÑÑ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐœÐ°Ñ ÑÑÑÐ°ÐœÐžÑÐ°, Ð¿ÐµÑÐµÐ²ÐµÐŽÐµÐœÐœÐ°Ñ Ð² ÑÑÐŸÑ ÑÐŸÑÐŒÐ°Ñ, Ð·Ð°ÐœÐžÐŒÐ°ÐµÑ Ð²ÑÐµÐ³ÐŸ 50 ÐºÐžÐ»ÐŸÐ±Ð°Ð¹Ñ, Ð¿ÐŸ ÑÑÐ°Ð²ÐœÐµÐœÐžÑ Ñ 2 Mb ÐžÐŽÐµÐœÑÐžÑÐœÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ, ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÐŸÐ¹ Ð² BMP.</Text>
+<Subsection id="low-cost_flat-bed_scanner)">
+<Title>
+<Text id="59">ÐÐµÐŽÐŸÑÐŸÐ³ÐžÐµ ÐœÐ°ÑÑÐŸÐ»ÑÐœÑÐµ ÑÐºÐ°ÐœÐµÑÑ (flat-based scanners)</Text>
+</Title>
+<Content>
+<Text id="60">ÐÐ°ÑÑÐŸÐ»ÑÐœÑÐµ ÑÐºÐ°ÐœÐµÑÑ ÑÐ²Ð»ÑÑÑÑÑ ÑÐ°ÐŒÑÐŒÐž ÐŽÐµÑÐµÐ²ÑÐŒÐž Ðž ÐœÐ°ÐžÐ±ÐŸÐ»ÐµÐµ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž ÑÐºÐ°ÐœÐµÑÐ°ÐŒÐž. Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐŒÐœÐŸÐ³ÐŸ ÑÐŸÑÐ³ÐŸÐ²ÑÑ
+ ÐŒÐ°ÑÐŸÐº, ÑÐ°ÐºÐžÑ
+ ÐºÐ°Ðº HP, Agfa, Acer Ðž Ñ.ÐŽ. ÐÑ
+ ÑÐµÐœÑ ÐºÐŸÐ»ÐµÐ±Ð»ÑÑÑÑ ÐŸÑ 100 ÐŽÐŸ 300 ÐŽÐŸÐ»Ð»Ð°ÑÐŸÐ². Ð¡ ÐžÑ
+ Ð¿ÐŸÐŒÐŸÑÑÑ ÐŒÐŸÐ¶ÐœÐŸ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ ÐºÐ°Ðº ÑÐµÑÐœÐŸ-Ð±ÐµÐ»ÑÐµ ÑÐžÑÑÐœÐºÐž, ÑÐ°Ðº Ðž ÑÐ²ÐµÑÐœÑÐµ. ÐÐžÐ·ÐºÐžÐµ ÑÐµÐœÑ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ ÐºÐ°Ð¶ÐŽÐŸÐŒÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐžÐŒÐµÑÑ ÐŸÐŽÐžÐœ ÐžÐ· ÑÐ°ÐºÐžÑ
+ ÑÐºÐ°ÐœÐœÐµÑÐŸÐ².</Text>
+<Text id="61">ÐÑ
+ ÐœÐµÐŽÐŸÑÑÐ°ÑÐºÐž - ÑÑÐŸ ÑÑÐµÐŽÐœÐžÐ¹ ÑÑÐŸÐ²ÐµÐœÑ ÐºÐ°ÑÐµÑÑÐ²Ð°, ÐŒÐµÐŽÐ»ÐµÐœÐœÐŸÐµ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ, ÐœÐµÐœÐ°ÐŽÐµÐ¶ÐœÐŸÑÑÑ Ð¿ÑÐž Ð²ÑÑÐŸÐºÐžÑ
+ ÑÐµÐŒÐ¿ÐµÑÐ°ÑÑÑÐ°Ñ
+ Ðž ÐŸÑÐœÐŸÑÐžÑÐµÐ»ÑÐœÐŸ ÑÐ°ÑÑÑÐµ Ð¿ÐŸÐ»ÐŸÐŒÐºÐž. Ð¡ÑÑÐ°ÐœÐžÑÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑÑÑ Ð²ÑÑÑÐœÑÑ Ðž ÐºÐ°Ð¶ÐŽÐ°Ñ ÐžÐ· ÑÑÑÐ°ÐœÐžÑ Ð¿ÐŸ ÐŸÑÐŽÐµÐ»ÑÐœÐŸÑÑÐž. ÐÐ°Ð¶ÐŽÑÑ ÑÑÑÐ°ÐœÐžÑÑ ÐœÑÐ¶ÐœÐŸ Ð¿ÐŸÐ»ÐŸÐ¶ÐžÑÑ ÑÐ°Ðº, ÑÑÐŸÐ±Ñ ÐŸÐœÐ° ÑÐ°ÑÐ¿ÐŸÐ»Ð°Ð³Ð°Ð»Ð°ÑÑ Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ. ÐÑÐŸÐŽÑÐºÑÐžÐ²ÐœÐŸÑÑÑ ÐœÐ° ÑÐ°ÐºÐžÑ
+ ÑÐºÐ°ÐœÐµÑÐ°Ñ
+ ÐŸÑÐµÐœÑ ÐœÐžÐ·ÐºÐ°. ÐÐµÑÐŒÐŸÑÑÑ ÐœÐ° ÑÐŸ, ÑÑÐŸ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»Ðž ÑÑÐ²ÐµÑÐ¶ÐŽÐ°ÑÑ, ÑÑÐŸ ÐŸÐŽÐœÑ ÑÑÑÐ°ÐœÐžÑÑ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ ÐŒÐµÐœÑÑÐµ, ÑÐµÐŒ Ð·Ð° ÐŸÐŽÐœÑ ÐŒÐžÐœÑÑÑ, ÐœÐ° Ð¿ÑÐ°ÐºÑÐžÐºÐµ ÑÑÑÐŽÐœÐŸ Ð¿ÑÐµÐŸÐŽÐŸÐ»ÐµÑÑ Ð³ÑÐ°ÐœÐžÑÑ Ð² 12 ÑÑÑÐ°ÐœÐžÑ Ð·Ð° ÑÐ°Ñ. Ð ÑÐŸÐŒÑ Ð¶Ðµ Ð¿ÑÐŸÑÐµÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð¿ÐŸÐ»ÐœÐŸÑÑÑÑ Ð·Ð°ÐœÐžÐŒÐ°ÐµÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐœÑÐµ ÑÐµÑÑÑÑÑ.</Text>
+<Text id="62">Ð¡Ð»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸ, ÑÐ°ÐºÐžÐµ ÑÐºÐ°ÐœÐµÑÑ ÑÐŽÐŸÐ±ÐœÑ ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ»Ñ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÐœÐµÐ±ÐŸÐ»ÑÑÐžÑ
+ ÑÐ°Ð±ÐŸÑ Ñ ÐœÐµÐ±ÐŸÐ»ÑÑÐžÐŒ ÐœÐ°Ð±ÐŸÑÐŸÐŒ ÑÑÑÐ°ÐœÐžÑ - ÐœÐµ Ð±ÐŸÐ»ÐµÐµ 200-400 Ð² ÐŒÐµÑÑÑ, ÐµÑÐ»Ðž Ð²ÑÐ¿ÐŸÐ»ÐœÑÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐµÐ³ÑÐ»ÑÑÐœÐŸ. Ð¢Ðµ, ÐºÑÐŸ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÑÐŸ ÑÐºÐ°ÐœÐµÑÐŸÐŒ Ð¿ÐŸÐ»ÐœÑÐ¹ ÐŽÐµÐœÑ, ÑÑÐŸ ÑÐŸÑÑÐ°Ð²Ð»ÑÐµÑ 1000-2000 ÑÑÑÐ°ÐœÐžÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="low-end_scanner_with_sheet_feeder">
+<Title>
+<Text id="63">Ð¡ÐºÐ°ÐœÐµÑÑ Ñ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐŸÐ¹ Ð¿ÐŸÐŽÐ°ÑÐµÐ¹ Ð±ÑÐŒÐ°Ð³Ðž</Text>
+</Title>
+<Content>
+<Text id="64">Ð¡ÐºÐ°ÐœÐµÑÑ Ñ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐŸÐ¹ Ð¿ÐŸÐŽÐ°ÑÐµÐ¹ Ð±ÑÐŒÐ°Ð³Ðž ÑÑÐŸÑÑ ÐŸÐºÐŸÐ»ÐŸ 500-1200 ÐŽÐŸÐ»Ð»Ð°ÑÐŸÐ². ÐÐŸÐ¶ÐœÐŸ Ð¿ÐŸÐŒÐµÑÐ°ÑÑ ÐŽÐŸ 10-15 ÑÑÑÐ°ÐœÐžÑ Ð² ÑÐºÐ°ÐœÐµÑ Ðž ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ ÐžÑ
+ ÐŸÐŽÐœÐŸÐ²ÑÐµÐŒÐµÐœÐœÐŸ: ÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸ, ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÑ ÐœÐµ ÐœÑÐ¶ÐœÐŸ Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸ Ð¿ÐŸÐŽÑ
+ÐŸÐŽÐžÑÑ Ðº Ð°Ð¿Ð¿Ð°ÑÐ°ÑÑ. Ð­ÑÐŸ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÑÐ²ÐµÐ»ÐžÑÐžÑÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÑÐœÐŸÑÑÑ ÐŽÐŸ 150-200 ÑÑÑÐ°ÐœÐžÑ Ð² ÐŽÐµÐœÑ. Ð­ÑÐž ÑÐºÐ°ÐœÐµÑÑ ÐœÐ°ÐžÐ±ÐŸÐ»ÐµÐµ ÑÑÐŸÐ¹ÐºÐžÐµ Ðž ÐœÐµ ÐœÑÐ¶ÐŽÐ°ÑÑÑÑ Ð² ÑÐµÐŒÐŸÐœÑÐµ Ð² ÑÐµÑÐµÐœÐžÐµ ÐŽÐŸÐ»Ð³ÐŸÐ³ÐŸ Ð²ÑÐµÐŒÐµÐœÐž (Ð¿ÐŸÑÐ»Ðµ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ 30000-50000 ÑÑÑÐ°ÐœÐžÑ).</Text>
+<Text id="65">ÐÑ
+ ÐœÐµÐŽÐŸÑÑÐ°ÑÐŸÐº ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ ÑÐºÐ°ÐœÐžÑÑÐµÑÑÑ ÑÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐœÐ° ÑÑÐŸÑÐŸÐœÐ° ÑÑÑÐ°ÐœÐžÑÑ; ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ ÐŽÑÑÐ³ÑÑ ÑÑÐŸÑÐŸÐœÑ, ÑÑÑÐ°ÐœÐžÑÑ ÐœÑÐ¶ÐœÐŸ Ð¿ÐµÑÐµÐ²ÐµÑÐœÑÑÑ. Ð­ÑÐŸ ÑÐ°ÑÑÐŸ ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ, ÑÐ°Ðº ÐºÐ°Ðº Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐ°Ñ Ð¿ÐŸÐŽÐ°ÑÐ° Ð±ÑÐŒÐ°Ð³ Ð²ÑÐµÐ³ÐŽÐ° Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ°ÑÐžÑÐœÐ° Ðž ÑÐ°ÑÑÐŸ ÑÑÑÐ°ÐœÐžÑÑ Ð·Ð°ÑÑÑÐµÐ²Ð°ÑÑ.</Text>
+<Text id="66">Ð­ÑÐž ÑÐºÐ°ÐœÐµÑÑ ÑÐŽÐŸÐ±ÐœÑ ÐŽÐ»Ñ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž 1500-3000 ÑÑÑÐ°ÐœÐžÑ Ð² ÐŒÐµÑÑÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="color_scanners">
+<Title>
+<Text id="67">ÐŠÐ²ÐµÑÐœÑÐµ ÑÐºÐ°ÐœÐµÑÑ</Text>
+</Title>
+<Content>
+<Text id="68">ÐÑÐ±Ð°Ñ ÐŸÐ¿ÐµÑÐ°ÑÐžÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÑÐ°Ð»ÐºÐžÐ²Ð°ÐµÑÑÑ Ñ ÑÐ²ÐµÑÐœÑÐŒÐž ÑÐžÑÑÐœÐºÐ°ÐŒÐž, Ð¿ÐŸÑÑÐŸÐŒÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐœÐ°Ð³ÐŸÑÐŸÐ²Ðµ ÐžÐŒÐµÑÑ ÑÐ²ÐµÑÐœÐŸÐ¹ ÑÐºÐ°ÐœÐµÑ. ÐÐ±ÑÑÐœÐŸ ÐŒÐµÐœÐµÐµ 5% Ð»ÑÐ±ÐŸÐ¹ Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐž ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐºÐ°ÐºÐžÐµ-Ð»ÐžÐ±ÐŸ ÑÐ²ÐµÑÐœÑÐµ ÑÐžÑÑÐœÐºÐž, Ð²ÐºÐ»ÑÑÐ°Ñ ÐŸÐ±Ð»ÐŸÐ¶ÐºÑ. ÐÐŸÑÑÐŸÐŒÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÑÑÑ ÐžÐŒÐµÑÑ ÐŽÐµÑÐµÐ²ÑÐ¹ ÑÐ²ÐµÑÐœÐŸÐ¹ ÐœÐ°ÑÑÐŸÐ»ÑÐœÑÐ¹ ÑÐºÐ°ÐœÐµÑ. Ð ÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÑÑÑ ÐžÐŒÐµÑÑ ÑÐºÐ°ÐœÐµÑ Ñ ÑÐ°Ð·ÑÐµÑÐµÐœÐžÐµÐŒ ÐœÐµ ÐŒÐµÐœÐµÐµ 600 dpi.</Text>
+</Content>
+</Subsection>
+<Subsection id="professional_duplex_scanners">
+<Title>
+<Text id="69">ÐÑÐŸÑÐµÑÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐµ ÐŽÑÐ¿Ð»ÐµÐºÑÐœÑÐµ ÑÐºÐ°ÐœÐµÑÑ</Text>
+</Title>
+<Content>
+<Text id="70">ÐÑÐŸÑÐµÑÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐµ ÑÐºÐ°ÐœÐµÑÑ ÐœÐ°ÐŽÐµÐ¶ÐœÑ, Ð¿ÑÐŸÑÐœÑ Ðž ÑÐ¿ÐŸÑÐŸÐ±ÐœÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ ÐŸÐºÐŸÐ»ÐŸ 2000-10000 ÑÑÑÐ°ÐœÐžÑ Ð² ÐŽÐµÐœÑ. ÐÐœÐž ÐžÐŒÐµÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÑÑ ÑÐžÑÑÐµÐŒÑ Ð¿ÐŸÐŽÐ°ÑÐž Ð±ÑÐŒÐ°Ð³Ðž, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÑÑÐŸÐ¿ÐºÐž Ð² 50-200 ÑÑÑÐ°ÐœÐžÑ. Ð¡Ð°ÐŒÑÐµ Ð»ÑÑÑÐžÐµ Ðž Ð±ÑÑÑÑÑÐµ ÑÐºÐ°ÐœÐµÑÑ - ÑÑÐŸ ÐŽÑÐ¿Ð»ÐµÐºÑÐœÑÐµ ÑÐºÐ°ÐœÐµÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÑÐºÐ°ÐœÐžÑÑÑÑ ÐŸÐ±Ðµ ÑÑÐŸÑÐŸÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐŸÐŽÐœÐŸÐ²ÑÐµÐŒÐµÐœÐœÐŸ.</Text>
+<Text id="71">Ð­ÑÐž ÑÐºÐ°ÐœÐµÑÑ ÐœÑÐ¶ÐŽÐ°ÑÑÑÑ Ð² ÐŒÐŸÑÐœÐŸÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ Ñ Ð¶ÐµÑÑÐºÐžÐŒ ÐŽÐžÑÐºÐŸÐŒ ÐºÐ°Ðº ÐŒÐžÐœÐžÐŒÑÐŒ ÐœÐ° 10-20 Gb. ÐÑ
+ ÑÐµÐœÑ Ð³ÑÐ°ÐœÐžÑÐ°Ñ ÐŸÑ $5000 ÐŽÐŸ $50000. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŽÑÐ¿Ð»ÐµÐºÑÐœÑÐ¹ ÑÐºÐ°ÐœÐœÐµÑ Canon DR-6020 ÑÑÐŸÐžÑ 5000 ÐŽÐŸÐ»Ð»Ð°ÑÐŸÐ² Ðž ÐŒÐŸÐ¶ÐµÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ ÐŽÐ²ÑÑ
+ÑÑÐŸÑÐŸÐœÐœÐžÐŒÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒÐž. ÐÐœ ÑÐ¿ÐŸÑÐŸÐ±ÐµÐœ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ ÐŽÐŸ 2000 Ð² ÐŽÐµÐœÑ Ðž ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÑÐ°Ð±ÐŸÑÐµÐŒ ÑÐŸÑÑÐŸÑÐœÐžÐž ÐŽÐŸ 600000-800000 ÑÑÑÐ°ÐœÐžÑ. Ð¡ÐºÐ°ÐœÐµÑÑ Bell&amp;Howell and Fujitsu ÑÑÐŸÑÑ ÐŸÑ 10000-50000 ÐŽÐŸÐ»Ð»Ð°ÑÐŸÐ² Ðž ÐŒÐŸÐ³ÑÑ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐŒÐžÐ»Ð»ÐžÐŸÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐŽÐŸ Ð¿ÐµÑÐ²ÐŸÐ³ÐŸ ÑÐµÐŒÐŸÐœÑÐ°.</Text>
+<Text id="72">Ð¡ÐºÐ°ÐœÐµÑÑ Micro-fische ÑÑÐŸÑÑ ÐŸÑ $15000 Ð·Ð° Ð¿ÐŸÐ»ÑÐ°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐžÐ¹ ÐœÐ°Ð±ÐŸÑ ÐŽÐŸ $80000, ÑÐ°Ð±ÐŸÑÐ°ÑÑÐžÐ¹ Ð¿ÐŸÐ»ÐœÐŸÑÑÑÑ Ð² Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ.</Text>
+</Content>
+</Subsection>
+<Subsection id="scanning_programs">
+<Title>
+<Text id="73">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŽÐ»Ñ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="74">ÐÐ°Ð¶ÐŽÑÐ¹ ÑÐºÐ°ÐœÐµÑ ÐžÐŒÐµÐµÑ ÑÐ²ÐŸÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ, Ð¿ÐŸÑÑÐŸÐŒÑ ÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÐœÐ° Ð²Ð°Ñ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑ. ÐÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐžÐŒÐµÑÑ computer card, ÐºÐŸÑÐŸÑÑÑ ÐœÑÐ¶ÐœÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÐŽÐ»Ñ ÑÑÐºÐŸÑÐµÐœÐžÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="preparing_the_documents">
+<Title>
+<Text id="75">ÐÐŸÐŽÐ³ÐŸÑÐŸÐ²ÐºÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="76">ÐÐŸÐºÑÐŒÐµÐœÑÑ ÐœÑÐ¶ÐœÐŸ Ð¿ÐŸÐŽÐ³ÐŸÑÐŸÐ²ÐžÑÑ Ð·Ð°ÑÐ°ÐœÐµÐµ ÐŽÐŸ ÐžÑ
+ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ. Ð¡ ÐœÐžÑ
+ ÐœÑÐ¶ÐœÐŸ ÑÑÑÑÑ
+ÐœÑÑÑ Ð¿ÑÐ»Ñ, Ð²ÑÑÑÑÐžÑÑ ÐŒÐŸÐºÑÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÑÐœÑÑÑ ÑÐºÑÐµÐ¿ÐºÐž Ðž ÑÐ°ÑÐ¿ÑÐ°Ð²ÐžÑÑ ÑÑÑÐ°ÐœÐžÑÑ.</Text>
+<Text id="77">ÐÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð°ÐºÐºÑÑÐ°ÑÐœÐŸ ÑÐœÑÑÑ ÑÑÐžÐ²ÐºÑ Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐºÐœÐžÐ³Ðž.</Text>
+<Text id="78">ÐÐœÐŸÐ³ÐžÐµ ÐºÐœÐžÐ³Ðž, ÐºÐŸÑÐŸÑÑÐµ Ð²Ñ Ð±ÑÐŽÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÐ»Ñ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð±ÑÐŽÐµÑ ÑÐœÐŸÐ²Ð° ÑÑÐžÑÑ, Ð¿ÐŸÑÑÐŸÐŒÑ Ð±ÑÐŽÑÑÐµ Ð²ÐœÐžÐŒÐ°ÑÐµÐ»ÑÐœÑ Ð¿ÑÐž ÑÐœÑÑÐžÐž ÑÑÐžÐ²ÐºÐž.</Text>
+<Text id="79">ÐÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐžÐŒÐµÑÑÐžÑ
+ ÐŸÐ±ÑÐµÐŒ Ð±ÐŸÐ»ÐµÐµ 20 ÑÑÑÐ°ÐœÐžÑ, ÐŒÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ Ð¿ÐŸÑÑÑÐžÑÑ Ð·Ð°ÐŽÐ°ÐœÐžÐµ ÐœÐ° ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐ¿ÐµÑÐžÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÐœÑÐŒ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑÐŒ, ÐžÐŒÐµÑÑÐžÐŒ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐµ ÐŸÐ±ÐŸÑÑÐŽÐŸÐ²Ð°ÐœÐžÐµ.</Text>
+</Content>
+</Section>
+<Section id="the_scanning_process">
+<Title>
+<Text id="80">ÐÑÐŸÑÐµÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ </Text>
+</Title>
+<Content>
+<Text id="81">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÐµÐŒÑÑ Ð²ÐŒÐµÑÑÐµ ÑÐŸ ÑÐºÐ°ÐœÐµÑÐŸÐŒ, Ð¿ÐŸÑÐ»Ðµ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð²Ñ Ð¿ÐŸÐ»ÑÑÐžÑÐµ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð² ÑÐŸÑÐŒÐ°ÑÐµ Bitmap ÐžÐ»Ðž TIFF. Ð­ÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐœÑÐ¶ÐœÐŸ ÑÐŸÑ
+ÑÐ°ÐœÐžÑÑ ÐœÐ° Ð¶ÐµÑÑÐºÐŸÐŒ ÐŽÐžÑÐºÐµ Ð¿ÐŸÐŽ Ð»ÑÐ±ÑÐŒ ÐžÐŒÐµÐœÐµÐŒ. The OCR process starts once some or all of a batch of documents have been scanned. It can be undertaken by the person who operates the scanner, or by someone else.</Text>
+<Text id="82">Typically a scanning resolution of 300 dpi is needed, although sometimes 200 dpi is acceptable.</Text>
+<Subsection id="quality_control">
+<Title>
+<Text id="83">ÐÐŸÐœÑÑÐŸÐ»Ñ ÐºÐ°ÑÐµÑÑÐ²Ð°</Text>
+</Title>
+<Content>
+<Text id="84">ÐÐŸÐœÐµÑÐœÐ°Ñ ÑÐµÐ»Ñ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ - ÑÑÐŸ Ð»ÐžÐ±ÐŸ Ð¿ÑÐŸÐ²ÐµÑÑÐž ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐµÑÐµÐ· Ð¿ÑÐŸÑÐµÑÑ ÐŸÐ¿ÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐœÐžÑ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² ÐÐ Ð¡ (optical character recognition) ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð² ÑÐŸÑÐŒÐ°ÑÐµ Word ÐžÐ»Ðž HTML, Ð»ÐžÐ±ÐŸ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÑÐŸÑÐŒÐ°ÑÐµ PDF. Ð Ð»ÑÐ±ÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐºÐ°ÑÐµÑÑÐ²ÐŸ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐŸÑÐµÐœÑ Ð²Ð°Ð¶ÐœÐŸ. ÐÑÐ»Ðž ÐºÐ°ÑÐµÑÑÐ²ÐŸ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÐœÐžÐ¶Ðµ ÑÑÐ°ÐœÐŽÐ°ÑÑÐ°, ÑÐŸ ÐŸÐœÐž Ð±ÑÐŽÑÑ Ð²ÑÐ³Ð»ÑÐŽÐµÑÑ ÑÐ°Ð·ÐŒÑÑÐŸ Ðž Ð·Ð°ÐœÐžÐŒÐ°ÑÑ Ð±ÐŸÐ»ÑÑÐµ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐœÐŸÐ¹ Ð¿Ð°ÐŒÑÑÐž. ÐÐ°ÑÐµÑÑÐ²ÐŸ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÐ°ÐºÐ¶Ðµ ÐŸÑÐµÐœÑ ÑÐžÐ»ÑÐœÐŸ Ð²Ð»ÐžÑÐµÑ ÐœÐ° Ð¿ÑÐŸÑÐµÑÑ ÐŸÐ¿ÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐœÐžÑ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² (ÐŽÐ°Ð»ÐµÐµ ÐÐ Ð¡). ÐÑÐž ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐœÐžÐ¶Ðµ ÐœÐŸÑÐŒÑ ÐµÐ³ÐŸ Ð¿ÑÐŸÐŽÑÐºÑÐžÐ²ÐœÐŸÑÑÑ Ð¿Ð°ÐŽÐ°ÐµÑ ÐœÐ° 40%. ÐÐ Ð¡, ÐºÐ°Ðº Ð¿ÑÐ°Ð²ÐžÐ»ÐŸ, ÑÐŸÑÑÐ°Ð²Ð»ÑÐµÑ 90% ÐŸÑ ÐŸÐ±ÑÐµÐ¹ ÑÑÐŸÐžÐŒÐŸÑÑÐž Ð²ÑÐµÐ³ÐŸ Ð¿ÑÐŸÑÐµÑÑÐ° Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ ÑÐ²ÐµÑÐŽÑÑ
+ ÐºÐŸÐ¿ÐžÐ¹ Ð² ÑÐžÑÑÐŸÐ²ÐŸÐ¹ ÑÐŸÑÐŒÐ°Ñ, Ð¿ÐŸÑÑÐŸÐŒÑ ÐºÐ°ÑÐµÑÑÐ²ÐŸ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŒÐŸÐ¶ÐµÑ ÐŸÑÐµÐœÑ ÑÐžÐ»ÑÐœÐŸ Ð¿ÐŸÐ²Ð»ÐžÑÑÑ ÐœÐ° ÐºÐŸÐœÐµÑÐœÑÐµ Ð·Ð°ÑÑÐ°ÑÑ.</Text>
+<Text id="85">ÐÐ°ÑÐµÑÑÐ²ÐŸ ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐŸÑÐŒÐ°ÑÐ° TIFF ÐŒÐŸÐ¶ÐœÐŸ ÑÐ»ÑÑÑÐžÑÑ Ð¿ÑÑÐµÐŒ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐžÐ¿Ð° Ð±ÑÐŒÐ°Ð³Ðž, ÐžÐ·ÐŒÐµÐœÑÑ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ. ÐÑÐœÐŸÑÐžÑÐµÐ»ÑÐœÐŸ ÑÐŸÐœÐºÐ°Ñ Ð±ÑÐŒÐ°Ð³Ð° Ð¿ÐŸÑÑÐµÐ±ÑÐµÑ ÐŽÑÑÐ³ÐžÑ
+ ÐœÐ°ÑÑÑÐŸÐµÐº, ÐœÐµÐ¶ÐµÐ»Ðž ÐŽÑÑÐ³Ð°Ñ: ÐºÐŸÐœÑÑÐ°ÑÑ ÐŽÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ ÐœÐ°ÑÑÑÐŸÐµÐœ Ð² Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÐºÐ°ÑÐµÑÑÐ²Ð° Ð¿ÐµÑÐ°ÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÐºÐŸÑÐŸÑÑÐ¹ Ð±ÑÐŽÐµÑ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°Ðœ , Ðž Ñ.ÐŽ.</Text>
+<Text id="86">ÐÐœÐ°ÑÐ°Ð»Ðµ ÑÐ°Ð·ÐŽÐµÐ»ÐžÑÐµ ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐŒÐ°ÑÐµÑÐžÐ°Ð» ÐœÐ° Ð³ÑÑÐ¿Ð¿Ñ ÑÐŸ ÑÑ
+ÐŸÐ¶ÐžÐŒ ÐºÐ°ÑÐµÑÑÐ²ÐŸÐŒ Ð±ÑÐŒÐ°Ð³Ðž Ðž ÑÑ
+ÐŸÐ¶ÐžÐŒ ÐºÐ°ÑÐµÑÑÐ²ÐŸÐŒ Ð¿ÐµÑÐ°ÑÐž. ÐÑÐŸÐ²ÐµÐŽÐžÑÐµ ÐžÑÐ¿ÑÑÐ°ÐœÐžÐµ ÐÐ Ð¡ ÐœÐ° ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÑÐºÐ·ÐµÐŒÐ¿Ð»ÑÑÐ°Ñ
+ Ð±ÑÐŒÐ°Ð³ ÐžÐ· Ð¿ÐµÑÐ²ÐŸÐ¹ Ð³ÑÑÐ¿Ð¿Ñ ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÐŸÐ¿ÑÐžÐŒÐ°Ð»ÑÐœÑÑ
+ ÐœÐ°ÑÑÑÐŸÐµÐº. ÐÐ°ÑÐµÐŒ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŒÐµÐ»ÐŸ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ Ð²ÐµÑÑ ÐŒÐ°ÑÐµÑÐžÐ°Ð» ÐžÐ· ÑÑÐŸÐ¹ Ð³ÑÑÐ¿Ð¿Ñ.</Text>
+</Content>
+</Subsection>
+<Subsection id="filename_conventions">
+<Title>
+<Text id="87">Ð ÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒÑÐµ Ð¿ÑÐ°Ð²ÐžÐ»Ð° ÐŽÐ»Ñ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="88">ÐÑÐžÑÐ²ÐŸÐ¹ÑÐµ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐºÐœÐžÐ³Ðµ ÐžÐ»Ðž ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐ²ÐŸÐ¹ ÐœÐŸÐŒÐµÑ ÐžÐ»Ðž ÐºÐŸÐŽ, ÐºÐŸÑÐŸÑÑÐ¹ ÑÑÐ°ÐœÐµÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµÐŒ Ð¿Ð°Ð¿ÐºÐž, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐµÐ¹ Ð²ÑÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ TIFF ÐžÐ· ÑÑÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ (DOS, Windows, UNIX, LINUX Ðž Ñ.ÐŽ.) ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŸÑ 8 ÐŽÐŸ 128 ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² Ð² ÐœÐ°Ð·Ð²Ð°ÐœÐžÐž ÑÐ°Ð¹Ð»Ð°. ÐÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ ÐœÐµ Ð¿ÑÐµÐ²ÑÑÐ°ÑÑ 8-16 ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ². ÐÐµÑÐ²ÑÐµ Ð¿ÑÑÑ Ð±ÑÐºÐ² ÐŒÐŸÐ³ÑÑ ÑÐžÐŒÐ²ÐŸÐ»ÐžÐ·ÐžÑÐŸÐ²Ð°ÑÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÑÐ»ÐµÐŽÑÑÑÐžÐµ Ð±ÑÐºÐ²Ñ ÑÐ·ÑÐºÐŸÐ²ÐŸÐ¹ ÐºÐŸÐŽ, Ð° ÐŸÑÑÐ°Ð»ÑÐœÑÐµ ÑÐžÑÑÑ -ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ ÑÑÑÐ°ÐœÐžÑÑ). ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµÂ <i>u7548el2.tif</i>Â ÐŒÐŸÐ¶ÐµÑ ÐŸÐ·ÐœÐ°ÑÐ°ÑÑ ÑÐžÑÑÐœÐŸÐº TIFF ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ 12, ÐœÐ°Ð¿ÐžÑÐ°ÐœÐœÐŸÐ¹ ÐœÐ° Ð°ÐœÐ³Ð»ÐžÐ¹ÑÐºÐŸÐŒ ÑÐ·ÑÐºÐµ Ð¿ÐŸÐŽ ÐºÐŸÐŽÐŸÐŒÂ <i>u7548e</i>.</Text>
+<Text id="89">Ð¡ÐŸÐ·ÐŽÐ°Ð¹ÑÐµ ÐŸÐŽÐœÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐœÐ° Ð¶ÐµÑÑÐºÐŸÐŒ ÐŽÐžÑÐºÐµ ÐŽÐ»Ñ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐœÑÑ
+ ÑÐ°Ð±ÐŸÑ, ÐœÐ°Ð·ÐŸÐ²ÐžÑÐµ, Ðº Ð¿ÑÐžÐŒÐµÑÑ,Â <i>scanjobs</i>. ÐÐ°ÑÐµÐŒ ÑÐŸÐ·ÐŽÐ°Ð¹ÑÐµ Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ Ð·Ð°ÐŽÐ°ÐœÐžÑ. ÐÐœÑÑÑÐž Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÐž ÑÐŸÐ·ÐŽÐ°Ð¹ÑÐµ ÐµÑÐµ ÐŸÐŽÐœÑ Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÑ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐž Ðž ÐºÐœÐžÐ³Ðž - Ðž7548 Ð² Ð¿ÑÐžÐŒÐµÑÐµ, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÐŸÐŒ Ð²ÑÑÐµ. Ð¡ÐŸÑ
+ÑÐ°ÐœÑÐ¹ÑÐµ Ð²ÑÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ TIFF ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, Ð²ÐºÐ»ÑÑÐ°Ñ ÑÐ²ÐµÑÐœÑÐµ ÑÐžÑÑÐœÐºÐž, Ð² ÑÑÐŸÐ¹ Ð¿Ð°Ð¿ÐºÐµ.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="productivity_and_resources">
+<Title>
+<Text id="90">ÐÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÑÐœÐŸÑÑÑ Ðž ÑÐµÑÑÑÑÑ</Text>
+</Title>
+<Content>
+<Text id="91">ÐÑ ÐœÐµ ÐŽÐŸÐ»Ð¶ÐœÑ ÐœÐµÐŽÐŸÐŸÑÐµÐœÐžÐ²Ð°ÑÑ Ð²ÐµÑÑ ÐŒÐ°ÑÑÑÐ°Ð± Ð¿ÑÐŸÑÐµÐŽÑÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ â Ð² ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž Ð¿ÑÐŸÑÐµÑÑ ÐÐ Ð¡. ÐÑÑÑÐµ Ð²ÑÐµÐ³ÐŸ ÑÑÐžÑÐ°ÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ðž ÐÐ Ð¡ ÐºÐ°Ðº Ð¿ÐŸÐ»ÐœÐŸÑÑÑÑ ÐœÐµÐ·Ð°Ð²ÐžÑÐžÐŒÑÐµ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž. ÐÐ¿ÑÐžÐŒÐ°Ð»ÑÐœÐŸÐµ ÑÐµÑÐµÐœÐžÐµ ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð±ÑÑÑ Ð¿ÑÐžÐœÑÑÐŸ Ð¿ÐŸ ÐºÐ°Ð¶ÐŽÐŸÐŒÑ ÐžÐ· ÐœÐžÑ
+ Ð² ÐŸÑÐŽÐµÐ»ÑÐœÐŸÑÑÐž.</Text>
+<Text id="92">ÐÐŸÑ ÐœÐµÐºÐŸÑÐŸÑÑÐµ Ð²ÐµÑÐž, ÐŸ ÐºÐŸÑÐŸÑÑÑ
+ ÑÐ»ÐµÐŽÑÐµÑ Ð¿ÐŸÐŽÑÐŒÐ°ÑÑ Ð¿ÐµÑÐµÐŽ Ð¿ÑÐžÐŸÐ±ÑÐµÑÐµÐœÐžÐµÐŒ ÑÐºÐ°ÐœÐµÑÐŸÐ² Ðž ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐŸÐ²: ÐœÐ°Ð»ÐžÑÐžÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÐ³ÐŸ Ð¿ÐŸÐŒÐµÑÐµÐœÐžÑ Ðž ÑÐ°Ð±ÐŸÑÐµÐ¹ ÑÐžÐ»Ñ, ÐŸÐ±ÑÑÐµÐœÐžÐµ ÑÐ°Ð±ÐŸÑÐžÑ
+; Ð·Ð°ÑÐ¿Ð»Ð°ÑÐ°; ÐŒÐžÐœÐžÐŒÐ°Ð»ÑÐœÐŸÐµ Ðž ÐŒÐ°ÐºÑÐžÐŒÐ°Ð»ÑÐœÐŸÐµ ÑÐžÑÐ»ÐŸ ÑÑÑÐ°ÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ; ÑÑÐŸÐºÐž; ÐŒÐŸÐ¶ÐœÐŸ Ð»Ðž ÑÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÐµÑÐµÐŽÐ°Ð²Ð°ÑÑ ÑÑÐµÑÑÐžÐŒ Ð»ÐžÑÐ°ÐŒ.</Text>
+<Subsection id="scanning_costs">
+<Title>
+<Text id="93">Ð¡ÑÐŸÐžÐŒÐŸÑÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="94">ÐÐ°Ð¶ÐœÐŸÐµ ÑÐµÑÐµÐœÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ ÐœÑÐ¶ÐœÐŸ Ð¿ÑÐžÐœÑÑÑ, - Ð¿ÐŸÐºÑÐ¿Ð°ÑÑ Ð»Ðž ÑÐºÐ°ÐœÐžÑÑÑÑÑÑ Ð°Ð¿Ð¿Ð°ÑÐ°ÑÑÑÑ Ðž Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐ°ÐŒÐžÐŒ, ÐžÐ»Ðž Ð¿ÐŸÑÑÑÐžÑÑ ÑÑÐŸ ÐŽÐµÐ»ÐŸ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÐž, ÑÐ¿ÐµÑÐžÐ°Ð»ÐžÐ·ÐžÑÑÑÑÐµÐ¹ÑÑ ÐœÐ° ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐž. ÐÐŸÑ Ð³Ð»Ð°Ð²ÐœÑÐµ Ð¿ÑÐœÐºÑÑ, ÐœÐ°ÐŽ ÐºÐŸÑÐŸÑÑÐŒÐž ÐœÐ°ÐŽÐŸ Ð¿ÐŸÐŽÑÐŒÐ°ÑÑ:</Text>
+<BulletList>
+<Bullet>
+<Text id="95">ÐÐŸÐœÐµÑÐœÑÐµ ÑÑÐŸÐºÐž ÐŽÐ»Ñ Ð·Ð°Ð²ÐµÑÑÐµÐœÐžÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ</Text>
+</Bullet>
+<Bullet>
+<Text id="96">ÐÐ±ÑÐµÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÑÑÑÐ°ÐœÐžÑ</Text>
+</Bullet>
+<Bullet>
+<Text id="97">ÐÐ°ÑÐ¿Ð»Ð°ÑÐ° ÑÐµÑ
+, ÐºÑÐŸ ÑÐŸÐ²ÐµÑÑÐ°ÐµÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</Bullet>
+</BulletList>
+<Text id="98">ÐÑÐŽÐž, Ð·Ð°ÐœÐžÐŒÐ°ÑÑÐžÐµÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµÐŒ, ÐŽÐŸÐ»Ð¶ÐœÑ ÐžÐŒÐµÑÑ Ð²ÑÑÐŸÐºÑÑ ÐŒÐŸÑÐžÐ²Ð°ÑÐžÑ, Ð±ÑÑÑ ÐžÑÐºÑÑÐœÑÐŒÐž Ðž ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÑÐŒÐž Ð·Ð° ÐºÐ°ÑÐµÑÑÐ²ÐŸ ÑÐ°Ð±ÐŸÑÑ.</Text>
+<Text id="99">Ð¡ÑÐµÐŽÐœÑÑ ÑÐµÐœÐ° Ð·Ð° ÐŸÐŽÐœÑ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐœÑÑ ÑÑÑÐ°ÐœÐžÑÑ Ñ Ð¿ÑÐŸÑÐµÑÑÐžÐŸÐœÐ°Ð»ÑÐœÑÑ
+ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÐ¹ ÑÐŸÑÑÐ°Ð²Ð»ÑÐµÑ $0.06. Ð ÑÑÐŸÐŒÑ ÐœÑÐ¶ÐœÐŸ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÑÑÐŸÐžÐŒÐŸÑÑÑ ÐŽÐŸÑÑÐ°Ð²ÐºÐž, ÐºÐŸÑÐŸÑÐ°Ñ ÐŒÐŸÐ¶ÐµÑ ÐŽÐŸÑÑÐžÐ³Ð°ÑÑ $0.03 Ð·Ð° ÑÑÐ°ÐœÑÐ¿ÐŸÑÑÐžÑÐŸÐ²ÐºÑ ÑÑÑÐ°ÐœÐžÑÑ ÐžÐ· ÑÐ°Ð·Ð²ÐžÐ²Ð°ÑÑÐµÐ¹ÑÑ ÑÑÑÐ°ÐœÑ Ð² ÑÐ°Ð·Ð²ÐžÑÑÑ, Ðž $0.015 - Ð·Ð° ÑÑÑÐ°ÐœÐžÑÑ Ð² ÑÐ°ÐŒÐŸÐ¹ ÑÑÑÐ°ÐœÐµ.</Text>
+<Text id="100">Ð ÑÐ°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="table_scanning_cost"/> Ð¿ÑÐžÐ²ÐµÐŽÐµÐœÐ° ÑÑÐŸÐžÐŒÐŸÑÑÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð²Ð°ÑÐžÐŒÐž ÑÑÐžÐ»ÐžÑÐŒÐž Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÑÐ°Ð·ÐœÑÑ
+ ÑÐžÐ¿ÐŸÐ² ÑÐºÐ°ÐœÐµÑÐŸÐ². ÐÐ°ÐŒÐµÑÑÑÐµ, ÑÑÐŸ Ð²ÑÐµ ÑÐžÑÑÑ Ð¿ÑÐžÐ±Ð»ÐžÐ·ÐžÑÐµÐ»ÑÐœÑ. ÐÐœÐž Ð¿ÑÐžÐŒÐµÑÐœÑ Ðž ÐŸÑÐœÐŸÐ²ÑÐ²Ð°ÑÑÑÑ ÐœÐ° ÐŸÐ¿ÑÑÐµ Ð°Ð²ÑÐŸÑÐŸÐ². ÐÐµÑÐ²ÑÐµ ÑÑÐž ÐºÐŸÐ»ÐŸÐœÐºÐž Ð²ÐºÐ»ÑÑÐ°ÑÑ ÑÑÐŸÐžÐŒÐŸÑÑÑ ÑÐ°Ð±ÐŸÑÐµÐ¹ ÑÐžÐ»Ñ. ÐÐµÑÐ²Ð°Ñ ÐžÐ· ÐœÐžÑ
+ - ÑÑÐŸ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÑÐœÐŸÑÑÑ Ð² ÑÑÑÐ°ÐœÐžÑÐ°Ñ
+/ÐŒÐµÑÑÑ Ð¿ÑÐž ÑÐ°Ð±ÐŸÑÐµ ÐœÐ° Ð¿ÐŸÐ»ÐœÑÑ ÑÑÐ°Ð²ÐºÑ. Ð Ð°ÑÑÐµÑ ÑÐµÐ»ÐŸÐ²ÐµÐºÐŸ-ÑÐ°ÑÐŸÐ² ÐœÐ° ÑÑÑÐ°ÐœÐžÑÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ Ð¿ÑÑÐµÐŒ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ ÑÐžÑÐ»Ð° ÑÐ°Ð±ÐŸÑÐžÑ
+ ÑÐ°ÑÐŸÐ² Ð² ÐŒÐµÑÑÑÐµ ÐœÐ° Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÑÐœÐŸÑÑÑ ÑÑÑÐ°ÐœÐžÑÐ°/ÐŒÐµÑÑÑ Ðž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ Ð²ÐŸ Ð²ÑÐŸÑÐŸÐ¹ ÐºÐŸÐ»ÐŸÐœÐºÐµ. ÐÑÐž ÑÐ°ÑÑÐµÑÐµ Ð¿ÑÐµÐŽÐ¿ÐŸÐ»Ð°Ð³Ð°ÐµÑÑÑ 180 ÑÐ°Ð±ÐŸÑÐžÑ
+ ÑÐ°ÑÐŸÐ² Ð² ÐŒÐµÑÑÑ.</Text>
+<Table id="table_scanning_cost">
+<Title>
+<Text id="101">Ð¡ÑÐŸÐžÐŒÐŸÑÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="104">Â </th>
+<th width="76">
+<Text id="102">ÐÐ±ÑÐµÐŒ (ÑÑÑÐ°ÐœÐžÑ/ÐŒÐµÑÑÑ)</Text>
+</th>
+<th width="66">
+<Text id="103">Ð§Ð°Ñ/ÑÑÑÐ° ÐœÐžÑÐ° (180 ÑÐ°ÑÐŸÐ² Ð² ÐŒÐµÑÑÑ)</Text>
+</th>
+<th width="66">
+<Text id="104">ÐŠÐµÐœÐ°/ÑÑÑ (Ð¿ÑÐµÐŽÐ¿ÐŸ-Ð»Ð°ÑÐ°Ñ $4/ÑÐ°Ñ)</Text>
+</th>
+<th width="66">
+<Text id="105">ÐŠÐµÐœÐ° ÑÐºÐ°ÐœÐµÑÐ°</Text>
+</th>
+<th width="66">
+<Text id="106">Ð Ð°Ð±ÐŸÑÐŸÑÐ¿ÐŸÑÐŸ Ð±ÐœÐŸÑÑÑ ÐŽÐŸ Ð¿ÐµÑÐ²ÐŸÐ³ÐŸ ÑÐµÐŒÐŸÐœÑÐ° (ÑÑÑÐ°ÐœÐžÑ)</Text>
+</th>
+<th width="85">
+<Text id="107">ÐÐ±ÑÐµÐŒ Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÂ­ÐŒÑÐ¹ Ð¿ÑÐŸÑÐµÑÑÐžÂ­ÐŸÐœÐ°Ð»ÑÐœÐŸÐ¹ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÐµÐ¹ (Ð¿ÑÐž $0,06 Ð·Ð° ÑÑÑÐ°ÐœÐžÑÑ)</Text>
+</th>
+</tr>
+<tr>
+<th width="104">
+<Text id="108">Ð¡ÑÑÐ°ÐœÐžÑÐœÑÐ¹ ÐœÐ°ÑÑÐŸÐ»ÑÐœÑÐ¹</Text>
+</th>
+<th width="76">
+<Text id="109">2,500</Text>
+</th>
+<th width="66">
+<Text id="110">0.072</Text>
+</th>
+<th width="66">
+<Text id="111">$0.288</Text>
+</th>
+<th width="66">
+<Text id="112">$300</Text>
+</th>
+<th width="66">
+<Text id="113">7,000</Text>
+</th>
+<th width="85">
+<Text id="114">5,000</Text>
+</th>
+</tr>
+<tr>
+<th width="104">
+<Text id="115">ÑÐºÐ°ÐœÐµÑ Ð¡ÐºÐ°ÐœÐµÑ Ñ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÂ­ÐºÐŸÐ¹</Text>
+</th>
+<th width="76">
+<Text id="116">8,000</Text>
+</th>
+<th width="66">
+<Text id="117">0.0225</Text>
+</th>
+<th width="66">
+<Text id="118">$0.09</Text>
+</th>
+<th width="66">
+<Text id="119">$800</Text>
+</th>
+<th width="66">
+<Text id="120">30,000</Text>
+</th>
+<th width="85">
+<Text id="121">13,000</Text>
+</th>
+</tr>
+<tr>
+<th width="104">
+<Text id="122">Ð¿ÐŸÐŽÐ°ÑÐµÐ¹ ÑÑÑÐ°ÐœÐžÑ ÐÑÐŸÑÐµÑÑÐžÂ­ÐŸÐœÐ°Ð»ÑÐœÑÐ¹ low end duplex</Text>
+</th>
+<th width="76">
+<Text id="123">40,000</Text>
+</th>
+<th width="66">
+<Text id="124">0.0045</Text>
+</th>
+<th width="66">
+<Text id="125">$0.018</Text>
+</th>
+<th width="66">
+<Text id="126">$6,000</Text>
+</th>
+<th width="66">
+<Text id="127">600,000</Text>
+</th>
+<th width="85">
+<Text id="128">100,000</Text>
+</th>
+</tr>
+<tr>
+<th width="104">
+<Text id="129">ÐÑÐŸÑÐµÑÑÐžÐŸÐœÐ°Â­Ð»ÑÐœÑÐ¹: high-end duplex</Text>
+</th>
+<th width="76">
+<Text id="130">150,000</Text>
+</th>
+<th width="66">
+<Text id="131">0.0012</Text>
+</th>
+<th width="66">
+<Text id="132">$0.0048</Text>
+</th>
+<th width="66">
+<Text id="133">$50,000</Text>
+</th>
+<th width="66">
+<Text id="134">8,000,000</Text>
+</th>
+<th width="85">
+<Text id="135">833,000</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="136">Ð§ÑÐŸÐ±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÑÑÐŸÐžÐŒÐŸÑÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŸÐŽÐœÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ, ÑÐŒÐœÐŸÐ¶ÑÑÐµ Ð¿ÐŸÐ»ÐœÑÑ ÑÐ°ÑÐŸÐ²ÑÑ Ð·Ð°ÑÐ¿Ð»Ð°ÑÑ ÐœÐ° Ð²ÑÐŸÑÑÑ ÐºÐŸÐ»ÐŸÐœÐºÑ. Ð Ð¿ÑÐžÐŒÐµÑÑ, Ð² ÑÑÐµÑÑÐµÐ¹ ÐºÐŸÐ»ÐŸÐœÐºÐµ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐ° ÑÐµÐœÐ° Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð¿ÑÐž ÐœÐ°Ð¹ÐŒÐµ ÑÑÑÐŽÐ° Ð±ÐµÐ· ÑÑÐµÑÐ° Ð·Ð°ÑÑÐ°Ñ ÐœÐ° ÑÐºÐ°ÐœÐµÑ - $4/ÑÐ°Ñ.</Text>
+<Text id="137">Ð­ÑÐž Ð¿ÐŸÐŽÑÑÐµÑÑ Ð¿ÐŸÐŽÑÐ°Ð·ÑÐŒÐµÐ²Ð°ÑÑ, ÑÑÐŸ ÑÐºÐ°ÐœÐµÑ Ð±ÑÐŽÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ðœ ÐŽÐ»Ñ ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ Ð±ÐŸÐ»ÑÑÐŸÐ³ÐŸ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²Ð° ÐºÐŸÐ¿ÐžÐ¹, ÑÑÐŸÐ±Ñ ÐŸÐºÑÐ¿ÐžÑÑ ÑÐ²ÐŸÑ ÐœÐ°ÑÐ°Ð»ÑÐœÑÑ ÑÑÐŸÐžÐŒÐŸÑÑÑ. ÐÐŸÑÐ»ÐµÐŽÐœÐžÐµ ÑÑÐž ÐºÐŸÐ»ÐŸÐœÐºÐž ÐŽÐ°ÑÑ Ð±ÐŸÐ»ÑÑÐµ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐŸ ÑÑÐŸÐžÐŒÐŸÑÑÐž ÑÐ°ÐŒÐŸÐ³ÐŸ ÑÐºÐ°ÐœÐµÑÐ°. ÐÐµÑÐ²Ð°Ñ ÐžÐ· ÐœÐžÑ
+ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÑÐŸÐžÐŒÐŸÑÑÑ ÑÐºÐ°ÐœÐµÑÐ°, ÑÐ»ÐµÐŽÑÑÑÐ°Ñ Ð¿ÑÐžÐ±Ð»ÐžÐ·ÐžÑÐµÐ»ÑÐœÑÑ Ð¿ÑÐŸÐŽÐŸÐ»Ð¶ÐžÑÐµÐ»ÑÐœÐŸÑÑÑ ÑÐ°Ð±ÐŸÑÐŸÑÐ¿ÐŸÑÐŸÐ±ÐœÐŸÑÑÐž. ÐÐŸÑÐ»ÐµÐŽÐœÑÑ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÐžÑÐ»ÐŸ ÑÑÑÐ°ÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ, ÐœÐ°ÐœÑÐ² ÐºÐŸÐŒÐ¿Ð°ÐœÐžÑ, Ð¿ÑÐž ÑÐµÐœÐµ $0.06/ÑÑÑÐ°ÐœÐžÑÐ°.</Text>
+<Text id="138">ÐÐŸÐœÐµÑÐœÐŸ Ð¶Ðµ ÐœÐ° Ð²ÑÐ±ÐŸÑ ÑÐºÐ°ÐœÐµÑÐ° Ð²Ð»ÐžÑÑÑ Ðž ÐŽÑÑÐ³ÐžÐµ ÑÐ°ÐºÑÐŸÑÑ: ÐœÐ°Ð»ÐžÑÐžÐµ ÐŽÐµÐœÐµÐ³, ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÑ Ð² ÐŒÐžÐœÐžÐŒÐžÐ·Ð°ÑÐžÐž Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÐŽÑÑÐ³ÐžÑ
+, ÐŽÐŸÐ³ÐŸÐ²ÐŸÑÐµÐœÐœÐŸÑÑÑ Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐŸÐ¹, ÑÐ°Ð·ÑÐµÑÐ°ÑÑÐ°Ñ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐºÐœÐžÐ³, ÐœÐµ Ð²ÑÐ²ÐŸÐ·Ñ ÐžÑ
+ Ð·Ð° Ð¿ÑÐµÐŽÐµÐ»Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ðž Ñ.ÐŽ.</Text>
+<Text id="139">Ð¢Ð°Ð±Ð»ÐžÑÐ° Ð¿ÑÐžÐ²ÐµÐŽÐµÐœÐœÐ°Ñ Ð²ÑÑÐµ, ÐŽÐ°ÐµÑ Ð¿ÑÐžÐŒÐµÑÐœÑÑ ÐŸÑÐµÐœÐºÑ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²Ð° ÑÑÑÐ°ÐœÐžÑ, ÐºÐŸÑÐŸÑÐŸÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ ÐŽÐ»Ñ ÐŸÐºÑÐ¿Ð°ÐµÐŒÐŸÑÑÐž Ð·Ð°ÑÑÐ°Ñ. ÐÑÐµÐœÑ ÑÐµÐŽÐºÐž ÑÐ»ÑÑÐ°Ðž, ÐºÐŸÐ³ÐŽÐ° ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑ ÐœÑÐ¶ÐŽÐ°ÐµÑÑÑ Ð² ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐž 800000 ÑÑÑÐ°ÐœÐžÑ. ÐÑÐž ÑÐ°ÐºÐŸÐŒ ÐŒÐ°ÑÑÑÐ°Ð±Ðµ Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ Ð±ÐŸÐ»ÐµÐµ ÑÐ»ÐŸÐ¶ÐœÑÐµ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ, ÑÐ°ÐºÐžÐµ ÐºÐ°Ðº ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÐŸÐ±ÐŸÑÑÐŽÐŸÐ²Ð°ÐœÐžÑ Ðž ÐŸÐºÑÐ¿Ð°ÐµÐŒÐŸÑÑÑ Ð·Ð°ÑÑÐ°Ñ Ð¿ÑÑÐµÐŒ ÑÐŽÐ°ÑÐž ÐµÐ³ÐŸ Ð² Ð°ÑÐµÐœÐŽÑ, ÐºÐŸÑÐŸÑÑÐµ ÐœÐµ Ð±ÑÐŽÑÑ ÐŸÐ±ÑÑÐ¶ÐŽÐ°ÑÑÑÑ Ð² ÑÑÐŸÐ¹ ÑÐ°ÑÑÐž.</Text>
+<Text id="140">Ð Ð°Ð·Ð²ÐžÑÐžÐµ Ð±ÐžÐ·ÐœÐµÑÐ° ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÐºÐ°Ð·Ð°ÑÑÑÑ ÐŸÑÐµÐœÑ Ð¿ÑÐžÐ²Ð»ÐµÐºÐ°ÑÐµÐ»ÑÐœÐŸÐ¹ ÐºÐŸÐŒÐŒÐµÑÑÐµÑÐºÐŸÐ¹ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑÑ, Ð² ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž Ð² ÑÐ°Ð·Ð²ÐžÐ²Ð°ÑÑÐžÑ
+ÑÑ ÑÑÑÐ°ÐœÐ°Ñ
+. ÐÐŸ Ð¿ÐŸÐŒÐœÐžÑÐµ, Ð§ÑÐŸ Ð¿ÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº Ð±ÑÐŽÑÑ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, Ð²Ð°ÑÐž ÐºÐ»ÐžÐµÐœÑÑ Ð±ÐŸÐ»ÑÑÐµ ÐœÐžÐºÐŸÐ³ÐŽÐ° ÐœÐµ Ð·Ð°ÐºÐ°Ð¶ÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐµÑ
+ Ð¶Ðµ ÑÐ°ÐŒÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² - Ð²ÐœÐµ Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÑÐŸÐ³ÐŸ, ÐœÐ°ÑÐºÐŸÐ»ÑÐºÐŸ Ñ
+ÐŸÑÐŸÑÐž Ð²Ð°ÑÐž Ñ ÐœÐžÐŒÐž ÐŸÑÐœÐŸÑÐµÐœÐžÑ. Ð¡ ÐºÐŸÐŒÐŒÐµÑÑÐµÑÐºÐŸÐ¹ ÑÐŸÑÐºÐž Ð·ÑÐµÐœÐžÑ ÑÑÐŸÑ Ð±ÐžÐ·ÐœÐµÑ ÐœÑÐ¶ÐŽÐ°ÐµÑÑÑ Ð² ÐžÐœÑÐµÐœÑÐžÐ²ÐœÐŸÐŒ ÐŒÐ°ÑÐºÐµÑÐžÐœÐ³ÐŸÐ²ÐŸÐŒ ÐžÐ·ÑÑÐµÐœÐžÐž. ÐÑ ÐœÐµ ÑÐŸÐ²ÐµÑÑÐµÐŒ ÐœÐµÐ¿ÑÐ°Ð²ÐžÑÐµÐ»ÑÑÑÐ²ÐµÐœÐœÑÐŒ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑÐŒ Ðž ÐœÐµÐºÐŸÐŒÐŒÐµÑÑÐµÑÐºÐžÐŒ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑÐŒ Ð·Ð°ÐœÐžÐŒÐ°ÑÑÑÑ ÑÐ°ÐºÐžÐŒ Ð±ÐžÐ·ÐœÐµÑÐŸÐŒ Ð±ÐµÐ· ÐŽÐµÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÐžÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ ÑÑÐœÐºÐ° Ðž Ñ
+ÐŸÑÐŸÑÐŸ Ð¿ÑÐŸÐŽÑÐŒÐ°ÐœÐœÐŸÐ³ÐŸ Ð±ÐžÐ·ÐœÐµÑ-Ð¿Ð»Ð°ÐœÐ°.</Text>
+<Text id="141">Ð Ð·Ð°ÐºÐ»ÑÑÐµÐœÐžÐµ ÐŸÑÐŒÐµÑÐžÐŒ, ÑÑÐŸ ÐµÑÐ»Ðž ÐœÑÐ¶ÐœÐŸ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ ÐŸÑ 10000 ÐŽÐŸ 50000 ÑÑÑÐ°ÐœÐžÑ, Ð»ÑÑÑÐµ Ð¿ÐŸÑÑÑÐžÑÑ ÑÑÑ ÑÐ°Ð±ÐŸÑÑ ÑÐºÐ°ÐœÐžÑÑÑÑÐµÐ¹ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÐž. ÐÑÐŸÑÐµÑÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐ¹ low-end ÑÐºÐ°ÐœÐµÑ Ð±ÑÐŽÐµÑ ÐŸÐºÑÐ¿Ð»ÐµÐœ ÑÐŸÐ»ÑÐºÐŸ Ð² ÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž Ð²Ñ ÐŸÑÑÐºÐ°ÐœÐžÑÑÐµÑÐµ Ð±ÐŸÐ»ÐµÐµ 100000 ÑÑÑÐ°ÐœÐžÑ. ÐÑÐ»Ðž Ð²Ñ ÑÐµÑÐžÐ»Ðž Ð¿ÑÐžÐŸÐ±ÑÐµÑÑÐž ÑÐ°ÐºÐŸÐ¹ ÑÐºÐ°ÐœÐµÑ, ÑÐŸ Ð»ÑÑÑÐµ ÑÑÐŸ ÑÐŽÐµÐ»Ð°ÑÑ ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸ Ñ ÐŽÑÑÐ³ÐŸÐ¹ ÐœÐµÐ¿ÑÐ°Ð²ÐžÑÐµÐ»ÑÑÑÐ²ÐµÐœÐœÐŸÐ¹ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐµÐ¹ ÐžÐ»Ðž Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐŸÐ¹.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="ocr">
+<Title>
+<Text id="142">ÐÐ Ð¡: ÐŸÐ¿ÑÐžÑÐµÑÐºÐžÐ¹ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÑÐµÐ»Ñ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="143">ÐÐ¿ÑÐžÑÐµÑÐºÐžÐ¹ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÑÐµÐ»Ñ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² ÐžÐ»Ðž ÐÐ Ð¡ ÑÑÐ°ÐœÑÑÐŸÑÐŒÐžÑÑÐµÑ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐµ ÑÐžÑÑÐŸÐ²ÐŸÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ Ð² ÑÐµÐºÑÑ. ÐÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐŒÐ°ÑÐµÑÐžÐ°Ð» - ÑÑÐŸ ÑÐžÑÑÐŸÐ²ÐŸÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ Ð² ÑÐŸÑÐŒÐ°ÑÐµ TIFF ÐžÐ»Ðž Bitmap â Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÐŸ ÑÑÐŸÐ±Ñ ÐŸÐœ Ð±ÑÐ» Ñ
+ÐŸÑÐŸÑÐµÐ³ÐŸ ÐºÐ°ÑÐµÑÑÐ²Ð°. ÐÐŸÑÐ»Ðµ Ð¿ÑÐŸÑ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ ÑÐµÑÐµÐ· ÐÐ Ð¡ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÑÐ°Ð¹Ð» Ð² ÑÐŸÑÐŒÐ°ÑÐµ RTF, Word, HTML ÐœÐ° Ð²Ð°ÑÐµ ÑÑÐŒÐŸÑÑÐµÐœÐžÐµ.</Text>
+<Text id="144">ÐÐŸÑ ÑÐ°Ð³Ðž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ Ð¿ÑÐž Ð¿ÐµÑÐµÐ²ÐŸÐŽÐµ Ð±ÑÐŒÐ°Ð¶ÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÑÐžÑÑÐŸÐ²ÐŸÐ¹ ÑÐŸÑÐŒÐ°Ñ:</Text>
+<BulletList>
+<Bullet>
+<Text id="145">ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</Bullet>
+<Bullet>
+<Text id="146">Ð°ÐœÐ°Ð»ÐžÐ·</Text>
+</Bullet>
+<Bullet>
+<Text id="147">ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐœÐžÐµ</Text>
+</Bullet>
+<Bullet>
+<Text id="148">ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐ¹ Ðž ÑÐ°Ð±Ð»ÐžÑ. </Text>
+</Bullet>
+</BulletList>
+<Text id="149">Ð¡Ð»ÐµÐŽÑÑ ÐžÐŒ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑ ÐºÐŸÐœÑÑÐŸÐ»Ñ ÐºÐ°ÑÐµÑÑÐ²Ð° Ð¿ÐŸÐ»ÑÑÐµÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² Ðž ÑÐŸÑ
+ÑÐ°ÐœÑÑÑ ÐžÑ
+ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐ¹ Ð¿Ð°Ð¿ÐºÐµ.</Text>
+<Text id="150">ÐÐ° ÑÑÐœÐºÐµ ÑÑÑÐµÑÑÐ²ÑÐµÑ ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ ÐŒÐœÐŸÐ³ÐŸ Ñ
+ÐŸÑÐŸÑÐžÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ ÐÐ Ð¡ ÑÑÐŸÐžÐŒÐŸÑÑÑÑ ÐŸÑ $100-400<FootnoteRef id="2"/>. ÐÐŸÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐžÐ· ÐœÐžÑ
+:</Text>
+<BulletList>
+<Bullet>
+<Text id="151">Read-Iris (http://www.readiris.com/)</Text>
+</Bullet>
+<Bullet>
+<Text id="152">Omnipage (http://www.omnipage.com/)</Text>
+</Bullet>
+<Bullet>
+<Text id="153">Fine-Reader (http://www.finereader.com/)</Text>
+</Bullet>
+</BulletList>
+<Text id="154">ÐÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, Ð²ÐºÐ»ÑÑÐ°Ñ Ð¿ÐµÑÐµÑÐµÐœÑ ÐŽÐžÑÑÑÐžÐ±ÑÑÑÐµÑÐŸÐ², ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐœÐ° ÐÐœÑÐµÑÐœÐµÑ ÑÐ°Ð¹ÑÐµ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÐµÐ¹. Ð¡ÑÐµÐŽÐž ÐœÐžÑ
+, Ð¿ÐŸ ÐŸÐ¿ÑÑÑ Ð°Ð²ÑÐŸÑÐ°, ÑÐ°ÐŒÑÐµ Ð»ÐµÐ³ÐºÐžÐµ Ð² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž Fine-Reader Ðž Omnipage. Fine-Reader ÑÐ²Ð»ÑÐµÑÑÑ ÑÐ°ÐŒÑÐŒ ÐŽÐµÑÐµÐ²ÑÐŒ Ðž ÑÑÐŸÐžÑ Ð²ÑÐµÐ³ÐŸ $100. ÐÐœ Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÐµÑ Ð³ÐžÐ±ÐºÐžÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ðž ÐœÐ°ÐžÐ±ÐŸÐ»ÑÑÐµÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÑÐ°Ð·ÐœÑÑ
+ ÑÐ·ÑÐºÐŸÐ².</Text>
+<Text id="155">ÐÐ°ÐŒ ÐœÑÐ¶ÐœÐŸ ÑÐµÑÐžÑÑ, Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑ Ð»Ðž ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ðž ÐÐ Ð¡ ÑÐ²ÐŸÐžÐŒÐž ÑÑÐžÐ»ÐžÑÐŒÐž ÐžÐ»Ðž Ð¿ÐŸÑÑÑÐžÑÑ ÑÑÐŸ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÐž, ÑÐ¿ÐµÑÐžÐ°Ð»ÐžÐ·ÐžÑÑÑÑÐµÐ¹ÑÑ Ð² ÑÑÐŸÐ¹ ÑÑÐµÑÐµ. ÐÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ Ð¿ÑÐŸÐ²ÐµÑÑÐž ÑÑÐŸÑ Ð¿ÑÐŸÑÐµÑÑ ÑÐ²ÐŸÐžÐŒÐž ÑÑÐžÐ»ÐžÑÐŒÐž, Ð²Ð°ÐŒ ÐœÑÐ¶ÐµÐœ ÑÐºÐ°ÐœÐµÑ, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÐÐ Ð¡, ÑÐ°Ð·Ð²ÐžÑÐžÐµ ÐœÐ°Ð²ÑÐºÐŸÐ² Ð² ÑÐ°Ð±ÐŸÑÐµ Ñ ÐÐ Ð¡, ÑÐ°Ð±ÐŸÑÐœÐžÐºÐž, ÐœÐ°ÑÐµÐ»ÐµÐœÐœÑÐµ ÐœÐ° ÐºÐ°ÑÐµÑÑÐ²ÐŸ ÐžÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÑÐ°Ð±ÐŸÑÑ.</Text>
+<Section id="the_ocr_process">
+<Title>
+<Text id="156">ÐÑÐŸÑÐµÑÑ ÐÐ Ð¡</Text>
+</Title>
+<Content>
+<Text id="157">ÐÑÐŸÑÐµÑÑ ÐÐ Ð¡ ÑÐ°Ð·Ð»ÐžÑÐ°ÐµÑÑÑ Ð²ÐŸ Ð²ÑÐµÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°Ñ
+ ÐÐ Ð¡, Ðž Ð»ÑÐ±Ð°Ñ ÐžÐ· Ð²ÑÐ±ÑÐ°ÐœÐœÑÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ ÑÑÐµÐ±ÑÐµÑ ÐŽÐŸÐ±ÑÐŸÑÐœÐŸÐ³ÐŸ ÐžÐ·ÑÑÐµÐœÐžÑ. ÐÐœÑÑÑÑÐºÑÐžÑ Ð¿ÐŸ ÑÐºÑÐ¿Ð»ÑÐ°ÑÐ°ÑÐžÐž ÐºÐ°Ð¶ÐŽÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŸÐ±ÑÑÑÐœÑÐµÑ ÑÑÐŸÑ Ð¿ÑÐŸÑÐµÑÑ Ð² ÐŽÐµÑÐ°Ð»ÑÑ
+. Ð§ÐµÑÑÑÐµ Ð¿ÑÐœÐºÑÐ° Ð¿ÑÐŸÑÐµÑÑÐ° ÐÐ Ð¡ Ð·Ð°ÑÐ»ÑÐ¶ÐžÐ²Ð°ÑÑ ÐŸÑÐŸÐ±ÐŸÐ³ÐŸ Ð²ÐœÐžÐŒÐ°ÐœÐžÑ: ÐºÐŸÐœÑÑÐŸÐ»Ñ ÐºÐ°ÑÐµÑÑÐ²Ð°, ÑÐ°Ð±Ð»ÐžÑÑ, ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ Ðž ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐžÐ¹ ÐŒÐ°ÑÐµÑÐžÐ°Ð» - ÑÐ°ÐºÐŸÐ¹, ÐºÐ°Ðº ÑÐŸÑÐŒÑÐ»Ñ, ÐžÐœÐŸÑÑÑÐ°ÐœÐœÑÐ¹ ÑÐ·ÑÐº Ðž Ñ.ÐŽ.</Text>
+<Subsection id="quality_control_1">
+<Title>
+<Text id="158">ÐÐŸÐœÑÑÐŸÐ»Ñ ÐºÐ°ÑÐµÑÑÐ²Ð°</Text>
+</Title>
+<Content>
+<Text id="159">ÐÑ ÑÐœÐŸÐ²Ð° Ðž ÑÐœÐŸÐ²Ð° Ñ
+ÐŸÑÐžÐŒ Ð·Ð°ÐŸÑÑÑÐžÑÑ Ð²Ð°ÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÐºÐŸÐœÑÑÐŸÐ»Ðµ ÐºÐ°ÑÐµÑÑÐ²Ð°. ÐÐŸÐœÑÑÐŸÐ»Ñ ÐºÐ°ÑÐµÑÑÐ²Ð° Ð»ÑÑÑÐµ Ð¿ÐŸÑÑÑÐ°ÑÑ Ð»ÑÐŽÑÐŒ, ÑÐµÐ¹ ÑÐŸÐŽÐœÐŸÐ¹ ÑÐ·ÑÐº ÑÐ²Ð»ÑÐµÑÑÑ ÑÐ°ÐºÐžÐŒ, ÐœÐ° ÐºÐŸÑÐŸÑÐŸÐŒ ÐœÐ°Ð¿ÐžÑÐ°Ðœ ÐŽÐŸÐºÑÐŒÐµÐœÑ, ÐžÐ»Ðž ÐŸÐœÐž Ð²Ð»Ð°ÐŽÐµÑÑ ÑÑÐžÐŒ ÑÐ·ÑÐºÐŸÐŒ Ð² ÑÐŸÐ²ÐµÑÑÐµÐœÑÑÐ²Ðµ. ÐÑÑÑÐžÐµ ÑÐ°Ð±ÐŸÑÐœÐžÐºÐž - ÑÑÐŸ ÑÐºÐŸÐ»ÑÐœÐžÐºÐž Ðž ÑÑÑÐŽÐµÐœÑÑ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŒÐŸÐ»ÐŸÐŽÑÐµ Ð»ÑÐŽÐž Ð±ÐŸÐ»ÐµÐµ Ð²ÐœÐžÐŒÐ°ÑÐµÐ»ÑÐœÑ Ðž Ð±ÐŸÐ»ÐµÐµ ÑÐºÐŸÐœÑÐµÐœÑÑÐžÑÐŸÐ²Ð°ÐœÑ Ð¿ÑÐž ÑÐ°ÐºÐŸÐŒ Ð²ÐžÐŽÐµ ÑÐ°Ð±ÐŸÑÑ, ÐœÐµÐ¶ÐµÐ»Ðž Ð¿ÐŸÐ¶ÐžÐ»ÑÐµ Ð»ÑÐŽÐž. </Text>
+<Text id="160">ÐÐ±ÑÑÐœÐŸ ÑÑÑÐµÑÑÐ²ÑÐµÑ ÑÐµÑÑÑÐµ ÑÑÐ°Ð¿Ð° ÐºÐŸÐœÑÑÐŸÐ»Ñ ÐºÐ°ÑÐµÑÑÐ²Ð°.</Text>
+<Text id="161">ÐÐµÑÐ²ÑÐ¹ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑÑ ÐŸÐŽÐœÐŸÐ²ÑÐµÐŒÐµÐœÐœÐŸ Ñ Ð¿ÑÐŸÑÐµÑÑÐŸÐŒ ÐÐ Ð¡. ÐÐ°Ð¶ÐŽÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐÐ Ð¡ ÐžÐŒÐµÐµÑ Ð²ÑÑÑÐŸÐµÐœÐœÑÑ Ð¿ÑÐŸÐ²ÐµÑÐºÑ ÐŸÑÑÐŸÐ³ÑÐ°ÑÐžÐž, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐŸÐŽÑÐµÑÐºÐžÐ²Ð°ÐµÑ Ð¿ÐŸÐŽÐŸÐ·ÑÐžÑÐµÐ»ÑÐœÑÐµ Ð¿ÐŸ ÐœÐ°Ð¿ÐžÑÐ°ÐœÐžÑ ÑÐ»ÐŸÐ²Ð°.</Text>
+<Text id="162">ÐÑÐŸÑÐŸÐ¹ ÑÑÐ°Ð¿ - ÐŸÐ±ÑÐ°Ñ Ð¿ÑÐŸÐ²ÐµÑÐºÐ° ÑÐµÐºÑÑÐ° Ð¿ÐŸÑÐ»Ðµ Ð·Ð°Ð²ÐµÑÑÐµÐœÐžÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÐÐ Ð¡. ÐÑÐµÐœÑ ÑÐ°ÑÑÐŸ Ð²ÑÑÑÐµÑÐ°ÑÑÑÑ ÑÐ°ÐºÐžÐµ ÐŸÑÐžÐ±ÐºÐž, ÐºÐ°Ðº Ð¿ÑÐŸÐ¿ÑÑÐº ÑÑÑÐ°ÐœÐžÑ, Ð°Ð±Ð·Ð°ÑÐµÐ², ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹ Ð³Ð»Ð°Ð² Ðž Ñ.ÐŽ. ÐÑÐ¶ÐœÐŸ Ð¿ÑÐŸÐ²ÐµÑÑÐž ÐŸÐ±ÑÐžÐ¹ ÐŸÐ±Ð·ÐŸÑ ÐœÐ° ÐœÐ°Ð»ÐžÑÐžÐµ Ð²ÑÐµÑ
+ ÑÑÑÐ°ÐœÐžÑ Ðž Ð¿ÑÐŸÐ²ÐµÑÐºÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐ², ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹ Ð³Ð»Ð°Ð², Ð°Ð±Ð·Ð°ÑÐµÐ² Ðž ÑÐ°Ð±Ð»ÐžÑ.</Text>
+<Text id="163">Ð¢ÑÐµÑÐžÐ¹ ÑÑÐ°Ð¿ - Ð¿ÑÐŸÐ²ÐµÑÐºÐ° ÐŸÑÑÐŸÐ³ÑÐ°ÑÐžÐž Ð² Microsoft Word. Ð Word, ÐºÐ°Ðº Ð¿ÑÐ°Ð²ÐžÐ»ÐŸ, ÐŸÑÑÐŸÐ³ÑÐ°ÑÐžÑÐµÑÐºÐžÐµ ÑÐ»ÐŸÐ²Ð°ÑÐž Ð±ÐŸÐ»ÐµÐµ ÐžÑÑÐµÑÐ¿ÑÐ²Ð°ÑÑÐžÐµ, ÑÐµÐŒ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°Ñ
+ ÐÐ Ð¡. ÐÑÑÐµÐŒ ÐžÐŒÐ¿ÐŸÑÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð² Word Ðž Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐžÑ ÐŸÑÑÐŸÐ³ÑÐ°ÑÐžÑÐµÑÐºÐŸÐ¹ Ð¿ÑÐŸÐ²ÐµÑÐºÐž ÐŒÐŸÐ¶ÐœÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ Ðž ÐžÑÐ¿ÑÐ°Ð²ÐžÑÑ Ð±ÐŸÐ»ÑÑÐµÐµ ÑÐžÑÐ»ÐŸ ÐŸÑÐžÐ±ÐŸÐº. ÐÐµ Ð·Ð°Ð±ÑÐŽÑÑÐµ Ð²Ð²ÐµÑÑÐž Ð² Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ Ð¿ÑÐŸÐ²ÐµÑÐºÐž ÐºÐŸÐŒÐ¿Ð»ÐµÐºÑÐœÑÐµ ÑÐ»ÐŸÐ²Ð° Ðž ÑÐµÑÐŒÐžÐœÑ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐžÑÑÑÐž ÑÐ°ÐºÐŸÐ³ÐŸ ÑÐŸÐŽÐ° ÑÐµÐºÑÑÐ°ÐŒ, ÐœÐ° ÐœÐ°Ð»ÐžÑÐžÐµ Ð² ÐœÐžÑ
+ ÐŸÑÐžÐ±ÐŸÐº.</Text>
+<Text id="164">Ð ÐœÐ°ÐºÐŸÐœÐµÑ, ÐœÐ° ÑÐµÑÐ²ÐµÑÑÐŸÐŒ ÑÑÐ°Ð¿Ðµ Ð·Ð°Ð²ÐµÑÑÐµÐœÐœÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐŽÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ Ð¿ÑÐŸÐ²ÐµÑÐµÐœ ÐŽÑÑÐ³ÐžÐŒ ÑÐµÐ»ÐŸÐ²ÐµÐºÐŸÐŒ, Ð·Ð°ÐœÐžÐŒÐ°ÑÑÐžÐŒÑÑ ÑÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÐµÐŒ Ð¿ÐŸÐ»ÐœÐŸÐ¹ ÐºÐœÐžÐ³Ðž, Ð¿ÑÐŸÐ²ÐµÑÑÑÑÐžÐŒ ÐŸÑÑÐŸÐ³ÑÐ°ÑÐžÑ, ÐœÐ°Ð»ÐžÑÐžÐµ Ð¿ÑÐŸÐ±Ð»ÐµÐŒ Ñ ÑÐ°Ð±Ð»ÐžÑÐ°ÐŒÐž, ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑÐŒÐž Ðž ÐŸÐ±ÑÐžÐŒ Ð²ÐžÐŽÐŸÐŒ Ð·Ð°Ð²ÐµÑÑÐµÐœÐœÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ°. Ð¢ÐŸÐ»ÑÐºÐŸ Ð¿ÐŸÑÐ»Ðµ ÑÑÐŸÐ³ÐŸ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÑÑ ÐºÐœÐžÐ³Ñ ÐŒÐŸÐ¶ÐœÐŸ ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÑÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="tables">
+<Title>
+<Text id="165">Ð¢Ð°Ð±Ð»ÐžÑÑ</Text>
+</Title>
+<Content>
+<Text id="166">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐÐ Ð¡ Ð¿Ð»ÐŸÑ
+ÐŸ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑÑÑ Ñ ÑÐ°Ð±Ð»ÐžÑÐ°ÐŒÐž. ÐÐŸÐ»ÐµÐµ ÑÐŸÐ³ÐŸ, ÑÐ°Ð±Ð»ÐžÑÑ ÑÑÑÐŽÐœÐŸ Ð¿ÑÐŸÐ²ÐµÑÑÑÑ. ÐÐœÐž ÑÐŸÐŽÐµÑÐ¶Ð°Ñ ÐŒÐœÐŸÐ³ÐŸ ÑÐžÑÑ Ðž ÑÐ°ÐºÐžÐµ ÑÐžÐŒÐ²ÐŸÐ»Ñ, ÐºÐ°Ðº ÑÐŸÑÐºÐž, Ð·Ð°Ð¿ÑÑÑÐµ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸ ÐŸÑÐžÐ±ÐºÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¿ÐµÑÐµÐœÐµÑÐµÐœÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐŸÐ¹ Ð² ÐŽÑÑÐ³ÐŸÐ¹ ÑÑÐŸÐ»Ð±ÐµÑ ÐžÐ»Ðž ÑÑÑÐŸÐºÑ. ÐÐŸÑÑÐŸÐŒÑ Ð¿ÑÐž Ð¿ÑÐŸÐ²ÐµÑÐºÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ, ÑÐ¿ÐŸÑÐœÐ°Ñ ÑÐ°Ð±ÐŸÑÐ°, ÑÐµÑÐ¿ÐµÐœÐžÐµ Ðž ÐºÐŸÐœÑÑÐŸÐ»Ñ ÐºÐ°ÑÐµÑÑÐ²Ð°. Ð¡ ÐœÐžÐŒÐž ÐŒÐŸÐ¶ÐœÐŸ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÑÑÐµÐŒÑ ÐŸÐ±ÑÑÐœÑÐŒÐž ÑÐ¿ÐŸÑÐŸÐ±Ð°ÐŒÐž.</Text>
+<Text id="167">ÐÐµÑÐ²ÑÐ¹ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ ÑÐ°Ð±Ð»ÐžÑÐ°ÐŒÐž ÐºÐ°Ðº Ñ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµÐŒ. Ð­ÑÐŸ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð² ÑÐµÐ±Ñ ÑÐµÑÐœÐŸ-Ð±ÐµÐ»ÐŸÐµ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐ¹ ÑÐ°Ð±Ð»ÐžÑ Ðž Ð¿ÐµÑÐµÐœÐŸÑ ÐžÑ
+ Ð² ÑÑÐŸÐ¹ ÑÐŸÑÐŒÐµ Ð² ÐœÑÐ¶ÐœÐŸÐµ ÐŒÐµÑÑÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð­ÑÐŸ ÑÐ°ÐŒÑÐ¹ Ð»ÐµÐ³ÐºÐžÐ¹ Ð¿ÑÑÑ. ÐÐµ Ð±ÑÐŽÐµÑ ÐœÐžÐºÐ°ÐºÐžÑ
+ ÐŸÑÐžÐ±ÐŸÐº, Ðž Ð²ÑÐµ Ð¿ÐŸÑÑÐ°ÑÐµÐœÐœÐŸÐµ Ð²ÑÐµÐŒÑ ÑÐ¹ÐŽÐµÑ ÑÐŸÐ»ÑÐºÐŸ ÐœÐ° ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ. ÐÐŽÐœÐ°ÐºÐŸ, Ð¿ÐŸÐ»ÑÑÐµÐœÐœÑÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÐ°Ð±Ð»ÐžÑ Ð±ÑÐŽÑÑ Ð·Ð°ÐœÐžÐŒÐ°ÑÑ Ð±ÐŸÐ»ÑÑÐµ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐœÐŸÐ¹ Ð¿Ð°ÐŒÑÑÐž. Ð¢Ð°ÐºÐ¶Ðµ ÑÐ°Ð·ÑÐµÑÐµÐœÐžÐµ ÑÐºÑÐ°ÐœÐ° ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ° ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐœÐµÐŽÐŸÑÑÐ°ÑÐŸÑÐœÑÐŒ Ð¿ÑÐž Ð²ÑÐ²ÐŸÐŽÐµ ÐœÐ° ÑÐºÑÐ°Ðœ Ð±ÐŸÐ»ÑÑÐžÑ
+ ÑÐ°Ð±Ð»ÐžÑ. ÐÑÐ»Ðž Ð²Ñ Ð·Ð°Ñ
+ÐŸÑÐžÑÐµ ÑÐ°Ð·ÐŒÐµÑÑÐžÑÑ Ð²ÑÑ ÑÐ°Ð±Ð»ÐžÑÑ ÐœÐ° ÑÐºÑÐ°ÐœÐµ, ÑÐŸ ÑÐ°Ð·ÑÐµÑÐµÐœÐžÐµ ÑÐºÑÐ°ÐœÐ° ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐœÐµÐŽÐŸÑÑÐ°ÑÐŸÑÐœÑÐŒ. ÐÑÐ»Ðž ÑÐ°Ð±Ð»ÐžÑÐ° ÑÐ»ÐžÑÐºÐŸÐŒ ÑÐžÑÐŸÐºÐ°, ÑÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð¿ÑÐžÐŽÐµÑÑÑ Ð¿ÑÐŸÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑ Ð²ÑÐµ ÐºÐŸÐ»ÐŸÐœÐºÐž Ðž ÑÑÑÐŸÐºÐž, ÐœÐµ Ð²ÐžÐŽÑ ÐžÑ
+ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹.</Text>
+<Text id="168">ÐÑÐŸÑÐŸÐ¹ ÐŒÐµÑÐŸÐŽ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÑÐ°Ð±Ð»ÐžÑ Ð²ÑÑÑÐœÑÑ, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÐ² ÐœÑÐ¶ÐœÐŸÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÑÑÑÐŸÐº Ðž ÑÑÐŸÐ»Ð±ÑÐŸÐ², Ðž Ð²ÑÑÑÐœÑÑ Ð²Ð¿ÐµÑÐ°ÑÐ°ÑÑ Ð² ÐœÐžÑ
+ ÐŽÐ°ÐœÐœÑÐµ.</Text>
+<Text id="169">Ð¢ÑÐµÑÐžÐ¹ ÑÐ¿ÐŸÑÐŸÐ± Ð·Ð°ÐºÐ»ÑÑÐ°ÐµÑÑÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ ÑÐ°Ð±Ð»ÐžÑÑ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÑÐŸÐ²ÐµÑÑÐž ÑÐµÑÐµÐ· ÐÐ Ð¡. Ð­ÑÐŸ ÑÐŸÑ
+ÑÐ°ÐœÐžÑ Ð±ÐŸÐ»ÑÑÐµ Ð²ÑÐµÐŒÐµÐœÐž, ÑÐµÐŒ Ð²ÑÐŸÑÐŸÐ¹ ÐŒÐµÑÐŸÐŽ, ÐœÐŸ Ð¿ÐŸÑÐµÐœÑÐžÐ°Ð»ÑÐœÐŸÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÐŸÑÐžÐ±ÐŸÐº ÑÐ²ÐµÐ»ÐžÑÐžÑÑÑ. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐºÐŸÐ»ÐŸÐœÐºÐž ÐžÐœÐŸÐ³ÐŽÐ° ÑÐ»ÐžÐ²Ð°ÑÑÑÑ, Ð° ÐžÐœÐŸÐ³ÐŽÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐµ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°ÐµÑ ÑÐŸÑÐºÐž Ðž Ð·Ð°Ð¿ÑÑÑÐµ.</Text>
+</Content>
+</Subsection>
+<Subsection id="images">
+<Title>
+<Text id="170">ÐÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="171">ÐÐŸÐºÑÐŒÐµÐœÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ ÑÑÐž ÐŸÑÐœÐŸÐ²ÐœÑÑ
+ Ð²ÐžÐŽÐ° ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐ¹:</Text>
+<BulletList>
+<Bullet>
+<Text id="172">Ð§ÐµÑÐœÐŸ- Ð±ÐµÐ»ÑÐµ ÑÐžÑÑÐœÐºÐž</Text>
+</Bullet>
+<Bullet>
+<Text id="173">Ð§ÐµÑÐœÐŸ-Ð±ÐµÐ»ÑÐµ ÑÐŸÑÐŸÐ³ÑÐ°ÑÐžÐž</Text>
+</Bullet>
+<Bullet>
+<Text id="174">ÐŠÐ²ÐµÑÐœÑÐµ ÑÐŸÑÐŸÐ³ÑÐ°ÑÐžÐž</Text>
+</Bullet>
+</BulletList>
+<Text id="175">Ð§ÐµÑÐœÐŸ-Ð±ÐµÐ»ÑÐµ ÑÐžÑÑÐœÐºÐž ÑÐ»ÐµÐŽÑÐµÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ Ð² ÑÑÑÐžÑ
+ÐŸÐ²ÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ (line art mode) Ðž Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÐŸ ÑÐŸÑ
+ÑÐ°ÐœÑÑÑ Ð² Ð²ÐžÐŽÐµ ÑÐ°Ð¹Ð»ÐŸÐ² GIF ÐžÐ»Ðž PNG. Ð§ÐµÑÐœÐŸÐ±ÐµÐ»ÑÐµ ÑÐŸÑÐŸÐ³ÑÐ°ÑÐžÐž ÑÐ»ÐµÐŽÑÐµÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ Ð² ÑÐµÐ¶ÐžÐŒÐµ grayscale Ðž ÑÐŸÑ
+ÑÐ°ÐœÑÑÑ ÐºÐ°Ðº ÑÐ°Ð¹Ð»Ñ GIF ÐžÐ»Ðž JPEG. ÐŠÐ²ÐµÑÐœÑÐµ ÑÐŸÑÐŸÐ³ÑÐ°ÑÐžÐž ÐœÑÐ¶ÐœÐŸ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ Ð² ÑÐ²ÐµÑÐœÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ Ðž ÑÐŸÑ
+ÑÐ°ÐœÑÑÑ ÐºÐ°Ðº ÑÐ°Ð¹Ð»Ñ JPEG. ÐÐ±ÑÑÐœÐŸ ÑÐ°Ð¹Ð» JPEG ÑÑÐµÐŽÐœÐµÐ³ÐŸ ÐºÐ°ÑÐµÑÑÐ²Ð° ÐžÐŒÐµÐµÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÐµ ÑÐ°Ð·ÑÐµÑÐµÐœÐžÐµ.</Text>
+<Text id="176">ÐÐœÐŸÐ³ÐžÐµ ÑÐžÑÑÐœÐºÐž Ð·Ð°ÐœÐžÐŒÐ°ÑÑ ÐœÐ°ÐžÐ±ÐŸÐ»ÑÑÐµÐµ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²ÐŸ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÐŸÐ¹ ÐœÐ° Ð¶ÐµÑÑÐºÐŸÐŒ ÐŽÐžÑÐºÐµ ÐžÐ»Ðž ÐœÐ° CD-ROM. ÐÐŸÑÑÐŸÐŒÑ ÐŸÑÐµÐœÑ Ð²Ð°Ð¶ÐœÐŸ ÐŸÐ¿ÑÐžÐŒÐžÐ·ÐžÑÐŸÐ²Ð°ÑÑ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ, ÑÐŽÐµÐ»Ð°Ð² ÐµÐ³ÐŸ ÐºÐ°Ðº ÐŒÐŸÐ¶ÐœÐŸ ÑÐ°Ð·Ð±ÐŸÑÑÐžÐ²ÐµÐµ Ðž ÑÐµÑÑÐµ, Ð² ÑÐŸ Ð¶Ðµ Ð²ÑÐµÐŒÑ ÑÐŒÐµÐœÑÑÐ°Ñ ÐµÐ³ÐŸ ÑÐ°Ð·ÐŒÐµÑ. ÐÐ»Ñ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐžÑ ÐŒÐµÑÑÐ° Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐžÑÐµÐ»ÑÐœÐµÐµ ÐœÐµ Ð²ÐºÐ»ÑÑÐ°ÑÑ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ, ÐœÐµ ÐŸÑÐœÐŸÑÑÑÐžÐµÑÑ Ðº ÑÐµÐºÑÑÑ.</Text>
+<Text id="177">Ð ÐžÑÑÐœÐºÐž ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÑ ÐºÐ°Ð¶ÐŽÑÐ¹ Ð¿ÐŸ ÐŸÑÐŽÐµÐ»ÑÐœÐŸÑÑÐž. ÐÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ ÐœÐ°Ð·ÑÐ²Ð°ÑÑ ÑÑÐž ÑÐžÑÑÐœÐºÐž Ð¿ÐµÑÐ²ÑÐŒÐž 6 Ð±ÑÐºÐ²Ð°ÐŒÐž ÐœÐ°Ð·Ð²Ð°ÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, Ð° ÐŸÑÑÐ°Ð»ÑÐœÑÐŒÐž ÑÐžÑÑÐ°ÐŒÐž ÐœÐŸÐŒÐµÑ ÑÑÑÐ°ÐœÐžÑÑ, ÐœÐ° ÐºÐŸÑÐŸÑÐŸÐ¹ ÐŸÐœ ÑÐ°ÑÐ¿ÐŸÐ»Ð°Ð³Ð°ÐµÑÑÑ. Ð ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²Ñ, Ð¿ÑÐµÐŽÐ¿ÐŸÐ»Ð°Ð³Ð°Ñ, ÑÑÐŸ ÐºÐ°Ð¶ÐŽÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÑÐ²ÐŸÐµÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÑÐŸÑÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð±ÑÐºÐ²Ñ, Ð¿ÐŸÑÐ»Ðµ ÑÐµÐ³ÐŸ ÐžÐŽÐµÑ ÑÑÑÐ°ÐœÐžÑÐ°, ÐœÐ° ÐºÐŸÑÐŸÑÐŸÐ¹ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÑÑÐŸ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ. ÐÑÐ»Ðž ÐœÐ° ÐŸÐŽÐœÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ ÑÑÑÐµÑÑÐ²ÑÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐžÑÑÐœÐºÐŸÐ², ÑÐŸ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐŽÑÑÐ³ÐžÐµ Ð±ÑÐºÐ²Ñ ÐŽÐ»Ñ ÐžÑ
+ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐžÑ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐµÑÐ»Ðž ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ Ð² ÑÐŸÑÐŒÐ°ÑÐµ JPEG Ð¿ÐŸÑÐ²ÐžÑÑÑ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ 36 Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐžÂ <i>u7548Ðµ</i>, ÑÐŸ ÐŸÐœÐŸ Ð±ÑÐŽÐµÑ Ð¿ÐŸÐŒÐµÑÐµÐœÐŸ Ð² ÑÐ°Ð¹Ð» ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÐ¹Â <i>u7548e36.jpg</i>Â ÐžÐ»ÐžÂ <i>p36.jpg</i>.</Text>
+<Text id="178">ÐÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÑ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÐ¿ÐµÑÐžÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŽÐ»Ñ ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐ°Ð·ÐŒÐµÑÐ° Ðž ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÑ ÑÐžÑÑÐœÐºÐ°.</Text>
+</Content>
+</Subsection>
+<Subsection id="specialized_material">
+<Title>
+<Text id="179">Ð¡Ð¿ÐµÑÐžÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ ÐŒÐ°ÑÐµÑÐžÐ°Ð»</Text>
+</Title>
+<Content>
+<Text id="180">ÐÐœÐŸÐ³ÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ ÑÐµÑ
+ÐœÐžÑÐµÑÐºÐžÐµ ÑÐµÑÐŒÐžÐœÑ, ÑÐ°ÐºÐžÐµ ÐºÐ°Ðº ÑÐ¿ÐµÑÐžÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÑÐžÐŒÐ²ÐŸÐ»Ñ, ÑÐŸÑÐŒÑÐ»Ñ Ðž ÐœÐµÑÐ°Ð·Ð±ÐŸÑÑÐžÐ²ÑÐµ ÑÑÑÐ°ÐœÐžÑÑ. Ð­ÑÐž ÑÑÑÐŽÐœÐŸ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐµÐŒÑÐµ ÑÐžÐŒÐ²ÐŸÐ»Ñ, ÐºÐ°Ðº Ð¿ÑÐ°Ð²ÐžÐ»ÐŸ, ÑÐ²ÑÐ·Ð°ÐœÑ Ñ ÑÐ°Ð·ÐœÑÐŒÐž ÑÐ·ÑÐ¿ÑÐ°ÐŒÐž. ÐÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð²ÑÐ±ÑÐ°ÑÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐ¹ ÑÐ·ÑÐº Ð² ÐŸÐ¿ÑÐžÑÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐÐ Ð¡. Ð€ÐŸÑÐŒÑÐ»Ñ ÐœÑÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ Ð¿ÐµÑÐµÐ¿ÐµÑÐ°ÑÑÐ²Ð°ÑÑ Ð²ÑÑÑÐœÑÑ, ÑÐ°Ðº ÐºÐ°Ðº Ð²ÐŸ ÐŒÐœÐŸÐ³ÐžÑ
+ ÑÐ»ÑÑÐ°ÑÑ
+ ÐÐ Ð¡ ÐžÑ
+ ÐœÐµ ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°ÐµÑ, Ðž ÐžÑ
+ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð²Ð²ÐŸÐŽÐžÑÑ Ð² Word. ÐÐµÑÐ°Ð·Ð±ÐŸÑÑÐžÐ²ÑÐµ ÑÑÑÐ°ÐœÐžÑÑ ÐŒÐŸÐ³ÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÐŒÐ°ÑÐµÑÐžÐ°Ð», ÐºÐŸÑÐŸÑÑÐ¹ ÑÑÑÐŽÐœÐŸ Ð²ÐŸÑÐ¿ÑÐŸÐžÐ·Ð²ÐµÑÑÐž ÐžÐ·-Ð·Ð° ÐºÐ°ÐºÐžÑ
+-Ð»ÐžÐ±ÐŸ Ð¿ÐŸÐ²ÑÐµÐ¶ÐŽÐµÐœÐžÐ¹ Ðž Ñ.ÐŽ., Ð¿ÐŸÑÑÐŸÐŒÑ ÑÐ°ÐºÐžÐµ ÐŒÐµÑÑÐ° Ð¿ÑÐžÐŽÐµÑÑÑ Ð¿ÐµÑÐµÐ¿ÐµÑÐ°ÑÑÐ²Ð°ÑÑ.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="productivity_and_resources_1">
+<Title>
+<Text id="181">ÐÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÑÐœÐŸÑÑÑ Ðž ÐŽÐŸÑÑÑÐ¿ÐœÑÐµ ÑÐµÑÑÑÑÑ</Text>
+</Title>
+<Content>
+<Text id="182">ÐÐ°Ðº Ð±ÑÐ»ÐŸ ÑÐ¿ÐŸÐŒÑÐœÑÑÐŸ ÑÐ°ÐœÐµÐµ, Ð²Ñ ÐœÐµ ÐŽÐŸÐ»Ð¶ÐœÑ ÐœÐµÐŽÐŸÐŸÑÐµÐœÐžÐ²Ð°ÑÑ ÑÐ»ÐŸÐ¶ÐœÐŸÑÑÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÐÐ Ð¡. Ð¥ÐŸÑÑ Ð¿ÑÐŸÑÐµÑÑ ÐÐ Ð¡ ÐœÑÐ¶ÐœÐŸ ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑ ÐŸÑÐŽÐµÐ»ÑÐœÐŸ ÐŸÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐŽÐ»Ñ ÐµÐ³ÐŸ ÐŸÑÐµÐœÐºÐž Ð¿ÑÐžÐŒÐµÐœÑÑÑÑÑ ÑÑ
+ÐŸÐ¶ÐžÐµ Ð¿ÑÐ°ÐºÑÐžÑÐµÑÐºÐžÐµ ÑÐµÐºÐŸÐŒÐµÐœÐŽÐ°ÑÐžÐž: ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÐµ ÑÐµÑÑÑÑÑ ÐŽÐ»Ñ Ð¿ÑÐžÐŸÐ±ÑÐµÑÐµÐœÐžÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐŸÐ², ÐŽÐŸÑÑÑÐ¿ÐœÐŸÑÑÑ ÑÐ°Ð±ÐŸÑÐµÐ¹ ÑÐžÐ»Ñ Ðž ÑÐŒÐµÐœÐžÐµ ÑÑÐºÐŸÐ²ÐŸÐŽÐžÑÑ; Ð·Ð°ÑÐ¿Ð»Ð°ÑÐ°; ÐŸÐ±ÑÐµÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÑÑÑÐ°ÐœÐžÑ, ÐœÑÐ¶ÐŽÐ°ÑÑÐžÑ
+ÑÑ Ð² ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐµ; ÐŒÐŸÐ¶ÐœÐŸ Ð»Ðž Ð¿ÐµÑÐµÐŽÐ°Ð²Ð°ÑÑ ÑÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÑÐµÑÑÐžÐŒ Ð»ÐžÑÐ°ÐŒ.</Text>
+<Text id="183">Ð ÑÐ»ÐµÐŽÑÑÑÐžÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŒÑ Ð¿ÐŸÐŽÐµÐ»ÐžÐŒÑÑ Ñ Ð²Ð°ÐŒÐž ÐœÐ°ÑÐžÐŒ ÐŸÐ¿ÑÑÐŸÐŒ ÑÐ°Ð±ÐŸÑÑ Ñ ÐÐ Ð¡ Ð² ÑÐ°ÐºÐžÑ
+ ÑÑÑÐ°ÐœÐ°Ñ
+, ÐºÐ°Ðº ÐÐµÐ»ÑÐ³ÐžÑ, ÐÐœÐŽÐžÑ Ðž Ð ÑÐŒÑÐœÐžÑ. ÐÑÐµ ÐžÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ, Ð¿ÐŸÐŽÑÑÐµÑÑ Ðž ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÑ ÐŽÐ»Ñ ÑÐžÐ¿ÐžÑÐœÑÑ
+ ÑÑÐ»ÐŸÐ²ÐžÐ¹ - ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÑÐµÐŽÐœÐµÐ¹ ÑÐ»ÐŸÐ¶ÐœÐŸÑÑÐž (Ð²ÐºÐ»ÑÑÐ°Ñ ÑÐ°Ð±Ð»ÐžÑÑ Ðž ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ), ÐºÐŸÑÐŸÑÑÐµ Ð²ÑÑÑÐµÑÐ°ÑÑÑÑ Ð² Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²Ðµ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐº Ðž Ð°ÑÑ
+ÐžÐ²ÐŸÐ², Ð²ÑÑÐŸÐºÐŸÐµ ÐºÐ°ÑÐµÑÑÐ²ÐŸ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² Ðž ÑÑÐµÐŽÐœÑÑ-ÐŽÐŸÐ»Ð³Ð°Ñ ÐŽÐ»ÐžÑÐµÐ»ÑÐœÐŸÑÑÑ ÑÐ°Ð±ÐŸÑÑ.</Text>
+<Subsection id="intensive_ocr">
+<Title>
+<Text id="184">ÐÐœÑÐµÐœÑÐžÐ²ÐœÑÐ¹ ÐÐ Ð¡</Text>
+</Title>
+<Content>
+<Text id="185">ÐÑÐŸÑÐµÑÑ ÐÐ Ð¡ ÑÐ²Ð»ÑÐµÑÑÑ ÑÑÑÐŽÐœÑÐŒ. ÐÐœ ÑÑÐµÐ±ÑÐµÑ Ð±ÐŸÐ»ÑÑÐŸÐ¹ ÐºÐŸÐœÑÐµÐœÑÑÐ°ÑÐžÐž Ð²ÐœÐžÐŒÐ°ÐœÐžÑ Ðž ÑÐŒÐµÐœÐžÑ. ÐÐµÑÐµÐŽ Ð¿ÐŸÐ¿ÑÑÐºÐŸÐ¹ ÐŽÐŸÑÑÐžÐ³ÐœÑÑÑ ÐŒÐ°ÐºÑÐžÐŒÐ°Ð»ÑÐœÑÑ
+ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² ÑÑÐµÐ±ÑÐµÑÑÑ Ð¿ÐŸÑÑÐŽÐºÐ° 6 ÐœÐµÐŽÐµÐ»Ñ ÑÐ°Ð±ÐŸÑÑ, Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÐºÐŸÑÐŸÑÐŸÐ¹ ÐžÐŽÐµÑ ÐœÐ°ÑÐ°ÑÑÐ°ÐœÐžÐµ ÐŸÐ¿ÑÑÐ°.</Text>
+<Text id="186">ÐÐ±ÑÑÐœÐŸ ÐŒÐ°ÐºÑÐžÐŒÐ°Ð»ÑÐœÐ°Ñ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÑÐœÐŸÑÑÑ ÐŽÐŸÑÑÐžÐ³Ð°ÐµÑÑÑ Ð² Ð¿ÐµÑÐ²ÑÐµ ÑÐ°ÑÑ ÐœÐ°ÑÐ°Ð»Ð° ÐŽÐœÑ. ÐÐŸÑÐ»Ðµ ÑÑÐµÑ
+ ÑÐ°ÑÐŸÐ² ÑÐ°Ð±ÐŸÑÑ Ñ ÐÐ Ð¡ ÐŸÐœÐ° ÑÐµÐ·ÐºÐŸ Ð¿Ð°ÐŽÐ°ÐµÑ, Ð¿ÑÐžÐŒÐµÑÐœÐŸ ÐœÐ° 50% ÐŸÑ ÐœÐ°ÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ. ÐÐŸÑÐ»Ðµ 6 ÑÐ°ÑÐŸÐ² Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ Ð»ÑÐŽÐµÐ¹ ÐŸÑÐµÐœÑ ÑÑÑÐ°ÑÑ.</Text>
+<Text id="187">Ð¢ÐŸ Ð¶Ðµ ÑÐ°ÐŒÐŸÐµ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ Ð² ÑÐµÑÐµÐœÐžÐµ Ð¿ÐµÑÐ²ÑÑ
+ ÐœÐµÐŽÐµÐ»Ñ ÑÐ°Ð±ÐŸÑÑ. Ð Ð¿ÐµÑÐ²ÑÐµ ÐœÐµÐŽÐµÐ»Ðž Ð¿ÑÐŸÐŽÑÐºÑÐžÐ²ÐœÐŸÑÑÑ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐœÐ° Ð²ÑÑÐŸÐºÐŸÐŒ ÑÑÐŸÐ²ÐœÐµ, ÐœÐŸ Ð¿ÐŸÑÐ»Ðµ ÑÑÐŸÐ³ÐŸ 2/3 Ð»ÑÐŽÐµÐ¹ ÑÑÑÐ°ÑÑ Ðž ÑÐµÑÑÑÑ ÐžÐœÑÐµÑÐµÑ Ðº ÑÐ°Ð±ÐŸÑÐµ. Ð¢Ð°ÐºÐžÐµ Ð»ÑÐŽÐž Ð»ÐžÐ±ÐŸ ÑÑ
+ÐŸÐŽÑÑ, Ð»ÐžÐ±ÐŸ Ð¿ÑÐŸÐŽÐŸÐ»Ð¶Ð°ÑÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐœÐ° ÐŸÑÐµÐœÑ ÐœÐžÐ·ÐºÐŸÐŒ ÑÑÐŸÐ²ÐœÐµ, Ð²Ð»ÐžÑÑÑÐµÐŒ ÐœÐ° ÐºÐ°ÑÐµÑÑÐ²ÐŸ Ðž Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÑÐœÐŸÑÑÑ. ÐÐ°Ð¶Ðµ ÑÐµ, ÐºÑÐŸ Ð²ÑÑÑÐŸÑÐ» ÐºÑÐžÑÐžÑÐµÑÐºÐžÐµ 1-5 ÐœÐµÐŽÐµÐ»Ñ Ðž ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ ÑÐ°ÑÑÑÑ ÑÐ°Ð±ÐŸÑÐµÐ¹ ÐºÐŸÐŒÐ°ÐœÐŽÑ, ÑÐ°ÑÑÐŸ ÑÑ
+ÐŸÐŽÑÑ Ð² Ð¿ÐŸÐžÑÐºÐ°Ñ
+ Ð»ÑÑÑÐµÐ¹ ÑÐ°Ð±ÐŸÑÑ Ð² Ð¿ÑÐŸÐŒÐµÐ¶ÑÑÐºÐµ 6-12 ÐŒÐµÑÑÑÐµÐ².</Text>
+<Text id="188">ÐÐ°ÐŒÐµÑÐºÐž, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÑÐŽÐµÐ»Ð°ÐœÑ Ð² ÑÐ°ÑÑÐž <CrossRef target="Section" ref="the_ocr_process"/> ÐŸ ÑÐ°Ð±ÐŸÑÐµÐ¹ ÑÐžÐ»Ðµ, ÐŸÑÐœÐŸÑÑÑÑÑ Ð² ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž Ðº ÐžÐœÑÐµÐœÑÐžÐ²ÐœÐŸÐŒÑ ÐÐ Ð¡. ÐÐŸÐœÑÑÐŸÐ»Ñ ÐºÐ°ÑÐµÑÑÐ²Ð° Ð»ÑÑÑÐµ Ð¿ÐŸÑÑÑÐ°ÑÑ Ð»ÑÐŽÑÐŒ, ÑÐµÐ¹ ÑÐŸÐŽÐœÐŸÐ¹ ÑÐ·ÑÐº ÑÐ²Ð»ÑÐµÑÑÑ ÑÐµÐŒ Ð¶Ðµ, ÐœÐ° ÐºÐŸÑÐŸÑÐŸÐŒ ÐœÐ°Ð¿ÐžÑÐ°Ðœ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐžÐ»Ðž ÐŸÐœÐž Ð²Ð»Ð°ÐŽÐµÑÑ ÑÑÐžÐŒ ÑÐ·ÑÐºÐŸÐŒ Ð² ÑÐŸÐ²ÐµÑÑÐµÐœÑÑÐ²Ðµ. ÐÑÑÑÐžÐµ ÑÐ°Ð±ÐŸÑÐœÐžÐºÐž - ÑÑÐŸ ÑÐºÐŸÐ»ÑÐœÐžÐºÐž Ðž ÑÑÑÐŽÐµÐœÑÑ, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÐŒÐŸÐ»ÐŸÐŽÑÐµ Ð»ÑÐŽÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð±ÐŸÐ»ÐµÐµ Ð²ÐœÐžÐŒÐ°ÑÐµÐ»ÑÐœÑ Ðž Ð±ÐŸÐ»ÐµÐµ ÑÐºÐŸÐœÑÐµÐœÑÑÐžÑÐŸÐ²Ð°ÐœÑ Ð¿ÑÐž ÑÐ°ÐºÐŸÐŒ Ð²ÐžÐŽÐµ ÑÐ°Ð±ÐŸÑÑ, ÐœÐµÐ¶ÐµÐ»Ðž Ð±ÐŸÐ»ÐµÐµ Ð²Ð·ÑÐŸÑÐ»ÐŸÐµ Ð¿ÐŸÐºÐŸÐ»ÐµÐœÐžÐµ Ðž Ð¿ÐŸÐ¶ÐžÐ»ÑÐµ Ð»ÑÐŽÐž. Ð£ÑÐ»ÐŸÐ²ÐœÑÐ¹ ÐºÑÐžÑÐµÑÐžÐ¹ ÐŸÑÐ±ÐŸÑÐ° ÑÐ°ÐºÐŸÐ² - Ð»ÑÐŽÐž Ð² Ð²ÐŸÐ·ÑÐ°ÑÑÐµ ÐŸÑ 18 ÐŽÐŸ 23 Ð»ÐµÑ ÐŸÐ±ÑÑÐœÐŸ Ð»ÑÑÑÐµ Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑ ÐœÐ° ÑÐ°ÐºÑÑ ÑÐ°Ð±ÐŸÑÑ, ÐœÐµÐ¶ÐµÐ»Ðž ÑÐµ, ÐºÐŸÐŒÑ Ð±ÐŸÐ»ÑÑÐµ 25.</Text>
+<Text id="189">Ð ÐœÐ°ÐºÐŸÐœÐµÑ, Ð¿ÑÐŸÑÐµÑÑ ÐÐ Ð¡ ÐŸÑÐµÐœÑ ÑÑÑÐžÐœÐµÐœ Ðž ÑÐºÑÑÐµÐœ. ÐÐŸÑÑÐŸÐŒÑ ÐœÑÐ¶ÐœÐŸ ÐºÐ°Ðº-ÑÐŸ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑ ÑÐ°Ð±ÐŸÑÐžÐ¹ ÐŽÑÑ
+, ÐŒÐŸÑÐžÐ²Ð°ÑÐžÑ Ðž Ð¿ÑÐžÐ²ÑÐ·Ð°ÐœÐœÐŸÑÑÑ Ðº ÑÐ°Ð±ÐŸÑÐµ.</Text>
+<Text id="190">ÐÐŸÑ ÐžÑÐŸÐ³ Ð²ÑÑÐµÐ¿ÐµÑÐµÑÐžÑÐ»ÐµÐœÐœÐŸÐ³ÐŸ:</Text>
+<BulletList>
+<Bullet>
+<Text id="191">ÐÐŸÐ»ÐŸÐŽÑÐµ Ð»ÑÐŽÐž Ð² Ð²ÐŸÐ·ÑÐ°ÑÑÐ° 18-25 Ð»ÐµÑ ÑÐ°ÐŒÑÐµ Ð»ÑÑÑÐžÐµ ÐºÐ°ÐœÐŽÐžÐŽÐ°ÑÑ ÐœÐ° ÑÐ°ÐºÑÑ ÑÐ°Ð±ÐŸÑÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="192">Ð¢Ð°Ðº ÐºÐ°Ðº Ð¿ÐµÑÐ²ÑÐµ ÑÐ°ÑÑ ÑÐ°Ð±ÐŸÑÑ ÑÐ²Ð»ÑÑÑÑÑ ÑÐ°ÐŒÑÐŒÐž Ð¿ÑÐŸÐŽÑÐºÑÐžÐ²ÐœÑÐŒÐž, ÑÐ»ÐµÐŽÑÐµÑ ÐœÐ°ÐœÐžÐŒÐ°ÑÑ ÑÐ°Ð±ÐŸÑÐžÑ
+ ÐœÐ° Ð¿ÐŸÐ»-ÐŽÐœÑ, Ðž ÑÐŸÐ»ÑÐºÐŸ ÑÐ°ÐŒÑÐŒ ÑÑÐµÑÐŽÐœÑÐŒ ÑÐ°Ð±ÐŸÑÐœÐžÐºÐ°ÐŒ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÑÐµÐ»ÑÐ¹ ÑÐ°Ð±ÐŸÑÐžÐ¹ ÐŽÐµÐœÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="193">ÐÐ²Ðµ ÑÑÐµÑÐž ÑÐ°Ð±ÐŸÑÐœÐžÐºÐŸÐ² Ð¿ÐŸÐºÐžÐŽÐ°ÑÑ ÑÐ°Ð±ÐŸÑÑ ÐŸÑ ÑÑÑÐ°Ð»ÐŸÑÑÐž ÐžÐ»Ðž ÐŸÑ ÑÑÑÐžÐœÑ Ð² ÑÐµÑÐµÐœÐžÐµ 3-5 ÐœÐµÐŽÐµÐ»Ñ, Ð²ÑÐµ ÑÑÐŸ ÐŸÑÑÐ°Ð¶Ð°ÐµÑÑÑ ÐœÐ° ÑÑ
+ÑÐŽÑÐµÐœÐžÐž Ð¿ÑÐŸÐŽÑÐºÑÐžÐ²ÐœÐŸÑÑÐž Ð² ÑÑÐŸÑ Ð¿ÐµÑÐžÐŸÐŽ.</Text>
+</Bullet>
+<Bullet>
+<Text id="194">ÐÑÐ¶ÐµÐœ Ð¿ÐŸÑÑÐŸÑÐœÐœÑÐ¹ Ð¿ÑÐžÑÐŸÐº ÑÐ°Ð±ÐŸÑÐœÐžÐºÐŸÐ² ÐŽÐ»Ñ Ð¿ÐŸÐºÑÑÑÐžÑ Ð·Ð°ÑÑÐ°Ñ ÐœÐ° ÐŸÐ±ÑÑÐµÐœÐžÐµ, Ð¿ÐŸÐŽÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÑÑÐµÑÐŽÐžÑ Ðž ÑÐ°Ð±ÐŸÑÐµÐ³ÐŸ ÐŽÑÑ
+Ð°.</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Subsection>
+<Subsection id="achievable_productivity">
+<Title>
+<Text id="195">ÐÐŸÑÑÐžÐ¶ÐžÐŒÐ°Ñ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÑÐœÐŸÑÑÑ</Text>
+</Title>
+<Content>
+<Table id="table_ocr_productivity">
+<Title>
+<Text id="196">Ð¿ÑÐŸÐŽÑÐºÑÐžÐ²ÐœÐŸÑÑÑ Ð¿ÑÐŸÑÐµÑÑÐ° ÐÐ Ð¡</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="161">Â  </th>
+<th width="132">
+<Text id="197">Ð Ð°Ð±ÐŸÑÐžÐµ ÑÐ°ÑÑ/ÐŽÐµÐœÑ</Text>
+</th>
+<th width="123">
+<Text id="198">Ð¡ÑÑÐ°ÐœÐžÑÑ/ÐŽÐµÐœÑ</Text>
+</th>
+<th width="113">
+<Text id="199">Ð¡ÑÑÐ°ÐœÐžÑÑ/ÐŒÐµÑÑÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="161">
+<Text id="200">ÐÐ°ÑÐ°Ð»ÑÐœÐ°Ñ Ð¿ÐŸÐŽÐ³ÐŸÑÐŸÐ²ÐºÐ°Â <i>(6</i>Â ÐœÐµÐŽÐµÐ»Ñ)</Text>
+</th>
+<th width="132">
+<Text id="201">3</Text>
+</th>
+<th width="123">
+<Text id="202">6</Text>
+</th>
+<th width="113">
+<Text id="203">120</Text>
+</th>
+</tr>
+<tr>
+<th width="161">
+<Text id="204">ÐÐ¿ÑÐžÐŒÐ°Ð»ÑÐœÑÐ¹ ÑÑÐŸÐ²ÐµÐœÑ Ð¿ÑÐŸÐŽÑÐºÑÐžÐ²ÐœÐŸÑÑÐž</Text>
+</th>
+<th width="132">
+<Text id="205">3</Text>
+</th>
+<th width="123">
+<Text id="206">9</Text>
+</th>
+<th width="113">
+<Text id="207">150 to 200</Text>
+</th>
+</tr>
+<tr>
+<th width="161">Â </th>
+<th width="132">
+<Text id="208">7</Text>
+</th>
+<th width="123">
+<Text id="209">28</Text>
+</th>
+<th width="113">
+<Text id="210">500 to 600</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="211">Ð Ð¢Ð°Ð±Ð»ÐžÑÐµ <CrossRef target="Table" ref="table_ocr_productivity"/> Ð¿ÑÐžÐ²ÐµÐŽÐµÐœÑ ÑÑÐµÐŽÐœÐžÐµ ÑÐžÑÑÑ Ð¿ÑÐŸÐŽÑÐºÑÐžÐ²ÐœÐŸÑÑÐž ÑÐ°Ð±ÐŸÑÑ ÐœÐ° ÐÐ Ð¡. ÐÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÑÐžÑ
+ÐŸÐŽÑÑ ÑÐ°Ð·ÐœÑÐŒÐž Ðž Ð¿ÐŸ ÑÐ°Ð·ÐŒÐµÑÑ, Ðž Ð¿ÐŸ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ. ÐÑÐž ÑÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÐž ÑÑÐŸÐ¹ ÑÐ°Ð±Ð»ÐžÑÑ Ð±ÑÐ»Ðž ÑÑÑÐµÐœÑ ÑÐ°ÐºÐžÐµ ÑÐ°ÐºÑÐŸÑÑ, ÐºÐ°Ðº ÑÐ°Ð·ÐœÐŸÐŸÐ±ÑÐ°Ð·ÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÑ
+ ÑÑÐµÐŽÐœÐµÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐ¹ Ðž ÑÐ°Ð±Ð»ÐžÑ - Ðº Ð¿ÑÐžÐŒÐµÑÑ ÐŸÐŽÐžÐœ ÑÐžÑÑÐœÐŸÐº Ðž ÐŸÐŽÐœÐ° ÑÐ°Ð±Ð»ÐžÑÐ° 5 ÐœÐ° 5 ÐœÐ° ÐºÐ°Ð¶ÐŽÑÐµ Ð²ÐŸÑÐµÐŒÑ ÑÑÑÐ°ÐœÐžÑ. Ð¢Ð°ÐºÐ¶Ðµ Ð¿ÑÐµÐŽÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐŸ, ÑÑÐŸ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÐ²Ð»ÑÑÑÑÑ ÑÑÐµÐŽÐœÐµÐ³ÐŸ-Ð²ÑÑÐŸÐºÐŸÐ³ÐŸ ÐºÐ°ÑÐµÑÑÐ²Ð°. ÐÐ°ÐŒÐµÑÑÑÐµ, ÐºÐ°Ðº ÑÑÐŸ Ð±ÑÐ»ÐŸ ÑÐ¶Ðµ ÑÐ°ÑÑÐŒÐŸÑÑÐµÐœÐŸ, ÑÑÐŸ ÑÑÐŸ Ð·Ð°Ð²ÐžÑÐžÑ ÐŸÑ ÐºÐ°ÑÐµÑÑÐ²Ð° ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž ÑÐ°ÐºÐ¶Ðµ ÐŸÑ ÑÐŸÐ³ÐŸ, ÐœÐ°ÑÐºÐŸÐ»ÑÐºÐŸ Ñ
+ÐŸÑÐŸÑÐŸ ÑÐ°Ð±ÐŸÑÐœÐžÐºÐž Ð·ÐœÐ°ÑÑ ÑÐ·ÑÐº, ÐœÐ° ÐºÐŸÑÐŸÑÐŸÐŒ ÐœÐ°Ð¿ÐžÑÐ°ÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ.</Text>
+<Text id="212">Ð ÑÐ°Ð±Ð»ÐžÑÐµ ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐžÐ²ÐµÐŽÐµÐœÑ ÐŽÐ°ÐœÐœÑÐµ ÐŸ ÑÐµÑ
+, ÐºÑÐŸ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÐŸÐ±ÑÑÐµÐœÐžÑ, Ðž ÑÐµÑ
+, ÐºÐŸÑÐŸÑÑÐµ ÑÐ¶Ðµ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ð² ÐŸÐ¿ÑÐžÐŒÐ°Ð»ÑÐœÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ. ÐÑÐ»Ðž ÑÐ»ÐµÐœ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐµÐ¹ ÐºÐŸÐŒÐ°ÐœÐŽÑ ÑÐŽÐµÐ»ÐžÑ ÐŽÐŸ ÑÑÐµÑ
+ ÑÐ°ÑÐŸÐ² Ð² ÐŽÐµÐœÑ ÐœÐ° Ð¿ÑÐŸÑÐµÑÑ ÐÐ Ð¡, ÑÐŸ ÐŸÐœ ÐŒÐŸÐ¶ÐµÑ ÐŽÐŸÑÑÐžÐ³ÐœÑÑÑ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐ° 180-200 ÑÑÑÐ°ÐœÐžÑ Ð² ÐŒÐµÑÑÑ. ÐÐ»Ñ Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð±ÐŸÑÐœÐžÐºÐ°, Ð¿ÑÐŸÑÐµÐŽÑÐµÐ³ÐŸ Ñ
+ÐŸÑÐŸÑÑÑ Ð¿ÐŸÐŽÐ³ÐŸÑÐŸÐ²ÐºÑ, Ñ Ð²ÑÑÐŸÐºÐŸÐ¹ Ð²ÐœÐžÐŒÐ°ÑÐµÐ»ÑÐœÐŸÑÑÑÑ Ðž ÐŸÑÐŽÐ°ÑÐµÐ¹ ÐŽÐŸÑÑÐžÐ³ÐœÑÑÑ 500-600 ÑÑÑÐ°ÐœÐžÑ Ð² ÐŒÐµÑÑÑ ÐœÐµ Ð±ÑÐŽÐµÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐŸÐ¹.</Text>
+<Text id="213">Ð¢ÐµÐŒ ÐœÐµ ÐŒÐµÐœÐµÐµ, Ñ ÐœÐµÑÐ°Ð·Ð±ÐŸÑÑÐžÐ²ÑÐŒÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒÐž Ð¿Ð»ÐŸÑ
+ÐŸÐ³ÐŸ ÐºÐ°ÑÐµÑÑÐ²Ð° Ðž ÐžÐ·ÐŸÐ±ÐžÐ»ÐžÐµÐŒ ÑÐ°Ð±Ð»ÐžÑ Ðž ÑÐžÑÑÐœÐºÐŸÐ² ÑÑÐž ÑÐžÑÑÑ Ð±ÑÐŽÑÑ ÐœÐžÐ¶Ðµ â ÐœÐ°Ð²ÐµÑÐœÐŸÐµ 300-400 ÑÑÑÐ°ÐœÐžÑ ÐŽÐ»Ñ Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð±ÐŸÑÐœÐžÐºÐ°.</Text>
+<Text id="214">ÐÑÐµÐŽÑÑÐ°Ð²ÑÑÐµ, ÑÑÐŸ Ð·Ð°ÑÐ¿Ð»Ð°ÑÐ° ÐŽÐ»Ñ ÐŒÐŸÑÐžÐ²ÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐ³ÐŸ Ð¿ÐŸÑÑÐŸÑÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð±ÐŸÑÐœÐžÐºÐ° ÑÐŸÑÑÐ°Ð²Ð»ÑÐµÑ $400 Ð² ÐŒÐµÑÑÑ, Ð° Ð·Ð°ÑÑÐ°ÑÑ ÐœÐ° ÐŒÐµÐœÐµÐŽÐ¶ÐŒÐµÐœÑ, ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÑ, Ð°ÑÐµÐœÐŽÑ, ÐºÐŸÐŒÐŒÑÐœÐ°Ð»ÑÐœÑÐµ ÑÑÐ»ÑÐ³Ðž Ðž Ñ.ÐŽ. ÑÑÐŸÐžÑ $300-400 ÐœÐ° ÑÐµÐ»ÐŸÐ²ÐµÐºÐ° Ð² ÐŒÐµÑÑÑ. ÐÐ»Ð°ÑÐ° Ð·Ð° 1 ÑÑÑÐ°ÐœÐžÑÑ ÐÐ Ð¡ $ 1.2-1.6. Ð£ÑÐžÑÑÐ²Ð°Ñ Ð¿ÐŸÐŽÐ³ÐŸÑÐŸÐ²ÐžÑÐµÐ»ÑÐœÑÐ¹ Ð¿ÐµÑÐžÐŸÐŽ, ÐŸÐ±ÑÐžÐ¹ ÐŸÐ±ÑÐµÐŒ, Ð²ÑÐµÐŒÑ, Ð·Ð°ÑÑÐ°ÑÑ ÐœÐ° ÑÐ²ÐŸÐ»ÑÐœÐµÐœÐžÐµ Ð¿ÑÐž Ð·Ð°ÐºÑÑÑÐžÐž Ð±ÐžÐ·ÐœÐµÑÐ°, ÑÑÐž ÑÐžÑÑÑ Ð¿ÐŸÐŽÐœÐžÐŒÑÑÑÑ ÐŽÐŸ $1.5-2.5 Ð·Ð° ÑÑÑÐ°ÐœÐžÑÑ.</Text>
+<Text id="215">Ð¡ÑÐŸÐžÐŒÐŸÑÑÑÐ²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÑÐ°Ð±ÐŸÑÑ ÑÐ°ÐŒÐžÐŒ ÐœÑÐ¶ÐœÐŸ ÑÑÐ°Ð²ÐœÐžÐ²Ð°ÑÑ ÑÐŸ ÑÑÐŸÐžÐŒÐŸÑÑÑÑ, ÐµÑÐ»Ðž Ð¿ÐŸÑÑÑÐžÑÑ ÑÑÑ ÑÐ°Ð±ÐŸÑÑ Ð¿ÑÐŸÑÐµÑÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐŒ ÐÐ Ð¡ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÑÐŒ. ÐÐµÐ¿ÑÐ°Ð²ÐžÑÐµÐ»ÑÑÑÐ²ÐµÐœÐœÐ°Ñ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑ Ð² Ð ÑÐŒÑÐœÐžÐž Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÐµÑ ÑÐ°ÐºÐžÐµ ÑÑÐ»ÑÐ³Ðž, Ðž ÑÐµÐœÐ° ÐŽÐ»Ñ Ð³ÑÐŒÐ°ÐœÐžÑÐ°ÑÐœÑÑ
+ ÐœÐµÐºÐŸÐŒÐŒÐµÑÑÐµÑÐºÐžÑ
+ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐ¹ ÐœÐžÐ¶Ðµ Ðž Ð³ÑÐ°ÐœÐžÑÐžÑ ÐŸÑ $1.2 ÐŽÐŸ $2 Ð·Ð° ÑÑÑÐ°ÐœÐžÑÑ. ÐÑÐ»Ðž Ñ Ð²Ð°Ñ ÐµÑÑÑ ÐºÐ°ÐºÐžÐµ-Ð»ÐžÐ±ÐŸ Ð²ÐŸÐ¿ÑÐŸÑÑ, Ð¿ÐžÑÐžÑÐµ ÐœÐ°ÐŒ ÐœÐ° scanning@humaninfo.org.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="alternatives_to_ocr">
+<Title>
+<Text id="216">ÐÐ»ÑÑÐµÑÐœÐ°ÑÐžÐ²Ð° ÐÐ Ð¡</Text>
+</Title>
+<Content>
+<Text id="217">Ð¡ÑÑÐµÑÑÐ²ÑÑÑ ÐŽÐ²Ðµ Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²Ñ Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐžÑ ÐÐ Ð¡.</Text>
+<Subsection id="manual_retyping">
+<Title>
+<Text id="218">Ð ÑÑÐœÐŸÐµ Ð¿ÐµÑÐµÐ¿ÐµÑÐ°ÑÑÐ²Ð°ÐœÐžÐµ</Text>
+</Title>
+<Content>
+<Text id="219">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑÐŸÑ ÐŒÐµÑÐŸÐŽ, ÐŒÐŸÐ¶ÐœÐŸ ÐœÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÐºÐ°ÐœÐµÑ Ð²ÐŸÐŸÐ±ÑÐµ, Ð¿ÑÐžÐŒÐµÐœÐžÐ² Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐµÐºÑÑÐŸÐ²ÐŸÐ¹ ÑÐµÐŽÐ°ÐºÑÐŸÑ. ÐÐŽÐžÐœÑÑÐ²ÐµÐœÐœÐŸÐµ, ÑÑÐŸ ÐŸÑÑÐ°ÑÑÑÑ ÑÐŽÐµÐ»Ð°ÑÑ, ÑÑÐŸ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ ÐŸÐ±Ð»ÐŸÐ¶ÐºÑ Ðž ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ, Ð¿ÐŸÑÑÐŸÐŒÑ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÐ±ÐŸÐ¹ÑÐžÑÑ Ð±ÐµÐ· ÐŽÐŸÑÐŸÐ³ÐžÑ
+ ÑÐºÐ°ÐœÐµÑÐŸÐ² Ðž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ ÐÐ Ð¡.</Text>
+<Text id="220">ÐÑÐŽÐž, Ð²ÑÑÐŸÐ»ÐœÑÑÑÐžÐµ ÑÑÑ ÑÐ°Ð±ÐŸÑÑ, ÐœÐµ ÐŸÐ±ÑÐ·Ð°ÑÐµÐ»ÑÐœÐŸ ÐŽÐŸÐ»Ð¶ÐœÑ Ð²ÐœÐžÐºÐ°ÑÑ Ð² ÑÑÑÑ ÑÐµÐºÑÑÐ°. ÐÑÐµ, ÑÑÐŸ ÐŸÑ ÐœÐžÑ
+ ÑÑÐµÐ±ÑÐµÑÑÑ, ÑÑÐŸ Ð°ÐºÐºÑÑÐ°ÑÐœÐŸ Ðž Ð±ÐµÐ·ÐŸÑÐžÐ±ÐŸÑÐœÐŸ Ð¿ÐµÑÐ°ÑÐ°ÑÑ ÑÐŸ, ÑÑÐŸ ÐŸÐœÐž Ð²ÐžÐŽÑÑ. Ð¢ÐµÐŒ ÐœÐµ ÐŒÐµÐœÐµÐµ, Ð¿ÐµÑÐµÐ¿ÐµÑÐ°ÑÑÐ²Ð°ÐœÐžÐµ Ð²ÐœÐŸÑÐžÑ ÐŸÑÐžÐ±ÐºÐž, Ð¿ÐŸÑÑÐŸÐŒÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŒÐµÑÐŸÐŽ ÐŽÐ²ÐŸÐ¹ÐœÐŸÐ³ÐŸ ÐœÐ°Ð±ÐŸÑÐ°. ÐÐ²Ð° ÑÐµÐ»ÐŸÐ²ÐµÐºÐ° Ð¿ÐµÑÐµÐ¿ÐµÑÐ°ÑÑÐ²Ð°ÑÑ ÐŸÐŽÐžÐœ Ðž ÑÐŸÑ Ð¶Ðµ ÑÐµÐºÑÑ, Ð¿ÐŸÑÐ»Ðµ ÑÐµÐ³ÐŸ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð¿ÑÐŸÐ²ÐµÑÑÐµÑ ÐŸÐ±Ðµ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÑÐµ Ð²ÐµÑÑÐžÐž ÑÑÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÑÐ»ÐŸÐ²ÐŸ Ð² ÑÐ»ÐŸÐ²ÐŸ ÑÑÐ°Ð²ÐœÐžÐ²Ð°Ñ ÐµÐ³ÐŸ Ñ ÐŸÑÐžÐ³ÐžÐœÐ°Ð»ÐŸÐŒ. ÐÑÐµÐŽÐ¿ÐŸÐ»Ð°Ð³Ð°ÐµÑÑÑ, ÑÑÐŸ ÑÐ»ÐŸÐ²ÐŸ, ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÐœÐœÐŸÐµ ÐŸÐŽÐžÐœÐ°ÐºÐŸÐ²ÐŸ Ð² ÐŸÐ±ÐŸÐžÑ
+ ÑÐ»ÑÑÐ°ÑÑ
+, ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÑÐŒ, Ñ
+ÐŸÑÑ ÑÑÐŸ ÐœÐµ Ð²ÑÐµÐ³ÐŽÐ° ÑÐ°Ðº, Ð¿ÐŸÑÑÐŸÐŒÑ ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐ°ÐºÑÐžÐºÑÐµÑÑÑ Ðž ÐŒÐµÑÐŸÐŽ ÑÑÐŸÐ¹ÐœÐŸÐ³ÐŸ ÐœÐ°Ð±ÐŸÑÐ°.</Text>
+<Text id="221">ÐÐŸÐ»ÐŸÐ¶ÐžÑÐµÐ»ÑÐœÐŸÐ¹ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÐŒÐµÑÐŸÐŽÐ° Ð¿ÐµÑÐµÐ¿ÐµÑÐ°ÑÑÐ²Ð°ÐœÐžÑ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐŸ, ÑÑÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÑÐœÐžÐ·ÐžÑÑ Ð·Ð°ÑÑÐ°ÑÑ, ÑÐ°Ðº ÐºÐ°Ðº ÐœÐµÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÐž Ð¿ÑÐžÐŸÐ±ÑÐµÑÐ°ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐÐ Ð¡ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð±ÐŸÐ»ÐµÐµ ÑÑÐ°ÑÐŸÐ¹ ÐŒÐŸÐŽÐžÑÐžÐºÐ°ÑÐžÐž ÐžÐ»Ðž Ð±/Ñ, Ð² ÑÐŸ Ð²ÑÐµÐŒÑ ÐºÐ°Ðº ÐŽÐ»Ñ Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐžÑ ÐÐ Ð¡ ÐœÑÐ¶ÐœÑ ÐŒÐŸÑÐœÑÐµ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÑ. Ð ÑÐŸÐŒÑ Ð¶Ðµ ÑÐ°Ð±ÐŸÑÐ° ÐŒÐŸÐ¶ÐµÑ Ð²ÑÐ¿ÐŸÐ»ÐœÑÑÑÑÑ ÐŒÐµÐœÐµÐµ ÐºÐ²Ð°Ð»ÐžÑÐžÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐŒÐž ÑÐ°Ð±ÐŸÑÐœÐžÐºÐ°ÐŒÐž. ÐÐŽÐžÐœ ÐœÐµÐŽÐŸÑÑÐ°ÑÐŸÐº ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒ Ð¿ÐŸÐŽÐ³ÐŸÑÐŸÐ²ÐžÑÐµÐ»ÑÐœÑÐ¹ Ð¿ÐµÑÐžÐŸÐŽ, ÐºÐ°Ðº ÐŒÐžÐœÐžÐŒÑÐŒ ÐŽÐŸ ÐŽÐ²ÑÑ
+ ÐŒÐµÑÑÑÐµÐ². ÐÐ°Ð±ÐŸÑ ÐŸÐŽÐœÐžÐŒ ÑÐµÐ»ÐŸÐ²ÐµÐºÐŸÐŒ Ð¿ÑÐžÐ²ÐŸÐŽÐžÑ Ðº ÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ñ ÐŸÑÐžÐ±ÐŸÐº, Ð¿ÐŸÑÑÐŸÐŒÑ Ð¿ÑÐžÑ
+ÐŸÐŽÐžÑÑÑ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑ ÐŽÐ²ÐŸÐ¹ÐœÐŸÐ¹ ÐžÐ»Ðž ÑÑÐŸÐ¹ÐœÐŸÐ¹ ÐœÐ°Ð±ÐŸÑ ÑÐµÐºÑÑÐ°, ÑÑÐŸ ÑÐ²ÑÐ·Ð°ÐœÐŸ Ñ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÐŒÐž Ð·Ð°ÑÑÐ°ÑÐ°ÐŒÐž.</Text>
+<Text id="222">ÐÑÐµ ÐžÐ·ÐŽÐµÑÐ¶ÐºÐž Ð·Ð°Ð²ÐžÑÑÑ ÐŸÑ ÑÑÐŸÐ²ÐœÑ Ð·Ð°ÑÐ¿Ð»Ð°ÑÑ. ÐÐ±ÑÑÐœÐŸ Ð»ÑÐŽÐž, Ð·Ð°ÐœÐžÐŒÐ°ÑÑÐžÐµÑÑ Ð¿ÐµÑÐ°ÑÐ°ÐœÐžÐµÐŒ, Ð² ÑÐ°Ð·Ð²ÐžÐ²Ð°ÑÑÐžÑ
+ÑÑ ÑÑÑÐ°ÐœÐ°Ñ
+ Ð¿ÐŸÐ»ÑÑÐ°ÑÑ ÐŸÐºÐŸÐ»ÐŸ $150 Ð² ÐŒÐµÑÑÑ. ÐÑ
+ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÐµÐ»ÑÐœÐŸÑÑÑ ÐŒÐŸÐ¶ÐµÑ ÑÐŸÑÑÐ°Ð²Ð»ÑÑÑ 20-30 ÑÑÑÐ°ÐœÐžÑ Ð² ÐŽÐµÐœÑ, ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸ 400 ÑÑÑÐ°ÐœÐžÑ Ð² ÐŒÐµÑÑÑ, Ð²ÐºÐ»ÑÑÐ°Ñ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ. Ð¡ ÐŽÐ²ÐŸÐ¹ÐœÑÐŒ ÐœÐ°Ð±ÐŸÑÐŸÐŒ ÑÑÐŸ ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ $300 Ð² ÐŒÐµÑÑÑ Ð¿Ð»ÑÑ ÐŽÑÑÐ³ÐžÐµ Ð·Ð°ÑÑÐ°ÑÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="image_files">
+<Title>
+<Text id="223">Ð€Ð°Ð¹Ð»Ñ ÐÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="224">ÐÑÐµÐœÑ ÐŽÐµÑÐµÐ²ÐŸÐ¹ Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²ÐŸÐ¹ ÐÐ Ð¡ ÑÐ²Ð»ÑÐµÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ Ð¿ÑÐŸÑÑÐŸÐ³ÐŸ ÑÐŸÑÐŒÐ°ÑÐ° PDF ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐŠÐµÐœÐ° ÑÐŸÑÑÐ°Ð²Ð»ÑÐµÑ Ð²ÑÐµÐ³ÐŸ Ð»ÐžÑÑ ÑÐ°ÑÑÑ ÐŸÑ ÑÑÐŸÐžÐŒÐŸÑÑÐž ÐÐ Ð¡ â ÐŸÐºÐŸÐ»ÐŸ $0.1 Ð·Ð° ÑÑÑÐ°ÐœÐžÑÑ.</Text>
+<Text id="225">ÐÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº Ð·Ð°Ð²ÐµÑÑÐµÐœÐŸ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ðž ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒ ÑÐ°Ð¹Ð»Ñ TIFF, Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐžÐ¹ ÐºÐŸÐœÐ²ÐµÑÑÐµÑ ÐŒÐŸÐ¶ÐµÑ (ÐŸÐ±ÑÑÐœÐŸ Adobe Acrobat, Adobe Photoshop) Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÑÑ Ð²ÑÐµ ÑÐ°Ð¹Ð»Ñ ÑÐŸÑÐŒÐ°ÑÐ° TIFF Ð² ÑÐ°Ð¹Ð»Ñ PDF.</Text>
+<Text id="226">ÐÑÑÐžÑÐ°ÑÐµÐ»ÑÐœÐŸÐ¹ ÑÐµÑÑÐŸÐ¹ ÑÐ°ÐºÐžÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐ²Ð»ÑÐµÑÑÑ ÑÐŸ, ÑÑÐŸ Ð¿ÐŸ ÐœÐžÐŒ ÐœÐµÐ»ÑÐ·Ñ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑ Ð¿ÐŸÐžÑÐº. Ð ÑÐŸÐŒÑ Ð¶Ðµ ÐŸÐœÐž ÐŽÐŸÐ²ÐŸÐ»ÑÐœÐŸ Ð±ÐŸÐ»ÑÑÐžÑ
+ ÑÐ°Ð·ÐŒÐµÑÐŸÐ², ÐŸÐ±ÑÑÐœÐŸ 50ÐºÐ± ÐœÐ° ÑÑÑÐ°ÐœÐžÑÑ Ð¿Ð»ÑÑ 20% Ð² Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÐºÐ°ÑÐµÑÑÐ²Ð° ÑÐ°Ð¹Ð»Ð° TIFF.</Text>
+<Text id="227">Ð€Ð°Ð¹Ð»Ñ PDF ÐŸÑÐµÐœÑ ÐŽÐŸÐ»Ð³ÐŸ Ð·Ð°Ð³ÑÑÐ¶Ð°ÑÑÑÑ Ñ ÐÐœÑÐµÑÐœÐµÑÐ° (Ð² ÑÐ°Ð·Ð²ÐžÐ²Ð°ÑÑÐžÑ
+ÑÑ ÑÑÑÐ°ÐœÐ°Ñ
+ ÑÑÐŸ ÐŸÑÐµÐœÑ ÐŽÐŸÑÐŸÐ³ÐŸ Ðž ÐŒÐœÐŸÐ³ÐžÐŒ ÐœÐµ Ð¿ÐŸ ÐºÐ°ÑÐŒÐ°ÐœÑ). ÐÐœÐž ÑÐµÐŽÐºÐŸ Ð¿ÐŸÐŒÐµÑÐ°ÑÑÑÑ ÐœÐ° ÑÐ»ÐŸÐ¿Ð¿Ðž-ÐŽÐžÑÐºÐµ Ðž ÐœÐµ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑ ÑÐ°ÐºÐžÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÐµ ÑÑÐœÐºÑÐžÐž, ÐºÐ°Ðº "Ð²ÑÑÐµÐ·Ð°ÑÑ" Ðž "Ð²ÑÑÐ°Ð²ÐžÑÑ".</Text>
+<Text id="228">ÐÑÐžÐ±ÐµÐ³Ð°ÑÑ Ðº ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ PDF-ÑÐ°Ð¹Ð»ÐŸÐ² ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÑÐŸÐ»ÑÐºÐŸ ÑÐŸÐ³ÐŽÐ°, ÐºÐŸÐ³ÐŽÐ° ÐœÐµÑ ÐŽÐµÐœÐµÐ³ ÐœÐ° ÐÐ Ð¡, Ðž ÐŽÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐŽÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÑ ÐŸÑÐœÐŸÑÐžÑÐµÐ»ÑÐœÐŸ ÐŒÐ°Ð»ÑÐŒ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸÐŒ Ð»ÑÐŽÐµÐ¹, ÐžÐŒÐµÑÑÐžÑ
+ Ð±ÑÑÑÑÑÑ ÐÐœÑÐµÑÐœÐµÑ-ÑÐ²ÑÐ·Ñ.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="combining_scanning_and_ocr">
+<Title>
+<Text id="229">Ð¡ÐŸÐ²ÐŒÐµÑÐµÐœÐžÐµ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Ñ ÐÐ Ð¡</Text>
+</Title>
+<Content>
+<Text id="230">ÐÑÐ»Ðž ÑÐºÐ°ÐœÐµÑ ÐœÐ°Ð¿ÑÑÐŒÑÑ Ð¿ÐŸÐŽÐºÐ»ÑÑÐµÐœ Ðº ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÑ, ÐœÐ° ÐºÐŸÑÐŸÑÐŸÐŒ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐÐ Ð¡, ÑÐŸ Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÑÑÐžÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ ÐŒÐŸÐ¶ÐµÑ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑ Ð¿ÑÐŸÑÐµÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž ÐÐ Ð¡ ÐŸÐŽÐœÐŸÐ²ÑÐµÐŒÐµÐœÐœÐŸ. Ð­ÑÐŸÑ ÐŒÐµÑÐŸÐŽ ÑÐ²Ð»ÑÐµÑÑÑ Ñ
+ÐŸÑÐŸÑÐµÐ¹ ÑÑÑÐ°ÑÐµÐ³ÐžÐµÐ¹, ÐµÑÐ»Ðž Ð²Ñ ÑÐ°Ð±ÐŸÑÐ°ÐµÑÐµ Ñ ÐœÐµÐ±ÐŸÐ»ÑÑÐžÐŒ ÐŸÐ±ÑÐµÐŒÐŸÐŒ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž, ÐœÐŸ Ð·Ð°Ð¹ÐŒÐµÑ ÐŸÑÐµÐœÑ ÐŒÐœÐŸÐ³ÐŸ Ð²ÑÐµÐŒÐµÐœÐž, ÐµÑÐ»Ðž ÐŸÐœ Ð²ÐµÐ»ÐžÐº.</Text>
+<Text id="231">ÐÑÐ»Ðž Ð²Ñ Ð¶ÐµÐ»Ð°ÐµÑÐµ Ð¿ÑÐžÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑÑÑ ÑÐµÐŒÐ¿Ð° 100-150 ÑÑÑÐ°ÐœÐžÑ Ð² ÐŒÐµÑÑÑ, ÑÐŸ ÑÑÐŸÑ ÐŒÐµÑÐŸÐŽ ÐŽÐ»Ñ Ð²Ð°Ñ. ÐÐ»Ñ Ð±ÐŸÐ»ÑÑÐµÐ³ÐŸ ÐŸÐ±ÑÐµÐŒÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð±ÑÑÑÑÐµÐµ Ðž ÑÐŽÐŸÐ±ÐœÐµÐµ ÑÐŸÐ²ÐµÑÑÐ°ÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐŸÑÐŽÐµÐ»ÑÐœÐŸ ÐŸÑ ÐÐ Ð¡.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="three_examples">
+<Title>
+<Text id="232">
+<br/>Ð¢ÑÐž Ð¿ÑÐžÐŒÐµÑÐ°: ÐŸÑ 1000 ÐŽÐŸ 100.000 ÑÑÑÐ°ÐœÐžÑ</Text>
+</Title>
+<Content>
+<Section id="typical_small_collection">
+<Title>
+<Text id="233">Â  ÐÐµÐ±ÐŸÐ»ÑÑÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ: ÐŸÑ 500 ÐŽÐŸ 1000 ÑÑÑÐ°ÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="234">ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÐÐÐ ÐœÑÐ¶ÐŽÐ°ÑÑÑÑ Ð² ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ð° ÐŸÐ±ÑÐµÐŒÐŸÐŒ 5000-1000 ÑÑÑÐ°ÐœÐžÑ. Ð­ÑÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÑÑÐµÑÑÐ²ÐžÑÑ Ðž Ð¿ÑÐŸÐ²ÐµÑÑÐž Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐÐ Ð¡ Ð±ÐµÐ· ÐŸÑÐŸÐ±ÐŸÐ³ÐŸ ÑÑÑÐŽÐ° Ð¿ÑÐž ÐœÐ°Ð»ÐžÑÐžÐž Ð²ÑÑÐŸÐºÐŸ ÑÐµÐ»ÐµÑÑÑÑÐµÐŒÐ»ÐµÐœÐœÑÑ
+ ÑÐ°Ð±ÐŸÑÐœÐžÐºÐŸÐ².</Text>
+<Part id="scanning">
+<Title>
+<Text id="235">Ð¡ÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</Title>
+<Content>
+<Text id="236">ÐÐµÑÐ²ÑÐ¹ ÑÐ°Ð³ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ð° ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ ÐµÐ³ÐŸ Ð² ÐºÐ°ÑÐµÑÑÐ²ÐµÐœÐœÐŸÐŒ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐŒ ÑÐŸÑÐŒÐ°ÑÐµ TIFF - ÐœÐ° ÐºÐ°Ð¶ÐŽÑÑ ÑÑÑÐ°ÐœÐžÑÑ Ð¿ÐŸ ÐŸÐŽÐœÐŸÐŒÑ ÑÐ°Ð¹Ð»Ñ. Ð ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐ°Ñ
+ ÐœÐ°ÐŽÐŸ Ð¿ÐŸÐŽÐ±ÐžÑÐ°ÑÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐµ ÑÐµÐ¶ÐžÐŒÑ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐžÐ¿Ð° ÑÐžÑÑÐœÐºÐ°. ÐÑÐµÐŽÐ¿ÐŸÐ»ÐŸÐ¶ÐžÐŒ, ÑÑÐŸ Ð·Ð°ÐŽÐ°ÑÐ° ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ ÐŸÑÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÑÑ 1000 ÑÑÑÐ°ÐœÐžÑ. Ð­ÑÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÐ³Ð°ÐœÐžÐ·ÐŸÐ²Ð°ÑÑ, ÐœÐ°ÐœÑÐ² ÑÐ°Ð±ÐŸÑÐœÐžÐºÐŸÐ² ÐœÐ° Ð¿ÐŸÐ»ÑÑÐ°Ð²ÐºÐž ÐœÐ° Ð¿ÑÐŸÑÑÐ¶ÐµÐœÐžÐž ÐŒÐµÑÑÑÐ° â ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ»Ñ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ. Ð€Ð°Ð¹Ð»Ñ TIFF Ð·Ð°Ð¹ÐŒÑÑ ÐŸÑ 60 ÐŽÐŸ 80ÐÐ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ð° ÐœÐ° Ð¶ÐµÑÑÐºÐŸÐŒ ÐŽÐžÑÐºÐµ Ðž Ð»ÑÑÑÐµ Ð²ÑÐµÐ³ÐŸ ÑÐ°ÐºÐ¶Ðµ Ð·Ð°Ð¿ÐžÑÐ°ÑÑ ÑÑÐž ÑÐ°Ð¹Ð»Ñ ÐœÐ° ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐº (CD-ROM). ÐÐµÐŽÐŸÑÐŸÐ³ÐŸÐ¹ ÐœÐ°ÑÑÐŸÐ»ÑÐœÑÐ¹ ÑÐºÐ°ÐœÐµÑ ÑÐµÐœÐŸÐ¹ $ 100-300 Ð±ÑÐŽÐµÑ ÐŽÐŸÑÑÐ°ÑÐŸÑÐµÐœ ÐŽÐ»Ñ ÑÑÐŸÐ¹ ÑÐ°Ð±ÐŸÑÑ. Ð¡ÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑ Ð²ÐµÑÐµÑÐŸÐŒ ÐžÐ»Ðž Ð¿ÐŸ Ð²ÑÑ
+ÐŸÐŽÐœÑÐŒ.</Text>
+</Content>
+</Part>
+<Part id="ocr">
+<Title>
+<Text id="237">ÐÐ Ð¡</Text>
+</Title>
+<Content>
+<Text id="238">Ð¡Ð»ÐµÐŽÑÑÑÐžÐ¹ ÑÐ°Ð³ - ÑÑÐŸ Ð¿ÑÐŸÐ²ÐµÑÑÐž Ð¿ÑÐŸÑÐµÑÑ ÐÐ Ð¡ ÐŸÐŽÐœÐžÐŒ ÐžÐ»Ðž ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÐŒÐž ÑÐ°Ð±ÐŸÑÐœÐžÐºÐ°ÐŒÐž, ÐžÐŒÐµÑÑÐžÐŒÐž Ñ
+ÐŸÑÐŸÑÐžÐµ ÑÐ·ÑÐºÐŸÐ²ÑÐµ ÐœÐ°Ð²ÑÐºÐž. Ð€Ð°Ð¹Ð»Ñ TIFF ÐŒÐŸÐ¶ÐœÐŸ ÑÐ°ÑÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ Ð¿ÐŸ ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°ÐŒ ÐžÐ»Ðž Ð²ÑÐ¿ÐŸÐ»ÐœÑÑÑ Ð²ÑÑ ÑÐ°Ð±ÐŸÑÑ ÐœÐ° ÐŸÐŽÐœÐŸÐŒ. ÐÐ±ÑÑÐœÐŸ ÑÑÐŸ Ð·Ð°Ð¹ÐŒÐµÑ ÐŸÐºÐŸÐ»ÐŸ Ð¿ÑÑÐž ÐžÐ»Ðž ÑÐµÑÑÐž ÐŒÐµÑÑÑÐµÐ² ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÐœÐžÐºÐ° ÐœÐ° Ð¿ÐŸÐ» -ÑÑÐ°Ð²ÐºÐž (Ð¿ÑÐžÐŒÐµÑÐœÐŸ 20 ÑÐ°ÑÐŸÐ² Ð² ÐœÐµÐŽÐµÐ»Ñ) ÐŽÐ»Ñ Ð¿ÐŸÐ»ÐœÐŸÐ¹ Ðž Ð±ÐµÐ·ÐŸÑÐžÐ±ÐŸÑÐœÐŸÐ¹ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐºÐž 1000 ÑÑÑÐ°ÐœÐžÑ Ð² ÑÐ°Ð¹Ð»Ñ Word ÐžÐ»Ðž HTML-ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+</Content>
+</Part>
+<Part id="outsourcing">
+<Title>
+<Text id="239">ÐÐŸÑÑÑÐµÐœÐžÐµ ÐŽÑÑÐ³ÐžÐŒ</Text>
+</Title>
+<Content>
+<Text id="240">Ð ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²Ñ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÑÑÑÐžÑÑ ÑÑÑ ÑÐ°Ð±ÐŸÑÑ Ð¿ÑÐŸÑÐµÑÑÐžÐŸÐœÐ°Ð»ÑÐœÐŸÐ¹ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÐž. Ð­ÑÐŸ Ð±ÑÐŽÐµÑ ÑÑÐŸÐžÑÑ ÐŸÐºÐŸÐ»ÐŸ $1500-$2000 ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ ÐŸÑÐ»ÐžÑÐœÑÑ
+ Word ÐžÐ»Ðž HTML-ÑÐ°Ð¹Ð»ÐŸÐ².</Text>
+</Content>
+</Part>
+</Content>
+</Section>
+<Section id="all_publications_from_an_organization">
+<Title>
+<Text id="241">ÐÑÐµ Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐž ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž: 5000 ÑÑÑÐ°ÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="242">ÐÐœÐŸÐ³ÐžÐµ Ð±ÐŸÐ»ÑÑÐžÐµ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž ÐžÐŒÐµÑÑ Ð°ÑÑ
+ÐžÐ²Ñ, ÑÐŸÑÑÐŸÑÑÐžÐµ Ð¿ÑÐžÐŒÐµÑÐœÐŸ ÐžÐ· 5000 ÑÑÑÐ°ÐœÐžÑ ÐžÐ·ÐŽÐ°ÐœÐžÐ¹, ÐºÐœÐžÐ³, ÑÐ°Ð·Ð»ÐžÑÐœÐŸÐ³ÐŸ ÑÐŸÐŽÐ° Ð»ÐžÑÐµÑÐ°ÑÑÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÑÐ¶Ðµ ÐœÐµ ÐžÐ·ÐŽÐ°ÑÑÑÑ.</Text>
+<Part id="scanning_1">
+<Title>
+<Text id="243">Ð¡ÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</Title>
+<Content>
+<Text id="244">Ð­ÑÐŸ ÑÐ»ÐžÑÐºÐŸÐŒ Ð±ÐŸÐ»ÑÑÐŸÐ¹ ÐŸÐ±ÑÐµÐŒ ÐŽÐ»Ñ Ð¿ÑÐŸÑÑÐŸÐ³ÐŸ ÐœÐ°ÑÑÐŸÐ»ÑÐºÐŸ ÑÐºÐ°ÐœÐµÑÐ°. Ð¡ÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð»ÑÑÑÐµ Ð»ÐžÐ±ÐŸ Ð¿ÐŸÑÑÑÐžÑÑ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÐž (ÐŸÐºÐŸÐ»ÐŸ $400 Ð·Ð° 5000 ÑÑÑÐ°ÐœÐžÑ) ÐžÐ»Ðž Ð¿ÑÐžÐŸÐ±ÑÐµÑÑÐž ÑÐºÐ°ÐœÐµÑ Ñ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐŸÐ¹ Ð¿ÐŸÐŽÐ°ÑÐµÐ¹ ÑÑÑÐ°ÐœÐžÑ (ÐŸÐºÐŸÐ»ÐŸ $900). ÐÐŸÐ¶ÐœÐŸ ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐžÐŸÐ±ÑÐµÑÑÐž ÑÐºÐ°ÐœÐµÑ ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸ Ñ ÐŽÑÑÐ³ÐžÐŒÐž ÐÐÐ ÐžÐ»Ðž ÐŽÑÑÐ³ÐžÐŒÐž ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑÐŒÐž ($6000 ÑÐ°Ð·ÐŽÐµÐ»ÐžÑÑ ÐœÐ° ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÑÐŸÐ²Ð»Ð°ÐŽÐµÐ»ÑÑÐµÐ²). ÐÑÐµ 5000 ÑÑÑÐ°ÐœÐžÑ Ð·Ð°Ð¹ÐŒÑÑ ÐŸÐºÐŸÐ»ÐŸ 300-400 MB, Ðž ÑÐœÐŸÐ²Ð° ÐŒÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ Ð²Ð°ÐŒ Ð¿Ð°ÑÐ°Ð»Ð»ÐµÐ»ÑÐœÐŸ Ð·Ð°Ð¿ÐžÑÐ°ÑÑ ÑÑÐŸ ÐœÐ° CD.</Text>
+</Content>
+</Part>
+<Part id="ocr_1">
+<Title>
+<Text id="245">ÐÐ Ð¡</Text>
+</Title>
+<Content>
+<Text id="246">Ð ÑÐœÐŸÐ²Ð° Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð¿ÑÐŸÐ¹ÑÐž ÑÐµÑÐµÐ· Ð¿ÑÐŸÑÐµÑÑ ÐÐ Ð¡, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑ
+ÐŸÐ¶ÑÑ ÑÐ°Ð±ÐŸÑÑÑ ÑÐžÐ»Ñ, ÑÑÐŸ Ðž Ð² Ð¿ÑÐµÐŽÑÐŽÑÑÐµÐŒ ÑÐ»ÑÑÐ°Ðµ. ÐÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŸÐŽÐžÐœ ÐžÐ»Ðž ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐŸÐ². ÐÐ° 5000 ÑÑÑÐ°ÐœÐžÑ ÑÑÐŸ Ð·Ð°Ð¹ÐŒÐµÑ ÐŸÐºÐŸÐ»ÐŸ 25-30 ÐŒÐµÑÑÑÐµÐ² Ð¿ÑÐž ÑÐ°Ð±ÐŸÑÐµ Ð¿ÐŸ 20 ÑÐ°ÑÐŸÐ² Ð² ÐœÐµÐŽÐµÐ»Ñ. ÐÐ° Ð¿ÑÐ°ÐºÑÐžÐºÐµ ÑÑÐŸ ÐŸÑÐµÐœÑ ÐŽÐŸÐ»Ð³ÐžÐ¹ ÑÑÐŸÐº. ÐÑÐ¶ÐµÐœ ÑÐµÐ»ÐŸÐ²ÐµÐº, ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÑÐ¹ Ð·Ð° Ð¿Ð»Ð°ÑÑ ÑÐ°Ð±ÐŸÑÐœÐžÐºÐ°ÐŒ, ÐœÐ°ÐŽÐ·ÐŸÑÐŸÐŒ Ð·Ð° ÐºÐ°ÑÐµÑÑÐ²ÐŸÐŒ, Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÐ³ÐŸ ÐŒÐµÑÑÐ° Ðž Ñ.ÐŽ. ÐŽÐ»Ñ ÐŸÐºÐŸÐœÑÐ°ÐœÐžÑ ÑÐ°Ð±ÐŸÑÑ ÐºÐ°ÑÐµÑÑÐ²ÐµÐœÐœÐŸ Ðž Ð·Ð° ÐŒÐµÐœÐµÐµ ÐºÐŸÑÐŸÑÐºÐžÐ¹ ÑÑÐŸÐº.</Text>
+<Text id="247">ÐÐŸÐ¶ÐœÐŸ ÑÐ°ÐºÐ¶Ðµ ÑÐŸÐ·ÐŽÐ°ÑÑ ÑÐ°Ð¹Ð»Ñ PDF, ÐºÐŸÑÐŸÑÑÐµ Ð·Ð°Ð¹ÐŒÑÑ ÐŸÐºÐŸÐ»ÐŸ 300-400 MB Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ð° Ðž Ð±ÑÐŽÑÑ ÐŸÑÐµÐœÑ ÐŽÐŸÐ»Ð³ÐŸ Ð·Ð°Ð³ÑÑÐ¶Ð°ÑÑÑÑ ÑÐµÑÐµÐ· ÐÐœÑÐµÑÐœÐµÑ.</Text>
+</Content>
+</Part>
+<Part id="outsourcing_1">
+<Title>
+<Text id="248">ÐÐŸÑÑÑÐµÐœÐžÐµ ÐŽÑÑÐ³ÐžÐŒ</Text>
+</Title>
+<Content>
+<Text id="249">ÐÐŸÐ¶ÐœÐŸ Ð¿ÐŸÑÑÑÐžÑÑ ÐŽÑÑÐ³ÐŸÐ¹ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÐž ÐºÐ°Ðº ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ, ÑÐ°Ðº Ðž ÐÐ Ð¡. Ð­ÑÐŸ Ð±ÑÐŽÐµÑ ÑÑÐŸÐžÑÑ ÐŸÑ $7500 ÐŽÐŸ $10000 Ð·Ð° Ð²ÑÑ ÑÐ°Ð±ÐŸÑÑ.</Text>
+</Content>
+</Part>
+</Content>
+</Section>
+<Section id="a_small_library">
+<Title>
+<Text id="250">ÐÐµÐ±ÐŸÐ»ÑÑÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°: 100.000 ÑÑÑÐ°ÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="251">Ð Ð°Ð·Ð»ÐžÑÐœÑÐµ ÐºÑÑÐ¿ÐœÑÐµ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž, ÑÐœÐžÐ²ÐµÑÑÐžÑÐµÑÑ, Ð¿ÑÐ°Ð²ÐžÑÐµÐ»ÑÑÑÐ²ÐŸ Ðž ÑÐ¿ÐµÑÐžÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÐŒÐŸÐ³ÑÑ Ð¿ÐŸÐ¶ÐµÐ»Ð°ÑÑ Ð¿ÐµÑÐµÐ²ÐµÑÑÐž Ð²ÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ Ð² ÑÐžÑÑÐŸÐ²ÐŸÐ¹ ÑÐŸÑÐŒÐ°Ñ â ÐŽÐŸÐ¿ÑÑÑÐžÐŒ 100.000 ÑÑÑÐ°ÐœÐžÑ. ÐÐµÑÐ²Ð°Ñ Ð²ÐµÑÑ, ÐŸ ÐºÐŸÑÐŸÑÐŸÐ¹ ÑÐ»ÐµÐŽÑÐµÑ Ð¿ÐŸÐ·Ð°Ð±ÐŸÑÐžÑÑÑÑ, - ÑÑÐŸ Ð°Ð²ÑÐŸÑÑÐºÐžÐµ Ð¿ÑÐ°Ð²Ð° ÐœÐ° Ð²ÑÐµ ÐžÐ·ÐŽÐ°ÐœÐžÑ. ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÑÐ°Ð·ÑÐµÑÐµÐœÐžÐµ Ð²Ð»Ð°ÐŽÐµÐ»ÑÑÐµÐ² ÑÑÐžÑ
+ Ð¿ÑÐ°Ð² Ð¿ÐµÑÐµÐŽ ÑÐµÐŒ, ÐºÐ°Ðº ÐœÐ°ÑÐ°ÑÑ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ. ÐÐ°ÐŒ ÑÐ°ÐºÐ¶Ðµ ÑÐ»ÐµÐŽÑÐµÑ ÑÐ±ÐµÐŽÐžÑÑÑÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ ÑÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐµÑÐµ ÐœÐµ ÑÑÑÐµÑÑÐ²ÑÑÑ Ð² ÑÐžÑÑÐŸÐ²ÐŸÐŒ ÑÐŸÑÐŒÐ°ÑÐµ. </Text>
+<Part id="scanning_2">
+<Title>
+<Text id="252">Ð¡ÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</Title>
+<Content>
+<Text id="253">Ð¢Ð°ÐºÐŸÐ¹ ÐŸÐ±ÑÐµÐŒ ÑÐ»ÐžÑÐºÐŸÐŒ Ð²ÐµÐ»ÐžÐº ÐŽÐ»Ñ ÑÐºÐ°ÐœÐµÑÐ° Ñ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐŸÐ¹ Ð¿ÐŸÐŽÐ°ÑÐµÐ¹ ÑÑÑÐ°ÐœÐžÑ. Ð­ÑÐŸ ÐœÑÐ¶ÐœÐŸ Ð»ÐžÐ±ÐŸ Ð¿ÐŸÑÑÑÐžÑÑ ÐŽÑÑÐ³ÐžÐŒ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑÐŒ ($8000 Ð·Ð° 100.000 ÑÑÑÐ°ÐœÐžÑ) ÐžÐ»Ðž Ð¿ÑÐžÐŸÐ±ÑÐµÑÑÐž ÐŽÐŸÑÐŸÐ³ÐŸÐ¹ ÑÐºÐ°ÐœÐµÑ ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸ Ñ ÐŽÑÑÐ³ÐžÐŒÐž ($6000). ÐÐ±ÑÐµÐŒ 100.000 ÑÑÑÐ°ÐœÐžÑ Ð·Ð°Ð¹ÐŒÐµÑ 6-8 GB. Ð¡ÐœÐŸÐ²Ð° Ð²Ð°ÐŒ Ð»ÑÑÑÐµ Ð¿ÐŸÐŒÐµÑÑÐžÑÑ ÐºÐŸÐ¿ÐžÑ Ð² ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐºÐŸÐ².</Text>
+</Content>
+</Part>
+<Part id="ocr_2">
+<Title>
+<Text id="254">ÐÐ Ð¡</Text>
+</Title>
+<Content>
+<Text id="255">ÐÑÐŸÑÐŸÐ¹ ÑÐ°Ð³ - ÑÑÐŸ Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐžÐµ ÐÐ Ð¡ (ÐžÐ»Ðž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ PDF-ÑÐ°Ð¹Ð»ÐŸÐ² ÐŽÐ»Ñ ÑÐµÐŽÐºÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²). Ð­ÑÐŸ Ð·Ð°Ð¹ÐŒÐµÑ ÐŸÐºÐŸÐ»ÐŸ 500 - 700 ÐŒÐµÑÑÑÐµÐ² ÐŽÐ»Ñ Ð²ÑÐµÐ³ÐŸ Ð¿ÑÐŸÑÐµÑÑÐ° ÐÐ Ð¡ Ðž Ð¿ÐµÑÐµÐ²ÐŸÐŽÐ° Ð² Word Ðž HTML Ð¿ÑÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž ÑÐ°Ð±ÐŸÑÐœÐžÐºÐŸÐ² ÐœÐ° Ð¿ÐŸÐ»ÑÑÐ°Ð²ÐºÐž. Ð­ÑÐŸ ÐœÐµÑÑÑÐµÐºÑÐžÐ²ÐœÐŸ, Ð¿ÐŸÑÑÐŸÐŒÑ Ð²Ð°ÐŒ Ð»ÑÑÑÐµ Ð¿ÐŸÑÑÑÐžÑÑ ÑÑÑ ÑÐ°Ð±ÐŸÑÑ Ð¿ÑÐŸÑÐµÑÑÐžÐŸÐœÐ°Ð»Ð°ÐŒ.</Text>
+<Text id="256">ÐÐ»Ñ ÑÐœÐžÐ¶ÐµÐœÐžÑ Ð·Ð°ÑÑÐ°Ñ Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÑÐµÐŽÐºÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ ÑÑÑÐ°ÐœÐžÑ (ÑÐºÐ°Ð¶ÐµÐŒ, 80% ÐžÐ»Ðž 80.000 Ñ.) ÐŒÐŸÐ¶ÐœÐŸ ÐºÐŸÐœÐ²ÐµÑÑÐžÑÐŸÐ²Ð°ÑÑ Ð² ÑÐ°Ð¹Ð»Ñ PDF, Ð° ÐŸÑÑÐ°Ð»ÑÐœÑÐµ 20.000 Ð² Word, HTML. Ð€Ð°Ð¹Ð»Ñ PDF Ð·Ð°ÐœÑÐ»Ðž Ð±Ñ 4-6 GB, ÐŽÐŸÐ»Ð³ÐŸ Ð·Ð°Ð³ÑÑÐ¶Ð°ÐµÐŒÑÑ
+ ÑÐµÑÐµÐ· ÐÐœÑÐµÑÐœÐµÑ, ÐœÐŸ ÑÑÐŸÐžÐ»Ðž Ð±Ñ ÐŸÐœÐž $0.2 Ð·Ð° ÑÑÑÐ°ÐœÐžÑÑ Ñ Ð¿ÑÐŸÑÐµÑÑÐžÐŸÐœÐ°Ð»ÑÐœÐŸÐ¹ ÐºÐŸÐŒÐ¿Ð°ÐœÐžÐž ($16.000 ÐŽÐ»Ñ 80.000 Ñ.). ÐÑÐ»Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐœÐ°ÐµÐŒÐœÑÐ¹ ÑÑÑÐŽ ÐŽÐ»Ñ ÐºÐŸÐœÐ²ÐµÑÑÐ°ÑÐžÐž TIFF Ð² PDF, ÑÐŸ ÑÑÐŸ Ð·Ð°ÐœÑÐ»ÐŸ Ð±Ñ 10-20 ÐŒÐµÑÑÑÐµÐ² ÑÐ°Ð±ÐŸÑÑ ÐœÐ° Ð¿ÐŸÐ»ÑÑÐ°Ð²ÐºÐž.</Text>
+</Content>
+</Part>
+<Part id="outsourcing_2">
+<Title>
+<Text id="257">ÐÐŸÑÑÑÐµÐœÐžÐµ ÐŽÑÑÐ³ÐžÐŒ</Text>
+</Title>
+<Content>
+<Text id="258">ÐÑÐ»Ðž ÑÐŸÑ
+ÑÐ°ÐœÐžÑÑ Ð¿ÑÐŸÐ¿ÐŸÑÑÐžÑ 80% PDF Ðž 20% HTML, Word, ÑÐŸ Ð¿ÐµÑÐ²Ð°Ñ ÑÐ°ÑÑÑ ÑÑÐŸÐžÑ ÐŸÐºÐŸÐ»ÐŸ $16.000, Ð° Ð²ÑÐŸÑÐ°Ñ - ÐŸÐºÐŸÐ»ÐŸ $30.000-$40.000, Ð° Ð² ÑÐµÐ»ÐŸÐŒ ÐŸÐºÐŸÐ»ÐŸ $50,000. ÐÑÐ»Ðž Ð²ÑÐµ Ð¿ÑÐŸÐ²ÐµÑÑÐž ÑÐµÑÐµÐ· ÐÐ Ð¡, ÑÑÐŸ Ð±ÑÐŽÐµÑ ÑÑÐŸÐžÑÑ $150.000-$200.000.</Text>
+</Content>
+</Part>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="creating_an_electronic_collection">
+<Title>
+<Text id="259">ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="260">Ð¡Ð»ÐµÐŽÑÐµÑ ÑÑÐžÑÑÐ²Ð°ÑÑ ÑÑÐž Ð²Ð°Ð¶ÐœÑÐµ Ð²ÐµÑÐž Ð¿ÑÐž Ð¿ÑÐžÐœÑÑÐžÐž ÑÐµÑÐµÐœÐžÑ ÐŸ ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐµÑÐ²ÐŸÐµ, ÐœÑÐ¶ÐœÐŸ ÑÑÐŸÐ±Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð±ÑÐ»Ð° ÐŸÑÐ³Ð°ÐœÐžÐ·ÐŸÐ²Ð°ÐœÐ° Ðž ÐžÐŒÐµÐ»Ð° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ ÑÑÑÑÐºÑÑÑÑ. Ð§ÐµÐŒ Ð±ÐŸÐ»ÑÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ, ÑÐµÐŒ ÑÐ°Ð·ÐœÐŸÐŸÐ±ÑÐ°Ð·ÐœÐµÐµ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐžÐœÐŽÐµÐºÑÑ Ðž ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐ° ÐŒÐŸÑÐœÐ°Ñ Ð¿ÐŸÐžÑÐºÐŸÐ²Ð°Ñ ÑÐžÑÑÐµÐŒÐ°. ÐÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐŸÐ±ÑÐµÐŒÐŸÐŒ 3000-5000 ÑÑÑÐ°ÐœÐžÑ ÐŸÑÐµÐœÑ Ð²Ð°Ð¶ÐœÐŸ ÐžÐŒÐµÑÑ ÑÑÐµÐ±ÐŸÐ²Ð°ÐœÐžÑ, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐµ Ð²ÑÑÐµ. ÐÐŸ-Ð²ÑÐŸÑÑÑ
+, Ð¿ÑÐµÐ¶ÐŽÐµ Ð²ÑÐµÐ³ÐŸ ÑÐ»ÐµÐŽÑÐµÑ ÑÑÐžÑÑÐ²Ð°ÑÑ ÐœÑÐ¶ÐŽÑ ÐºÐŸÐœÐµÑÐœÐŸÐ³ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ. Ð¡Ð»ÐµÐŽÑÐµÑ ÑÐµÑÐºÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ Ð³ÑÑÐ¿Ð¿Ñ Ð»ÑÐŽÐµÐ¹, ÐŽÐ»Ñ ÐºÐŸÑÐŸÑÑÑ
+ ÑÐŸÐ·ÐŽÐ°ÐµÑÑÑ ÑÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, Ðž ÐœÐµÐ¿ÑÐµÐŒÐµÐœÐœÐŸ ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÐžÐŒ ÐºÐŸÐœÑÑÐ»ÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÑÑÐ»ÑÐ³Ðž. Ð ÐœÐ°ÐºÐŸÐœÐµÑ, ÐœÐ°Ð»ÐžÑÐžÐµ ÑÑÐµÐŽÑÑÐ² ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑ ÐŸÐ±ÑÐµÐŒ Ð¿ÐŸÑÐµÐœÑÐžÐ°Ð»ÑÐœÐŸÐ¹ ÑÐ°Ð±ÐŸÑÑ.</Text>
+<Section id="methods_of_collection_building">
+<Title>
+<Text id="261">Â  ÐÐµÑÐŸÐŽÑ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</Title>
+<Content>
+<Text id="262">Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐŒÐœÐŸÐ³ÐŸ Ð¿ÑÐžÐŒÐµÑÐŸÐ² Ð¿ÑÐµÐ²ÐŸÑÑ
+ÐŸÐŽÐœÑÑ
+ ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐºÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐ·ÐŽÐ°ÐœÑ Ð¿ÐŸ ÐŒÐŸÐŽÐµÐ»Ðž Ð²ÐµÐ±-ÑÑÑÐ°ÐœÐžÑ. HTML, PDF ÐžÐ»Ðž ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Word ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑÑÑ Ðž ÑÐ²ÑÐ·ÑÐ²Ð°ÑÑÑÑ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ Ð³ÐžÐ¿ÐµÑÑÑÑÐ»ÐŸÐº. ÐÐ°Ð²ÐžÐ³Ð°ÑÐžÑ ÑÐŽÐµÐ»Ð°ÐœÐ° Ð¿ÑÐŸÑÑÐŸÐ¹ Ðž Ð¿ÑÐžÐ²Ð»ÐµÐºÐ°ÑÐµÐ»ÑÐœÐŸÐ¹ Ð¿ÑÐž Ð¿ÐŸÐŒÐŸÑÐž Ð³ÐžÐ¿ÐµÑÑÐ²ÑÐ·ÐµÐ¹, ÑÑÐµÐ¹ÐŒÐŸÐ², ÐºÐ»ÑÑÐµÐ²ÑÑ
+ ÑÐ»ÐŸÐ², ÐžÐœÐŽÐµÐºÑÐŸÐ² Ðž Ñ.ÐŽ. Ð¢Ð°ÐºÐžÐµ ÑÐžÑÑÐµÐŒÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ
+ÐŸÑÐŸÑÐŸ Ð²Ð¿Ð»ÐŸÑÑ ÐŽÐŸ ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÑÑÑÑÑ ÑÑÑÐ°ÐœÐžÑ, ÐœÐŸ Ñ 3000 ÐŽÐŸ 5000 ÑÑÑÐ°ÐœÐžÑ Ð²Ð°Ð¶ÐœÐŸ ÐžÐŒÐµÑÑ Ñ
+ÐŸÑÐŸÑÐŸ ÑÑÑÑÐºÑÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ðž ÐŒÐŸÑÐœÑÐµ ÑÑÐµÐŽÑÑÐ²Ð° Ð¿ÐŸÐžÑÐºÐ°. ÐÐŒÐµÐœÐœÐŸ Ð² ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone ÐŒÐŸÐ¶ÐµÑ ÑÑÑÐµÐºÑÐžÐ²ÐœÐŸ Ð¿ÐŸÐŒÐŸÑÑ.</Text>
+<Text id="263">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÐŠÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone ÑÐŸÐ·ÐŽÐ°ÐµÑ ÑÑÑÑÐºÑÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÑ ÑÐžÑÑÐŸÐ²ÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ Ðž Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐŸÑÐµÐœÑ ÐŒÐŸÑÐœÑÐµ Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ðž ÑÑÐµÐŽÑÑÐ²Ð° Ð²ÐŸÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐžÑ. ÐÐŸ 150000 ÑÑÑÐ°ÐœÐžÑ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð¿ÑÐŸÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐŸ ÐœÐ° ÐŸÑÐŽÐµÐ»ÑÐœÐŸÐŒ CD-ROM. ÐÐ°Ð¶ÐŽÑÐ¹ CD-ROM ÐŒÐŸÐ¶ÐµÑ ÑÑÐ°ÑÑ ÑÐµÑÐ²ÐµÑÐŸÐŒ ÐÐœÑÐµÑÐœÐµÑÐ°. Greenstone ÑÐ²Ð»ÑÐµÑÑÑ ÐŸÑÐºÑÑÑÑÐŒ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐŒ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµÐŒ Ñ ÐŸÑÐºÑÑÑÐŸÐ¹ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐŸÐ¹ Ðž ÑÐ²ÐŸÐ±ÐŸÐŽÐœÐŸ ÐŽÐŸÑÑÑÐ¿ÐœÐŸ ÑÐŸÐ³Ð»Ð°ÑÐœÐŸ Ð»ÐžÑÐµÐœÐ·ÐžÐž GNU.</Text>
+<Text id="264">Ð¡ÐŸÐ¿ÑÑÑÑÐ²ÑÑÑÐžÐµ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÐŸÐ¿ÐžÑÑÐ²Ð°ÑÑ, ÐºÐ°Ðº ÑÑÑÐŸÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone. ÐÑÑÑ Ð¿ÐŸ ÑÑÑÐµÑÑÐ²Ñ ÑÑÐž ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð¿ÑÑÐž ÐžÑ
+ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ:</Text>
+<BulletList>
+<Bullet>
+<Text id="265">ÐÐœÑÐµÑÑÐµÐ¹Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ </Text>
+</Bullet>
+<Bullet>
+<Text id="266">ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ</Text>
+</Bullet>
+<Bullet>
+<Text id="267">ÐÐŸÑÑÑÐŸÐµÐœÐžÐµ ÐžÐ· ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž.</Text>
+</Bullet>
+</BulletList>
+<Text id="268">ÐÐµÑÐ²ÑÐ¹ ÐŒÐµÑÐŸÐŽ - "Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐžÐ¹" ÐžÐœÑÐµÑÑÐµÐ¹Ñ, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐ¹ Ð² ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð¿ÐŸ ÐŠÐžÑÑÐŸÐ²ÐŸÐ¹ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐµ ÐÑÐžÐœÑÑÐŸÑÐœ (ÐÐ»Ð°Ð²Ð° 3, Â«Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐÑÐžÐœÑÑÐŸÑÐœÂ»). Ð­ÑÐŸ - Ð²ÑÐµÑÑÐŸÑÐŸÐœÐœÐµÐµ ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÐŸÐµ ÑÑÐµÐŽÑÑÐ²ÐŸ ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹. Ð¡ ÑÑÐžÐŒ, ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÑÑÐŸÐžÑÑ ÐœÐ°Ð±ÐŸÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐžÐ»Ðž ÐœÐ°Ð·ÐœÐ°ÑÐ°ÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, Ðž ÐŸÐ±ÑÐµÐŽÐžÐœÑÑÑ ÐžÑ
+ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐÑÐžÐœÑÑÐŸÑÐœ. ÐÑÐŸÑÐŸÐ¹Â  ÐŒÐµÑÐŸÐŽ - "ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ" Ð¿ÐŸÐŽÑÐžÑÑÐµÐŒÐ°, ÐŸÐ¿ÐžÑÐ°ÐœÐœÐ°Ñ Ð² 4 ÐÐ»Ð°Ð²Ðµ Ð² ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ. Ð­ÑÐŸ â Ð¿ÑÐµÐŽÐžÐŽÑÑÐµÐµ ÑÑÐµÐŽÑÑÐ²ÐŸ, ÐºÐŸÑÐŸÑÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²ÐœÑÐ¹ Ð¿ÑÑÑ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÑÐµÑÐž ÐžÐ»Ðž ÐŽÑÑÐ³ÐžÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÐµÐŽÑÑÐµÐµ ÐÐ°Ñ ÑÐµÑÐµÐ· Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸÑÑÑ ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÑÑ
+ Ð²ÐµÐ± ÑÑÑÐ°ÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ Ð·Ð°Ð¿ÑÐ°ÑÐžÐ²Ð°ÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ. ÐÐŽÐœÐ°ÐºÐŸ, ÑÑÐŸ ÐœÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ, ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðº ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ, Ðž - Ð¿ÐŸÑÐºÐŸÐ»ÑÐºÑ ÑÑÐŸ â Ð²ÐµÐ± ÐžÐœÑÐµÑÑÐµÐ¹Ñ - ÑÑÐŸ ÐœÐµ Ð²ÑÐµÐ³ÐŽÐ° Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÐµÐµ ÑÑÐµÐŽÑÑÐ²ÐŸ ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÑÑÐµÐ±ÑÑÑ Ð±ÐŸÐ»ÑÑÐµ ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÐŒÐžÐœÑÑ ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ. Ð¢ÑÐµÑÐžÐ¹ ÐŒÐµÑÐŸÐŽ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°ÐŒÐž ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ ÐžÐ· ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž; ÑÑÐŸ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð¿ÐŸ ÐŠÐžÑÑÐŸÐ²ÐŸÐ¹ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐµ ÐÑÐžÐœÑÑÐŸÑÐœ (ÐÐ»Ð°Ð²Ð° 1). Ð­ÑÐŸ ÐŽÐ°ÐµÑ Ð±ÐŸÐ»ÑÑÐµÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ Ð³ÐžÐ±ÐºÐŸÑÑÐž ÐŽÐ»Ñ ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ, ÑÐºÐŸÐœÐŸÐŒÑ ÐœÐ° Ð¿ÑÐŸÐŒÐµÐ¶ÑÑÐŸÑÐœÑÑ
+ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐ°Ñ
+, Ðž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÑ ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ ÐŸÑÐµÐœÑ ÐŒÐœÐŸÐ³ÐŸ Ð²ÑÐµÐŒÐµÐœÐž. ÐÐ°ÐŒ Ð±ÑÐŽÐµÑ ÑÐ°ÐºÐ¶Ðµ Ð¿ÐŸÐ»ÐµÐ·ÐœÐŸ Ð¿ÑÐŸÑÐžÑÐ°ÑÑ Ð³Ð»Ð°Ð²Ñ 2 ÐÐžÐŽÐ° ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð²ÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐžÂ  ÐÑÐžÐœÑÑÐŸÑÐœ, ÑÑÐŸÐ±Ñ ÑÑÑÐŸÐžÑÑ Ð¿ÑÐŸÐŽÐ²ÐžÐœÑÑÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="269">ÐÑÑÑ ÑÐ°ÐºÐ¶Ðµ ÑÐµÑÐ²ÐµÑÑÑÐ¹ ÐŒÐµÑÐŸÐŽ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ðž ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŒÐ°ÑÐµÑÐžÐ°Ð»ÐŸÐ² Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÐŸÐ¹ ÐÑÐ³Ð°ÐœÐ°Ð¹Ð·ÐµÑÐŸÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹. ÐÐŽÐœÐ°ÐºÐŸ, ÐµÐµ ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ð±ÑÐ» Ð·Ð°ÐŒÐµÐœÐµÐœÑ Ð²ÑÑÐµ ÑÐ¿ÐŸÐŒÑÐœÑÑÑÐŒ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐŸÐŒ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ. ÐÐ¿ÐžÑÐ°ÐœÐœÑÐŒ Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐµ ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÑÐ³Ð°ÐœÐ°Ð¹Ð·ÐµÑÐ°.</Text>
+</Content>
+</Section>
+<Section id="getting_started_in_seven_steps_and_15_minutes">
+<Title>
+<Text id="270">ÐÐ±ÑÑÐµÐœÐžÐµ Ð·Ð° 7 ÑÐ°Ð³ÐŸÐ² Ðž 15 ÐŒÐžÐœÑÑ</Text>
+</Title>
+<Content>
+<Text id="271">ÐÑÑÑÐžÐ¹ ÑÐ¿ÐŸÑÐŸÐ± Ð²Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ Ð² ÑÑÑÐµÑÑÐ²ÐŸ ÐŽÐµÐ»Ð° â ÑÑÐŸ Ð¿ÐŸÑÐŒÐŸÑÑÐµÑÑ Ðž Ð¿ÑÐŸÑÑÐ²ÑÑÐ²ÐŸÐ²Ð°ÑÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ. ÐÐœ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ ÑÐ°ÐºÑÐžÑÐµÑÐºÐž ÑÐŸÐ·ÐŽÐ°ÑÑ ÐŒÐ°Ð»ÐµÐœÑÐºÑÑ ÑÐµÑÑÐŸÐ²ÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ. ÐÑÐ»Ðž ÐÑ ÑÐ°ÑÐ¿ÐŸÐ»Ð°Ð³Ð°ÐµÑÐµ 15-Ñ ÐŒÐžÐœÑÑÐ°ÐŒÐž, Ð¿ÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, ÑÐ»ÐµÐŽÑÐ¹ÑÐµ ÑÑÐžÐŒÐž ÑÐ°Ð³Ð°ÐŒÐž, Ðž ÐÑ Ð¿ÐŸÐ¹ÐŒÐµÑÐµ ÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐœÐ°ÐŒÐœÐŸÐ³ÐŸ Ð»ÑÑÑÐµ.</Text>
+<Text id="272">ÐÐŸ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐÑ ÐœÐ°ÑÐœÐµÑÐµ ÐŸÐ±ÑÑÐµÐœÐžÐµ, ÑÐœÐ°ÑÐ°Ð»Ð° ÐžÐœÑÑÐ°Ð»Ð»ÐžÑÑÐ¹ÑÐµ Greenstone (ÑÐŒ.Â <i>Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð¿ÐŸ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Greenstone</i>), ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÐºÐ»ÑÑÐ°ÐµÑÂ <i>ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ</i>Â Ð² ÑÐŸÑÐŒÐ°ÑÐµ DLS Ðž ÐµÐµ ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÑÐ°Ð¹Ð»Ñ.Â <b>ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÑÐŸ, ÑÑÐŸ ÐµÑÐ»Ðž ÐÑ Ñ
+ÐŸÑÐžÑÐµ ÐžÐŒÐµÑÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ Ðº ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð»ÑÐ±ÐŸÐ¹ ÐžÐ· 140 ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð²Ñ
+ÐŸÐŽÑÑÐžÑ
+ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ DLS (Ð²ÐŒÐµÑÑÐŸ Ð²ÑÐµÐ³ÐŸ Ð»ÐžÑÑ 11 ÐžÐ· ÑÑÐžÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone), ÑÐŸ ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÐžÐœÑÑÐ°Ð»Ð»ÐžÑÐŸÐ²Ð°ÑÑ DLS Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŸÐŽÐœÐŸÐ³ÐŸ ÐžÐ· Ð¿ÑÐžÐŒÐµÑÐŸÐ² Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐº Greenstone.</b>Â Â  ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐ°Ñ Ðž DLS ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð±ÑÐŽÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ Ð²Â <i>C:\Program Files\gsdl\gsld\collect</i>Â Ð² ÑÑÐ±ÐŽÐžÑÐµÐºÑÐŸÑÐžÑÑ
+Â <i>demo</i>Â ÐžÂ <i>Â  dls</i>Â cÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸ. ÐÑÐ»Ðž ÐÑ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐžÐ»Ðž Greenstone Ð±ÐµÐ· DLS Ðž Ñ
+ÐŸÑÐžÑÐµ ÐžÐœÑÑÐ°Ð»Ð»ÐžÑÐŸÐ²Ð°ÑÑ ÐµÐµ, ÑÐŸ ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÐžÑÑ CD-ROM Ñ Greenstone Ðž ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐµÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÐž Ð²ÐœÐ°ÑÐ°Ð»Ðµ ÐŽÐµÐžÐœÑÑÐ°Ð»Ð»ÐžÑÐŸÐ²Ð°ÑÑ Greenstone.</Text>
+<Text id="273">ÐÑ Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÐµÐŒ, ÑÑÐŸÐ±Ñ ÐÑ ÐŸÑÐ¿ÐµÑÐ°ÑÐ°Ð»Ðž ÐžÐœÑÑÑÑÐºÑÐžÐž, ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐœÑÐµ ÐœÐžÐ¶Ðµ, Ðž ÑÐ»ÐµÐŽÐŸÐ²Ð°Ð»Ðž ÐžÐŒ ÑÐ°Ð³ Ð·Ð° ÑÐ°Ð³ÐŸÐŒ: </Text>
+<NumberedList>
+<NumberedItem>
+<Text id="274">ÐÐ°Ð¿ÑÑÑÐžÑÐµ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐŽ Windows, Ð²ÑÐ±ÐžÑÐ°ÑÂ <i>Greenstone Digital Library</i>Â ÐžÐ· ÑÐ°Ð·ÐŽÐµÐ»Ð°Â <i>Programs</i>Â Ð² ÐŒÐµÐœÑÂ Â <i>Start</i>Â Ðž Ð² ÐœÐµÐŒÂ <i>Librarian Interface</i>ÐÑÐ»Ðž ÐÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ Unix, ÑÐŸ Ð²ÐŒÐµÑÑÐŸ ÑÑÐŸÐ³ÐŸ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<CodeLine>cd gli</CodeLine>
+<CodeLine>./gli.sh</CodeLine>
+<Text id="275">Ð³ÐŽÐµÂ <i>~/gsdl</i>Â â ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐ°Ñ ÑÐžÑÑÐµÐŒÑ Greenstone.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="276">ÐÑÐ±ÐµÑÐžÑÐµÂ <i>New</i>Â ÐžÐ· ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸ ÐŒÐµÐœÑ Ð² Ð³ÐŸÑÐžÐ·ÐŸÐœÑÐ°Ð»ÑÐœÐŸÐ¹ Ð»ÐžÐœÐµÐ¹ÐºÐµ ÐŒÐµÐœÑ ÐœÐ°Ð²ÐµÑÑ
+Ñ ÐŸÐºÐœÐ°, ÐŽÐ°Ð¹ÑÐµ ÐµÐŒÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, Â«Â <i>My First Collection</i>Â Â» Ðž Ð·Ð°Ð¿ÐŸÐ»ÐœÐžÑÐµ ÐÐ°Ñ Ð°ÐŽÑÐµÑ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ Ðž ÐºÑÐ°ÑÐºÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð ÐŒÐµÐœÑ Â«Â <i>ÐÑÐœÐŸÐ²Ð° ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</i>Â Â» Ð²ÑÐ±ÐµÑÐžÑÐµ Â«Â <i>ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ Ð¿ÑÐžÐŒÐµÑ Greenstone</i>Â Â» ÐžÐ»Ðž Â«Â <i>ÐÐŸÐŽÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÑÐ°Ð·Ð²ÐžÑÐžÑ</i>Â Â» (ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ Ð±ÑÐŽÐµÑ ÑÐŸÑ Ð¶Ðµ ÑÐ°ÐŒÑÐ¹, Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ ÑÑÐž ÐŽÐ²Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐŒÐµÑÑ ÐŸÐŽÐžÐœÐ°ÐºÐŸÐ²ÑÑ ÑÑÑÑÐºÑÑÑÑ).</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="277">Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐžÐ· ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐžÐ»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž DLS, ÐµÑÐ»Ðž ÐŸÐœÐ° ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ°) Ð² ÐÐ°ÑÑ ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÑÐµÐ»ÐºÐœÐžÑÐµ ÐŽÐ²Ð°Ð¶ÐŽÑ ÐœÐ° Ð¿Ð°Ð¿ÐºÐµ Greenstone Ñ Ð»ÐµÐ²ÐŸÐ¹ ÑÑÐŸÑÐŸÐœÑ, Ð·Ð°ÑÐµÐŒ ÐŽÐ²Ð°Ð¶ÐŽÑ - ÐœÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÑÑ ÐÑ Ñ
+ÐŸÑÐžÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ. ÐÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÐœÐµÐ¹ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ Ð²ÐœÐžÐ·Ñ. ÐÑÐ±ÐµÑÐžÑÐµ ÐŸÐŽÐžÐœ ÐžÐ· ÐœÐžÑ
+, Ð¿ÐµÑÐµÑÑÐœÐžÑÐµ ÐµÐ³ÐŸ Ðž Ð¿ÐŸÐŒÐµÑÑÐžÑÐµ ÐœÐ° Ð¿Ð°ÐœÐµÐ»Ñ Ñ Ð¿ÑÐ°Ð²ÐŸÐ¹ ÑÑÐŸÑÐŸÐœÑ. Ð­ÑÐ° Ð¿Ð°ÐœÐµÐ»Ñ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐºÐŸÑÐŸÑÑÑ ÐÑ ÑÐŸÐ·ÐŽÐ°ÐµÑÐµ. ÐÑÐ±ÐµÑÐžÑÐµ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ðž Ð¿ÐµÑÐµÑÑÐœÐžÑÐµ ÐžÑ
+ Ð² ÐœÐµÐµ Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸ ÐŸÐŽÐžÐœ Ð·Ð° ÐŽÑÑÐ³ÐžÐŒ ÐžÐ»Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐµÐœÐœÑÐ¹ Ð²ÑÐ±ÐŸÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐŒ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="278">ÐÐŸÐ±Ð°Ð²ÑÑÐµ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐžÐ· ÐÐ°ÑÐžÑ
+ ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐœÐµ Ð²Ñ
+ÐŸÐŽÑÑ Ð² ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐ»Ðž DLS-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐ°ÐºÑÐŸÐ¹ÑÐµ Ð¿Ð°Ð¿ÐºÑÂ <i>Greenstone Ð¡ollections</i>Â ÐœÐ° Ð»ÐµÐ²ÐŸÐ¹ Ð¿Ð°ÐœÐµÐ»Ðž Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ 2 ÑÐ°Ð·Ð° ÐœÐ° Ð¿Ð°Ð¿ÐºÐµÂ <i>Local Filespace</i>, Ð¿ÐµÑÐµÐ¹ÐŽÐžÑÐµ Ðº ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŒÐ°Ð»ÐµÐœÑÐºÐžÐµ ÑÐ°Ð¹Ð»Ñ Word ÐžÐ»Ðž HTML). ÐÐµÑÐµÑÐ°ÑÐžÑÐµ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐžÐ· ÐœÐžÑ
+ Ð² Ð¿ÑÐ°Ð²ÑÑ Ð¿Ð°ÐœÐµÐ»Ñ, ÑÑÐŸÐ±Ñ Ð²ÐºÐ»ÑÑÐžÑÑ ÐžÑ
+ Ð² ÐÐ°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="279">ÐÐŸÐ±Ð°Ð²ÑÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ Ð² ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÐºÐ° ÐÑ ÑÐ°Ð±ÐŸÑÐ°Ð»Ðž Ð¿ÐŸÐŽ Ð¿Ð°ÐœÐµÐ»ÑÑÂ <i>Gather</i>, ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐœÐŸÐ¹ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐŒÂ <i>Gather</i>Â Ð¿ÐŸÐŽ Ð³ÐŸÑÐžÐ·ÐŸÐœÑÐ°Ð»ÑÐœÐŸÐ¹ Ð»ÐžÐœÐµÐ¹ÐºÐŸÐ¹ ÐŒÐµÐœÑ ÐœÐ°Ð²ÐµÑÑ
+Ñ ÐŸÐºÐœÐ°. Ð©ÐµÐ»ÐºÐœÐžÑÐµ ÑÐžÐŒÐ²ÐŸÐ»Â <i>Enrich</i>Â ÐŸÐºÐŸÐ»ÐŸ ÐœÐµÐµ. ÐÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐµÐ¿ÐµÑÑ Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ ÐœÐ° Ð¿Ð°ÐœÐµÐ»Ðž Ñ Ð»ÐµÐ²ÐŸÐ¹ ÑÑÐŸÑÐŸÐœÑ. Ð©ÐµÐ»ÐºÐœÐžÑÐµ ÐŸÐŽÐžÐœ ÑÐ°Ð· Ðž ÐžÑÑÐ»ÐµÐŽÑÐ¹ÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÑÐ²ÑÐ·Ð°ÐœÐœÑÐµ Ñ ÐœÐžÐŒÐž, Ð² ÑÐ°Ð±Ð»ÐžÑÐµ Â«Â <i>Ð­Ð»ÐµÐŒÐµÐœÑâŠ ÐÐœÐ°ÑÐµÐœÐžÐµ</i>Â Â» ÐœÐ°Ð²ÐµÑÑ
+Ñ ÑÐ¿ÑÐ°Ð²Ð°. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐœÐžÐ¶ÐœÑÑ Ð¿Ð°ÐœÐµÐ»Ñ, ÑÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ, Ð²ÑÐ±ÐžÑÐ°Ñ Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÑÐ¹Â <i>Ð­Ð»ÐµÐŒÐµÐœÑ</i>Â Ðž ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŽÐ»Ñ ÐœÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° ÐžÐ»Ðž Ð²ÑÐ¿ÐžÑÑÐ²Ð°Ñ ÐœÐŸÐ²ÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð² Ð¿ÐŸÐ»Ðµ ÐŸÐºÐŸÐ»ÐŸ ÐŸÑÐœÐŸÐ²Ð°ÐœÐžÑ. ÐÐŸÐ±Ð°Ð²ÑÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµÂ <i>ÐÐ°Ð·Ð²Ð°ÐœÐžÑ, ÐÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž, ÐÐ»ÑÑÐµÐ²ÑÑ
+ ÑÐ»ÐŸÐ²</i>Â Ðº ÐºÐ°Ð¶ÐŽÐŸÐŒÑ ÐžÐ· ÐÐ°ÑÐžÑ
+ ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐÑ Ð²Ð²ÐµÐ»Ðž Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐÑ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð»Ðž ÐºÐ°Ð¶ÐŽÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ, Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐµÐ»ÐºÐœÑÑÑÂ <i>Append,</i>Â Â ÑÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÑÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ðº ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒ.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="280">Ð©ÐµÐ»ÐºÐœÐžÑÐµ ÐºÐ»Ð°Ð²ÐžÑÑÂ <i>Create,</i>Â ÑÑÐŸÐ±Ñ Ð¿ÐŸÐºÐžÐœÑÑÑ ÑÐ¿ÐŸÑÐŸÐ±Â <i>Enrich</i>Â Ðž ÑÐŸÐ·ÐŽÐ°ÑÑ ÐÐ°ÑÑ ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. Ð©ÐµÐ»ÐºÐœÐžÑÐµ ÐºÐœÐŸÐ¿ÐºÑÂ <i>Build Collection</i>Â Ð² ÐŸÑÐœÐŸÐ²Ð°ÐœÐžÐž ÑÐºÑÐ°ÐœÐ°. ÐÐŸ Ð²ÑÐµÐŒÑ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐŸÐŒÂ  ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐÑ Ð±ÑÐŽÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐ°ÑÑ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÑÐ²ÐµÐŽÐµÐœÐžÑ ÐŸ ÑÐŸÐŒ, ÑÑÐŸ ÐŸÐœ ÐŽÐµÐ»Ð°ÐµÑ.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="281">ÐÐŸÐ³ÐŽÐ° ÑÑÐŸ Ð·Ð°Ð²ÐµÑÑÐµÐœÐŸ, ÑÐµÐ»ÐºÐœÐžÑÐµ ÑÐžÐŒÐ²ÐŸÐ»Â <i>ÐÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÑÐ¹ Ð¿ÑÐŸÑÐŒÐŸÑÑ</i>, ÑÑÐŸÐ±Ñ ÑÐ°ÑÑÐŒÐŸÑÑÐµÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°. ÐÑÐŸÐ²ÐµÑÑÑÐµÂ <i>ÐÐ°Ð·Ð²Ð°ÐœÐžÑ a-z, ÐÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž</i>, ÑÑÐŸÐ±Ñ ÐžÐŒÐµÑÑ ÑÐ²ÐµÑÐµÐœÐœÐŸÑÑÑ, ÑÑÐŸ ÐÐ°ÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð±ÑÐ»Ðž Ð²ÐºÐ»ÑÑÐµÐœÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÑÐž Ð¿ÐŸÑÐµÑÐµÐœÐžÐž ÐÐ°ÑÐžÑ
+ ÐŽÐŸÐŒÐ°ÑÐœÐžÑ
+ ÑÑÑÐ°ÐœÐžÑ Greenstone ÐÑ ÑÐ°ÐºÐ¶Ðµ ÐœÐ°Ð¹ÐŽÐµÑÐµ, ÑÑÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð±ÑÐ»Ð° ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÐºÐ°Ðº ÐŸÐŽÐœÐ° ÐžÐ· ÐŸÐ±ÑÑÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹.</Text>
+</NumberedItem>
+</NumberedList>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="282">ÐÑÐµ ÑÐµÐœÑ, ÑÐ¿ÐŸÐŒÑÐœÑÑÑÐµ Ð² ÑÑÐŸÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐµ, ÐŽÐ°ÐœÑ Ð² ÐŽÐŸÐ»Ð»Ð°ÑÐ°Ñ
+ Ð¡ÐšÐ, 2001 Ð³ÐŸÐŽÐ°.</Text>
+</Footnote>
+<Footnote id="2">
+<Text id="283">Recall that all sums of money are expressed in 2001 US dollars.</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/manuals/xml-source/ru/User_ru.xml
===================================================================
--- /trunk/gsdl-documentation/manuals/xml-source/ru/User_ru.xml	(revision 13632)
+++ /trunk/gsdl-documentation/manuals/xml-source/ru/User_ru.xml	(revision 13632)
@@ -0,0 +1,3370 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Manual>
+<Heading>
+<Text id="1">ÐŠÐÐ€Ð ÐÐÐÐ¯ ÐÐÐÐÐÐÐ¢ÐÐÐ GREENSTONE</Text>
+</Heading>
+<Title>
+<Text id="2">ÐÐÐ¡Ð¢Ð Ð£ÐÐŠÐÐ¯ ÐÐÐÐ¬ÐÐÐÐÐ¢ÐÐÐ¯</Text>
+</Title>
+<Author>
+<Text id="3">Ian H. Witten, Stefan Boddie and John Thompson</Text>
+</Author>
+<Affiliation>
+<Text id="4">Department of Computer Science <br/>University of Waikato, New Zealand</Text>
+</Affiliation>
+<Text id="5">Greenstone ÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐŸÐ¹, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐ¹ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ðž ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœÐžÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÑ
+ÑÑ Ð² ÑÐžÑÑÐŸÐ²ÐŸÐŒ ÑÐŸÑÐŒÐ°ÑÐµ. ÐÐœÐ° Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐœÐŸÐ²ÑÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž Ðž Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž Ð² ÐÐœÑÐµÑÐœÐµÑÐµ ÐžÐ»Ðž ÐœÐ° ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐºÐ°Ñ
+ CD-ROM. Greenstone Ð±ÑÐ» ÑÐŸÐ·ÐŽÐ°Ðœ Ð¿ÐŸ Ð¿ÑÐŸÐµÐºÑÑ New Zealand Digital Library Project Ð¿ÑÐž ÑÐœÐžÐ²ÐµÑÑÐžÑÐµÑÐµ ÐÐ°Ð¹ÐºÐ°ÑÐŸ, ÐŽÐŸÑÐ°Ð±ÐŸÑÐ°Ðœ Ðž ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœ Ð¿ÑÐž ÑÐŸÐŽÐµÐ¹ÑÑÐ²ÐžÐž Ð®ÐÐÐ¡ÐÐ Ðž ÐœÐµÐ¿ÑÐ°Ð²ÐžÑÐµÐ»ÑÑÑÐ²ÐµÐœÐœÐŸÐ¹ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž  Human info. Ð­ÑÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐŽÐŸÑÑÑÐ¿ÐœÐ° Ð²ÑÐµÐŒ ÐœÐ° ÑÐ°Ð¹ÑÐµ <i>http://greenstone.org</i> ÑÐŸÐŸÑÐ²ÐµÑÑÑÑÐµÑ ÑÑÐ»ÐŸÐ²ÐžÑÐŒ GNU General Public License.</Text>
+<Comment>
+<Text id="6">ÐÑ ÐœÐ°ÐŽÐµÐµÐŒÑÑ, ÑÑÐŸ ÑÑÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ñ
+ÐŸÑÐŸÑÐŸ. ÐÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, ÑÐŸÐŸÐ±ÑÐžÑÐµ ÐŸ Ð»ÑÐ±ÑÑ
+ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ°Ñ
+ Ð¿ÐŸÐ°ÐŽÑÐµÑÑ: greenstone@cs.waikato.ac.nz</Text>
+</Comment>
+<Version>
+<Text id="7">Greenstone gsdl-2.70</Text>
+</Version>
+<Date>
+<Text id="8">ÐÐ°ÑÑ 2006</Text>
+</Date>
+<Section id="about_this_manual">
+<Title>
+<Text id="9">ÐÐ± ÑÑÐŸÐŒ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ</Text>
+</Title>
+<Content>
+<Text id="10">Ð­ÑÐŸ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð²ÑÐµÑÑÐŸÑÐŸÐœÐœÐµÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ ÐŽÐŸÑÑÑÐ¿Ð° Ðž Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÑÐžÑÑÐŸÐ²ÑÑ
+ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐº. </Text>
+<Text id="11">Ð ÑÐ°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Chapter" ref="overview_of_greenstone"/> Ð¿ÑÐžÐ²ÐŸÐŽÐžÑÑÑ ÐºÑÐ°ÑÐºÐžÐ¹ ÐŸÐ±Ð·ÐŸÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐµÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ. Ð ÑÐ°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Chapter" ref="using_greenstone_collections"/> ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ, ÐºÐ°Ðº ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone. ÐÐœÑÐµÑÑÐµÐ¹Ñ ÑÐ°ÐŒ Ð¿ÐŸÑÑÐœÑÐµÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ: Ð»ÑÑÑÐžÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÐœÐ°ÑÑÐžÑÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ ÐžÐŒ - ÑÑÐŸ ÐŽÐµÐ»Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ Ð²ÐºÐ»ÑÑÐµÐœÐ° ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²Ð°Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ Ð¿ÐŸÐŒÐŸÑÐž Ð¿ÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÑÐžÐ¿ÐžÑÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð ÑÐ°Ð·ÐŽÐµÐ»Ðµ <CrossRef target="Chapter" ref="making_greenstone_collections"/> ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ, ÐºÐ°Ðº ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐÐ°ÑÐž ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÑÐµ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Greenstone. Ð Ð°Ð·ÐŽÐµÐ» <CrossRef target="Chapter" ref="administration"/> Ð²Ð²ÐŸÐŽÐžÑ Ð² ÑÑÐµÐŽÑÑÐ²Ð° Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ ÑÐžÑÑÐµÐŒÐœÐŸÐŒÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑÑ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑ ÑÐµÐŒ, ÑÑÐŸ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ, Ðž ÑÐµÐŒÐž, ÐºÑÐŸ ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="12">Appendices list the features of the Greenstone software, and give a glossary of terms used throughout the Greenstone documentation.</Text>
+</Content>
+</Section>
+<Section id="companion_documents">
+<Title>
+<Text id="13">Ð¡ÐŸÐ¿ÑÑÑÑÐ²ÑÑÑÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ</Text>
+</Title>
+<Content>
+<Text id="14">ÐÐŸÐ»ÐœÑÐ¹ ÐºÐŸÐŒÐ¿Ð»ÐµÐºÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÐž Ðº Greenstone ÑÐŸÑÑÐŸÐžÑ ÐžÐ· 4 ÑÐŸÐŒÐŸÐ²:</Text>
+<BulletList>
+<Bullet>
+<Text id="15">Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð¿ÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="16">ÐÐœÑÑÑÑÐºÑÐžÑ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone (ÑÑÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ)</Text>
+</Bullet>
+<Bullet>
+<Text id="17">Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐº Ð° ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone</Text>
+</Bullet>
+<Bullet>
+<Text id="18">ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: ÐŸÑ ÐÑÐŒÐ°Ð³Ðž ÐŽÐŸ ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Bullet>
+</BulletList>
+</Content>
+</Section>
+<Section id="acknowledgements">
+<Title>
+<Text id="19">ÐÐ»Ð°Ð³ÐŸÐŽÐ°ÑÐœÐŸÑÑÑ</Text>
+</Title>
+<Content>
+<Text id="20">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone - Ð¿ÑÐŸÐŽÑÐºÑ ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸÐ³ÐŸ ÑÑÑÐŽÐ° ÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ð° Ð»ÑÐŽÐµÐ¹. Rodger McNab Ðž Stefan Boddie Ð¿ÑÐžÐœÑÐžÐ¿ÐžÐ°Ð»ÑÐœÑÐµ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐž ÑÐžÑÑÐµÐŒÑ. ÐÐµÐŸÑÐµÐœÐžÐŒÑÐ¹ Ð²ÐºÐ»Ð°ÐŽ Ð²ÐœÐµÑÐ»Ðž David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, Ðž Stuart Yeates. ÐÑÑÐ°Ð»ÑÐœÑÐµ ÑÐ»ÐµÐœÑ ÐÑÐŸÐµÐºÑÐ° ÐÐŸÐ²ÐŸÐ·ÐµÐ»Ð°ÐœÐŽÑÐºÐŸÐ¹ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž  ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°Ð»Ðž Ð²ÐŽÐŸÑ
+ÐœÐŸÐ²ÐµÐœÐœÑÐ¹ ÐŽÐžÐ·Ð°Ð¹Ðœ Ð²ÑÐµÐ¹ ÑÐžÑÑÐµÐŒÑ: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols Ðž Lloyd Smith. ÐÑ ÑÐ°ÐºÐ¶Ðµ Ð²ÑÑÐ°Ð¶Ð°ÐµÐŒ ÑÐ²ÐŸÑ Ð¿ÑÐžÐ·ÐœÐ°ÑÐµÐ»ÑÐœÐŸÑÑÑ Ð²ÑÐµÐŒ ÑÐµÐŒ, ÐºÑÐŸ ÑÑÑÐŽÐžÐ»ÑÑ ÐœÐ°ÐŽ ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµÐŒ Ð¿Ð°ÐºÐµÑÐŸÐ², Ð¿ÐŸÐ¿Ð°ÐŽÐ°ÑÑÐžÑ
+ Ð¿ÐŸÐŽ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð»ÐžÑÐµÐœÐ·ÐžÐž  GNU, Ðž Ð²ÐºÐ»ÑÑÐµÐœÐœÑÑ
+ Ð² ÐŽÐžÑÑÑÐžÐ±ÑÑÐžÐ²: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE Ðž XLHTML.</Text>
+</Content>
+</Section>
+<Chapter id="overview_of_greenstone">
+<Title>
+<Text id="21">ÐÐ±Ð·ÐŸÑ Greenstone</Text>
+</Title>
+<Content>
+<Text id="22">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone - ÑÑÐŸ ÐžÑÑÐµÑÐ¿ÑÐ²Ð°ÑÑÐ°Ñ ÑÐžÑÑÐµÐŒÐ° ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÑÐŸÑÑÐŸÑÑÐžÑ
+ ÐžÐ· ÐŒÐœÐŸÐ³ÐžÑ
+ ÐŒÐžÐ»Ð»ÐžÐŸÐœÐœÐŸÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð²ÐºÐ»ÑÑÐ°ÑÑÐžÑ
+ ÑÐµÐºÑÑÑ, ÑÐžÑÑÐœÐºÐž, Ð°ÑÐŽÐžÐŸ- Ðž Ð²ÐžÐŽÐµÐŸ-ÑÐ°Ð¹Ð»Ñ.</Text>
+<Section id="collections">
+<Title>
+<Text id="23">ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="24">Ð¢ÐžÐ¿ÐžÑÐœÐ°Ñ ÑÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°, ÑÐŸÐ·ÐŽÐ°ÐœÐœÐ°Ñ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ Greenstone, ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð² ÑÐµÐ±Ðµ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐŸÑÐ³Ð°ÐœÐžÐ·ÐŸÐ²Ð°ÐœÐœÑÑ
+ Ð¿ÐŸ ÐŸÑÐŽÐµÐ»ÑÐœÐŸÑÑÐž, Ñ
+ÐŸÑÑ ÐŸÐœÐž ÐžÐŒÐµÑÑ ÐŒÐœÐŸÐ³ÐŸ ÑÑ
+ÐŸÐŽÑÑÐ²Ð° ÐŽÑÑÐ³ Ñ ÐŽÑÑÐ³ÐŸÐŒ. ÐÐµÐ³ÐºÐŸ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÐŒÑÐµ, ÑÑÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÑ Ðž Ð¿ÐµÑÐµÑÑÑÐŸÐµÐœÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž.</Text>
+<Text id="25">Ð¡ÑÑÐµÑÑÐ²ÑÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐ² Ð¿ÐŸÐžÑÐºÐ° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž Ð²ÐŸ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Greenstone. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŒÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐºÐ°ÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐµ ÑÐ»ÐŸÐ²Ð°, ÐºÐŸÑÐŸÑÑÐµ Ð²ÑÑÑÐµÑÐ°ÑÑÑÑ Ð² ÑÐµÐºÑÑÐµ ÐžÐ»Ðž Ð² ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐ¹ ÑÐ°ÑÑÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÐŸ ÐœÐ°ÐžÐŒÐµÐœÐŸÐ²Ð°ÐœÐžÑ: Ð¿ÑÐŸÑÑÐŸ ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐžÐºÐŸÐœÐºÑ ÐºÐœÐžÐ³Ðž ÐŽÐ»Ñ ÑÑÐµÐœÐžÑ. Ð¢Ð°ÐºÐ¶Ðµ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐ¹ ÑÐµÐŒÐ°ÑÐžÐºÐµ. Ð¢ÐµÐŒÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÑ Ð² Ð²ÐžÐŽÐµ ÐºÐœÐžÐ¶ÐœÑÑ
+ Ð¿ÐŸÐ»ÐŸÐº: Ð¿ÑÐŸÑÑÐŸ ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐžÐºÐŸÐœÐºÑ ÐºÐœÐžÐ¶ÐœÐŸÐ¹ Ð¿ÐŸÐ»ÐºÐž, ÑÑÐŸÐ±Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ ÐºÐœÐžÐ³Ðž. ÐÑÑÑ ÑÐ°ÐºÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, Ð² ÐºÐŸÑÐŸÑÑÑ
+ ÐžÐŒÐµÑÑÑÑ ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÑ: Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐœÐ°Ð¶Ð°ÑÑ ÐœÐ° Ð³Ð»Ð°Ð²Ñ ÐžÐ»Ðž ÐµÐµ ÑÐ°ÑÑÑ ÐŽÐ»Ñ ÐŸÑÐºÑÑÑÐžÑ, Ð° ÑÐ°ÐºÐ¶Ðµ ÐŸÑÐºÑÑÑÑ Ð¿ÐŸÐ»ÐœÐŸÐµ ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐµ Ð²ÐŸ Ð²ÐµÑÑ ÑÐºÑÐ°Ðœ ÐžÐ»Ðž Ð¿ÐŸÐ»ÐœÐŸÑÑÑÑ Ð¿ÐŸÐŒÐµÑÑÐžÑÑ Ð²ÐµÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð² ÐŸÐºÐœÐŸ Ð²Ð°ÑÐµÐ³ÐŸ Ð±ÑÐ°ÑÐ·ÐµÑÐ° (Ð¿ÐŸÐ»ÐµÐ·ÐœÐŸ Ð¿ÑÐž Ð¿ÐµÑÐ°ÑÐž). ÐÐ° Ð²ÐµÐ±-ÑÐ°Ð¹ÑÐµ New Zealand Digital Library (nzdl.org) ÐŒÐŸÐ¶ÐœÐŸ ÐœÐ°Ð¹ÑÐž ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐŸ Ð¿ÐŸÐºÐ°Ð·Ð°ÑÐµÐ»ÑÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹.</Text>
+<Text id="26">ÐÐ° Ð²ÐœÐµÑÐœÐµÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐ°Ð¿ÐžÑÐ°ÐœÐ° ÑÐµÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ, ÐºÑÐ°ÑÐºÐžÐ¹ ÐŸÐ±Ð·ÐŸÑ Ðž ÐŸÐ±ÑÑÑÐœÐµÐœÐžÐµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐŸÑÐ³Ð°ÐœÐžÐ·ÐŸÐ²Ð°ÐœÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÐºÑÑÑÑ Ð¿ÑÑÐµÐŒ Ð¿ÐŸÐžÑÐºÐ° Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°.   ÐÑÐž Ð¿ÐŸÐžÑÐºÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone Ð¿ÑÐŸÑÐŒÐ°ÑÑÐžÐ²Ð°ÐµÑ Ð²ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÐµÑÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐœÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ "full text search" "Ð¿ÐŸÐžÑÐº Ð¿ÐŸ Ð²ÑÐµÐŒÑ ÑÐµÐºÑÑÑ"). ÐÐŸ ÐŒÐœÐŸÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+ ÑÑÑÐµÑÑÐ²ÑÑÑ ÐžÐœÐŽÐµÐºÑÑ, ÑÐ°Ð·Ð±ÐžÐ²Ð°ÑÑÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐœÐ° ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ°ÑÑÐµÐ¹, Ð¿ÐŸ ÐºÐŸÑÐŸÑÑÐŒ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐ°ÐºÐ¶Ðµ ÐŒÐŸÐ¶ÐµÑ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑ Ð¿ÐŸÐžÑÐº. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐŒÐµÑÑ ÐžÐœÐŽÐµÐºÑÑ Ð¿ÐŸÐ»ÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐžÐœÐŽÐµÐºÑÑ Ð¿Ð°ÑÐ°Ð³ÑÐ°ÑÐŸÐ², ÐžÐœÐŽÐµÐºÑÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹, Ð¿ÐŸ ÐºÐ°Ð¶ÐŽÐŸÐŒÑ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑ Ð¿ÐŸÐžÑÐº ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÑÐ»ÐŸÐ² ÐžÐ»Ðž ÑÑÐ°Ð·. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐžÐœÐŽÐµÐºÑÑ, ÐŒÐŸÐ¶ÐœÐŸ ÐœÐ°Ð¹ÑÐž Ð²ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ ÐœÐ°Ð±ÐŸÑ ÑÐ»ÐŸÐ² (ÑÑÐž ÑÐ»ÐŸÐ²Ð° ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ°Ð·Ð±ÑÐŸÑÐ°ÐœÑ Ð¿ÐŸ Ð²ÑÐµÐŒÑ ÑÐµÐºÑÑÑ), ÐžÐ»Ðž Ð²ÑÐµ Ð¿Ð°ÑÐ°Ð³ÑÐ°ÑÑ Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐŒ ÐœÐ°Ð±ÐŸÑÐŸÐŒ ÑÐ»ÐŸÐ² (ÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÐ»Ð¶ÐœÑ Ð²ÑÐµ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑÑ Ð² ÑÑÐŸÐŒ Ð¿Ð°ÑÐ°Ð³ÑÐ°ÑÐµ), ÐžÐ»Ðž Ð²ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÐœÐ°Ð·Ð²Ð°ÐœÐžÑÑ
+ ÐºÐŸÑÐŸÑÑÑ
+ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑÑ ÑÑÐž ÑÐ»ÐŸÐ²Ð° (Ð²ÑÐµ ÑÐºÐ°Ð·Ð°ÐœÐœÑÐµ ÑÐ»ÐŸÐ²Ð° ÐŽÐŸÐ»Ð¶ÐœÑ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑÑ Ð² ÐœÐ°Ð·Ð²Ð°ÐœÐžÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°). Ð¢Ð°ÐºÐ¶Ðµ ÐŒÐŸÐ³ÑÑ ÑÑÑÐµÑÑÐ²ÐŸÐ²Ð°ÑÑ Ðž ÐŽÑÑÐ³ÐžÐµ ÐžÐœÐŽÐµÐºÑÑ, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ ÐžÐœÐŽÐµÐºÑÑ ÑÐµÐºÑÐžÐ¹ Ðž ÐžÐœÐŽÐµÐºÑÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹ ÑÐµÐºÑÐžÐ¹. ÐÑÐŸÑÐŒÐŸÑÑ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð² ÑÐµÐ±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ Ð¿ÐµÑÐµÑÐµÐœÑ, ÐºÐŸÑÐŸÑÑÐŒ Ð¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ: Ð¿ÐµÑÐµÑÐµÐœÑ Ð°Ð²ÑÐŸÑÐŸÐ², ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹, ÐŽÐ°Ñ, ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐŸÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÑÑÑÐºÑÑÑÑ Ðž Ñ.ÐŽ. Ð Ð°Ð·ÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÑÑ ÑÐ°Ð·ÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°.</Text>
+</Content>
+</Section>
+<Section id="finding_information">
+<Title>
+<Text id="27">ÐÐŸÐžÑÐº ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="28">Greenstone ÐžÐŒÐµÐµÑ Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÑÐµ ÐžÐœÐŽÐµÐºÑÑ- ÑÐµ ÐžÐœÐŽÐµÐºÑÑ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑ Ð¿ÐŸÐžÑÐº Ð»ÑÐ±ÑÑ
+ ÑÐ»ÐŸÐ² Ð¿ÐŸ Ð²ÑÐµÐŒÑ ÑÐµÐºÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð ÐžÐœÐŽÐµÐºÑÐ°Ñ
+ ÑÐ°ÐºÐ¶Ðµ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐºÐ°ÑÑ Ð¿ÐŸ ÐŸÐŽÐœÐŸÐŒÑ ÑÐ»ÐŸÐ²Ñ, ÐœÐ°Ð±ÐŸÑÑ ÑÐ»ÐŸÐ², ÑÑÐ°Ð·, Ð¿ÐŸÑÐ»Ðµ ÑÐµÐ³ÐŸ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑÑÑÑ Ð² ÑÐ°ÐºÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐŸÐœÐž Ð±ÐŸÐ»ÐµÐµ Ð²Ð°Ð¶ÐœÑ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ.</Text>
+<Text id="29">ÐÐŸ ÐŒÐœÐŸÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+ ÑÐ°ÐºÐžÐµ ÐŽÐ°ÐœÐœÑÐµ, ÐºÐ°Ðº Ð°Ð²ÑÐŸÑ, ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÐŽÐ°ÑÐ°, ÐºÐ»ÑÑÐµÐ²ÑÐµ ÑÐ»ÐŸÐ²Ð°, ÐžÐŒÐµÐµÑ ÐºÐ°Ð¶ÐŽÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ. Ð­ÑÐ° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐœÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž. ÐÐœÐŸÐ³ÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐŒÐµÑÑ Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÑÐµ ÐžÐœÐŽÐµÐºÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð²ÐŸ ÐŒÐœÐŸÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ ÐžÐœÐŽÐµÐºÑÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+<Text id="30">ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ðž ÐŒÐŸÐ³ÑÑ Ð¿ÑÐŸÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑ Ð¿ÐµÑÐµÑÐœÐž Ðž ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐžÐµ ÑÑÑÑÐºÑÑÑÑ. ÐÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐ²Ð»ÑÑÑÑÑ ÐœÐ°ÑÐ°Ð»ÑÐœÑÐŒ Ð¿ÑÐœÐºÑÐŸÐŒ ÐŽÐ»Ñ ÐŸÑÑÑÐµÑÑÐ²Ð»ÐµÐœÐžÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°. Ð Ð°Ð·ÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÑÑ ÑÐ°Ð·ÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°. ÐÐœÐŽÐµÐºÑÑ ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ° Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÑÐŸÐ·ÐŽÐ°ÑÑÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ "building" Ð¿ÑÐŸÑÐµÑÑÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐ°Ð¹Ð»Ð°, Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹ Ð² ÐºÐŸÐœÑÐžÐ³-ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="31">Greenstone ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð²ÑÐµ ÐžÐœÐŽÐµÐºÑÐœÑÐµ ÑÑÑÑÐºÑÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ðž Ð²ÑÐ¿ÐŸÐŒÐŸÐ³Ð°ÑÐµÐ»ÑÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ²: ÐœÐžÑÐµÐ³ÐŸ ÐœÐµ ÐœÑÐ¶ÐœÐŸ ÐŽÐµÐ»Ð°ÑÑ Ð²ÑÑÑÐœÑÑ. ÐÑÐ»Ðž Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ ÐœÐŸÐ²ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÑÐ°ÐºÐŸÐŒ Ð¶Ðµ ÑÐŸÑÐŒÐ°ÑÐµ, ÐŸÐœÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¿ÑÐžÑÐŸÐµÐŽÐžÐœÐµÐœÑ Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž. ÐÐ»Ñ ÐŒÐœÐŸÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÑÑÐž Ð¿ÑÐŸÑÐµÑÑÑ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž, Ð¿ÐŸÐžÑÐº ÐœÐŸÐ²ÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž Ðž Ð¿ÐµÑÐµÑÑÑÐŸÐ¹ÐºÐ° ÐžÐœÐŽÐµÐºÑÐŸÐ² - Ð²ÑÐµ Ð±ÐµÐ· ÑÑÑÐœÐŸÐ¹ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž.</Text>
+</Content>
+</Section>
+<Section id="document_formats">
+<Title>
+<Text id="32">Ð€ÐŸÑÐŒÐ°ÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="33">ÐÐŸÐºÑÐŒÐµÐœÑÑ, Ð²Ð¿ÐŸÑÐ»ÐµÐŽÑÑÐ²ÐžÐž ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÐŒÑÐµ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ°Ð·ÐœÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ "Ð¿Ð»Ð°Ð³ÐžÐœÐŸÐ²" ("plugins") Ð¿ÐµÑÐµÐ²ÐŸÐŽÑÑÑÑ Ð² ÐŸÐŽÐžÐœ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐ¹ ÑÐŸÑÐŒÐ°Ñ XML. ÐÐ»Ð°Ð³ÐžÐœÑ, ÐºÐŸÑÐŸÑÑÐµ ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÑÑÑÑ Ð²ÐŒÐµÑÑÐµ Ñ Greenstone, ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÑÑ Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐµÐºÑÑ, HTML, ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐŸÑÐŒÐ°ÑÐŸÐ² DOC Ðž PDF, Ð° ÑÐ°ÐºÐ¶Ðµ ÑÐŸÐŸÐ±ÑÐµÐœÐžÑ Usenet Ðž ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ (email). ÐÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÑ Ðž ÐœÐŸÐ²ÑÐµ Ð¿Ð»Ð°Ð³ÐžÐœÑ ÐŽÐ»Ñ ÐŽÑÑÐ³ÐžÑ
+ Ð²ÐžÐŽÐŸÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² (ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ ÐžÐ·ÑÑÐžÑÑ Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÐŽÐ»Ñ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ°). ÐÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÑÑÑÑÐºÑÑÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð°ÐœÐ°Ð»ÐŸÐ³ÐžÑÐœÐ°Ñ ÑÐžÑÑÐµÐŒÐ° "ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ²". Ð¡ Ð¿ÐŸÐŒÐŸÑÑÑ ÐœÐžÑ
+ ÐŒÐŸÐ¶ÐœÐŸ ÑÐŸÐ·ÐŽÐ°ÑÑ ÑÐ°Ð·ÐœÑÐµ ÐžÐœÐŽÐµÐºÑÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°: Ð°Ð»ÑÐ°Ð²ÐžÑÐœÑÐµ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ðž, ÐŽÐ°ÐœÐœÑÐµ Ðž ÑÐ°Ð·ÐœÐŸÐŸÐ±ÑÐ°Ð·ÐœÑÐµ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐžÐµ ÑÑÑÑÐºÑÑÑÑ. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ Ð»ÑÐŽÐž, ÑÐŒÐµÑÑÐžÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÑÑ Ð² Greenstone, ÐŒÐŸÐ³ÑÑ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐœÐŸÐ²ÑÐµ ÑÑÑÑÐºÑÑÑÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°.</Text>
+</Content>
+</Section>
+<Section id="multimedia_and_multilingual_documents">
+<Title>
+<Text id="34">ÐÑÐ»ÑÑÐžÐŒÐµÐŽÐžÐ¹ÐœÑÐµ Ðž ÑÐ°Ð·ÐœÐŸÑÐ·ÑÑÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ</Text>
+</Title>
+<Content>
+<Text id="35">ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÑÐµÐºÑÑ, ÑÐžÑÑÐœÐºÐž, Ð°ÑÐŽÐžÐŸ- Ðž Ð²ÐžÐŽÐµÐŸ ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ñ. ÐÐµÑÐµÐºÑÑÐŸÐ²ÐŸÐ¹ ÐŒÐ°ÑÐµÑÐžÐ°Ð» ÑÐ²ÑÐ·Ð°Ðœ Ñ ÑÐµÐºÑÑÐŸÐ²ÑÐŒ ÑÐ°Ð¹Ð»ÐŸÐŒ Ð»ÐžÐ±ÐŸ ÑÐµÑÐµÐ· ÑÑÑÐ»ÐºÑ, Ð»ÐžÐ±ÐŸ ÐžÐŒÐµÐµÑ ÑÐµÐºÑÑÐŸÐ²ÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ (ÑÐ°ÐºÐŸÐµ ÐºÐ°Ðº Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº) ÐŽÐ»Ñ ÐŸÐ±Ð»ÐµÐ³ÑÐµÐœÐžÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÐŸÐžÑÐºÐ° Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°.</Text>
+<Text id="36">Unicode, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ²Ð»ÑÐµÑÑÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐ¹ ÑÑ
+ÐµÐŒÐŸÐ¹ Ð¿ÑÐž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐž ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ², Ð¿ÑÐžÐŒÐµÐœÑÐµÐŒÑÑ
+ Ð² ÐŒÐžÑÐŸÐ²ÑÑ
+ ÑÐ·ÑÐºÐ°Ñ
+, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ Greenstone. Ð­ÑÐŸ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÐµÑÐµÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐœÐ° Ð»ÑÐ±ÐŸÐ¹ ÑÐ·ÑÐº Ðž Ð¿ÐŸÐºÐ°Ð·Ð°ÑÑ ÐµÐ³ÐŸ ÐœÐ° ÑÐºÑÐ°ÐœÐµ Ð² Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸÐ¹ ÑÐŸÑÐŒÐµ Ðž Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸÑÑÐž. ÐÑÐ»Ðž ÑÐŸÐ·ÐŽÐ°ÐœÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÐµ Ð°ÑÐ°Ð±ÑÐºÐžÐ¹, ÐºÐžÑÐ°Ð¹ÑÐºÐžÐ¹, Ð°ÐœÐ³Ð»ÐžÐ¹ÑÐºÐžÐ¹, ÑÑÐ°ÐœÑÑÐ·ÑÐºÐžÐ¹ Ðž ÐžÑÐ¿Ð°ÐœÑÐºÐžÐ¹ ÑÐ·ÑÐºÐž. ÐÑÐž ÑÐ°Ð±ÐŸÑÐµ Ñ ÑÐ°Ð·ÐœÐŸÑÐ·ÑÑÐœÑÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ ÑÐ·ÑÐº. ÐÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŽÐŸÑÑÑÐ¿ÐµÐœ ÐœÐ° Ð²ÑÐµÑ
+ Ð²ÑÑÐµÑÐ¿ÐŸÐŒÑÐœÑÑÑÑ
+ ÑÐ·ÑÐºÐ°Ñ
+ Ðž ÐŽÑÑÐ³ÐžÑ
+.</Text>
+</Content>
+</Section>
+<Section id="distributing_greenstone">
+<Title>
+<Text id="37">Ð Ð°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœÐžÐµ Greenstone</Text>
+</Title>
+<Content>
+<Text id="38">ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐŸÑÑÑÐ¿ÐœÑ Ð² ÐÐœÑÐµÑÐœÐµÑÐµ ÐžÐ»Ðž Ð¿ÑÐ±Ð»ÐžÐºÑÑÑÑÑ ÐœÐ° ÑÐ°ÐŒÐŸÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑÐžÑ
+ÑÑ ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐºÐ°Ñ
+ Ð² ÑÐ°ÐºÐŸÐŒ Ð¶Ðµ Ð²ÐžÐŽÐµ, ÐºÐ°Ðº Ð² ÐžÐœÑÐµÑÐœÐµÑÐµ. ÐÐ»Ñ ÑÐŒÐµÐœÑÑÐµÐœÐžÑ ÐŸÐ±ÑÐµÐŒÐ° ÑÐµÐºÑÑÐ° Ðž ÐžÐœÐŽÐµÐºÑÐŸÐ² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÑÐ¶Ð°ÑÐžÐµ. ÐÑÐŸÑÐŸÐºÐŸÐ» Corba Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ ÑÐ°Ð¿ÑÐŸÑÑÑÐ°ÐœÑÐµÐŒÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð³ÑÐ°ÑÐžÑÐµÑÐºÐžÐµ ÐžÐœÑÐµÑÑÐµÐ¹ÑÑ.</Text>
+<Text id="39">ÐŠÐžÑÑÐŸÐ²Ð°Ñ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° ÐÐŸÐ²ÐŸÐ¹ ÐÐµÐ»Ð°ÐœÐŽÐžÐž (nzdl.org) Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÐµÑ ÐŒÐœÐŸÐ³ÐžÐµ Ð¿ÐŸÐºÐ°Ð·Ð°ÑÐµÐ»ÑÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð²ÐºÐ»ÑÑÐ°ÑÑÐžÐµ ÐžÑÑÐŸÑÐžÑÐµÑÐºÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, Ð³ÑÐŒÐ°ÐœÐžÑÐ°ÑÐœÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ Ðž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÑÐ°Ð·Ð²ÐžÑÐžÑ, ÑÐµÑ
+ÐœÐžÑÐµÑÐºÐžÐµ ÐŽÐŸÐºÐ»Ð°ÐŽÑ Ðž Ð±ÐžÐ±Ð»ÐžÐŸÐ³ÑÐ°ÑÐžÐž, Ñ
+ÑÐŽÐŸÐ¶ÐµÑÑÐ²ÐµÐœÐœÑÐµ ÐºÐœÐžÐ³Ðž Ðž Ð¶ÑÑÐœÐ°Ð»Ñ.</Text>
+<Text id="40">ÐÑÐŽÑÑÐž ÐŸÑÐºÑÑÑÑÐŒ ÐžÑÑÐŸÑÐœÐžÐºÐŸÐŒ, Greenstone Ð³ÐŸÑÐŸÐ²Ð° Ðº ÑÐ°Ð·Ð²ÐžÑÐžÑ Ðž ÐžÐ·Ð²Ð»ÐµÐºÐ°ÑÑ Ð²ÑÐ³ÐŸÐŽÑ ÐžÐ· Ð²ÐºÐ»ÑÑÐµÐœÑÑ
+ Ð² GNU-ÐÐžÑÐµÐ·ÐžÑ ÐŒÐŸÐŽÑÐ»ÐµÐ¹ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÐŸÐžÑÐºÐ°, ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ Ð±Ð°Ð·Ð°ÐŒÐž ÐŽÐ°ÐœÐœÑÑ
+, ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÑ ÑÐµÐºÑÑÐŸÐ² ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐ¿ÐµÑÐžÑÐžÑÐœÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ². Ð¢ÐŸÐ»ÑÐºÐŸ ÑÐµÑÐµÐ· ÑÐŸÐ²ÐŒÐµÑÑÐœÐŸÐµ ÐŒÐµÐ¶ÐŽÑÐœÐ°ÑÐŸÐŽÐœÐŸÐµ ÑÐŸÑÑÑÐŽÐœÐžÑÐµÑÑÐ²ÐŸ ÑÐžÑÑÐŸÐ²ÐŸÐµ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÑÑÐ°ÐœÐµÑ ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ Ð²ÑÐµÑÑÐŸÑÐŸÐœÐœÐžÐŒ, Ð¿ÐŸÐ»ÐœÑÐŒ Ðž Ð³ÐžÐ±ÐºÐžÐŒ, ÑÐŽÐŸÐ²Ð»ÐµÑÐ²ÐŸÑÑÑÑÐžÐŒ ÐŒÐžÑÐŸÐ²ÑÐµ Ð¿ÐŸÑÑÐµÐ±ÐœÐŸÑÑÐž, ÑÑÐŸ Ðž Ð·Ð°ÑÐ»ÑÐ¶ÐžÐ²Ð°ÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ðž.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="using_greenstone_collections">
+<Title>
+<Text id="41">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Greenstone</Text>
+</Title>
+<Content>
+<Text id="42">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone ÑÐŸÐ·ÐŽÐ°ÐœÐŸ Ð¿ÐŸ Ð¿ÑÐžÐœÑÐžÐ¿Ñ Ð¿ÑÐŸÑÑÐŸÑÑ Ð² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž. ÐÐœÑÐµÑÑÐµÐ¹Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐœÐ° CD-ROM Ðž ÐŽÐŸÑÑÑÐ¿ÐœÑÑ
+ ÑÐµÑÐµÐ· ÐÐœÑÐµÑÐœÐµÑ ÐžÐŽÐµÐœÑÐžÑÐµÐœ. Ð£ÑÑÐ°ÐœÐŸÐ²ÐºÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ Greenstone Ñ CD-ROM ÐœÐ° ÐºÐŸÐŒÐ¿ÑÑÑÐµÑ Ñ ÐÐ¡ Windows ÐžÐ»Ðž Unix ÐœÐ° ÑÐ°ÐŒÐŸÐŒ ÐŽÐµÐ»Ðµ ÐŸÑÐµÐœÑ Ð¿ÑÐŸÑÑÐ°; ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð²ÐŒÐµÑÑÐµ Ñ Ð¿ÑÐµÐŽÐºÐŸÐŒÐ¿ÐžÐ»ÐžÑÐŸÐ²Ð°ÐœÐœÑÐŒ ÐŽÐ²ÐŸÐžÑÐœÑÐŒ ÐºÐŸÐŽÐŸÐŒ. ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸ ÐœÐ° ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ, Ð³ÐŽÐµ ÐŸÐœÐž Ð±ÑÐ»Ðž ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ. ÐÑÐ»Ðž ÐºÐŸÐŒÐ¿ÑÑÑÐµÑ Ð¿ÐŸÐŽÐºÐ»ÑÑÐµÐœ Ðº ÑÐµÑÐž, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²ÐžÑ Ð²ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°ÐŒ ÑÐµÑÐž ÐŽÐŸÑÑÑÐ¿ Ðº ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒ.</Text>
+<Text id="43">Ð ÑÐ»ÐµÐŽÑÑÑÐµÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐŸ, ÐºÐ°Ðº ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Greenstone Ñ CD-ROM. ÐÐ°ÑÐµÐŒ ÐŒÑ ÑÐ°ÑÑÐŒÐŸÑÑÐžÐŒ Ð¿ÐŸÐžÑÐº Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ, Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÐµÐŒÑÑ
+ ÐŸÐ±ÑÑÐœÐŸÐ¹ ÐÐŸÐ»Ð»ÐµÐºÑÐžÐ¹. "ÐÐµÐŒÐŸ" ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Greenstone Ð¿ÐŸÑÑÐ°Ð²Ð»ÑÐµÑÑÑ Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐŒ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµÐŒ Greenstone. ÐÑÑÐ³ÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ Ð¿ÑÐŸÑÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ. ÐÑÐ»Ðž Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ ÐŸÐŽÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹, ÑÐŸ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ Ð²ÑÐµÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž. Ð¡Ð»ÐµÐŽÑÑÑÐžÐ¹ ÑÐ°Ð·ÐŽÐµÐ» ÐŸÐ±ÑÑÑÐœÑÐµÑ, ÐºÐ°Ðº ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ Ð²Ð°ÑÐžÐŒÐž ÑÑÐµÐ±ÐŸÐ²Ð°ÐœÐžÑÐŒÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Preferences page (ÑÑÑÐ°ÐœÐžÑÑ Ð²ÑÐ±ÐŸÑÐ° Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÐ¹).</Text>
+<Section id="using_a_greenstone_cd-rom">
+<Title>
+<Text id="44">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ CD-ROM Greenstone</Text>
+</Title>
+<Content>
+<Text id="45">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÐŠÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Greenstone Ð¿ÐŸÑÑÐ°Ð²Ð»ÑÐµÑÑÑ ÐœÐ° CD-ROM, Ðž Ð²Ñ ÐžÐ»Ðž Ð²Ð°Ñ ÑÐžÑÑÐµÐŒÐœÑÐ¹ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÐµÐ³ÐŸ ÐŽÐ»Ñ Ð²Ð°ÑÐµÐ¹ ÑÐžÑÑÐµÐŒÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐžÐœÑÑÑÑÐºÑÐžÐž, ÐžÐ·Ð»ÐŸÐ¶ÐµÐœÐœÑÐµ Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÑÐžÐž "ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone: Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð¿ÐŸ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ". Ð ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž Greenstone ÑÐ¶Ðµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÐ¿ÑÑÑÐžÑÑ ÐŽÐ°ÐœÐœÑÐ¹ ÑÐ°Ð·ÐŽÐµÐ».</Text>
+<Text id="46">ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone Ð¿ÐŸÑÑÐ°Ð²Ð»ÑÑÑÑÑ ÐœÐ° CD-ROMe Greenstone, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐœÐ°Ð±ÐŸÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒ, ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÑÐ¹ ÐŽÐ»Ñ Ð·Ð°Ð¿ÑÑÐºÐ° ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ»Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ Ð¿ÑÐŸÑÑÐŸ Ð¿ÐŸÐŒÐµÑÑÐžÑÐµ ÐµÐ³ÐŸ Ð² CD-ROM-ÑÑÐžÑÑÐ²Ð°ÑÑÐµÐµ ÑÑÑÑÐŸÐ¹ÑÑÐ²ÐŸ ÐœÐ° ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ Ñ ÐÐ¡ Windows. ÐÐŸÑÐ»Ðµ ÑÑÐŸÐ³ÐŸ (ÐµÑÐ»Ðž, ÐºÐŸÐœÐµÑÐœÐŸ, ÐœÐ° Ð²Ð°ÑÐµÐŒ PC ÑÐ°Ð·ÑÐµÑÐµÐœÐ° Ð¿ÑÐŸÑÐµÐŽÑÑÐ° Ð°Ð²ÑÐŸÐ·Ð°Ð¿ÑÑÐºÐ°) Ð¿ÐŸÑÐ²ÐžÑÑÑ ÐŸÐºÐœÐŸ Ð¿ÑÐžÐ³Ð»Ð°ÑÐµÐœÐžÑ Ðº ÑÑÑÐ°ÐœÐŸÐ²ÐºÐµ ÐÐ GreenStone. ÐÑÐ»Ðž ÑÑÐŸÐ³ÐŸ ÐœÐµ Ð¿ÑÐŸÐžÐ·ÐŸÑÐ»ÐŸ, ÐœÐ°Ð¹ÐŽÐžÑÐµ CD-ROM ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ (ÐŽÐ»Ñ ÐÐ¡ Windows Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐºÐ»ÐžÐºÐœÑÑÑ Ð¿ÐŸ ÐžÐºÐŸÐœÐºÐµ "My Computer/ÐÐŸÐ¹ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑ" ÐœÐ° ÑÐ°Ð±ÐŸÑÐµÐŒ ÑÑÐŸÐ»Ðµ) Ðž ÐŽÐ²Ð°Ð¶ÐŽÑ ÑÐµÐ»ÐºÐœÐžÑÐµ ÐŒÑÑÑÑ Ð¿ÐŸ ÑÐ°Ð¹Ð»Ñ Setup.exe. ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Setup Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑÑÑ Ðž Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑ Ð²Ð°Ñ ÑÐµÑÐµÐ· Ð¿ÑÐŸÑÐµÐŽÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž. ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ Ð»ÑÐŽÐµÐ¹ ÐŸÑÐ²ÐµÑÐ°ÑÑ Yes/ÐÐ° ÐœÐ° Ð²ÑÐµ Ð²ÐŸÐ¿ÑÐŸÑÑ.</Text>
+<Text id="47">ÐÐŸ ÐŸÐºÐŸÐœÑÐ°ÐœÐžÐž Ð¿ÑÐŸÑÐµÐŽÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ð²Ñ ÐœÐ°Ð¹ÐŽÐµÑÐµ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ Ð² ÐŒÐµÐœÑ ÐÐ¡ Windows Start->Programs (ÐÑÑÐº->ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÑ) Ð¿ÐŸÐŽ ÐžÐŒÐµÐœÐµÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, "Development Library" ÐžÐ»Ðž "United Nations UniversityUnited...").</Text>
+<Text id="48">ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐÐ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐŸ, Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Ð±ÑÐŽÐµÑ ÐŸÑÐºÑÑÐ²Ð°ÑÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐ°Ð·, ÐºÐŸÐ³ÐŽÐ° Ð²Ñ Ð²ÑÑÐ°Ð²Ð»ÑÐµÑÐµ CD-ROM, ÐµÑÐ»Ðž, ÐºÐŸÐœÐµÑÐœÐŸ, ÑÐ°Ð·ÑÐµÑÐµÐœÐ° Ð¿ÑÐŸÑÐµÐŽÑÑÐ° Ð°Ð²ÑÐŸÐ·Ð°Ð¿ÑÑÐºÐ°.</Text>
+</Content>
+</Section>
+<Section id="finding_information_1">
+<Title>
+<Text id="49">ÐÐŸÐžÑÐº ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="50">Ð¡Ð°ÐŒÑÐ¹ Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÐœÐ°ÑÑÐžÑÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž Greenstone - ÑÑÐŸ Ð¿ÑÐŸÑÑÐŸ Ð¿ÐŸÐ¿ÑÐŸÐ±ÐŸÐ²Ð°ÑÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ð² ÐœÐžÑ
+. ÐÐµ Ð²ÐŸÐ»ÐœÑÐ¹ÑÐµÑÑ, Ð²Ñ ÐœÐžÑÐµÐ³ÐŸ ÐœÐµ ÑÐ»ÐŸÐŒÐ°ÐµÑÐµ. ÐÐ°Ð¶ÐžÐŒÐ°Ð¹ÑÐµ ÐœÐ° ÐžÐºÐŸÐœÐºÐž Ð±ÐµÐ· ÐºÐŸÐ»ÐµÐ±Ð°ÐœÐžÐ¹. ÐÑÐ»Ðž Ð²Ñ Ð·Ð°ÐŽÐµÑÐ¶ÐžÑÐµ ÐºÑÑÑÐŸÑ ÐŒÑÑÐž ÐœÐ° ÐžÐºÐŸÐœÐºÐµ ÐœÐ° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ Ð¿ÐµÑÐžÐŸÐŽ, ÑÐŸ Ð¿ÐŸÑÐ²ÐžÑÑÑ ÐœÐµÐ±ÐŸÐ»ÑÑÐŸÐµ Ð¿ÐŸÑÑÐœÐµÐœÐžÐµ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐœÐ°Ð¿ÐžÑÐ°ÐœÐŸ, ÑÑÐŸ ÑÐ»ÑÑÐžÑÑÑ Ð¿ÐŸÑÐ»Ðµ ÐœÐ°Ð¶Ð°ÑÐžÑ.</Text>
+<Text id="51">Ð­ÐºÑÐ¿ÐµÑÐžÐŒÐµÐœÑÐžÑÑÐ¹ÑÐµ! ÐÐ°Ð±ÐžÑÐ°Ð¹ÑÐµ ÑÐ°ÐºÐžÐµ ÑÐŸÑÐ·Ñ ÐºÐ°Ðº "Ðž"Ð² ÐŸÐºÐœÐµ Ð¿ÐŸÐžÑÐºÐ° Ðž Ð¶ÐŒÐžÑÐµ ÐœÐ° Ð¿ÐŸÐžÑÐº, Ð¿ÐŸÑÐ»Ðµ ÑÐµÐ³ÐŸ Ð¿ÐŸÑÐ²ÑÑÑÑ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÑ Ð¿ÐŸÐžÑÐºÐ°. ÐÐ°Ðº Ð²ÐžÐŽÐžÑÐµ, ÐœÐžÑÐµÐ³ÐŸ ÐœÐµ ÑÐ»ÐŸÐŒÐ°Ð»ÐŸÑÑ.</Text>
+<Text id="52">ÐŠÐžÑÑÐŸÐ²ÑÐµ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐµ ÑÐžÑÑÐµÐŒÑ Greenstone, ÐºÐ°Ðº Ð¿ÑÐ°Ð²ÐžÐ»ÐŸ, ÑÐŸÑÑÐŸÑÑ ÐžÐ· ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ - ÑÐ°ÐºÐžÑ
+, ÐºÐ°Ðº ÑÐµÑ
+ÐœÐžÑÐµÐºÐžÐµ ÐŽÐŸÐºÐ»Ð°ÐŽÑ ÐžÐ· ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐœÐŸÐ¹ ÑÑÐµÑÑ, Ñ
+ÑÐŽÐŸÐ¶ÐµÑÑÐ²ÐµÐœÐœÑÐµ ÐºÐœÐžÐ³Ðž, Ð¶ÑÑÐœÐ°Ð»Ñ Ðž Ñ.ÐŽ. Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ WWW-ÑÑÑÐ°ÐœÐžÑÐ° ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÑÐºÑÑÐ²Ð°ÐµÑ ÐŽÐŸÑÑÑÐ¿ Ðº Ð»ÑÐ±ÑÐŒ ÐŸÐ±ÑÐµÐŽÐŸÑÑÑÐ¿ÐœÑÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒ: Ðº ÑÐŸÐŒÑ Ð¶Ðµ ÐºÐ°Ð¶ÐŽÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐŒÐµÐµÑ ÐŸÐ·ÐœÐ°ÐºÐŸÐŒÐžÑÐµÐ»ÑÐœÑÑ ÑÑÑÐ°ÐœÐžÑÐºÑ, Ð² ÐºÐŸÑÐŸÑÐŸÐ¹ ÑÐŸÐŽÐµÑÐ¶ÐžÑÑÑ ÐžÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÑÐŸÐŒ, ÐºÐ°Ðº ÐŸÑÐ³Ð°ÐœÐžÐ·ÐŸÐ²Ð°ÐœÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ðž ÑÑÐŸ Ð² ÐœÐµÐ¹ ÐµÑÑÑ. Ð§ÑÐŸÐ±Ñ Ð²ÐµÑÐœÑÑÑÑÑ ÐœÐ° ÑÑÑ ÑÑÑÐ°ÐœÐžÑÐºÑ Ð² Ð»ÑÐ±ÐŸÐµ Ð²ÑÐµÐŒÑ, Ð¿ÑÐŸÑÑÐŸ ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐžÐºÐŸÐœÐºÑ "ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ", ÐºÐŸÑÐŸÑÐ°Ñ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² Ð²ÐµÑÑ
+ÐœÐµÐŒ Ð»ÐµÐ²ÐŸÐŒ ÑÐ³Ð»Ñ ÑÑÑÐ°ÐœÐžÑÑ.</Text>
+<Text id="53">ÐÐ° Ð ÐžÑÑÐœÐºÐµ 1 ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð²ÐºÐ»ÑÑÐµÐœÐ° Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone, ÐŸÐœÐ° ÑÐ²Ð»ÑÐµÑÑÑ ÐŸÑÑÑÐ²ÐºÐŸÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ð Ð°Ð·Ð²ÐžÑÐžÑ. ÐÑ Ð±ÑÐŽÐµÐŒ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐµÐµ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð¿ÑÐžÐŒÐµÑÐ° ÐŽÐ»Ñ ÑÐ°Ð·ÐœÐŸÐ³ÐŸ Ð²ÐžÐŽÐ° Ð¿ÐŸÐžÑÐºÐ° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž. ÐÑÐ»Ðž Ð²Ñ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ ÐœÐ°Ð¹ÑÐž ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ ÑÐ°Ð·Ð²ÐžÑÐžÑ; ÐŸÐœÐž Ð²ÑÐ³Ð»ÑÐŽÑÑ ÐŸÐŽÐžÐœÐ°ÐºÐŸÐ²ÐŸ. ÐÐŸ-Ð¿ÐµÑÐ²ÑÑ
+, Ð¿ÑÐ°ÐºÑÐžÑÐµÑÐºÐž ÐœÐ° Ð²ÑÐµ ÐžÐºÐŸÐœÐºÐž ÐŒÐŸÐ¶ÐœÐŸ ÐœÐ°Ð¶ÐžÐŒÐ°ÑÑ. ÐÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐžÐºÐŸÐœÐŸÐº ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ ÐœÐ°Ð²ÐµÑÑ
+Ñ Ð¿ÐŸÑÑÐž ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ. Ð¢Ð°Ð±Ð»ÐžÑÐ° 1 Ð³ÐŸÐ²ÐŸÑÐžÑ ÐŸ ÑÐŸÐŒ, ÑÑÐŸ ÐŸÐœÐž ÐŸÐ·ÐœÐ°ÑÐ°ÑÑ.</Text>
+<Figure id="using_the_demo_collection">
+<Title>
+<Text id="54">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÐµÐŒÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<File width="397" height="286" url="images/User_Fig_1.png"/>
+</Figure>
+<Table id="what_the_icons_at_the_top_of_each_page_mean">
+<Title>
+<Text id="55">ÐÐœÐ°ÑÐµÐœÐžÑ ÐžÐºÐŸÐœÐŸÐº, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÑ
+ÑÑ ÐœÐ° Ð²ÐµÑÑ
+ÐœÐµÐ¹ Ð¿Ð°ÐœÐµÐ»Ðž</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="132">
+<File width="68" height="32" url="images/User_Icon_1.png"/>
+</th>
+<th width="397">
+<Text id="56">ÐÐœÐ° ÑÐŸÐµÐŽÐžÐœÑÐµÑ Ð²Ð°Ñ ÑÐŸ ÑÑÑÐ°ÐœÐžÑÐµÐ¹ "ÐŸÐ·ÐœÐ°ÐºÐŸÐŒÐ»ÐµÐœÐžÑ" (ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž)</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<File width="36" height="16" url="images/User_Icon_2.png"/>
+</th>
+<th width="397">
+<Text id="57">ÐÐœÐ° Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ Ð²Ð°Ñ Ðº ÐœÐ°ÑÐ°Ð»ÑÐœÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ, Ñ ÐºÐŸÑÐŸÑÐŸÐ¹ ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÐºÑÑÑÑ ÐŽÑÑÐ³ÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<File width="29" height="16" url="images/User_Icon_3.png"/>
+</th>
+<th width="397">
+<Text id="58">ÐÐŸÑÐ²Ð»ÑÐµÑÑÑ ÑÐµÐºÑÑ, Ð¿ÐŸÑ
+ÐŸÐ¶ÐžÐ¹ ÐœÐ° ÑÐŸÑ, ÑÑÐŸ Ð²Ñ ÑÐžÑÐ°ÐµÑÐµ ÑÐµÐ¹ÑÐ°Ñ</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<File width="70" height="16" url="images/User_Icon_4.png"/>
+</th>
+<th width="397">
+<Text id="59">ÐÐ°ÐµÑ Ð²Ð°ÐŒ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÐœÐ°ÑÑÑÐŸÐžÑÑ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ðž ÑÐµÐ¶ÐžÐŒ Ð¿ÐŸÐžÑÐºÐ°, ÐºÐŸÑÐŸÑÑÐ¹ Ð±ÑÐŽÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ðœ</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="60">ÐÐ°ÐœÐµÐ»Ñ "Ð¿ÐŸÐžÑÐº... ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ñ.... ÐœÐ°Ð·Ð²Ð°ÐœÐžÑ Ð°-Ñ..ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž... ÑÐ¿ÐŸÑÐŸÐ±Ñ" ÐŽÐ°ÐµÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÑÐ°Ð·ÐœÑÐŒ ÑÐµÐ¶ÐžÐŒÐ°ÐŒ Ð¿ÐŸÐžÑÐºÐ° Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°. Ð¡Ð°ÐŒÐ°Ñ Ð»ÐµÐ²Ð°Ñ ÐžÐºÐŸÐœÐºÐ° Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐ° ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ°, Ð° ÑÐµÑÑÑÐµ ÑÐ¿ÑÐ°Ð²Ð° -Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑ Ð² ÑÐ°Ð·ÐœÑÑ
+ ÑÐµÐ¶ÐžÐŒÐ°Ñ
+. Ð­ÑÐž Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐµ ÑÐµÑÑÑÐµ ÐºÐœÐŸÐ¿ÐºÐž ÐŒÐŸÐ³ÑÑ Ð²Ð°ÑÑÐžÑÐŸÐ²Ð°ÑÑÑÑ ÐŸÑ ÐŸÐŽÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðº ÐŽÑÑÐ³ÐŸÐ¹.</Text>
+<Subsection id="how_to_find_information">
+<Title>
+<Text id="61">ÐÐ°Ðº ÐœÐ°Ð¹ÑÐž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ</Text>
+</Title>
+<Content>
+<Text id="62">Ð¢Ð°Ð±Ð»ÐžÑÐ° 2 ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ Ð¿ÑÑÑ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐ² Ð¿ÐŸÐžÑÐºÐ° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐœÐ° ÐÐµÐŒÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Table id="table_icons_on_the_search_browse_bar">
+<Title>
+<Text id="63">ÐÐœÐ°ÑÐµÐœÐžÑ ÐžÐºÐŸÐœÐŸÐº Ð¿ÐŸÐžÑÐº\Ð¿ÑÐŸÑÐŒÐŸÑÑ</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="123">
+<File width="61" height="11" url="images/User_Icon_5.png"/>
+</th>
+<th width="407">
+<Text id="64">Ð¿ÐŸÐžÑÐº Ð¿ÐŸ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÐŒ ÑÐµÑÐŒÐžÐœÐ°ÐŒ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="58" height="11" url="images/User_Icon_6.png"/>
+</th>
+<th width="407">
+<Text id="65">ÐÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐµ Ð¿ÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐžÑ ÑÐ°Ð±ÐŸÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="58" height="11" url="images/User_Icon_7.png"/>
+</th>
+<th width="407">
+<Text id="66">ÐÑÐµÐŽÐŒÐµÑÐœÑÐ¹ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ñ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="71" height="11" url="images/User_Icon_8.png"/>
+</th>
+<th width="407">
+<Text id="67">ÐÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐµ Ð¿ÐŸ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑÐŒ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="58" height="11" url="images/User_Icon_9.png"/>
+</th>
+<th width="407">
+<Text id="68">ÐÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐµ Ð¿ÐŸ ÑÐ¿ÐŸÑÐŸÐ±Ñ Ð¿ÑÐžÐŒÐµÐœÐµÐœÐžÑ.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="69">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐºÐ°ÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐµ ÑÐ»ÐŸÐ²Ð°, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÐµÑÑ Ð² ÑÐµÐºÑÑÐµ ÑÐµÑÐµÐ· ÑÑÑÐ°ÐœÐžÑÑ "Ð¿ÐŸÐžÑÐº". ÐÐ° Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÑ ÑÑÑÐ°ÐœÐžÑÑ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÐŸÐ¿Ð°ÑÑÑ Ñ Ð»ÑÐ±ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ, ÐœÐ°Ð¶Ð°Ð² ÐºÐœÐŸÐ¿ÐºÑ ÐÐŸÐžÑÐº. Ð¢Ð°ÐºÐ¶Ðµ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ Ð¿ÑÐ±Ð»ÐžÐºÐ°ÑÐžÐž ÐœÐ° ÑÐµÐŒÑ, ÐœÐ°Ð¶Ð°Ð² ÐœÐ° ÐºÐœÐŸÐ¿ÐºÑ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ñ. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÑÐµÑÑÐ²ÐžÑÑ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÐŒ ÑÐµÑÐŒÐžÐœÐ°ÐŒ ÑÐŸ ÑÑÑÐ°ÐœÐžÑÑ Ð¿ÐŸÐžÑÐºÐ°. Ð­ÑÐ° ÑÑÑÐ°ÐœÐžÑÐ° ÑÐ²Ð»ÑÐµÑÑÑ ÑÑÐ°ÑÑÐŸÐ²ÐŸÐ¹, ÐºÐŸÐ³ÐŽÐ° Ð²Ñ ÐœÐ°ÑÐžÐœÐ°ÐµÑÐµ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹, Ðž ÐœÐ° ÐœÐµÐµ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÐŸÐ¿Ð°ÑÑÑ Ñ Ð»ÑÐ±ÑÑ
+ ÐŽÑÑÐ³ÐžÑ
+ ÑÑÑÐ°ÐœÐžÑ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐœÐ°Ð¶Ð°ÑÐžÑ ÐºÐœÐŸÐ¿ÐºÐž ÐÐŸÐžÑÐº. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ Ð¿ÑÐµÐŽÐŒÐµÑÐœÑÐŒ ÑÐºÐ°Ð·Ð°ÑÐµÐ»ÐµÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž , ÐœÐ°Ð¶Ð°Ð² ÐºÐœÐŸÐ¿ÐºÑ Ð£ÐºÐ°Ð·Ð°ÑÐµÐ»Ñ. ÐÑÐµÐŽÐŒÐµÑÐœÑÐ¹ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœ Ð¿ÐŸ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐŸÐŒÑ Ð¿ÑÐžÐœÑÐžÐ¿Ñ Ðž ÐŽÐ°ÐµÑ ÐœÐ°ÐžÐ±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐ»ÐœÐŸÐµ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐµ Ð¿ÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐžÑÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐœÐ°Ð¶Ð°ÑÐžÐµÐŒ ÐºÐœÐŸÐ¿ÐºÐž ÐÐ°Ð·Ð²Ð°ÐœÐžÑ Ð-Ð¯. Ð ÑÑÐŸÐŒ ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐž Ð²Ñ ÑÐ²ÐžÐŽÐžÑÐµ ÑÐ¿ÐžÑÐŸÐº ÐºÐœÐžÐ³ Ð² Ð°Ð»ÑÐ°Ð²ÐžÑÐœÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐµ Ð¿ÐŸ ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑÐŒ ÐœÐ°Ð¶Ð°ÑÐžÐµÐŒ ÐºÐœÐŸÐ¿ÐºÐž ÐÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž. Ð ÑÑÐŸÐŒ ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐž Ð²Ñ ÑÐ²ÐžÐŽÐžÑÐµ ÑÐ¿ÐžÑÐŸÐº ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐ¹. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐµ Ð¿ÐŸ ÑÐ¿ÐŸÑÐŸÐ±Ð°ÐŒ Ð¿ÑÐžÐŒÐµÐœÐµÐœÐžÑ ÐœÐ°Ð¶Ð°ÑÐžÐµÐŒ ÐºÐœÐŸÐ¿ÐºÐž Ð¡Ð¿ÐŸÑÐŸÐ±. Ð ÑÑÐŸÐŒ ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐž Ð²Ñ ÑÐ²ÐžÐŽÐžÑÐµ ÑÐ¿ÐžÑÐŸÐº Ð¿ÑÐ°ÐºÑÐžÑÐµÑÐºÐžÑ
+ ÑÐµÐºÐŸÐŒÐµÐœÐŽÐ°ÑÐžÐ¹, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÑ
+ÑÑ Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°Ñ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. All these buttons are visible in Figure 1.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_to_read_the_documents">
+<Title>
+<Text id="70">ÐÐ°Ðº ÑÐžÑÐ°ÑÑ ÐºÐœÐžÐ³Ðž</Text>
+</Title>
+<Content>
+<Text id="71">ÐÐŸÐ³ÐŽÐ° Ð²Ñ ÐŸÑÐºÑÐŸÐµÑÐµ ÐºÐ°ÐºÑÑ-ÐœÐžÐ±ÑÐŽÑ ÐºÐœÐžÐ³Ñ, Ð²Ñ ÑÐ²ÐžÐŽÐžÑÐµ ÑÐžÑÑÐœÐŸÐº ÐµÐµ ÐŸÐ±Ð»ÐŸÐ¶ÐºÐž Ð² Ð»ÐµÐ²ÐŸÐŒ Ð²ÐµÑÑ
+ÐœÐµÐŒ ÑÐ³Ð»Ñ ÑÑÑÐ°ÐœÐžÑÑ. ÐÑÐŸÐŒÐµ ÑÐžÑÑÐœÐºÐ° ÐŸÐ±Ð»ÐŸÐ¶ÐºÐž, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐœÐ°Ð¹ÑÐž ÑÐ°Ð±Ð»ÐžÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ. Ð¢Ð°Ð±Ð»ÐžÑÐ° ÐŒÐŸÐ¶ÐµÑ ÑÐ°ÑÑÐžÑÑÑÑÑÑ: ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° Ð¿Ð°Ð¿ÐºÐž, ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ ÐŸÑÐºÑÑÑÑ ÐžÐ»Ðž Ð·Ð°ÐºÑÑÑÑ ÐžÑ
+. ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐŸÑÐºÑÑÑÑÑ ÐºÐœÐžÐ³Ñ Ð²Ð²ÐµÑÑ
+Ñ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ, ÑÑÐŸÐ±Ñ Ð·Ð°ÐºÑÑÑÑ ÐµÐµ.</Text>
+<Text id="72">ÐÐžÐ¶Ðµ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÑÐµÐºÑÑ ÑÐµÐºÑÑÐµÐ³ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð°. ÐÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº Ð²Ñ Ð¿ÑÐŸÑÐžÑÐ°ÐµÑÐµ ÐµÐ³ÐŸ, Ð²ÐœÐžÐ·Ñ Ð²Ñ ÑÐ²ÐžÐŽÐžÑÐµ ÑÑÑÐµÐ»ÐºÐž ÐŽÐ»Ñ Ð¿ÐµÑÐµÑ
+ÐŸÐŽÐ° Ðº ÑÐ»ÐµÐŽÑÑÑÐµÐŒÑ ÐžÐ»Ðž Ð¿ÑÐµÐŽÑÐŽÑÑÐµÐŒÑ ÑÐ°Ð·ÐŽÐµÐ»Ñ.</Text>
+<Text id="73">ÐÐžÐ¶Ðµ ÑÐŸÑÐŸÐ³ÑÐ°ÑÐžÐž ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐºÐœÐŸÐ¿ÐŸÐº. ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐÐµÑÑ ÑÐµÐºÑÑ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐŸÑÐŸÐ±ÑÐ°Ð·ÐžÑÑ ÐœÐ° ÑÐºÑÐ°ÐœÐµ Ð²ÐµÑÑ ÑÐµÐºÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÑÐ»Ðž ÐºÐœÐžÐ³Ð° ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ Ð±ÐŸÐ»ÑÑÐ°Ñ, ÑÐŸ ÑÑÐŸ ÐŒÐŸÐ¶ÐµÑ Ð·Ð°ÐœÑÑÑ ÐœÐµÐºÐŸÑÐŸÑÐŸÐµ Ð²ÑÐµÐŒÑ Ðž ÐŒÐœÐŸÐ³ÐŸ Ð¿Ð°ÐŒÑÑÐž. ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐŸÑÐŸÐ±ÑÐ°Ð·ÐžÐ»ÐŸÑÑ Ð²ÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ, Ð³ÐŽÐµ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ²ÐžÐŽÐµÑÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐž Ð²ÑÐµÑ
+ Ð³Ð»Ð°Ð² Ðž Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ². ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° Ð ÐœÐŸÐ²ÐŸÐŒ ÐŸÐºÐœÐµ ÑÑÐŸÐ±Ñ ÐŸÑÐŸÐ±ÑÐ°Ð·ÐžÑÑ ÐŽÐ°ÐœÐœÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð² ÐœÐŸÐ²ÐŸÐŒ ÐŸÐºÐœÐµ. Ð­ÑÐŸ Ð±ÑÐ²Ð°ÐµÑ Ð¿ÐŸÐ»ÐµÐ·ÐœÐŸ, ÐµÑÐ»Ðž Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ ÑÑÐ°Ð²ÐœÐžÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐžÐ»Ðž ÑÐžÑÐ°ÑÑ ÑÑÐ°Ð·Ñ ÐŽÐ²Ð°. ÐÐ°ÐºÐŸÐœÐµÑ, ÐµÑÐ»Ðž Ð²Ñ ÐœÐ°ÑÐ»Ðž ÑÑÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð¿ÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐŒ ÑÐ»ÐŸÐ²Ð°ÐŒ, ÑÐŸ ÐŸÐœÐž Ð±ÑÐŽÑÑ Ð²ÑÐŽÐµÐ»ÐµÐœÑ Ð² ÑÐµÐºÑÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° Ð¡ÐœÑÑÑ Ð²ÑÐŽÐµÐ»ÐµÐœÐžÐµ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐžÑÐºÐŸÐŒÑÐµ ÑÐ»ÐŸÐ²Ð° ÐœÐµ Ð²ÑÐŽÐµÐ»ÑÐ»ÐžÑÑ Ð² ÑÐµÐºÑÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°.</Text>
+<Text id="74"></Text>
+<Figure id="a_book_in_the_demo_collection">
+<Title>
+<Text id="75">ÐÐœÐžÐ³Ð° Ð² ÐÐµÐŒÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<File width="397" height="476" url="images/User_Fig_2.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="what_the_icons_mean">
+<Title>
+<Text id="76">Ð§ÑÐŸ ÐŸÐ·ÐœÐ°ÑÐ°ÑÑ ÐžÐºÐŸÐœÐºÐž</Text>
+</Title>
+<Content>
+<Text id="77">ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð²Ñ ÑÑÐŸÐ»ÐºÐœÐµÑÐµÑÑ Ñ ÑÐ»ÐµÐŒÐµÐœÑÐ°ÐŒÐž, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÑÐŒÐž Ð² Ð¢Ð°Ð±Ð»ÐžÑÐµ 3.</Text>
+</Content>
+</Subsection>
+<Subsection id="how_to_search_for_particular_words">
+<Title>
+<Text id="78">ÐÐ°Ðº ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÐŒ ÑÐµÑÐŒÐžÐœÐ°ÐŒ</Text>
+</Title>
+<Content>
+<Text id="79">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŽÐµÐ»Ð°ÑÑ Ð¿ÑÐŸÑÑÐŸÐ¹ Ð·Ð°Ð¿ÑÐŸÑ ÑÐŸ ÑÑÑÐ°ÐœÐžÑÑ Ð¿ÐŸÐžÑÐºÐ°, ÑÐŸÐ³Ð»Ð°ÑÐœÐŸ ÑÐ»ÐµÐŽÑÑÑÐžÑ
+ ÑÐ°Ð³ÐŸÐ²:</Text>
+<BulletList>
+<Bullet>
+<Text id="80">ÐÐ¿ÑÐµÐŽÐµÐ»ÐžÑÐµ ÑÑÐŸ Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ ÐœÐ°Ð¹ÑÐž</Text>
+</Bullet>
+<Bullet>
+<Text id="81">ÐÐ¿ÑÐµÐŽÐµÐ»ÐžÑÐµ, ÐºÐ°Ðº Ð²Ñ ÑÑÐŸ Ñ
+ÐŸÑÐžÑÐµ ÐžÑÐºÐ°ÑÑ: ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÑÑÐ°Ð·Ñ ÐžÐ»Ðž ÐŸÑÐŽÐµÐ»ÑÐœÑÐµ ÑÐ»ÐŸÐ²Ð°</Text>
+</Bullet>
+<Bullet>
+<Text id="82">ÐÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ ÑÐµÐºÑÑ Ð·Ð°Ð¿ÑÐŸÑÐ° Ð² ÑÑÑÐŸÐºÐµ Ð¿ÐŸÐžÑÐºÐ°</Text>
+</Bullet>
+<Bullet>
+<Text id="83">ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐºÐœÐŸÐ¿ÐºÑ ÐÐ°ÑÐ°ÑÑ Ð¿ÐŸÐžÑÐº</Text>
+</Bullet>
+</BulletList>
+<Text id="84">ÐÐŸÑÐ»Ðµ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ Ð·Ð°Ð¿ÑÐŸÑÐ° ÐœÐ° ÑÐºÑÐ°ÐœÐµ Ð¿ÐŸÑÐ²ÐžÑÑÑ 20 ÐœÐ°ÐžÐŒÐµÐœÐŸÐ²Ð°ÐœÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². Ð ÐºÐŸÐœÑÐµ ÑÐ¿ÐžÑÐºÐ° ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐºÐœÐŸÐ¿ÐºÐ°, Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐºÐŸÑÐŸÑÐŸÐ¹ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐ¹ÑÐž Ðº ÑÐ»ÐµÐŽÑÑÑÐžÐŒ 20. ÐÐ° ÑÐ»ÐµÐŽÑÑÑÐžÑ
+ ÑÑÑÐ°ÐœÐžÑÐ°Ñ
+ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² Ð²Ñ ÑÐ²ÐžÐŽÐžÑÐµ ÐºÐœÐŸÐ¿ÐºÐž ÐŽÐ»Ñ Ð¿ÐµÑÐµÑ
+ÐŸÐŽÐ° Ðº ÑÐ»ÐµÐŽÑÑÑÐžÐŒ 20 ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ ÐžÐ»Ðž ÐŸÐ±ÑÐ°ÑÐœÐŸ Ðº Ð¿ÑÐµÐŽÑÐŽÑÑÐžÐŒ Ðž Ñ.ÐŽ. ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ Ð»ÑÐ±ÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐžÐ»Ðž Ð·ÐœÐ°ÑÐŸÐº Ð¿ÐµÑÐµÐŽ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµÐŒ, ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ ÐµÐ³ÐŸ. ÐÐ°ÐºÑÐžÐŒÐ°Ð»ÑÐœÐŸÐµ ÑÐžÑÐ»ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐ° Ð¿ÐŸÐžÑÐºÐ° - 100. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÑÑÐŸ ÑÐžÑÐ»ÐŸ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ ÐœÐ°ÑÑÑÐŸÐµÐº ( ÐºÐœÐŸÐ¿ÐºÐ° ÐÐ°ÑÑÑÐŸÐ¹ÐºÐž Ð²Ð²ÐµÑÑ
+Ñ ÑÑÑÐ°ÐœÐžÑÑ ).</Text>
+<Table id="table_icons_that_you_will_encounter_when_browsing">
+<Title>
+<Text id="85">ÐÐºÐŸÐœÐºÐž, Ñ ÐºÐŸÑÐŸÑÑÐŒÐž Ð²Ñ Ð±ÑÐŽÐµÑÐµ ÑÐ°Ð±ÐŸÑÐ°ÑÑ</Text>
+</Title>
+<TableContent>
+<tr>
+<th width="123">
+<File width="19" height="12" url="images/User_Icon_10.png"/>
+</th>
+<th width="407">
+<Text id="86">ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐžÐºÐŸÐœÐºÑ ÐºÐœÐžÐ³Ðž, ÑÑÐŸÐ±Ñ ÑÐžÑÐ°ÑÑ ÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ ÐºÐœÐžÐ³Ñ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="22" height="17" url="images/User_Icon_11.png"/>
+</th>
+<th width="407">
+<Text id="87">ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐžÐºÐŸÐœÐºÑ ÐºÐœÐžÐ¶ÐœÐŸÐ¹ Ð¿ÐŸÐ»ÐºÐž, ÑÑÐŸÐ±Ñ ÑÐŒÐŸÑÑÐµÑÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="25" height="16" url="images/User_Icon_12.png"/>
+</th>
+<th width="407">
+<Text id="88">ÐºÐœÐžÐ³Ðž Ð¿ÐŸ ÑÑÐŸÐ¹ ÑÐµÐŒÐµ. Ð¡ÐŒÐŸÑÑÐµÑÑ ÑÑÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="25" height="16" url="images/User_Icon_13.png"/>
+</th>
+<th width="407">
+<Text id="89">ÐÑÐºÑÐŸÐ¹ÑÐµ ÑÑÑ Ð¿Ð°Ð¿ÐºÑ Ðž Ð¿ÐŸÑÐŒÐŸÑÑÐžÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="29" height="25" url="images/User_Icon_14.png"/>
+</th>
+<th width="407">
+<Text id="90">ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐžÐºÐŸÐœÐºÑ, ÑÑÐŸÐ±Ñ Ð·Ð°ÐºÑÑÑÑ ÐºÐœÐžÐ³Ñ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="25" height="17" url="images/User_Icon_15.png"/>
+</th>
+<th width="407">
+<Text id="91">ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐžÐºÐŸÐœÐºÑ, ÑÑÐŸÐ±Ñ Ð·Ð°ÐºÑÑÑÑ Ð¿Ð°Ð¿ÐºÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="32" height="17" url="images/User_Icon_16.png"/>
+</th>
+<th width="407">
+<Text id="92">ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÑÑÑÐµÐ»ÐºÑ, ÑÑÐŸÐ±Ñ Ð¿ÐµÑÐµÐ¹ÑÐž Ðº ÑÐ»ÐµÐŽÑÑÑÐµÐŒÑ ÑÐ°Ð·ÐŽÐµÐ»Ñ...</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="32" height="17" url="images/User_Icon_17.png"/>
+</th>
+<th width="407">
+<Text id="93">... ÐžÐ»Ðž ÐœÐ°Ð·Ð°ÐŽ  Ðº Ð¿ÑÐµÐŽÑÐŽÑÑÐµÐŒÑ ÑÐ°Ð·ÐŽÐµÐ»Ñ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="49" height="31" url="images/User_Icon_18.png"/>
+</th>
+<th width="407">
+<Text id="94">ÐÑÐºÑÐŸÐžÑÐµ ÑÑÑ ÑÑÑÐ°ÐœÐžÑÑ Ð² ÐœÐŸÐ²ÐŸÐŒ ÐŸÐºÐœÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="61" height="32" url="images/User_Icon_19.png"/>
+</th>
+<th width="407">
+<Text id="95">Ð Ð°Ð·Ð²ÐµÑÐœÑÑÑ ÐŸÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="48" height="32" url="images/User_Icon_20.png"/>
+</th>
+<th width="407">
+<Text id="96">ÐÑÐŸÐ±ÑÐ°Ð·ÐžÑÑ Ð²ÐµÑÑ ÑÐµÐºÑÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<File width="55" height="31" url="images/User_Icon_21.png"/>
+</th>
+<th width="407">
+<Text id="97">ÐÐŸÐŽÑÐ²ÐµÑÐžÑÑ ÑÐµÑÐŒÐžÐœÑ Ð¿ÐŸÐžÑÐºÐ°</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+<Text id="98">ÐÐ»Ñ ÐŸÑÐºÑÑÑÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐµÐ³ÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐžÐ»Ðž ÐœÐ° ÐžÐºÐŸÐœÐºÑ Ð²ÐŸÐ·Ð»Ðµ ÐœÐµÐ³ÐŸ. ÐÐ° ÐžÐºÐŸÐœÐºÐµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° ÐºÐœÐžÐ³Ð°, Ð¿Ð°Ð¿ÐºÐ° ÐžÐ»Ðž ÑÑÑÐ°ÐœÐžÑÐ°: Ð² ÑÐ»ÑÑÐ°Ðµ ÐºÐœÐžÐ³Ðž ÑÐ°ÐŒ Ð±ÑÐŽÐµÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° ÐžÐºÐŸÐœÐºÐ° Ñ ÐºÐœÐžÐ³ÐŸÐ¹; Ð² ÐŽÑÑÐ³ÐžÑ
+ ÑÐ»ÑÑÐ°ÑÑ
+ Ð¿ÑÐž Ð¿ÐŸÐžÑÐºÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ² Ð±ÑÐŽÐµÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° Ð¿Ð°Ð¿ÐºÐ° ÐžÐ»Ðž ÑÑÑÐ°ÐœÐžÑÐ° Ð² Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÑÐŸÐ³ÐŸ, ÐžÐŒÐµÐµÑ Ð»Ðž ÐœÐ°Ð¹ÐŽÐµÐœÐœÐ°Ñ ÑÐµÐºÑÐžÑ Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»Ñ.</Text>
+<Part id="search_terms">
+<Title>
+<Text id="99">Ð¡Ð»ÐŸÐ²Ð° ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ°</Text>
+</Title>
+<Content>
+<Text id="100">Ð¢ÐŸ, ÑÑÐŸ Ð²Ñ Ð²Ð²ÐŸÐŽÐžÑÐµ Ð² ÑÑÑÐŸÐºÐµ Ð·Ð°Ð¿ÑÐŸÑÐ°, ÐœÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ "ÑÐ»ÐŸÐ²Ð°ÐŒÐž ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ°". ÐÐ°Ð¶ÐŽÐŸÐµ ÑÐ»ÐŸÐ²ÐŸ ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð±ÑÐºÐ²Ñ Ðž ÑÐžÑÑÑ. Ð¡Ð»ÐŸÐ²Ð° ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÑ Ð¿ÑÐŸÐ±ÐµÐ»Ð°ÐŒÐž. ÐÑÐ»Ðž ÐžÐŒÐµÐµÑÑÑ ÐºÐ°ÐºÐŸÐ¹-Ð»ÐžÐ±ÐŸ ÐŽÑÑÐ³ÐŸÐ¹ Ð·ÐœÐ°Ðº, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, Ð·ÐœÐ°ÐºÐž Ð¿ÑÐœÐºÑÑÐ°ÑÐžÐž, ÑÐŸ ÐŸÐœÐž ÑÐ»ÑÐ¶Ð°Ñ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÐ°Ð·ÐŽÐµÐ»ÐžÑÐµÐ»ÐµÐ¹ ÑÐ»ÐŸÐ², ÐºÐ°Ðº Ðž Ð¿ÑÐŸÐ±ÐµÐ»Ñ, ÑÐŸ ÐµÑÑÑ ÐžÐ³ÐœÐŸÑÐžÑÑÑÑÑÑ. ÐÑ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÑÐµÑÑÐ²ÐžÑÑ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ ÑÐ»ÐŸÐ²Ð°ÐŒ, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÐŒ Ð·ÐœÐ°ÐºÐž Ð¿ÑÐœÐºÑÑÐ°ÑÐžÐž.</Text>
+<Text id="101">ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÑÐ°ÑÑÐŒÐŸÑÑÐžÐŒ Ð·Ð°Ð¿ÑÐŸÑ</Text>
+<Text type="code" id="102">Ð¡ÐµÐ»ÑÑÐºÐŸ-Ð»ÐµÑÐœÐŸÐµ Ñ
+ÐŸÐ·ÑÐ¹ÑÑÐ²ÐŸ ÐœÐ° ÐŸÑÑÑÐŸÐ²Ð°Ñ
+ Ð¢ÐžÑ
+ÐŸÐ³ÐŸ ÐŸÐºÐµÐ°ÐœÐ°: Ð¡ÐžÑÑÐµÐŒÐ° Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž (1993)</Text>
+<Text id="103">ÐŸÐœ Ð±ÑÐŽÐµÑ ÑÐ°Ð²ÐœÐŸÑÐžÐ»ÐµÐœ ÑÐ»ÐµÐŽÑÑÑÐµÐŒÑ</Text>
+<Text type="code" id="104">Ð¡ÐµÐ»ÑÑÐºÐŸÐµ Ð»ÐµÑÐœÐŸÐµ Ñ
+ÐŸÐ·ÑÐ¹ÑÑÐ²ÐŸ ÐœÐ° ÐŸÑÑÑÐŸÐ²Ð°Ñ
+ Ð¢ÐžÑ
+ÐŸÐ³ÐŸ ÐŸÐºÐµÐ°ÐœÐ° Ð¡ÐžÑÑÐµÐŒÐ° Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž 1993</Text>
+</Content>
+</Part>
+<Part id="query_type">
+<Title>
+<Text id="105">Ð¢ÐžÐ¿Ñ Ð·Ð°Ð¿ÑÐŸÑÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="106">Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐŽÐ²Ð° ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐžÐ¿Ð° Ð·Ð°Ð¿ÑÐŸÑÐ°.</Text>
+<BulletList>
+<Bullet>
+<Text id="107">ÐÐ°Ð¿ÑÐŸÑÑ Ð¿ÐŸ <b>Ð²ÑÐµÐŒ</b> ÑÐ»ÐŸÐ²Ð°ÐŒ. Ð­ÑÐŸ Ð¿ÐŸÐŽÑ
+ÐŸÐŽÐžÑ ÐŽÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ Ð²ÑÐµ ÑÐ»ÐŸÐ²Ð°, ÐºÐŸÑÐŸÑÑÐµ Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ Ð²ÐºÐ»ÑÑÐžÑÑ Ð² ÑÑÑÐŸÐºÑ Ð¿ÐŸÐžÑÐºÐ°.ÐÐŸÐºÑÐŒÐµÐœÑÑ, ÑÐŽÐŸÐ²Ð»ÐµÑÐ²ÐŸÑÑÑÑÐžÐµ Ð·Ð°Ð¿ÑÐŸÑÑ, Ð±ÑÐŽÑÑ Ð²ÑÐ²ÐµÐŽÐµÐœÑ Ð² Ð°Ð»ÑÐ°Ð²ÐžÑÐœÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ.</Text>
+</Bullet>
+<Bullet>
+<Text id="108">ÐÐ°Ð¿ÑÐŸÑÑ Ð¿ÐŸ <b>ÐœÐµÐºÐŸÑÐŸÑÑÐŒ</b> ÑÐ»ÐŸÐ²Ð°ÐŒ. ÐÐŸÑÑÐ°ÑÐŸÑÐœÐŸ ÐœÐ°Ð¿ÐžÑÐ°ÑÑ Ð»ÐžÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ, Ð²ÐµÑÐŸÑÑÐœÐŸ, ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ Ð² ÑÐµÐºÑÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐŸÐºÑÐŒÐµÐœÑÑ Ð±ÑÐŽÑÑ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÑ Ð² Ð¿ÐŸÑÑÐŽÐºÐµ ÑÐŒÐµÐœÑÑÐµÐœÐžÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÑ Ð·Ð°Ð¿ÑÐŸÑÑ. Ð¡ÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐµ Ð·Ð°Ð¿ÑÐŸÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑÑÑ ÑÐ°Ðº:</Text>
+<BulletList>
+<Bullet>
+<Text id="109">ÑÐµÐŒ Ð±ÐŸÐ»ÑÑÐµ ÐžÑÐºÐŸÐŒÑÑ
+ ÑÐµÑÐŒÐžÐœÐŸÐ² ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ, ÑÐµÐŒ Ð±ÐŸÐ»ÑÑÐµ ÐŸÐœ Ð¿ÐŸÐŽÑ
+ÐŸÐŽÐžÑ;</Text>
+</Bullet>
+<Bullet>
+<Text id="110">ÑÐµÐŽÐºÐžÐµ ÑÐ»ÐŸÐ²Ð° Ð±ÐŸÐ»ÐµÐµ Ð²Ð°Ð¶ÐœÑ, ÑÐµÐŒ ÐŸÐ±ÑÐžÐµ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÑ;</Text>
+</Bullet>
+<Bullet>
+<Text id="111">ÐŒÐ°Ð»ÐµÐœÑÐºÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑ Ð»ÑÑÑÐµ, ÑÐµÐŒ Ð±ÐŸÐ»ÑÑÐžÐµ.</Text>
+</Bullet>
+</BulletList>
+</Bullet>
+</BulletList>
+</Content>
+</Part>
+<Text id="112">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÑÑÐŸÐ»ÑÐºÐŸ ÑÐ»ÐŸÐ² ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ°, ÑÐºÐŸÐ»ÑÐºÐŸ Ð²Ð°ÐŒ ÑÐ³ÐŸÐŽÐœÐŸ - ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÑÐµÐ»ÐŸÐµ Ð¿ÑÐµÐŽÐ»ÐŸÐ¶ÐµÐœÐžÐµ, ÐžÐ»Ðž Ð¿Ð°ÑÐ°Ð³ÑÐ°Ñ. ÐÑÐ»Ðž Ð²Ñ Ð²Ð²ÐµÐŽÐµÑÐµ ÑÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐœÐŸ ÑÐ»ÐŸÐ²ÐŸ, ÑÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð±ÑÐŽÑÑ ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÑ Ð¿ÐŸ ÑÐ±ÑÐ²Ð°ÐœÐžÑ ÑÐ°ÑÑÐŸÑÑ ÐµÐ³ÐŸ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="scope_of_queries">
+<Title>
+<Text id="113">ÐÐžÐ°Ð¿Ð°Ð·ÐŸÐœ Ð¿ÐŸÐžÑÐºÐ°</Text>
+</Title>
+<Content>
+<Text id="114">Ð Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÐžÐœÐŽÐµÐºÑÑ ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ°. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐžÐœÐŽÐµÐºÑ Ð¿ÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐžÑÐŒ ÐºÐœÐžÐ³ ÐžÐ»Ðž Ð¿ÐŸ ÑÐ°ÐŒÐžÐ»ÐžÑÐŒ Ð°Ð²ÑÐŸÑÐŸÐ². Ð­ÑÐŸ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ°ÐºÐ¶Ðµ ÐžÐœÐŽÐµÐºÑÑ Ð¿ÐŸ Ð³Ð»Ð°Ð²Ð°ÐŒ ÐžÐ»Ðž Ð¿ÐŸ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ°ÐŒ ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ². ÐÑÐ»Ðž Ð²Ñ ÐœÐµ ÑÐºÐ°Ð¶ÐµÑÐµ ÑÑÐµÐ±ÑÐµÐŒÑÐ¹ ÐžÐœÐŽÐµÐºÑ (Ð¿ÐŸ Ð³Ð»Ð°Ð²Ð°ÐŒ ÐžÐ»Ðž Ð¿ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð°ÐŒ), ÑÐŸ ÐœÐ° ÑÐºÑÐ°Ðœ Ð±ÑÐŽÐµÑ Ð²ÑÐ²ÐµÐŽÐµÐœ Ð²ÐµÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ.</Text>
+<Text id="115">ÐÑÐ»Ðž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐµÐ»Ð°Ñ ÐºÐœÐžÐ³Ð°, ÑÐŸ ÐŸÐœÐ° Ð±ÑÐŽÐµÑ ÐŸÑÐºÑÑÑÐ° Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐŒ ÐŒÐµÑÑÐµ.</Text>
+</Content>
+</Subsection>
+<Subsection id="advanced_search_features">
+<Title>
+<Text id="116">Ð Ð°ÑÑÐžÑÐµÐœÐžÐµ Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž</Text>
+</Title>
+<Content>
+<Text id="117">Ð¥ÐŸÑÑ Ð²ÑÑÐµÐ¿ÐµÑÐµÑÐžÑÐ»ÐµÐœÐœÐŸÐµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÑÐŒ ÐŽÐ»Ñ ÐŸÑÑÑÐµÑÑÐ²Ð»ÐµÐœÐžÑ Ð¿ÐŸÐžÑÐºÐ°, ÑÑÑÐµÑÑÐ²ÑÑÑ Ð±ÐŸÐ»ÐµÐµ ÑÐ°ÑÑÐžÑÐµÐœÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž. ÐÑ
+ ÐŒÐŸÐ¶ÐœÐŸ Ð²ÐºÐ»ÑÑÐžÑÑ Ð² ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐ°Ñ
+ <i>(preferences)</i>, ÐœÐ°Ð¶Ð°Ð² ÐœÐ° ÐÐ°ÑÑÑÐŸÐ¹ÐºÐž Ð²Ð²ÐµÑÑ
+Ñ ÑÑÑÐ°ÐœÐžÑÑ â ÑÐŒÐŸÑÑÐžÑÐµ ÑÐ°Ð·ÐŽÐµÐ» 2.3 ÐœÐžÐ¶Ðµ. ÐÐŸÑÐ»Ðµ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ ÐœÐ°ÑÑÑÐŸÐµÐº, ÐœÐµ ÐœÐ°Ð¶ÐžÐŒÐ°Ð¹ÑÐµ ÐœÐ° ÐºÐœÐŸÐ¿ÐºÑ ÐÐ°Ð·Ð°ÐŽ Ð²Ð°ÑÐµÐ³ÐŸ Ð±ÑÐ°ÑÐ·ÐµÑÐ°, ÑÐ°Ðº ÐºÐ°Ðº ÐŸÐœÐŸ Ð²ÐµÑÐœÐµÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð² ÐžÑÑ
+ÐŸÐŽÐœÐŸÐµ Ð¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐµ. ÐÐŒÐµÑÑÐŸ ÑÑÐŸÐ³ÐŸ ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° Ð»ÑÐ±ÑÑ ÐžÐ· ÐºÐœÐŸÐ¿ÐŸÐº ÐœÐ° Ð¿Ð°ÐœÐµÐ»Ðž Ð¿ÐŸÐžÑÐºÐ°/Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° <i>(search/browse bar)</i></Text>
+<Part id="case_sensitivity_and_stemming">
+<Title>
+<Text id="118">Ð ÐµÐ³ÐžÑÑÑÑ Ðž ÑÑÐµÐŒÐŒÐžÐœÐ³</Text>
+</Title>
+<Content>
+<Text id="119">ÐÐ²Ð° Ð¿ÐµÑÐµÐºÐ»ÑÑÐ°ÑÐµÐ»Ñ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑ ÑÐŸÑÐœÐŸÑÑÑÑ Ð¿ÐŸÐžÑÐºÐ° ÑÐµÐºÑÑÐ°. ÐÐµÑÐµÐºÐ»ÑÑÐ°ÑÐµÐ»Ñ ("Ð ÐµÐ³ÐžÑÑÑÑ") Ð²ÐºÐ»ÑÑÐ°ÐµÑ/ÐŸÑÐŒÐµÐœÑÐµÑ ÑÑÐµÑ ÑÐµÐ³ÐžÑÑÑÐ°.</Text>
+<Text id="120">ÐÐµÑÐµÐºÐ»ÑÑÐ°ÑÐµÐ»Ñ "ÐÐºÐŸÐœÑÐ°ÐœÐžÑ ÑÐ»ÐŸÐ²" Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐžÐ»Ðž ÐžÐ³ÐœÐŸÑÐžÑÐŸÐ²Ð°ÑÑ ÐŸÐºÐŸÐœÑÐ°ÐœÐžÑ Ñ ÑÐ»ÐŸÐ². ÐÐµÑÐµÐºÐ»ÑÑÐ°ÑÐµÐ»Ñ "Ð Ð°Ð·ÐŒÐµÑ ÐŸÐºÐœÐ° Ð¿ÐŸÐžÑÐºÐ°" Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð²Ð²ÐŸÐŽÐžÑÑ ÑÐµÐ»ÑÐ¹ Ð°Ð±Ð·Ð°Ñ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÐµÐºÑÑÐ° Ð·Ð°Ð¿ÑÐŸÑÐ°.</Text>
+<Text id="121">ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐµÑÐ»Ðž Ð²ÑÐ±ÑÐ°ÐœÐŸ ÐžÐ³ÐœÐŸÑÐžÑÐŸÐ²Ð°ÑÑ ÑÐµÐ³ÐžÑÑÑÑ Ðž ÐžÐ³ÐœÐŸÑÐžÑÐŸÐ²Ð°ÑÑ ÐŸÐºÐŸÐœÑÐ°ÐœÐžÑ ÑÐ»ÐŸÐ²,ÑÐŸ Ð·Ð°Ð¿ÑÐŸÑ</Text>
+<Text type="code" id="122">African building</Text>
+<Text id="123">Ð±ÑÐŽÐµÑ ÑÑÐ°ÐºÑÐŸÐ²Ð°ÑÑÑÑ ÐºÐ°Ðº</Text>
+<Text type="code" id="124">africa builds</Text>
+<Text id="125">Ð¿ÐŸÑÐŸÐŒÑ ÑÑÐŸ Ð±ÑÐºÐ²Ð° Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÐµÐ³ÐžÑÑÑÐ° ÐžÐ· ÑÐ»ÐŸÐ²Ð° "African" Ð±ÑÐŽÐµÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐ° ÐœÐ° Ð±ÑÐºÐ²Ñ ÐœÐžÐ¶ÐœÐµÐ³ÐŸ ÑÐµÐ³ÐžÑÑÑÐ°, Ð° ÑÑÑÑÐžÐºÑÑ "Ð¿" Ðž "ing" Ð±ÑÐŽÑÑ ÑÐŽÐ°Ð»ÐµÐœÑ ÐžÐ· ÑÐ»ÐŸÐ² "African" Ðž "building" (ÑÐ°ÐºÐ¶Ðµ, "s" Ð±ÑÐŽÐµÑ ÑÐŽÐ°Ð»ÐµÐœÐ° ÐžÐ· "builds").</Text>
+<Text id="126">Generally case differences and word endings should be ignored unless you are querying for particular names or acronyms.</Text>
+</Content>
+</Part>
+<Part id="phrase_searching">
+<Title>
+<Text id="127">ÐÐŸÐžÑÐº ÑÑÐ°Ð·</Text>
+</Title>
+<Content>
+<Text id="128">ÐÑÐ»Ðž Ð²Ð°Ñ Ð·Ð°Ð¿ÑÐŸÑ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð² ÑÐµÐ±Ñ ÑÑÐ°Ð·Ñ Ð² ÐºÐ°Ð²ÑÑÐºÐ°Ñ
+, ÑÐŸ Ð±ÑÐŽÑÑ Ð²ÑÐ²ÐµÐŽÐµÐœÑ ÑÐŸÐ»ÑÐºÐŸ ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÐžÐŒÐµÑÑ ÑÑÐ°Ð·Ñ, ÐžÐŽÐµÐœÑÐžÑÐœÑÑ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÐœÐœÐŸÐ¹.</Text>
+<Text id="129">ÐÑÐ»Ðž Ð²Ñ Ð¶ÐµÐ»Ð°ÐµÑÐµ ÐœÐ°ÑÑÐžÑÑÑÑ Ð¿ÐŸÐžÑÐºÑ ÑÑÐ°Ð·, ÑÐŸ ÐœÑÐ¶ÐœÐŸ ÑÑÐŸ ÑÐ°Ð·ÐŸÐ±ÑÐ°ÑÑ. Ð€ÑÐ°Ð·Ñ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÑÑÑÑ Ð² post-retrieval scan (ÐŽÐ²ÑÑ
+-ÑÐ°Ð·ÐŸÐ²ÐŸÐµ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ). Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð·Ð°Ð¿ÑÐŸÑ ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑÑÑ ÐŸÐ±ÑÑÐœÑÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, ÐºÐ°Ð¶ÐŽÐŸÐµ ÐžÐ· ÑÐ»ÐŸÐ² ÑÑÐ°Ð·Ñ ÐžÐœÑÐµÑÐ¿ÑÐµÑÐžÑÑÐµÑÑÑ ÐºÐ°Ðº Ð¿ÐŸÐžÑÐºÐŸÐ²ÐŸÐµ ÑÐ»ÐŸÐ²ÐŸ; Ð·Ð°ÑÐµÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ñ ÑÑÐžÐŒÐž ÑÐ»ÐŸÐ²Ð°ÐŒÐž ÑÐœÐŸÐ²Ð° Ð¿ÑÐŸÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑÑÑ ÐŽÐ»Ñ ÐŸÑÐ±ÑÐ°ÑÑÐ²Ð°ÐœÐžÑ ÑÐµÑ
+, Ð² ÐºÐŸÑÐŸÑÑÑ
+ ÐœÐµÑ ÑÑÐŸÐ¹ ÑÑÐ°Ð·Ñ.</Text>
+<Text id="130">Ð Ð¿ÑÐŸÑÐµÑÑÐµ ÐŽÐ²ÑÑ
+-ÑÐ°Ð·ÐŸÐ²ÐŸÐ³ÐŸÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÑÐ°Ð·Ñ Ð¿ÑÐŸÐ²ÐµÑÑÑÑÑÑ ÑÐŸÑÐœÐŸ ÑÐ°Ðº Ð¶Ðµ, ÐºÐ°Ðº ÐŸÐœÐž Ð²Ð²ÐµÐŽÐµÐœÑ, Ð²ÐºÐ»ÑÑÐ°Ñ Ð·ÐœÐ°ÐºÐž Ð¿ÑÐœÐºÑÑÐ°ÑÐžÐž. Ð Ð¿ÑÐžÐŒÐµÑÑ,</Text>
+<Text type="code" id="131">Ð·Ð°Ð¿ÑÐŸÑ Ð§ÑÐŸ ÑÐ°ÐºÐŸÐµ "ÐŽÐ²ÑÑ
+-ÑÐ°Ð·ÐŸÐ²ÐŸÐµ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ?"</Text>
+<Text id="132">ÐÐ° Ð¿ÐµÑÐ²ÐŸÐ¹ ÑÑÐ°ÐŽÐžÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑÑ Ð²ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÐµ ÑÐ»ÐŸÐ²Ð°</Text>
+<Text id="779">ÑÑÐŸ ÑÐ°ÐºÐŸÐ¹ ÐŽÐ²Ð° ÑÐ°Ð·Ð° ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+<Text id="133">Ð·Ð°ÑÐµÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ñ ÑÑÐžÐŒÐž ÑÐ»ÐŸÐ²Ð°ÐŒÐž Ð±ÑÐŽÑÑ Ð¿ÑÐŸÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÑ Ð Ð°ÑÑÐžÑÐµÐœÑÐ¹ Ð²ÐžÐŽ Ð·Ð°Ð¿ÑÐŸÑÐ° ÐœÐ° ÐœÐ°Ð»ÐžÑÐžÐµ ÑÑÐ°Ð·Ñ</Text>
+<Text type="code" id="134">ÐŽÐ²ÑÑ
+-ÑÐ°Ð·ÐŸÐ²ÐŸÐµ ÑÐºÐ°ÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ?</Text>
+<Text id="135">ÐÐ°Ð¹ÐŽÐµÐœÐœÑÐµ ÑÑÐ°Ð·Ñ ÐœÐµ Ð±ÑÐŽÑÑ ÑÑÐ²ÑÑÐ²ÐžÑÐµÐ»ÑÐœÑ Ðº ÑÐµÐ³ÐžÑÑÑÐ°ÐŒ, ÐµÑÐ»Ðž ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÐŸÐ¿ÑÐžÑ ÐžÐ³ÐœÐŸÑÐžÑÐŸÐ²Ð°ÑÑ ÑÐµÐ³ÐžÑÑÑÑ.</Text>
+</Content>
+</Part>
+<Part id="advanced_query_mode">
+<Title>
+<Text id="136">Ð Ð°ÑÑÐžÑÐµÐœÐœÐ°Ñ ÑÐŸÑÐŒÐ° Ð·Ð°Ð¿ÑÐŸÑÐ°</Text>
+</Title>
+<Content>
+<Text id="137">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐºÐ»ÑÑÐžÑÑÑÑ Ð² ÑÐ°ÑÑÐžÑÐµÐœÐœÑÑ ÑÐŸÑÐŒÑ Ð·Ð°Ð¿ÑÐŸÑÐ°, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÑÐŸÑÐµÑÐ°ÑÑ ÑÐ»ÐŸÐ²Ð°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð (&amp;), ÐÐÐ (|), Ð ÐÐ (!). Ð­ÑÐŸ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ Ð±ÐŸÐ»ÐµÐµ ÑÐŸÑÐœÑÐµ Ð·Ð°Ð¿ÑÐŸÑÑ. Ð¢Ð°ÐºÐ¶Ðµ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐºÐ»ÑÑÐžÑÑ Ð¿ÐŸÐºÐ°Ð· ÐžÑÑÐŸÑÐžÐž Ð·Ð°Ð¿ÑÐŸÑÐ°, ÐºÐŸÐ³ÐŽÐ° Ð±ÑÐŽÑÑ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ Ð¿ÑÐµÐŽÑÐŽÑÑÐžÐµ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÑ Ð¿ÐŸÐžÑÐºÐ°. Ð­ÑÐŸ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÑÐ»ÐµÐ³ÐºÐ° ÐžÐ·ÐŒÐµÐœÐµÐœÐœÑÐµ ÑÐŸÑÐŒÑ Ð·Ð°Ð¿ÑÐŸÑÐŸÐ². ÐÐ°ÐºÐŸÐœÐµÑ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐµÐ³ÑÐ»ÐžÑÐŸÐ²Ð°ÑÑ ÐŸÐ±ÑÐµÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² - ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² Ð¿ÐŸÐžÑÐºÐ°, Ð° ÑÐ°ÐºÐ¶Ðµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐœÐ° ÐŸÐŽÐœÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ.</Text>
+<Text id="138">If the words AND, OR, and NOT appear in your query they are treated as ordinary search terms, not operators. For operators you must use &amp;, |, and !. In addition, parentheses can be used for grouping.</Text>
+</Content>
+</Part>
+<Part id="using_search_history">
+<Title>
+<Text id="139">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ Ñ
+ÑÐŸÐœÐŸÐ»ÐŸÐ³ÐžÐž Ð¿ÐŸÐžÑÐºÐ°</Text>
+</Title>
+<Content>
+<Text id="140">ÐÐŸÐ³ÐŽÐ° Ð²Ñ Ð²ÐºÐ»ÑÑÐ°ÐµÑÐµ "Ñ
+ÑÐŸÐœÐŸÐ»ÐŸÐ³ÐžÐž Ð¿ÐŸÐžÑÐºÐ°" ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ Ð²ÑÐ±ÐŸÑÐ° Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÐ¹ (Preferences page), ÑÐŸ Ð²Ð°ÐŒ Ð±ÑÐŽÑÑ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ Ð²Ð°ÑÐž Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐµ Ð²Ð°ÑÐžÐ°ÐœÑÑ Ð¿ÐŸÐžÑÐºÐ°, ÐœÐ°ÑÑÐŽÑ Ñ ÐºÑÐ°ÑÐºÐžÐŒÐž ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐ°ÐŒÐž, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÑ. ÐÐ°Ð¶ÐŒÐžÑÐµ ÐºÐœÐŸÐ¿ÐºÑ ÐŸÐºÐŸÐ»ÐŸ ÐŸÐŽÐœÐŸÐ³ÐŸ ÐžÐ· Ð¿ÑÐµÐŽÑÐŽÑÑÐžÑ
+ Ð²Ð°ÑÐžÐ°ÐœÑÐŸÐ² Ð¿ÐŸÐžÑÐºÐ°, ÑÑÐŸÐ±Ñ ÑÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÑÑ ÑÐµÐºÑÑ Ð² Ð¿ÐŸÐ»Ðµ Ð¿ÐŸÐžÑÐºÐ°. Ð­ÑÐŸ ÐŸÐ±Ð»ÐµÐ³ÑÐžÑ Ð¿ÑÐŸÑÐµÑÑ, ÐµÑÐ»Ðž Ð²Ñ Ð¿ÐŸÐ»ÑÐ·ÑÐµÑÐµÑÑ ÑÐ»ÐµÐ³ÐºÐ° ÐžÐ·ÐŒÐµÐœÐµÐœÐœÐŸÐ¹ Ð²ÐµÑÑÐžÐµÐ¹ Ð¿ÑÐµÐŽÑÐŽÑÑÐžÑ
+ Ð·Ð°Ð¿ÑÐŸÑÐŸÐ².</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="changing_the_preferences">
+<Title>
+<Text id="141">ÐÐ·ÐŒÐµÐœÐµÐœÐžÐµ ÐœÐ°ÑÑÑÐŸÐµÐº</Text>
+</Title>
+<Content>
+<Figure id="the_preferences_page">
+<Title>
+<Text id="142">Ð¡ÑÑÐ°ÐœÐžÑÐ° ÐœÐ°ÑÑÑÐŸÐµÐº</Text>
+</Title>
+<File width="394" height="439" url="images/User_Fig_3.png"/>
+</Figure>
+<Text id="143">ÐÐ° ÑÑÑÐ°ÐœÐžÑÐµ <i>ÐÐ°ÑÑÑÐŸÐ¹ÐºÐž</i> (ÐºÐœÐŸÐ¿ÐºÐ° Ð² Ð²ÐµÑÑ
+ÐœÐµÐ¹ ÑÐ°ÑÑÐž ÑÑÑÐ°ÐœÐžÑÑ) Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐœÐµÐºÐŸÑÐŸÑÑÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°. ÐÑÐµ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž Ð·Ð°Ð²ÐžÑÑÑ ÐŸÑ ÑÐžÐ¿Ð° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž; Ð¿ÑÐžÐŒÐµÑ Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ ÐœÐ° ÑÐžÑÑÐœÐºÐµ 3. ÐÐŸÑÐ»Ðµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐœÐ°ÑÑÑÐŸÐµÐº ÐœÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐºÐœÐŸÐ¿ÐºÑ "ÐÐ°Ð·Ð°ÐŽ" ÐœÐ° Ð±ÑÐ°ÑÐ·ÐµÑÐµ, ÑÐ°Ðº ÐºÐ°Ðº Ð²ÑÐµ ÐœÐ°ÑÑÐŸÐ¹ÐºÐž Ð²ÐµÑÐœÑÑÑÑ Ð² ÐžÑÑ
+ÐŸÐŽÐœÐŸÐµ Ð¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐµ. ÐÐŒÐµÑÑÐŸ ÑÑÐŸÐ³ÐŸ ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐŸÐŽÐœÑ ÐžÐ· ÐºÐœÐŸÐ¿ÐŸÐº ÐœÐ° Ð¿Ð°ÐœÐµÐ»Ðž Ð²Ð²ÐµÑÑ
+Ñ ÑÐºÑÐ°ÐœÐ°.</Text>
+<Subsection id="collection_preferences">
+<Title>
+<Text id="144">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</Title>
+<Content>
+<Text id="145">ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐŸÐŽÐµÑÐ¶Ð°Ñ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, Ð¿ÐŸÐžÑÐº Ð¿ÐŸ ÐºÐŸÑÐŸÑÑÐŒ ÐŒÐŸÐ¶ÐµÑ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑÑÑ ÐºÐ°Ðº Ð¿ÐŸ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐžÐ· ÐœÐžÑ
+, ÑÐ°Ðº Ðž Ð¿ÐŸ Ð²ÑÐµÐŒ Ð²ÐŒÐµÑÑÐµ. ÐÐ° ÑÑÑÐ°ÐœÐžÑÐµ ÐÐ°ÑÑÑÐŸÐ¹ÐºÐž ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ ÑÐµ Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ Ð²ÐºÐ»ÑÑÐžÑÑ Ð² Ð¿ÐŸÐžÑÐº. </Text>
+</Content>
+</Subsection>
+<Subsection id="language_preferences">
+<Title>
+<Text id="146">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐž ÑÐ·ÑÐºÐ°</Text>
+</Title>
+<Content>
+<Text id="147">ÐÐ°Ð¶ÐŽÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐŒÐµÐµÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐ¹ ÑÐ·ÑÐº ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°, ÐœÐŸ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ Ð»ÑÐ±ÐŸÐ¹ ÐŽÑÑÐ³ÐŸÐ¹. Ð¢Ð°ÐºÐ¶Ðµ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ ÐŽÑÑÐ³ÑÑ ÐºÐŸÐŽÐžÑÐŸÐ²ÐºÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ Ð² ÐŽÐ°ÐœÐœÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ, Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÑÑ ÐŽÐ»Ñ Ð²Ð°ÑÐµÐ³ÐŸ Ð±ÑÐ°ÑÐ·ÐµÑÐ° - Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÑÑÐ°Ð²ÐžÑÑÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ, ÐœÐŸ ÐœÐ° ÐœÐµÐºÐŸÑÑÑÑ
+ Ð±ÑÐ°ÑÐ·ÐµÑÐ°Ñ
+ Ð»ÑÑÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ ÐºÐŸÐŽÐžÑÐŸÐ²ÐºÑ Ð²ÑÑÑÐœÑÑ. ÐÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ ÑÐ°ÐºÐ¶Ðµ Ð¿ÐµÑÐµÐ¹ÑÐž ÐŸÑ Ð³ÑÐ°ÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÑÐµÐ¶ÐžÐŒÐ° Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ðº ÑÐµÐºÑÑÐŸÐ²ÐŸÐŒÑ, Ðž ÐœÐ°ÐŸÐ±ÐŸÑÐŸÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="presentation_preferences">
+<Title>
+<Text id="148">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐž ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°</Text>
+</Title>
+<Content>
+<Text id="149">Ð Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð² ÐœÐµÐ¹ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐœÐ°ÑÑÑÐŸÐµÐº ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°. ÐÐŸÐ»Ð»ÐµÐºÑÐžÑ Web-ÑÑÑÐ°ÐœÐžÑ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð¿Ð°ÐœÐµÐ»Ñ ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ Ð²Ð²ÐµÑÑ
+Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, Ð¿ÐŸÑÐ»Ðµ Ð¿ÐŸÐžÑÐºÐ° Ð²Ñ ÑÑÐ°Ð·Ñ Ð¿ÐŸÐ¿Ð°ÐŽÐµÑÐµ ÐœÐ° Web-ÑÑÑÐ°ÐœÐžÑÑ Ð±ÐµÐ· Ð²ÑÑÐºÐŸÐ³ÐŸ Greenstone Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ°. Ð§ÑÐŸÐ±Ñ ÑÐŽÐµÐ»Ð°ÑÑ ÐœÐŸÐ²ÑÐ¹ Ð·Ð°Ð¿ÑÐŸÑ, ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ ÐœÐ°Ð¶Ð°ÑÑ ÐºÐœÐŸÐ¿ÐºÑ "ÐœÐ°Ð·Ð°ÐŽ" Ð² Ð²Ð°ÑÐµÐŒ Ð±ÑÐ°ÑÐ·ÐµÑÐµ. Ð¢Ð°ÐºÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐ°ÐºÐ¶Ðµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ Ð·Ð°Ð¿ÑÐµÑÐ°ÑÑ ÑÐžÑÑÐµÐŒÐœÑÐµ ÐŸÑÐžÐ±ÐºÐž, ÐºÐŸÐ³ÐŽÐ° Ð²Ñ ÐœÐ°Ð¶ÐžÐŒÐ°ÐµÑÐµ ÐœÐ° ÑÑÑÐ»ÐºÐž, Ð²ÑÐ²ÐŸÐŽÑÑÐžÐµ Ð²Ð°Ñ Ð·Ð° ÑÐ°ÐŒÐºÐž ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Ð² WWW</Text>
+</Content>
+</Subsection>
+<Subsection id="search_preferences">
+<Title>
+<Text id="150">ÐÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÑ Ð¿ÐŸÐžÑÐºÐ°</Text>
+</Title>
+<Content>
+<Text id="151">ÐÐ° ÑÐžÑÑÐœÐºÐµ 3 Search preferences (Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÑ Ð¿ÐŸÐžÑÐºÐ°), Ð¿ÐµÑÐ²Ð°Ñ Ð¿Ð°ÑÐ° ÐºÐœÐŸÐ¿ÐŸÐº Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð²Ð°ÐŒ Ð¿ÐŸÐ»ÑÑÐ°ÑÑ Ð±ÐŸÐ»ÑÑÐŸÐµ Ð¿ÐŸÐ»Ðµ Ð·Ð°Ð¿ÑÐŸÑÐ°, ÑÐ°Ðº ÑÑÐŸÐ±Ñ Ð²Ñ ÐŒÐŸÐ³Ð»Ðž Ð»ÐµÐ³ÐºÐŸ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ Ð¿Ð°ÑÐ°Ð³ÑÐ°ÑÐ°ÐŒ. Ð Greenstone ÑÐŽÐžÐ²ÐžÑÐµÐ»ÑÐœÐŸ Ð±ÑÑÑÑÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÐœÐ°Ð¹ÑÐž Ð±ÐŸÐ»ÑÑÐžÐµ Ð¿ÐŸÑÑÐžÐž ÑÐµÐºÑÑÐ°. Ð¡Ð»ÐµÐŽÑÑÑÐžÐµ ÐŽÐ²Ðµ Ð¿Ð°ÑÑ ÐºÐœÐŸÐ¿ÐŸÐº ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑ Ð²ÐžÐŽÐŸÐŒ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÑ ÑÐµÐºÑÑÐ° Ð¿ÑÐž Ð¿ÐŸÐžÑÐºÐµ. ÐÐµÑÐ²ÑÐ¹ ÐœÐ°Ð±ÐŸÑ (Ð¿ÐŸÐŒÐµÑÐµÐœÐœÑÐ¹ ÐºÐ°Ðº "<i>ÑÐ°Ð·Ð»ÐžÑÐœÑÐ¹ ÑÐµÐ³ÐžÑÑÑ</i>") ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑ ÑÐµÐŒ, ÐŽÐŸÐ»Ð¶ÐµÐœ Ð»Ðž ÑÑÐžÑÑÐ²Ð°ÑÑÑÑ Ð²ÐµÑÑ
+ÐœÐžÐ¹ Ðž ÐœÐžÐ¶ÐœÐžÐ¹ ÑÐµÐ³ÐžÑÑÑ. ÐÑÐŸÑÐŸÐ¹ ("<i>ÐŸÐºÐŸÐœÑÐ°ÐœÐžÑ ÑÐ»ÐŸÐ²</i>") ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ, ÐžÐ³ÐœÐŸÑÐžÑÐŸÐ²Ð°ÑÑ Ð»Ðž ÐŸÐºÐŸÐœÑÐ°ÐœÐžÑ ÑÐ»ÐŸÐ²Ð° ÐžÐ»Ðž ÐœÐµÑ. </Text>
+<Text id="152">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÑÐ»ÐµÐŽÑÑÑÐµÐ¹ Ð¿Ð°ÑÑ ÐºÐœÐŸÐ¿ÐŸÐº ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÐµÑÐµÐºÐ»ÑÑÐžÑÑÑÑ Ð² "ÑÐ°ÑÑÐžÑÐµÐœÐœÑÐ¹" ÑÐ¿ÑÐ°Ð²ÐŸÑÐœÑÐ¹ ÑÐµÐ¶ÐžÐŒ, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐ¹ Ð²ÑÑÐµ, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð²Ð°ÐŒ ÑÐŸÑÑÐ°Ð²Ð»ÑÑÑ Ð±ÐŸÐ»ÐµÐµ ÑÐŸÑÐœÑÐµ Ð·Ð°Ð¿ÑÐŸÑÑ, ÐºÐŸÐŒÐ±ÐžÐœÐžÑÑÑ ÑÐµÑÐŒÐžÐœÑ,ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ <i>AND</i> (&amp;), <i>OR</i>, Ðž <i>NOT</i>. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐºÐ»ÑÑÐ°ÑÑ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž Ñ
+ÑÐŸÐœÐŸÐ»ÐŸÐ³ÐžÐž Ð¿ÐŸÐžÑÐºÐ°, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐµ Ð²ÑÑÐµ, ÐœÐ°Ð¶ÐžÐŒÐ°Ñ Ð²ÐºÐ». Ðž Ð²ÑÐºÐ». ÐÐ°ÐºÐŸÐœÐµÑ, ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸÐŒ ÐœÐ°Ð¶Ð°ÑÐžÐ¹ ÐŽÐ»Ñ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐµÐœÐžÑ, Ðž ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸÐŒ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÑÑ
+ ÐœÐ° ÐºÐ°Ð¶ÐŽÐŸÐŒ ÑÐºÑÐ°ÐœÐµ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÐŸÐ² Ð²ÐŸ Ð²ÑÐµÐŒÑ Ð¿ÐŸÑÐ»ÐµÐŽÐœÐµÐ³ÐŸ Ð²Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ (ÑÐŒ. ÑÐžÑÑÐœÐŸÐº 3).</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="making_greenstone_collections">
+<Title>
+<Text id="153">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Greenstone</Text>
+</Title>
+<Content>
+<Text id="154">Ð¡Ð°ÐŒÑÐ¹ Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Greenstone (GLI). ÐÐœ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐÐ°ÐŒ ÑÐŸÐ±ÐžÑÐ°ÑÑ Ð¿ÐŸÐŽÐ±ÐŸÑÐºÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐžÐ»Ðž Ð·Ð°ÐŽÐ°Ð²Ð°ÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ðž Ð²ÑÑÑÐ°ÐžÐ²Ð°ÑÑ ÐžÑ
+ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Greenstone. ÐÐœ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÑ Ð¿ÑÑÑ ÐŸÑÐœÐŸÐ²ÐœÑÑ
+ ÐŽÐµÐ¹ÑÑÐ²ÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³ÑÑ ÐŒÐµÐœÑÑÑ Ð¿ÐŸÑÑÐŽÐŸÐº, ÐœÐŸ ÐœÐŸÐŒÐžÐœÐ°Ð»ÑÐœÐŸ Ð¿ÑÐµÐŽÐ¿ÑÐžÐœÐžÐŒÐ°ÑÑÑÑ Ð² ÐžÐ·Ð»Ð°Ð³Ð°ÐµÐŒÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="155">ÐÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐžÐ· ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ð° ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°, Ð²ÐºÐ»ÑÑÐ°Ñ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð² ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÑÐ±ÑÐµ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŸÑÑÐ°ÑÑÑÑ Â«Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐœÑÐŒÐžÂ» Ðº ÑÑÐžÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ. ÐÐŸÐºÑÐŒÐµÐœÑÑ ÐŒÐŸÐ³ÑÑ ÑÐ°ÐºÐ¶Ðµ Ð±ÑÑÑ ÑÐŸÐ±ÑÐ°ÐœÑ ÐžÐ· ÐÐœÑÐµÑÐœÐµÑÐ° Ñ Ð¿ÐŸÐŒÐŸÑÑÑ Ð²ÑÑÑÐŸÐµÐœÐœÑÑ
+ Ð·ÐµÑÐºÐ°Ð»ÑÐœÑÑ
+ ÑÑÐµÐŽÑÑÐ².</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="156">ÐÐ°ÑÑÑÐµÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐµÐŒ ÐœÐŸÐ²ÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðº ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÑÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ ÐžÐ»Ðž Ð³ÑÑÐ¿Ð¿Ð°ÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². </Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="157">ÐÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑ, ÐºÐ°Ðº ÐŸÐœÐ° ÐŽÐŸÐ»Ð¶ÐœÐ° Ð²ÑÐ³Ð»ÑÐŽÐµÑÑ, Ðž ÑÑÐµÐŽÑÑÐ²Ð° ÐŽÐŸÑÑÑÐ¿Ð°, ÐºÐŸÑÐŸÑÑÐµ ÐŸÐœÐ° ÐŽÐŸÐ»Ð¶ÐœÑ ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÑÑ. </Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="158">ÐÐŸÑÑÑÐŸÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ Greenstone.</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="159">ÐÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÑÐ¹ Ð¿ÑÐŸÑÐŒÐŸÑÑ Ð²ÐœÐŸÐ²Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÐ°Ñ Ð±ÑÐŽÐµÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÐœÐ° ÐÐ°ÑÐµÐ¹ ÑÑÐ°ÑÑÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ Greenstone Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŸÐŽÐœÐŸÐ¹ ÐžÐ· ÑÑÐŽÐŸÐ²ÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹.</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="160">ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐÐ°ÐŒ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ ÑÐŸ, ÑÑÐŸ ÐŸÐ±ÑÑÐœÐŸ ÐœÐ°Ð·ÑÐ²Ð°ÑÑ Â«Ð²ÐœÐµÑÐœÐžÐŒÐžÂ» ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž, ÑÐŸ ÐµÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐžÐœÐ°ÐŽÐ»ÐµÐ¶Ð°Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÑÐµÐ»ÐŸÐŒ. ÐÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐ°ÑÑÐŸ ÐŽÐŸÐ»Ð¶ÐœÑ Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»ÑÑÑÑÑ Ð¿ÐŸ ÑÐ°Ð·ÐŽÐµÐ»Ð°ÐŒ Ðž Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»Ð°ÐŒ, Ðž Â«Ð²ÐœÑÑÑÐµÐœÐœÐžÐµÂ» ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ²ÑÐ·Ð°ÐœÑ Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐµÑ ÑÐ°ÑÑÑÑ. Ð Greenstone  ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐœÐ°ÐŽÐµÐ»ÐµÐœÑ ÑÑÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹, Ðž ÐŒÑ ÐŸÐ±ÑÑÑÐœÑÐµÐŒ ÑÑÐŸ Ð² ÑÐ°Ð·ÐŽÐµÐ»Ðµ 3.3.</Text>
+<Text id="161">ÐÐ°ÐºÐŸÐœÐµÑ, Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²ÐœÑÐ¹ ÑÐ¿ÐŸÑÐŸÐ± Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑÑÑ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐŸÐŒ, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐŒÐŸÐ³Ð°ÐµÑ ÐÐ°ÐŒ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐœÐŸÐ²ÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐžÐ·ÐŒÐµÐœÑÑ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ, ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑ Ðº ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐŒ ÐžÐ»Ðž ÑÐŽÐ°Ð»ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐœ Ð±ÑÐ» ÑÐŸÐ·ÐŽÐ°Ðœ ÐŽÐŸ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°, Ðž ÐŽÐ»Ñ Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²Ð° Ð¿ÑÐ°ÐºÑÐžÑÐµÑÐºÐžÑ
+ ÑÐµÐ»ÐµÐ¹ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ ÐŽÐŸÐ»Ð¶ÐµÐœ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ Ð²ÐŒÐµÑÑÐŸ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ°. Ð­ÑÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐŸ Ð² ÑÐ°Ð·ÐŽÐµÐ»Ðµ 3.4.</Text>
+<Text id="162">Ð§ÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Greenstone ÐœÐ° Ð¿ÐŸÐ»ÐœÑÑ ÐŒÐŸÑÐœÐŸÑÑÑ ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ Ð¿ÑÐŸÐŽÐ²ÐžÐœÑÑÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐÑ Ð±ÑÐŽÐµÑÐµ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐŸÑÐµÑÑÑ Ð³Ð»Ð°Ð²Ñ 2 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ°.</Text>
+<Section id="the_librarian_interface">
+<Title>
+<Text id="163">ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ</Text>
+</Title>
+<Content>
+<Text id="164">Ð§ÑÐŸÐ±Ñ ÑÐ°Ð·ÑÑÑÐœÐžÑÑ, ÐºÐ°Ðº ÐŽÐµÐ¹ÑÑÐ²ÑÐµÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Greenstone, ÐŒÑ Ð¿ÐŸÐºÐ°Ð¶ÐµÐŒ ÑÑÐŸ ÐœÐ°  Ð¿ÑÐŸÑÑÐŸÐŒ Ð¿ÑÐžÐŒÐµÑÐµ. Ð ÐžÑÑÐœÐºÐž 4-15 â ÑÑÐŸ ÑÐœÐžÐŒÐºÐž ÑÐºÑÐ°ÐœÐ° ÐœÐ° ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÑÐ°ÐŽÐžÑÑ
+ Ð² ÑÐµÑÐµÐœÐžÐµ Ð²Ð·Ð°ÐžÐŒÐŸÐŽÐµÐ¹ÑÑÐ²ÐžÑ. Ð ÑÑÐŸÐŒ Ð¿ÑÐžÐŒÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐžÐ· ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÐŸÐŽÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ð° ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÑÐ°Ð·Ð²ÐžÑÐžÑ (DLS), ÐºÐŸÑÐŸÑÐ°Ñ ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÐµÑÑÑ Ð²ÐŒÐµÑÑÐµ Ñ Greenstone. ÐÐ»Ñ ÐŸÐ¿ÐžÑÐ°ÑÐµÐ»ÑÐœÑÑ
+ ÑÐµÐ»ÐµÐ¹ ÑÐºÑÐºÑÑÑ Ð¿ÑÐžÐŒÐµÑ Ð²ÐžÐŽ Ð¿ÑÐŸÑ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ ÐŸÑÐŽÐµÐ»ÑÐœÑÑ
+ ÑÑÐ°Ð¿ÐŸÐ², ÑÐ¿ÐŸÐŒÐžÐœÐ°Ð²ÑÐžÑ
+ÑÑ Ð²ÑÑÐµ. ÐÐŸÐ»ÐµÐµ ÑÐµÐ°Ð»ÑÐœÑÐ¹ ÐŸÐ±ÑÐ°Ð·ÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ Ð¿ÐµÑÐµÐºÐ»ÑÑÐ°ÑÑ Ð¿ÑÐŸÑ
+ÐŸÐ¶ÐŽÐµÐœÐžÐµ ÐœÐ°Ð·Ð°ÐŽ Ðž Ð²Ð¿ÐµÑÐµÐŽ ÑÐµÑÐµÐ· ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÑÑÐ°ÐŽÐžÐž Ð¿ÐŸ ÐŒÐµÑÐµ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ Ð·Ð°ÐŽÐ°ÑÐž.</Text>
+<Text id="165">ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð·Ð°Ð¿ÑÑÐµÐœ Ð² ÐŸÐŽÐœÐŸÐŒ ÐžÐ· 4 ÑÐµÐ¶ÐžÐŒÐ°Ñ
+: ÐÐŸÐŒÐŸÑÐœÐžÐº ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ, ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ, Ð¡ÐžÑÑÐµÐŒÐœÑÐ¹ ÑÐ¿ÐµÑÐžÐ°Ð»ÐžÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž, Ðž Ð­ÐºÑÐ¿ÐµÑÑ. Ð ÐµÐ¶ÐžÐŒÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÑÑÐŸÐ²ÐµÐœÑ ÐŽÐµÑÐ°Ð»ÐžÐ·Ð°ÑÐžÐž ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°, Ðž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÑÐµÑÐµÐ· ÑÐ°Ð·ÐŽÐµÐ» 'ÐÐ°ÑÑÑÐŸÐ¹ÐºÐž' ÐŒÐµÐœÑ 'Ð€Ð°Ð¹Ð»'. Ð Ð°ÑÑÐºÐ°Ð· ÐŸÐ± ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ Ð¿ÐŸÐŽÑÐ°Ð·ÑÐŒÐµÐ²Ð°ÐµÑ, ÑÑÐŸ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ Ð² ÑÐµÐ¶ÐžÐŒ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, 'ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ'.</Text>
+<Subsection id="getting_started">
+<Title>
+<Text id="166">ÐÐ°ÑÐ°Ð»ÑÐœÑÐ¹ ÑÑÐ°Ð¿</Text>
+</Title>
+<Content>
+<Text id="167">ÐÐ°Ð¿ÑÑÑÐžÑÐµ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐŽ Windows, Ð²ÑÐ±ÐžÑÐ°Ñ ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone  ÐžÐ· ÑÐ°Ð·ÐŽÐµÐ»Ð° ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŒÐµÐœÑ Ð¡ÑÐ°ÑÑ Ðž Ð² ÐœÐµÐŒ - ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ.      ÐÑÐ»Ðž ÐÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ Unix, Ð²ÐŒÐµÑÑÐŸ ÑÑÐŸÐ³ÐŸ ÐœÐ°Ð±ÐµÑÐžÑÐµ</Text>
+<CodeLine>cd ~/gsdl</CodeLine>
+<CodeLine>cd gli</CodeLine>
+<CodeLine>./gli.sh</CodeLine>
+<Text id="168">Ð³ÐŽÐµ ~/gsdl  - ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐ°Ñ ÑÐžÑÑÐµÐŒÑ  Greenstone. Ð§ÑÐŸÐ±Ñ ÐœÐ°ÑÐ°ÑÑ ÑÐ°Ð±ÐŸÑÑ, ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÐŸÑÐºÑÑÑÑ ÑÑÑÐµÑÑÐ²ÑÑÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐ»Ðž ÐœÐ°ÑÐ°ÑÑ ÐœÐŸÐ²ÑÑ. Ð ÐžÑÑÐœÐŸÐº 4 Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð¿ÑÐŸÑÐµÑÑ ÐœÐ°ÑÐ°Ð»Ð° ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐœ Ð²ÑÐ±ÑÐ°Ð» ÐÐŸÐ²Ð°Ñ ÐžÐ· ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸ ÐŒÐµÐœÑ Ðž ÐœÐ°ÑÐ°Ð» Ð·Ð°Ð¿ÐŸÐ»ÐœÑÑÑ ÐŸÐ±ÑÐžÐµ ÑÐ²ÐµÐŽÐµÐœÐžÑ ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž â ÐµÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, Ð°ÐŽÑÐµÑ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ Ð»ÐžÑÐ°, ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸÐ³ÐŸ Ð·Ð° ÐœÐµÑ, Ðž ÐºÑÐ°ÑÐºÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ â Ð² Ð²ÑÐ¿Ð»ÑÐ²Ð°ÑÑÐµÐŒ ÐŸÐºÐœÐµ. ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž â ÑÑÐŸ ÐºÐŸÑÐŸÑÐºÐ°Ñ ÑÑÐ°Ð·Ð°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ Ð²ÑÑÐŽÑ Ð² ÐŠÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐµ, ÑÑÐŸÐ±Ñ ÐžÐŽÐµÐœÑÐžÑÐžÑÐžÑÐŸÐ²Ð°ÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¡ÑÑÐµÑÑÐ²ÑÑÑÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐŒÐµÑÑ ÐžÐŒÐµÐœÐ° ÑÐžÐ¿Ð° ÐÑÐŸÐŽÐŸÐ²ÐŸÐ»ÑÑÑÐ²ÐžÐµ Ðž ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Ð¿ÐžÑÐ°ÐœÐžÑ, ÐÑÐµÐŒÐžÑÐœÐ°Ñ ÑÐºÐŸÐ»ÐŸÐ³ÐžÑÐµÑÐºÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Ðž Ñ.ÐŽ. ÐÐŸÐ³ÐŽÐ° ÐÑ Ð²Ð¿ÐµÑÐ°ÑÐ°Ð»Ðž ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÑÐžÑÑÐµÐŒÐ° ÐœÐ°Ð·ÐœÐ°ÑÐ°ÐµÑ ÑÐœÐžÐºÐ°Ð»ÑÐœÑÐ¹ ÐŒÐœÐµÐŒÐŸÐœÐžÑÐµÑÐºÐžÐ¹ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑ Â«ÐžÐŒÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐžÂ» ÐŽÐ»Ñ Ð²ÐœÑÑÑÐµÐœÐœÐµÐ³ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ (ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐµÐ³ÐŸ, ÐµÑÐ»Ðž Ð·Ð°Ñ
+ÐŸÑÐžÑÐµ). ÐÐŽÑÐµÑ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ Ð¿ÐµÑÐ²ÑÐ¹ Ð¿ÑÐœÐºÑ ÐºÐŸÐœÑÐ°ÐºÑÐ°  Ð² ÑÐ»ÑÑÐ°Ðµ Ð»ÑÐ±ÑÑ
+ Ð¿ÑÐŸÐ±Ð»ÐµÐŒ, Ñ ÐºÐŸÑÐŸÑÑÐŒÐž ÑÑÐ°Ð»ÐºÐžÐ²Ð°ÑÑÑÑ Ð¿ÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="169">ÐÑÐ°ÑÐºÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ â ÑÑÐŸ Ð¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐµ, ÐŸÐ¿ÐžÑÑÐ²Ð°ÑÑÐµÐµ Ð¿ÑÐžÐœÑÐžÐ¿Ñ, ÐºÐŸÑÐŸÑÑÐŒÐž ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÑÑÑÑÑ, ÑÑÐŸ Ð²ÐºÐ»ÑÑÐ°ÑÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐœÐŸ Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÐŸÐŽ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐŒ ÐÐ± ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž  ÐœÐ° ÐœÐ°ÑÐ°Ð»ÑÐœÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Figure id="starting_a_new_collection">
+<Title>
+<Text id="170">ÐÐ°ÑÐ°Ð»ÐŸ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<File width="407" height="317" url="images/User_Fig_4.png"/>
+</Figure>
+<Figure id="exploring_the_local_file_space">
+<Title>
+<Text id="171">ÐÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÐµ Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ð°</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_5.png"/>
+</Figure>
+<Text id="172">ÐÐ° ÑÑÐŸÐŒ ÑÑÐ°Ð¿Ðµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐµÑÐ°ÐµÑ, ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ Ð»Ðž ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐ°ÐºÐŸÐ¹ Ð¶Ðµ ÑÑÑÑÐºÑÑÑÑ, ÑÑÐŸ Ðž ÑÑÑÐµÑÑÐ²ÑÑÑÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐžÐ»Ðž ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ Ð¿ÐŸÐ»ÐœÐŸÑÑÑÑ ÐœÐŸÐ²ÑÐ¹ Ð²ÐžÐŽ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ° ÑÐžÑ.4 ÐŸÐœ Ð²ÑÐ±ÑÐ°Ð» Ð±Ð°Ð·ÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐœÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÐŸÐŽÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ð° ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÑÐ°Ð·Ð²ÐžÑÐžÑ (ÐÐÐ ). Ð­ÑÐŸ Ð¿ÐŸÐŽÑÐ°Ð·ÑÐŒÐµÐ²Ð°ÐµÑ, ÑÑÐŸ ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐÐÐ , ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð±ÑÐŽÐµÑ Ð¿ÑÐžÐŒÐµÐœÐµÐœ Ðž ÐŽÐ»Ñ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. (Ð€Ð°ÐºÑÐžÑÐµÑÐºÐž, ÑÑÐŸÑ ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ð»ÑÑ ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Greenstone, ÐºÐŸÑÐŸÑÑÐµ ÐžÐŒÐµÑÑ ÐŸÐ±ÑÑÑ ÑÑÑÑÐºÑÑÑÑ Ðž ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑ, ÐœÐŸ ÑÐ°Ð·Ð»ÐžÑÐœÐŸÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ, Ð²ÐºÐ»ÑÑÐ°Ñ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ ÑÐ°Ð·Ð²ÐžÑÐžÑ Ðž ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, Ð¿ÐŸÑÑÐ°Ð²Ð»ÑÐµÐŒÑÐµ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŸÐ±ÑÐ°Ð·ÑÐŸÐ² Ñ Greenstone).</Text>
+<Text id="173">ÐÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ DLS ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÐ»ÐµÐŽÑÑÑÐžÐµ Ð¿ÑÐœÐºÑÑ:</Text>
+<BulletList>
+<Bullet>
+<Text id="174">ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ</Text>
+</Bullet>
+<Bullet>
+<Text id="175">ÐÑÐµÐŽÐŒÐµÑ</Text>
+</Bullet>
+<Bullet>
+<Text id="176">Ð¯Ð·ÑÐº</Text>
+</Bullet>
+<Bullet>
+<Text id="177">ÐÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑ</Text>
+</Bullet>
+<Bullet>
+<Text id="178">ÐÐ»ÑÑÐµÐ²ÑÐµ ÑÐ»ÐŸÐ²Ð°</Text>
+</Bullet>
+</BulletList>
+<Text id="179">(ÐÑÐŸÐŒÐµ ÑÐŸÐ³ÐŸ, ÐžÐŒÐµÐµÑÑÑ Ð¿ÑÐœÐºÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÑÐ¹ AZList, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ, ÐºÐ°ÐºÐŸÐ¹ ÑÑÐ°ÑÑÐŸÐº Ð°Ð»ÑÐ°Ð²ÐžÑÐœÐŸÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ° ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑÐŒÐž ÑÐžÐ¿Ð° âÐ-Bâ ÐžÐ»Ðž âC-D-Eâ. Ð­ÑÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐžÐŒÐµÑÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÑÐŸÑÐœÐŸÐ³ÐŸ ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ ÑÐ°Ð·ÐŽÐµÐ»Ð°ÐŒÐž ÑÐ¿ÐžÑÐºÐ°. ÐÐ»Ñ Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²Ð° ÐŽÑÑÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÑÑÐ° ÐŸÐ¿ÑÐžÑ ÐŸÑÑÑÑÑÑÐ²ÑÐµÑ, Ðž Greenstone  ÐœÐ°Ð·ÐœÐ°ÑÐ°ÐµÑ ÑÐµÐ³ÐŒÐµÐœÑÑ ÑÐ°ÐŒÐŸÑÑÐŸÑÑÐµÐ»ÑÐœÐŸ).</Text>
+<Text id="180">ÐÑÐ»Ðž Ð¶Ðµ ÐœÐ° ÑÑÐŸÐŒ ÑÑÐ°Ð¿Ðµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð²ÑÐ±ÑÐ°Ð» ÐŽÑÑÐ³ÐŸÐ¹ Ð²Ð°ÑÐžÐ°ÐœÑ - Â«ÐÐŸÐ²Ð°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÂ», ÑÐŸ ÐµÐ³ÐŸ Ð¿ÐŸÐ¿ÑÐŸÑÐžÐ»Ðž Ð±Ñ Ð²ÑÐ±ÑÐ°ÑÑ, ÐºÐ°ÐºÐžÐµ ÐœÐ°Ð±ÐŸÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐŸÐ»Ð¶ÐœÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ Ð² ÑÑÐŸÐ¹ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¢ÑÐž ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÑ
+ ÐœÐ°Ð±ÐŸÑÐ° Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ: Dublin Core, ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ DLS, ÑÐ¿ÐŸÐŒÐžÐœÐ°Ð²ÑÐµÐ¹ÑÑ Ð²ÑÑÐµ, Ðž ÐœÐ°Ð±ÐŸÑ, ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÑÐ»ÐµÐŒÐµÐœÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐœÑÐµ Greenstone Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŒÐŸÐ¶ÐµÑ ÑÐ°ÐºÐ¶Ðµ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐœÐŸÐ²ÑÐµ ÐœÐ°Ð±ÐŸÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÑÑ Ð¿Ð°ÐœÐµÐ»Ñ, Ð°ÐºÑÐžÐ²ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÐœÑÑ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐŒÐµÐœÑ Â«ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµÂ».</Text>
+<Text id="181">ÐÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐœÐ°Ð±ÐŸÑÐŸÐ² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ²ÑÐ·Ð°ÐœÑ Ñ ÐŸÐŽÐœÐŸÐ¹ Ðž ÑÐŸÐ¹ Ð¶Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹; ÑÐžÑÑÐµÐŒÐ° ÐŽÐµÑÐ¶ÐžÑ ÐžÑ
+ ÐŸÑÐŽÐµÐ»ÑÐœÐŸ, ÑÐ°Ðº ÑÑÐŸ, ÐœÐ°Ð¿ÑÐžÐŒÐµÑ,  ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐŒÐŸÐ³Ð»Ðž Ð±Ñ ÐžÐŒÐµÑÑ ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐ°Ðº Ð² Dublin Core, ÑÐ°Ðº Ðž Ð² DLS. Ð Ð°Ð·Ð»ÐžÑÐœÑÐµ ÐœÐ°Ð±ÐŸÑÑ ÑÐµÑÐºÐŸ ÐŸÑÐ»ÐžÑÐ°ÑÑÑÑ Ð¿ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÑ. ÐÐµÑÐ²ÐœÐŸ ÐœÐ°Ð±ÐŸÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ Ð² XML. </Text>
+</Content>
+</Subsection>
+<Subsection id="assembling_the_source_material">
+<Title>
+<Text id="182">Ð¡Ð±ÐŸÑ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ³ÐŸ ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ð°</Text>
+</Title>
+<Content>
+<Text id="183">ÐÐŸÑÐ»Ðµ ÑÐµÐ»ÑÐºÐ° ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ ÐÐ Ð² ÐŒÐµÐœÑ Â«ÐÐŸÐ²Ð°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÂ» ÐŸÑÑÐ°ÑÑÐžÐµÑÑ ÑÐ°ÑÑÐž ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÐŽÐŸ ÑÐŸÐ³ÐŸ ÑÐµÑÐŸÐ³ÐŸ ÑÐ²ÐµÑÐ°, ÑÑÐ°ÐœÐŸÐ²ÑÑÑÑ Ð°ÐºÑÐžÐ²ÐœÑÐŒÐž. ÐÐ°ÐœÐµÐ»Ñ Ð¡Ð±ÐŸÑÑÐžÐºÐ°, ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÐ°Ñ ÐºÐ»Ð°Ð²ÐžÑÐµÐ¹ Ñ ÑÐµÐŒ Ð¶Ðµ ÐžÐŒÐµÐœÐµÐŒ ÑÐ²ÐµÑÑ
+Ñ ÐœÐ° ÑÐžÑ.4, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐ° Ð² Ð¿ÐµÑÐ²ÐŸÐœÐ°ÑÐ°Ð»ÑÐœÐŸÐŒ Ð²ÐžÐŽÐµ. Ð­ÑÐŸ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸÐµ ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐµ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²ÐŸ Ðž ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÐ±ÐžÑÐ°Ñ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐŽÐ»Ñ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ°ÐœÐµÐ»Ñ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐ° ÐœÐ° ÐŽÐ²Ðµ ÑÐ°ÑÑÐž, Ð»ÐµÐ²Ð°Ñ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐ° ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ ÑÑÑÑÐºÑÑÑÑ, Ð° Ð¿ÑÐ°Ð²Ð°Ñ â ÐŽÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="184">ÐÐµÐ¹ÑÑÐ²ÐžÑ, ÐŽÐŸÑÑÑÐ¿ÐœÑÐµ ÐœÐ° ÑÑÐŸÐŒ ÑÑÐ°Ð¿Ðµ, Ð²ÐºÐ»ÑÑÐ°ÑÑ:</Text>
+<BulletList>
+<Bullet>
+<Text id="185">ÐÐ°Ð²ÐžÐ³Ð°ÑÐžÑ Ð¿ÐŸ ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ¹ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐŸÐ¹ ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ¹ ÑÑÑÑÐºÑÑÑÐµ Ðž Ð¿ÐŸ ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ¹ ÑÑÑÑÐºÑÑÑÐµ, ÐŽÐµÐ¹ÑÑÐ²ÑÑ ÐŸÐ±ÑÑÐœÑÐŒ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ.</Text>
+</Bullet>
+<Bullet>
+<Text id="186">ÐÐµÑÐµÐŒÐµÑÐµÐœÐžÐµ Ðž Ð²Ð²ÐŸÐŽ ÑÐ°Ð¹Ð»ÐŸÐ² Ð² ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="187">ÐÐœÐŸÐ¶ÐµÑÑÐ²ÐµÐœÐœÑÐ¹ Ð²ÑÐ±ÐŸÑ ÑÐ°Ð¹Ð»ÐŸÐ².</Text>
+</Bullet>
+<Bullet>
+<Text id="188">ÐÐµÑÐµÐŒÐµÑÐµÐœÐžÐµ Ðž Ð²Ð²ÐŸÐŽ Ð¿ÐŸÐ»ÐœÑÑ
+ Ð¿ÐŸÐŽÐžÐµÑÐ°ÑÑ
+ÐžÐ¹.</Text>
+</Bullet>
+<Bullet>
+<Text id="189">Ð£ÐŽÐ°Ð»ÐµÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐžÐ· Ð²ÐŸÐ·ÐœÐžÐºÐ°ÑÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</Bullet>
+<Bullet>
+<Text id="190">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐœÐŸÐ²ÑÑ
+ Ð¿ÐŸÐŽÐžÐµÑÐ°ÑÑ
+ÐžÐ¹ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</Bullet>
+<Bullet>
+<Text id="191">Ð€ÐžÐ»ÑÑÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐ°Ð¹Ð»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÑÐ²Ð»ÑÑÑÑÑ Ð²ÐžÐŽÐžÐŒÑÐŒÐž, Ðž Ð² Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ¹ ÑÐžÑÑÐµÐŒÐµ, Ðž Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐŸÑÐœÐŸÐ²Ð°ÐœÐœÐŸÐ¹ ÐœÐ° Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ Ð³ÑÑÐ¿Ð¿Ð°Ñ
+ ÐžÐ»Ðž ÐœÐ° ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ, Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÐžÑ
+ ÑÐµÑÐŒÐžÐœÐŸÐ².</Text>
+</Bullet>
+<Bullet>
+<Text id="192">ÐÐ°Ð¿ÑÑÐº ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŽÐ»Ñ Ð¿ÐŸÐºÐ°Ð·Ð° ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð° ÐŽÐ²ÐŸÐ¹ÐœÑÐŒ ÑÐµÐ»ÑÐºÐŸÐŒ ÐœÐ° ÐœÑÐŒ.</Text>
+</Bullet>
+</BulletList>
+<Text id="193">ÐÑÐµÐŽÐ¿ÑÐžÐœÑÑÑ ÐŒÐµÑÑ Ð¿ÑÐµÐŽÐŸÑÑÐŸÑÐŸÐ¶ÐœÐŸÑÑÐž, ÐºÐŸÐ³ÐŽÐ° ÐžÐŒÐµÑÑ ÐŽÐµÐ»ÐŸ ÑÐŸ ÑÑÐŸÐ»ÐºÐœÐŸÐ²ÐµÐœÐžÑÐŒÐž ÐžÐŒÑÐœ, ÐµÑÐ»Ðž ÑÐ°Ð¹Ð»Ñ Ñ ÐŸÐŽÐžÐœÐ°ÐºÐŸÐ²ÑÐŒ ÐžÐŒÐµÐœÐµÐŒ Ð² ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐ°ÑÑÑÑ
+ ÑÑÑÑÐºÑÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ° ÑÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÑ Ð² ÐŸÐŽÐœÑ Ð¿Ð°Ð¿ÐºÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="194">ÐÐ° ÑÐžÑÑÐœÐºÐµ 5 Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐžÐœÑÐµÑÐ°ÐºÑÐžÐ²ÐœÑÐ¹ Ð¿ÐŸÐºÐ°Ð· ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸ ÐŽÐµÑÐµÐ²Ð° ÐŽÐ»Ñ ÐžÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐžÑ Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ. ÐÐ° ÑÑÐŸÐ¹ ÑÑÐ°ÐŽÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐ¿ÑÐ°Ð²Ð° Ð¿ÑÑÑÐ°, Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐœÐ°Ð¿ÐŸÐ»ÐœÑÐµÑ ÐµÐµ, Ð¿ÐµÑÐµÑÑÐ³ÐžÐ²Ð°Ñ Ðž Ð¿ÑÐŸÐ¿ÑÑÐºÐ°Ñ ÐžÐœÑÐµÑÐµÑÑÑÑÐžÐµ ÐµÐ³ÐŸ ÑÐ°Ð¹Ð»Ñ Ñ Ð»ÐµÐ²ÐŸÐ¹ ÐœÐ° Ð¿ÑÐ°Ð²ÑÑ ÑÐ°ÑÑÑ Ð¿Ð°ÐœÐµÐ»Ðž. Ð¢Ð°ÐºÐžÐµ ÑÐ°Ð¹Ð»Ñ ÑÐºÐŸÑÐµÐµ Â«ÑÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÑÂ», ÑÐµÐŒ Â«Ð¿ÐµÑÐµÐŒÐµÑÐµÐœÑÂ», ÑÑÐŸÐ±Ñ ÐœÐµ ÐœÐ°ÑÑÑÐ°ÑÑ Ð¿ÐµÑÐ²ÐŸÐœÐ°ÑÐ°Ð»ÑÐœÑÑ ÑÐ°Ð¹Ð»ÐŸÐ²ÑÑ ÑÐžÑÑÐµÐŒÑ. ÐÐ±ÑÑÐœÑÐµ ÐŒÐµÑÐŸÐŽÑ Ð²ÑÐ±ÐŸÑÐ° ÐŽÐ»Ñ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐµÐœÐœÐŸÐ³ÐŸ Ð¿ÐµÑÐµÐŒÐµÑÐµÐœÐžÑ Ðž Ð²Ð²ÐŸÐŽÐ°, ÑÑÑÑÐºÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÑÐµÐŒ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹ (Â«Ð¿Ð°Ð¿ÐŸÐºÂ»), Ð° ÑÐ°ÐºÐ¶Ðµ ÑÐŽÐ°Ð»ÐµÐœÐžÑ ÑÐ°Ð¹Ð»ÐŸÐ² ÐžÐ· ÐœÐžÑ
+, Ð¿ÐµÑÐµÐŒÐµÑÐ°Ñ ÐžÑ
+ Ð² ÐºÐŸÑÐ·ÐžÐœÑ, Ð²ÑÐµ ÐŸÐœÐž ÑÐ²Ð»ÑÑÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž. </Text>
+<Text id="195">Ð¡ÑÑÐµÑÑÐ²ÑÑÑÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÑ Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÐµÐ¹ ÑÐ»ÐµÐ²Ð°, ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÐŸÐ¹ Â«ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž GreenstoneÂ», ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÑÐºÑÑÑÑ Ðž ÐžÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÑ Ð¿ÐŸÐŽÐŸÐ±ÐœÐŸ Ð»ÑÐ±ÐŸÐ¹ ÐŽÑÑÐ³ÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž. ÐÐŽÐœÐ°ÐºÐŸ, ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÐœÐµÐ¹ ÐŸÑÐ»ÐžÑÐ°ÑÑÑÑ ÐŸÑ ÐŸÐ±ÑÑÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐµÐŒ, ÑÑÐŸ ÐŸÐœÐž ÑÐ¶Ðµ ÐžÐŒÐµÑÑ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐœÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÑ
+ÑÐ°ÐœÑÑÑÑÑ Ð¿ÑÐž Ð¿ÐµÑÐµÐŒÐµÑÐµÐœÐžÐž Ð² ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐŸÐœÑÐ»ÐžÐºÑÑ ÐŒÐŸÐ³ÑÑ Ð²ÐŸÐ·ÐœÐžÐºÐœÑÑÑ ÐžÐ·-Ð·Ð° ÑÐŸÐ³ÐŸ, ÑÑÐŸ ÐžÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ, Ð±ÑÐ»Ðž Ð·Ð°ÐŽÐ°ÐœÑ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐœÐ°Ð±ÐŸÑÐŸÐ² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, Ð¿ÑÐžÐŒÐµÐœÐµÐœÐœÑÑ
+ ÐŽÐ»Ñ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŽÐŸÐ»Ð¶ÐµÐœ ÑÐ°Ð·ÑÐµÑÐžÑÑ ÑÑÐž ÐºÐŸÐœÑÐ»ÐžÐºÑÑ. ÐÐ° ÑÐžÑÑÐœÐºÐµ 6 Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð²ÑÐ±ÑÐ°Ð» ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐžÐ· ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð¿ÐµÑÐµÑÑÐœÑÐ» ÐžÑ
+ Ð² ÐœÐŸÐ²ÑÑ. ÐÑÐ¿Ð»ÑÐ²Ð°ÑÑÐµÐµ ÐŸÐºÐœÐŸ ÐŸÐ±ÑÑÑÐœÑÐµÑ, ÑÑÐŸ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑ ÐœÐµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°Ðœ, Ðž Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÐµÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐžÐ»Ðž Ð²ÑÐ±ÑÐ°ÑÑ ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÑÑ ÐÐŸÐ±Ð°Ð²ÐžÑÑ, ÑÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÑÑÐŸÑ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðº ÐŽÐ°ÐœÐœÐŸÐŒÑ ÐœÐ°Ð±ÐŸÑÑ<FootnoteRef id="1"/>, ÐžÐ»Ðž Ð²ÑÐ±ÑÐ°ÑÑ ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, Ð° Ð·Ð°ÑÐµÐŒ ÑÐ»ÐµÐŒÐµÐœÑ Ðž ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÑÑ Ð¡Ð»ÐžÑÑ, ÑÑÐŸÐ±Ñ ÑÑÑÐµÐºÑÐžÐ²ÐœÐŸ Ð¿ÐµÑÐµÐžÐŒÐµÐœÐŸÐ²Ð°ÑÑ ÑÑÐ°ÑÑÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐœÐ° ÐœÐŸÐ²ÑÐ¹, ÐŸÐ±ÑÐµÐŽÐžÐœÑÑ ÐžÑ
+. ÐÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð² Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐžÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°Ñ
+ ÐžÐ· ÑÐŸÐ¹ Ð¶Ðµ ÑÐ°ÐŒÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð±ÑÐŽÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÐœÑ ÑÐµÐŒ Ð¶Ðµ ÑÐ°ÐŒÑÐŒ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ.</Text>
+<Text id="196">ÐÐŸÐ³ÐŽÐ° ÐŸÑÐŸÐ±ÑÐ°ÐœÑ Ð±ÐŸÐ»ÑÑÐžÐµ ÐœÐ°Ð±ÐŸÑÑ Ð¿ÐµÑÐµÑÑÐ³ÐžÐ²Ð°ÐœÐžÐµÐŒ Ðž Ð²Ð²ÐµÐŽÐµÐœÐžÐµÐŒ ÐžÑ
+ Ð² ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐŽÐµÐ¹ÑÑÐ²ÐžÑ Ð¿ÐŸ ÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŒÐŸÐ³ÑÑ Ð·Ð°ÐœÑÑÑ ÐœÐµÐºÐŸÑÐŸÑÐŸÐµ Ð²ÑÐµÐŒÑ, ÐŸÑÐŸÐ±ÐµÐœÐœÐŸ ÐµÑÐ»Ðž Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. Ð§ÑÐŸÐ±Ñ ÐŸÑÑÐ°Ð·ÐžÑÑ Ð¿ÑÐŸÐŽÐ²ÐžÐ¶ÐµÐœÐžÐµ Ð¿ÑÐŸÑÐµÑÑÐ°, ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ, ÐºÐ°ÐºÐŸÐ¹ ÑÐ°Ð¹Ð» Ð² ÐŽÐ°ÐœÐœÐŸÐµ Ð²ÑÐµÐŒÑ ÐºÐŸÐ¿ÐžÑÑÐµÑÑÑ Ðž ÐºÐ°ÐºÐŸÐ¹ Ð¿ÑÐŸÑÐµÐœÑ ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐ¶Ðµ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°Ðœ.</Text>
+<Text id="197">ÐÑÐµÐŽÑÑÐŒÐŸÑÑÐµÐœÑ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÐµ ÑÑÐµÐŽÑÑÐ²Ð° ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐœÐžÑ, ÐºÐŸÐ³ÐŽÐ° ÐžÐŒÐµÑÑ ÐŽÐµÐ»ÐŸ Ñ Ð±ÐŸÐ»ÑÑÐžÐŒÐž ÐœÐ°Ð±ÐŸÑÐ°ÐŒÐž ÑÐ°Ð¹Ð»ÐŸÐ². ÐÐ°Ð¿ÑÐžÐŒÐµÑ, Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŒÐŸÐ¶ÐµÑ Ð²ÑÐ±ÑÐ°ÑÑ ÑÐžÐ»ÑÑÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸ ÐŽÐµÑÐµÐ²Ð°, ÑÑÐŸÐ±Ñ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÑÐŸÐ»ÑÐºÐŸ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÑÐ°Ð¹Ð»Ñ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð¿ÐŸÐœÐžÐ¶Ð°ÑÑÐžÐµÑÑ ÐŒÐµÐœÑ ÑÐžÐ¿ÐŸÐ² ÑÐ°Ð¹Ð»ÐŸÐ², Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÑÑ
+ Ð¿ÐŸÐŽ ÐŽÐµÑÐµÐ²ÑÑÐŒÐž. ÐÐ° ÑÐžÑÑÐœÐºÐµ 7 Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ ÑÐŸÐ»ÑÐºÐŸ ÑÐ°Ð¹Ð»Ñ ÐÐ¢Ð Ðž ÐÐ¢ÐL (Ðž ÑÐŸÐ»ÑÐºÐŸ ÑÑÐž ÑÐ°Ð¹Ð»Ñ Ð±ÑÐŽÑÑ ÑÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÑ Ð¿ÑÑÐµÐŒ Ð¿ÐµÑÐµÐŒÐµÑÐµÐœÐžÑ Ðž ÐŸÑÑÐ°ÐœÐŸÐ²ÐºÐž).</Text>
+</Content>
+</Subsection>
+<Subsection id="enriching_the_documents">
+<Title>
+<Text id="198">ÐÐ°Ð¿ÐŸÐ»ÐœÐµÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="199">Ð¡Ð»ÐµÐŽÑÑÑÐ°Ñ ÑÑÐ°ÐŽÐžÑ Ð² ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐŸÐ»Ð¶ÐœÐ° ÐœÐ°Ð¿ÐŸÐ»ÐœÐžÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ  ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐµÐŒ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐ»Ð°Ð²ÐžÑÐ° Â«ÐÐ±ÐŸÐ³Ð°ÑÐžÑÑÂ» Ð²ÑÐ²ÐŸÐŽÐžÑ ÐœÐŸÐ²ÑÑ Ð¿Ð°ÐœÐµÐ»Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž (ÑÐžÑÑÐœÐŸÐº 8), ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐŽÐµÑÐµÐ²ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐ»ÐµÐ²Ð°, Ð° ÑÐ¿ÑÐ°Ð²Ð° â Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ðº ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÑÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ ÐžÐ»Ðž Ðº Ð³ÑÑÐ¿Ð¿Ðµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+<Text id="200">ÐÐŸÐºÑÐŒÐµÐœÑÑ, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÑÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÑ Ð² Ñ
+ÐŸÐŽÐµ Ð¿ÐµÑÐ²ÐŸÐ³ÐŸ ÑÑÐ°Ð¿Ð°, ÐžÐŽÑÑ Ñ Ð»ÑÐ±ÑÐŒÐž Ð¿ÑÐžÐŒÐµÐœÐžÐŒÑÐŒÐž Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐœÑÐŒÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž. ÐÑÐ»Ðž ÐŽÐŸÐºÑÐŒÐµÐœÑ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐ°ÑÑÑÑ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+, ÑÐŸ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð¿ÐµÑÐµÐœÐŸÑÑÑÑÑ Ð² ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐŸÐœÐµÑÐœÐŸ, ÑÑÐ° ÐœÐŸÐ²Ð°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐŒÐŸÐ¶ÐµÑ ÐžÐŒÐµÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÐœÐ°Ð±ÐŸÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐžÐ»Ðž Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ ÑÐŸÐ»ÑÐºÐŸ ÑÐ°ÑÑÑ ÐœÐ°Ð±ÐŸÑÐ° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, Ðž ÑÐŸÐ»ÑÐºÐŸ ÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐžÐœÐ°ÐŽÐ»ÐµÐ¶Ð°Ñ ÐœÐ°Ð±ÐŸÑÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð¿ÐµÑÐµÐœÐŸÑÑÑÑÑ. Ð Ð°Ð·ÑÐµÑÐµÐœÐžÐµ ÑÐ°ÐºÐžÑ
+ ÐºÐŸÐœÑÐ»ÐžÐºÑÐŸÐ² ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÑÑÐµÐ±ÐŸÐ²Ð°ÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐŸÐ³ÐŸ Ð²ÐŒÐµÑÐ°ÑÐµÐ»ÑÑÑÐ²Ð° ÑÐµÑÐµÐ· ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÐ¹ ÐŽÐžÐ°Ð»ÐŸÐ³ (ÑÐžÑÑÐœÐŸÐº 6). ÐÑÐ±ÑÐµ ÑÐŽÐµÐ»Ð°ÐœÐœÑÐµ Ð²ÑÐ±ÐŸÑÑ Ð·Ð°Ð¿ÐŸÐŒÐžÐœÐ°ÑÑÑÑ ÐŽÐ»Ñ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÑÐžÑ
+ ÐºÐŸÐ¿ÐžÐ¹ ÑÐ°Ð¹Ð»ÐŸÐ². </Text>
+<Text id="201">ÐÐ°ÐœÐµÐ»Ñ Â«ÐÐ±ÐŸÐ³Ð°ÑÐžÑÑÂ» Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð·Ð°ÐŽÐ°ÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐœÐŸÐ²ÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŒÐŸÐ¶ÐœÐŸ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ Ðº ÐœÐ°Ð±ÐŸÑÑ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ ÐŽÐ»Ñ ÑÐ»ÐµÐŒÐµÐœÑÐ°. ÐÑÐ»Ðž Ð·ÐœÐ°ÑÐµÐœÐžÑ ÑÐ»ÐµÐŒÐµÐœÑÐ° ÐžÐŒÐµÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÑÑ ÑÑÑÑÐºÑÑÑÑ, ÐžÐµÑÐ°ÑÑ
+ÐžÑ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÑÐ°ÑÑÐžÑÐµÐœÐ° ÑÐµÐŒ Ð¶Ðµ ÑÐ°ÐŒÑÐŒ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ.</Text>
+<Figure id="importing_existing_metadata">
+<Title>
+<Text id="202">ÐÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</Title>
+<File width="407" height="317" url="images/User_Fig_6.png"/>
+</Figure>
+<Figure id="filtering_the_file_trees">
+<Title>
+<Text id="203">Ð€ÐžÐ»ÑÑÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐ°Ð¹Ð»ÐŸÐ²ÑÑ
+ ÐŽÐµÑÐµÐ²ÑÐµÐ²</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_7.png"/>
+</Figure>
+<Figure id="assigning_metadata_using_enrich_view">
+<Title>
+<Text id="204">ÐÐ°ÐŽÐ°ÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑ</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_8.png"/>
+</Figure>
+<Figure id="viewing_all_metadata_for_selected_files">
+<Title>
+<Text id="205">ÐÑÐŸÑÐŒÐŸÑÑ Ð²ÑÐµÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+  ÐŽÐ»Ñ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ²</Text>
+</Title>
+<File width="407" height="317" url="images/User_Fig_9.png"/>
+</Figure>
+<Text id="206">ÐÐœÐ°ÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐŸÐ³ÑÑ ÑÐ°ÐºÐ¶Ðµ Ð±ÑÑÑ Ð·Ð°ÐŽÐ°ÐœÑ ÐŽÐ»Ñ Ð¿Ð°Ð¿ÐŸÐº ÑÐµÐŒ Ð¶Ðµ ÑÐ°ÐŒÑÐŒ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ. ÐÐŸÐºÑÐŒÐµÐœÑÑ Ð² ÑÑÐžÑ
+ Ð¿Ð°Ð¿ÐºÐ°Ñ
+, ÐŽÐ»Ñ ÐºÐŸÑÐŸÑÑÑ
+ ÑÑÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐœÐµ ÑÐºÐ°Ð·Ð°ÐœÑ, ÐœÐ°ÑÐ»ÐµÐŽÑÑÑ ÑÑÐž Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐŽÐœÐ°ÐºÐŸ ÐŸÐœÐž ÐŒÐŸÐ³ÑÑ Ð²Ð¿ÐŸÑÐ»ÐµÐŽÑÑÐ²ÐžÐž Ð±ÑÑÑ Ð¿ÐµÑÐµÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÐµÐŒ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ.</Text>
+<Text id="207">ÐÐµÐ¹ÑÑÐ²ÐžÐµ ÐœÐ° ÑÑÐŸÐ¹ ÑÑÐ°ÐŽÐžÐž Ð²ÐºÐ»ÑÑÐ°ÑÑ:</Text>
+<BulletList>
+<Bullet>
+<Text id="208">ÐÐ°Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐœÐŸÐ²ÑÑ
+ Ðž ÑÑÑÐµÑÑÐ²ÑÑÑÐžÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+</Bullet>
+<Bullet>
+<Text id="209">ÐÐ°Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðº ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÐŸÐŒÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="210">ÐÐ°Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðº Ð¿Ð°Ð¿ÐºÐµ (ÐŸÐœÐž ÐœÐ°ÑÐ»ÐµÐŽÑÑÑÑÑ Ð²ÑÐµÐŒÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒÐž Ð² Ð¿Ð°Ð¿ÐºÐµ, Ð²ÐºÐ»ÑÑÐ°Ñ ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÐµÑÑ Ð²ÐŸ Ð²Ð»ÐŸÐ¶ÐµÐœÐœÑÑ
+ Ð¿Ð°Ð¿ÐºÐ°Ñ
+).</Text>
+</Bullet>
+<Bullet>
+<Text id="211">ÐÐ°Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐžÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÑÑ ÑÑÑÑÐºÑÑÑÐ° ÐŒÐŸÐ¶ÐµÑ ÐŽÐžÐœÐ°ÐŒÐžÑÐµÑÐºÐž ÐŸÐ±ÐœÐŸÐ²Ð»ÑÑÑÑÑ, ÐµÑÐ»Ðž ÑÑÐŸ ÑÑÐµÐ±ÑÐµÑÑÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="212">Ð ÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐžÐ»Ðž ÐŸÐ±ÐœÐŸÐ²Ð»ÐµÐœÐžÐµ ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+</Bullet>
+<Bullet>
+<Text id="213">Ð Ð°ÑÑÐŒÐŸÑÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÑ
+ Ðº Ð²ÑÐ±ÑÐ°ÐœÐœÑÐŒ ÑÐ°Ð¹Ð»Ð°ÐŒ Ðž ÐŽÐžÑÐµÐºÑÐŸÑÐžÑÐŒ.</Text>
+</Bullet>
+</BulletList>
+<Text id="214">ÐÐ»Ñ ÐœÐ°ÑÐµÐ³ÐŸ Ð¿ÑÐžÐŒÐµÑÐ° ÐœÐ° ÑÐžÑÑÐœÐºÐµ 8 Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð²ÑÐ±ÑÐ°Ð» Ð¿Ð°Ð¿ÐºÑ ÐµÑ121Ðµ Ðž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÐ» Â«EC CourierÂ» Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž. ÐÐœÐŸÐ¿ÐºÐž ÐŽÐ»Ñ ÐŸÐ±ÐœÐŸÐ²Ð»ÐµÐœÐžÑ Ðž ÑÐŽÐ°Ð»ÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÑÑÐ°ÐœÐŸÐ²ÑÑÑÑ Ð°ÐºÑÐžÐ²ÐœÑÐŒÐž Ð² Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÑÐŸÐ³ÐŸ, ÐºÐ°ÐºÐŸÐ¹ Ð²ÑÐ±ÐŸÑ Ð±ÑÐ» ÑÐŽÐµÐ»Ð°Ðœ.</Text>
+<Text id="215">Ð ÑÐµÑÐµÐœÐžÐµ ÑÑÐ°Ð¿Ð° ÐœÐ°Ð¿ÐŸÐ»ÐœÐµÐœÐžÑ ÐžÐ»Ðž Ð² ÑÐ»ÑÑÐ°Ðµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÐž Ð² Ð»ÑÐ±ÐŸÐµ ÐŽÑÑÐ³ÐŸÐµ Ð²ÑÐµÐŒÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŒÐŸÐ¶ÐµÑ Ð·Ð°Ñ
+ÐŸÑÐµÑÑ ÑÐ°ÑÑÐŒÐŸÑÑÐµÑÑ Ð²ÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž Ð·Ð°ÐŽÐ°ÐœÑ ÐŽÐ»Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð­ÑÐŸ ÐŽÐµÐ»Ð°ÐµÑÑÑ Ð¿ÑÑÐµÐŒ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÐœÐ°Ð±ÐŸÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ðž Ð²ÑÐ±ÐŸÑÐ° ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Â«ÐÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµÂ» Ð² ÐŒÐµÐœÑ, ÐºÐŸÑÐŸÑÐŸÐµ Ð¿ÑÐžÐœÐŸÑÐžÑ Ð²ÑÐ¿Ð»ÑÐ²Ð°ÑÑÐµÐµ ÐŸÐºÐœÐŸ, ÐºÐ°Ðº ÐœÐ° ÑÐžÑÑÐœÐºÐµ 9, ÐºÐŸÑÐŸÑÐŸÐµ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð² ÑÐŸÑÐŒÐµ ÐºÑÑÐ¿ÐœÐŸÑÐŸÑÐŒÐ°ÑÐœÐŸÐ¹ ÑÐ°Ð±Ð»ÐžÑÑ. ÐÐ»Ñ Ð±ÐŸÐ»ÑÑÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð¿ÐŸÐ»ÐµÐ·ÐœÐŸ ÐžÐŒÐµÑÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÐ²ÑÐ·Ð°ÐœÐœÑÑ
+ ÑÐŸÐ»ÑÐºÐŸ Ñ ÐŸÑÐŽÐµÐ»ÑÐœÑÐŒ ÑÐžÐ¿ÐŸÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, Ðž ÐµÑÐ»Ðž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÐ» ÑÐžÐ»ÑÑÑ ÑÐ°Ð¹Ð»Ð°, ÐºÐ°Ðº Ð±ÑÐ»ÐŸ ÑÐ¿ÐŸÐŒÑÐœÑÑÐŸ Ð²ÑÑÐµ, ÑÐŸ  ÑÐŸÐ»ÑÐºÐŸ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÑÐ°ÑÑÐ²ÑÑÑ Ð² Ð¿ÐŸÐºÐ°Ð·Ðµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+<Text id="216">ÐÐ°ÐœÐµÐ»Ñ ÐœÐ° ÑÐžÑÑÐœÐºÐµ 10 Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐœÐ°Ð±ÐŸÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐŽÐµÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÐµÑ ÑÐ»ÐµÐŒÐµÐœÑ ÐÑÐµÐŽÐŒÐµÑ ÐžÐ· DLS. ÐÐœÐ°ÑÐµÐœÐžÑ ÑÑÐŸÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐ° ÑÐŸÑÐŒÐžÑÑÑÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑ, Ðž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐžÑÑÐ»ÐµÐŽÑÐµÑ, Ð° Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ Ðž ÐžÐ·ÐŒÐµÐœÑÐµÑ, ÑÐ¿ÐžÑÐŸÐº Ð·ÐœÐ°ÑÐµÐœÐžÐ¹, Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐ°. Ð¢Ð° Ð¶Ðµ ÑÐ°ÐŒÐ°Ñ Ð¿Ð°ÐœÐµÐ»Ñ ÑÐ°ÐºÐ¶Ðµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐÐ°ÐŒ ÐžÐ·ÐŒÐµÐœÑÑÑ Â«Ð¿ÑÐŸÑÐžÐ»ÑÂ» ÐŽÐ»Ñ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² ÐŸÐŽÐœÐŸÐ³ÐŸ ÐœÐ°Ð±ÐŸÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐœÐ° ÐŽÑÑÐ³ÐŸÐ¹. Ð­ÑÐŸÑ Ð¿ÑÐŸÑÐžÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐµÑÑÑ Ð¿ÑÐž ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐžÐ· ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÐžÐŒÐµÑÑ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð·Ð°ÐŽÐ°ÐœÐœÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ. </Text>
+<Figure id="editing_the_metadata_set">
+<Title>
+<Text id="217">Ð ÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐœÐ°Ð±ÐŸÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</Title>
+<File width="407" height="317" url="images/User_Fig_10.png"/>
+</Figure>
+<Figure id="designing_the_collection">
+<Title>
+<Text id="218">ÐÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_11.png"/>
+</Figure>
+<Figure id="specifying_which_plug-ins_to_use">
+<Title>
+<Text id="219">ÐÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ, ÐºÐ°ÐºÐžÐµ Ð¿Ð»Ð°Ð³ÐžÐœÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_12.png"/>
+</Figure>
+<Figure id="configuring_arguments_to_a_plug-in">
+<Title>
+<Text id="220">ÐÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² ÐŽÐ»Ñ Ð¿Ð»Ð°Ð³ÐžÐœÐŸÐ²</Text>
+</Title>
+<File width="407" height="317" url="images/User_Fig_13.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="designing_the_collection_1">
+<Title>
+<Text id="221">ÐÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="222">ÐÐ°ÐœÐµÐ»Ñ Â«ÐÑÐŸÐµÐºÑÂ» (ÑÐžÑÑÐœÐŸÐº 11-13) Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÑÑÑÑÐºÑÑÑÑ, ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÑ Ðž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÐµÐŒÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ°Ðº ÐŸÑÐŒÐµÑÐ°Ð»ÐŸÑÑ Ð²ÑÑÐµ, ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ ÑÑÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐµÑÑÐ° Ð·Ð°Ð¿ÐžÑÐ°Ðœ Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÑÐ¹  Ð² Greenstone ÑÐ²Ð»ÑÐµÑÑÑ ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ ÐŸÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÑÑÐµÐŽÑÑÐ² ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐœÐžÑ, ÑÑÐµÐ±ÑÐµÐŒÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹. Ð­ÑÐŸÑ ÑÑÐ°Ð¿ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÑÐµÑÐžÑ ÐŸÑÐŽÐµÐ»ÑÐœÑÑ
+ ÑÐºÑÐ°ÐœÐŸÐ² Ð²Ð·Ð°ÐžÐŒÐŸÐŽÐµÐ¹ÑÑÐ²ÐžÑ, ÐºÐ°Ð¶ÐŽÑÐ¹ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ ÐžÐŒÐµÐµÑ ÐŽÐµÐ»ÐŸ Ñ ÐŸÐŽÐœÐžÐŒ Ð°ÑÐ¿ÐµÐºÑÐŸÐŒ Ð¿ÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸÑÑÐž, ÐŸÐœ ÑÐ»ÑÐ¶ÐžÑ Ð³ÑÐ°ÑÐžÑÐµÑÐºÐžÐŒ ÑÐºÐ²ÐžÐ²Ð°Ð»ÐµÐœÑÐŸÐŒ ÐŸÐ±ÑÑÐœÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÑÑÐœÐŸÐ³ÐŸ ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð°.</Text>
+<Text id="223">ÐÐµÐ¹ÑÑÐ²ÐžÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ:</Text>
+<BulletList>
+<Bullet>
+<Text id="224">ÐÑÐŸÑÐŒÐŸÑÑ Ðž ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐžÐ¿Ð° ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÐÐ²ÑÐŸÑ Ðž ÐÐ±ÑÐµÐŽÐŸÑÑÑÐ¿ÐœÐŸÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</Bullet>
+<Bullet>
+<Text id="225">ÐÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ ÑÐŸÐ³ÐŸ, ÐºÐ°ÐºÐžÐµ ÐžÐœÐŽÐµÐºÑÑ Ð¿ÐŸÐ»ÐœÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ°  ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÑ.</Text>
+</Bullet>
+<Bullet>
+<Text id="226">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÑÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ðž ÐžÐœÐŽÐµÐºÑÐŸÐ² ÐŽÐ»Ñ ÐœÐžÑ
+.</Text>
+</Bullet>
+<Bullet>
+<Text id="227">ÐÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐµ ÐžÐ»Ðž ÑÐŽÐ°Ð»ÐµÐœÐžÐµ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐºÐž ÐŽÐ»Ñ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÑÐ·ÑÐºÐŸÐ² ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°.</Text>
+</Bullet>
+<Bullet>
+<Text id="228">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÑÐ¿ÐžÑÐºÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ Ð¿Ð»Ð°Ð³ÐžÐœÐŸÐ² Ðž ÐžÑ
+ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ².</Text>
+</Bullet>
+<Bullet>
+<Text id="229">ÐÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐ¿ÐžÑÐºÐ° ÐŽÐ»Ñ ÐŸÐ±Ð·ÐŸÑÐ° Ðž ÐŒÐŸÐŽÐžÑÐžÐºÐ°ÑÐžÐž.</Text>
+</Bullet>
+<Bullet>
+<Text id="230">ÐÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÑÑ
+ Ð¿Ð»Ð°Ð³ÐžÐœÐŸÐ².</Text>
+</Bullet>
+<Bullet>
+<Text id="231">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÑÐ¿ÐžÑÐºÐ° Â«ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ²Â», ÐžÑ
+ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ², ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ Ðž ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž.</Text>
+</Bullet>
+<Bullet>
+<Text id="232">ÐÐ°Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÑÑÑÐŸÐº ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŽÐ»Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð²ÐžÐŽÐŸÐ² ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐžÐ·ÐŒÐµÐœÑÑ ÑÐ°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ ÐµÑ Ð²ÐžÐŽ.</Text>
+</Bullet>
+<Bullet>
+<Text id="233">ÐÑÐŸÑÐŒÐŸÑÑ ÐœÐ°Ð±ÐŸÑÐŸÐ² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÐžÑ
+ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ², ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</Bullet>
+</BulletList>
+<Text id="234">ÐÐ° ÑÐžÑ.11 Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐµÐ»ÐºÐœÑÐ» ÐºÐ»Ð°Ð²ÐžÑÑ Â«ÐÑÐŸÐµÐºÑÂ» Ðž ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÐµÑ ÐŸÐ±ÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð²Ð²ÐµÐŽÐµÐœÐœÑÑ Ð¿ÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¡Ð»ÐµÐ²Ð° Ð² ÑÐ¿ÐžÑÐŸÐº Ð²ÐœÐµÑÐµÐœÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ Ð°ÑÐ¿ÐµÐºÑÑ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŒÐŸÐ¶ÐµÑ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÑÑ: ÐÐ±ÑÐµÐµ, ÐÐ»Ð°Ð³ÐžÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÐÐžÐŽÑ Ð¿ÐŸÐžÑÐºÐ°, ÐÐœÐŽÐµÐºÑÑ Ð¿ÐŸÐžÑÐºÐ°, ÐÐœÐŽÐµÐºÑÑ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ, ÐÐµÑÐµÑÐµÐºÐ°ÑÑÐžÐ¹ÑÑ Ð¿ÐŸÐžÑÐº, ÐÑÐŸÑÐŒÐŸÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ², Ð¡Ð²ÐŸÐ¹ÑÑÐ²Ð° ÑÐŸÑÐŒÐ°ÑÐ°, ÐÐµÑÐµÐ²ÐŸÐŽ ÑÐµÐºÑÑÐ°, ÐÐ°Ð±ÐŸÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐžÐŽ Ðž ÑÑÐœÐºÑÐžÐŸÐœÐ°Ð»ÑÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐ·ÐŒÐµÐœÑÑÑÑÑ Ð² Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÐœÐžÑ
+. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÑÐµÐ»ÐºÐ°Ñ ÐºÐœÐŸÐ¿ÐºÑ Â«ÐÐ»Ð°Ð³ÐžÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°Â», ÐŒÐŸÐ¶ÐœÐŸ Ð²ÑÐ·Ð²Ð°ÑÑ ÑÐºÑÐ°Ðœ, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÑÐ¹ ÐœÐ° ÑÐžÑ.12, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐÐ°ÐŒ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ, ÑÐŽÐ°Ð»ÑÑÑ ÐžÐ»Ðž ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÑÑ Ð¿Ð»Ð°Ð³ÐžÐœÑ Ðž ÐžÐ·ÐŒÐµÐœÑÑÑ Ð¿ÐŸÑÑÐŽÐŸÐº, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐŸÐœÐž Ð¿ÑÐžÐŒÐµÐœÐµÐœÑ Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ.</Text>
+<Text id="235">ÐÐ»Ð°Ð³ÐžÐœÑ Ðž ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÐžÐŒÐµÑÑ ÐŒÐœÐŸÐ³ÐŸ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² ÐžÐ»Ðž Â«Ð²Ð°ÑÐžÐ°ÐœÑÐŸÐ²Â», ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŒÐŸÐ¶ÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ. ÐÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÐŸÐµ ÐŸÐºÐœÐŸ ÐœÐ° ÑÐžÑ.13 Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð·Ð°ÐŽÐ°ÐœÐœÑÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÐŽÐ»Ñ ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÐžÐ· Ð¿Ð»Ð°Ð³ÐžÐœÐŸÐ². Ð¡ÐµÑÑÐµ Ð¿ÐŸÐ»Ñ ÑÑÐ°ÐœÐŸÐ²ÑÑÑÑ Ð°ÐºÑÐžÐ²ÐœÑÐŒÐž, ÐºÐŸÐ³ÐŽÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑ ÐŸÐ¿ÑÐžÐž, ÑÐµÐ»ÐºÐ°Ñ ÐŸÐºÐŸÐ»ÐŸ ÐŒÐžÐ³Ð°ÑÑÐµÐ³ÐŸ Ð¿ÐŸÐ»Ñ. ÐÐŸÑÐºÐŸÐ»ÑÐºÑ Greenstone ÑÐ²Ð»ÑÐµÑÑÑ ÐœÐµÐ¿ÑÐµÑÑÐ²ÐœÐŸ ÑÐ°Ð·Ð²ÐžÐ²Ð°ÑÑÐµÐ¹ÑÑ  ÐŸÑÐºÑÑÑÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÐŸÐ¹, ÑÐžÑÐ»ÐŸ Ð²Ð°ÑÐžÐ°ÐœÑÐŸÐ² ÐžÐŒÐµÐµÑ ÑÐµÐœÐŽÐµÐœÑÐžÑ Ðº ÑÐ²ÐµÐ»ÐžÑÐµÐœÐžÑ, ÑÐ°Ðº ÐºÐ°Ðº ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐž ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ ÐœÐŸÐ²ÑÐµ ÑÑÐµÐŽÑÑÐ²Ð° ÐŸÐ±ÑÐ»ÑÐ¶ÐžÐ²Ð°ÐœÐžÑ. Ð§ÑÐŸÐ±Ñ Ð¿ÐŸÐŒÐŸÑÑ ÑÐ¿ÑÐ°Ð²ÐžÑÑÑÑ Ñ ÑÑÐžÐŒ, Greenstone ÐžÐŒÐµÐµÑ Ð¿Ð»Ð°Ð³ÐžÐœ Â«ÐÐœÑÐŸÑÐŒÐ°ÑÐžÑÂ» - ÑÐµÑÐ²ÐžÑÐœÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð²ÐœÐŸÑÐžÑ Ð² ÑÐ¿ÐžÑÐŸÐº ÐŽÐŸÑÑÑÐ¿ÐœÑÐµ ÐŸÐ¿ÑÐžÐž ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ Ð¿Ð»Ð°Ð³ÐžÐœÐ°, Ð° ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð²ÑÐ·ÑÐ²Ð°ÐµÑ ÐµÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ, ÐºÐ°ÐºÐžÐµ Ð²Ð°ÑÐžÐ°ÐœÑÑ Ð¿ÐŸÐºÐ°Ð·Ð°ÑÑ. Ð­ÑÐŸ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÐŸÐŒÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐŸÐŒÑ ÐžÐœÑÐµÑÑÐµÐ¹ÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐžÐŽÑÐž Ð² ÐœÐŸÐ³Ñ Ñ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ°ÐŒÐž Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐŒ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐž.</Text>
+<Figure id="getting_ready_to_create_new_collection">
+<Title>
+<Text id="236">ÐÐŸÐŽÐ³ÐŸÑÐŸÐ²ÐºÐ° Ðº ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<File width="407" height="318" url="images/User_Fig_14.png"/>
+</Figure>
+<Figure id="previewing_the_newly_built_collection">
+<Title>
+<Text id="237">ÐÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÑÐ¹ Ð¿ÑÐŸÑÐŒÐŸÑÑ ÐœÐµÐŽÐ°Ð²ÐœÐŸ ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<File width="407" height="291" url="images/User_Fig_15.png"/>
+</Figure>
+</Content>
+</Subsection>
+<Subsection id="building_the_collection">
+<Title>
+<Text id="238">ÐÐŸÑÑÑÐŸÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="239">ÐÐ°ÐœÐµÐ»Ñ Â«Ð¡ÐŸÐ·ÐŽÐ°ÑÑÂ» (ÑÐžÑ.14) ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐŸÑÐœÐŸÐ²Ð°ÐœÐœÐŸÐ¹ ÐœÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°Ñ
+ Ðž Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐ»Ð°Ð²ÐœÑÑ ÐœÐ°Ð³ÑÑÐ·ÐºÑ Ð² ÑÑÐŸÐ¹ ÑÐ°Ð±ÐŸÑÐµ ÐœÐµÑÐµÑ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone. ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐ¿ÑÐ°Ð²Ð»ÑÐµÑ ÑÑÐžÐŒ Ð²ÐœÐµÑÐœÐžÐŒ Ð¿ÑÐŸÑÐµÑÑÐŸÐŒ ÑÐµÑÐµÐ· Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÑÐ¹ ÑÑÐŽ ÑÐºÑÐ°ÐœÐŸÐ², ÐºÐ°Ð¶ÐŽÑÐ¹ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ ÐžÐŒÐµÐµÑ ÐŽÐµÐ»ÐŸ Ñ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ°ÐŒÐž, ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÑÑÐžÐŒÐž ÐŸÑÐŽÐµÐ»ÑÐœÑÐµ ÑÑÐ°Ð¿Ñ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ.</Text>
+<Text id="240">ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐœÐ°Ð±Ð»ÑÐŽÐ°ÐµÑ Ð¿ÑÐŸÑÐµÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ, Ñ
+ÐŸÑÑ ÐŸÐºÐœÐŸ, ÐºÐŸÑÐŸÑÐŸÐµ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐµ ÑÐŸÐ»ÑÐºÐŸ ÑÐµÐºÑÑÐŸÐ²ÑÑ Ð¿ÑÐŸÐŽÑÐºÑÐžÑ, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÑ Greenstone Ð¿ÑÑÐµÐŒ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž ÑÐºÑÐžÐ¿ÑÐŸÐ², ÑÑÑÐŸÑÑÐžÑ
+ ÐžÐœÐŽÐµÐºÑ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ, ÐœÐŸ ÑÐ°ÐºÐ¶Ðµ Ðž Ð»ÐžÐœÐµÐ¹ÐºÐž Ð¿ÑÐŸÐŽÐ²ÐžÐ¶ÐµÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÑÑÐµÐ¿ÐµÐœÑ Ð·Ð°Ð²ÐµÑÑÐµÐœÐœÐŸÑÑÐž ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐºÑÐžÐ¿ÑÐ°.</Text>
+<Text id="241">ÐÐ° ÑÐžÑ.14 Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ Ð²ÐžÐŽ Â«Ð¡ÐŸÐ·ÐŽÐ°ÑÑÂ». Ð¡Ð²ÐµÑÑ
+Ñ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŸÐ¿ÑÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¿ÑÐžÐŒÐµÐœÐµÐœÑ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ. ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð²ÑÐ±ÐžÑÐ°ÐµÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŽÐ»Ñ Ð²ÑÐ±ÑÐ°ÐœÐœÐŸÐ³ÐŸ Ð²Ð°ÑÐžÐ°ÐœÑÐ°. Ð­ÑÐŸÑ ÑÐžÑÑÐœÐŸÐº ÐžÐ»Ð»ÑÑÑÑÐžÑÑÐµÑ Ð²ÑÐ¿Ð»ÑÐ²Ð°ÑÑÐžÐµ Â«ÐžÐœÑÑÑÑÐŒÐµÐœÑÑ Ð¿ÐŸÐŽÑÐºÐ°Ð·ÐºÐžÂ», ÐºÐŸÑÐŸÑÑÐµ ÑÐ²Ð»ÑÑÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž Ð¿ÐŸ Ð²ÑÐµÐŒÑ ÐžÐœÑÐµÑÑÐµÐ¹ÑÑ, ÑÑÐŸÐ±Ñ ÐŸÐ±ÑÑÑÐœÐžÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ°. Ð ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÐµÐŒÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð²ÑÐ±ÐžÑÐ°ÐµÑ ÑÑÐŸÐ²ÐµÐœÑ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÑÑÐž ÐŽÐ»Ñ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž,  Ðž ÐžÐœÑÑÑÑÐŒÐµÐœÑ Ð¿ÐŸÐŽÑÐºÐ°Ð·ÐºÐž ÑÐŸÐŸÐ±ÑÐ°ÐµÑ, ÑÑÐŸ ÐŸÐœ ÑÐ²Ð»ÑÐµÑÑÑ ÑÐžÑÐ»ÐŸÐŒ ÐŒÐµÐ¶ÐŽÑ 0 Ðž 3, ÐºÐŸÑÐŸÑÑÐµ ÐžÐœÑÐŸÑÐŒÐžÑÑÑÑ ÐŸ ÑÐŸÐŒ, ÐºÐ°Ðº ÐŒÐœÐŸÐ³ÐŸ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐŸ Ð¿ÑÐŸÑÐµÑÑÐµ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÐœÐŸ Ð² ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐŒ Ð¿ÐŸÑÐŸÐºÐµ: Â«0Â» ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ ÐœÐµÐŒÐœÐŸÐ³ÐŸ, Ð° Â«3Â» - Ð±ÐŸÐ»ÑÑÐŸÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ.</Text>
+<Text id="242">ÐÑÐ»Ðž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐŽÐŸÐ²Ð»ÐµÑÐ²ÐŸÑÐµÐœ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐ°ÐŒÐž, ÐŸÐœ ÑÐµÐ»ÐºÐ°ÐµÑ ÐœÐ° Â«Ð¡ÐŸÐ·ÐŽÐ°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÂ». Greenstone ÐœÐµÐ¿ÑÐµÑÑÐ²ÐœÐŸ Ð²ÑÐŽÐ°ÐµÑ ÑÐµÐºÑÑ, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð¿ÑÐŸÐŽÐ²ÐžÐ¶ÐµÐœÐžÐµ, Ðž ÐŸÐœ ÐžÐŽÐµÑ ÐœÐ°ÑÑÐŽÑ Ñ Ð±ÐŸÐ»ÐµÐµ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐ²ÐœÐŸÐ¹ Ð»ÐžÐœÐµÐ¹ÐºÐŸÐ¹ Ð¿ÑÐŸÐŽÐ²ÐžÐ¶ÐµÐœÐžÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="previewing">
+<Title>
+<Text id="243">ÐÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÑÐ¹ Ð¿ÑÐŸÑÐŒÐŸÑÑ</Text>
+</Title>
+<Content>
+<Text id="244">ÐºÐœÐŸÐ¿ÐºÐ° <i>ÐÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°</i> (ÑÐžÑ.14) ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÐ°Ñ Ð±ÑÐ»Ð° ÑÐŸÐ·ÐŽÐ°ÐœÐ°. ÐÑÐž ÐœÐ°Ð¶Ð°ÑÐžÐž ÐœÐ° ÑÑÑ ÐºÐœÐŸÐ¿ÐºÑ ÐŸÑÐºÑÑÐ²Ð°ÐµÑÑÑ Ð²ÐµÐ±-Ð±ÑÐ°ÑÐ·ÐµÑ Ñ ÐŽÐŸÐŒÐ°ÑÐœÐµÐ¹ ÑÑÑÐ°ÐœÐžÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (Ð ÐžÑÑÐœÐŸÐº 15).  ÐÑÐ°ÐºÑÐžÑÐµÑÐºÐž, Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÑÐ¹ Ð¿ÑÐŸÑÐŒÐŸÑÑ ÑÐ°ÑÑÐŸ ÐŸÐ±ÐœÐ°ÑÑÐ¶ÐžÐ²Ð°ÐµÑ ÐœÐµÐŽÐŸÑÑÐ°ÑÐºÐž Ð² Ð¿ÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐ»Ðž Ð² ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÑÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, Ðž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐ°ÑÑÐŸ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑÑÑ Ðº Ð±ÐŸÐ»ÐµÐµ ÑÐ°ÐœÐœÐžÐŒ ÑÑÐ°Ð¿Ð°ÐŒ ÐŽÐ»Ñ ÐžÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ ÐžÑ
+. Ð­ÑÐ° ÐºÐœÐŸÐ¿ÐºÐ° ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ Ð°ÐºÑÐžÐ²ÐœÐŸÐ¹, ÐºÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð±ÑÐ»Ð° ÑÐŸÐ·ÐŽÐ°ÐœÐ°. ÐÐµÐŽÐ°Ð²ÐœÐŸ ÑÐŸÐ·ÐŽÐ°ÐœÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð±ÑÐŽÐµÑ ÑÐ°ÐºÐ¶Ðµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÐœÐ° ÐÐ°ÑÐµÐ¹ ÑÑÐ°ÑÑÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ Greenstone ÐºÐ°Ðº ÐŸÐŽÐœÐ° ÐžÐ· ÐŸÐ±ÑÑÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹.</Text>
+</Content>
+</Subsection>
+<Subsection id="help">
+<Title>
+<Text id="245">ÐÐŸÐŒÐŸÑÑ</Text>
+</Title>
+<Content>
+<Text id="246">ÐÐžÐ°Ð»ÐŸÐ³ÐŸÐ²Ð°Ñ Ð¿ÐŸÐŒÐŸÑÑ Ð²ÑÐµÐ³ÐŽÐ° ÐŽÐŸÑÑÑÐ¿ÐœÐ°. ÐÐœÐ° Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑÑÑ Ð¿ÑÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž Ð¿ÑÐœÐºÑÐ° Â«ÐÐŸÐŒÐŸÑÑÂ» Ð² Ð¿ÑÐ°Ð²ÐŸÐ¹ ÑÑÐŸÑÐŸÐœÐµ Ð³Ð»Ð°Ð²ÐœÐŸÐ¹ Ð»ÐžÐœÐµÐ¹ÐºÐž ÐŒÐµÐœÑ ÐœÐ°Ð²ÐµÑÑ
+Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐžÑÑÐœÐºÐ°. ÐÐœÐ° ÐŸÑÐºÑÑÐ²Ð°ÐµÑ ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐž ÑÑÑÑÐºÑÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ ÑÐµÐºÑÑÐŸÐ²ÑÐ¹ ÑÐ°Ð¹Ð» Ð¿ÐŸÐŒÐŸÑÐž; ÐŸÐ±ÑÑÑÐœÐµÐœÐžÐµ Ð²ÑÑÐµÐºÐ°ÐµÑ ÐžÐ· ÑÐµÐºÑÑÐµÐ³ÐŸ ÐºÐŸÐœÑÐµÐºÑÑÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð¿ÑÐž Ð¿ÐŸÐŽÑÐ²ÐµÑÐžÐ²Ð°ÐœÐžÐž ÑÐ°Ð·ÐŽÐµÐ»Ð°, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÐµÑ ÑÐµÐºÑÑÐµÐ¹ ÑÑÐ°ÐŽÐžÐž Ð²Ð·Ð°ÐžÐŒÐŸÐŽÐµÐ¹ÑÑÐ²ÐžÑ. ÐÑÐŸÐŒÐµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐŸÑÐŒÐµÑÐµÐœÐŸ Ð²ÑÑÐµ, Ð²ÑÑÐºÐžÐ¹ ÑÐ°Ð·, ÐºÐŸÐ³ÐŽÐ° ÐŒÑÑÑ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐœÐ°ÐŽ Ð»ÑÐ±ÑÐŒ ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÑÐŒ ÐŸÐ±ÑÐµÐºÑÐŸÐŒ, Ð²ÑÐ¿Ð»ÑÐ²Ð°ÐµÑ ÐŒÐ°Ð»ÐµÐœÑÐºÐŸÐµ ÐŸÐºÐœÐŸ, ÑÑÐŸÐ±Ñ ÐŽÐ°ÑÑ ÑÐµÐºÑÑ Ð¿ÐŸÐŽÑÐºÐ°Ð·ÐºÐž, ÐºÐ°Ðº ÑÑÐŸ Ð±ÑÐ»ÐŸ ÐžÐ»Ð»ÑÑÑÑÐžÑÐŸÐ²Ð°ÐœÐŸ ÐŸÐºÐŸÐ»ÐŸ ÐŸÑÐœÐŸÐ²Ð°ÐœÐžÑ ÐœÐ° ÑÐžÑ.14.</Text>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="librarian_interface_user_guide">
+<Title>
+<Text id="247">Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ</Text>
+</Title>
+<Content>
+<Subsection id="starting_off">
+<Title>
+<Text id="248">ÐÐŸ ÑÑÐ°ÑÑÐ°</Text>
+</Title>
+<Content>
+<Text id="249">Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÑÐ°ÑÑÐºÐ°Ð·Ð°ÐœÐŸ, ÐºÐ°Ðº ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ, Ð·Ð°Ð³ÑÑÐ¶Ð°ÑÑ Ðž ÑÐŽÐ°Ð»ÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. </Text>
+<Part id="creating_a_new_collection">
+<Title>
+<Text id="250">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="251">Ð§ÑÐŸÐ±Ñ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐŸÑÐºÑÐŸÐ¹ÑÐµ ÐŒÐµÐœÑ "Ð€Ð°Ð¹Ð»" Ðž Ð²ÑÐ±ÐµÑÐžÑÐµ Ð² ÐœÑÐŒ Ð¿ÑÐœÐºÑ "ÐÐŸÐ²ÑÐ¹...". ÐÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐ»Ñ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐŸÐ±ÑÐ·Ð°ÑÐµÐ»ÑÐœÐŸ Ð·Ð°Ð¿ÐŸÐ»ÐœÐµÐœÑ, ÐœÐŸ ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð·Ð°ÐŒÐµÐœÐžÑÑ ÐžÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÑ Ð¿ÐŸÐ·Ð¶Ðµ, ÐµÑÐ»Ðž ÐÑ Ð² ÑÑÐŸÐŒ ÐœÑÐ¶ÐŽÐ°ÐµÑÐµÑÑ Ñ ÑÐŸÑÐºÐž Ð·ÑÐµÐœÐžÑ ÐŽÐžÐ·Ð°Ð¹ÐœÐ°. </Text>
+<Text id="252">ÐÐ°Ð³Ð»Ð°Ð²ÐžÐµ "ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ/Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž" - ÑÑÐŸ ÑÐµÐºÑÑ, ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐœÑÐ¹ ÐœÐ°Ð²ÐµÑÑ
+Ñ ÐŽÐŸÐŒÐ°ÑÐœÐµÐ¹ ÑÑÑÐ°ÐœÐžÑÑ ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐœÐŸ ÐŒÐŸÐ¶ÐµÑ ÐžÐŒÐµÑÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐ»ÑÐœÑÑ ÐŽÐ»ÐžÐœÑ. </Text>
+<Text id="253">"ÐÐ¿ÐžÑÐ°ÐœÐžÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ" ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð¿ÑÐµÐŽÑÑÐ°Ð²ÐžÑÑ ÐºÐ°Ðº ÐŒÐŸÐ¶ÐœÐŸ ÐŽÐµÑÐ°Ð»ÑÐœÐµÐµ ÑÐŸ,ÐŸ ÑÑÐŒ ÑÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐºÐ»Ð°Ð²ÐžÑÑ [Enter] ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ,ÑÑÐŸÐ±Ñ ÑÐ°Ð·Ð±ÐžÑÑ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐœÐ° Ð¿Ð°ÑÐ°Ð³ÑÐ°ÑÑ. </Text>
+<Text id="254">ÐÐ°ÐºÐŸÐœÐµÑ ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ, ÐŽÐŸÐ»Ð¶ÐœÐ° Ð»Ðž ÐœÐŸÐ²Ð°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐŒÐµÑÑ ÑÐŸÑ Ð¶Ðµ ÑÐ°ÐŒÑÐ¹ Ð²ÐžÐŽ Ðž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÑÐŸ Ðž ÑÑÑÐµÑÑÐ²ÑÑÑÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐžÐ»Ðž Ð¶Ðµ ÐœÐ°ÑÐ°ÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ "ÐÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ". </Text>
+<Text id="255">Ð©ÐµÐ»ÐºÐœÐžÑÐµ "OK", ÑÑÐŸÐ±Ñ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÑÐ»Ðž ÐÑ Ð²ÑÐ±ÑÐ°Ð»Ðž "ÐÐŸÐ²Ð°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ", ÑÐŸ ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ Ð²Ð²ÐµÑÑÐž ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐžÑ
+ Ð² ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ Ð±ÐŸÐ»ÑÑÐµ,ÑÐµÐŒ ÐŸÐŽÐœÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ, Ð° ÐŒÐŸÐ¶ÐµÑÐµ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐŽÑÑÐ³ÐžÐµ Ð¿ÐŸÐ·Ð¶Ðµ.</Text>
+<Text id="256">ÐÐ°Ð¶Ð°ÑÐžÐµ ÐºÐ»Ð°Ð²ÐžÑÐž "ÐÑÐŒÐµÐœÐžÑÑ" ÐœÐµÐŒÐµÐŽÐ»ÐµÐœÐœÐŸ Ð²ÐŸÐ·Ð²ÑÐ°ÑÐ°ÐµÑ ÐÐ°Ñ Ðº Ð³Ð»Ð°Ð²ÐœÐŸÐŒÑ ÑÐºÑÐ°ÐœÑ.</Text>
+</Content>
+</Part>
+<Part id="saving_the_collection">
+<Title>
+<Text id="257">Ð¡ÐŸÑ
+ÑÐ°ÐœÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="258">Ð¡ÐŸÑ
+ÑÐ°ÐœÑÐ¹ÑÐµ ÐÐ°ÑÑ ÑÐ°Ð±ÐŸÑÑ ÑÐµÐ³ÑÐ»ÑÑÐœÐŸ, ÐŸÑÐºÑÑÐ²Ð°Ñ ÐŒÐµÐœÑ "Ð€Ð°Ð¹Ð»" Ðž Ð²ÑÐ±ÐžÑÐ°Ñ Ð² ÐœÑÐŒ Ð¿ÑÐœÐºÑ "Ð¡ÐŸÑ
+ÑÐ°ÐœÐžÑÑ". Ð¡ÐŸÑ
+ÑÐ°ÐœÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž - ÑÑÐŸ ÐœÐµ ÑÐŸ Ð¶Ðµ ÑÐ°ÐŒÐŸÐµ, ÐºÐ°Ðº ÑÐŽÐµÐ»Ð°ÑÑ ÐµÑ Ð³ÐŸÑÐŸÐ²ÐŸÐ¹ Ðº ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ Ð² Greenstone. (see Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž).</Text>
+<Text id="259">ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð·Ð°ÑÐžÑÐ°ÐµÑ ÐÐ°ÑÑ ÑÐ°Ð±ÐŸÑÑ Ð¿ÑÑÑÐŒ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐžÑ ÐµÑ Ð²ÑÑÐºÐžÐ¹ ÑÐ°Ð·, ÐºÐŸÐ³ÐŽÐ° ÐÑ Ð²ÑÑ
+ÐŸÐŽÐžÑÐµ ÐžÐ· Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐžÐ»Ðž Ð·Ð°Ð³ÑÑÐ¶Ð°ÐµÑÐµ ÐŽÑÑÐ³ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ.</Text>
+<Text id="260">Ð¡ÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð·Ð°Ð¿ÐžÑÑÐ²Ð°ÑÑÑÑ Ð² ÑÐ°Ð¹Ð», ÐžÐŒÐµÑÑÐžÐ¹ ÑÐŸ Ð¶Ðµ ÐžÐŒÑ, ÑÑÐŸ Ðž ÐžÐŒÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ñ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµÐŒ ".col", Ðž ÑÐ°ÑÐ¿ÐŸÐ»Ð°Ð³Ð°ÐµÑÑÑ Ð² Ð¿Ð°Ð¿ÐºÐµ ÑÐŸÐ³ÐŸ Ð¶Ðµ ÐœÐ°ÐžÐŒÐµÐœÐŸÐ²Ð°ÐœÐžÑ, ÑÑÐŸ Ðž Ð¿Ð°Ð¿ÐºÐ° "collect" Ð¿ÑÐž ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Greenstone.</Text>
+</Content>
+</Part>
+<Part id="opening_an_existing_collection">
+<Title>
+<Text id="261">ÐÑÐºÑÑÑÐžÐµ ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="262">ÐÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ ÐŸÑÐºÑÑÑÑ ÑÑÑÐµÑÑÐ²ÑÑÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, Ð²ÑÐ±ÐµÑÐžÑÐµ "ÐÑÐºÑÑÑÑ" Ð² ÐŒÐµÐœÑ "Ð€Ð°Ð¹Ð»",ÑÑÐŸÐ±Ñ Ð±ÑÑÑÑÐŸ Ð¿ÐµÑÐµÐ¹ÑÐž Ðº ÐÑÐºÑÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐŸÑÐ²Ð»ÑÐµÑÑÑ ÑÐ¿ÐžÑÐŸÐº ÐÐ°ÑÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð² Greenstone. ÐÑÐ±ÐµÑÐžÑÐµ ÐŸÐŽÐœÑ,ÑÑÐŸÐ±Ñ ÑÐ²ÐžÐŽÐµÑÑ ÐµÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ,Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "OÑÐºÑÑÑÑ", ÑÑÐŸÐ±Ñ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ ÐµÐµ. ÐÑÐ»Ðž ÐÑ ÐžÑÐžÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð²ÐœÐµ Ð¿Ð°Ð¿ÐºÐž "Ð¡ollect Greenstone",ÑÐŸ ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð Ð°ÑÑÐŒÐŸÑÑÐµÑÑ" ÐŽÐ»Ñ Ð²ÑÐ·ÐŸÐ²Ð° ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÑÐ°Ð¹Ð»ÐŸÐ².</Text>
+<Text id="263">Ð ÑÐ»ÑÑÐ°Ðµ, ÐµÑÐ»Ðž Ð±ÐŸÐ»ÑÑÐµ ÑÐµÐŒ ÐŸÐŽÐœÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Greenstone Ð²Ð²ÐŸÐŽÐžÑÑÑ ÐŸÐŽÐœÐŸÐ²ÑÐµÐŒÐµÐœÐœÐŸ, ÑÐµÐ»ÐµÐ²Ð°ÐœÑÐœÑÐµ ÐŽÐžÑÐµÐºÑÑÐžÐž "Ð·Ð°ÐºÑÑÑÑ",ÑÑÐŸÐ±Ñ Ð¿ÑÐµÐŽÐŸÑÐ²ÑÐ°ÑÐžÑÑ ÐœÐ°Ð»ÐŸÐ¶ÐµÐœÐžÐµ.ÐÑÐž ÐŸÑÐºÑÑÑÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐµÐ±ÐŸÐ»ÑÑÐŸÐ¹ Ð²ÑÐµÐŒÐµÐœÐœÑÐ¹ Ð±Ð»ÐŸÐºÐžÑÑÑÑÐžÐ¹ ÑÐ°Ð¹Ð» ÑÐŸÐ·ÐŽÐ°ÐµÑÑÑ Ð² ÐµÑ Ð¿Ð°Ð¿ÐºÐµ.ÐÐµÑÐµÐŽ ÐŸÑÐºÑÑÑÐžÐµÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑ Ð¿ÑÐŸÐ²ÐµÑÐºÑ,ÑÑÐŸÐ±Ñ ÑÐ±ÐµÐŽÐžÑÑÑÑ,ÑÑÐŸ ÐœÐžÐºÐ°ÐºÐžÑ
+ Ð±Ð»ÐŸÐºÐžÑÑÑÑÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² ÐœÐµ ÑÑÑÐµÑÑÐ²ÑÐµÑ. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐºÐ°Ð·Ð°ÑÑ,Ð·Ð°ÐºÑÑÑÐ° Ð»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, Ð¿ÐŸ ÑÐ²ÐµÑÑ ÐµÑ ÐžÐºÐŸÐœÐºÐž:Ð·ÐµÐ»ÑÐœÑÐ¹ - ÐŽÐ»Ñ ÐœÐŸÑÐŒÐ°Ð»ÑÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž,ÐºÑÐ°ÑÐœÑÐ¹ - ÐŽÐ»Ñ Ð·Ð°ÐºÑÑÑÐŸÐ¹. ÐÐŽÐœÐ°ÐºÐŸ,ÐºÐŸÐ³ÐŽÐ° ÐžÐ· ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Ð²ÑÑ
+ÐŸÐŽÑÑ Ð¿ÑÐµÐ¶ÐŽÐµÐ²ÑÐµÐŒÐµÐœÐœÐŸ, Ð±Ð»ÐŸÐºÐžÑÑÑÑÐžÐ¹ ÑÐ°Ð¹Ð» ÐžÐœÐŸÐ³ÐŽÐ° ÐŸÑÑÐ°ÐµÑÑÑ ÐœÐ° ÐŒÐµÑÑÐµ. ÐÐŸÐ³ÐŽÐ° ÐÑ ÐŸÑÐºÑÑÐ²Ð°ÐµÑÐµ ÑÐ°ÐºÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Ð·Ð°Ð¿ÑÐ°ÑÐžÐ²Ð°ÐµÑ,Ñ
+ÐŸÑÐžÑÐµ Ð»Ðž ÐÑ "ÑÐºÑÐ°ÑÑÑ" ÐµÐ³ÐŸ ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ. ÐÐžÐºÐŸÐ³ÐŽÐ° ÐœÐµ ÐŽÐµÐ»Ð°Ð¹ÑÐµ ÑÑÐŸÐ³ÐŸ,ÐµÑÐ»Ðž ÐºÑÐŸ-ÑÐŸ ÐµÑÐµ Ð² ÑÐŸ Ð¶Ðµ ÑÐ°ÐŒÐŸÐµ Ð²ÑÐµÐŒÑ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ. </Text>
+<Text id="264">ÐÐŸÐ³ÐŽÐ° ÐÑ ÐŸÑÐºÑÑÐ²Ð°ÐµÑÐµ ÐºÐŸÐ»ÐµÐºÑÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐ° ÐœÐµ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Greenstone, ÐÐ°Ñ Ð¿ÐŸÐ¿ÑÐŸÑÑÑ Ð²ÑÐ±ÑÐ°ÑÑ ÐœÐ°Ð±ÐŸÑ (ÐžÐ»Ðž ÐœÐ°Ð±ÐŸÑÑ) ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÑÐ»Ðž ÐœÐž ÐŸÐŽÐžÐœ ÐœÐµ ÐŸÑÐŸÐ±ÑÐ°Ðœ, Ð»ÑÐ±ÑÐµ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð±ÑÐŽÑÑ ÐžÐ³ÐœÐŸÑÐžÑÐŸÐ²Ð°ÑÑÑÑ. ÐÐœÐ°ÑÐµ, ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð±ÑÐŽÑÑ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÑ ÑÐ°Ðº Ð¶Ðµ, ÐºÐ°Ðº Ðž ÐºÐŸÐ³ÐŽÐ° ÐÑ Ð¿ÐµÑÐµÑÑÐ³ÐžÐ²Ð°ÐµÑÐµ Ð² ÑÐ°Ð¹Ð»Ñ Ñ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐŒÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž. ÐÑÐŸÑÐµÑÑ ÐŸÐ¿ÐžÑÐ°Ðœ Ð² ÐÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐž Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð²ÑÐ±ÑÐ°ÐœÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. </Text>
+</Content>
+</Part>
+<Part id="deleting_collections">
+<Title>
+<Text id="265">Ð£ÐŽÐ°Ð»ÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</Title>
+<Content>
+<Text id="266">ÐÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÐœÐµÐžÐ·ÐŒÐµÐœÐœÐŸ ÑÐŽÐ°Ð»ÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐ· ÐžÐœÑÑÐ°Ð»ÑÑÐžÐŸÐœÐœÐŸÐ¹ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Greenstone, Ð²ÑÐ±ÐµÑÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ..." ÐžÐ· ÐŒÐµÐœÑ "Ð€Ð°Ð¹Ð»". ÐÑÐºÑÐŸÐµÑÑÑ ÑÐ¿ÐžÑÐŸÐº Ð²ÑÐµÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Greenstone. ÐÑÐ±ÐµÑÐžÑÐµ ÐœÑÐ¶ÐœÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÐ° ÐµÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ, Ð¿ÐŸÑÐ»Ðµ ÑÑÐŸÐ³ÐŸ Ð¿ÐŸÑÑÐ°Ð²ÑÐµ Ð³Ð°Ð»ÐŸÑÐºÑ Ð² Ð¿ÑÐœÐºÑÐµ Ð²ÐœÐžÐ·Ñ ÐŽÐžÐ°Ð»ÐŸÐ³Ð° Ðž ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° "Ð£ÐŽÐ°Ð»ÐžÑÑ", ÑÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. Ð­ÑÐ° ÐŸÐ¿ÐµÑÐ°ÑÐžÑ Ð±ÐµÐ·Ð²ÐŸÐ·Ð²ÑÐ°ÑÐœÐ°, Ð¿ÐŸÑÑÐŸÐŒÑ Ð¿ÑÐŸÐ²ÐµÑÑÑÐµ Ð²ÐœÐžÐŒÐ°ÑÐµÐ»ÑÐœÐŸ, ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸ Ð»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐœÐµÐœÑÐ¶ÐœÐ°! </Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="downloading_files_from_the_internet">
+<Title>
+<Text id="267">ÐÐ°Ð³ÑÑÐ·ÐžÑÑ ÑÐ°Ð¹Ð»Ñ ÐžÐ· ÐžÐœÑÐµÑÐœÐµÑ</Text>
+</Title>
+<Content>
+<Text id="268">ÐÐžÐŽ "ÐÐµÑÐºÐ°Ð»ÐŸ" Ð¿ÐŸÐŒÐŸÐ¶ÐµÑ Ð²Ð°ÐŒ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐžÐ· ÐÐœÑÐµÑÐœÐµÑÐ°. ÐÐ°ÐœÐœÐ°Ñ ÑÐµÐºÑÐžÑ ÐŸÐ±ÑÑÑÐœÑÐµÑ Ð¿ÑÐŸÑÐµÑÑ Ð·ÐµÑÐºÐ°Ð»ÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð² ÐÐœÑÐµÑÑÐµÐ¹ÑÐµ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ. </Text>
+<Part id="the_download_view">
+<Title>
+<Text id="269">ÐÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐÐ°Ð³ÑÑÐ·ÐžÑÑ</Text>
+</Title>
+<Content>
+<Text id="270">Ð­ÑÐ° ÑÐµÐºÑÐžÑ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÐºÐ°Ðº ÐºÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÑÑ Ð·Ð°ÐŽÐ°ÑÑ Ðž ÐºÐŸÐœÑÑÐŸÐ»Ñ Ð¿ÑÐŸÑÐµÑÑÐ° Ð·Ð°Ð³ÑÑÐ·ÐºÐž. ÐÐŸÑÑÑÐ¿ Ðº Ð¿ÑÐŸÑÐŒÐŸÑÑÑ "ÐÐ°Ð³ÑÑÐ·ÐžÑÑ" ÐœÐ°Ð¶Ð°ÑÐµÐŒ ÑÑÐŸÐ¹ Ð·Ð°ÐºÐ»Ð°ÐŽÐºÐž. ÐÐµÑÑ
+ÐœÑÑ Ð¿ÐŸÐ»ÐŸÐ²ÐžÐœÐ° ÑÐºÑÐ°ÐœÐ° Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐºÐŸÐœÑÑÐŸÐ»Ñ Ð·Ð°Ð³ÑÑÐ·ÐºÐž. ÐÐžÐ¶ÐœÑÑ Ð¿ÐŸÐ»ÐŸÐ²ÐžÐœÐ° Ð² ÐœÐ°ÑÐ°Ð»Ðµ Ð¿ÑÑÑÐ°, ÐŸÐŽÐœÐ°ÐºÐŸ Ð¿ÐŸÐºÐ°Ð¶ÐµÑ Ð¿ÐµÑÐµÑÐµÐœÑ ÐŸÐ¶ÐžÐŽÐ°ÐµÐŒÑÑ
+ Ðž Ð·Ð°ÐºÐŸÐœÑÐµÐœÐœÑÑ
+ Ð·Ð°Ð³ÑÑÐ·ÐŸÐº. </Text>
+<Text id="271">Ð€Ð°Ð¹Ð»Ñ Ð·Ð°Ð³ÑÑÐ¶ÐµÐœÐœÑÐµ Ð² Ð¿Ð°Ð¿ÐºÑ ÑÐ°Ð±ÐŸÑÐµÐ³ÐŸ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ð° ÐœÐ°Ð·ÑÐ²Ð°ÑÑÑÑ "ÐÐ°Ð³ÑÑÐ¶Ð°ÐµÐŒÑÐµ ÑÐ°Ð¹Ð»Ñ", Ðž ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐ° Ð²ÑÐµÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž Ð¿ÐŸÑÑÑÐŸÐµÐœÐœÑÐŒÐž Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐÐœÑÐµÑÑÐµÐ¹ÑÐ° ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ. Ð€Ð°Ð¹Ð»Ñ Ð² ÑÑÐŸÐ¹ ÐŸÐ±Ð»Ð°ÑÑÐžÐžÐŒÐµÐœÑÑÑÑÑ Ð¿ÐŸ ÐžÑ
+ Ð¿ÐŸÐ»ÐœÐŸÐŒÑ URL Ð°ÐŽÑÐµÑÑ. Ð¡ÐŸÐ·ÐŽÐ°ÐµÑÑÑ ÐœÐŸÐ²Ð°Ñ Ð¿Ð°Ð¿ÐºÐ° ÐœÐ° ÐºÐ°Ð¶ÐŽÐŸÐŒ Ñ
+ÐŸÑÑÐµ, ÐœÐ°ÑÐ»ÐµÐŽÑÐµÐŒÐ°Ñ ÐŽÑÑÐ³ÐžÐŒÐž ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÑÐ°Ð³ÐŒÐµÐœÑÐ° Ð¿ÑÑÐž. Ð­ÑÐŸ Ð³Ð°ÑÐ°ÐœÑÐžÑÑÐµÑ ÐŸÑÐ»ÐžÑÐžÐµ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð°. </Text>
+<Text id="272">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ Ð¿ÐµÑÐ²ÑÐ¹ ÐžÐ· ÐºÐŸÐœÑÑÐŸÐ»ÐžÑÑÐµÐŒÑÑ
+ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐ¹ Ð·Ð°Ð³ÑÑÐ·ÐŸÐº, "ÐÑÑ
+ÐŸÐŽÐœÑÐ¹ URL", ÑÑÐŸÐ±Ñ Ð²Ð²ÐµÑÑÐž URL Ð°ÐŽÑÐµÑ Ð² ÑÐµÐ»ÐµÐ²ÐŸÐ¹ ÑÐµÑÑÑÑ. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐºÐŸÐœÑÑÐŸÐ»Ñ "ÐÐ»ÑÐ±ÐžÐœÑ ÐÐ°Ð³ÑÑÐ·ÐºÐž" ÐŽÐ»Ñ ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÐžÑ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²Ð° Ð³ÐžÐ¿ÐµÑÑÑÑÐ»ÐŸÐº ÐŽÐ»Ñ Ð·Ð°Ð³ÑÑÐ·ÐºÐž: Ð£ÑÑÐ°ÐœÐŸÐ²ÐžÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ 0 ÐŽÐ»Ñ Ð·Ð°Ð³ÑÑÐ·ÐºÐž ÐŸÐŽÐœÐŸÐ¹ Ð²ÐµÐ± ÑÑÑÐ°ÐœÐžÑÑ; Ð·ÐœÐ°ÑÐµÐœÐžÐµ 1 ÑÑÐŸÐ±Ñ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ ÐŸÐŽÐœÑ ÑÑÑÐ°ÐœÐžÑÑ Ðž Ð²ÑÐµ ÑÑÑÐ°ÐœÐžÑÑ ÑÐ²ÑÐ·Ð°ÐœÐœÑÐµ Ñ ÐœÐµÐ¹ . Ð¿ÑÐµÐŽÐµÐ» Ð³Ð»ÑÐ±ÐžÐœÑ ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÐµÑÑÑ ÑÐŸÐ»ÑÐºÐŸ ÐœÐ° html ÑÑÑÐ°ÐœÐžÑÑ. Ð¡Ð»ÐµÐŽÑÐ¹ÑÐµÐµ, Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐ° ÑÑÑÐ°ÐœÐŸÐ²ÐºÐ° ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ "Ð³Ð°Ð»ÐŸÑÐµÐº", ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ, ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ ÑÑÐŸÐ±Ñ Ð²ÐºÐ»ÑÑÐžÑÑ ÑÐºÐ°Ð·Ð°ÐœÐœÑÑ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÑ ÐºÐŸÐœÐºÑÐµÑÐœÐŸÐ¹ Ð·Ð°Ð³ÑÑÐ·ÐºÐž. ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐ°, ÐœÐ°Ð¶ÐŒÐžÑÐµ "ÐÐ°Ð³ÑÑÐ·ÐºÐ°", ÑÑÐŸÐ±Ñ ÐœÐ°ÑÐ°ÑÑ ÐœÐŸÐ²ÑÑ Ð·Ð°Ð³ÑÑÐ·ÐºÑ. ÐÑÑÑ ÐŽÐ²Ðµ ÐŽÑÑÐ³ÐžÑ
+ ÐºÐœÐŸÐ¿ÐºÐž: Ð² ÑÐ°Ð·ÐŽÐµÐ»Ðµ "ÐÐ°ÑÑÑÐŸÐ¹ÐºÐž", ÐºÐŸÑÐŸÑÑÐµ ÑÐ²ÑÐ·Ð°ÐœÑ Ñ ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐŒ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÑÐ²ÑÐ·Ðž, Ð³ÐŽÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ Ð¿ÑÐŸÐºÑÐž ÑÐµÑÐ²ÐµÑÐ° ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐžÐ·ÐŒÐµÐœÐµÐœÑ; Ðž "ÐÑÐžÑÑÐºÐ° ÐÑÑ", ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŽÐ°Ð»ÑÐµÑ Ð²ÑÐµ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð·Ð°Ð³ÑÑÐ¶ÐµÐœÐœÑÐµ ÑÐ°Ð¹Ð»Ñ. </Text>
+<Text id="273">Ð¡Ð¿ÐžÑÐŸÐº Ð·Ð°Ð³ÑÑÐ·ÐºÐž ÐžÐŒÐµÐµÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ Ð·Ð°Ð³ÑÑÐ¶Ð°ÐµÐŒÐŸÐ¹ Ð²ÐµÐ± ÑÑÑÐ°ÐœÐžÑÑ. ÐÐ°Ð¶ÐŽÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐžÐŒÐµÐµÑ ÑÐµÐºÑÑ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÑÑÐžÐ¹ ÐŽÐµÑÐ°Ð»Ðž Ð·Ð°ÐŽÐ°ÑÐž Ð²ÐŒÐµÑÑÐµ Ñ ÐžÐœÐŽÐžÐºÐ°ÑÐŸÑÐŸÐŒ Ð¿ÑÐŸÐ³ÑÐµÑÑÐ° ÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÑÑÑÐžÐŒ ÑÐµÐºÑÑÑÑ ÐŽÐµÑÑÐµÐ»ÑÐœÐŸÑÑÑ. Ð¢ÑÐž ÐºÐœÐŸÐ¿ÐºÐž Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ ÑÐ»ÐµÐ²Ð° ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑ. "ÐÐ°ÑÐ·Ð°" ÐŽÐ»Ñ Ð¿ÑÐžÐŸÑÑÐ°ÐœÐŸÐ²ÐºÐž Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÑÐµÐºÑÑÐµÐ³ÐŸ Ð¿ÑÐŸÑÐµÑÑÐ°. "Ð¡ÐŒÐŸÑÑÐµÑÑ ÐÐŸÐ³Ðž" ÐŸÑÐºÑÑÐ²Ð°ÐµÑ ÐŸÐºÐœÐŸ ÑÐ°Ð¹Ð»Ð° Ð·Ð°Ð³ÑÑÐ·ÐºÐž. "ÐÐ°ÐºÑÑÑÑ" Ð·Ð°Ð²ÐµÑÑÐ°ÐµÑ Ð·Ð°Ð³ÑÑÐ·ÐºÑ Ð·Ð°ÐŽÐ°ÑÐž ÐžÐ· ÑÐ¿ÐžÑÐºÐ°. </Text>
+<Text id="274">Ð¡ÐµÐºÑÐžÑ ÐÐ°ÑÑÑÐŸÐµÐº ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÐºÐ°Ðº ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÐžÐœÑÐµÑÐœÐµÑ ÑÐŸÐµÐŽÐžÐœÐµÐœÐžÐµ ÑÐµÑÐµÐ· Ð¿ÑÐŸÐºÑÐž ÑÐµÑÐ²ÐµÑ. ÐÑÐ»Ðž ÐœÑÐ¶ÐœÐ° ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐ°Ñ Ð°ÑÑÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÑ, Ð¿ÑÐŸÐºÑÐž ÑÐµÑÐ²ÐµÑ Ð·Ð°Ð¿ÑÐŸÑÐžÑ ÐžÐŒÑ Ðž Ð¿Ð°ÑÐŸÐ»Ñ. ÐÐœÑÐµÑÑÐµÐ¹Ñ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ ÐœÐµ ÑÐŸÐ·ÑÐ°ÐœÑÐµÑ Ð¿Ð°ÑÐŸÐ»Ðž ÐŒÐµÐ¶ÐŽÑ ÑÐµÑÑÐžÑÐŒÐž.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="collecting_files_for_your_collection">
+<Title>
+<Text id="275">Ð¡Ð±ÐŸÑ ÑÐ°Ð¹Ð»ÐŸÐ² ÐŽÐ»Ñ ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="276">ÐÑÐ»Ðž ÐÑ ÑÐŸÐ·ÐŽÐ°ÐµÑÐµ ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ,ÑÐŸ Ð²ÐŸÐ·ÐœÐžÐºÐ°ÐµÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÑ Ð²Ð²ÐŸÐŽÐ° Ð² ÐœÐµÐµ ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ².ÐÐœÐž ÐŒÐŸÐ³ÑÑ Ð¿ÐŸÑÑÑÐ¿ÐžÑÑ ÐžÐ· Ð²Ð°ÑÐµÐ³ÐŸ ÐŸÐ±ÑÑÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ð° ÐžÐ· ÐŽÑÑÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Greenstone. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³ÑÑ ÑÐ¶Ðµ ÐžÐŒÐµÑÑ Ð¿ÑÐžÑÐŸÐµÐŽÐžÐœÐµÐœÐœÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ.Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑÑÑ,ÐºÐ°Ðº ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÑÐ°Ð¹Ð»Ñ. </Text>
+<Part id="the_gather_view">
+<Title>
+<Text id="277">ÐÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐœÐ°ÐºÐŸÐ¿ÐžÑÐµÐ»Ñ</Text>
+</Title>
+<Content>
+<Text id="278">Ð­ÑÐŸÑ ÑÐ°Ð·ÐŽÐµÐ» Ð²Ð²ÐŸÐŽÐžÑ Ð² ÐŸÐ±Ð»Ð°ÑÑÑ ÐœÐ°ÐºÐŸÐ¿Ð»ÐµÐœÐžÑ,ÐºÐŸÑÐŸÑÑÑ ÐÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ,ÑÑÐŸÐ±Ñ Ð²ÑÐ±ÑÐ°ÑÑ,ÐºÐ°ÐºÐžÐµ ÑÐ°Ð¹Ð»Ñ Ð²ÐºÐ»ÑÑÐ°ÑÑ Ð² ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÐµÐŒÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ ÐœÐ°ÑÐžÐœÐ°ÐµÑÑÑ Ñ ÐŸÐ±Ð·ÐŸÑÐ° ÐœÐ°ÐºÐŸÐ¿Ð»ÐµÐœÐžÑ. Ð§ÑÐŸÐ±Ñ Ð²ÐµÑÐœÑÑÑÑÑ Ðº ÑÑÐŸÐŒÑ ÐŸÐ±Ð·ÐŸÑÑ Ð¿ÐŸÐ·Ð¶Ðµ,ÑÐµÐ»ÐºÐœÐžÑÐµ ÐœÐ° ÑÐžÐŒÐ²ÐŸÐ»Ðµ "Gather", ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐœÑÐŒ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ ÐœÐžÐ¶Ðµ Ð»ÐžÐœÐµÐ¹ÐºÐž ÐŒÐµÐœÑ.</Text>
+<Text id="279">ÐÐ²Ðµ Ð±ÐŸÐ»ÑÑÐžÐµ ÐŸÐ±Ð»Ð°ÑÑÐž,ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÐµ "Ð Ð°Ð±ÐŸÑÐµÐµ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²ÐŸ" Ðž "ÐoÐ»Ð»ÐµÐºÑÐžÑ" ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ ÑÐŸÐ³ÐŸ,ÑÑÐŸÐ±Ñ Ð¿ÐµÑÐµÐŒÐµÑÑÐžÑÑ ÑÐ°Ð¹Ð»Ñ Ð² ÐÐ°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐœÐž Ð²ÐºÐ»ÑÑÐ°ÑÑ "ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐµ ÐŽÐµÑÐµÐ²ÐŸ",Ð³ÑÐ°ÑÐžÑÐµÑÐºÐžÐµ ÑÑÑÑÐºÑÑÑÑ,ÐºÐŸÑÐŸÑÑÐµ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶Ð°ÑÑ ÑÐ°Ð¹Ð»Ñ Ðž Ð¿Ð°Ð¿ÐºÐž.</Text>
+<Text id="280">ÐÑÐ±ÐµÑÐžÑÐµ ÑÐ»ÐµÐŒÐµÐœÑ ÐŽÐµÑÐµÐ²Ð°, ÐœÐ°Ð¶Ð°Ð² ÐœÐ° ÐœÐµÐ³ÐŸ Ð»ÐµÐ²ÐŸÐ¹ ÐºÐ»Ð°Ð²ÐžÑÐµÐ¹ ÐŒÑÑÐž. (Ð¢ÐŸ Ð¶Ðµ ÑÐ°ÐŒÐŸÐµ ÐŒÐŸÐ¶ÐœÐŸ ÑÐŽÐµÐ»Ð°ÑÑ ÐžÐœÐ°ÑÐµ, ÑÐŒ. ÐœÐžÐ¶Ðµ). ÐÐ²ÐŸÐ¹ÐœÑÐŒ ÑÐµÐ»ÑÐºÐŸÐŒ Ð²ÑÐ±ÐµÑÐžÑÐµ Ð¿Ð°Ð¿ÐºÑ, ÐžÐ»Ðž ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÑÐžÐŒÐ²ÐŸÐ» ÑÑÐŽÐŸÐŒ Ñ ÐœÐµÐ¹, ÑÑÐŸÐ±Ñ ÑÐ°Ð·Ð²ÐµÑÐœÑÑÑ (ÐžÐ»Ðž ÑÐ²ÐµÑÐœÑÑÑ) ÐµÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ. ÐÐ²ÐŸÐ¹ÐœÑÐŒ ÑÐµÐ»ÑÐºÐŸÐŒ ÐœÐ° ÐœÑÐ¶ÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ ÐŸÑÐºÑÐŸÐ¹ÑÐµ ÐµÐ³ÐŸ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÐŸÐ¹ ÐŽÐ°ÐœÐœÐŸÐŒÑ ÑÐžÐ¿Ñ ÑÐ°Ð¹Ð»ÐŸÐ² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ (ÑÐŒ.ÐÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ).</Text>
+<Text id="281">ÐÐµÑÐµÐ²ÐŸ ÑÐ°Ð±ÐŸÑÐµÐ³ÐŸ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ð° Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐžÑÑÐŸÑÐœÐžÐºÐž ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐŸÑÑÑÐ¿ÐœÑÑ
+ Ð² ÐÐœÑÐµÑÑÐµÐ¹ÑÐµ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°ÑÑ -- ÑÐµÐºÑÑÑÑ ÑÐ°Ð¹Ð»ÐŸÐ²ÑÑ ÑÐžÑÑÐµÐŒÑ (Ð²ÐºÐ»ÑÑÐ°Ñ ÐŽÐžÑÐºÐŸÐ²ÐŸÐŽ Ðž CD-ROM), ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐÑÐžÐœÑÑÐŸÑÐœ, Ðž ÐºÑÑ Ð·Ð°Ð³ÑÑÐ¶ÐµÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ². ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐŽÐµÑÑ Ðž ÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÑÑ ÑÑÐž ÑÐ°Ð¹Ð»Ñ, ÐŸÐŽÐœÐ°ÐºÐŸ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐœÐŸÑÐžÑÑ, ÑÐŽÐ°Ð»ÑÑÑ, ÐžÐ»Ðž ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐžÑ
+, Ð·Ð° ÐžÑÐºÐ»ÑÑÐµÐœÐžÐµÐŒ ÑÐ¶Ðµ Ð·Ð°Ð³ÑÑÐ¶ÐµÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐŽÐ°Ð»ÐµÐœÑ. ÐÑÑÑÐµÑÑÐ²Ð»ÑÑÑ ÐœÐ°Ð²ÐžÐ³Ð°ÑÐžÑ Ð² ÑÑÐŸÐŒ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ðµ ÑÑÐŸÐ±Ñ ÐœÐ°Ð¹ÑÐž ÑÐ°Ð¹Ð»Ñ ÐºÐŸÑÐŸÑÑÐµ Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ Ð²ÐºÐ»ÑÑÐžÑÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ.</Text>
+<Text id="282">Ð€Ð°Ð¹Ð»ÐŸÐ²ÐŸÐµ ÐŽÐµÑÐµÐ²ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÑ Ð¿ÐŸÐ»ÐœÐŸÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐµÑÐ²ÐŸÐœÐ°ÑÐ°Ð»ÑÐœÐŸ ÐŸÐœÐŸ Ð¿ÑÑÑÐŸ.</Text>
+<Text id="283">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÑÐ°Ð·ÐŒÐµÑÑ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ð°, Ð¿ÐµÑÐµÐŽÐ²ÐžÐ³Ð°Ñ ÐŒÑÑÑ Ð¿ÐŸ ÑÐµÑÐŸÐ¹ Ð»ÐžÐœÐµÐ¹ÐºÐµ, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÑÐŽÐµÐ»ÑÐµÑ ÐŽÐµÑÐµÐ²ÑÑ (ÑÐŸÑÐŒÐ° ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ñ ÐžÐ·ÐŒÐµÐœÑÐµÑÑÑ),Ðž Ð±ÑÐºÑÐžÑÑÑ ÐžÑ
+.</Text>
+<Text id="284">ÐÐœÐžÐ·Ñ ÐŸÐºÐœÐ° ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐ° ÑÑÐ°ÑÑÑÐœÐ°Ñ ÐŸÐ±Ð»Ð°ÑÑÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð¿ÑÐŸÐ³ÑÐµÑÑ ÐŸÐ¿ÐµÑÐ°ÑÐžÐ¹ ÐœÐ°ÐŽ ÑÐ°Ð¹Ð»Ð°ÐŒÐž (ÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÐžÐµ, Ð¿ÐµÑÐµÐŒÐµÑÐµÐœÐžÐµ, ÑÐŽÐ°Ð»ÐµÐœÐžÐµ). ÐÐœÐž ÐŒÐŸÐ³ÑÑ Ð·Ð°ÐœÑÑÑ ÐºÐ°ÐºÐŸÐµ-ÑÐŸ Ð²ÑÐµÐŒÑ. ÐÐœÐŸÐ¿ÐºÐ° "Ð¡ÑÐŸÐ¿" ÐŸÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑ Ð»ÑÐ±ÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð² ÐœÐ°ÑÑÐŸÑÑÐµÐµ Ð²ÑÐµÐŒÑ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ.</Text>
+<Text id="285">ÐÐ²Ðµ Ð±ÐŸÐ»ÑÑÐžÐµ ÐºÐœÐŸÐ¿ÐºÐž Ð·Ð°ÐœÐžÐŒÐ°ÑÑ ÐœÐžÐ¶ÐœÐžÐ¹ Ð¿ÑÐ°Ð²ÑÐ¹ ÑÐ³ÐŸÐ» ÑÐºÑÐ°ÐœÐ°."ÐÐŸÐ²Ð°Ñ ÐÐ°Ð¿ÐºÐ°",Ñ ÐºÐ°ÑÑÐžÐœÐŸÐ¹ Ð¿Ð°Ð¿ÐºÐž, ÑÐŸÐ·ÐŽÐ°ÑÑ ÐœÐŸÐ²ÑÐµ Ð¿Ð°Ð¿ÐºÐž (ÑÐŒ. Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ Ð¿Ð°Ð¿ÐŸÐº). ÐÐœÐŸÐ¿ÐºÐ° "Ð£ÐŽÐ°Ð»ÐžÑÑ"ÑÐŽÐ°Ð»ÑÐµÑ ÑÐ°Ð¹Ð»Ñ Ñ ÐœÐµÐœÑÐ¶ÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹.Ð©ÐµÐ»ÑÐŸÐº ÐœÐ° ÐºÐœÐŸÐ¿ÐºÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ" ÑÐŽÐ°Ð»ÐžÑ Ð»ÑÐ±ÑÐµ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÑÐµ ÑÐ°Ð¹Ð»Ñ ÐžÐ· ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸ ÐŽÐµÑÐµÐ²Ð° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ»ÑÑÐµÑÐœÐ°ÑÐžÐ²ÐœÐŸ, ÑÐ°Ð¹Ð»Ñ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐŽÐ°Ð»ÐµÐœÑ Ð¿ÑÑÐµÐŒ Ð¿ÐµÑÐµÑÑÐ³ÐžÐ²Ð°ÐœÐžÑ ÐžÑ
+ ÐœÐ° ÐºÐœÐŸÐ¿ÐºÑ "Ð£ÐŽÐ°Ð»ÐžÑÑ".</Text>
+<Text id="286">Ð§ÑÐŸÐ±Ñ ÐŸÑÐŸÐ±ÑÐ°ÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÑÑ
+ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ²,Ð²ÑÐ±ÐµÑÐžÑÐµ Ð¿ÐµÑÐ²ÑÐ¹ Ðž Ð·Ð°ÑÐµÐŒ ÑÐŽÐµÑÐ¶ÐžÐ²Ð°Ñ [Shift],ÑÐµÐ»ÐºÐœÐžÑÐµ ÐœÐ° Ð¿ÐŸÑÐ»ÐµÐŽÐœÐµÐŒ - Ð¿ÑÐž ÑÑÐŸÐŒ Ð±ÑÐŽÑÑ ÐŸÑÐŸÐ±ÑÐ°ÐœÑ Ð²ÑÐµ ÐŸÑ
+Ð²Ð°ÑÐµÐœÐœÑÐµ ÑÐ»ÐµÐŒÐµÐœÑÑ.ÐÑÐ±ÐŸÑ ÐœÐµ ÑÐ»ÐµÐŽÑÑÑÐžÑ
+ ÐŸÐŽÐžÐœ Ð·Ð° ÐŽÑÑÐ³ÐžÐŒ ÑÐ°Ð¹Ð»ÐŸÐ² Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ Ð¿ÑÐž ÐœÐ°Ð¶Ð°ÑÐŸÐ¹ ÐºÐ»Ð°Ð²ÐžÑÐµ [Ctrl] Ðž ÑÐµÐ»ÑÐºÐµ ÐœÐ° Ð²ÑÐ±ÐžÑÐ°ÐµÐŒÑÑ
+ ÑÐ°Ð¹Ð»Ð°Ñ
+. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÑÑÐž ÐŽÐ²Ð° ÐŒÐµÑÐŸÐŽÐ° Ð²ÐŒÐµÑÑÐµ ÐŽÐ»Ñ Ð³ÑÑÐ¿Ð¿Ñ ÐœÐµÑÐŒÐµÐ¶ÐœÑÑ
+ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ².</Text>
+<Text id="287">ÐÐµÐºÐŸÑÐŸÑÑÐµ Ð¿Ð°Ð¿ÐºÐž - ÑÐžÐ¿Ð° ÑÐµÑ
+,ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ ÐÐ°ÑÐž ÑÐŸÐ±ÑÑÐ²ÐµÐœÐœÑÐµ Ð²ÐµÐ±-ÑÑÑÐ°ÐœÐžÑÑ - ÐžÐœÐŸÐ³ÐŽÐ° ÐžÐŒÐµÑÑ ÐŸÑÐŸÐ±ÑÑ Ð²Ð°Ð¶ÐœÐŸÑÑÑ.ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÐµÑÐµÐœÐµÑÑÐž ÑÐ°ÐºÐžÐµ Ð¿Ð°Ð¿ÐºÐž ÐœÐ° Ð¿ÐµÑÐ²ÑÐ¹ ÑÑÐŸÐ²ÐµÐœÑ ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸ ÐŽÐµÑÐµÐ²Ð°. Ð§ÑÐŸÐ±Ñ ÑÐŽÐµÐ»Ð°ÑÑ ÑÑÐŸ, ÑÐµÐ»ÐºÐœÐžÑÐµ Ð¿ÑÐ°Ð²ÐŸÐ¹ ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ ÐŒÑÑÐž ÐœÐ° Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÐŸÐ¹ Ð¿Ð°Ð¿ÐºÐµ. ÐÑÐ±ÐµÑÐžÑÐµ "Ð¡ÐŸÐ·ÐŽÐ°ÑÑ ÑÐŸÐºÑÐ°ÑÐµÐœÐžÐµ" Ðž Ð²Ð²ÐµÐŽÐžÑÐµ ÐžÐŒÑ ÐŽÐ»Ñ Ð¿Ð°Ð¿ÐºÐž. ÐÐ»Ñ ÑÐŽÐ°Ð»ÐµÐœÐžÑ ÑÐ»ÐµÐŒÐµÐœÑÐ° ÑÐµÐ»ÐºÐœÐžÑÐµ Ð¿ÑÐ°Ð²ÐŸÐ¹ ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ ÐŒÑÑÐž ÐœÐ° Ð¿ÐŸÐŒÐµÑÐµÐœÐœÐŸÐ¹ Ð¿Ð°Ð¿ÐºÐµ Ðž Ð²ÑÐ±ÐµÑÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ ÑÐŸÐºÑÐ°ÑÐµÐœÐžÑ".</Text>
+</Content>
+</Part>
+<Part id="creating_folders">
+<Title>
+<Text id="288">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ Ð¿Ð°Ð¿ÐŸÐº</Text>
+</Title>
+<Content>
+<Text id="289">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ "ÐÐ°Ð¿ÐºÐž" Ð² ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐŒ ÐŽÐµÑÐµÐ²Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÑÐŸÐ±Ñ Ð³ÑÑÐ¿Ð¿ÐžÑÐŸÐ²Ð°ÑÑ Ð²ÐŒÐµÑÑÐµ Ðž Ð±ÐŸÐ»ÐµÐµ Ð»ÐµÐ³ÐºÐŸ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑ ÐžÑ
+. ÐÐ°Ð¿ÐºÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¿ÐŸÐŒÐµÑÐµÐœÑ Ð²ÐœÑÑÑÐž Ð¿Ð°Ð¿ÐŸÐº. Ð€Ð°ÐºÑÐžÑÐµÑÐºÐž ÐœÐµÑ ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÐžÑ ÐœÐ° ÑÐŸ,ÑÐºÐŸÐ»ÑÐºÐŸ Ð¿Ð°Ð¿ÐŸÐº ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÐŒÐµÑÑ ÐžÐ»Ðž ÐºÐ°Ðº Ð³Ð»ÑÐ±ÐŸÐºÐŸ ÐŸÐœÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð²Ð»ÐŸÐ¶ÐµÐœÑ. </Text>
+<Text id="290">Ð§ÑÐŸÐ±Ñ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐœÐŸÐ²ÑÑ Ð¿Ð°Ð¿ÐºÑ, Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐ»ÑÐœÐŸ Ð²ÑÐ±ÐµÑÐžÑÐµ ÑÑÑÐµÑÑÐ²ÑÑÑÑÑ Ð¿Ð°Ð¿ÐºÑ Ð² ÐÐµÑÐµÐ²Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ ÐœÐ° ÐºÐœÐŸÐ¿ÐºÐµ "ÐÐŸÐ²Ð°Ñ Ð¿Ð°Ð¿ÐºÐ°". ÐÐŸÐ²Ð°Ñ Ð¿Ð°Ð¿ÐºÐ° Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÐŸÐ³ÐŸ ÐžÐ»Ðž ÐœÐ° Ð²ÑÑÑÐµÐŒ ÑÑÐŸÐ²ÐœÐµ,ÐµÑÐ»Ðž ÐœÐž ÐŸÐŽÐœÐ° ÐœÐµ ÐŸÑÐŸÐ±ÑÐ°ÐœÐ°.ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ Ð¿ÑÐŸÑÐ²ÐŸÐžÑÑ Ð¿Ð°Ð¿ÐºÐµ ÐžÐŒÑ (Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ "ÐÐŸÐ²Ð°Ñ Ð¿Ð°Ð¿ÐºÐ°").</Text>
+<Text id="291">ÐÐ°Ð¿ÐºÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ°ÐºÐ¶Ðµ ÑÐŸÐ·ÐŽÐ°ÐœÑ ÑÐµÐ»ÑÐºÐŸÐŒ Ð¿ÑÐ°Ð²ÐŸÐ¹ ÐºÐœÐŸÐ¿ÐºÐž ÐŒÑÑÐž Ð¿ÐŸ Ð¿Ð°Ð¿ÐºÐµ,Ð²ÑÐ±ÐžÑÐ°Ñ "ÐÐŸÐ²Ð°Ñ Ð¿Ð°Ð¿ÐºÐ°" Ðž ÐŽÐµÐ¹ÑÑÐ²ÑÑ,ÐºÐ°Ðº ÑÐºÐ°Ð·Ð·Ð°ÐœÐŸ Ð²ÑÑÐµ.</Text>
+</Content>
+</Part>
+<Part id="adding_files">
+<Title>
+<Text id="292">ÐÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐµ ÑÐ°Ð¹Ð»ÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="293">Ð€Ð°Ð¹Ð»Ñ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐŒÑÑÑÑ Ð¿ÑÑÐµÐŒ ÐžÑ
+ Ð¿ÐµÑÐµÑÑÐ³ÐžÐ²Ð°ÐœÐžÑ Ðž ÐŸÑÐ¿ÑÑÐºÐ°ÐœÐžÑ. Ð£ÐºÐ°Ð·Ð°ÑÐµÐ»Ñ ÐŒÑÑÐž ÐŸÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ ÐœÐ°ÐŽ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÑÐŒ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐŒ ÐžÐ»Ðž, ÐµÑÐ»Ðž Ð²ÑÐ±ÐžÑÐ°ÐµÑÑÑ Ð±ÐŸÐ»ÑÑÐµ,ÑÐµÐŒ ÐŸÐŽÐžÐœ,ÐœÐ°ÐŽ ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÐŒÐž. ÐÑÐŸÐ¿ÑÑÑÐžÑÐµ Ð²ÑÐ±ÑÐ°ÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» Ð² ÐÐµÑÐµÐ²ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÑÐŸÐ±Ñ Ð·ÐŽÐµÑÑ ÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÑÑ ÑÐ°Ð¹Ð»Ñ (ÐµÑÐ»Ðž ÐžÑÑÐŸÑÐœÐžÐºÐŸÐŒ Ð±ÑÐ»ÐŸ ÐÐµÑÐµÐ²ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž).</Text>
+<Text id="294">ÐÑÐž ÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐŒÐœÐŸÐ¶ÐµÑÑÐ²ÐµÐœÐœÑÑ
+(ÑÐŸÑÑÐ°Ð²ÐœÑÑ
+) ÑÐ°Ð¹Ð»ÐŸÐ²,Ð²ÑÐµ ÐŸÐœÐž Ð¿ÐµÑÐµÐŒÐµÑÐ°ÑÑÑÑ Ð² ÑÐµÐ»ÐµÐ²ÑÑ Ð¿Ð°Ð¿ÐºÑ ÐœÐ° ÑÐŸÑ Ð¶Ðµ ÑÐ°ÐŒÑÐ¹ ÑÑÐŸÐ²ÐµÐœÑ,ÐœÐµÐ·Ð°Ð²ÐžÑÐžÐŒÐŸ ÐŸÑ ÑÑÑÑÐºÑÑÑÑ Ð¿Ð°Ð¿ÐºÐž,ÐºÐŸÑÐŸÑÑÑ ÐŸÐœÐž Ð·Ð°ÐœÐžÐŒÐ°Ð»Ðž Ð¿ÐµÑÐ²ÐŸÐœÐ°ÑÐ°Ð»ÑÐœÐŸ. ÐÐŸÐ³ÐŽÐ° ÐÑ ÐºÐŸÐ¿ÐžÑÑÐµÑÐµ Ð²ÑÐŸÑÐŸÐ¹ ÑÐ°Ð¹Ð» Ñ ÑÐµÐŒ Ð¶Ðµ ÑÐ°ÐŒÑÐŒ ÐžÐŒÐµÐœÐµÐŒ Ð² ÑÑ Ð¶Ðµ ÑÐ°ÐŒÑÑ Ð¿Ð°Ð¿ÐºÑ, ÐÐ°Ñ Ð·Ð°Ð¿ÑÐŸÑÑÑ, Ð·Ð°ÑÐµÑÐµÑÑ Ð»Ðž Ð¿ÐµÑÐ²ÑÐ¹. ÐÑÐ²ÐµÑÑÑÐµ "ÐÐµÑ" Ðž ÑÑÐŸÑ ÑÐ°Ð¹Ð» ÐœÐµ Ð±ÑÐŽÐµÑ ÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÑÑÑÑ,ÐœÐŸ ÐŽÑÑÐ³ÐžÐµ Ð±ÑÐŽÑÑ. Ð§ÑÐŸÐ±Ñ ÐŸÑÐŒÐµÐœÐžÑÑ Ð²ÑÐµ ÐŸÑÑÐ°ÑÑÐžÐµÑÑ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ Ð¿ÐŸ ÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÐžÑ,ÑÐµÐ»ÐºÐœÐžÑÐµ ÐœÐ° ÐºÐœÐŸÐ¿ÐºÐµ "Ð¡ÑÐŸÐ¿".</Text>
+<Text id="295">Ð¢ÐŸÐ»ÑÐºÐŸ "ÑÐ°ÐŒÑÐµ Ð²ÑÑÐŸÐºÐžÐµ"ÐžÐ· ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÑÑ
+ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² Ð±ÑÐŽÑÑ Ð¿ÐµÑÐµÐŒÐµÑÐµÐœÑ. ÐÐ°Ð¿ÐºÐ° Ð²ÑÑÐµ, ÑÐµÐŒ ÐµÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐœÑÐµ. ÐÑ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ ÑÐ°Ð¹Ð»Ñ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ Ð¿Ð°Ð¿ÐºÐž,Ð° ÑÐ°ÐºÐ¶Ðµ ÑÐ°ÐŒÑ Ð¿Ð°Ð¿ÐºÑ ÐœÐµÐ¿ÐŸÑÑÐµÐŽÑÑÐ²ÐµÐœÐœÐŸ.</Text>
+<Text id="296">ÐÐŸÐ³ÐŽÐ° ÐÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑÐµ ÑÐ°Ð¹Ð», ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑ Ð¿ÐŸÐžÑÐº Ð² ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ Ð¿Ð°Ð¿ÐºÐ°Ñ
+ Ð²ÑÐ¿ÐŸÐŒÐŸÐ³Ð°ÑÐµÐ»ÑÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ², ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+ Ðº ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÐŒÐŸÐŒÑ ÑÐ°Ð¹Ð»Ñ,Ðž ÐµÑÐ»Ðž ÐŸÐœ ÐœÐ°Ñ
+ÐŸÐŽÐžÑ ÐµÐ³ÐŸ,ÑÐŸ ÐœÐ°ÑÐžÐœÐ°ÐµÑ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÑÑÐž ÐŽÐ°ÐœÐœÑÐµ. ÐÑÐ»Ðž Ð¿ÑÐŸÑÐµÑÑ Ð¿ÑÐŸÐŽÐŸÐ»Ð¶Ð°ÐµÑÑÑ,ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð±ÑÑÑ Ð·Ð°Ð¿ÑÐŸÑÐµÐœÑ (Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ°Ð·) ÐŸ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž,ÑÑÐŸÐ±Ñ ÐŽÐŸÑÑÐžÑÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÑ ÐžÐŒÐ¿ÐŸÑÑÐžÑÑÐµÐŒÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ñ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž,ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐœÑÐŒÐž Ð² ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð­ÑÐŸÑ Ð¿ÑÐŸÑÐµÑÑ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐŒÐœÐŸÐ³ÐžÐµ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ Ð·Ð°Ð¿ÑÐŸÑÑ, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐµ Ð² ÑÐ°Ð·ÐŽÐµÐ»ÐµÐÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+.ÐÐ»Ñ Ð±ÐŸÐ»ÐµÐµ ÐŽÐµÑÐ°Ð»ÑÐœÐŸÐ³ÐŸ ÐŸÐ±ÑÑÑÐœÐµÐœÐžÑ Ð°ÑÑÐŸÑÐžÐžÑÐŸÐ²Ð°ÐœÐœÑÑ
+ Ñ ÑÐ°Ð¹Ð»Ð°ÐŒÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÑÐžÑÐ°Ð¹ÑÐµ ÐÐ»Ð°Ð²Ñ 2 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° Greenstone - ÐÐ·Ð²Ð»ÐµÑÐµÐœÐžÐµ Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²Ð° Ð²Ð°ÑÐžÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². </Text>
+</Content>
+</Part>
+<Part id="removing_files">
+<Title>
+<Text id="297">Ð£ÐŽÐ°Ð»ÐµÐœÐžÐµ ÑÐ°Ð¹Ð»ÐŸÐ²</Text>
+</Title>
+<Content>
+<Text id="298">Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŒÐµÑÐŸÐŽÐŸÐ² ÑÐŽÐ°Ð»ÐµÐœÐžÑ ÑÐ°Ð¹Ð»ÐŸÐ² Ðž Ð¿Ð°Ð¿ÐŸÐº. ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐœÐ°ÑÐ°Ð»Ð° ÑÐºÐ°Ð·Ð°ÑÑ,ÐºÐ°ÐºÐžÐµ ÐžÐ· ÐœÐžÑ
+ ÑÐŽÐ°Ð»ÑÑÑ, Ð²ÑÐ±ÐžÑÐ°Ñ ÐŸÐŽÐžÐœ ÐžÐ»Ðž Ð±ÐŸÐ»ÐµÐµ ÑÐ°Ð¹Ð»ÐŸÐ² Ðž Ð¿Ð°Ð¿ÐŸÐº, ÐºÐ°Ðº ÐŸÐ¿ÐžÑÐ°ÐœÐŸ Ð² ÐÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐœÐ°ÐºÐŸÐ¿Ð»ÐµÐœÐžÐ¹.</Text>
+<Text id="299">ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÑÐ°Ð¹Ð»Ñ ÐŸÑÐŸÐ±ÑÐ°ÐœÑ, ÐŽÐ»Ñ ÐžÑ
+ ÑÐŽÐ°Ð»ÐµÐœÐžÑ ÑÐµÐ»ÐºÐ°ÑÑ ÐºÐœÐŸÐ¿ÐºÑ "Ð£ÐŽÐ°Ð»ÐžÑÑ"ÐžÐ»Ðž ÐœÐ°Ð¶ÐžÐŒÐ°ÑÑ ÐºÐºÐ»Ð°Ð²ÐžÑÑ [Ð£ÐŽÐ°Ð»ÐžÑÑ] ÐœÐ° ÐºÐ»Ð°Ð²ÐžÐ°ÑÑÑÐµ, ÐžÐ»Ðž Ð¶Ðµ ÑÑÐœÑÑ ÐžÑ
+ ÐžÐ· ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐŸ ÐºÐœÐŸÐ¿ÐºÐž "Ð£ÐŽÐ°Ð»ÐžÑÑ" Ðž ÑÐ°ÐŒ ÐŸÑÐ¿ÑÑÐºÐ°ÑÑ.</Text>
+</Content>
+</Part>
+<Part id="filtering_the_tree">
+<Title>
+<Text id="300">Ð€ÐžÐ»ÑÑÑÐŸÐ²Ð°ÐœÐžÐµ ÐŽÐµÑÐµÐ²Ð°</Text>
+</Title>
+<Content>
+<Text id="301">"Ð€ÐžÐ»ÑÑÑÐŸÐ²Ð°ÐœÐžÐµ" ÐŽÐµÑÐµÐ²Ð° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐÐ°ÐŒ ÑÑÐ¶Ð°ÑÑ Ð¿ÐŸÐžÑÐº ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ².</Text>
+<Text id="302">ÐÑÐœÐºÑ "ÐÐŸÐºÐ°Ð·Ð°ÑÑ ÑÐ°Ð¹Ð»Ñ" Ð² ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐµÐŒ ÐŒÐµÐœÑ Ð¿ÐŸÐŽ ÐºÐ°Ð¶ÐŽÑÐŒ ÐŽÐµÑÐµÐ²ÐŸÐŒ Ð²ÑÐ²ÐŸÐŽÐžÑ ÑÐ¿ÐžÑÐŸÐº Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÑÑ
+ ÑÐžÐ»ÑÑÑÐŸÐ² ÑÐžÐ¿Ð° "Images".ÐÑÐ±ÐµÑÐžÑÐµ Ðž Ð²ÑÐµ Ð²ÑÐµÐŒÐµÐœÐœÐŸ ÑÐºÑÑÑÑÐµ ÑÐ°Ð¹Ð»Ñ Ð² ÐŽÐµÑÐµÐ²Ðµ.Ð§ÑÐŸÐ±Ñ Ð²ÐŸÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÐŽÐµÑÐµÐ²ÐŸ,Ð·Ð°ÐŒÐµÐœÐžÑÐµ ÑÐžÐ»ÑÑÑ ÑÐœÐŸÐ²Ð° ÐœÐ° "ÐÑÐµ ÑÐ°Ð¹Ð»Ñ".Ð­ÑÐž ÐŽÐµÐ¹ÑÑÐ²ÐžÑ ÐœÐµ ÐžÐ·ÐŒÐµÐœÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð¿ÑÐž ÑÑÐŸÐŒ ÐŸÐœÐž ÐœÐµ Ð·Ð°ÑÑÐ°Ð³ÐžÐ²Ð°ÑÑ Ð¿Ð°Ð¿ÐºÐž Ð² ÐŽÐµÑÐµÐ²Ðµ.</Text>
+<Text id="303">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð·Ð°ÐŽÐ°ÑÑ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÑ ÑÐžÐ»ÑÑÑÐ°,ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð² Ð² ÑÑ
+ÐµÐŒÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐµ ÑÐ°Ð¹Ð»ÐŸÐ² (Ð¢ÐŸÐ»ÑÐºÐŸ ÐŽÐ»Ñ ÑÐµÐ¶ÐžÐŒÐŸÐ² Ð¡Ð¿ÐµÑÐžÐ°Ð»ÐžÑÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÑ
+ Ð¡ÐžÑÑÐµÐŒ Ðž Ð­ÐºÑÐ¿ÐµÑÑ).ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐµ Ð°Ð±Ð±ÑÐµÐ²ÐžÐ°ÑÑÑÑ ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ ÑÐžÐ¿Ð° "*.*" ÐžÐ»Ðž "*.doc" ("*" ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÐµÑ Ð»ÑÐ±ÑÐŒ ÑÐžÐŒÐ²ÐŸÐ»Ð°ÐŒ).</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="enriching_the_collection_with_metadata">
+<Title>
+<Text id="304">ÐÐ±ÐŸÐ³Ð°ÑÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž</Text>
+</Title>
+<Content>
+<Text id="305">ÐÐŒÐµÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐœÐ°ÐºÐŸÐ¿Ð»ÐµÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž,ÐœÐ°Ð¿ÐŸÐ»ÐœÐžÑÐµ ÐžÑ
+ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹,ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÐŸÐ¹ "ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ".Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ, ÐºÐ°Ðº ÑÐŸÐ·ÐŽÐ°ÑÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ,ÐºÐ°Ðº ÐŸÐœÐž ÑÐµÐŽÐ°ÐºÑÐžÑÑÑÑÑÑ, ÐœÐ°Ð·ÐœÐ°ÑÐ°ÑÑÑÑ Ðž Ð²ÐŸÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑÑÑ,Ð° ÑÐ°ÐºÐ¶Ðµ ÐºÐ°Ðº ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð²ÐœÐµÑÐœÐžÐµ ÐžÑÑÐŸÑÐœÐžÐºÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ (ÑÐ°ÐºÐ¶Ðµ ÑÐŒ.ÐÐ»Ð°Ð²Ñ 2 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° Greenstone - ÐÐŸÐ»ÑÑÐµÐœÐžÐµ Ð±ÐŸÐ»ÑÑÐµÐ¹ ÑÐ°ÑÑÐž ÐžÐ· Ð²Ð°ÑÐžÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²).</Text>
+<Part id="the_enrich_view">
+<Title>
+<Text id="306">ÐÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐŸÐ±ÐŸÐ³Ð°ÑÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="307">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐŸÐ±ÐŸÐ³Ð°ÑÐµÐœÐžÑ ÐŽÐ»Ñ Ð·Ð°ÐŽÐ°ÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ - ÑÑÐŸ ÐŽÐ°ÐœÐœÑÐµ ÐŸ ÐŽÐ°ÐœÐœÑÑ
+ - ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ,ÐÐ²ÑÐŸÑ,ÐÐ°ÑÐ° ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ðž Ñ.ÐŽ. ÐÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ - ÑÑÐŸ ÐŽÐ°ÐœÐœÑÐµ ÐŸ ÐŽÐ°ÐœÐœÑÑ
+, ÐŸÐ±ÑÑÐœÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, Ð°Ð²ÑÐŸÑ, ÐŽÐ°ÑÐ° ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ðž.Ñ.Ð¿. ÐÐ°Ð¶ÐŽÑÐ¹ Ð¿ÑÐµÐŽÐŒÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÑÐŸÑÑÐŸÐžÑ ÐžÐ· ÐŽÐ²ÑÑ
+ ÑÐ°ÑÑÐµÐ¹: "ÑÐ»ÐµÐŒÐµÐœÑ" ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÐºÐ°ÐºÐŸÐ¹ Ð¿ÑÐµÐŽÐŒÐµÑ ÐžÐŒÐµÐµÑÑÑ Ð²Ð²ÐžÐŽÑ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, Ð°Ð²ÑÐŸÑ), Ð° "Ð·ÐœÐ°ÑÐµÐœÐžÐµ" Ð¿ÑÐžÑÐ²Ð°ÐžÐ²Ð°ÐµÑ ÑÑÐŸÐŒÑ ÑÐ»ÐµÐŒÐµÐœÑÑ ÐµÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐžÐŒÑ Ð°Ð²ÑÐŸÑÐ°).</Text>
+<Text id="308">Ð "ÑÐ°ÑÑÐžÑÐµÐœÐœÐŸÐŒ" Ð²ÐžÐŽÐµ ÑÐ»ÐµÐ²Ð° ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐÐµÑÐµÐ²ÐŸ ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐ¿ÑÐ°Ð²Ð° Ð¢Ð°Ð±Ð»ÐžÑÐ° ÐÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ Ð²ÑÐ±ÑÐ°ÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð° ÐžÐ»Ðž Ð¿Ð°Ð¿ÐºÐž ÐžÐ· ÐÐµÑÐµÐ²Ð° ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¡ÑÐŸÐ»Ð±ÑÑ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÑ ÑÐµÑÑÐŒ ÑÐ²ÐµÑÐŸÐŒ Ð²Ð²ÐµÑÑ
+Ñ Ðž ÐžÑ
+ ÑÐ°Ð·ÐŒÐµÑ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÐ·ÐŒÐµÐœÑÐœ Ð¿ÑÑÑÐŒ Ð¿ÐµÑÐµÐŽÐ²ÐžÐ¶ÐµÐœÐžÑ Ð»ÐžÐœÐžÐž ÑÐ°Ð·ÐŽÐµÐ»Ð°. ÐÐ°Ð¶Ð°Ð² ÐœÐ° Ð»ÑÐ±ÐŸÐ¹ ÑÑÐŽ Ð² ÑÐ°Ð±Ð»ÐžÑÐµ, Ð²Ñ ÑÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ Ðž ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐŽÐµÑÐ°Ð»Ðž ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+ Ð² ÐœÐžÐ¶ÐœÐµÐ¹ ÑÐµÐºÑÐžÐž ÐŸÐºÐœÐ°. Ð§ÐµÑÐœÑÐ¹ ÑÐµÐºÑÑ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ, ÑÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÑÐ²Ð»ÑÐµÑÑÑ ÐŸÐ±ÑÐžÐŒ ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ²,ÑÐŸÐ³ÐŽÐ° ÐºÐ°Ðº ÑÐµÑÑÐ¹ ÑÐµÐºÑÑ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ,ÑÑÐŸ ÑÑÐŸ - ÐœÐµ ÑÐ°Ðº.Ð§ÐµÑÐœÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÐ±ÐœÐŸÐ²Ð»ÐµÐœÑ ÐžÐ»Ðž ÑÐŽÐ°Ð»ÐµÐœÑ, Ð² ÑÐŸ Ð²ÑÐµÐŒÑ ÐºÐ°Ðº ÑÐµÑÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐŽÐ°Ð»ÐµÐœÑ ÐžÐ· ÑÐµÑ
+,ÐºÐŸÑÐŸÑÑÐµ ÐžÐŒÐµÑÑ ÐžÑ
+,ÐžÐ»Ðž ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÑ Ðº ÐŽÑÑÐ³ÐžÐŒ.</Text>
+<Text id="309">ÐÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ Ð¿Ð°Ð¿ÐºÐž ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ ÐŸÐºÐŸÐ»ÐŸ ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ Ð²Ñ
+ÐŸÐŽÐŸÐ² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+.Ð­ÑÐŸ ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐœÐ° ÑÐŸ,ÑÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÑÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÑ ÐŸÑ Ð¿Ð°Ð¿ÐŸÐº ÑÐŸÐŽÐžÑÐµÐ»ÐµÐ¹ (ÐžÐ»Ðž Ð¿ÑÐµÐŽÐºÐŸÐ²). Ð£ÐœÐ°ÑÐ»ÐµÐŽÐŸÐ²Ð°ÐœÐœÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐœÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÑ ÐžÐ»Ðž ÑÐŽÐ°Ð»ÐµÐœÑ, Ð° ÑÐŸÐ»ÑÐºÐŸ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÑ Ð² ÐºÐŸÐœÐµÑ ÑÐ¿ÐžÑÐºÐ° ÐžÐ»Ðž Ð¿ÐµÑÐµÐ¿ÐžÑÐ°ÐœÑ.Ð©ÐµÐ»ÐºÐœÐžÑÐµ ÐœÐ° ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐž Ð¿Ð°Ð¿ÐºÐž,ÑÑÐŸÐ±Ñ ÐœÐµÐŒÐµÐŽÐ»ÐµÐœÐœÐŸ Ð¿ÐµÑÐµÐ¹ÑÐž Ð² ÑÑ Ð¿Ð°Ð¿ÐºÑ, Ð³ÐŽÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð·Ð°ÐŽÐ°ÐœÑ.</Text>
+<Text id="310">ÐÑÐ±ÐµÑÐžÑÐµ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ð² ÑÐ°Ð±Ð»ÐžÑÐµ, ÑÑÐŸÐ±Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐ° Ð² ÐŸÐ±Ð»Ð°ÑÑÐž "Ð¡ÑÑÐµÑÑÐ²ÑÑÑÐžÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŽÐ»Ñ ...", ÐœÐ°Ñ
+ÐŸÐŽÑÑÐµÐ¹ÑÑ Ð²ÐœÐžÐ·Ñ ÑÐ°Ð±Ð»ÐžÑÑ. ÐÐµÑÐµÐ²ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ ÐŒÐŸÐ¶ÐµÑ ÑÐ°ÑÑÐžÑÑÑÑÑÑ Ðž ÑÐ°Ð·ÑÑÑÐ°ÑÑÑÑ. ÐÐ±ÑÑÐœÐŸ ÑÑÐŸ - ÑÐ¿ÐžÑÐŸÐº, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð²ÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ, Ð²Ð²ÐµÐŽÐµÐœÐœÑÐµ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ ÐŽÐ»Ñ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÐŸÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐ°. Ð©ÐµÐ»ÑÐŸÐº ÐœÐ° Ð²Ñ
+ÐŸÐŽÐµ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÑÐ°Ð·ÐŒÐµÑÐ°ÐµÑ ÐµÐ³ÐŸ Ð² Ð¿ÐŸÐ»Ðµ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹. Ð¡ ÐŽÑÑÐ³ÐŸÐ¹ ÑÑÐŸÑÐŸÐœÑ,Ð¿ÑÐž ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÐœÐœÐŸÐŒ Ð·ÐœÐ°ÑÐµÐœÐžÐž Ð² ÑÐµÐºÑÑÐŸÐ²ÐŸÐŒ Ð¿ÐŸÐ»Ðµ Ð²ÑÐ±ÐŸÑÐºÐž ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² ÐÐµÑÐµÐ²Ð° Ð·ÐœÐ°ÑÐµÐœÐžÐ¹, ÑÐžÑÑÐµÐŒÐ° ÐœÐ°ÑÐžÐœÐ°ÐµÑ ÑÐ°Ð±ÐŸÑÑ Ñ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐÑ Ð²Ð²ÐµÐ»Ðž. ÐÐ°Ð¶Ð°ÑÐžÐµ [Tab] Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð·Ð°Ð²ÐµÑÑÐ°ÐµÑ Ð¿ÐµÑÐ°ÑÐ°ÐœÐžÐµ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÐŸÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑ.</Text>
+<Text id="311">ÐÐœÐ°ÑÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŸÑÐ³Ð°ÐœÐžÐ·ÐŸÐ²Ð°ÐœÑ Ð² ÐžÐµÑÐ°ÑÑ
+ÐžÑ. Ð­ÑÐŸ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ Ð² ÐÐµÑÐµÐ²Ðµ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð¿Ð°Ð¿ÐºÐž ÐŽÐ»Ñ Ð²ÐœÑÑÑÐµÐœÐœÐžÑ
+ ÑÑÐŸÐ²ÐœÐµÐ¹. ÐÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÐžÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð²Ð²ÐµÐŽÐµÐœÑ,ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð·ÐœÐ°Ðº "|" ÐŽÐ»Ñ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ ÑÑÐŸÐ²ÐœÐµÐ¹. ÐÐ°Ð¿ÑÐžÐŒÐµÑ,"Cards|Red|Diamonds|Seven" ÐŒÐŸÐ³ Ð±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ Ð² ÐžÐµÑÐ°ÑÑ
+ÐžÐž, Ð¿ÑÐžÐŒÐµÑÐŸÐŒ ÐºÐŸÑÐŸÑÐŸÐ¹ ÑÐ²Ð»ÑÐµÑÑÑ Ð¿Ð°ÐºÐµÑ ÐžÐ³ÑÑ Ð² ÐºÐ°ÑÑÑ.Ð­ÑÐŸ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð³ÑÑÐ¿Ð¿ÐžÑÐŸÐ²Ð°ÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ Ð²ÐŒÐµÑÑÐµ. ÐÑÑÐ¿Ð¿Ñ ÐŒÐŸÐ³ÑÑ ÑÐ°ÐºÐ¶Ðµ ÐœÐ°Ð·ÐœÐ°ÑÐ°ÑÑÑÑ ÐºÐ°Ðº ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ðº ÑÐ°Ð¹Ð»Ð°ÐŒ.</Text>
+<Text id="312">Greenstone Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐžÐ·Ð²Ð»ÐµÐºÐ°ÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÐ»ÐµÐŒÐµÐœÑÑ ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ ÐžÐŒÐµÑÑ Ð¿ÑÐµÑÐžÐºÑ "ex.". Ð­ÑÐŸ ÐœÐµ ÐžÐŒÐµÐµÑ ÐœÐžÐºÐ°ÐºÐŸÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŽÐµÑÐµÐ²Ð° Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐŸ.</Text>
+</Content>
+</Part>
+<Part id="selecting_metadata_sets">
+<Title>
+<Text id="313">ÐÑÐ±ÐŸÑ ÐœÐ°Ð±ÐŸÑÐŸÐ² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</Title>
+<Content>
+<Text id="314">Ð£ÑÑÐ°ÐœÐŸÐ²ÐºÐ° ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ² Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐžÐ·Ð²ÐµÑÑÐœÐ° ÐºÐ°Ðº "ÐœÐ°Ð±ÐŸÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+". ÐÑÐžÐŒÐµÑÐŸÐŒ ÑÐ²Ð»ÑÐµÑÑÑ ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Dublin Core. ÐÐŸÐ³ÐŽÐ° ÐÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑÐµ ÐºÐŸÐŒÐ¿Ð»ÐµÐºÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðº ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸ ÐµÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÑ ÑÑÐ°ÐœÐŸÐ²ÑÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž ÐŽÐ»Ñ Ð²ÑÐ±ÐŸÑÐ°. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÐŒÐµÑÑ Ð±ÐŸÐ»ÑÑÐµ,ÑÐµÐŒ ÐŸÐŽÐžÐœ ÐœÐ°Ð±ÐŸÑ. ÐÐ»Ñ Ð¿ÑÐµÐŽÐŸÑÐ²ÑÐ°ÑÐµÐœÐžÑ ÑÑÐŸÐ»ÐºÐœÐŸÐ²ÐµÐœÐžÑ ÐŸÐŽÐžÐœÐ°ÐºÐŸÐ²ÑÑ
+ ÐžÐŒÑÐœ Ðº ÐœÐ°Ð·Ð²Ð°ÐœÐžÑ ÑÐ»ÐµÐŒÐµÐœÑÐ° Ð¿ÑÐžÑÐŸÐµÐŽÐžÐœÑÐµÑÑÑ ÐºÐŸÑÐŸÑÐºÐžÐ¹ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐŸÑ,ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÑÐŽÐµÐ»ÑÐµÑ ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÑÐ»ÐµÐŒÐµÐœÑ Dublin Core "Creator" ÑÑÐ°ÐœÐµÑ "dc.Creator".ÐÐ°Ð±ÐŸÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ñ
+ÑÐ°ÐœÑÑÑÑ Ð² ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° Ðž ÐžÐŒÐµÑÑ ÑÑÑÑÐžÐºÑ ".mds". </Text>
+<Text id="315">Ð§ÑÐŸÐ±Ñ ÐºÐŸÐœÑÑÐŸÐ»ÐžÑÐŸÐ²Ð°ÑÑ ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð²ÑÐ±ÐµÑÐžÑÐµ "ÐÐ°Ð±ÐŸÑ ÐÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+" Ð² Ð¿ÑÐŸÑÐŒÐŸÑÑÐµ "ÐÐžÐ·Ð°Ð¹Ðœ".</Text>
+</Content>
+</Part>
+<Part id="appending_new_metadata">
+<Title>
+<Text id="316">ÐÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</Title>
+<Content>
+<Text id="317">Ð¢ÐµÐ¿ÐµÑÑ ÐŒÑ ÐŽÐŸÐ±Ð°Ð²ÐžÐŒ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ - Ðž ÑÐ°ÐŒ ÑÐ»ÐµÐŒÐµÐœÑ,Ðž ÐµÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑ - Ðº ÑÐ°Ð¹Ð»Ñ. Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð²ÑÐ±ÐµÑÐµÐŒ ÑÐ°Ð¹Ð» ÐžÐ· ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ³ÐŸ ÐŽÐµÑÐµÐ²Ð° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.Ð¢Ð°ÐºÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð²ÑÐ·ÑÐ²Ð°ÐµÑ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÐµ Ð»ÑÐ±ÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+,Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ ÑÐ²ÑÐ·Ð°ÐœÐœÑÑ
+ Ñ ÑÑÐžÐŒ ÑÐ°Ð¹Ð»ÐŸÐŒ,Ð² ÑÐ°Ð±Ð»ÐžÑÐµ ÑÐ¿ÑÐ°Ð²Ð°.</Text>
+<Text id="318">ÐÐ°ÑÐµÐŒ Ð²ÑÐ±ÐµÑÐµÐŒ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+,ÐºÐŸÑÐŸÑÑÐ¹ Ñ
+ÐŸÑÐžÐŒ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ,Ð¿ÑÑÐµÐŒ ÑÐµÐ»ÑÐºÐ° ÑÑÐŽÐŸÐŒ Ñ ÐœÐžÐŒ Ð² ÑÐ°Ð±Ð»ÐžÑÐµ.</Text>
+<Text id="319">ÐÐ¿ÐžÑÐžÑÐµ ÑÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð² Ð¿ÐŸÐ»Ðµ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ Ð·ÐœÐ°Ðº "|", ÑÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÑÑÑÑÐºÑÑÑÑ, ÐºÐ°Ðº ÐŸÐ¿ÐžÑÐ°ÐœÐŸ Ð² ÑÐµÐºÑÐžÐž Ð Ð°ÑÑÐžÑÐžÑÑ ÐÐžÐŽ. ÐÐ°Ð¶Ð°Ð² ÐºÐ»Ð°Ð²ÐžÑÐž [ÐÐ²ÐµÑÑ
+] ÐžÐ»Ðž [ÐÐœÐžÐ·], ÐÑ ÑÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ ÑÑÐµÐ±ÑÐµÐŒÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ. ÐÐ°Ð¶Ð°Ð² ÐºÐ»Ð°Ð²ÐžÑÑ [Enter], ÐÑ ÑÐŒÐŸÐ¶ÐµÑÐµ ÑÐŸÑ
+ÑÐ°ÐœÐžÑÑ Ð²ÑÐ±ÑÐ°ÐœÐœÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðž ÑÐŸÐ·ÐŽÐ°ÑÑ ÐœÐŸÐ²ÐŸÐµ ÐœÐµÐ·Ð°Ð¿ÐŸÐ»ÐœÐµÐœÐœÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŽÐ»Ñ ÑÐ»ÐµÐŒÐµÐœÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, Ð¿ÐŸÐ·Ð²ÐŸÐ»ÐžÐ² ÐÐ°ÐŒ ÐŸÐ¿ÑÐµÐŽÐžÐ»ÐžÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ ÐŽÐ»Ñ ÐŸÐŽÐœÐŸÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐ°.</Text>
+<Text id="320">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐ°ÐºÐ¶Ðµ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ðº Ð¿Ð°Ð¿ÐºÐµ ÐžÐ»Ðž ÑÑÐ°Ð·Ñ Ðº ÐœÐµÐºÐŸÑÐŸÑÐŸÐŒÑ ÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ñ ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ². Ð­ÑÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑÑÑ ÐºÐŸ Ð²ÑÐµÐŒ ÑÐ°Ð¹Ð»Ð°ÐŒ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ Ð¿Ð°Ð¿ÐºÐž ÐžÐ»Ðž Ðº ÐŸÑÐŸÐ±ÑÐ°ÐœÐœÑÐŒ Ðž Ðº Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐœÑÐŒ Ð¿Ð°Ð¿ÐºÐ°ÐŒ. ÐÐŒÐµÐ¹ÑÐµ Ð² Ð²ÐžÐŽÑ,ÑÑÐŸ ÐµÑÐ»Ðž ÐÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÐ»Ðž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ðº Ð¿Ð°Ð¿ÐºÐµ, ÑÐŸ Ð»ÑÐ±ÑÐµ ÐœÐŸÐ²ÑÐµ ÑÐ°Ð¹Ð»Ñ Ð² ÐœÐµÐ¹ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÑÐœÐ°ÑÐ»ÐµÐŽÑÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐžÐ· ÑÑÐŸÐ¹ Ð¿Ð°Ð¿ÐºÐž.</Text>
+</Content>
+</Part>
+<Part id="adding_previously_defined_metadata">
+<Title>
+<Text id="321">ÐÐŸÐ±Ð°Ð²Ð»ÐœÐžÐµ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</Title>
+<Content>
+<Text id="322">Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ, ÑÐœÐ°ÑÐ°Ð»Ð° Ð²ÑÐ±ÐµÑÐžÑÐµ ÑÐ°Ð¹Ð», Ð·Ð°ÑÐµÐŒ ÑÑÐµÐ±ÑÐµÐŒÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐžÐ· ÐŽÐµÑÐµÐ²Ð° Ð·ÐœÐ°ÑÐµÐœÐžÐ¹, ÑÐ°ÑÑÐžÑÑÑ Ð¿Ð°Ð¿ÐºÐž ÐžÐµÑÐ°ÑÑ
+ÐžÐž Ð¿ÐŸ ÐŒÐµÑÐµ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÐž. ÐÑÐ±ÑÐ°ÐœÐœÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ Ð² Ð¿ÐŸÐ»Ðµ ÑÐµÐºÑÑÐ° (Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²ÐœÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð°Ð²ÑÐŸÐ²ÑÐ±ÐŸÑ Ð² ÐŽÐµÑÐµÐ²Ðµ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ Ðž ÑÑÐµÐŽÑÑÐ² Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐŸÐ³ÐŸ Ð·Ð°Ð²ÐµÑÑÐµÐœÐžÑ).</Text>
+<Text id="323">ÐÑÐŸÑÐµÑÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ñ ÑÐ¶Ðµ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐŒÐž Ð·ÐœÐ°ÑÐµÐœÐžÑÐŒÐž Ðº Ð¿Ð°Ð¿ÐºÐ°ÐŒ ÐžÐ»Ðž ÐŒÐœÐŸÐ¶ÐµÑÑÐ²Ñ ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐ°ÐºÐŸÐ¹ Ð¶Ðµ.</Text>
+</Content>
+</Part>
+<Part id="editing_or_removing_metadata">
+<Title>
+<Text id="324">ÐÐ·ÐŒÐµÐœÐžÑÑ ÐžÐ»Ðž ÑÐŽÐ°Ð»ÐžÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ</Text>
+</Title>
+<Content>
+<Text id="325">Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐžÐ»Ðž ÑÐŽÐ°Ð»ÐžÑÑ ÑÐ°ÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÐœÐ°ÑÐ°Ð»Ð° Ð²ÑÐ±ÐµÑÐžÑÐµ Ð¿ÐŸÐŽÑ
+ÐŸÐŽÑÑÐžÐ¹ ÑÐ°Ð¹Ð», Ð° Ð¿ÐŸÑÐŸÐŒ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ð² ÑÐ°Ð»Ð±ÐžÑÑ. Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÐŽÐ°Ð»ÐžÑÐµ ÑÐµÐºÑÑ ÐµÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÑ.</Text>
+<Text id="326">ÐÑÐŸÑÐµÑÑ ÐŸÐ±ÐœÐŸÐ²Ð»ÐµÐœÐžÑ ÐŽÐ°ÐœÐœÑÑ
+ Ð¿Ð°Ð¿ÐºÐž Ñ Ð¿ÐŸÐŽÐ¿Ð°Ð¿ÐºÐ°ÐŒÐž ÐžÐ»Ðž ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐŸÑ Ð¶Ðµ ÑÐ°ÐŒÑÐ¹, ÐœÐŸ Ð²Ñ ÑÐŒÐŸÐ¶ÐµÑÐµ ÐŸÐ±ÐœÐŸÐ²ÐžÑÑ ÑÐŸÐ»ÑÐºÐŸ ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÐµ, ÐŸÐ±ÑÐžÐµ ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ²/Ð¿Ð°Ð¿ÐŸÐº.</Text>
+<Text id="327">ÐÐµÑÐµÐ²ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð²ÑÐµ ÑÐµÐºÑÑÐžÐµ Ð¿ÑÐžÐ·ÐœÐ°ÑÐµÐœÐœÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ, Ð° ÑÐ°ÐºÐ¶Ðµ Ð²ÑÐµ Ð¿ÑÐµÐŽÑÐŽÑÑÐžÐµ ÐžÐ· ÑÐµÐºÑÑÐµÐ³ÐŸ ÑÐµÐ°ÐœÑÐ°, ÑÐ°Ðº ÑÑÐŸ ÐžÐ·ÐŒÐµÐœÐµÐœÐœÑÐµ ÐžÐ»Ðž ÑÐŽÐ°Ð»ÐµÐœÐœÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŸÑÑÐ°ÑÑÑÑ Ð² ÐŽÐµÑÐµÐ²Ðµ. ÐÐ°ÐºÑÑÐ² Ðž Ð²ÐœÐŸÐ²Ñ ÐŸÑÐºÑÑÐ² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐÑ ÑÐŽÐ°Ð»ÐžÑÐµ Ð²ÑÐµ ÑÐ°ÐœÐµÐµ Ð¿ÑÐžÐ·ÐœÐ°ÑÐµÐœÐœÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ.</Text>
+</Content>
+</Part>
+<Part id="reviewing_assigned_metadata">
+<Title>
+<Text id="328">ÐÑÐŸÑÐŒÐŸÑÑ Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</Title>
+<Content>
+<Text id="329">ÐÐœÐŸÐ³ÐŽÐ° ÐÐ°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ,Ð·Ð°ÐŽÐ°ÐœÐœÑÐµ ÐŽÐ»Ñ ÐŒÐœÐŸÐ³ÐžÑ
+ ÐžÐ»Ðž Ð²ÑÐµÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² ÑÑÐ°Ð·Ñ - ÐœÐ°Ð¿ÑÐžÐŒÐµÑ,ÑÑÐŸÐ±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ,ÑÐºÐŸÐ»ÑÐºÐŸ ÑÐ°Ð¹Ð»ÐŸÐ² ÐŸÑÑÐ°ÑÑÑÑ ÐŽÐ»Ñ Ð²ÐŸÐ·ÐŽÐµÐ¹ÑÑÐ²ÐžÑ ÐžÐ»Ðž Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐžÐŽÐµÐž ÐŸÑÐœÐŸÑÐžÑÐµÐ»ÑÐœÐŸ ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœÐžÑ ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+<Text id="330">ÐÑÐ±ÐµÑÐžÑÐµ ÑÐ°Ð¹Ð»Ñ, ÐºÐŸÑÐŸÑÑÐµ Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ, Ð¿ÐŸÑÐŸÐŒ ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° Ð¿ÑÐ°Ð²ÑÑ ÐºÐœÐŸÐ¿ÐºÑ ÐŒÑÑÐž Ðž Ð²ÑÐ±ÐµÑÐžÑÐµ "ÐÐ°Ð·ÐœÐ°ÑÐµÐœÑÐµ ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÐµ...". ÐÐŸÑÐ²Ð»ÑÐµÑÑÑ ÐŸÐºÐœÐŸ,ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÐŸÐµ "ÐÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ", Ð·Ð°ÐœÑÑÐŸÐµ Ð±ÐŸÐ»ÑÑÐŸÐ¹ ÑÐ°Ð±Ð»ÐžÑÐµÐ¹,ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐµÐ¹ ÐŒÐœÐŸÐ³ÐŸ ÐºÐŸÐ»ÐŸÐœÐŸÐº.ÐÐµÑÐ²Ð°Ñ ÐºÐŸÐ»ÐŸÐœÐºÐž Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐžÐŒÐµÐœÐ° ÑÐ°Ð¹Ð»ÐŸÐ²;ÑÑÑÐŸÐºÐž Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ Ð²ÑÐµ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+,Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ ÑÑÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ².</Text>
+<Text id="331">Ð ÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÑÐ°Ð±Ð»ÐžÑÑ ÐŒÐŸÐ¶ÐµÑ Ð·Ð°ÐœÑÑÑ ÐœÐµÐºÐŸÑÐŸÑÐŸÐµ Ð²ÑÐµÐŒÑ,ÐµÑÐ»Ðž Ð²ÑÐ¿Ð°Ð»ÐŸ ÐŒÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»ÐŸÐ².ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÐŽÐŸÐ»Ð¶Ð°ÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐŒ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐŸÐŒ Ð¿ÑÐž ÐŸÑÐºÑÑÑÐŸÐŒ ÐŸÐºÐœÐµ "ÐÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ".</Text>
+<Text id="332">ÐÐŸÐ³ÐŽÐ° ÐŸÐœÐ° ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ ÑÐ»ÐžÑÐºÐŸÐŒ Ð±ÐŸÐ»ÑÑÐŸÐ¹,ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÐžÐ»ÑÑÑÐŸÐ²Ð°ÑÑ ÑÐ°Ð±Ð»ÐžÑÑ "ÐÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ",Ð¿ÑÐžÐŒÐµÐœÑÑ ÑÐžÐ»ÑÑÑÑ Ðº ÐºÐŸÐ»ÐŸÐœÐºÐ°ÐŒ.ÐÐŸÑÐºÐŸÐ»ÑÐºÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÑ ÐœÐŸÐ²ÑÐµ ÑÐžÐ»ÑÑÑÑ, ÑÐŸÐ»ÑÐºÐŸ ÑÐµ ÑÑÑÐŸÐºÐž,ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑ ÐžÐŒ,ÐŸÑÑÐ°ÑÑÑÑ Ð²ÐžÐŽÐžÐŒÑÐŒÐž.Ð§ÑÐŸÐ±Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ,ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐžÐ»Ðž ÐŸÑÐžÑÑÐžÑÑ ÑÐžÐ»ÑÑÑ,ÑÐµÐ»ÐºÐœÐžÑÐµ Ð¿ÐŸ ÐžÐºÐŸÐœÐºÐµ "ÐÐŸÑÐŸÐœÐºÐ°" ÐœÐ°Ð²ÐµÑÑ
+Ñ ÐºÐŸÐ»ÐŸÐœÐºÐž. Ð£ Ð²Ð°Ñ Ð±ÑÐŽÐµÑ Ð·Ð°Ð¿ÑÐŸÑÐµÐœÐ° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÑÐžÐ»ÑÑÑÐµ. ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÑÐžÐ»ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ,ÐžÐ·ÐŒÐµÐœÑÐµÑÑÑ ÑÐ²ÐµÑ ÐºÐŸÐ»ÐŸÐœÐºÐž.</Text>
+<Text id="333">ÐÐ°Ð¿ÑÐŸÑ ÐžÐŒÐµÐµÑ ÑÐžÐŒÐ²ÐŸÐ»Ñ "ÐÑÐŸÑÑÐŸÐ¹" Ðž "ÐÑÐŸÐŽÐ²ÐžÐœÑÑÑÐ¹".ÐÑÐŸÑÑÐ°Ñ Ð²ÐµÑÑÐžÑ ÑÐžÐ»ÑÑÑÑÐµÑ ÐºÐŸÐ»ÐŸÐœÐºÐž ÑÐ°Ðº,ÑÑÐŸ ÐŸÐœÐž Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÑÐŸÐ»ÑÐºÐŸ ÑÑÑÐŸÐºÐž, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ("*" ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÐµÑ Ð²ÑÐµÐŒ Ð·ÐœÐ°ÑÐµÐœÐžÑÐŒ).ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐžÐ· ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐµÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ°.ÐÑÐŸÐŽÐ²ÐžÐœÑÑÐ°Ñ Ð²ÐµÑÑÐžÑ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð²ÑÐ¿ÐŸÐ»ÐœÑÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ:ÐÐŸÐ»Ð¶ÐµÐœ ÐœÐ°ÑÐ°ÑÑÑÑ Ñ,ÐÐµ ÑÐŸÐŽÐµÑÐ¶ÐžÑ,Ð Ð°Ð»ÑÐ°Ð²ÐžÑÐœÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ,ÐÐµÐœÑÑÐµ ÑÐµÐŒ, Ð­ÐºÐ²ÐžÐ²Ð°Ð»ÐµÐœÑÐµÐœ. ÐÐœÐ°ÑÐµÐœÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð±ÑÐŽÐµÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐŸÐ²Ð°ÑÑ, ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐŸ ÑÐ°Ðº,ÑÑÐŸÐ±Ñ Ð±ÑÑÑ Ð»ÑÐ±ÐŸÐ¹ ÑÑÑÐŸÐºÐŸÐ¹,Ð²ÐºÐ»ÑÑÐ°Ñ "*". ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ,ÐŽÐŸÐ»Ð¶ÐœÐŸ Ð»Ðž ÑÑÐŸ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐµ Ð±ÑÑÑ ÐœÐµ ÑÑÐ²ÑÑÐ²ÐžÑÐµÐ»ÑÐœÑÐŒ ÑÐ»ÑÑÐ°ÐµÐŒ. ÐÐ°ÐºÐŸÐœÐµÑ,ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ Ð²ÑÐŸÑÐŸÐµ ÑÑÐ»ÐŸÐ²ÐžÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÑ,ÐºÐŸÑÐŸÑÐŸÐµ ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÑÐ°ÐœÐ³Ð° Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ (Ð²ÑÐ±ÐžÑÐ°Ñ Ð Ð±ÐŸÐ»ÑÑÐŸÐµ) ÐžÐ»Ðž Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²ÐœÑÑ
+ Ð·ÐœÐ°ÑÐµÐœÐžÐ¹ (Ð²ÑÐ±ÐžÑÐ°Ñ ÐÐÐ).ÐÐžÐ¶Ðµ ÑÑÐŸÐ¹ ÐŸÐ±Ð»Ð°ÑÑÐž ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð¿ÐŸÐ»Ðµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐÐ°ÐŒ ÐžÐ·ÐŒÐµÐœÑÑÑ Ð¿ÐŸÑÑÐŽÐŸÐº ÑÐŸÑÑÐžÑÐŸÐ²ÐºÐž (Ð²ÐŸÐ·ÑÐ°ÑÑÐ°ÑÑÐžÐ¹ ÐžÐ»Ðž Ð¿ÐŸÐœÐžÐ¶Ð°ÑÐžÐ¹ÑÑ).ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐÑ Ð·Ð°ÐºÐŸÐœÑÐžÑÐµ,ÐœÐ°Ð¶ÐŒÐžÑÐµ "Ð£ÑÑÐ°ÐœÐŸÐ²ÐºÐ° ÑÐžÐ»ÑÑÑÐ°",ÑÑÐŸÐ±Ñ Ð¿ÑÐžÐŒÐµÐœÐžÑÑ ÐœÐŸÐ²ÑÐ¹ ÑÐžÐ»ÑÑÑ Ðº ÐºÐŸÐ»ÐŸÐœÐºÐµ.ÐÐ°Ð¶ÐŒÐžÑÐµ "ÐÑÐžÑÑÐžÑÑ ÑÐžÐ»ÑÑÑ",ÑÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÑÐµÐºÑÑÐžÐ¹ ÑÐžÐ»ÑÑÑ.ÐÐ±ÑÐ°ÑÐžÑÐµ Ð²ÐœÐžÐŒÐ°ÐœÐžÐµ ÐœÐ° ÑÐŸ,ÑÑÐŸ ÐŽÐµÑÐ°Ð»Ðž ÑÐžÐ»ÑÑÑÐ° ÑÐŸÑ
+ÑÐ°ÐœÑÑÑÑÑ, ÐŽÐ°Ð¶Ðµ ÐºÐŸÐ³ÐŽÐ° ÑÐžÐ»ÑÑÑ ÐŸÑÐžÑÐµÐœ.</Text>
+<Text id="334">ÐÐ°Ð¿ÑÐžÐŒÐµÑ,ÑÑÐŸÐ±Ñ ÐŸÑÑÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÑÐ°Ð±Ð»ÐžÑÑ "ÐÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ",Ð²ÑÐ±ÐµÑÐžÑÐµ ÐºÐŸÐ»ÐŸÐœÐºÑ, Ð²ÑÐ±ÐµÑÐžÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÑ ÑÐžÐ»ÑÑÑÐ° Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ (Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐžÐ»ÑÑÑ ÐœÐ° "*") Ðž Ð²ÐŸÐ·ÑÐ°ÑÑÐ°ÑÑÐžÐ¹ ÐžÐ»Ðž Ð¿ÐŸÐœÐžÐ¶Ð°ÑÑÐžÐ¹ÑÑ Ð¿ÐŸÑÑÐŽÐŸÐº.</Text>
+</Content>
+</Part>
+<Part id="importing_previously_assigned_metadata">
+<Title>
+<Text id="335">ÐÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</Title>
+<Content>
+<Text id="336">Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÑÐ°ÑÑÐºÐ°Ð·Ð°ÐœÐŸ, ÐºÐ°Ðº ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÐµ ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐµ ÑÐ°ÐœÑÑÐµ. Ð ÐµÑÑ ÐžÐŽÐµÑ ÐŸ ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÑ Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐ°ÐœÑÑÐµ.</Text>
+<Text id="337">ÐÑÐ»Ðž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð² ÑÐŸÑÐŒÐµ,ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐµÐŒÐŸÐ¹ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐŒ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐŸÐŒ,Ð±ÑÐ»Ðž Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð·Ð°ÐŽÐ°ÐœÑ ÑÐ°Ð¹Ð»Ñ - ÐœÐ°Ð¿ÑÐžÐŒÐµÑ,ÐºÐŸÐ³ÐŽÐ° ÐÑ Ð²ÑÐ±ÐžÑÐ°ÐµÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐžÐ· ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone - ÐŸÐœÐž ÐžÐŒÐ¿ÐŸÑÑÐžÑÑÑÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž,ÐºÐŸÐ³ÐŽÐ° ÐÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑÐµ ÑÐ°Ð¹Ð».Ð§ÑÐŸÐ±Ñ ÑÐŽÐµÐ»Ð°ÑÑ ÑÑÐŸ, ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÑ Ð² ÑÑÑÐ°ÐœÐŸÐ²ÐºÐ°Ñ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+,ÐŽÐŸÑÑÑÐ¿ÐœÑÑ
+ Ð² ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="338">ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð·Ð°Ð¿ÑÐ°ÑÐžÐ²Ð°ÐµÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ.ÐÐ°Ð¿ÑÐŸÑ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐºÑÐ°ÑÐºÐžÐµ ÐžÐœÑÑÑÑÐºÑÐžÐž Ðž Ð·Ð°ÑÐµÐŒ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐžÐŒÑ ÑÐ»ÐµÐŒÐµÐœÑÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+,ÐºÐŸÑÐŸÑÑÐµ ÐžÐŒÐ¿ÐŸÑÑÐžÑÑÑÑÑÑ,ÐºÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐŸÐœ Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ Ð² ÐžÑÑ
+ÐŸÐŽÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ.Ð­ÑÐŸ Ð¿ÐŸÐ»Ðµ ÐœÐµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐŸ ÐžÐ»Ðž ÐžÐ·ÐŒÐµÐœÐµÐœÐŸ.ÐÐ°ÑÐµÐŒ ÐÑ Ð²ÑÐ±ÐžÑÐ°ÐµÑÐµ,ÐºÐ°ÐºÐžÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐœÐŸÐ²ÐŸÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐ° ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÑ,Ð° Ð·Ð°ÑÐµÐŒ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ð² ÑÑÐžÑ
+ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐ°Ñ
+.Ð¡ÐžÑÑÐµÐŒÐ° Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð²ÑÐ±ÐžÑÐ°ÐµÑ ÑÐ°ÐŒÐŸÐµ Ð±Ð»ÐžÐ·ÐºÐŸÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐµ Ð² ÑÐµÑÐŒÐžÐœÐ°Ñ
+ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ðž ÑÐ»ÐµÐŒÐµÐœÑÐ° ÐŽÐ»Ñ ÐœÐŸÐ²ÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+<Text id="339">ÐÑÐŸÐ²ÐµÑÐžÐ² ÑÑÐž ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐžÑ,ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐ±ÑÐ°ÑÑ "ÐÐŸÐ±Ð°Ð²ÐžÑÑ",ÑÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐœÐŸÐ²ÑÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ðº Ð²ÑÐ±ÑÐ°ÐœÐœÑÐŒ ÐœÐ°Ð±ÐŸÑÐ°ÐŒ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+.Ð­ÑÐŸ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ ÑÐŸÐ»ÑÐºÐŸ ÑÐŸÐ³ÐŽÐ°,ÐºÐŸÐ³ÐŽÐ° ÐŸÑÑÑÑÑÑÐ²ÑÐµÑ ÑÐ»ÐµÐŒÐµÐœÑ Ñ ÑÐµÐŒ Ð¶Ðµ ÑÐ°ÐŒÑÐŒ ÐžÐŒÐµÐœÐµÐŒ Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ Ð²ÑÐ±ÑÐ°ÐœÐœÑÑ
+ ÑÑÑÐ°ÐœÐŸÐ²ÐŸÐº; "ÐÐ±ÑÐµÐŽÐžÐœÐžÑÑ" ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ Ð¿ÑÐžÑÐŸÐµÐŽÐžÐœÐµÐœÐžÐµ ÐœÐŸÐ²ÐŸÐ³ÐŸ ÑÐ»ÐµÐŒÐµÐœÑÐ° Ðº ÑÐ¶Ðµ ÑÐ°ÐœÐµÐµ Ð²ÑÐ±ÑÐ°ÐœÐœÐŸÐŒÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐŒ;ÐœÐ°ÐºÐŸÐœÐµÑ, "ÐÐµ ÑÑÐžÑÑÐ²Ð°ÑÑ", ÑÑÐŸÐ±Ñ ÐœÐµ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐœÐžÐºÐ°ÐºÐžÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ñ ÑÑÐžÐŒ ÐžÐŒÐµÐœÐµÐŒ ÑÐ»ÐµÐŒÐµÐœÑÐ°. ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÐ»Ðž,ÐºÐ°Ðº ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐœÐµÐºÐŸÑÐŸÑÑÑ ÑÐ°ÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, Ð·Ð°Ð¿ÐžÑÐ°ÐœÐœÐ°Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÑÐŸÑ
+ÑÐ°ÐœÑÐµÑÑÑ ÐœÐ° Ð²ÑÐµÐŒÑ ÑÑÑÐµÑÑÐ²ÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="340">ÐÐ»Ñ ÐŽÐµÑÐ°Ð»ÐµÐ¹ ÐŸÑÐœÐŸÑÐžÑÐµÐ»ÑÐœÐŸ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ð² metadata.xml, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² Greenstone ÐŽÐ»Ñ Ñ
+ÑÐ°ÐœÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÐŒ.Ð³Ð»Ð°Ð²Ñ 2 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° Greenstone.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="designing_your_collection_appearance">
+<Title>
+<Text id="341">ÐÑÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="342">ÐÐŸÐ³ÐŽÐ° ÐÐ°ÑÐž ÑÐ°Ð¹Ð»Ñ ÑÐœÐ°Ð±Ð¶ÐµÐœÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž,ÐŽÐ°Ð»ÐµÐµ ÐÑ ÑÐµÑÐ°ÐµÑÐµ,Ð² ÐºÐ°ÐºÐŸÐŒ Ð²ÐžÐŽÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Greenstone ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ.ÐÐ°ÐºÐŸÐ³ÐŸ Ð²ÐžÐŽÐ° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŽÐŸÑÑÑÐ¿ÐœÐ° ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ°? ÐÐ°ÐºÐžÐµ Ð¿ÑÑÐž Ð¿ÑÐµÐŽÑÑÐŒÐŸÑÑÐµÐœÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°? ÐÐ°ÐºÐžÐµ ÑÐ·ÑÐºÐž Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑÑÑ? ÐÐŽÐµ ÑÐ°Ð·ÐŒÐµÑÑÐžÑÑ ÐºÐœÐŸÐ¿ÐºÐž ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ? Ð­ÑÐž Ð²ÐµÑÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐœÐ°ÑÑÑÐŸÐµÐœÑ;Ð² ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑÑÑ,ÐºÐ°Ðº ÑÑÐŸ ÑÐŽÐµÐ»Ð°ÑÑ.</Text>
+<Part id="the_design_view">
+<Title>
+<Text id="343">ÐÐžÐŽ ÐŽÐžÐ·Ð°Ð¹ÐœÐ°</Text>
+</Title>
+<Content>
+<Text id="344">Ð­ÑÐŸÑ ÑÐ°Ð·ÐŽÐµÐ» Ð²Ð²ÐŸÐŽÐžÑ ÐÐ°Ñ Ð² ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÐµÐŒÑÐ¹ Ð¿ÑÐŸÐµÐºÑ Ðž ÐŸÐ±ÑÑÑÐœÑÐµÑ,ÐºÐ°Ðº Ð²ÑÐ±ÑÐ°ÑÑ ÐŒÐµÐ¶ÐŽÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒÐž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑÐŒÐž Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ Ð°ÐºÑÐžÐ²ÐœÐŸÐ¹ ÑÐ°ÑÑÐž ÐŸÐºÐœÐ°.</Text>
+<Text id="345">ÐÑÐž Ð¿ÐŸÐŒÐŸÑÐž ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÑÑ Ð²ÐžÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÐµÐŒÐŸÐ¹ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ.ÐÐ°ÑÐžÐ°ÐœÑÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÑ ÐœÐ° ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÑÐ°Ð·ÐŽÐµÐ»Ñ, ÐºÐ°Ð¶ÐŽÑÐ¹ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ ÑÐ²ÑÐ·Ð°Ðœ ÑÐŸ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐŸÐ¹ ÑÑÐ°ÐŽÐžÐµÐ¹ ÐœÐ°Ð²ÐžÐ³Ð°ÑÐžÐž ÐžÐ»Ðž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž.</Text>
+<Text id="346">Ð¡Ð»ÐµÐ²Ð° ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÑÐ¿ÐžÑÐŸÐº ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐ¹,Ð° ÑÐ¿ÑÐ°Ð²Ð° - ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÑÐµÐºÑÑÐžÐŒ ÑÐ¿ÐžÑÐºÐŸÐŒ.Ð§ÑÐŸÐ±Ñ Ð¿ÐµÑÐµÐ¹ÑÐž ÐœÐ° Ð²ÑÐ±ÑÐ°ÐœÐœÐŸÐµ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ,ÑÐµÐ»ÐºÐœÐžÑÐµ ÐµÐ³ÐŸ ÐžÐŒÑ Ð² ÑÐ¿ÐžÑÐºÐµ.</Text>
+<Text id="347">Ð§ÑÐŸÐ±Ñ Ð¿ÐŸÐœÐžÐŒÐ°ÑÑ ÑÑÐ°ÐŽÐžÐž Ðž ÑÐµÑÐŒÐžÐœÑ,ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐµ Ð¿ÑÐž Ð¿ÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐœÐ°ÑÐ°Ð»Ð° Ð¿ÑÐŸÑÑÐžÑÐµ Ð³Ð»Ð°Ð²Ñ 1 Ðž 2 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° Greenstone.</Text>
+</Content>
+</Part>
+<Part id="general">
+<Title>
+<Text id="348">ÐÐ±ÑÐµÐµ</Text>
+</Title>
+<Content>
+<Text id="349">Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ,ÐºÐ°Ðº Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ Ðž ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐŸÐ±ÑÐžÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž, ÐŸÑÐœÐŸÑÑÑÐžÐµÑÑ Ðº ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð² "Ð Ð°Ð·ÐŽÐµÐ»Ð°Ñ
+ ÐŽÐžÐ·Ð°Ð¹ÐœÐ°" ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐ±ÑÐžÐµ".</Text>
+<Text id="350">ÐÐŽÐµÑÑ Ð·ÐœÐ°ÑÐµÐœÐžÑ,Ð¿ÑÐµÐŽÑÑÐŒÐŸÑÑÐµÐœÐœÑÐµ Ð¿ÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž,ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐžÐ·ÐŒÐµÐœÐµÐœÑ.</Text>
+<Text id="351">Ð¡ÐœÐ°ÑÐ°Ð»Ð° ÐžÐŽÑÑ ÐºÐŸÐœÑÐ°ÐºÑÐœÑÐµ Ð°ÐŽÑÐµÑÐ° ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ ÑÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑÐµÐ³ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð»ÐžÑÐ°. Ð¡Ð»ÐµÐŽÑÑÑÐµÐµ Ð¿ÐŸÐ»Ðµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐÐ°ÐŒ ÐžÐ·ÐŒÐµÐœÑÑÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¡Ð»ÐµÐŽÑÑÐµÐµ ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð¿Ð°Ð¿ÐºÑ, Ð² ÐºÐŸÑÐŸÑÐŸÐ¹ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐœÐŸ ÐœÐµ Ð¿ÐŸÐŽÐ»ÐµÐ¶ÐžÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑÐŒ. Ð¡Ð»ÐµÐŽÑÑÑÐµÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑ (Ð² ÑÐŸÑÐŒÐµ URL) ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÐµ,ÑÑÐŸÐ±Ñ Ð¿ÐŸÐºÐ°Ð·Ð°ÑÑ ÐœÐ°Ð²ÐµÑÑ
+Ñ ÑÐ»ÐµÐ²Ð° ÐŸÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÑÑÐ°ÐœÐžÑÑ ÐŸ ÐœÐµÐ¹, Ðž ÑÐ»ÐµÐŽÑÑÑÐµÐµ - ÐžÐºÐŸÐœÐºÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ Ð² Greenstone ÑÑÑÐ°ÐœÐžÑÐ° ÐŽÐ»Ñ ÑÐ²ÑÐ·Ðž Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹. ÐÐŸÑÐ»Ðµ ÑÑÐŸÐ³ÐŸ, Ð²Ñ ÑÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐŽÐµÐ»ÐžÑÑ Ð¿ÑÐœÐºÑ Ð³Ð°Ð»ÐŸÑÐºÐŸÐ¹, ÑÐºÐ°Ð·Ð°Ð², ÐŽÐŸÑÑÑÐ¿ÐœÐ° Ð»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐŽÑÑÐ³ÐžÐŒ. ÐÐ°ÐºÐŸÐœÐµÑ, ÑÐ»ÐµÐŽÑÐµÑ ÐŸÐ±Ð»Ð°ÑÑÑ ÑÐµÐºÑÑÐ° "ÐÐ¿ÐžÑÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž",Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐœÐ°Ñ ÑÐ°ÐœÐµÐµ Ð² Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</Content>
+</Part>
+<Part id="document_plugins">
+<Title>
+<Text id="352">ÐÐ»Ð°Ð³ÐžÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°</Text>
+</Title>
+<Content>
+<Text id="353">Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ¿ÐžÑÐ°ÐœÐŸ,ÐºÐ°Ðº ÑÐŸÑÐŒÐžÑÐŸÐ²Ð°ÑÑ Ð¿Ð»Ð°Ð³ÐžÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐŽÐ»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹.Ð ÐœÑÐŒ ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ,ÐºÐ°Ðº ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ,ÐºÐ°ÐºÐžÐµ Ð¿Ð»Ð°Ð³ÐžÐœÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ, ÐºÐ°ÐºÐžÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ Ð¿ÐµÑÐµÐŽÐ°Ð²Ð°ÑÑ Ðº ÐœÐžÐŒ Ðž Ð² ÐºÐ°ÐºÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ ÐŸÐœÐž Ð²Ñ
+ÐŸÐŽÑÑ. Ð©ÐµÐ»ÐºÐœÐžÑÐµ "ÐÐ»Ð°Ð³ÐžÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²" Ð² Ð¿ÑÐœÐºÑÐµ "Ð Ð°Ð·ÐŽÐµÐ»Ñ Ð¿ÑÐŸÐµÐºÑÐ°".</Text>
+<Text id="354">Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÑÑ Ð¿Ð»Ð°Ð³ÐžÐœ, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ,ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ "ÐÑÐ±ÐŸÑ Ð¿Ð»Ð°Ð³ÐžÐœÐ° ÐŽÐ»Ñ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÑ" Ð² ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐµÐŒ ÑÐ¿ÐžÑÐºÐµ ÐŸÐºÐŸÐ»ÐŸ ÐŸÑÐœÐŸÐ²Ð°ÐœÐžÑ,Ðž Ð·Ð°ÑÐµÐŒ ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐŸÐ±Ð°Ð²ÐžÑÑ Ð¿Ð»Ð°Ð³ÐžÐœ". ÐÐŸÑÐ²Ð»ÑÐµÑÑÑ ÐŸÐºÐœÐŸ Ñ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµÐŒ "ÐÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ²";ÐŸÐœÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐŸ ÐœÐžÐ¶Ðµ. ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐÑ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°Ð»Ðž ÐœÐŸÐ²ÑÐ¹ Ð¿Ð»Ð°Ð³ÐžÐœ, ÐŸÐœ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑÑÑ Ð² ÐºÐŸÐœÐµÑ ÑÐ¿ÐžÑÐºÐ° "Ð£ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐœÑÐµ ÑÐµÐºÑÑÐžÐµ Ð¿Ð»Ð°Ð³ÐžÐœÑ". ÐÐ°ÐŒÐµÑÑÑÐµ, ÑÑÐŸ, ÐºÑÐŸÐŒÐµ UnknownPlug, ÐºÐ°Ð¶ÐŽÑÐ¹ Ð¿Ð»Ð°Ð³ÐžÐœ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð²ÑÐ²ÐµÐŽÐµÐœ ÑÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐžÐœ ÑÐ°Ð· Ð² ÑÐ¿ÐžÑÐºÐµ.</Text>
+<Text id="355">Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ Ð¿Ð»Ð°Ð³ÐžÐœ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ Ð² ÑÐ¿ÐžÑÐºÐµ Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ Ð¿Ð»Ð°Ð³ÐžÐœ".</Text>
+<Text id="356">ÐÐ»Ð°Ð³ÐžÐœÑ ÑÐŸÑÐŒÐžÑÑÑÑÑÑ Ð¿ÑÑÐµÐŒ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ². Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐžÑ
+, Ð²ÑÐ±ÐµÑÐžÑÐµ Ð¿Ð»Ð°Ð³ÐžÐœ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð€ÐŸÑÐŒÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð¿Ð»Ð°Ð³ÐžÐœÐŸÐ²"(ÐžÐ»Ðž ÐŽÐ²ÐŸÐ¹ÐœÑÐŒ ÑÐµÐ»ÑÐºÐŸÐŒ ÐœÐ° Ð¿Ð»Ð°Ð³ÐžÐœÐµ). ÐÐžÐ°Ð»ÐŸÐ³ "ÐÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÐÑÐ³ÑÐŒÐµÐœÑÑ" Ð²ÐŸÐ·ÐœÐžÐºÐ°ÐµÑ Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒÐž ÐŸÐ¿ÑÐžÑÐŒÐž ÐŽÐ»Ñ ÑÐºÐ°Ð·Ð°ÐœÐžÑ Ð°ÑÐ³ÑÐŒÐµÐœÑÐŸÐ².</Text>
+<Text id="357">Ð¡ÑÑÐµÑÑÐ²ÑÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ Ð²ÐžÐŽÑ ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÑÐ²Ð»ÑÑÑÑÑ ÐœÐµÐ·Ð°Ð²ÐžÑÐžÐŒÑÐŒÐž ÐºÐœÐŸÐ¿ÐºÐ°ÐŒÐž Ðž ÑÐµÐ»ÑÐŸÐº ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ ÐŸÐ¿ÑÐžÑ Ðº Ð¿Ð»Ð°Ð³ÐžÐœÑ. ÐÑÑÐ³ÐžÐµ Ð²ÑÑÑÑÐ¿Ð°ÑÑ Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ ÑÑÑÐŸÐºÐž ÑÐµÐºÑÑÐ° Ñ ÐœÐµÐ·Ð°Ð²ÐžÑÐžÐŒÐŸÐ¹ ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ Ðž ÐŸÐ±Ð»Ð°ÑÑÑÑ ÑÐµÐºÑÑÐ°. Ð©ÐµÐ»ÐºÐœÐžÑÐµ ÐœÐ° Ð¿ÐŸÐ»Ðµ,ÑÑÐŸÐ±Ñ Ð²ÑÐ·Ð²Ð°ÑÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑ,Ð·Ð°ÑÐµÐŒ ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°Ð¹ÑÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐ¹ ÑÐµÐºÑÑ (Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸÐµ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÐµ,Ð¿ÑÑÑ ÑÐ°Ð¹Ð»Ð° Ðž Ñ.ÐŽ.) Ð² Ð¿ÐŸÐ»Ðµ. ÐÑÑÐ³ÐžÐµ - ÑÑÐŸ ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐžÐµ ÐŒÐµÐœÑ,Ð² ÐºÐŸÑÐŸÑÑÑ
+ ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÑÐ±ÐžÑÐ°ÑÑ ÐœÑÐ¶ÐœÐŸÐµ ÐžÐ· Ð·Ð°ÐŽÐ°ÐœÐœÐŸÐ³ÐŸ ÐœÐ°Ð±ÐŸÑÐ° Ð·ÐœÐ°ÑÐµÐœÐžÐ¹. Ð§ÑÐŸÐ±Ñ Ð¿ÐŸÐœÑÑÑ,ÑÑÐŸ ÐŽÐµÐ»Ð°ÐµÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑ, ÐŽÐ°Ð¹ÑÐµ ÐŒÑÑÐž ÐœÐ° ÐŒÐ³ÐœÐŸÐ²ÐµÐœÐžÐµ Ð¿ÑÐŸÐ¹ÑÐž Ð¿ÐŸ ÐµÐ³ÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐžÑ Ðž ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ Ð¿ÐŸÑÐ²ÐžÑÑÑ.</Text>
+<Text id="358">ÐÐŸÐ³ÐŽÐ° ÐÑ ÐžÐ·ÐŒÐµÐœÐžÐ»Ðž ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÑ,ÐœÐ°Ð¶ÐŒÐžÑÐµ "ÐÐ", ÑÑÐŸÐ±Ñ Ð¿ÑÐžÐœÑÑÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ðž Ð·Ð°ÐºÑÑÑÑ ÐŽÐžÐ°Ð»ÐŸÐ³,ÐžÐ»Ðž "ÐÑÐŒÐµÐœÐžÑÑ",ÑÑÐŸÐ±Ñ Ð·Ð°ÐºÑÑÑÑ ÐŽÐžÐ°Ð»ÐŸÐ³ Ð±ÐµÐ· ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð»ÑÐ±ÑÑ
+ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ² Ð¿Ð»Ð°Ð³ÐžÐœÐ°.</Text>
+<Text id="359">ÐÐ»Ð°Ð³ÐžÐœÑ Ð² ÑÐ¿ÐžÑÐºÐµ ÑÐ°ÑÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÑ Ð² ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÐŸÐŒ Ð¿ÐŸÑÑÐŽÐºÐµ,ÑÐ°Ðº ÐºÐ°Ðº ÑÐ¿ÐŸÑÑÐŽÐŸÑÐµÐœÐžÐµ ÐžÐœÐŸÐ³ÐŽÐ° Ð²Ð°Ð¶ÐœÐŸ. ÐÐŸÑÑÐŽÐŸÐº ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÑÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÑ
+ ÐŒÐŸÐŽÑÐ»ÐµÐ¹ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÐ·ÐŒÐµÐœÐµÐœ ÑÐŸÐ»ÑÐºÐŸ Ð² ÑÐµÐ¶ÐžÐŒÐ°Ñ
+ Ð¡Ð¿ÐµÑÐžÐ°Ð»ÐžÑÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÑ
+ Ð¡ÐžÑÑÐµÐŒ Ðž Ð­ÐºÑÐ¿ÐµÑÑ (ÑÐŒ. ÐÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÑ).</Text>
+</Content>
+</Part>
+<Part id="search_types">
+<Title>
+<Text id="360">ÐÐžÐŽÑ Ð¿ÐŸÐžÑÐºÐ°</Text>
+</Title>
+<Content>
+<Text id="361">Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ,ÐºÐ°Ðº ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž ÐœÐŸÐ²ÐŸÐ³ÐŸ ÐŽÐžÐ·Ð°Ð¹ÐœÐ° Ð² Greenstone; Ð²ÐžÐŽÑ Ð¿ÐŸÐžÑÐºÐ°,ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ Ð¿ÐŸÐ»ÑÐŒ. ÐÐžÐŽÑ Ð¿ÐŸÐžÑÐºÐ° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ, ÐºÐ°ÐºÐŸÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÐŸÐžÑÐºÐ° ÐŽÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœ: ÑÐŸÑÐŒÐ° ÐŽÐ»Ñ Ð¿ÐŸÐ»ÐµÐ¹ Ð¿ÐŸÐžÑÐºÐ° Ðž/ÐžÐ»Ðž Ð¿ÑÐŸÑÑÐŸÐ¹ ÐŽÐ»Ñ ÑÐµÐ³ÑÐ»ÑÑÐœÐŸÐ³ÐŸ Ð¿ÐŸÐžÑÐºÐ°. Ð©ÐµÐ»ÐºÐœÐžÑÐµ Ð²ÐžÐŽÑ Ð¿ÐŸÐžÑÐºÐ° Ð² "Ð Ð°Ð·ÐŽÐµÐ»Ð°Ñ
+ ÐŽÐžÐ·Ð°Ð¹ÐœÐ°".</Text>
+<Text id="362">ÐÐŸÐ³ÐŽÐ° ÐÑ ÐœÐ°ÑÐžÐœÐ°ÐµÑÐµ Ð¿ÑÐŸÑÐŒÐŸÑÑ Ð²ÐžÐŽÐŸÐ² Ð¿ÐŸÐžÑÐºÐ°, ÑÐœÐ°ÑÐ°Ð»Ð° Ð²ÑÐ±ÐµÑÐžÑÐµ "ÐÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÑÐ°ÑÑÐžÑÐµÐœÐœÐŸÐ³ÐŸ Ð¿ÐŸÐžÑÐºÐ°",ÐºÐŸÑÐŸÑÑÐ¹ Ð°ÐºÑÐžÐ²ÐžÐ·ÐžÑÑÐµÑ ÐŽÑÑÐ³ÐžÐµ ÑÑÐµÐŽÑÑÐ²Ð° ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ. ÐÑÐž ÑÑÐŸÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð±ÑÐŽÐµÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐ°: ÐžÐœÐŽÐµÐºÑÐžÑÑÑÑÐžÐ¹ ÐŒÐµÑ
+Ð°ÐœÐžÐ·ÐŒ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÐžÑ Ð¿ÑÐŸÐ²ÐµÑÑÐž Ð¿ÐŸÐžÑÐº Ñ ÐžÑÐ¿ÐŸÐ»ÐžÐ·ÐŸÐ²Ð°ÐœÐžÐµÐŒ Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÑ
+ Ð¿ÐŸÐ»ÐµÐ¹. Ð¡Ð¿ÐµÑÐžÑÐžÐºÐ°ÑÐžÑ ÐžÐœÐŽÐµÐºÑÐ° Ð² ÑÑÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ ÐœÐµÐŒÐœÐŸÐ³ÐŸ ÐžÐ·ÐŒÐµÐœÐµÐœÐ°. (ÐÑÐž Ð¿ÐµÑÐµÐºÐ»ÑÑÐµÐœÐžÐž ÐŒÐµÐ¶ÐŽÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐŒ Ðž Ð¿ÑÐŸÐŽÐ²ÐžÐœÑÑÑÐŒ Ð¿ÑÐžÑÐºÐŸÐŒ ÐÐÐ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑ ÐºÐŸÐœÐ²ÐµÑÑÐžÐ²ÐŸÐ²Ð°ÐœÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ ÐžÐœÐŸÐ³ÐŽÐ° ÐœÐµ ÐŽÐŸÑÑÐ°ÑÐŸÑÐœÐŸ ÑÐŸÑÐœÐŸ.)</Text>
+<Text id="363">Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ Ð²ÐžÐŽ Ð¿ÐŸÐžÑÐºÐ°,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° "ÐÐžÐŽÑ Ð¿ÐŸÐžÑÐºÐ°" Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐŸÐ±Ð°Ð²ÐžÑÑ Ð²ÐžÐŽ Ð¿ÐŸÐžÑÐºÐ°".ÐÐ°Ð¶ÐŽÑÐ¹ Ð²ÐžÐŽ Ð¿ÐŸÐžÑÐºÐ° ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÑÐ²ÐžÑÑÑÑ Ð² ÑÐ¿ÐžÑÐºÐµ ÑÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐžÐœ ÑÐ°Ð·. ÐÐµÑÐ²ÑÐ¹ Ð²ÐžÐŽ Ð¿ÐŸÐžÑÐºÐ° Ð±ÑÐŽÐµÑ Ð¿ÐŸ-ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Ðž ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑÑ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ Ð¿ÐŸÐžÑÐºÐ° ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐµ ÐŸÑÑÐ°Ð»ÑÐœÑÐµ Ð²ÐžÐŽÑ ÐŒÐŸÐ¶ÐœÐŸ Ð±ÑÐŽÐµÑ Ð²ÑÐ±ÑÐ°ÑÑ ÐœÐ° ÑÑÑÐ°ÐœÐžÑÐµ ÐŸÐ¿ÑÐžÐ¹.</Text>
+<Text id="364">Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ Ð²ÐžÐŽ Ð¿ÐŸÐžÑÐºÐ°, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° "Ð¢ÐµÐºÑÑÐžÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ Ð²ÐžÐŽÐŸÐ² Ð¿ÐŸÐžÑÐºÐ°" Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ Ð²ÐžÐŽ Ð¿ÐŸÐžÑÐºÐ°".Ð¡Ð¿ÐžÑÐŸÐº ÐŽÐŸÐ»Ð¶ÐµÐœ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ Ð¿ÐŸ ÐºÑÐ°Ð¹ÐœÐµÐ¹ ÐŒÐµÑÐµ ÐŸÐŽÐžÐœ Ð²ÐžÐŽ Ð¿ÐŸÐžÑÐºÐ°.</Text>
+</Content>
+</Part>
+<Part id="search_indexes">
+<Title>
+<Text id="365">ÐÐœÐŽÐµÐºÑÑ Ð¿ÐŸÐžÑÐºÐ°</Text>
+</Title>
+<Content>
+<Text id="366">ÐÐœÐŽÐµÐºÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ,ÐºÐ°ÐºÐžÐµ ÑÐ°ÑÑÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐ²Ð»ÑÑÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž ÐŽÐ»Ñ Ð¿ÐŸÐžÑÐºÐ°. Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ,ÐºÐ°Ðº ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ Ðž ÑÐŽÐ°Ð»ÐžÑÑ ÐžÐœÐŽÐµÐºÑÑ,Ð° ÑÐ°ÐºÐ¶Ðµ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÐžÐœÐŽÐµÐºÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ.ÐÐŸÐŽ "Ð Ð°Ð·ÐŽÐµÐ»Ð°ÐŒÐž ÐŽÐžÐ·Ð°Ð¹ÐœÐ°" ÑÐµÐ»ÐºÐœÐžÑÐµ ÐžÐœÐŽÐµÐºÑÑ Ð¿ÐŸÐžÑÐºÐ°.</Text>
+<Text id="367">Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐžÐœÐŽÐµÐºÑ,Ð²Ð²ÐµÐŽÐžÑÐµ ÐžÐŒÑ ÐŽÐ»Ñ ÐœÐµÐ³ÐŸ Ð² Ð¿ÐŸÐ»Ðµ "ÐÐŒÑ ÐžÐœÐŽÐµÐºÑÐ°".ÐÑÐ±ÐµÑÐžÑÐµ, ÐºÐ°ÐºÐžÐµ ÐžÐ· Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÑ
+ ÐžÑÑÐŸÑÐœÐžÐºÐŸÐ² ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž Ð¿ÑÐžÑÐŸÐµÐŽÐžÐœÐžÑÑ Ðº ÐžÐœÐŽÐµÐºÑÑ, ÑÐµÐ»ÐºÐ°Ñ ÐœÐ° Ð¿ÐŸÐ»Ðµ ÐŸÐºÐŸÐ»ÐŸ ÐœÐžÑ
+. Ð¡Ð¿ÐžÑÐŸÐº Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð²ÑÐµ Ð·Ð°ÐŽÐ°ÐœÐœÑÐµ ÑÐ»ÐµÐŒÐµÐœÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, Ð° ÑÐ°ÐºÐ¶Ðµ Ð¿ÐŸÐ»ÐœÑÐ¹ ÑÐµÐºÑÑ. Ð Ð°ÑÐ¿ÐŸÐ»Ð°Ð³Ð°Ñ Ð²ÑÐ±ÑÐ°ÐœÐœÑÐŒÐž ÐžÑÑÐŸÑÐœÐžÐºÐ°ÐŒÐž ÐŽÐ°ÐœÐœÑÑ
+, Ð²ÑÐ±ÐµÑÐžÑÐµ ÑÑÐµÐ¿ÐµÐœÑ ÐŽÐµÑÐ°Ð»ÐžÐ·Ð°ÑÐžÐž ÐžÐœÐŽÐµÐºÑÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐŒÐµÐœÑ "ÐÐ° ÑÑÐŸÐ²ÐœÐµ". ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÑÑÐž ÐŽÐµÑÐ°Ð»Ðž ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ,Ð¿ÑÐœÐºÑ "ÐÐŸÐ±Ð°Ð²ÐžÑÑ ÐžÐœÐŽÐµÐºÑ" ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ Ð°ÐºÑÐžÐ²ÐœÑÐŒ (ÐµÑÐ»Ðž ÐœÐµÑ ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ³ÐŸ ÐžÐœÐŽÐµÐºÑÐ° Ñ ÑÐµÐŒÐž Ð¶Ðµ ÑÐ°ÐŒÑÐŒÐž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐ°ÐŒÐž).Ð©ÐµÐºÐœÐžÑÐµ ÐœÐ° ÐœÑÐŒ, ÑÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐœÐŸÐ²ÑÐ¹ ÐžÐœÐŽÐµÐºÑ.</Text>
+<Text id="368">Ð§ÑÐŸÐ±Ñ ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐžÐœÐŽÐµÐºÑ, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ Ðž ÐžÐ·ÐŒÐµÐœÐžÑÐµ ÐŽÐµÑÐ°Ð»Ðž. ÐÐŸÐŽÑÐ²ÐµÑÐŽÐžÑÐµ, ÐœÐ°Ð¶Ð°Ð² ÐœÐ° "ÐÐ°ÐŒÐµÐœÐžÑÑ ÐžÐœÐŽÐµÐºÑ".</Text>
+<Text id="369">Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÐžÐœÐŽÐµÐºÑ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÑ
+ ÐžÐœÐŽÐµÐºÑÐŸÐ² Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ ÐžÐœÐŽÐµÐºÑ".</Text>
+<Text id="370">Ð§ÑÐŸÐ±Ñ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐžÐœÐŽÐµÐºÑ ÐžÐ· ÑÐºÐŸÐœÐ²ÐµÑÑÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐ³ÐŸ ÑÐµÐºÑÑÐ° Ðž Ð²ÑÐµÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐœÐ°Ð¶ÐŒÐžÑÐµ "ÐÑÐ±ÑÐ°ÑÑ ÐÑÐµ".</Text>
+<Text id="371">ÐÐœÐŽÐµÐºÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ - ÑÐŸÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐœÐ° Ð¿ÐŸÐžÑÐºÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž,Ð¿ÐŸÐŒÐµÑÐµÐœ ÑÑÐ³Ð°ÐŒÐž "[ÐÐœÐŽÐµÐºÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ]" Ð² ÑÐ¿ÐžÑÐºÐµ "ÐÐ°ÐŽÐ°ÐœÐœÑÐµ ÐžÐœÐŽÐµÐºÑÑ".Ð§ÑÐŸÐ±Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÐµÐ³ÐŸ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐžÐœÐŽÐµÐºÑ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ".</Text>
+<Text id="372">ÐÑÐ»Ðž Ð¿ÐŸÐ·Ð²ÐŸÐ»ÐµÐœ ÑÐ°ÑÑÐžÑÐµÐœÐœÑÐ¹ Ð¿ÐŸÐžÑÐº (ÑÐµÑÐµÐ· Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑ Ð²ÐžÐŽÐŸÐ² Ð¿ÐŸÐžÑÐºÐ°), ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐžÐœÐŽÐµÐºÑÐŸÐŒ ÐŸÑÐ»ÐžÑÐ°ÐµÑÑÑ. ÐÐŒÐµÐµÑÑÑ ÐœÐŸÐ²ÑÐ¹ ÐžÑÑÐŸÑÐœÐžÐº Ð¿ÑÐµÐ²ÐŽÐŸÐŽÐ°ÐœÐœÑÑ
+ "Ð²ÑÐµ Ð¿ÐŸÐ»Ñ",ÐºÐŸÑÐŸÑÑÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÑÑ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ Ð²ÑÐµÐŒ ÑÐºÐ°Ð·Ð°ÐœÐœÑÐŒ ÐžÐœÐŽÐµÐºÑÐ°ÐŒ ÑÑÐ°Ð·Ñ.Ð£ÑÐŸÐ²ÐœÐž ÐœÐµ Ð¿ÑÐžÐ²ÑÐ·Ð°ÐœÑ Ðº ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸÐŒÑ ÐžÐœÐŽÐµÐºÑÑ,Ð° Ð¿ÑÐžÐŒÐµÐœÑÑÑÑÑ ÐºÐŸ Ð²ÑÐµÐŒ ÐžÐœÐŽÐµÐºÑÐ°ÐŒ.Ð¢Ð°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ,ÐžÐœÐŽÐµÐºÑÑ Ðž ÑÑÐŸÐ²ÐœÐž ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑÑÑ ÐŸÑÐŽÐµÐ»ÑÐœÐŸ. "ÐÐŸÐ±Ð°Ð²ÐžÑÑ ÐÑÐµ" ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐŸÑÐŽÐµÐ»ÑÐœÑÐ¹ ÐžÐœÐŽÐµÐºÑ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ Ð¿ÐŸÐ»Ñ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ Ð² ÑÑÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ. </Text>
+<Text id="373">ÐÐŒÑ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐžÐœÐŽÐµÐºÑÐ° Ð±ÑÐŽÐµÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÑÐ²ÑÐ·Ð°ÐœÐŸ Ñ ÐžÐŒÐµÐœÐµÐŒ ÐžÑÑÐŸÑÐœÐžÐºÐ°.Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐžÐŒÑ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐžÐœÐŽÐµÐºÑ,ÐžÐ·ÐŒÐµÐœÐžÑÐµ ÐµÐ³ÐŸ ÐŽÐµÑÐ°Ð»Ðž Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐ°ÐŒÐµÐœÐžÑÑ ÐžÐœÐŽÐµÐºÑ".</Text>
+</Content>
+</Part>
+<Part id="partition_indexes">
+<Title>
+<Text id="374">ÐÐœÐŽÐµÐºÑÑ ÑÐ°Ð·Ð±ÐžÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="375">ÐÐœÐŽÐµÐºÑÑ Ð¿ÐŸÑÑÑÐŸÐµÐœÑ ÐœÐ° ÐŽÐµÑÐ°Ð»ÑÐœÐŸÐŒ ÑÐµÐºÑÑÐµ ÐžÐ»Ðž ÐžÑÑÐŸÑÐœÐžÐºÐ°Ñ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. ÐÐµÑÑÐŸ Ð¿ÐŸÐžÑÐºÐ° ÐŒÐŸÐ¶ÐµÑ Ð² ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÐµÐŒ ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑÑÑ Ð¿ÑÑÑÐŒ ÑÐ°Ð·Ð±ÐžÐµÐœÐžÑ ÐžÐœÐŽÐµÐºÑÐŸÐ² Ð»ÐžÐ±ÐŸ Ð¿ÐŸ ÑÐ·ÑÐºÑ ÐžÐ»Ðž Ð¿ÐŸ ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐŒ ÑÐžÐ»ÑÑÑÐ°ÐŒ.Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑÑÑ,ÐºÐ°Ðº ÑÑÐŸ ÑÐŽÐµÐ»Ð°ÑÑ. ÐÐœÑÑÑÐž "Ð Ð°Ð·ÐŽÐµÐ»ÐŸÐ² ÐŽÐžÐ·Ð°Ð¹ÐœÐ°" ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐœÐŽÐµÐºÑÑ ÑÐ°Ð·Ð±ÐžÐµÐœÐžÑ".</Text>
+<Text id="376">ÐÐžÐŽ "ÐÐœÐŽÐµÐºÑÑ ÑÐ°Ð·Ð±ÐžÐµÐœÐžÑ" ÐžÐŒÐµÐµÑ ÑÑÐž Ð·ÐœÐ°ÑÐµÐœÐžÑ:"ÐÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÑÐžÐ»ÑÑÑÑ","ÐÐ°Ð·ÐœÐ°ÑÐžÑÑ ÑÐ°Ð·Ð±ÐžÐµÐœÐžÐµ" Ðž "ÐÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÑÐ·ÑÐºÐž". ÐÐ»Ñ ÑÐŸÐ³ÐŸ ÑÑÐŸÐ±Ñ Ð±ÐŸÐ»ÑÑÐµ ÑÐ·ÐœÐ°ÑÑ ÐŸ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÐž, ÑÐžÑÐ°Ð¹ÑÐµ ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+ Ðž Ð¿ÐŸÐŽÐžÐœÐŽÐµÐºÑÐ°Ñ
+ Ð² Ð³Ð»Ð°Ð²Ðµ 2 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° Greenstone.</Text>
+<Text id="377">Ð­ÐºÑÐ°Ðœ ÐÐœÐŽÐµÐºÑÐŸÐ² Ð Ð°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐµÐœ ÑÐŸÐ»ÑÐºÐŸ Ð² ÑÐµÐ¶ÐžÐŒÐ°Ñ
+ Ð¡Ð¿ÐµÑÐžÐ°Ð»ÐžÑÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÑ
+ Ð¡ÐžÑÑÐµÐŒ Ðž Ð­ÐºÑÐ¿ÐµÑÑ (ÑÐŒ. ÐÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÑ). ÐÐ°ÐŒÐµÑÑÑÐµ, ÑÑÐŸ ÐŸÐ±ÑÐµÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ Ð¿ÑÐŸÐžÐ·Ð²ÐµÐŽÐµÐœÐœÑÑ
+ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÐ¹ ÑÐ²Ð»ÑÐµÑÑÑ ÐºÐŸÐŒÐ±ÐžÐœÐ°ÑÐžÐµÐ¹ Ð²ÑÐµÑ
+ ÐžÐœÐŽÐµÐºÑÐŸÐ², ÑÐžÐ»ÑÑÑÐŸÐ² ÑÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð²ÑÐ±ÑÐ°ÐœÐœÑÑ
+ ÑÐ·ÑÐºÐŸÐ². ÐÐ²Ð° ÐžÐœÐŽÐµÐºÑÐ° Ñ ÐŽÐ²ÑÐŒÑ ÑÐžÐ»ÑÑÑÐ°ÐŒÐž ÑÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÐŸ ÐŽÐ²ÑÐŒ ÑÐ·ÑÐºÐ°ÐŒ Ð¿ÑÐžÐ²ÐµÐ»ÐŸ Ð±Ñ Ðº Ð²ÐŸÑÑÐŒÐž ÐžÐœÐŽÐµÐºÑÐ°ÐŒ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ.</Text>
+</Content>
+</Part>
+<Part id="define_filters">
+<Title>
+<Text id="378">ÐÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÑÐžÐ»ÑÑÑÑ</Text>
+</Title>
+<Content>
+<Text id="379">Ð€ÐžÐ»ÑÑÑÑ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ ÐÐ°ÐŒ Ð³ÑÑÐ¿Ð¿ÐžÑÐŸÐ²Ð°ÑÑ Ð² Ð¿ÐŸÐŽÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð²ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÐŸ ÐžÐœÐŽÐµÐºÑÑ,ÐŽÐ»Ñ ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÐµÑ Ð·Ð°ÐŽÐ°ÐœÐœÐŸÐ¹ ÐŒÐŸÐŽÐµÐ»Ðž.</Text>
+<Text id="380">Ð§ÑÐŸÐ±Ñ ÑÐŸÐ·ÐŽÐ°ÑÑ ÑÐžÐ»ÑÑÑ,ÑÐµÐ»ÐºÐœÐžÑÐµ ÐºÐ»Ð°Ð²ÐžÑÑ "ÐÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÑÐžÐ»ÑÑÑÑ" Ðž Ð²Ð²ÐµÐŽÐžÑÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐŽÐ»Ñ ÐœÐŸÐ²ÐŸÐ³ÐŸ ÑÐžÐ»ÑÑÑÐ° Ð² Ð¿ÐŸÐ»Ðµ "ÐÐŒÑ ÑÐžÐ»ÑÑÑÐ° ÑÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž:".ÐÐ°ÑÐµÐŒ Ð²ÑÐ±ÐµÑÐžÑÐµ Ñ
+Ð°ÑÐ°ÐºÑÐµÑÐœÑÐµ Ð¿ÑÐžÐ·ÐœÐ°ÐºÐž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°, ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐµ ÐžÐ»Ðž ÑÐ»ÐµÐŒÐµÐœÑÐ°ÐŒ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+,ÐžÐ»Ðž ÐœÐ°Ð·Ð²Ð°ÐœÐžÑ ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÐµÐŒÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð°.ÐÐ²ÐµÐŽÐžÑÐµ Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸÐµ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÐµ,ÑÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð² ÑÐµÑÐµÐœÐžÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ ÑÑÐŸÐ³ÐŸ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÑ.ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐºÐ»ÑÑÐ°ÑÑ "ÐÐºÐ»ÑÑÐµÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²", ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑ ÑÐžÐ»ÑÑÑÑ, ÐžÐ»Ðž "ÐÑÐºÐ»ÑÑÐµÐœÐžÐµ" ÐžÑ
+.ÐÐ°ÐºÐŸÐœÐµÑ,ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ Ð»ÑÐ±ÐŸÐ¹ ÑÑÐ°ÐœÐŽÐ°ÑÑ PERL, Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÑÐµ ÑÐ»Ð°Ð³Ðž Ð²ÑÑÐ°Ð¶ÐµÐœÐžÑ,ÑÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð¿ÑÐž ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ("i" ÐŽÐ»Ñ ÑÐ»ÑÑÐ°Ñ ÐœÐµÑÑÐ²ÑÑÐ²ÐžÑÐµÐ»ÑÐœÐŸÐ³ÐŸ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÑ),ÐÐ°ÐºÐŸÐœÐµÑ,ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐŸÐ±Ð°Ð²ÐžÑÑ ÑÐžÐ»ÑÑÑ",ÑÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÑÐžÐ»ÑÑÑ Ðº ÑÐ¿ÐžÑÐºÑ "Ð€ÐžÐ»ÑÑÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÑÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹".</Text>
+<Text id="381">Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÑÐžÐ»ÑÑÑ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ ÑÐžÐ»ÑÑÑ".</Text>
+<Text id="382">Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÑÐžÐ»ÑÑÑ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ°,Ð·Ð°ÐŒÐµÐœÐžÑÐµ Ð»ÑÐ±ÐŸÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ, ÐºÐŸÑÐŸÑÐŸÐµ Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ Ð² ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐž ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµÐŒ Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐ°ÐŒÐµÐœÐžÑÑ ÑÐžÐ»ÑÑÑ",ÑÑÐŸÐ±Ñ Ð·Ð°ÐºÑÐµÐ¿ÐžÑÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ.</Text>
+</Content>
+</Part>
+<Part id="assign_partitions">
+<Title>
+<Text id="383">ÐÐ°Ð·ÐœÐ°ÑÐµÐœÐžÐµ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="384">ÐÐŒÐµÑ Ð·Ð°ÐŽÐ°ÐœÐœÑÐ¹ ÑÐžÐ»ÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐºÐ»Ð°Ð²ÐžÑÑ "ÐÐ°Ð·ÐœÐ°ÑÐžÑÑ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ" ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐžÐœÐŽÐµÐºÑÐŸÐ² ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ ÐžÐ»Ðž ÐŽÐ»Ñ Ð³ÑÑÐ¿Ð¿Ñ ÑÐžÐ»ÑÑÑÐŸÐ². ÐÑÐ±ÐµÑÐžÑÐµ Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÑÐ¹ ÑÐžÐ»ÑÑÑ (ÐžÐ»Ðž ÑÐžÐ»ÑÑÑÑ) ÐžÐ· ÑÐ¿ÐžÑÐºÐ° "ÐÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐžÐ»ÑÑÑÑ ÑÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž", Ð²Ð²ÐµÐŽÐžÑÐµ ÐžÐŒÑ ÐŽÐ»Ñ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ Ð² Ð¿ÐŸÐ»Ðµ "ÐÐŒÑ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ" Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐŸÐ±Ð°Ð²ÐžÑÑ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÐµ".</Text>
+<Text id="385">Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÐµ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÐµ".</Text>
+<Text id="386">Ð§ÑÐŸÐ±Ñ Ð¿ÑÐŸÐžÐ·Ð²ÐµÑÑÐž ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÐµ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÑÑÐ°ÐœÐŸÐ²ÐžÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ".</Text>
+</Content>
+</Part>
+<Part id="assign_languages">
+<Title>
+<Text id="387">ÐÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐ·ÑÐºÐž</Text>
+</Title>
+<Content>
+<Text id="388">Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŽÐµÑÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÐŸ,ÐºÐ°Ðº ÐŸÐ³ÑÐ°ÐœÐžÑÐžÑÑ ÐžÐœÐŽÐµÐºÑÑ Ð¿ÐŸÐžÑÐºÐ° ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐžÐŒÐž ÑÐ·ÑÐºÐ°ÐŒÐž. ÐÑ ÑÐŸÐ²ÐµÑÑÐ°ÐµÑÐµ ÑÑÐŸ Ð¿ÑÐž ÑÐµÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐžÐž ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ,ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐºÐ»Ð°Ð²ÐžÑÑ "ÐÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐ·ÑÐºÐž" Ð² Ð¿ÐµÑÐµÑÐœÐµ "ÐÐœÐŽÐµÐºÑÑ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ".</Text>
+<Text id="389">Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐœÐŸÐ²ÑÐ¹ ÑÐ·ÑÐº ÐŽÐ»Ñ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐºÐ»Ð°Ð²ÐžÑÑ "ÐÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐ·ÑÐºÐž" ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐžÐœÐŽÐµÐºÑÐ° ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ. ÐÑÐ±ÐµÑÐžÑÐµ Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÑÐ¹ ÑÐ·ÑÐº ÐžÐ· ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐµÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ° "Ð¯Ð·ÑÐºÐž ÐŽÐ»Ñ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÑ" Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐŸÐ±Ð°Ð²ÐžÑÑ ÑÐ·ÑÐº".</Text>
+<Text id="390">Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÑÐ·ÑÐº,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° "ÐÑÐ±ÐŸÑÑ ÑÐ·ÑÐºÐ°" Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ ÑÐ·ÑÐº".</Text>
+<Text id="391">Ð§ÑÐŸÐ±Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÑÐ·ÑÐº Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÑÑÐ°ÐœÐŸÐ²ÐºÐ° Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ".</Text>
+</Content>
+</Part>
+<Part id="cross-collection_search">
+<Title>
+<Text id="392">ÐÐŸÐžÑÐº Ð² Ð¿ÐµÑÐµÑÐµÐºÐ°ÑÑÐžÑ
+ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+</Text>
+</Title>
+<Content>
+<Text id="393">Greenstone Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑ Ð¿ÐŸÐžÑÐº Ð² ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+, ÐºÐ°Ðº ÐµÑÐ»Ðž Ð±Ñ ÐŸÐœÐž Ð±ÑÐ»Ðž ÐŸÐ±ÑÐµÐŽÐžÐœÐµÐœÑ. Ð­ÑÐŸ ÑÐŽÐµÐ»Ð°ÐœÐŸ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÐºÐ°Ð·Ð°ÐœÐžÑ ÑÐ¿ÐžÑÐºÐ° ÐŽÑÑÐ³ÐžÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, Ð² ÐºÐŸÑÐŸÑÑÑ
+ ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœ Ð¿ÐŸÐžÑÐº Ð²ÐŒÐµÑÑÐµ Ñ ÐœÐ°ÑÑÐŸÑÑÐµÐ¹. Ð "Ð Ð°Ð·ÐŽÐµÐ»Ð°Ñ
+ ÐŽÐžÐ·Ð°Ð¹ÐœÐ°" ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐŸÐžÑÐº Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+".</Text>
+<Text id="394">ÐÐµÐ¶ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐŸÐœÐœÑÐ¹ Ð¿ÐŸÐžÑÐº Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐºÐŸÐœÑÑÐŸÐ»ÑÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº ÐŽÐŸÑÑÑÐ¿ÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹.Ð¢ÐµÐºÑÑÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð¿ÐŸÐŒÐµÑÐµÐœÑ Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐŸÑÑÐµÑÐœÐ°. Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐŽÑÑÐ³ÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð² ÐºÐŸÑÐŸÑÑÑ
+ Ð¿ÐŸÐžÑÐº Ð±ÑÐŽÐµÑ Ð¿ÑÐŸÐ²ÐŸÐŽÐžÑÑÑÑ Ð¿Ð°ÑÐ°Ð»Ð»ÐµÐ»ÑÐœÐŸ, ÑÐµÐ»ÐºÐœÐžÑÐµ ÐœÐ° ÐœÐžÑ
+ Ð² ÑÐ¿ÐžÑÐºÐµ (ÑÐµÐ»ÐºÐœÐžÑÐµ ÑÐœÐŸÐ²Ð°, ÑÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÐžÑ
+). ÐÑÐ»Ðž ÐŸÑÐŸÐ±ÑÐ°ÐœÐ° ÑÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐœÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÑÐŸ ÐŒÐµÐ¶ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐŸÐœÐœÑÐ¹ Ð¿ÐŸÐžÑÐº ÐœÐµÐ²ÐŸÐ·ÐŒÐŸÐ¶ÐµÐœ.</Text>
+<Text id="395">ÐÑÐ»Ðž ÐžÐœÐŽÐžÐ²ÐžÐŽÑÐ°Ð»ÑÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐµ ÐžÐŒÐµÑÑ ÐŸÐŽÐžÐœÐ°ÐºÐŸÐ²ÑÑ
+ ÐžÐœÐŽÐµÐºÑÐŸÐ² (Ð²ÐºÐ»ÑÑÐ°Ñ ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÑ ÐœÐ° ÑÑÐ±ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž ÑÐ°Ð·ÐŽÐµÐ»ÐµÐœÐžÐµ Ð¿ÐŸ ÑÐ·ÑÐºÐ°ÐŒ) Ñ ÐŽÑÑÐ³ÐžÐŒÐž, ÑÐŸ Ð¿ÐµÑÐµÐºÑÐµÑÑÐœÑÐ¹ Ð¿ÐŸÐžÑÐº ÐœÐµ Ð±ÑÐŽÐµÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐŽÐŸÐ»Ð¶ÐœÑÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ. ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð±ÑÐŽÐµÑ ÑÐŸÐ»ÑÐºÐŸ ÑÐ¿ÐŸÑÐŸÐ±ÐµÐœ Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑ Ð¿ÐŸÐžÑÐº, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐžÐœÐŽÐµÐºÑÑ, ÐŸÐ±ÑÐžÐµ ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹.</Text>
+<Text id="396">ÐÐ»Ñ ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÐžÑ
+ ÐŽÐµÑÐ°Ð»ÐµÐ¹ ÑÐŒ.Ð³Ð»Ð°Ð²Ñ 1 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° Greenstone.</Text>
+</Content>
+</Part>
+<Part id="browsing_classifiers">
+<Title>
+<Text id="397">ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°</Text>
+</Title>
+<Content>
+<Text id="398">Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ,ÐºÐ°Ðº ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°. Ð "Ð Ð°Ð·ÐŽÐµÐ»Ð°Ñ
+ ÐŽÐžÐ·Ð°Ð¹ÐœÐ°" ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÑÐŸÑÐŒÐŸÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ²".</Text>
+<Text id="399">Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ,ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐžÐ¹ ÑÐ¿ÐžÑÐŸÐº "ÐÑÐ±ÐŸÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ° ÐŽÐ»Ñ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÑ" Ð²ÐœÐžÐ·Ñ ÐŸÐºÐœÐ°,Ðž Ð·Ð°ÑÐµÐŒ ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐŸÐ±Ð°Ð²ÑÑÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ". ÐÐŸÑÐ²Ð»ÑÐµÑÑÑ ÐŸÐºÐœÐŸ, ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÐŸÐµ "ÐÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ²".ÐÐœÑÑÑÑÐºÑÐžÐž ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ ÐŽÐžÐ°Ð»ÐŸÐ³Ð° ÑÐµ Ð¶Ðµ ÑÐ°ÐŒÑÐµ,ÑÑÐŸ ÐºÐ°ÑÐ°ÑÑÑÑ Ð¿Ð»Ð°Ð³ÐžÐœÐŸÐ² (ÐÐ»Ð°Ð³ÐžÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°).ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐÑ ÑÑÐŸÑÐŒÐžÑÐŸÐ²Ð°Ð»Ðž ÐœÐŸÐ²ÑÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ, ÐŸÐœ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑÑÑ Ð² ÐºÐŸÐœÐµÑ ÑÐ¿ÐžÑÐºÐ° "Ð¢ÐµÐºÑÑÐžÐµ Ð·Ð°ÐŽÐ°ÐœÐœÑÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ".</Text>
+<Text id="400">Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ".</Text>
+<Text id="401">Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐ°, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐŸÐœÑÐžÐ³ÑÑÐžÑÑÐ¹ÑÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ." (ÐžÐ»Ðž ÑÐµÐ»ÐºÐœÑÑÑ ÐŽÐ²Ð° ÑÐ°Ð·Ð° ÐœÐ° ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐµ Ð² ÑÐ¿ÐžÑÐºÐµ).</Text>
+<Text id="402">ÐÐŸÑÑÐŽÐŸÐº ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ² Ð² ÐœÐ°Ð²ÐžÐ³Ð°ÑÐžÐŸÐœÐœÐŸÐ¹ Ð»ÐžÐœÐµÐ¹ÐºÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐž ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÐµÑ ÑÐŸÐŒÑ,ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ Ð·ÐŽÐµÑÑ.Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ Ð¿ÐŸÑÑÐŽÐŸÐº,Ð²ÑÐ±ÐµÑÐžÑÐµ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÐÑ Ñ
+ÐŸÑÐžÑÐµ Ð¿ÐµÑÐµÐŒÐµÑÑÐžÑÑ, Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐ²ÐžÐ³Ð°ÑÑÑÑ Ð²Ð²ÐµÑÑ
+" ÐžÐ»Ðž "ÐÐ²ÐžÐ³Ð°ÑÑÑÑ Ð²ÐœÐžÐ·".</Text>
+<Text id="403">ÐÐ»Ñ ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÐµÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐŸÑÐœÐŸÑÐžÑÐµÐ»ÑÐœÐŸ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐ² ÑÐžÑÐ°Ð¹ÑÐµ Ð³Ð»Ð°Ð²Ñ 2 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° Greenstone.</Text>
+</Content>
+</Part>
+<Part id="format_features">
+<Title>
+<Text id="404">ÐÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž ÑÐŸÑÐŒÐ°ÑÐ°</Text>
+</Title>
+<Content>
+<Text id="405">ÐÐµÐ±-ÑÑÑÐ°ÐœÐžÑÑ, ÐºÐŸÑÐŸÑÑÐµ ÐÑ Ð²ÐžÐŽÐžÑÐµ, ÐºÐŸÐ³ÐŽÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ Greenstone, ÐœÐµ ÑÐ²Ð»ÑÑÑÑÑ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÐœÑÐŒÐž, Ð° ÑÐŸÐ·ÐŽÐ°ÑÑÑÑ "ÐœÐ° Ð»ÐµÑÑ", ÐºÐŸÐ³ÐŽÐ° Ð² ÐœÐžÑ
+ ÐµÑÑÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÑÑÑ. ÐÐŸÐŒÐ°ÐœÐŽÑ ÑÐŸÑÐŒÐ°ÑÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÑ ÑÑÐžÑ
+ ÑÐ³ÐµÐœÐµÑÐžÑÐŸÐ²Ð°ÐœÐœÑÑ
+ ÑÑÑÐ°ÐœÐžÑ. ÐÐœÐž Ð·Ð°ÑÑÐ°Ð³ÐžÐ²Ð°ÑÑ ÑÐ°ÐºÐžÐµ Ð²ÐµÑÐž,ÐºÐ°Ðº ÐŒÐµÑÑÐŸ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÑ ÐºÐœÐŸÐ¿ÐºÐž,ÐºÐŸÐ³ÐŽÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ,Ðž ÐºÐ°ÐºÐžÐµ ÑÐ²ÑÐ·Ðž ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÑÑÑÑ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÐŸÐŒ DateList. ÐÐŸÐŒÐ°ÐœÐŽÑ ÑÐŸÑÐŒÐ°ÑÐ° ÐœÐµ Ð»ÐµÐ³ÐºÐŸ ÑÐ°Ð·ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÑÑ,Ðž ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ Ð¿ÑÐŸÑÐžÑÐ°ÑÑ Ð³Ð»Ð°Ð²Ñ 2 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° Greenstone. Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ±ÑÑÐ¶ÐŽÐ°ÑÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÑÐŸÑÐŒÐ°ÑÐ° Ðž ÑÐŸ, ÐºÐ°Ðº ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐµÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÐœÐžÐŒ. Ð "Ð Ð°Ð·ÐŽÐµÐ»Ð°Ñ
+ ÐŽÐžÐ·Ð°Ð¹ÐœÐ°" ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž ÑÐŸÑÐŒÐ°ÑÐ°".</Text>
+<Text id="406">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐžÐŒÐµÐœÐžÑÑ ÐºÐŸÐŒÐ°ÐœÐŽÑ ÑÐŸÑÐŒÐ°ÑÐ° Ðº ÑÐµÐŒÑ-ÐœÐžÐ±ÑÐŽÑ Ð² ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐµÐŒ ÑÐ¿ÐžÑÐºÐµ "ÐÑÐ±ÐŸÑ ÑÑÐµÐŽÑÑÐ²",ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐºÐ°Ð¶ÐŽÑÐ¹ ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ Ðž Ð²ÑÑÑÐŸÐµÐœÐœÑÐ¹ ÑÐ¿ÐžÑÐŸÐº ÑÑÐµÐŽÑÑÐ². ÐÐŸÐ³ÐŽÐ° ÐÑ Ð²ÑÐ±ÐžÑÐ°ÐµÑÐµ ÑÑÐµÐŽÑÑÐ²Ð°, ÐµÑÑÑ ÐŽÐ²Ð° ÑÐžÐ¿Ð° ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÑÑÐµÐŽÑÑÐ²Ð° ÑÐ²Ð»ÑÑÑÑÑ Ð¿ÑÐŸÑÑÐŸ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž ÐžÐ»Ðž ÐœÐµÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž,ÐŸÐœÐž ÑÐ¿ÑÐ°Ð²Ð»ÑÑÑÑÑ ÐºÐœÐŸÐ¿ÐºÐ°ÐŒÐž. ÐÑÑÐ³ÐžÐµ ÑÑÐµÐ±ÑÑÑ, ÑÑÐŸÐ±Ñ Ð±ÑÐ»Ð° ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐ° ÑÐŸÑÐŒÐ°ÑÐœÐ°Ñ ÑÑÑÐŸÐºÐ°. ÐÐ»Ñ ÐœÐžÑ
+ ÐžÐŒÐµÐµÑÑÑ ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐžÐ¹ ÑÐ¿ÐžÑÐŸÐº "ÐÐŸÐ·ÐŽÐµÐ¹ÑÑÐ²ÑÑÑÐžÐ¹ ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑ", ÑÑÐŸÐ±Ñ Ð²ÑÐ±ÑÐ°ÑÑ, Ðº ÐºÐ°ÐºÐŸÐ¹ ÑÐ°ÑÑÐž ÑÑÐµÐŽÑÑÐ² ÑÑÑÐŸÐºÐ° ÐŸÐ±ÑÐ°ÑÐ°ÐµÑÑÑ,ÐµÑÐ»Ðž ÑÑÐŸ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ, ÐŸÐ±Ð»Ð°ÑÑÑ ÑÐµÐºÑÑÐ° ("Ð¡ÑÑÐŸÐºÐ° ÑÐŸÑÐŒÐ°ÑÐ° HTML") ÐŽÐ»Ñ Ð²Ð²ÐŸÐŽÐ° ÑÑÑÐŸÐºÐž, Ðž Ð²ÑÐ±ÐŸÑ Ð·Ð°ÐŽÐ°ÐœÐœÑÑ
+ "ÐÐµÑÐµÐŒÐµÐœÐœÑÑ
+". Ð§ÑÐŸÐ±Ñ Ð²ÑÑÐ°Ð²ÐžÑÑ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÑ Ð² ÑÐµÐºÑÑÑÑ Ð¿ÐŸÐ·ÐžÑÐžÑ Ð² ÑÐŸÑÐŒÐ°ÑÐœÑÑ ÑÑÑÐŸÐºÑ, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÑ ÐžÐ· ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐµÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÑÑÐ°Ð²ÐžÑÑ".</Text>
+<Text id="407">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÑÐŸÑÐŒÐ°Ñ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐŽÐ»Ñ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐŸÐ³ÐŸ ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑÐ°, Ð²ÑÐ±ÐžÑÐ°Ñ Ð±Ð»Ð°ÐœÐº ÑÐ²ÐŸÐ¹ÑÑÐ². Ð­ÑÐŸÑ ÑÐŸÑÐŒÐ°Ñ Ð·Ð°ÑÐµÐŒ Ð¿ÑÐžÐŒÐµÐœÑÐµÑÑÑ ÐºÐŸ Ð²ÑÐµÐŒ Ð¿ÑÐžÐŒÐµÐœÐžÐŒÑÐŒ ÑÐ²ÐŸÐ¹ÑÑÐ²Ð°ÐŒ, ÐµÑÐ»Ðž ÐŽÑÑÐ³ÐŸÐµ ÐœÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐŸ.</Text>
+<Text id="408">Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐœÐŸÐ²ÑÑ ÐºÐŸÐŒÐ°ÐœÐŽÑ ÑÐŸÑÐŒÐ°ÑÐ°,Ð²ÐœÐµÑÐžÑÐµ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ,ÐºÐ°Ðº ÐŸÐ±ÑÑÑÐœÐµÐœÐŸ Ð²ÑÑÐµ, Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐŸÐ±Ð°Ð²ÐžÑÑ ÑÐŸÑÐŒÐ°Ñ".ÐÐŸÐ²Ð°Ñ ÐºÐŸÐŒÐ°ÐœÐŽÐ° ÑÐŸÑÐŒÐ°ÑÐ° Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ Ð² ÑÐ¿ÐžÑÐºÐµ "Ð¢ÐµÐºÑÑÐžÐµ Ð·Ð°ÐŽÐ°ÐœÐœÑÐµ ÐºÐŸÐŒÐ°ÐœÐŽÑ ÑÐŸÑÐŒÐ°ÑÐ°".Ð¢ÐŸÐ»ÑÐºÐŸ ÐŸÐŽÐœÐ° ÐºÐŸÐŒÐ°ÐœÐŽÐ° ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÑÐ²ÑÐ·Ð°ÐœÐ° Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐºÐŸÐŒÐ±ÐžÐœÐ°ÑÐžÐµÐ¹ ÑÐ²ÐŸÐ¹ÑÑÐ²ÐŸ/ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑ.</Text>
+<Text id="409">Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÐºÐŸÐŒÐ°ÐœÐŽÑ ÑÐŸÑÐŒÐ°ÑÐ°, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÑ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ ÑÐŸÑÐŒÐ°Ñ".</Text>
+<Text id="410">Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐºÐŸÐŒÐ°ÐœÐŽÑ ÑÐŸÑÐŒÐ°ÑÐ°, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÑ ÐŒÐ· ÑÐ¿ÐžÑÐºÐ°, ÐžÐ·ÐŒÐµÐœÐžÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐ°ÐŒÐµÐœÐžÑÑ ÑÐŸÑÐŒÐ°Ñ".</Text>
+<Text id="411">ÐÐ° ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹ ÐŸ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÑ
+ Ðž ÐºÐŸÐŒÐ¿ÐŸÐœÐµÐœÑÐ°Ñ
+ ÑÑÐµÐŽÑÑÐ² ÐŸÐ±ÑÐ°ÑÐžÑÐµÑÑ Ðº Ð³Ð»Ð°Ð²Ðµ 2 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° Greenstone.</Text>
+<Text id="412">ÐÑÐ»Ðž ÐºÐœÐŸÐ¿ÐºÐ° "ÐÐŸÐ·Ð²ÐŸÐ»ÐµÐœÐœÑÐµ ÑÐ°ÑÑÐžÑÐµÐœÐœÑÐµ Ð²Ð°ÑÐžÐ°ÐœÑÑ" Ð¿ÐŸÐŒÐµÑÐµÐœÐ°,ÑÐŸ ÑÐ°Ð·ÑÐµÑÐµÐœÑ ÐœÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÑÐŸÐŽÐ²ÐžÐœÑÑÑÐµ Ð²Ð°ÑÐžÐ°ÐœÑÑ ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÑ . Ð¡Ð¿ÐžÑÐŸÐº ÑÑÐµÐŽÑÑÐ², ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÑ, ÐœÐµÐŒÐœÐŸÐ³ÐŸ ÐžÐ·ÐŒÐµÐœÐµÐœ Ðž Ð±ÐŸÐ»ÑÑÐµÐµ ÑÐžÑÐ»ÐŸ Ð¿ÐµÑÐµÐŒÐµÐœÐœÑÑ
+ ÐŽÐŸÑÑÑÐ¿ÐœÐŸ ÐŽÐ»Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐŒÐ°ÐœÐŽÐŸÐ¹ ÑÐŸÑÐŒÐ°ÑÐ°, ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°Ñ Ð±ÐŸÐ»ÑÑÐµÐµ ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÑÑÑÐ°ÐœÐžÑÐµÐ¹ ÐŸÑÐžÐ³ÐžÐœÐ°Ð»-ÐŒÐ°ÐºÐµÑÐ°.</Text>
+</Content>
+</Part>
+<Part id="translate_text">
+<Title>
+<Text id="413">ÐÐµÑÐµÐ²ÐŸÐŽ ÑÐµÐºÑÑÐ°</Text>
+</Title>
+<Content>
+<Text id="414">Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ Ð¿ÐµÑÐµÐ²ÐŸÐŽÐ°, Ð³ÐŽÐµ ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ ÑÐ·ÑÐº ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ ÑÑÐ°Ð³ÐŒÐµÐœÑÐŸÐ² ÑÐµÐºÑÑÐ° ÐŽÐ»Ñ ÑÐ°ÑÑÐµÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð "Ð Ð°Ð·ÐŽÐµÐ»Ðµ ÐŽÐžÐ·Ð°Ð¹ÐœÐ°" ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐµÑÐµÐ²ÐµÑÑÐž ÑÐµÐºÑÑ".</Text>
+<Text id="415">Ð¡ÐœÐ°ÑÐ°Ð»Ð° Ð²ÑÐ±ÐµÑÐžÑÐµ Ð²Ñ
+ÐŸÐŽ Ð² ÑÐ¿ÐžÑÐŸÐº "Ð¡Ð²ÐŸÐ¹ÑÑÐ²Ð°". ÐÐžÐ¶Ðµ Ð¿ÐŸÑÐ²ÑÑÑÑ ÑÑÑÐŸÐºÐž ÑÐ¿ÐµÑÐžÑÐžÑÐœÐŸÐ³ÐŸ ÑÐ·ÑÐºÐ°, ÑÐ²ÑÐ·Ð°ÐœÐœÑÐµ Ñ ÑÑÐžÐŒ ÑÐ²ÐŸÐ¹ÑÑÐ²ÐŸÐŒ. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐžÐ¹ ÑÐ¿ÐžÑÐŸÐº "Ð¯Ð·ÑÐº Ð¿ÐµÑÐµÐ²ÐŸÐŽÐ°",ÑÑÐŸÐ±Ñ Ð²ÑÐ±ÑÐ°ÑÑ ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐ¹ ÑÐ·ÑÐº Ðž Ð²Ð²ÐµÑÑÐž Ð¿ÐµÑÐµÐ²ÐµÐŽÐµÐœÐœÑÐ¹ ÑÐµÐºÑÑ Ð² ÐŸÐ±Ð»Ð°ÑÑÑ ÑÐµÐºÑÑÐ°, ÐŸÐ±ÑÐ°ÑÐ°ÑÑÑ Ðº "ÐÐ°ÑÐ°Ð»ÑÐœÐŸÐŒÑ ÑÑÐ°Ð³ÐŒÐµÐœÑÑ ÑÐµÐºÑÑÐ°",ÐµÑÐ»Ðž ÑÑÐŸ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ. ÐÐŸ ÐŸÐºÐŸÐœÑÐ°ÐœÐžÐž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐŸÐ±Ð°Ð²ÐžÑÑ Ð¿ÐµÑÐµÐ²ÐŸÐŽ".</Text>
+<Text id="416">Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐ¹ Ð¿ÐµÑÐµÐ²ÐŸÐŽ, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ Ð² ÑÐ°Ð±Ð»ÐžÑÐµ "ÐÐ°ÐŽÐ°ÐœÐœÑÐµ Ð¿ÐµÑÐµÐ²ÐŸÐŽÑ" Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ Ð¿ÐµÑÐµÐ²ÐŸÐŽ".</Text>
+<Text id="417">Ð§ÑÐŸÐ±Ñ ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ Ð¿ÐµÑÐµÐ²ÐŸÐŽ, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ, ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÑÐ¹ÑÐµ Ð² ÑÐµÐºÑÑÐŸÐ²ÐŸÐ¹ ÐŸÐ±Ð»Ð°ÑÑÐž "ÐÐµÑÐµÐ²ÐµÐŽÐµÐœÐœÑÐ¹ ÑÐµÐºÑÑ" Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐ°ÐŒÐµÐœÐžÑÑ Ð¿ÐµÑÐµÐ²ÐŸÐŽ".</Text>
+</Content>
+</Part>
+<Part id="metadata_sets">
+<Title>
+<Text id="418">Ð£ÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</Title>
+<Content>
+<Text id="419">Ð­ÑÐŸÑ ÑÐ°Ð·ÐŽÐµÐ» ÐŸÐ±ÑÑÑÐœÑÐµÑ ÐŸÐ±Ð·ÐŸÑÐœÑÑ Ð¿Ð°ÐœÐµÐ»Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+. Ð "Ð Ð°Ð·ÐŽÐµÐ»Ðµ ÐŽÐžÐ·Ð°Ð¹ÐœÐ°" ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+". </Text>
+<Text id="420">Ð­ÑÐŸ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ,ÑÑÐŸÐ±Ñ ÑÐ°ÑÑÐŒÐŸÑÑÐµÑÑ ÐœÐ°Ð±ÐŸÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+,ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹,Ðž ÑÐ»ÐµÐŒÐµÐœÑÑ,ÐºÐŸÑÐŸÑÑÐµ ÑÐ²Ð»ÑÑÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž Ð² Ð¿ÑÐµÐŽÐµÐ»Ð°Ñ
+ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐœÐ°Ð±ÐŸÑÐ°. ÐÑÐ±ÐµÑÐžÑÐµ ÐžÐ· ÑÐ¿ÐžÑÐºÐ° "ÐÐŸÑÑÑÐ¿ÐœÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+",ÑÑÐŸÐ±Ñ Ð²ÐžÐŽÐµÑÑ ÐŽÐµÑÐ°Ð»Ðž ÐžÑ
+ ÑÐ»ÐµÐŒÐµÐœÑÐŸÐ².</Text>
+<Text id="421">Ð§ÑÐŸÐ±Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÑÑÐ³ÐŸÐ¹ ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ Ð·Ð°Ð³ÑÑÐ¶ÐµÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° "ÐÐŸÐ±Ð°Ð²ÐžÑÑ ÐÐ°Ð±ÐŸÑ ÐÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+" Ðž Ð²ÑÐ±ÐµÑÐžÑÐµ ÑÐ°Ð¹Ð» Ñ ÐœÐ°Ð±ÐŸÑÐŸÐŒ ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+ (.mds).</Text>
+<Text id="422">Ð ÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐœÐ°Ð±ÐŸÑÐ° ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐŸ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ Greenstone Editor for Metadata Sets (GEMS). ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐºÐœÐŸÐ¿ÐºÑ "Ð ÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐÐ°Ð±ÐŸÑ ÐÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+", ÑÑÐŸÐ±Ñ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ GEMS.</Text>
+<Text id="423">ÐÑÐ»Ðž ÐœÐ°Ð±ÐŸÑ ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+ Ð²Ð°ÐŒ Ð±ÐŸÐ»ÑÑÐµ ÐœÐµ ÐœÑÐ¶ÐµÐœ, Ð²ÑÐ±ÐµÑÐžÑÐµ ÐµÐ³ÐŸ Ðž ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° "Ð£ÐŽÐ°Ð»ÐžÑÑ ÐÐ°Ð±ÐŸÑ ÐÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+". ÐÑÐ»Ðž Ð²Ñ ÐœÐ°Ð·ÐœÐ°ÑÐžÐ»Ðž ÐºÐ°ÐºÐžÐµ-Ð»ÐžÐ±ÐŸ ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÐµ Ðº ÑÐ»ÐµÐŒÐµÐœÑÐ°ÐŒ Ð² ÑÐŽÐ°Ð»ÐµÐœÐœÐŸÐŒ ÐœÐ°Ð±ÐŸÑÐµ, Ñ Ð²Ð°Ñ ÑÐ¿ÑÐŸÑÑÑ ÐºÐ°Ðº Ñ ÐœÐžÐŒÐž Ð¿ÐŸÑÑÑÐ¿ÐžÑÑ Ð¿ÑÐž ÑÐ»ÐµÐŽÑÑÐµÐ¹ Ð·Ð°Ð³ÑÑÐ·ÐºÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="producing_your_collection">
+<Title>
+<Text id="424">ÐÐŸÑÑÑÐŸÐµÐœÐžÐµ ÐÐ°ÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="425">ÐÐŒÐµÑ ÑÐŸÐ±ÑÐ°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐŽÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð°ÐœÐœÐŸÑÐžÑÐŸÐ²Ð°Ð² ÐžÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž Ðž ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°Ð² ÐŽÐžÐ·Ð°Ð¹Ðœ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž,ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐµÐ¿ÐµÑÑ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Greenstone. Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ,ÐºÐ°Ðº ÑÑÐŸ ÑÐŽÐµÐ»Ð°ÑÑ.</Text>
+<Part id="the_create_view">
+<Title>
+<Text id="426">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="427">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ,ÑÑÐŸÐ±Ñ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ,Ð²ÑÐ¿ÐŸÐ»ÐœÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐµ ÑÑÐµÐœÐ°ÑÐžÐž Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone ÐžÐ· ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž, ÐºÐŸÑÐŸÑÑÑ ÐÑ Ð¿ÐŸÐŽÐ³ÐŸÑÐŸÐ²ÐžÐ»Ðž. Ð©ÐµÐ»ÑÐŸÐº ÐœÐ° "ÐÐŸÑÑÑÐŸÐµÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž" ÐœÐ°ÑÐžÐœÐ°ÐµÑ Ð¿ÑÐŸÑÐµÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐµÐŒÑ, ÐºÐŸÑÐŸÑÐŸÐµ ÐŽÐ»Ñ ÑÑÐŸÐ³ÐŸ Ð¿ÐŸÑÑÐµÐ±ÑÐµÑÑÑ, Ð·Ð°Ð²ÐžÑÐžÑ ÐŸÑ ÑÐ°Ð·ÐŒÐµÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž ÑÐžÑÐ»Ð° ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÐµÐŒÑÑ
+ ÐžÐœÐŽÐµÐºÑÐŸÐ² (ÐŽÐ»Ñ ÐŸÐ³ÑÐŸÐŒÐœÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÑÑÐŸ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ°ÑÑ). ÐÐœÐŽÐžÐºÐ°ÑÐŸÑ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ, ÐœÐ°ÑÐºÐŸÐ»ÑÐºÐŸ Ð²ÑÐ¿ÐŸÐ»ÐœÐµÐœ Ð¿ÑÐŸÑÐµÑÑ. Ð§ÑÐŸÐ±Ñ ÐŸÑÐŒÐµÐœÐžÑÑ Ð¿ÑÐŸÑÐµÑÑ Ð² Ð»ÑÐ±ÐŸÐµ Ð²ÑÐµÐŒÑ, ÐœÐ°Ð¶ÐŒÐžÑÐµ "ÐÑÐŒÐµÐœÐ° Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ".</Text>
+<Text id="428">ÐÐ°Ð¶Ð°Ð² ÐœÐ° "ÐÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÑÐ¹ Ð¿ÑÐŸÑÐŒÐŸÑÑ" Ð¿ÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð±ÑÐ»Ð° ÑÑÐ¿ÐµÑÐœÐŸ ÑÐŸÐ±ÑÐ°ÐœÐ°, ÐŒÐŸÐ¶ÐœÐŸ ÐŸÑÐºÑÑÑÑ Ð²ÐµÐ±-Ð±ÑÐ°ÑÐ·ÐµÑ Ñ Ð³Ð»Ð°Ð²ÐœÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="429">Ð ÐŒÐŸÐŽÑÑÐµ Ð­ÐºÑÐ¿ÐµÑÑ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ Ð·Ð°Ð¿ÐžÑÑ "ÐÐŸÐ³ Ð¡ÐŸÐŸÐ±ÑÐµÐœÐžÐ¹" ÑÐ»ÐµÐ²Ð°, ÑÑÐŸÐ±Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ, Ð±ÑÐ»Ðž Ð»Ðž Ð¿ÑÐµÐŽÑÐŽÑÑÐžÐµ Ð¿ÐŸÐ¿ÑÑÐºÐž ÑÐºÐŸÐœÑÑÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÑÐ¿ÐµÑÐœÑ ÐžÐ»Ðž ÐœÐµÑ. ÐÑÐ±ÐµÑÐžÑÐµ Ð¶ÐµÐ»Ð°ÐµÐŒÑÑ Ð·Ð°Ð¿ÐžÑÑ,ÑÐµÐ»ÐºÐ°Ñ Ð¿ÐŸ Ð²ÑÐ±ÑÐ°ÐœÐœÐŸÐ¹ ÐŽÐ°ÑÐµ Ð² ÑÐ¿ÐžÑÐºÐµ "ÐÑÑÐŸÑÐžÑ Ð·Ð°Ð¿ÐžÑÐž".</Text>
+</Content>
+</Part>
+<Part id="import_and_build_settings">
+<Title>
+<Text id="430">ÐÐŒÐ¿ÐŸÑÑ Ðž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="431">Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ, ÐºÐ°Ðº Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑÐŒ ÐžÐŒÐ¿ÐŸÑÑÐ° Ðž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐ°ÐŒ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ. ÐÐ° ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹ Ð¿ÐŸ ÐžÐŒÐ¿ÐŸÑÑÑ Ðž Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÑÐžÑÐ°Ð¹ÑÐµ Ð³Ð»Ð°Ð²Ñ 1 Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ð° ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° Greenstone.</Text>
+<Text id="432">Ð£Ð¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒÐž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐ°ÐŒÐž ÑÐŽÐµÐ»Ð°ÐœÐŸ Ð¿ÐŸÐŽÐŸÐ±ÐœÐŸ ÑÐŸÐŒÑ ÑÐ¿ÐŸÑÐŸÐ±Ñ, ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÐ¿ÐžÑÐ°Ðœ Ð¿ÑÐž "ÐÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐž Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ²" Ð² ÐÐ»Ð°Ð³ÐžÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°. ÐÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐ»Ñ ÑÑÐµÐ±ÑÑÑ ÑÐžÑÐ»ÐµÐœÐœÑÑ
+ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ². ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑ
+ ÐžÐ»Ðž ÐœÐ°Ð¿ÐµÑÐ°ÑÐ°ÑÑ ÐžÐ»Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÑÑÐµÐ»ÐºÐž Ð²Ð²ÐµÑÑ
+ Ðž Ð²ÐœÐžÐ·, ÑÑÐŸÐ±Ñ ÑÐ²ÐµÐ»ÐžÑÐžÑÑ ÐžÐ»Ðž ÑÐŒÐµÐœÑÑÐžÑÑ ÑÐµÐºÑÑÐµÐµ Ð·ÐœÐ°ÑÐµÐœÐžÐµ (Ð² ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÑÐ»ÑÑÐ°ÑÑ
+ ÐžÐœÑÐµÑÑÐµÐ¹Ñ ÐŸÐ³ÑÐ°ÐœÐžÑÐžÐ²Ð°ÐµÑ ÐŽÐžÐ°Ð¿Ð°Ð·ÐŸÐœ, Ð² ÐºÐŸÑÐŸÑÑÐ¹ ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐŸÐ¹ÑÐž). ÐÑÑÐ³ÐžÐµ Ð¿ÐŸÐ»Ñ ÑÐ²Ð»ÑÑÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž Ð¿ÑÐž ÑÐµÐ»ÑÐºÐµ Ð¿ÐŸ ÐºÐœÐŸÐ¿ÐºÐµ (ÐÐŸÐ²ÑÐŸÑÐœÑÐ¹ ÑÐµÐ»ÑÐŸÐº ÐŽÐµÐ»Ð°ÐµÑ ÐžÑ
+ ÐœÐµÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž).</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="miscellaneous">
+<Title>
+<Text id="433">Ð Ð°Ð·ÐœÐŸÐµ</Text>
+</Title>
+<Content>
+<Text id="434">Ð­ÑÐŸÑ ÑÐ°Ð·ÐŽÐµÐ» ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÑ ÐŸÑÐŸÐ±ÐµÐœÐœÐŸÑÑÐž ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°,ÐºÐŸÑÐŸÑÑÐµ ÐœÐµ ÑÐ²ÑÐ·Ð°ÐœÑ ÐœÐž Ñ ÐºÐ°ÐºÐžÐŒ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐžÐŒ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµÐŒ.</Text>
+<Part id="preferences">
+<Title>
+<Text id="435">ÐÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Text id="436">Ð ÑÑÐŸÐŒ ÑÐ°Ð·ÐŽÐµÐ»Ðµ ÐŸÐ±ÑÑÑÐœÑÐµÑÑÑ ÐŽÐžÐ°Ð»ÐŸÐ³ Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÐ¹,ÐŽÐŸÑÑÑÐ¿ÐœÑÐ¹ Ð¿ÑÐž ÐŸÑÐºÑÑÑÐžÐž "Ð€Ð°Ð¹Ð»Ð°", Ð° Ð·Ð°ÑÐµÐŒ "ÐÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÐ¹".</Text>
+<Text id="437">ÐÐµÑÐ²Ð°Ñ ÐŸÐ¿ÑÐžÑ "ÐÐ±ÑÐµÐµ" - ÑÑÐŸ ÑÐµÐºÑÑÐŸÐ²ÐŸÐµ Ð¿ÐŸÐ»Ðµ ÐŽÐ»Ñ Ð²Ð²ÐµÐŽÐµÐœÐžÑ Ð°ÐŽÑÐµÑÐ° Ð²Ð°ÑÐµÐ¹ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÐŸÐ¹ Ð¿ÐŸÑÑÑ. ÐÐœ Ð±ÑÐŽÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ðœ Ð² Ð·ÐœÐ°ÑÐµÐœÐžÐž ÐŒÐµÑÐ°-ÐŽÐ°ÐœÐœÑÑ
+ "Ð¡ÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ" Ðž "ÐÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÑÐ¹". Ð¡Ð»ÐµÐŽÑÑÐ°Ñ ÐŸÐ¿ÑÐžÑ - ÑÑÐŸ Ð²ÑÐ¿Ð°ÐŽÐ°ÑÑÐµÐµ ÐŒÐµÐœÑ Ñ ÑÐ·ÑÐºÐ°ÐŒÐž, Ð² ÐºÐŸÑÐŸÑÑÑ
+ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐÐœÑÐµÑÑÐµÐ¹Ñ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœ. ÐÑÐ»Ðž ÐÑ ÐžÐ·ÐŒÐµÐœÑÐµÑÐµ ÑÐ»ÐŸÐ²Ð°ÑÑ, Ð²ÑÐ±ÐžÑÐ°Ñ ÐºÐ°ÐºÐŸÐ¹-Ð»ÐžÐ±ÐŸ ÐžÐ· ÑÐ¿ÐžÑÐºÐ°, ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ Ð¿ÐµÑÐµÐ·Ð°Ð³ÑÑÐ·ÐžÑÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ, ÑÑÐŸÐ±Ñ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ ÐœÐŸÐ²ÑÐµ ÑÑÑÐŸÐºÐž ÑÐ·ÑÐºÐ° ÐžÐ· ÑÑÐŸÐ³ÐŸ ÑÐ»ÐŸÐ²Ð°ÑÑ.</Text>
+<Text id="438">ÐÑÐ»Ðž Ð²ÑÐ±ÑÐ°ÐœÐ° "ÐÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐžÐ·Ð²Ð»ÐµÐºÐ°ÐµÐŒÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+", ÑÐ°Ð·Ð»ÐžÑÐœÐŸÐµ ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÐµ, ÑÐ²ÑÐ·Ð°ÐœÐœÐŸÐµ Ñ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐŒÐž, Ð²ÑÐµÐ³ÐŽÐ° Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð²ÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐžÐ·Ð²Ð»ÐµÑÐµÐœÑ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÑÐŒÐµÐœÐ° ÑÑÐŸÐ³ÐŸ Ð²ÑÐ±ÐŸÑÐ° ÑÐºÑÑÐ²Ð°ÐµÑ ÑÑÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, Ñ
+ÐŸÑÑ ÐŸÐœÐž Ð²ÑÑ ÐµÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑ Ð² ÑÐµÑÐµÐœÐžÐµ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐºÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð² ÑÐ°ÐŒÐºÐ°Ñ
+ ÐŸÐºÐŸÐœÑÐ°ÑÐµÐ»ÑÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone. ÐÑÐ»Ðž Ð²ÑÐ±ÑÐ°ÐœÐŸ "ÐÐŸÐºÐ°Ð·Ð°ÑÑ ÑÐ°Ð·ÐŒÐµÑÑ ÑÐ°Ð¹Ð»Ð°", ÑÐŸ ÑÐ°Ð·ÐŒÐµÑ ÑÐ°Ð¹Ð»Ð° Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ ÑÑÐŽÐŸÐŒ Ñ ÐºÐ°Ð¶ÐŽÑÐŒ ÑÐ°Ð¹Ð»ÐŸÐŒ Ð² ÑÐ°Ð±ÐŸÑÐµÐŒ Ð¿ÑÐŸÑÑÑÐ°ÐœÑÑÐ²Ðµ, Ð° ÑÐ°ÐºÐ¶Ðµ Ð² ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐŒ ÐŽÐµÑÐµÐ²Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð² Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑÑ
+ Gather Ðž Enrich.</Text>
+<Text id="439">ÐÐ°ÐœÐµÐ»Ñ "Ð¡Ð¿ÐŸÑÐŸÐ±" ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÑÐ¿ÑÐ°Ð²Ð»ÐµÐœÐžÑ ÑÑÐŸÐ²ÐœÐµÐŒ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÑÑÐµÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°. ÐÐ° ÑÐ°ÐŒÐŸÐŒ ÐœÐžÐ¶ÐœÐµÐŒ ÑÑÐŸÐ²ÐœÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐŸÐº ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ "ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ Ð¿ÐŸÐŒÐŸÑÐœÐžÐº", Ð¿ÑÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ Ð¿ÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÐŸ, Ð¿Ð°ÑÐ°ÐŒÐµÑÑÑ, ÑÑÐµÐ±ÑÑÑÐžÐµ Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸÐ³ÐŸ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÑ, ÑÐºÑÑÑÑ Ðž Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÐŸÐžÐ·Ð²ÐŸÐŽÐžÑÑÑ ÐŒÐžÐœÐžÐŒÐ°Ð»ÑÐœÐŸ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÐŒ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸÐŒ Ð·Ð°Ð¿ÐžÑÐµÐ¹. ÐÐ°ÐŸÐ±ÐŸÑÐŸÑ, ÐœÐ°ÐžÐ²ÑÑÑÐ°Ñ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐ° "Ð­ÐºÑÐ¿ÐµÑÑ" ÐŸÐ±ÐµÑÐ¿ÐµÑÐžÐ²Ð°ÐµÑ ÐŽÐŸÑÑÑÐ¿ ÐºÐŸ Ð²ÑÐµÐŒ ÑÑÐµÐŽÑÑÐ²Ð°ÐŒ Ð¿ÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ, Ð²ÐºÐ»ÑÑÐ°Ñ Ð¿ÐŸÐ·ÐžÑÐžÐŸÐœÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð¿Ð»Ð°Ð³ÐžÐœÐŸÐ² Ðž Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸÐµ Ð²ÑÑÐ°Ð¶ÐµÐœÐžÐµ Ð¿Ð°ÑÐ°ÐŒÐµÑÑÐŸÐ², Ð° ÑÐ°ÐºÐ¶Ðµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÐŸÐ»ÐœÑÐ¹ Ð²ÑÑ
+ÐŸÐŽ ÐžÐ· Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÑÐŸÐ±Ñ Ð·Ð°ÑÐžÐºÑÐžÑÐŸÐ²Ð°ÑÑ Ð² Ð¶ÑÑÐœÐ°Ð»Ðµ Ð·Ð°Ð¿ÐžÑÐµÐ¹. Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐžÐ»Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ ÑÐ¿ÐŸÑÐŸÐ±Ñ, ÐºÐ»ÐžÐºÐœÐžÑÐµ ÑÐ°ÐŽÐžÐŸ-ÐºÐœÐŸÐ¿ÐºÑ, ÑÐ»ÐµÐŽÑÑÑÑÑ Ð·Ð° ÑÐ¿ÐŸÑÐŸÐ±ÐŸÐŒ, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÐœÑÐµÑÐµÑÑÐµÑ ÐÐ°Ñ. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð±ÑÑÑÑÐŸ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ, ÐºÐ°ÐºÐŸÐ¹ ÑÐ¿ÐŸÑÐŸÐ± ÐÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ, ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°Ñ Ð»ÐžÐœÐµÐ¹ÐºÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹ Ð² ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐŒ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐµ.</Text>
+<Text id="440">ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÑÐµÑ
+ÐœÐŸÐ»ÐŸÐ³ÐžÑÐµÑÐºÐžÐµ Ð¿ÑÐŸÑÐµÑÑÑ Ð¿ÑÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐž, ÐºÐ°ÐºÐžÐµ ÐžÐ· ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÐ¹ ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ² ÑÐ²Ð»ÑÑÑÑÑ Ð²ÐžÐŽÐžÐŒÑÐŒÐž. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÐºÐ»Ð°Ð²ÐžÑÑ "Ð¢ÐµÑ
+ÐœÐŸÐ»ÐŸÐ³ÐžÑÐµÑÐºÐžÐµ Ð¿ÑÐŸÑÐµÑÑÑ", ÑÑÐŸÐ±Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ, ÐºÐ°ÐºÐžÐµ Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÑÐ²Ð»ÑÑÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž, Ð¿ÑÐŸÐ²ÐµÑÑÑ Ð¿ÐŸÐ»Ñ ÑÑÐŽÐŸÐŒ Ñ ÑÐµÐŒÐž Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÐµÐœÐžÑÐŒÐž, ÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒÐž. ÐÐŒÐµÑÑÐŸ ÑÑÐŸÐ³ÐŸ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐžÐ¹ ÑÐ¿ÐžÑÐŸÐº Ð²ÐœÐžÐ·Ñ ÑÐºÑÐ°ÐœÐ°,ÑÑÐŸÐ±Ñ Ð²ÑÐ±ÑÐ°ÑÑ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸ Ð·Ð°ÐŽÐ°ÐœÐœÑÐµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž. ÐÐ°ÐºÑÑÑÐžÐµ ÐŽÐžÐ°Ð»ÐŸÐ³Ð° Ð¿ÑÐµÐŽÐ¿ÐŸÑÑÐµÐœÐžÐ¹ Ð·Ð°ÐºÑÐµÐ¿Ð»ÑÐµÑ ÑÑÐž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž ÑÐµÑ
+ÐœÐŸÐ»ÐŸÐ³ÐžÑÐµÑÐºÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐµÑÑÐ°. Ð­ÑÐž ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž Ñ
+ÑÐ°ÐœÑÑÑÑ Ð²ÐŒÐµÑÑÐµ Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹,Ð° ÐœÐµ Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°.</Text>
+<Text id="441">ÐÐ»Ð°Ð²ÐžÑÐ° "Ð¡ÐŸÐµÐŽÐžÐœÐµÐœÐžÐµ" Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐÐ°ÐŒ ÐžÐ·ÐŒÐµÐœÑÑÑ Ð¿ÑÑÑ Ðº Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸÐŒÑ ÑÐµÑÐ²ÐµÑÑ Greenstone, ÐºÐŸÑÐŸÑÑÐ¹ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ð¿ÑÐµÐŽÐ²Ð°ÑÐžÑÐµÐ»ÑÐœÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐŸÐŒÐµ ÑÐŸÐ³ÐŸ ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐžÑÑ ÐŒÐŸÐŽÑÐ»Ñ ÐŽÐŸÑÑÑÐ¿Ð° Ðº ÐÐœÑÐµÑÐœÐµÑÑ Ð¿ÑÐŸÐºÑÐž (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, ÐŽÐ»Ñ Ð·Ð°Ð³ÑÑÐ·ÐºÐž ÑÐ°Ð¹Ð»ÐŸÐ²; ÑÐŒÐŸÑÑÐž ÑÐ°Ð·ÐŽÐµÐ» ÐÐ°Ð³ÑÑÐ¶Ð°ÑÑ Ð€Ð°Ð¹Ð»Ñ ÐžÐ· ÐÐœÑÐµÑÐœÐµÑÐ° ÐŽÐ»Ñ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÑÑÐµÐ¹). ÐÐŸÐŒÐµÑÑÑÐµ ÑÐ»Ð°Ð³ÐŸÐ²ÑÑ ÐºÐœÐŸÐ¿ÐºÑ, ÑÑÐŸÐ±Ñ Ð²ÐºÐ»ÑÑÐžÑÑ ÐŒÐŸÐŽÑÐ»Ñ ÐŽÐŸÑÑÑÐ¿Ð°, Ðž ÑÐºÐ°Ð¶ÐžÑÐµ ÐŽÐµÑÐ°Ð»Ðž Ð°ÐŽÑÐµÑÐ° ÑÐµÑÐ²ÐµÑÐ° Ð¿ÑÐŸÐºÑÐž Ðž ÐœÐŸÐŒÐµÑ Ð¿ÐŸÑÑÐ°. ÐÐŸÐŽÑÐ»Ñ ÐŽÐŸÑÑÑÐ¿Ð° Ð±ÑÐŽÐµÑ Ð°ÐºÑÐžÐ²ÐžÑÐŸÐ²Ð°Ðœ Ð¿ÑÐž Ð·Ð°ÐºÑÑÑÐžÐž ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÐŸÐ³ÐŸ ÐŸÐºÐœÐ° ÐÐ¿ÑÐžÐ¹.</Text>
+<Text id="442">Ð ÑÐµÑÐµÐœÐžÐµ ÑÐµÑÑÐžÐž ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ ÐŒÐŸÐ¶ÐµÑ ÐŽÐ°Ð²Ð°ÑÑ Ð¿ÑÐµÐŽÑÐ¿ÑÐµÐŽÐžÑÐµÐ»ÑÐœÑÐµ ÑÐŸÐŸÐ±ÑÐµÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ ÐžÐœÑÐŸÑÐŒÐžÑÑÑÑ ÐÐ°Ñ ÐŸ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÑ
+ ÐœÐµÐ¿ÑÐµÐŽÐ²ÐžÐŽÐµÐœÐœÑÑ
+ Ð¿ÐŸÑÐ»ÐµÐŽÑÑÐ²ÐžÑÑ
+ ÐÐ°ÑÐžÑ
+ ÐŽÐµÐ¹ÑÑÐ²ÐžÐ¹. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÑÑ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐµ, Ð²ÑÐ±ÐžÑÐ°Ñ Ð¿ÐŸÐ»Ðµ "ÐÐµ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÑÑÐŸ Ð¿ÑÐµÐŽÑÐ¿ÑÐµÐ¶ÐŽÐµÐœÐžÐµ ÑÐœÐŸÐ²Ð°". ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐŸÐ·ÐŸÐ±ÐœÐŸÐ²ÐžÑÑ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÐµ Ð¿ÑÐµÐŽÑÐ¿ÑÐµÐ¶ÐŽÐ°ÑÑÐžÑ
+ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐ¹,ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ ÐºÐ»Ð°Ð²ÐžÑÑ "ÐÑÐµÐŽÑÐ¿ÑÐµÐ¶ÐŽÐµÐœÐžÐµ". ÐÑÐ±ÐµÑÐžÑÐµ Ð¿ÐŸÐ»Ðµ ÑÑÐŽÐŸÐŒ Ñ Ð¿ÑÐµÐŽÑÐ¿ÑÐµÐ¶ÐŽÐ°ÑÑÐžÐŒÐž ÑÐŸÐŸÐ±ÑÐµÐœÐžÑÐŒÐž, ÐµÑÐ»Ðž ÐÑ Ñ
+ÐŸÑÐžÑÐµ ÑÐœÐŸÐ²Ð° Ð¿ÐŸÐ»ÑÑÐ°ÑÑ ÐžÑ
+.</Text>
+</Content>
+</Part>
+<Part id="file_associations">
+<Title>
+<Text id="443">ÐÑÑÐŸÑÐžÐ°ÑÐžÐž ÑÐ°Ð¹Ð»Ð°</Text>
+</Title>
+<Content>
+<Text id="444">ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐ¹ ÐÐœÑÐµÑÑÐµÐ¹Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÑÐ¿ÐµÑÐžÑÐžÑÐµÑÐºÐžÐµ Ð¿ÑÐžÐºÐ»Ð°ÐŽÐœÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, ÑÑÐŸÐ±Ñ ÐŸÑÐºÑÑÐ²Ð°ÑÑ ÑÐ¿ÐµÑÐžÑÐžÑÐœÑÐµ ÑÐžÐ¿Ñ ÑÐ°Ð¹Ð»ÐŸÐ². Ð§ÑÐŸÐ±Ñ ÐžÐ·ÐŒÐµÐœÐžÑÑ Ð°ÑÑÐŸÑÐžÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÑÐ°Ð¹Ð»Ñ ÐŸÑÐºÑÑÐ²Ð°ÑÑ ÐŒÐµÐœÑ "Ð€Ð°Ð¹Ð»" Ðž ÑÐµÐ»ÐºÐ°ÑÑ "ÐÑÑÐŸÑÐžÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÑÐ°Ð¹Ð»Ñ".</Text>
+<Text id="445">Ð§ÑÐŸÐ±Ñ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ Ð°ÑÑÐŸÑÐžÐ°ÑÐžÐž, Ð²ÑÐ±ÐµÑÐžÑÐµ ÑÐµÐ»ÐµÐ²ÐŸÐµ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµ ÑÐ°Ð¹Ð»Ð° ÐžÐ· ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐµÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ° ÐžÐ»Ðž ÐœÐ°Ð¿ÐžÑÐžÑÐµ ÐœÐŸÐ²ÐŸÐµ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµ (ÐœÐµ Ð²ÐºÐ»ÑÑÐ°Ñ "."). ÐÐ°ÑÐµÐŒ ÐžÐ»Ðž ÐœÐ°Ð¿ÐžÑÐžÑÐµ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐµÐŒ Ð¿ÐŸÐ»Ðµ ÐºÐŸÐŒÐ°ÐœÐŽÑ,Ð·Ð°Ð¿ÑÑÐºÐ°ÑÑÑÑ Ð¶ÐµÐ»Ð°ÑÐµÐ»ÑÐœÐŸÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ,ÐžÐ»Ðž Ð²ÑÐ±ÐµÑÐžÑÐµ Ð¿ÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐžÐ· ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÐŸÐ³ÐŸ ÐŸÐºÐœÐ° "ÐÑÐŸÑÐŒÐŸÑÑ". ".%1" ÐŒÐŸÐ¶ÐµÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑÑÑ Ð² ÐºÐŸÐŒÐ°ÐœÐŽÐµ Ð·Ð°Ð¿ÑÑÐºÐ°, ÑÑÐŸÐ±Ñ Ð²ÑÑÐ°Ð²ÐžÑÑ ÐžÐŒÑ ÑÐ°Ð¹Ð»Ð°, ÐºÐŸÑÐŸÑÑÐ¹ ÐŽÐŸÐ»Ð¶ÐµÐœ ÐŸÑÐºÑÑÑÑÑÑ. ÐÐ°Ðº ÑÐŸÐ»ÑÐºÐŸ ÐŸÐœÐž Ð·Ð°Ð¿ÐŸÐ»ÐœÐµÐœÑ,Ð¿ÑÐœÐºÑ "ÐÐŸÐ±Ð°Ð²ÐžÑÑ" ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒ Ðž ÐŒÐŸÐ¶ÐœÐŸ ÑÐµÐ»ÑÐºÐŸÐŒ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ Ð°ÑÑÐŸÑÐžÐ°ÑÐžÑ.</Text>
+<Text id="446">Ð§ÑÐŸÐ±Ñ ÐŸÑÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ Ð°ÑÑÐŸÑÐžÐ°ÑÐžÑ, Ð²ÑÐ±ÐµÑÐžÑÐµ ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐµ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµ ÑÐ°Ð¹Ð»Ð°. ÐÑÐ±Ð°Ñ ÑÑÑÐµÑÑÐ²ÑÑÑÐ°Ñ ÐºÐŸÐŒÐ°ÐœÐŽÐ° ÑÐ²ÑÐ·Ðž Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ Ð² Ð¿ÐŸÐ»Ðµ Ð·Ð°Ð¿ÑÑÐºÐ° ÐºÐŸÐŒÐ°ÐœÐŽ. ÐÑÑÐµÐŽÐ°ÐºÑÐžÑÑÐ¹ÑÐµ ÐµÐµ Ðž Ð·Ð°ÑÐµÐŒ ÑÐµÐ»ÐºÐœÐžÑÐµ "ÐÐ°ÐŒÐµÐœÐžÑÑ".</Text>
+<Text id="447">Ð§ÑÐŸÐ±Ñ ÑÐŽÐ°Ð»ÐžÑÑ Ð°ÑÑÐŸÑÐžÐ°ÑÐžÑ, Ð²ÑÐ±ÐµÑÐžÑÐµ ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐµ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµ ÑÐ°Ð¹Ð»Ð° Ðž ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð£ÐŽÐ°Ð»ÐžÑÑ".(Ð Ð°ÑÑÐžÑÐµÐœÐžÐµ ÑÐ°Ð¹Ð»Ð° ÐŸÑÑÐ°ÐµÑÑÑ Ð² ÐœÐžÑÐ¿Ð°ÐŽÐ°ÑÑÐµÐŒ ÑÐ¿ÐžÑÐºÐµ "ÐÐ»Ñ ÐŸÐºÐŸÐœÑÐ°ÐœÐžÑ ÑÐ°Ð¹Ð»ÐŸÐ²").</Text>
+<Text id="448">ÐÑÐŸÑÐžÐ°ÑÐžÐ²ÐœÑÐµ ÑÐ°Ð¹Ð»Ñ Ñ
+ÑÐ°ÐœÑÑÑÑ Ð² Ð³Ð»Ð°Ð²ÐœÐŸÐ¹ Ð¿Ð°Ð¿ÐºÐµ ÐÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÐŸÐ³ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°, Ð² ÑÐ°Ð¹Ð»Ðµ, ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÐŸÐŒ "associations.xml".</Text>
+</Content>
+</Part>
+<Part id="exporting_collections_to_cddvd">
+<Title>
+<Text id="449">Ð­ÐºÑÐ¿ÐŸÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐœÐ° CD/DVD</Text>
+</Title>
+<Content>
+<Text id="450">Greenstone ÐŒÐŸÐ¶ÐµÑ ÑÐºÑÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐŸÐŽÐœÑ ÐžÐ»Ðž Ð±ÐŸÐ»ÐµÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð² ÑÐ°ÐŒÐŸÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑÐžÐ¹ÑÑ CD/DVD Ð¿ÐŸÐŽ Windows. Ð§ÑÐŸÐ±Ñ ÑÑÐŸ ÑÐŽÐµÐ»Ð°ÑÑ, ÐŽÐŸÐ»Ð¶ÐµÐœ Ð±ÑÑÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ Ð¿Ð°ÐºÐµÑ "Ð­ÐºÑÐ¿ÐŸÑÑ Ð² CD-ROM". ÐÐœ ÐœÐµ Ð²ÐºÐ»ÑÑÐµÐœ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, Ð¿ÐŸÑÑÐŸÐŒÑ ÐÑ ÐŽÐŸÐ»Ð¶ÐœÑ ÐžÐ·ÐŒÐµÐœÐžÑÑ ÐÐ°ÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÑ, ÑÑÐŸÐ±Ñ ÐµÐ³ÐŸ Ð²ÐºÐ»ÑÑÐžÑÑ.</Text>
+<Text id="451">Ð§ÑÐŸÐ±Ñ ÑÐºÑÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐŸÑÐºÑÐŸÐ¹ÑÐµ ÐŒÐµÐœÑ "Ð€Ð°Ð¹Ð»" Ðž Ð²ÑÐ±ÐµÑÐžÑÐµ "Ð­ÐºÑÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÑÑ Ð² CD-ROM/DVD...". ÐÐŸÑÐ²Ð»ÑÐµÑÑÑ ÑÐ¿ÐžÑÐŸÐº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÑÐŸÐ±ÑÐ°ÐœÐžÐ¹ Greenstone; ÑÐµÐ»ÐºÐœÐžÑÐµ ÐœÐ° Ð»ÑÐ±ÐŸÐ¹, ÑÑÐŸÐ±Ñ ÑÐ²ÐžÐŽÐµÑÑ ÐµÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ. ÐÐŸÐŒÐµÑÑÑÐµ Ð²ÑÐ±ÑÐ°ÐœÐœÑÐµ Ð¿ÐŸÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐŽÐ»Ñ ÑÐºÑÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²Ð²ÐµÑÑÐž ÐžÐŒÑ CD/DVD Ð² Ð¿ÐŸÐ»Ðµ: ÑÑÐŸ ÑÐŸ, ÑÑÐŸ Ð¿ÐŸÑÐ²ÐžÑÑÑ Ð² ÑÑÐ°ÑÑÐŸÐ²ÐŸÐŒ ÐŒÐµÐœÑ, ÐºÐŸÐ³ÐŽÐ° CD/DVD Ð±ÑÐŽÐµÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ. ÐÐ°ÑÐµÐŒ ÑÐµÐ»ÐºÐœÐžÑÐµ "Ð­ÐºÑÐ¿ÐŸÑÑ". ÐÑÐŸÑÐµÑÑ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐŒÐœÐŸÐ³ÐžÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ² Ðž ÐŒÐŸÐ¶ÐµÑ Ð·Ð°ÐœÑÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐŒÐžÐœÑÑ.</Text>
+<Text id="452">ÐÐŸÑÐ»Ðµ ÐŸÐºÐŸÐœÑÐ°ÐœÐžÑ Greenstone Ð¿ÐŸÐºÐ°Ð¶ÐµÑ ÐžÐŒÑ Ð¿Ð°Ð¿ÐºÐž, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐµÐ¹ ÑÐºÑÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ Ð¿ÐžÑÑÑÐžÐ¹ ÐºÐŸÐŒÐ¿Ð°ÐºÑ-ÐŽÐžÑÐº ÐŽÐ»Ñ ÐºÐŸÐ¿ÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐµÐ³ÐŸ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÐœÐ° ÑÐžÑÑÑÐ¹ CD/DVD.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+<Section id="tagging_document_files">
+<Title>
+<Text id="453">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÑÑÐ³ÐŸÐ² Ðº ÑÐ°Ð¹Ð»Ð°ÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ</Text>
+</Title>
+<Content>
+<Text id="454">ÐÑÐ»Ðž ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐºÐŸÑÐŸÑÑÑ Ð¶ÐµÐ»Ð°ÐµÑÐµ Ð¿ÐŸÑÑÑÐŸÐžÑÑ, ÐŸÑÐ³Ð°ÐœÐžÐ·ÐŸÐ²Ð°ÐœÑ Ð² ÑÐ°Ð·ÐŽÐµÐ»Ñ Ðž Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»Ñ, ÑÐŸ Ð²Ð°ÐŒ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÑÐºÐ°Ð·Ð°ÑÑ ÑÑÐŸ Ð² ÐžÑÑ
+ÐŸÐŽÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ (source files), ÑÐ°Ðº ÑÑÐŸÐ±Ñ Greenstone Ð¿ÑÐž ÑÐŸÐ·ÐŽÐ°ÐœÐžÐž ÐÐ³Ð»Ð°Ð²Ð»ÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ ÑÐŸÐ·ÐŽÐ°ÑÑ ÑÑÑÐ»ÐºÐž (active links) Ðº ÐºÐ°Ð¶ÐŽÐŸÐŒÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ. Ð­ÑÐŸ ÐŽÐµÐ»Ð°ÐµÑÑÑ Ð¿ÑÑÐµÐŒ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ â Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° Ðž Ð¿ÐŸÐŽÐ·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ° ÑÐ°Ð·ÐŽÐµÐ»Ð° Ðž Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»Ð°.</Text>
+<Text id="455">ÐÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ - ÑÑÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, ÐºÐ°Ðº Ð¿ÑÐ°Ð²ÐžÐ»ÐŸ Ð¿ÐŸÐ»ÑÑÐµÐœÐœÑÐµ Ð¿ÐŸÑÐ»Ðµ Ð¿ÑÐŸÑÐµÑÑÐ° ÐÐ Ð¡, Ðž ÑÐ²Ð»ÑÑÑÐžÐµÑÑ ÐœÐ°Ð±ÐŸÑÐŸÐŒ ÑÐµÐºÑÑÐŸÐ²ÑÑ
+ ÑÐ°Ð»ÐŸÐ² Word, Ð²ÐºÐ»ÑÑÐ°Ñ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ. ÐÑÐ»Ðž ÐŸÐœÐž ÑÐ²Ð»ÑÑÑÑÑ ÑÐ°Ð¹Ð»Ð°ÐŒÐž Word, ÑÐŸ ÐŸÐœÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÑ Ð² Greenstone Ñ Ð¿ÐŸÐŒÐŸÑÑÑ Word plugin. ÐÐ°Ðº Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ²Ð° , ÐŸÐœÐž ÑÐ°Ðº Ð¶Ðµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÑ Ð² ÑÐŸÑÐŒÐ°Ñ HTML, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ HTML plugin.</Text>
+<Text id="456">Ð Ð»ÑÐ±ÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ, ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŸ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ°Ñ
+ Ðž Ð¿ÐŸÐŽÐ·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐ°Ñ
+ ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÑÐºÐ°Ð·Ð°ÐœÑ ÑÑÐ³Ð°ÐŒÐž Ð² ÑÐµÐºÑÑÐµ ÑÐ»ÐµÐŽÑÑÑÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ:</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<Text type="code" id="457">&lt;Metadata name="Title"&gt;Realizing human rights for poor people: Strategies for achieving the international development targets&lt;/Metadata&gt;</Text>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="458"><i>(text of section goes here)</i></Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="459">ÐÐ°ÑÐºÐµÑÑ &lt;!â...â&gt; ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ, ÑÐ°Ðº ÐºÐ°Ðº ÐŸÐœÐž ÑÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÐºÐŸÐŒÐŒÐµÐœÑÐ°ÑÐžÐž Ð² HTML; ÑÐ°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, ÑÑÐž ÑÑÐ³Ðž ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ² ÐœÐµ Ð±ÑÐŽÑÑ Ð²Ð»ÐžÑÑÑ ÐœÐ° ÑÐŸÑÐŒÐ°ÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°.</Text>
+<Text id="460">Ð ÐŸÐ±Ð»Ð°ÑÑÐž Description (ÐŒÐµÐ¶ÐŽÑ ÑÑÐ³Ð°ÐŒÐž &lt;Description&gt;, &lt;/Description&gt; ÐŒÐŸÐ¶ÐœÐŸ ÑÐºÐ°Ð·Ð°ÑÑ ÐŽÑÑÐ³ÐžÐµ Ð²ÐžÐŽÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐœÐŸ ÐŽÐ»Ñ ÑÐ°ÐºÐŸÐ³ÐŸ ÑÐŸÐŽÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐºÐŸÑÐŸÑÑÐµ ÐŒÑ ÐŸÐ¿ÐžÑÑÐ²Ð°ÐµÐŒ, ÐŸÐœÐž ÐœÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ). Ð Ð°Ð·ÐŽÐµÐ»Ñ ÐŒÐŸÐ³ÑÑ ÐžÐŒÐµÑÑ Ðž Ð¿ÐŸÐŽÑÐ°Ð·ÐŽÐµÐ»Ñ ÐºÐ°Ðº Ð¿ÑÐŸÐŽÐŸÐ»Ð¶ÐµÐœÐžÐµ ÑÐ»ÑÑÐ°Ñ, ÐŸÐ¿ÐžÑÐ°ÐœÐœÐŸÐ³ÐŸ Ð²ÑÑÐµ.</Text>
+<Text id="461">ÐÑÐ»Ðž Ð²Ñ When you Ð²ÑÑÐ°Ð²ÐžÐ»Ðž ÑÐµÐºÑÐžÑ ÑÐµÐ³ÐŸÐ² Ð² Ð²Ð°Ñ ÐŽÐŸÐºÑÐŒÐµÐœÑ, Ð·Ð°Ð¿ÐŸÐŒÐœÐžÑÐµ ÑÑÐŸ Ð²Ñ ÑÐŸÐ·ÐŽÐ°Ð»Ðž ÐžÐµÑÐ°ÑÑ
+ÐžÑÐµÑÐºÑÑ ÑÐ°Ð±Ð»ÐžÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ. Ð­ÑÐŸ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ ÑÑÐŸ ÑÐµÐºÑÐžÐž ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑÑ Ð²ÐœÑÑÑÐž ÐŽÑÑÐ³ÐžÑ
+ ÑÐµÐºÑÐžÐ¹. Ð€Ð°ÐºÑÐžÑÐµÑÐºÐž, Ð²ÑÐµ ÑÐµÐºÑÐžÐž ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ Ð²ÐºÐ»ÑÑÐµÐœÑ Ð² ÐŸÐŽÐœÑ Ð·Ð°ÐºÐ»ÑÑÐžÑÐµÐ»ÑÐœÑÑ ÑÐµÐºÑÐžÑ ÐºÐŸÑÐŸÑÐ°Ñ Ð·Ð°ÐºÐ»ÑÑÐ°ÐµÑ Ð²ÐµÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ.</Text>
+<Text id="462">Ð¡Ð»ÐµÐŽÑÑÑÐžÐ¹ Ð¿ÑÐžÐŒÐµÑ ÐŽÐµÐŒÐŸÐœÑÑÑÐžÑÑÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ñ ÐŽÐ²ÑÐŒÑ Ð³Ð»Ð°Ð²Ð°ÐŒÐž, Ð²ÑÐŸÑÐ°Ñ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÐŽÐ²Ðµ Ð¿ÐŸÐŽÑÐµÐºÑÐžÐž. ÐÐ»Ñ ÑÐµÐ°Ð»ÑÐœÐŸÐ³ÐŸ Ð¿ÑÐžÐŒÐµÑÐ° Ð¿ÐµÑÐ²ÐŸÐžÑÑÐŸÑÐœÐžÐºÐž ÐŸÑÐŸÑÐŒÐ»ÐµÐœÑ ÑÐµÐ³Ð°ÐŒÐž ÑÐ°Ðº ÑÑÐŸÐ±Ñ ÐŸÐœÐž Ð²ÑÐ³Ð»ÑÐŽÐµÐ»Ðž ÐºÐ°Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐŽÐ»Ñ ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÐ»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž .</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>&lt;Metadata name="Title"&gt;My Document&lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>&lt;Metadata name="Title"&gt;Chapter 1&lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text type="code" id="463">(text of chapter 1 goes here)</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>&lt;Metadata name="Title"&gt;Chapter 2&lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>&lt;Metadata name="Title"&gt;Subsection 1&lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text type="code" id="464">(text of sub-section 1 goes here)</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;Section&gt;</CodeLine>
+<CodeLine>&lt;Description&gt;</CodeLine>
+<CodeLine>&lt;Metadata name="Title"&gt;Subsection 2&lt;/Metadata&gt;</CodeLine>
+<CodeLine>&lt;/Description&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text type="code" id="465">(text of sub-section 2 goes here)</Text>
+<CodeLine>&lt;!--</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>&lt;/Section&gt;</CodeLine>
+<CodeLine>--&gt;</CodeLine>
+<Text id="466">ÐÐŒÐµÐ¹ÑÐµ Ð²Ð²ÐžÐŽÑ ÑÑÐŸ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐœÐ°Ð·ÐœÐ°ÑÐµÐœÐœÑÐµ Ð² ÑÐµÐºÑÐžÐž ÑÐµÐ³ÐŸÐ² Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐµ Ð¿ÐµÑÐ²ÐŸÐžÑÑÐŸÑÐœÐžÐºÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ Ð²ÐµÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ. Ð­ÑÐŸ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ ÑÑÐŸ ÐÐ°ÐŒ ÐœÐµ ÑÐ»ÐµÐŽÑÐµÑ ÐŽÐµÑÐ°Ð»ÑÐœÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐÐ°Ð·Ð²Ð°ÐœÐžÑ ÐŽÐ»Ñ ÑÐµÐºÑÐžÐž Ð²ÐµÑÑ
+ÐœÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ, ÐµÑÐ»Ðž Ð²Ñ ÐœÐµ Ñ
+ÐŸÑÐžÑÐµ Ð¿ÐµÑÐµÑÐŸÐ·ÐŽÐ°ÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐµ ÑÐ°ÐœÐµÐµ.  Ð Ð²ÑÑÐµÑÐºÐ°Ð·Ð°ÐœÐœÐŸÐŒ Ð¿ÑÐžÐŒÐµÑÐµ ÐºÐ°Ðº ÐŒÐžÐœÐžÐŒÑÐŒ ÐµÑÐ»Ðž Ð²Ñ Ñ
+ÐŸÑÐžÑÐµ Ð¿ÐµÑÐµÑÐŸÐ·ÐŽÐ°ÑÑ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐŸÐº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð²Ð°ÐŒ ÑÐ»ÐµÐŽÑÐµÑ Ð¿ÑÐŸÐ¿ÑÑÑÐžÑÑ ÑÑÑÐŸÐºÑ ÐºÐŸÑÐŸÑÑÑ Ð²Ñ ÑÐµÐ¹ÑÐ°Ñ ÑÐžÑÐ°ÐµÑÐµ</Text>
+<CodeLine>&lt;Metadata name="Title"&gt;My Document&lt;/Metadata&gt;</CodeLine>
+</Content>
+</Section>
+<Section id="the_collector">
+<Title>
+<Text id="467">ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ</Text>
+</Title>
+<Content>
+<Text id="468">ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð²Ð°ÐŒ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐœÐŸÐ²ÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð° ÑÐ°ÐºÐ¶Ðµ ÐžÐ·ÐŒÐµÐœÑÑÑ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ ÐžÐ»Ðž ÑÐŽÐ°Ð»ÑÑÑ. ÐÐ»Ñ ÑÑÐŸÐ³ÐŸ ÐŒÑ Ð¿ÑÐŸÐ¹ÐŽÐµÐŒ ÑÐµÑÐµÐ· ÑÑÐŽ Ð²ÐµÐ±-ÑÑÑÐ°ÐœÐžÑ, ÐºÐŸÑÐŸÑÑÐµ ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑ ÑÑÐŸÑ Ð¿ÑÐŸÑÐµÑÑ. Ð ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð°Ð»ÑÑÐµÑÐœÐ°ÑÐžÐ² ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÑ Ð²Ñ ÑÐ°ÐºÐ¶Ðµ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐºÐŸÐŒÐ°ÐœÐŽÐœÐŸÐ¹ ÑÑÑÐŸÐºÐž - Ð¿ÐµÑÐ²ÑÐµ ÑÑÑÐ°ÐœÐžÑÑ ÐÐœÑÑÑÑÐºÑÐžÐž Ð Ð°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ° ÐŽÐµÑÐ°Ð»ÑÐœÐŸ ÑÐ°ÑÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑ ÑÑÐŸÑ Ð²ÐŸÐ¿ÑÐŸÑ.</Text>
+<Text id="469">Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ Ðž ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœÐžÐµ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÑ
+ Ð²Ð»ÐµÑÐµÑ Ð·Ð° ÑÐŸÐ±ÐŸÐ¹ ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐŸÑÑÑ, ÐºÐŸÑÐŸÑÑÑ ÑÐ»ÐµÐŽÑÐµÑ ÑÑÐµÑÑÑ Ð¿ÐµÑÐµÐŽ ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµÐŒ. Ð¡ÑÑÐµÑÑÐ²ÑÑÑ Ð°Ð²ÑÐŸÑÑÐºÐžÐµ Ð¿ÑÐ°Ð²Ð°: ÐžÐŒÐµÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ ÐœÐµ ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ, ÑÑÐŸ Ð²Ð°ÐŒ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÐµÐœÐŸ ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÑÑ ÐµÐµ ÐŽÐ»Ñ ÐŽÑÑÐ³ÐžÑ
+. Ð¡ÑÑÐµÑÑÐ²ÑÑÑ ÑÐ°ÐºÐ¶Ðµ Ð²ÐŸÐ¿ÑÐŸÑÑ ÑÑÐžÐºÐž: Ðº ÐœÐµÐºÐŸÑÐŸÑÑÐŒ Ð²ÐµÑÑÐŒ Ð¿ÑÐŸÑÑÐŸ ÐœÑÐ¶ÐœÐŸ ÐŸÐ³ÑÐ°ÐœÐžÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿. ÐÐµÑÐŸ ÐŸÑÑÑÐµÐµ ÐŒÐµÑÐ°! ÐÑÐŽÑÑÐµ ÐŸÑÑÐŸÑÐŸÐ¶ÐœÑ Ðž ÑÐŒÐµÐ»ÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ ÑÐžÐ»Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž.</Text>
+<Text id="470">ÐÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ ÑÑÑÐ»ÐºÑ (Collector) Ð² ÑÑÐ°ÑÑÐŸÐ²ÐŸÐŒ ÐŸÐºÐœÐµ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž.</Text>
+<Text id="471">Ð Greenstone ÑÑÑÑÐºÑÑÑÐ° ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŸÐ¿ÑÐµÐŽÐµÐ»ÑÐµÑÑÑ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÐµÐµ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ. Ð­ÑÐŸ Ð²ÐºÐ»ÑÑÐ°ÐµÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÐµ ÑÐŸÑÐŒÐ°ÑÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐžÑ
+ Ð²ÑÐ²ÐŸÐŽ ÐœÐ° ÑÐºÑÐ°Ðœ, ÐžÑÑÐŸÑÐœÐžÐº ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÐºÐ°ÐºÐžÐµ Ð¿ÑÐµÐŽÐŒÐµÑÐœÑÐµ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ðž ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ Ð²ÐºÐ»ÑÑÐµÐœÑ, ÐºÐ°ÐºÐžÐµ Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÑÐµ ÐžÐœÐŽÐµÐºÑÑ ÑÐ»ÐµÐŽÑÐµÑ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²ÐžÑÑ Ðž ÐºÐ°Ðº ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÑ ÑÐµÐ·ÑÐ»ÑÑÐ°ÑÑ Ð¿ÐŸÐžÑÐºÐ°. ÐÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐŸÐ·ÐŽÐ°ÐœÐ°, Ð² ÐœÐµÐµ Ð»ÐµÐ³ÐºÐŸ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐœÐŸÐ²ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÑÐž ÑÑÐ»ÐŸÐ²ÐžÐž, ÑÑÐŸ ÐŸÐœÐž ÑÐŸÐ³ÐŸ Ð¶Ðµ ÑÐŸÑÐŒÐ°ÑÐ°, ÑÑÐŸ Ðž ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, Ðž ÐžÐŒÐµÑÑ ÑÑ
+ÐŸÐ¶ÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ.</Text>
+<Text id="472">ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÑ ÑÐ»ÐµÐŽÑÑÑÐžÐµ ÐŸÑÐœÐŸÐ²ÐœÑÐµ ÑÑÐœÐºÑÐžÐž:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="473">ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐžÐŒÐµÑÑÐµÐ¹ ÑÐ°ÐºÑÑ Ð¶Ðµ ÑÑÑÑÐºÑÑÑÑ, ÐºÐ°Ðº Ðž ÑÑÑÐµÑÑÐ²ÑÑÑÐ°Ñ;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="474">ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐžÐŒÐµÑÑÐµÐ¹ ÐŽÑÑÐ³ÑÑ ÑÑÑÑÐºÑÑÑÑ, ÐœÐµÐ¶ÐµÐ»Ðž ÑÑÑÐµÑÑÐ²ÑÑÑÐ°Ñ;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="475">ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐœÐŸÐ²ÑÐ¹ ÐŒÐ°ÑÐµÑÐžÐ°Ð» Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="476">ÐžÐ·ÐŒÐµÐœÐžÑÑ ÑÑÑÑÐºÑÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="477">ÑÐŽÐ°Ð»ÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ;</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="478">Ð·Ð°Ð¿ÐžÑÐ°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐœÐ° ÑÐ°ÐŒÐŸÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑÐžÐ¹ÑÑ CD-ROM</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="479">Ð ÐžÑÑÐœÐŸÐº 16 Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð² ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐžÐ· ÐœÐ°Ð±ÐŸÑÐ° ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐŸÑÐŒÐ°ÑÐ° HTML. ÐÑÐµÐ¶ÐŽÐµ Ð²ÑÐµÐ³ÐŸ Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ ÑÐµÑÐžÑÑ, Ñ
+ÐŸÑÐžÑÐµ Ð»Ðž Ð²Ñ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹ ÐžÐ»Ðž ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐœÐŸÐ²ÑÑ. ÐÐµÑÐ²Ð°Ñ ÐºÐ°ÑÐ°ÐµÑÑÑ Ð¿ÑÐœÐºÑÐŸÐ² 3-6, Ð° Ð¿ÐŸÑÐ»ÐµÐŽÐœÑÑ 1-2.</Text>
+<Figure id="using_the_collector_to_build_a_new_collection">
+<Title>
+<Text id="480">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ° ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (Ð¿ÑÐŸÐŽÐŸÐ»Ð¶ÐµÐœÐžÐµ ÐœÐ° ÑÐ»ÐµÐŽÑÑÑÐµÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ)</Text>
+<SubTitle>
+<Text id="481">(a)</Text>
+</SubTitle>
+</Title>
+<File width="369" height="440" url="images/User_Fig_16a.png"/>
+</Figure>
+<Subsection id="logging_in">
+<Title>
+<Text id="482">ÐÑ
+ÐŸÐŽ</Text>
+</Title>
+<Content>
+<Text id="483">Ð Ð»ÑÐ±ÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ Ð²Ð°ÐŒ Ð¿ÑÐµÐ¶ÐŽÐµ Ð²ÑÐµÐ³ÐŸ ÐœÑÐ¶ÐœÐŸ Ð²ÐŸÐ¹ÑÐž Ð² ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ. ÐÐ°ÐŒÐµÑÑÑÐµ, ÑÑÐŸ ÐŸÐ±ÑÑÐœÐŸ, ÑÐµÑÐµÐ· ÑÐ²ÐŸÐž ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÑ Ð»ÑÐŽÐž ÐžÐŒÐµÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÑÐ¿ÐµÑÐžÐ°Ð»ÐžÐ·ÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐŒÑ ÐŸÑÐŽÐ°Ð»ÐµÐœÐœÐŸÐŒÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÑ Ð² ÑÐµÑÐž, ÐžÐŒÐµÑÑÐµÐŒÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹. ÐÐŸÐœÐµÑÐœÐŸ Ð¶Ðµ ÐŒÑ ÐœÐµ ÐŒÐŸÐ¶ÐµÐŒ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÐžÑÑ ÐºÐ°Ð¶ÐŽÐŸÐŒÑ ÐžÐŒÐµÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÑÐ°ÐºÐžÐŒ ÑÐµÑÐ²ÐµÑÐ°ÐŒ Ðž ÑÑÑÐŸÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð¿ÐŸÑÑÐŸÐŒÑ Greenstone ÐžÐŒÐµÐµÑ ÑÐžÑÑÐµÐŒÑ Ð±ÐµÐ·ÐŸÐ¿Ð°ÑÐœÐŸÑÑÐž, Ð³ÐŽÐµ Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ Ð²Ð²ÐµÑÑÐž ÑÐ²ÐŸÐ¹ ID Ðž Ð¿Ð°ÑÐŸÐ»Ñ. Ð¢Ð°Ðº Ð¶Ðµ, ÐµÑÐ»Ðž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐŸ Ñ Ð²Ð°Ñ ÐœÐ° ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐ° ÐœÐµÐŒ. Ð¢ÐµÐŒ ÐœÐµ ÐŒÐµÐœÐµÐµ, Ð²Ñ ÑÐ°ÐºÐ¶Ðµ ÐŽÐŸÐ»Ð¶ÐœÑ Ð²Ð²ÐµÑÑÐž ID Ðž Ð¿Ð°ÑÐŸÐ»Ñ, ÑÑÐŸÐ±Ñ ÐŸÐ³ÑÐ°ÐŽÐžÑÑ Ð¿ÐŸÑÑÐŸÑÐŸÐœÐœÐžÑ
+ Ð»ÑÐŽÐµÐ¹ ÐŸÑ Ð²Ñ
+ÐŸÐŽÐ° Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð±ÐµÐ· ÑÐ°Ð·ÑÐµÑÐµÐœÐžÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="dialog_structure">
+<Title>
+<Text id="484">ÐÐžÐ°Ð»ÐŸÐ³ÐŸÐ²Ð°Ñ ÑÑÑÑÐºÑÑÑÐ°</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_1">
+<Title>
+<Text id="485">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ° ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐÑÐŸÐŽÐŸÐ»Ð¶)</Text>
+<SubTitle>
+<Text id="486">(b)</Text>
+</SubTitle>
+</Title>
+<File width="369" height="435" url="images/User_Fig_16b.png"/>
+</Figure>
+<Text id="487">ÐÐŸÑÐ»Ðµ Ð²Ñ
+ÐŸÐŽÐ° ÐœÐ° ÑÐºÑÐ°ÐœÐµ Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ ÑÑÑÐ°ÐœÐžÑÐ°, ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐœÐ°Ñ ÐœÐ° ÑÐžÑÑÐœÐºÐµ 16b. ÐÐ° ÐœÐµÐ¹ Ð¿ÐŸÐºÐ°Ð·Ð°Ðœ Ð¿ÐµÑÐµÑÐµÐœÑ ÑÐ°Ð³ÐŸÐ², ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð­ÑÐŸ:</Text>
+<NumberedList>
+<NumberedItem>
+<Text id="488">Ð¡Ð±ÐŸÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="489">Ð£ÐºÐ°Ð·Ð°ÐœÐžÐµ ÐžÑÑÐŸÑÐœÐžÐºÐŸÐ²</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="490">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="491">ÐÐŸÑÑÑÐŸÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</NumberedItem>
+<NumberedItem>
+<Text id="492">ÐÑÐŸÑÐŒÐŸÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</NumberedItem>
+</NumberedList>
+<Text id="493">Ð Ð¿ÐµÑÐ²ÐŸÐŒ ÑÐ°Ð³Ðµ ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž ÑÐŸÐ¿ÑÑÑÑÐ²ÑÑÑÐ°Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ. ÐÑÐŸÑÐŸÐ¹ ÑÐ°Ð³ - ÑÐºÐ°Ð·Ð°ÑÑ, ÐŸÑÐºÑÐŽÐ° ÑÐºÐ°ÑÐžÐ²Ð°ÑÑ Ðž Ð¿ÐŸÐ»ÑÑÐ°ÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ. ÐÐ°ÑÐµÐŒ ÑÐ»ÐµÐŽÑÐµÑ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐ° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð­ÑÐŸ ÑÐ°Ð³, ÐºÐŸÑÐŸÑÑÐ¹ ÑÑÐ°ÐœÐŸÐ²ÐžÑÑÑ Ð±ÐŸÐ»ÐµÐµ Ð²Ð°Ð¶ÐœÑÐŒ Ñ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÐµÐŒ Ð²ÑÐµ Ð±ÐŸÐ»ÑÑÐµÐ³ÐŸ ÐŸÐ¿ÑÑÐ° ÑÐ°Ð±ÐŸÑÑ Ñ Greenstone. Ð§ÐµÑÐ²ÐµÑÑÑÐ¹ ÑÐ°Ð³ - ÑÑÐŸ ÑÐ°ÐŒ, Ð³ÐŽÐµ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ ÑÐ±ÐŸÑÐºÐ° Ðž ÑÐ°Ð±ÐŸÑÐ°. Ð Ð¿ÑÐŸÑÐµÑÑÐµ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÑÐŸÐ·ÐŽÐ°ÐµÑ Ð²ÑÐµ ÐžÐœÐŽÐµÐºÑÑ Ðž ÑÐŸÐ±ÐžÑÐ°ÐµÑ Ð²ÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÑÑ ÐŽÐ»Ñ ÑÑÐœÐºÑÐžÐŸÐœÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÑÑÐ¹ ÑÐ°Ð³ - ÑÑÐŸ Ð¿ÑÐŸÑÐŒÐŸÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÐœÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. </Text>
+<Text id="494">Ð­ÑÐž Ð¿ÑÑÑ ÑÐ°Ð³ÐŸÐ² ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÑ Ð² Ð²ÐžÐŽÐµ Ð»ÐžÐœÐµÐ¹ÐœÐŸÐ¹ Ð¿ÐŸÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÐœÐŸÑÑÐž ÑÐµÑÑÑ
+ ÐºÐœÐŸÐ¿ÐŸÐº Ð²ÐœÐžÐ·Ñ ÑÑÑÐ°ÐœÐžÑÑ ÐœÐ° Ð ÐžÑÑÐœÐºÐµ 16b Ðž Ð²ÐœÐžÐ·Ñ Ð²ÑÐµÑ
+ ÑÑÑÐ°ÐœÐžÑ, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÑ
+ Ð² ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐµ. Ð­ÑÐ° Ð¿Ð°ÐœÐµÐ»Ñ ÐºÐœÐŸÐ¿ÐŸÐº Ð¿ÐŸÐŒÐŸÐ¶ÐµÑ Ð²Ð°ÐŒ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÑ, ÐœÐ° ÐºÐ°ÐºÐŸÐ¹ ÑÑÐ°ÐŽÐžÐž Ð¿ÑÐŸÑÐµÑÑÐ° Ð²Ñ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÐµÑÑ. ÐÐœÐŸÐ¿ÐºÐ°, ÐœÐ° ÐºÐŸÑÐŸÑÑÑ ÐœÑÐ¶ÐœÐŸ ÐœÐ°Ð¶Ð°ÑÑ ÐŽÐ»Ñ Ð¿ÑÐŸÐŽÐŸÐ»Ð¶ÐµÐœÐžÑ Ð¿ÑÐŸÑÐµÑÑÐ°, ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° Ð·ÐµÐ»ÐµÐœÑÐŒ ÑÐ²ÐµÑÐŸÐŒ (collection information ÐœÐ° ÑÐžÑÑÐœÐºÐµ 16b). ÐÐœÐŸÐ¿ÐºÐž ÑÐµÑÐŸÐ³ÐŸ ÑÐ²ÐµÑÐ° (Ð²ÑÐµ ÐŸÑÑÐ°Ð»ÑÐœÑÐµ ÐœÐ° Ð ÐžÑÑÐœÐºÐµ 16b) ÑÐ²Ð»ÑÑÑÑÑ ÐœÐµÐ°ÐºÑÐžÐ²ÐœÑÐŒÐž. ÐÐœÐŸÐ¿ÐºÐž ÐŒÐµÐœÑÑÑ ÑÐ²ÐµÑ ÐœÐ° Ð¶ÐµÐ»ÑÑÐ¹ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ Ð¿ÐµÑÐµÑ
+ÐŸÐŽÐ°. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐµÑÐœÑÑÑÑÑ Ðº Ð¿ÑÐµÐŽÑÐŽÑÑÐµÐŒÑ ÑÐ°Ð³Ñ, ÐœÐ°Ð¶Ð°Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ Ð¶ÐµÐ»ÑÑÑ ÐºÐœÐŸÐ¿ÐºÑ. Ð­ÑÐŸÑ Ð²ÐžÐŽ ÐŽÐžÑÐ¿Ð»ÐµÑ ÑÐŒÐŸÐŽÐµÐ»ÐžÑÐŸÐ²Ð°Ðœ ÐœÐ°Ð¿ÐŸÐŽÐŸÐ±ÐžÐµ âÐ¿ÑÑÐµÐ²ÐŸÐŽÐžÑÐµÐ»ÐµÐ¹, ÐŒÐ°ÑÑÐµÑÐŸÐ²â (wizards) ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð² ÐŽÑÑÐ³ÐžÑ
+ ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÐµÐœÐœÑÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÑ
+ ÑÑÐµÐŽÑÑÐ²Ð°Ñ
+, ÑÑÐµÐ±ÑÐµÐŒÑÑ
+ ÐŽÐ»Ñ Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ ÑÐµÑÐµÐ· Ð¿ÑÐŸÑÐµÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="collection_information">
+<Title>
+<Text id="495">ÐÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_2">
+<Title>
+<Text id="496">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ° ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐÑÐŸÐŽÐŸÐ»Ð¶)</Text>
+<SubTitle>
+<Text id="497">(c)</Text>
+</SubTitle>
+</Title>
+<File width="369" height="504" url="images/User_Fig_16c.png"/>
+</Figure>
+<Text id="498">ÐÐµÑÐ²ÑÐ¹ ÑÐ°Ð³ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ - ÑÑÐŸ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐœÐ°Ñ ÐœÐ° ÑÐžÑÑÐœÐºÐµ 16Ñ. ÐÑÐž ÐµÐµ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ Ð²Ð²ÐµÑÑÐž:</Text>
+<BulletList>
+<Bullet>
+<Text id="499">ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ</Text>
+</Bullet>
+<Bullet>
+<Text id="500">ÐÐŸÐœÑÐ°ÐºÑÐœÑÐ¹ e-mail Ð°ÐŽÑÐµÑ</Text>
+</Bullet>
+<Bullet>
+<Text id="501">ÐÑÐ°ÑÐºÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ</Text>
+</Bullet>
+</BulletList>
+<Text id="502">ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž - ÑÑÐŸ ÐºÐŸÑÐŸÑÐºÐ°Ñ ÑÑÐ°Ð·Ð°, Ð¿ÐŸÐ²ÑÐµÐŒÐµÑÑÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ Ð² ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐµ ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¢ÐžÐ¿ÐžÑÐœÑÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹: ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Ð¿ÐžÑÐž Ðž Ð¿ÐžÑÐ°ÑÐµÐ»ÑÐœÑÑ
+ Ð²ÐµÑÐµÑÑÐ², ÐÐžÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° ÐŸÐºÑÑÐ¶Ð°ÑÑÐµÐ¹ ÑÑÐµÐŽÑ, ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° ÑÐ°Ð·Ð²ÐžÑÐžÑ Ðž Ñ.ÐŽ. Ð­Ð»ÐµÐºÑÑÐŸÐœÐœÑÐ¹ Ð°ÐŽÑÐµÑ Ð¿ÑÐµÐŽÐœÐ°Ð·ÐœÐ°ÑÐµÐœ ÐŽÐ»Ñ ÐœÐµÐŒÐµÐŽÐ»ÐµÐœÐœÐŸÐ³ÐŸ ÐºÐŸÐœÑÐ°ÐºÑÐ° Ñ ÑÐŸÐ·ÐŽÐ°ÑÐµÐ»ÐµÐŒ Ð¿ÑÐž Ð²ÐŸÐ·ÐœÐžÐºÐœÐŸÐ²ÐµÐœÐžÐž Ð¿ÑÐŸÐ±Ð»ÐµÐŒ Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹. ÐÑÐž ÐŸÐ±ÐœÐ°ÑÑÐ¶ÐµÐœÐžÐž Ð¿ÑÐŸÐ±Ð»ÐµÐŒ ÐžÐ»Ðž ÐŸÑÐžÐ±ÐºÐž, Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone</Text>
+<Text id="503">ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÑÐ»Ð°ÑÑ ÐŸÑÑÐµÑ ÐŸ ÐŽÐžÐ°Ð³ÐœÐŸÑÑÐžÐºÐµ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ ÐœÐ° ÑÑÐŸÑ Ð°ÐŽÑÐµÑ. Ð ÐœÐ°ÐºÐŸÐœÐµÑ, ÐºÑÐ°ÑÐºÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ - ÑÑÐŸ ÐœÐµÐ±ÐŸÐ»ÑÑÐžÐµ Ð¿ÑÐµÐŽÐ»ÐŸÐ¶ÐµÐœÐžÑ, ÐŸÐ¿ÐžÑÑÐ²Ð°ÑÑÐžÐµ, ÐºÐ°Ðº ÑÑÑÑÐŸÐµÐœÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐœÐŸ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð¿ÐŸÐŽ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐŒ About this collection (ÐÐ± ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž) ÐœÐ° Ð¿ÐµÑÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐµÑÑÐŸ ÐœÐ°Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŸÑÐŸÐ±ÑÐ°Ð¶Ð°ÐµÑÑÑ ÑÑÑÐµÐ»ÐºÐŸÐ¹, ÐºÐŸÑÐŸÑÐ°Ñ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÐœÐ° ÐŽÐžÑÐ¿Ð»ÐµÐµ Ð²ÐœÐžÐ·Ñ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÑ. ÐÐ° ÑÐžÑÑÐœÐºÐµ 16Ñ, collection information stage (ÑÑÐ°ÐŽÐžÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž). ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð¿ÑÐŸÐŽÐ²ÐžÐ³Ð°ÐµÑÑÑ Ðº Ð ÐžÑÑÐœÐºÑ 16d, ÐœÐ°Ð¶Ð°Ð² ÐœÐ° Ð·ÐµÐ»ÐµÐœÑÑ ÐºÐœÐŸÐ¿ÐºÑ.</Text>
+</Content>
+</Subsection>
+<Subsection id="source_data">
+<Title>
+<Text id="504">ÐÑÑÐŸÑÐœÐžÐºÐž ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_3">
+<Title>
+<Text id="505">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ° ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐÑÐŸÐŽÐŸÐ»Ð¶)</Text>
+<SubTitle>
+<Text id="506">(d)</Text>
+</SubTitle>
+</Title>
+<File width="368" height="532" url="images/User_Fig_16d.png"/>
+</Figure>
+<Text id="507">ÐÐ°ÑÐžÐœÐ°Ñ Ñ Ð ÐžÑÑÐœÐºÐ° 16d, Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŽÐŸÐ»Ð¶ÐµÐœ ÑÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÑÐµÐºÑÑÐŸÐ²ÑÐµ ÐžÑÑÐŸÑÐœÐžÐºÐž, ÑÐŸÑÑÐ°Ð²Ð»ÑÑÑÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐŸÐ·ÐŽÐ°ÑÑ Ð²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð»ÐžÐ±ÐŸ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÑÑÑÐºÑÑÑÑ, ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐœÐŸÐ¹ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, Ð»ÐžÐ±ÐŸ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÑÑÑÐºÑÑÑÑ, ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ¹ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="508">ÐÑÐ»Ðž Ð²Ñ Ð²ÑÐ±ÐµÑÐµÑÐµ ÑÑÑÑÐºÑÑÑÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ, ÐœÐŸÐ²Ð°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐŒÐŸÐ¶ÐµÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐŸÑÐŒÐ°ÑÐ° HTML (ÑÐ°Ð¹Ð»Ñ, ÐžÐŒÐµÑÑÐžÐµ ÑÐ°ÑÑÐžÑÐµÐœÐžÐµ .htm, .html) ÐžÐ»Ðž Ð¿ÑÐŸÑÑÑÐµ ÑÐµÐºÑÑÐŸÐ²ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ (.txt, .text), ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Microsoft Word (.doc), PDF (.pdf) ÐžÐ»Ðž ÐŽÐŸÐºÑÐŒÐµÐœÑÑ e-mail (.email). ÐÐŸÐ»ÑÑÐµ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐŸ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐ°Ñ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÑÐŸÐŽÐµÑÐ¶ÐžÑÑÑ ÐœÐžÐ¶Ðµ Ð² ÑÐ°ÑÑÐž âÐ€ÐŸÑÐŒÐ°ÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²â.</Text>
+<Text id="509">ÐÑÐ»Ðž Ð²Ñ ÑÐŸÐ·ÐŽÐ°ÐµÑÐµ ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐœÐ° ÐŸÑÐœÐŸÐ²Ðµ ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸ ÑÐ°Ð¹Ð»Ñ Ð² ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÐŸÐ±ÑÐ·Ð°ÑÐµÐ»ÑÐœÐŸ ÑÐŸÐ³ÐŸ Ð¶Ðµ ÑÐ°ÐŒÐŸÐ³ÐŸ ÑÐŸÑÐŒÐ°ÑÐ°, ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°Ð»ÐžÑÑ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ°ÐŒÐµÑÑÑÐµ, ÑÑÐŸ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ ÐœÐµÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐµ ÑÐŸÑÐŒÐ°ÑÑ ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ ÑÐ°Ð¹Ð»ÐŸÐ², Ð² ÑÐŸ Ð²ÑÐµÐŒÑ ÐºÐ°Ðº ÐŽÑÑÐ³ÐžÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÐµÑÑ Ð²ÐŸ Ð²ÑÐ¿ÐŸÐŒÐŸÐ³Ð°ÑÐµÐ»ÑÐœÑÑ
+ ÑÐ°Ð¹Ð»Ð°Ñ
+. ÐÑÐ»Ðž Ð²Ð°ÑÐž ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐ°ÐœÐœÑÐµ ÐœÐµ ÐžÐŒÐµÑÑ ÑÑÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž, ÑÐŸ ÐœÐµÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÐœÐµ Ð±ÑÐŽÑÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐœÐŸÑÐŒÐ°Ð»ÑÐœÐŸ. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐµÑÐ»Ðž Ð²Ñ âÐºÐ»ÐŸÐœÐžÑÑÐµÑÐµâ ÐÐµÐŒÐŸ-ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÑÐŸ Ð·Ð°ÐŒÐµÑÐžÑÐµ, ÑÑÐŸ ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ðž âÐœÐ°Ð·Ð²Ð°ÐœÐžÑ Ð°-Ñâ, âÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐžâ Ðž âÑÐ¿ÐŸÑÐŸÐ±Ñâ ÐœÐµ Ð±ÑÐŽÑÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ. Ð ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÑÑ
+ ÐŸÐºÐœÐ°Ñ
+ ÑÐ»ÐµÐŽÑÐµÑ ÑÐºÐ°Ð·Ð°ÑÑ ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐµ ÐžÑÑÐŸÑÐœÐžÐºÐŸÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+<Text id="510">ÐÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐºÐ°Ð·Ð°ÐœÐŸ ÐŽÐŸ ÑÑÐµÑ
+ ÐŸÑÐŽÐµÐ»ÑÐœÑÑ
+ ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ ÐžÑÑÐŸÑÐœÐžÐºÐŸÐ², ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐœÑÑ
+ ÐœÐ° ÑÐžÑÑÐœÐºÐµ 16d. ÐÑÐ»Ðž Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð±ÐŸÐ»ÑÑÐµ, Ð¿ÑÐŸÑÑÐŸ
+ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÐºÐœÐŸÐ¿ÐºÑ âmore sourcesâ (Ð±ÐŸÐ»ÑÑÐµ ÐžÑÑÐŸÑÐœÐžÐºÐŸÐ²) </Text>
+<Text id="511">Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÑÑÐž Ð²ÐžÐŽÐ° ÑÐºÐ°Ð·Ð°ÐœÐžÐ¹:</Text>
+<BulletList>
+<Bullet>
+<Text id="512">ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Ð² ÑÐžÑÑÐµÐŒÐµ ÑÐµÑÐ²ÐµÑÐ° Greenstone (ÐœÐ°ÑÐžÐœÐ°ÐµÑÑÑ Ñ âfile://â)</Text>
+</Bullet>
+<Bullet>
+<Text id="513">ÐÐŽÑÐµÑ, ÐœÐ°ÑÐžÐœÐ°ÑÑÐžÐ¹ÑÑ Ñ âhttp://â ÐŽÐ»Ñ ÑÐ°Ð¹Ð»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐœÑÐ¶ÐœÐŸ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ Ñ ÐÐœÑÐµÑÐœÐµÑÐ°</Text>
+</Bullet>
+<Bullet>
+<Text id="514">ÐÐŽÑÐµÑ, ÐœÐ°ÑÐžÐœÐ°ÑÑÐžÐ¹ÑÑ Ñ âftp://â ÐŽÐ»Ñ ÑÐ°Ð¹Ð»ÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ¶ÐœÐŸ Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑ Ð°ÐœÐŸÐœÐžÐŒÐœÑÐ¹ FTP.</Text>
+</Bullet>
+</BulletList>
+<Text id="515">ÐÑÐ»Ðž Ð²Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ file:// ÐžÐ»Ðž ftp:// ÐŽÐ»Ñ ÑÐºÐ°Ð·Ð°ÐœÐžÑ ÑÐ°Ð¹Ð»Ð°, ÑÐŸ Ð±ÑÐŽÐµÑ Ð·Ð°Ð³ÑÑÐ¶ÐµÐœ ÑÑÐŸÑ ÑÐ°Ð¹Ð».</Text>
+<Text id="516">ÐÑÐ»Ðž Ð²Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ http://, ÑÐŸ ÑÐµÐ·ÑÐ»ÑÑÐ°Ñ Ð·Ð°Ð²ÐžÑÐžÑ ÐŸÑ ÑÐŸÐ³ÐŸ, Ð²ÑÐŽÐ°ÐµÑ Ð»Ðž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐŸÐ±ÑÑÐœÑÑ ÐžÐœÑÐµÑÐœÐµÑ ÑÑÑÐ°ÐœÐžÑÐºÑ ÐœÐ° ÑÐºÑÐ°Ðœ ÐžÐ»Ðž ÑÐ¿ÐžÑÐŸÐº ÑÐ°Ð¹Ð»ÐŸÐ². ÐÑÐ»Ðž ÑÑÑÐ°ÐœÐžÑÐºÑ, ÑÐŸ ÐŸÐœÐ° Ð±ÑÐŽÐµÑ Ð·Ð°Ð³ÑÑÐ¶ÐµÐœÐ° â ÐºÐ°Ðº Ðž Ð²ÑÐµ ÑÑÑÐ°ÐœÐžÑÑ, ÐœÐ° ÐºÐŸÑÐŸÑÑÐµ ÑÑÑÐµÑÑÐ²ÑÑÑ ÑÑÑÐ»ÐºÐž Ñ ÑÑÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐºÐž Ðž Ñ.ÐŽ. Ð¿ÑÐž ÑÑÐ»ÐŸÐ²ÐžÐž, ÑÑÐŸ ÐŸÐœÐž ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ ÐœÐ° ÐŸÐŽÐœÐŸÐŒ Ð²ÐµÐ±-ÑÐ°Ð¹ÑÐµ.</Text>
+<Text id="517">ÐÑÐ»Ðž Ð²Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÐµ file:// ÐžÐ»Ðž ftp:// ÐŽÐ»Ñ ÑÐºÐ°Ð·Ð°ÐœÐžÑ Ð¿Ð°Ð¿ÐºÐž ÐžÐ»Ðž ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž ÐžÐ»Ðž Ð²Ð²ÐµÐŽÐµÑÐµ http:// Ð°ÐŽÑÐµÑ, ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÐµÐŽÐµÑ Ðº ÑÐ¿ÐžÑÐºÑ ÑÐ°Ð¹Ð»ÐŸÐ², ÑÐŸ Ð²ÑÐµ ÑÑÐŸ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² Ð¿Ð°Ð¿ÐºÐµ Ðž Ð²ÑÐµ Ð¿ÐŸÐŽÐ¿Ð°Ð¿ÐºÐž Ð±ÑÐŽÑÑ Ð²ÐºÐ»ÑÑÐµÐœÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ.</Text>
+<Text id="518">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐºÐ°Ð·Ð°ÑÑ ÐžÑÑÐŸÑÐœÐžÐºÐž ÐŽÑÑÐ³ÐžÑ
+ Ð²ÐžÐŽÐŸÐ².</Text>
+<Text id="519">Ð ÑÐ°ÐºÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ (Ð ÐžÑÑÐœÐŸÐº 16d) ÐœÐŸÐ²Ð°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð±ÑÐŽÐµÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ, Ð²Ð·ÑÑÑÐµ ÐºÐ°Ðº ÐžÐ· Ð»ÐŸÐºÐ°Ð»ÑÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ, ÑÐ°Ðº Ðž Ñ ÐŸÑÐŽÐ°Ð»ÐµÐœÐœÐŸÐ³ÐŸ ÐÐœÑÐµÑÐœÐµÑ-ÑÐµÑÑÑÑÐ°, ÐºÐŸÑÐŸÑÑÐ¹ Ð±ÑÐŽÐµÑ ÑÐºÐ°Ð·Ð°Ðœ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ.</Text>
+<Text id="520">ÐÐŸÐ³ÐŽÐ° Ð²Ñ ÐœÐ°Ð¶ÐŒÐµÑÐµ ÐœÐ° configure collection (ÐºÐŸÐœÑÐžÐ³ÑÑÐžÑÐŸÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ) ÐŽÐ»Ñ Ð¿ÑÐŸÐŽÐŸÐ»Ð¶ÐµÐœÐžÑ Ð¿ÑÐŸÑÐµÑÑÐ° Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ , ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ Ð¿ÑÐŸÐ²ÐµÑÐžÑ, ÐŽÐŸÑÑÑÐ¿ÐœÑ Ð»Ðž Ð²ÑÐµ ÐžÑÑÐŸÑÐœÐžÐºÐž, ÐºÐŸÑÐŸÑÑÐµ Ð²Ñ ÑÐºÐ°Ð·Ð°Ð»Ðž. Ð­ÑÐŸ ÐŒÐŸÐ¶ÐµÑ Ð·Ð°ÐœÑÑÑ ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐµÐºÑÐœÐŽ ÐžÐ»Ðž ÐŽÐ°Ð¶Ðµ ÐŒÐžÐœÑÑ, ÐµÑÐ»Ðž Ð²Ñ ÑÐºÐ°Ð·Ð°Ð»Ðž
+ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÐžÑÑÐŸÑÐœÐžÐºÐŸÐ². ÐÑÐ»Ðž ÐŸÐŽÐžÐœ ÐžÐ»Ðž ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ ÑÐºÐ°Ð·Ð°ÐœÐœÑÑ
+ Ð²Ð°ÐŒÐž ÐžÑÑÐŸÑÐœÐžÐºÐŸÐ² ÐœÐµÐŽÐŸÑÑÑÐ¿ÐœÑ, ÑÐŸ Ð¿ÐŸÑÐ²ÐžÑÑÑ ÑÑÑÐ°ÐœÐžÑÐ°, ÑÑ
+ÐŸÐ¶Ð°Ñ Ñ Ð ÐžÑÑÐœÐºÐŸÐŒ 16Ðµ, Ð³ÐŽÐµ ÑÐºÐ°Ð·Ð°ÐœÑ ÐœÐµÐŽÐŸÑÑÑÐ¿ÐœÑÐµ ÐžÑÑÐŸÑÐœÐžÐºÐž (Ð² ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐŸÐ±Ð°).</Text>
+<Figure id="using_the_collector_to_build_a_new_collection_4">
+<Title>
+<Text id="521">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ° ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐÑÐŸÐŽÐŸÐ»Ð¶)</Text>
+<SubTitle>
+<Text id="522">(e)</Text>
+</SubTitle>
+</Title>
+<File width="368" height="531" url="images/User_Fig_16e.png"/>
+</Figure>
+<Text id="523">ÐÑÑÐŸÑÐœÐžÐºÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐœÐµÐŽÐŸÑÑÑÐ¿ÐœÑ Ð¿ÐŸ ÑÐ»ÐµÐŽÑÑÑÐžÐŒ Ð¿ÑÐžÑÐžÐœÐ°ÐŒ:</Text>
+<BulletList>
+<Bullet>
+<Text id="524">Ð€Ð°Ð¹Ð», ÑÐ°Ð¹Ñ FTP ÐžÐ»Ðž URL ÐœÐµ ÑÑÑÐµÑÑÐ²ÑÑÑ</Text>
+</Bullet>
+<Bullet>
+<Text id="525">ÐÐ°ÐŒ ÐœÑÐ¶ÐœÐŸ Ð¿ÐŸÐŽÐºÐ»ÑÑÐžÑÑÑÑ Ðº ÐžÐœÑÐµÑÐœÐµÑÑ</Text>
+</Bullet>
+<Bullet>
+<Text id="526">ÐÑ Ð¿ÑÑÐ°ÐµÑÐµÑÑ Ð¿ÐŸÐ¿Ð°ÑÑÑ ÐœÐ° Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ Ð°ÐŽÑÐµÑ.</Text>
+</Bullet>
+</BulletList>
+<Text id="527">ÐÐŸÑÐ»ÐµÐŽÐœÐžÐ¹ ÐžÐ· ÑÐ»ÑÑÐ°ÐµÐ² ÑÐ°ÐŒÑÐ¹ ÐœÐµÐ¿ÐŸÐœÑÑÐœÑÐ¹. ÐÐœ ÑÐ»ÑÑÐ°ÐµÑÑÑ ÑÐŸÐ³ÐŽÐ°, ÐºÐŸÐ³ÐŽÐ° Ð²Ñ ÐžÐŒÐµÐµÑÐµ ÐŽÐŸÑÑÑÐ¿ Ðº ÐžÐœÑÐµÑÐœÐµÑÑ Ð¿ÐŸ ÑÐµÐ»ÐµÑÐŸÐœÐœÐŸÐ¹ Ð»ÐžÐœÐžÐž (dial-up). ÐÐœÐŸÐ³ÐŽÐ° Ð±ÑÐ²Ð°ÐµÑ ÑÐ°Ðº, ÑÑÐŸ Ð²Ñ Ð²ÐžÐŽÐžÑÐµ Ð²ÐµÐ±-ÑÑÑÐ°ÐœÐžÑÑ, ÐœÐ°Ð±ÑÐ°Ð² Ð°ÐŽÑÐµÑ Ð² Ð±ÑÐ°ÑÐ·ÐµÑÐµ, Ð° ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ ÐŸÑÐ²ÐµÑÐ°ÐµÑ, ÑÑÐŸ ÑÑÑÐ°ÐœÐžÑÐ° ÐœÐµÐŽÐŸÑÑÑÐ¿ÐœÐ°. ÐÐ±ÑÑÑÐœÐµÐœÐžÐµ ÑÑÐŸÐ³ÐŸ ÑÐŸÑÑÐŸÐžÑ Ð² ÑÐŸÐŒ, ÑÑÐŸ ÑÑÑÐ°ÐœÐžÑÐ° ÐŒÐŸÐ¶ÐµÑ ÐžÑÑ
+ÐŸÐŽÐžÑÑ ÐžÐ· locally cashed copy. Ð ÑÐŸÐ¶Ð°Ð»ÐµÐœÐžÑ, locally cashed copy ÑÐ²Ð»ÑÑÑÑÑ ÐœÐµÐ²ÐžÐŽÐžÐŒÑÐŒÐž ÐŽÐ»Ñ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ°. Ð ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ ÐŒÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ ÑÐœÐ°ÑÐ°Ð»Ð° Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ ÑÑÐž ÑÑÑÐ°ÐœÐžÑÑ ÐžÐ· ÐÐœÑÐµÑÐœÐµÑÐ°.</Text>
+</Content>
+</Subsection>
+<Subsection id="configuring_the_collection">
+<Title>
+<Text id="528">ÐÐ°ÑÑÑÐŸÐ¹ÐºÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_5">
+<Title>
+<Text id="529">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ° ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐÑÐŸÐŽÐŸÐ»Ð¶)</Text>
+<SubTitle>
+<Text id="530">(f)</Text>
+</SubTitle>
+</Title>
+<File width="369" height="467" url="images/User_Fig_16f.png"/>
+</Figure>
+<Text id="531">ÐÐ° Ð ÐžÑÑÐœÐºÐµ 16f ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° ÑÐ»ÐµÐŽÑÑÑÐ°Ñ ÑÑÐ°ÐŽÐžÑ. Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ Ðž Ð¿ÐŸÐºÐ°Ð· Ð²ÑÐµÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐºÐŸÐœÑÑÐŸÐ»ÐžÑÑÐµÑÑÑ ÐŸÑÐŽÐµÐ»ÑÐœÑÐŒ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐŒ ÑÐ°Ð¹Ð»ÐŸÐŒ (ÑÐŒÐŸÑÑÐžÑÐµ ÐœÐžÐ¶Ðµ). ÐÐŸÐ»ÐµÐµ ÐŸÐ¿ÑÑÐœÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ðž ÐŒÐŸÐ³ÑÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ ÑÑÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµÐ¹ ÐŽÐ»Ñ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÑ
+ ÐœÐ°ÑÑÑÐŸÐµÐº. ÐÐŽÐœÐ°ÐºÐŸ, Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ ÑÑÐ°Ð·Ñ Ð¶Ðµ Ð¿ÐµÑÐµÐ¹ÐŽÑÑ Ðº Ð·Ð°Ð²ÐµÑÑÐ°ÑÑÐµÐ¹ ÑÑÐ°ÐŽÐžÐž. ÐÐ° Ð ÐžÑÑÐœÐºÐµ 16d ÐºÐœÐŸÐ¿ÐºÐž configure collection (ÐœÐ°ÑÑÑÐŸÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ) Ðž build collection (Ð¿ÐŸÑÑÑÐŸÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ) ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÑ Ð·ÐµÐ»ÐµÐœÑÐŒ ÑÐ²ÐµÑÐŸÐŒ, ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÑÐŸ ÑÑÐµÑÑÑ ÑÑÐ°ÐŽÐžÑ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÑÐŸÑÑÐŸ Ð¿ÑÐŸÐ¿ÑÑÑÐžÑÑ.</Text>
+<Text id="532">Ð ÐœÐ°ÑÐµÐŒ Ð¿ÑÐžÐŒÐµÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð²ÐœÐµÑ ÐœÐµÐ±ÐŸÐ»ÑÑÐžÐµ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ð² ÐœÐ°ÑÐ°Ð»ÑÐœÑÑ Ð²ÐµÑÑÐžÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž, ÐŽÐŸÐ±Ð°Ð²ÐžÐ² ÑÐ»Ð°Ð³ file_is_url Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐŒ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµÐŒ (plugin) HTML. Ð­ÑÐŸÑ ÑÐ»Ð°Ð¶ÐŸÐº Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð²ÑÑÐ°Ð²Ð»ÑÑÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐžÐœÑÐµÑÐœÐµÑ-Ð°ÐŽÑÐµÑÐŸÐ² Ð² ÐºÐ°Ð¶ÐŽÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ¹ ÐºÐŸÐœÐ²ÐµÐœÑÐžÐµÐ¹, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐŸÐ¹. Ð­ÑÐž ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ ÑÐµÑÐµÐ· ÑÑÑÐ»ÐºÑ ÑÐŸÐµÐŽÐžÐœÑÑÑÑÑ Ñ ÐŸÑÐžÐ³ÐžÐœÐ°Ð»ÐŸÐŒ, ÐºÐŸÑÐŸÑÑÐ¹ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÐÐœÑÐµÑÐœÐµÑÐµ, Ð° ÐœÐµ Ñ ÐºÐŸÐ¿ÐžÐµÐ¹, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐµÐ¹ÑÑ Ð² ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ.</Text>
+</Content>
+</Subsection>
+<Subsection id="building_the_collection_1">
+<Title>
+<Text id="533">ÐÐŸÑÑÑÐŸÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Figure id="using_the_collector_to_build_a_new_collection_6">
+<Title>
+<Text id="534">ÐÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÐ° ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐÑÐŸÐŽÐŸÐ»Ð¶)</Text>
+<SubTitle>
+<Text id="535">(g)</Text>
+</SubTitle>
+</Title>
+<File width="369" height="304" url="images/User_Fig_16g.png"/>
+</Figure>
+<Text id="536">Ð ÐžÑÑÐœÐŸÐº 16g Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÑÐ°ÐŽÐžÑ âÐ¿ÐŸÑÑÑÐŸÐµÐœÐžÑâ. ÐÐ° ÑÑÐŸÐ¹ ÑÑÐ°ÐŽÐžÐž Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ ÑÐ°ÐŒÐŸ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. </Text>
+<Text id="537">ÐÐŸ Ð²ÑÐµÐŒÑ ÑÑÐŸÐ³ÐŸ Ð¿ÑÐŸÑÐµÑÑÐ° ÑÐŸÐ·ÐŽÐ°ÑÑÑÑ ÐžÐœÐŽÐµÐºÑÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ðž Ð¿ÐŸÐžÑÐºÐ° Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ ÑÐµÐŒ, ÑÑÐŸ Ð²Ñ Ð²Ð²ÐµÐ»Ðž Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð». ÐÑÐŸÑÐµÑÑ Ð·Ð°ÐœÐžÐŒÐ°ÐµÑ ÐœÐµÐºÐŸÑÐŸÑÐŸÐµ Ð²ÑÐµÐŒÑ: ÐŸÑ ÐŒÐžÐœÑÑ ÐŽÐŸ ÑÐ°ÑÐŸÐ² Ð² Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÑÐ°Ð·ÐŒÐµÑÐŸÐ² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð±ÑÑÑÑÐŸÐŽÐµÐ¹ÑÑÐ²ÐžÑ Ð²Ð°ÑÐµÐ³ÐŸ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐŸÐ±ÑÐµÐŒÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð·Ð°ÐœÐžÐŒÐ°ÑÑ ÐŽÐ°Ð¶Ðµ ÑÐµÐ»ÑÐ¹ ÐŽÐµÐœÑ.</Text>
+<Text id="538">ÐÐŸÐ³ÐŽÐ° Ð²Ñ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÐµÑÑ ÐœÐ° ÑÑÐŸÐ¹ ÑÑÐ°ÐŽÐžÐž, Ð²ÐœÐžÐ·Ñ ÑÑÑÐ°ÐœÐžÑÑ ÑÐ¿ÐµÑÐžÐ°Ð»ÑÐœÐ°Ñ Ð¿Ð°ÐœÐµÐ»Ñ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ, ÐºÐ°Ðº Ð¿ÑÐŸÑ
+ÐŸÐŽÐžÑ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÐµ, ÐŸÐ±ÐœÐŸÐ²Ð»ÑÑÑÑ ÑÐµÑÐµÐ· ÐºÐ°Ð¶ÐŽÑÐµ Ð¿ÑÑÑ ÑÐµÐºÑÐœÐŽ.</Text>
+<Text id="539">Ð ÑÐ»ÑÑÐ°Ðµ, ÐºÐŸÐ³ÐŽÐ° ÑÐºÐ°Ð·Ð°ÐœÑÐµ ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÑÐ°Ð¹Ð»Ñ ÐžÐ»Ðž ÐžÐœÑÐµÑÐœÐµÑ-Ð°ÐŽÑÐµÑÐ° ÐœÐµ ÑÑÑÐµÑÑÐ²ÑÑÑ ÐžÐ»Ðž ÐŸÐœÐž ÐµÑÑÑ, ÐœÐŸ ÐŸÑÑÑÑÑÑÐ²ÑÐµÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐœÐŸÐµ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ (plugin), ÐºÐŸÑÐŸÑÐŸÐµ ÐŒÐŸÐ³Ð»ÐŸ Ð±Ñ ÐžÑ
+ ÐŸÐ±ÑÐ°Ð±ÐŸÑÐ°ÑÑ, ÐžÐ»Ðž plugin ÐœÐµ ÐŒÐŸÐ¶ÐµÑ ÐœÐ°Ð¹ÑÐž ÑÐŸÐ¿ÑÑÑÑÐ²ÑÑÑÐžÐ¹ ÑÐ°Ð¹Ð», ÑÐ°ÐºÐŸÐ¹ ÐºÐ°Ðº ÑÐžÑÑÐœÐŸÐº, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÐ¹ÑÑ Ð² ÐŽÐŸÐºÑÐŒÐµÐœÑÐµ ÑÐŸÑÐŒÐ°ÑÐ° HTML ÑÐŸ Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÐµÐŽÑÐ¿ÑÐµÐ¶ÐŽÐ°ÑÑÐµÐµ ÑÐŸÐŸÐ±ÑÐµÐœÐžÐµ. Ð­ÑÐŸ ÑÐŽÐµÐ»Ð°ÐœÐŸ Ñ ÑÐŸÐ¹ ÑÐµÐ»ÑÑ ÑÑÐŸÐ±Ñ Ð²Ñ ÐŒÐŸÐ³Ð»Ðž ÐœÐ°Ð±Ð»ÑÐŽÐ°ÑÑ Ð·Ð° Ð¿ÑÐŸÑÐµÑÑÐŸÐŒ. ÐÑÐ»Ðž Ð¿ÑÐŸÐžÐ·ÐŸÐ¹ÐŽÑÑ ÐºÐ°ÐºÐžÐµ-Ð»ÐžÐ±ÐŸ ÑÐ±ÐŸÐž ÐžÐ»Ðž ÐŸÑÐžÐ±ÐºÐž, ÐºÐŸÑÐŸÑÑÐµ ÐŸÑÐŒÐµÐœÑÑ Ð¿ÑÐŸÑÐµÑÑ, ÐŸÐœÐž Ð±ÑÐŽÑÑ Ð²ÑÐ²ÐµÐŽÐµÐœÑ Ð² ÑÑÐŸÐŒ ÐŸÐºÐœÐµ.</Text>
+<Text id="540">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐµÐºÑÐ°ÑÐžÑÑ Ð¿ÑÐŸÑÐµÑÑ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ Ð² Ð»ÑÐ±ÐŸÐµ Ð²ÑÐµÐŒÑ, ÐœÐ°Ð¶Ð°Ð² ÐœÐ° ÐºÐœÐŸÐ¿ÐºÑ stop building (Ð¿ÑÐµÐºÑÐ°ÑÐžÑÑ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÐµ), ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐœÐŸÐ¹ ÐœÐ° Ð ÐžÑÑÐœÐºÐµ 16g. ÐÑÐ»Ðž Ð²Ñ ÐœÐµ Ð²ÐŒÐµÑÐ°ÐµÑÐµÑÑ Ð² Ð¿ÑÐŸÑÐµÑÑ, ÑÐŸ ÐŸÐœ Ð¿ÑÐŸÐŽÐŸÐ»Ð¶ÐžÑÑÑ, Ðž ÐœÐŸÐ²Ð°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð±ÑÐŽÐµÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° Ðž ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐ° Ð¿ÐŸÑÐ»Ðµ Ð·Ð°Ð²ÐµÑÑÐµÐœÐžÑ Ð¿ÑÐŸÑÐµÑÑÐ°.</Text>
+</Content>
+</Subsection>
+<Subsection id="viewing_the_collection">
+<Title>
+<Text id="541">ÐÑÐŸÑÐŒÐŸÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="542">ÐÐŸÑÐ»Ðµ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ Ðž ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð² Ð ÐžÑÑÐœÐºÐµ 16g ÐœÐ° ÐœÐžÐ¶ÐœÐµÐ¹ Ð¿Ð°ÐœÐµÐ»Ðž Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ ÑÑÐŽ ÐºÐœÐŸÐ¿ÐŸÐº, ÐºÐŸÑÐŸÑÑÐµ Ð±ÑÐ»Ðž ÐœÐ° Ð ÐžÑÑÐœÐºÐ°Ñ
+  16b-f Ñ Ð°ÐºÑÐžÐ²ÐœÐŸÐ¹ ÐºÐœÐŸÐ¿ÐºÐŸÐ¹ View (ÐÑÐŸÑÐŒÐŸÑÑ). ÐÐ°Ð¶Ð°Ð² ÐœÐ° ÐœÐµÐµ Ð²Ñ ÑÑÐ°Ð·Ñ Ð¿ÐŸÐ¿Ð°ÐŽÐµÑÐµ Ð² ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ.</Text>
+<Text id="543">Ð ÐœÐ°ÐºÐŸÐœÐµÑ ÑÑÑÐµÑÑÐ²ÑÐµÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ Ð¿ÐŸÑÐ»Ð°ÑÑ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÑÑ Ð¿ÐŸÑÑÑ ÑÐžÑÑÐµÐŒÐœÐŸÐŒÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑÑ ÑÑÐ°Ð·Ñ Ð¶Ðµ Ð¿ÐŸÑÐ»Ðµ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐžÐ»Ðž ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ). Ð­ÑÐŸ Ð¿ÐŸÐŒÐŸÐ³Ð°ÐµÑ Ð»ÐžÑÐ°ÐŒ, ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÑÐŒ Ð·Ð° ÑÐžÑÑÐµÐŒÑ, Ð±ÑÑÑ ÐŸÑÐ²ÐµÐŽÐŸÐŒÐ»ÐµÐœÐœÑÐŒÐž ÐŸ Ð²ÑÐµÑ
+ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑÑ
+ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÑÑÐžÑ
+ Ð² ÑÐžÑÑÐµÐŒÐµ. ÐÐ²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐ°Ñ ÐŸÑÑÑÐ»ÐºÐ° email Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Ð²ÑÐºÐ»ÑÑÐµÐœÐ°, ÐœÐŸ Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐµÐµ Ð°ÐºÑÐžÐ²ÐžÑÐŸÐ²Ð°ÑÑ, ÐœÐ°ÑÑÑÐŸÐžÐ² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» main.cfg (Ð¡ÐŒÐŸÑÑÐžÑÐµ ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ°, ÑÐ°ÑÑÑ <CrossRef target="Chapter" external="Develop" lang="ru" ref="configuring_your_greenstone_site"/>).</Text>
+</Content>
+</Subsection>
+<Subsection id="working_with_existing_collections">
+<Title>
+<Text id="544">Ð Ð°Ð±ÐŸÑÐ° Ñ ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž</Text>
+</Title>
+<Content>
+<Text id="545">ÐÑÐž Ð²Ñ
+ÐŸÐŽÐµ Ð² ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑ Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐºÐ°Ð·Ð°ÑÑ, Ñ
+ÐŸÑÐžÑÐµ Ð»Ðž Ð²Ñ ÑÐŸÐ·ÐŽÐ°ÑÑ Ð¿ÐŸÐ»ÐœÐŸÑÑÑÑ ÐœÐŸÐ²ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐ»Ðž ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ ÑÑÑÐµÑÑÐ²ÑÑÑÐµÐ¹, ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑ ÐžÐ»Ðž ÑÐŽÐ°Ð»ÑÑ ÐŽÐ°ÐœÐœÑÐµ. Ð¡ÐŸÐ·ÐŽÐ°Ð²Ð°Ñ Ð²ÑÐµÐ²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÐµ ÑÑÑÑÐºÑÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž, Greenstone Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ñ Ð»ÐµÐ³ÐºÐŸÑÑÑÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ ÐœÐŸÐ²ÑÐµ ÐŽÐ°ÐœÐœÑÐµ Ð² ÑÑÑÐµÑÑÐ²ÑÑÑÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="546">ÐÐ»Ñ ÑÐ°Ð±ÐŸÑÑ ÑÐŸ ÑÑÐ°ÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹ Ð²Ñ ÑÐœÐ°ÑÐ°Ð»Ð° ÐŽÐŸÐ»Ð¶ÐœÑ Ð²ÑÐ±ÑÐ°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐžÐ· Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐœÐŸÐ³ÐŸ ÑÐ¿ÐžÑÐºÐ°. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐžÐ·Ð°ÑÐžÑÐµÐœÑ ÐŸÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÐ¹: ÑÐ°ÐºÐžÐµ ÐœÐµ Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ Ð² ÑÐ¿ÐžÑÐºÐµ. Ð¡ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐµÐ¹ Ð²Ñ ÑÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŸÐ²ÐµÑÑÐž ÑÐ»ÐµÐŽÑÑÑÐžÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ:</Text>
+<BulletList>
+<Bullet>
+<Text id="547">ÐÐŸÐ±Ð°Ð²ÐžÑÑ ÐœÐŸÐ²ÑÐµ ÐŽÐ°ÐœÐœÑÐµ Ðž Ð¿ÐµÑÐµÑÑÑÐŸÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ</Text>
+</Bullet>
+<Bullet>
+<Text id="548">Ð ÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</Bullet>
+<Bullet>
+<Text id="549">ÐÐŸÐ»ÐœÐŸÑÑÑÑ ÑÐŽÐ°Ð»ÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ</Text>
+</Bullet>
+<Bullet>
+<Text id="550">ÐÐµÑÐµÐ¿ÐžÑÐ°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐœÐ° CD-ROM</Text>
+</Bullet>
+</BulletList>
+<Part id="add_new_data">
+<Title>
+<Text id="551">ÐÐŸÐ±Ð°Ð²Ð»ÐµÐœÐžÐµ ÐœÐŸÐ²ÑÑ
+ ÐŽÐ°ÐœÐœÑÑ
+ </Text>
+</Title>
+<Content>
+<Text id="552">Ð€Ð°Ð¹Ð»Ñ, ÑÐºÐ°Ð·Ð°ÐœÐœÑÐµ Ð²Ð°ÐŒÐž, Ð±ÑÐŽÑÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÐµÐœÑ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. ÐÐ°ÐŒ ÑÐ»ÐµÐŽÑÐµÑ ÑÐ±ÐµÐŽÐžÑÑÑÑ Ð² ÑÐŸÐŒ, ÑÑÐŸÐ±Ñ ÑÐºÐ°Ð·Ð°ÐœÐœÑÐ¹ Ð²Ð°ÐŒÐž ÑÐ°Ð¹Ð» ÐœÐµ Ð±ÑÐ» ÑÐ¶Ðµ Ð² ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÐžÐœÐ°ÑÐµ ÑÐ°ÐŒ Ð±ÑÐŽÑÑ ÐŽÐ²Ðµ ÐºÐŸÐ¿ÐžÐž ÐŸÐŽÐœÐŸÐ³ÐŸ Ðž ÑÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð°. Ð€Ð°Ð¹Ð»Ñ ÐœÑÐ¶ÐœÐŸ ÑÐºÐ°Ð·ÑÐ²Ð°ÑÑ Ð¿ÐŸ Ð¿ÐŸÐ»ÐœÑÐŒ ÐœÐ°Ð·Ð²Ð°ÐœÐžÑÐŒ (pathname), Ð° Ð²ÑÐ±-ÑÑÑÐ°ÐœÐžÑÑ ÐžÑ
+ Ð¿ÐŸÐ»ÐœÑÐŒÐž www-Ð°ÐŽÑÐµÑÐ°ÐŒÐž. Ð¢ÐŸÑÐœÐŸ ÑÐ°Ðº Ð¶Ðµ Ð²Ñ ÐŽÐŸÐ»Ð¶ÐœÑ ÑÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž Ðž ÑÐ°Ð¹Ð»Ñ Ð¿ÑÐž Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÐž ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="553">ÐÑÐ»Ðž Ð²Ñ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑÐµ ÐŽÐ°ÐœÐœÑÐµ Ðº ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð¿ÐŸ ÐºÐ°ÐºÐŸÐ¹-ÑÐŸ Ð¿ÑÐžÑÐžÐœÐµ Ð¿ÑÐŸÑÐµÑÑ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐŸÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ, ÑÐŸ ÑÑÐ°ÑÐ°Ñ Ð²ÐµÑÑÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŸÑÑÐ°ÐµÑÑÑ Ð±ÐµÐ· ÐžÐ·ÐŒÐµÐœÐµÐœÐžÐ¹.</Text>
+</Content>
+</Part>
+<Part id="edit_configuration_file">
+<Title>
+<Text id="554">Ð ÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð°</Text>
+</Title>
+<Content>
+<Text id="555">ÐÐ¿ÑÑÐœÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ðž ÐŒÐŸÐ³ÑÑ ÑÐµÐŽÐ°ÐºÑÐžÑÐŸÐ²Ð°ÑÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð ÑÐµÑÐ²ÐµÑÑÐŸÐ¹ ÑÐ°ÑÑÐž ÐŸÐ¿ÐžÑÐ°ÐœÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÑÑÑÐ°ÐœÐŸÐ²ÐºÐž.</Text>
+</Content>
+</Part>
+<Part id="delete_the_collection">
+<Title>
+<Text id="556">Ð£ÐŽÐ°Ð»ÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</Title>
+<Content>
+<Text id="557">ÐÑÐž ÑÐŽÐ°Ð»ÐµÐœÐžÐž Ð²Ð°Ñ Ð¿ÐŸÐ¿ÑÐŸÑÑÑ Ð¿ÐŸÐŽÑÐ²ÐµÑÐŽÐžÑÑ ÑÐŽÐ°Ð»ÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐ°Ð¿ÐŸÐŒÐœÐžÑÐµ, ÑÑÐŸ Ð¿ÐŸÑÐ»Ðµ ÑÐŽÐ°Ð»ÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐµ Ð²ÐŸÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑÑÑ.</Text>
+</Content>
+</Part>
+<Part id="export_the_collection">
+<Title>
+<Text id="558">ÐÐµÑÐµÐŒÐµÑÐµÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</Title>
+<Content>
+<Text id="559">ÐÑ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐœÐµÑÑÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð² ÑÐŸÑÐŒÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð·Ð°Ð¿ÐžÑÐ°ÐœÐ° ÐœÐ° Ð°Ð²ÑÐŸÐœÐŸÐŒÐœÑÐ¹, ÑÐ°ÐŒÐŸÐ·Ð°Ð¿ÐžÑÑÐ²Ð°ÑÑÐžÐ¹ÑÑ CD-ROM, ÑÐ°Ð±ÐŸÑÐ°ÑÑÐžÐ¹ Ð² Windows. Ð¢Ð°Ðº ÐºÐ°Ðº ÐŽÑÑÐ³ÐžÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ, Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑÐžÐµ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÑÐ°ÐŒÐŸ-ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÑÑÐžÐµÑÑ CD-ROM, ÐŽÐŸÑÐŸÐ³Ðž, Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ ÑÑÑÐµÑÑÐ²ÑÐµÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐŸÐœÐœÑÐ¹ ÐŒÐŸÐŽÑÐ»Ñ.</Text>
+<Text id="560">ÐÐŸÑÐ»Ðµ ÑÐŸÐ³ÐŸ, ÐºÐ°Ðº Ð²Ñ Ð¿ÐµÑÐµÐŒÐµÑÑÐžÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, Ð² ÐŽÐžÐ°Ð»ÐŸÐ³ÐŸÐ²ÐŸÐŒ ÐŸÐºÐœÐµ Ð²ÑÑÐ²ÐµÑÐžÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ, Ð² ÐºÐŸÑÐŸÑÑÑ ÐŸÐœÐ° Ð¿ÐµÑÐµÐœÐµÑÐµÐœÐ°. ÐÑÐž Ð·Ð°Ð¿ÐžÑÐž Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÑÑÑÐŸÐ¹ÑÑÐ²Ð° ÐŽÐ»Ñ Ð·Ð°Ð¿ÐžÑÐž CD (CD-Writer) ÐœÑÐ¶ÐœÐŸ ÑÐ±ÐµÐŽÐžÑÑÑÑ, ÑÑÐŸ Ð²ÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ Ð±ÑÐ»Ð° Ð·Ð°Ð¿ÐžÑÐ°ÐœÐ° ÐœÐ° ÐŽÐžÑÐº.</Text>
+<Text id="561">ÐÑ ÐœÐµ ÑÐŒÐŸÐ³Ð»Ðž ÐŽÐŸ ÐºÐŸÐœÑÐ° Ð¿ÑÐŸÐ²ÐµÑÐžÑÑ Ðž Ð¿ÑÐŸÑÐµÑÑÐžÑÐŸÐ²Ð°ÑÑ Greenstone Installer Ð¿ÑÐž Ð²ÑÐµÐ²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÑ
+ ÑÑÐ»ÐŸÐ²ÐžÑÑ
+ Ð² ÑÐ²ÑÐ·Ðž Ñ ÐŸÑÐµÐœÑ Ð±ÐŸÐ»ÑÑÐžÐŒ ÑÐ°Ð·ÐœÐŸÐŸÐ±ÑÐ°Ð·ÐžÐµÐŒ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐ¹ Windows. Ð¥ÐŸÑÑ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐŸÑ ÐŒÐŸÐ¶ÐµÑ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ CD-ROMÑ, ÑÐ°Ð±ÐŸÑÐ°ÑÑÐžÐµ Ð² ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÑÑ
+ Windows, ÐŸÐœ Ð²ÑÐµ ÐµÑÐµ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÑÑÐ°ÐŽÐžÐž ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐºÐž. ÐÑÐ»Ðž Ð²Ñ ÑÑÐŸÐ»ÐºÐœÐµÑÐµÑÑ Ñ ÐºÐ°ÐºÐžÐŒÐž-Ð»ÐžÐ±ÐŸ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ°ÐŒÐž Ðž Ð±ÑÐŽÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐºÐŸÐŒÐŒÐµÑÑÐµÑÐºÐžÐµ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐŸÐœÐœÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ (ÑÐ°ÐºÐžÐµ, ÐºÐ°Ðº InstallShield) ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ð¡D, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐœÑÑ Greenstone. ÐÑÑÐµÑÐ¿ÐŸÐŒÑÐœÑÑÐ°Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ, ÐºÑÐŽÐ° Ð¿ÐµÑÐµÐŒÐµÑÐ°ÑÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÐŽÐµÑÐ¶ÐžÑ ÑÐµÑÑÑÐµ ÑÐ°Ð¹Ð»Ð°, ÐŸÑÐœÐŸÑÑÑÐžÐµÑÑ Ðº ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐŸÐœÐœÐŸÐŒÑ Ð¿ÑÐŸÑÐµÑÑÑ, Ðž ÑÑÐž Ð¿ÐŸÐŽÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐŽÐµÑÐ¶Ð°Ñ Ð·Ð°ÐºÐŸÐœÑÐµÐœÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ðž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ. Ð£ÐŽÐ°Ð»ÐžÑÐµ ÑÑÐž ÑÐµÑÑÑÐµ ÑÐ°Ð¹Ð»Ð° Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐ¹ÑÐµ InstallShield ÐŽÐ»Ñ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž ÑÑÐžÑ
+ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐ¹ Ðž ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÑÑÐ»ÑÐºÐ° Ðº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ gsdl\server.exe.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+<Subsection id="document_formats_1">
+<Title>
+<Text id="562">Ð€ÐŸÑÐŒÐ°ÑÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² </Text>
+</Title>
+<Content>
+<Text id="563">ÐÑÐž Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ ÐºÐ°Ð¶ÐŽÑÐ¹ ÑÐŸÑÐŒÐ°Ñ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° Ð¿ÑÑÐµÐŒ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÐ¹ Ðº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ (ÐŽÐ°Ð»ÐµÐµ ÐžÐŒÐµÐœÑÐµÑÑÑ - Ð¿Ð»Ð°Ð³ÐžÐœ), ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³Ð»Ðž Ð±Ñ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ ÐºÐ°Ð¶ÐŽÑÐŒ ÑÐŸÑÐŒÐ°ÑÐŸÐŒ Ð¿ÐŸ ÐŸÑÐŽÐµÐ»ÑÐœÐŸÑÑÐž. ÐÐ»Ð°Ð³ÐžÐœÑ ÑÐºÐ°Ð·Ð°ÐœÑ Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Greenstone ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÑÐ°ÑÑÐžÑÐµÐœÐžÐ¹ ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÑÐŸÑÐŒÐ°ÑÐŸÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², â ÐœÐ°Ð¿ÑÐžÐŒÐµÑ, foo.txt ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑÑÑ ÐºÐ°Ðº ÑÐµÐºÑÑÐŸÐ²ÐŸÐ¹ ÑÐ°Ð¹Ð», foo.html ÐºÐ°Ðº HTML, Ð° foo.doc ÐºÐ°Ðº ÐŽÐŸÐºÑÐŒÐµÐœÑ Word.</Text>
+<Text id="564">ÐÐžÐ¶Ðµ Ð²Ñ ÑÐ²ÐžÐŽÐžÑÐµ ÑÐ¿ÐžÑÐŸÐº Ð¿Ð»Ð°Ð³ÐžÐœÐŸÐ², ÐŽÐŸÑÑÑÐ¿ÐœÑÑ
+ ÐŽÐ»Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ Ð²ÐžÐŽÐŸÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÐŸÐ»ÐµÐµ ÐŽÐµÑÐ°Ð»ÑÐœÐŸÐµ ÐŸÐ±ÑÑÑÐœÐµÐœÐžÐµ ÐŸ ÐœÐžÑ
+ Ðž ÐŽÑÑÐ³ÐžÑ
+ Ð²ÐžÐŽÐ°Ñ
+ ÑÐµÐŽÐºÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ² ÐŒÐŸÐ¶ÐœÐŸ ÐœÐ°Ð¹ÑÐž Ð² Ð ÑÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ Ð Ð°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ°.</Text>
+<Part id="textplug">
+<Title>
+<Text id="565">TEXTPlug (*.txt, *.text)</Text>
+</Title>
+<Content>
+<Text id="566">TEXTPlug ÑÐ°ÑÐ¿ÐŸÐ·ÐœÐ°ÐµÑ Ð¿ÑÐŸÑÑÐŸÐ¹ ÑÐµÐºÑÑÐŸÐ²ÐŸÐ¹ ÑÐ°Ð¹Ð» ÐºÐ°Ðº ÐŸÐ±ÑÑÐœÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ. ÐÐœ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÐŸÑÐœÐŸÐ²ÑÐ²Ð°ÑÑÑ ÐœÐ° Ð¿ÐµÑÐ²ÐŸÐ¹ ÑÑÑÐŸÐºÐµ ÑÐ°Ð¹Ð»Ð°. </Text>
+</Content>
+</Part>
+<Part id="htmlplug_(*.htm,_*.html;_also_.shtml,_.shm,_.asp,_.php,_.cgi)">
+<Title>
+<Text id="567">HTMLPlug (*.htm, *.html; also .shtml, .shm, .asp, .php, .cgi)</Text>
+</Title>
+<Content>
+<Text id="568">HTMLPlug ÐŸÐ±ÑÐ°Ð±Ð°ÑÑÐ²Ð°ÐµÑ HTML-ÑÐ°Ð¹Ð»Ñ. ÐÐœ Ð¿ÐŸÐ»ÑÑÐ°ÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÐŸÑÐœÐŸÐ²ÑÐ²Ð°ÑÑÑ ÐœÐ° ÑÑÐ³Ðµ &lt;title&gt; (ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ), ÐŽÑÑÐ³ÐžÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐ°ÐºÐ¶Ðµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð¿ÐŸÐ»ÑÑÐµÐœÑ Ð¿ÑÐž Ð¿ÐŸÐŒÐŸÑÐž ÑÐžÐœÑÐµÐºÑÐ° ÐŒÐµÑÐ°ÑÑÐ³ÐŸÐ² HTML (HTMLâs metatag syntex) . Ð¡ÑÑÐµÑÑÐ²ÑÑÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ð¿ÑÐž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž ÑÑÐŸÐ³ÐŸ Ð¿Ð»Ð°Ð³ÐžÐœÐ°, ÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐµ Ð² Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ Ð Ð°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ°.</Text>
+</Content>
+</Part>
+<Part id="wordplug_(*.doc)">
+<Title>
+<Text id="569">WORDPlug (*.doc)</Text>
+</Title>
+<Content>
+<Text id="570">WORDPlug ÐžÐŒÐ¿ÐŸÑÑÐžÑÑÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Microsoft Word. Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐŒÐœÐŸÐ³ÐŸ ÑÐ°Ð·ÐœÑÑ
+ Ð²ÐµÑÑÐžÐ¹ ÑÐŸÑÐŒÐ°ÑÐ° Word, Ðž ÐŽÐ°Ð¶Ðµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Microsoft ÑÐ°ÑÑÐŸ ÑÐŸÐ²ÐµÑÑÐ°ÑÑ ÐŸÑÐžÐ±ÐºÐž Ð¿ÑÐž Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÐž. Greenstone ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐœÐµÐ·Ð°Ð²ÐžÑÐžÐŒÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ ÐŽÐ»Ñ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ ÑÐ°Ð¹Ð»ÐŸÐ² Word Ð² ÑÐŸÑÐŒÐ°Ñ HTML. ÐÐ»Ñ ÐœÐµÐºÐŸÑÐŸÑÑÑ
+ ÑÑÐ°ÑÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ² Word Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Ð¿ÑÐŸÑÑÐŸÐ¹ Ð°Ð»Ð³ÐŸÑÐžÑÐŒ ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÑ (extraction algorithm), ÐºÐŸÑÐŸÑÑÐ¹ ÐœÐ°Ñ
+ÐŸÐŽÐžÑ Ð²ÑÐµ ÑÐµÐºÑÑÐŸÐ²ÑÐµ ÑÑÑÐŸÐºÐž Ð² ÐžÑÑ
+ÐŸÐŽÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ.</Text>
+</Content>
+</Part>
+<Part id="pdfplug_(*.pdf)">
+<Title>
+<Text id="571">PDFPlug (*.pdf)</Text>
+</Title>
+<Content>
+<Text id="572">PDFPlug ÐžÐŒÐ¿ÐŸÑÑÐžÑÑÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð² ÑÐŸÑÐŒÐ°ÑÐµ PDF. Ð¢Ð°Ðº Ð¶Ðµ, ÐºÐ°Ðº Ðž WORDPlug, ÐŸÐœ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐœÐµÐ·Ð°Ð²ÐžÑÐžÐŒÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, Ð² ÑÑÐŸÐŒ ÑÐ»ÑÑÐ°Ðµ pdftohtml, ÐŽÐ»Ñ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ PDF ÑÐ°Ð¹Ð»ÐŸÐ² Ð² HTML.</Text>
+<Text id="573">ÐÐ°Ðº Ðž Ð² ÑÐ»ÑÑÐ°Ðµ Ñ WORDPlug, Ð¿ÑÐž ÐœÐ°Ð¶Ð°ÑÐžÐž ÐœÐ° ÐžÐºÐŸÐœÐºÑ document ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Ð±ÑÐŽÐµÑ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÑÐ°Ð¹Ð», ÑÐºÐ²ÐžÐ²Ð°Ð»ÐµÐœÑÐœÑÐ¹ HTML; ÑÐµÐŒ ÐœÐµ ÐŒÐµÐœÐµÐµ, ÑÑÑÐŸÐºÐž ÑÐŸÑÐŒÐ°ÑÐ° Ð² ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐœÐ°ÑÑÑÐŸÐµÐœÑ ÑÐ°Ðº, ÑÑÐŸÐ±Ñ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÐžÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐžÐŒÐµÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÐœÐ°ÑÐ°Ð»ÑÐœÐŸÐŒÑ PDF-ÑÐ°Ð¹Ð»Ñ, Ðž ÐŒÑ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÐŒ Ð²Ð°ÐŒ ÑÐŽÐµÐ»Ð°ÑÑ ÐžÐŒÐµÐœÐœÐŸ ÑÐ°Ðº. Ð¡ÐœÐŸÐ²Ð° Ð¿ÑÐŸÑÑÐŸ Ð·Ð°ÐŒÐµÐœÐžÑÐµ ÑÑÐ³Ðž <i>&lt;link&gt; âŠ &lt;/link&gt;</i> ÐœÐ° <i>&lt;srclink&gt; âŠ &lt;/srclink&gt;</i>.</Text>
+<Text id="574">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° pdftohtml ÐœÐµ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ñ ÐœÐµÐºÐŸÑÐŸÑÑÐŒÐž PDF-ÑÐ°Ð¹Ð»Ð°ÐŒÐž. ÐÐµÐ»ÐŸ Ð² ÑÐŸÐŒ, ÑÑÐŸ Ð¿ÑÐŸÑÐµÑÑ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ Ð·Ð°ÐœÐžÐŒÐ°ÐµÑ ÐŸÑÐµÐœÑ ÐŒÐœÐŸÐ³ÐŸ Ð²ÑÐµÐŒÐµÐœÐž, Ðž ÑÐ°ÑÑÐŸ Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ ÑÐŸÐŸÐ±ÑÐµÐœÐžÑ ÐŸ ÑÐ±ÐŸÐµ, ÑÐ²ÑÐ·Ð°ÐœÐœÐŸÐŒ Ñ Ð¿ÑÐŸÑÐµÑÑÐŸÐŒ Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐžÑ. ÐÑÐ»Ðž ÑÑÐŸ ÑÐ°Ðº, ÑÐŸ ÐµÐŽÐžÐœÑÑÐ²ÐµÐœÐœÐŸÐµ ÑÐµÑÐµÐœÐžÐµ - ÑÑÐŸ ÑÐŽÐ°Ð»ÐžÑÑ ÑÑÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑ ÐžÐ· ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. Ð¢Ð°Ðº Ð¶Ðµ PDFPlug ÐœÐµ ÐŒÐŸÐ¶ÐµÑ ÑÐ¿ÑÐ°Ð²ÐžÑÑÑÑ Ñ Ð·Ð°ÑÐžÑÑÐŸÐ²Ð°ÐœÐœÑÐŒÐž ÑÐ°Ð¹Ð»Ð°ÐŒÐž PDF.</Text>
+</Content>
+</Part>
+<Part id="psplug_(*.ps)">
+<Title>
+<Text id="575">PSPlug (*.ps)</Text>
+</Title>
+<Content>
+<Text id="576">PSPlug ÐžÐŒÐ¿ÐŸÑÑÐžÑÑÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐŸÑÐŒÐ°ÑÐ° PostScript. ÐÑÑÑÐµ Ð²ÑÐµÐ³ÐŸ ÐŸÐœ ÑÐ°Ð±ÐŸÑÐ°ÐµÑ, ÐµÑÐ»Ðž ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Linux, ÐºÐŸÑÐŸÑÐ°Ñ ÐœÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ ps2ascii. ÐÐœÐ° ÐŽÐŸÑÑÑÐ¿ÐœÐ° Ð² Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²Ðµ Linux-ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑÑ
+, ÐœÐŸ ÐœÐµ Ð² Windows. ÐÑÐ»Ðž ÑÑÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐœÐµÐŽÐŸÑÑÑÐ¿ÐœÐ°, PSPlug ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Ð¿ÑÐŸÑÑÐŸÐ¹ Ð°Ð»Ð³ÐŸÑÐžÑÐŒ ÑÐµÐºÑÑÐŸÐ²ÐŸÐ³ÐŸ ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÑ.</Text>
+</Content>
+</Part>
+<Part id="emailplug_(*.email)">
+<Title>
+<Text id="577">EMAILPlug (*.email)</Text>
+</Title>
+<Content>
+<Text id="578">EMAILPlug ÐžÐŒÐ¿ÐŸÑÑÐžÑÑÐµÑ ÑÐ°Ð¹Ð»Ñ, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÐµ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÑÑ Ð¿ÐŸÑÑÑ, Ðž ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ñ Ð¿ÑÐžÐ²ÑÑÐœÑÐŒÐž E-mail ÑÐŸÑÐŒÐ°ÑÐ°ÐŒÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐŒÐž Ð² Netscape, Eudora, Unix. ÐÐ°Ð¶ÐŽÑÐ¹ ÐžÑÑ
+ÐŸÐŽÐœÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ Ð¿ÑÐŸÐ²ÐµÑÑÐµÑÑÑ ÐœÐ° ÐœÐ°Ð»ÐžÑÐžÐµ ÐŸÐŽÐœÐŸÐ¹ ÐžÐ»Ðž ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÑ
+ ÑÐ»ÐµÐºÑÑÐŸÐœÐœÑÑ
+ Ð¿ÐŸÑÑ, ÑÐŸÐµÐŽÐžÐœÐµÐœÐœÑÑ
+ Ð² ÐŸÐŽÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ, Ðž Ð¿ÑÐµÐŸÐ±ÑÐ°Ð·ÐŸÐ²ÑÐ²Ð°ÐµÑ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐµ. ÐÐ»Ð°Ð³ÐžÐœ ÐžÐ·Ð²Ð»ÐµÐºÐ°ÐµÑ ÐºÐ°Ð¶ÐŽÑÐ¹ Ð²ÐžÐŽ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+, ÑÐ°ÐºÐžÑ
+ ÐºÐ°Ðº Ð¢ÐµÐŒÐ°, ÐÐŸÐŒÑ, ÐÑ ÐºÐŸÐ³ÐŸ, ÐÐ°ÑÐ°. Ð¢ÐµÐŒ ÐœÐµ ÐŒÐµÐœÐµÐµ, ÑÑÐŸÑ Ð¿Ð»Ð°Ð³ÐžÐœ ÐµÑÐµ ÐœÐµ ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÐ»ÐœÐŸÑÑÑÑ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ Ð¿ÐŸÑÑÐŸÐ¹, ÐºÐŸÐŽÐžÑÐŸÐ²Ð°ÐœÐœÐŸÐ¹ Ð² MIME.</Text>
+</Content>
+</Part>
+<Part id="zipplug_(.gz,_.z,_.tgz,_.taz,_.bz,_.zip,_.tar)">
+<Title>
+<Text id="579">ZIPPlug (.gz, .z, .tgz, .taz, .bz, .zip, .tar)</Text>
+</Title>
+<Content>
+<Text id="580">ÐÐ»Ð°Ð³ÐžÐœ ZIPPlug ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÑÐŸ ÑÐ¶Ð°ÑÑÐŒÐž ÐžÐ»Ðž Ð·Ð°Ð°ÑÑ
+ÐžÐ²ÐžÑÐŸÐ²Ð°ÐœÐœÑÐŒÐž ÐžÑÑ
+ÐŸÐŽÐœÑÐŒÐž ÑÐŸÑÐŒÐ°ÑÐ°ÐŒÐž: gzip(.gz,.z,.tgz,.taz), bzip (.bz), zip (zip, .jar)
+and tar (.tar). ÐÐœ Ð±Ð°Ð·ÐžÑÑÐµÑÑÑ ÐœÐ° ÑÐ°ÐºÐžÑ
+ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°Ñ
+, ÐºÐ°Ðº gunzip, bunzip,unzip Ðž bar, ÐºÐŸÑÐŸÑÑÐµ ÑÐ²Ð»ÑÑÑÑÑ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐŒÐž Linux-ÑÑÐžÐ»ÐžÑÐ°ÐŒÐž. Ð Windows ZIPPlug ÐŸÑÐºÐ»ÑÑÐµÐœ.</Text>
+</Content>
+</Part>
+</Content>
+</Subsection>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="administration">
+<Title>
+<Text id="581">ÐÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</Title>
+<Content>
+<Text id="582">Ð¡ÑÐµÐŽÑÑÐ²ÐŸ ÐŽÐ»Ñ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ Ð²ÐºÐ»ÑÑÐµÐœÐŸ Ð²ÐŸ Ð²ÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ Greenstone. Ð§ÑÐŸÐ±Ñ ÐŸÑÐºÑÑÑÑ ÑÑÐŸ ÑÑÐµÐŽÑÑÐ²ÐŸ, Ð¿ÑÐŸÑÑÐŸ ÐœÐ°Ð¶ÐŒÐžÑÐµ ÐœÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ ÑÑÑÐ»ÐºÑ ÐœÐ° ÑÑÐ°ÑÑÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ.</Text>
+<Text id="583">ÐÐ°ÑÐ°Ð»ÑÐœÐ°Ñ ÑÑÑÐ°ÐœÐžÑÐ°, Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐ°Ñ ÐœÐ° Ð ÐžÑÑÐœÐºÐµ 17, ÐŽÐ°ÐµÑ ÐŸÐ±Ð·ÐŸÑ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐžÐ· ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐœÐ°Ñ
+ÐŸÐŽÑÑÐžÑ
+ÑÑ Ð² ÑÐžÑÑÐµÐŒÐµ. ÐÐ°ÐŒÐµÑÑÑÐµ, ÑÑÐŸ ÑÑÐŽÐ° Ð²ÐºÐ»ÑÑÐµÐœÑ Ð²ÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž â ÑÐ°Ðº ÐºÐ°Ðº ÐŒÐŸÐ³ÑÑ ÑÑÑÐµÑÑÐ²ÐŸÐ²Ð°ÑÑ "ÑÐ°ÑÑÐœÑÐµ", ÐºÐŸÑÐŸÑÑÐµ ÐœÐµ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ ÐœÐ° ÑÑÐ°ÑÑÐŸÐ²ÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ Greenstone. ÐÐœÐž Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ Ð²ÐœÐµ Ð·Ð°Ð²ÐžÑÐžÐŒÐŸÑÑÐž ÐŸÑ ÑÐŸÐ³ÐŸ, ÐžÐŒÐµÑÑ Ð»Ðž ÐŸÐœÐž ÑÐŸÐºÑÐ°ÑÐµÐœÐœÐŸÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐžÐ»Ðž Ð¿ÐŸÐ»ÐœÐŸÐµ, ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÑ Ð»Ðž Ð² ÐŽÐŸÑÑÑÐ¿Ðµ, Ð² ÑÐ°Ð±ÐŸÑÐµÐŒ ÑÐŸÑÑÐŸÑÐœÐžÐž ÐžÐ»Ðž ÐœÐµÑ. ÐÑÐžÐœÐ°Ð¶Ð°ÑÐžÐž ÐœÐ° ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÑÑ Ð°Ð±Ð±ÑÐµÐ²ÐžÐ°ÑÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (Ð¿ÐµÑÐ²Ð°Ñ ÐºÐŸÐ»ÐŸÐœÐºÐ° ÑÑÑÐ»ÐŸÐº ÐœÐ° ÑÐžÑÑÐœÐºÐµ 17) Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð²ÑÐ²ÐŸÐŽÐžÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð¿ÐŸÐ»ÑÑÐµÐœÐœÑÑ ÐžÐ· ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ³ÐŸ ÑÐ°Ð¹Ð»Ð° Ðž ÐžÐ· ÐŽÑÑÐ³ÐžÑ
+ Ð²ÐœÑÑÑÐµÐœÐœÐžÑ
+ ÑÑÑÑÐºÑÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ ÑÑÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÑÐ»Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ ÑÐ²Ð»ÑÐµÑÑÑ ÐŸÐ±ÑÐµÐŽÐŸÑÑÑÐ¿ÐœÐŸÐ¹ Ðž ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² ÑÐ°Ð±ÐŸÑÐµÐŒ ÑÐŸÑÑÐŸÑÐœÐžÐž, ÐœÐ°Ð¶Ð°ÑÐžÐµ ÐœÐ° Ð¿ÐŸÐ»ÐœÐŸÐµ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (Ð²ÑÐŸÑÐ°Ñ ÑÑÑÐ»ÐºÐ°) Ð¿ÑÐžÐ²ÐµÐŽÐµÑ Ð²Ð°Ñ Ðº ÑÐ°ÐŒÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="584">ÐÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐºÐŸÑÐŸÑÑÑ ÐŒÑ Ð¿ÐŸÑÑÑÐŸÐžÐ»Ðž Ð² ÑÐ°Ð·ÐŽÐµÐ»Ðµ 3.2-3.6, ÐŒÑ ÐœÐ°Ð·Ð²Ð°Ð»Ðž wohiex, ÐžÐ· ÐŸÑÑÑÐ²ÐºÐ° Women's History Excerpt, Ðž ÐŸÐœÐ° Ð²ÐžÐŽÐœÐ° Ð²ÐœÐžÐ·Ñ Ð ÐžÑÑÐœÐºÐ° 17. ÐÐ° Ð ÐžÑÑÐœÐºÐµ 18 ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐ° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÑÐž ÐœÐ°Ð¶Ð°ÑÐžÐž ÐœÐ° ÑÑÑ ÑÑÑÐ»ÐºÑ. Ð Ð¿ÐµÑÐ²ÐŸÐ¹ ÑÐ°ÑÑÐž ÐµÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ Ðž ÑÐ°Ð·ÐŒÐµÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž (ÐŸÐºÐŸÐ»ÐŸ 1000 ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐŸÐºÐŸÐ»ÐŸ 1 ÐŒÐžÐ»Ð»ÐžÐŸÐœÐ° ÑÐ»ÐŸÐ² ÑÐ°Ð·ÐŒÐµÑÐŸÐŒ Ð² 6 mb). Ð¡Ð»ÐµÐŽÑÑÑÐ°Ñ ÑÐ°ÑÑÑ ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð²ÐœÑÑÑÐµÐœÐœÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, ÐŸÑÐœÐŸÑÑÑÑÑÑÑ Ðº Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ñ ÑÐ²ÑÐ·Ðž, ÑÐµÑÐµÐ· ÐºÐŸÑÐŸÑÑÐ¹ ÐŸÑÐºÑÑÐ²Ð°ÐµÑÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ. Ð Ð¿ÑÐžÐŒÐµÑÑ, ÐŸÐ¿ÑÐžÐž ÑÐžÐ»ÑÑÑÐ°ÑÐžÐž (filter options) ÐŽÐ»Ñ ÑÐžÐ»ÑÑÑÐ° Ð·Ð°Ð¿ÑÐŸÑÐ° (query filter) Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÐŸÐ¿ÑÐžÐž Ðž Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÐµ ÑÑÐ»ÐŸÐ²ÐžÑ, ÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÑ Ð¿ÑÐž Ð¿ÐŸÑÑÐ°ÐœÐŸÐ²ÐºÐµ Ð·Ð°Ð¿ÑÐŸÑÐ° Ð² Ð¿ÑÐŸÑÐµÑÑÐµ Ð¿ÐŸÐžÑÐºÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+<Text id="585">ÐÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐ°ÐºÐ¶Ðµ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÐµÑ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸÐ± ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Ðž Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐµÐµ ÐŒÐŸÐŽÐžÑÐžÑÐžÑÐŸÐ²Ð°ÑÑ. ÐÐœÐ° Ð¿ÐŸÐŒÐŸÐ³Ð°ÐµÑ Ð°ÐœÐ°Ð»ÐžÐ·ÐžÐ·ÐžÑÐŸÐ²Ð°ÑÑ ÑÐ°Ð¹Ð»Ñ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐž (logs), ÐŽÐ°Ð²ÑÐžÐµ Ð²ÐœÑÑÑÐµÐœÐœÐžÐ¹ ÑÐ±ÐŸÐ¹, Ðž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐžÐµ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÑÐ°Ð¹Ð»Ñ (user logs), ÐºÐŸÑÐŸÑÑÐµ Ð·Ð°Ð¿ÐžÑÑÐ²Ð°ÑÑ Ð²ÑÐµ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž, ÑÐŸÐ²ÐµÑÑÐ°ÐµÐŒÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒÐž. ÐÐœÐ° ÑÐ°ÐºÐ¶Ðµ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÐŸÑÐŽÐµÐ»ÑÐœÐŸÐŒÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ (ÐžÐ»Ðž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ) Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÑÑ ÐŽÐŸÑÑÑÐ¿ ÐŽÑÑÐ³ÐžÐŒ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ðž ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ ÐœÐŸÐ²ÑÐ¹ ÐŒÐ°ÑÐµÑÐžÐ°Ð» Ðº Ð³ÐŸÑÐŸÐ²ÑÐŒ ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ð°ÐŒ. ÐÑÐµ ÑÑÐž ÑÑÐµÐŽÑÑÐ²Ð° ÐŽÐŸÑÑÑÐ¿ÐœÑ ÐžÐ· ÐŒÐµÐœÑ Ð² Ð»ÐµÐ²ÐŸÐ¹ ÑÐ°ÑÑÐž Ð ÐžÑÑÐœÐºÐ° 5. </Text>
+<Figure id="greenstone_administration_facility">
+<Title>
+<Text id="586">Ð¡ÑÐµÐŽÑÑÐ²Ð° Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ Greenstone</Text>
+</Title>
+<File width="335" height="699" url="images/User_Fig_17.png"/>
+</Figure>
+<Figure id="information_about_the_women's_history_excerpt_collection">
+<Title>
+<Text id="587">ÐÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Women's History Excerpt</Text>
+</Title>
+<File width="331" height="699" url="images/User_Fig_18a.png"/>
+<File width="331" height="699" url="images/User_Fig_18b.png"/>
+</Figure>
+<Section id="configuration_files">
+<Title>
+<Text id="588">ÐÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÑÐ°Ð¹Ð»Ñ</Text>
+</Title>
+<Content>
+<Text id="589">Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÐŽÐ²Ð° ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÑ
+ ÑÐ°Ð¹Ð»Ð°, ÐºÐŸÑÐŸÑÑÐµ ÐŸÑÐ²ÐµÑÐ°ÑÑ Ð·Ð° ÑÐ°Ð±ÐŸÑÐµÐµ ÑÐŸÑÑÐŸÑÐœÐžÐµ Greenstone: ÑÐ°Ð¹Ð» ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐž ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÑ (site configuration) gsdlsite.cfg Ðž Ð³Ð»Ð°Ð²ÐœÑÐ¹ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» main.cfg.</Text>
+<Text id="590">ÐÐŸÐœÑÐžÐ³-ÑÐ°Ð¹Ð» gsdlsite.cfg ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÑ, ÐºÑÐŽÐ° Ð±ÑÐŽÐµÑ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°. ÐÐœ ÑÐ¿ÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°Ðœ ÑÐ°ÐºÐžÐŒ ÐŸÐ±ÑÐ°Ð·ÐŸÐŒ, ÑÑÐŸÐ±Ñ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÐŸÐ¿ÑÐžÐž ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐŸÐ²Ð°Ð»Ðž ÑÐŸÐ»ÑÐºÐŸ ÑÑÐŸÐŒÑ ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÑ. Ð Ð¿ÑÐžÐŒÐµÑÑ, ÑÑÐŸ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, ÐºÑÐŽÐ° ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°, HTTP-Ð°ÐŽÑÐµÑ ÑÐžÑÑÐµÐŒÑ Greenstone, Ðž ÐœÐ°Ð»ÐžÑÐžÐµ Ð² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž ÑÑÐµÐŽÑÑÐ²Ð° fastcgi. ÐÐŸÐœÑÑÐžÑ, ÑÐ¿ÐŸÐŒÑÐœÑÑÑÐµ Ð² ÑÑÐŸÐŒ Ð¿Ð°ÑÐ°Ð³ÑÐ°ÑÐµ, Ð±ÐŸÐ»ÐµÐµ ÐŽÐµÑÐ°Ð»ÑÐœÐŸ ÑÐ°Ð·ÐŸÐ±ÑÐ°ÐœÑ Ð² Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ Ð¿ÐŸ Ð£ÑÑÐ°ÐœÐŸÐ²ÐºÐµ.</Text>
+<Text id="591">Ð ÑÐ°Ð¹Ð»Ðµ Main.cfg ÑÐŸÐŽÐµÑÐ¶ÐžÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÑÐžÑÑÑÐ° Ð²ÑÐµÐŒ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°ÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÑ
+ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ Greenstone. ÐÐœ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð² ÑÐµÐ±Ñ Ð°ÐŽÑÐµÑ E-mail ÑÐžÑÑÐµÐŒÐœÐŸÐ³ÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÑÐ°, ÑÐ°ÐºÐžÐµ ÐŸÐ¿ÑÐžÐž, ÐºÐŸÑÐŸÑÑÐµ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ, Ð²ÐºÐ»ÑÑÐµÐœÑ Ð»Ðž ÑÑÐ°ÑÑÑÐœÑÐµ Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐŸÑÐœÑÐµ ÑÑÑÐ°ÐœÐžÑÑ, ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÑ Ð»Ðž ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÑÐ°Ð¹Ð»Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹, Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ Ð»Ðž ÐÐœÑÐµÑÐœÐµÑ-cookies ÐŽÐ»Ñ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÐž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹.</Text>
+</Content>
+</Section>
+<Section id="logs">
+<Title>
+<Text id="592">Ð€Ð°Ð¹Ð»Ñ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐž</Text>
+</Title>
+<Content>
+<Text id="593">Ð¡ÑÑÐµÑÑÐ²ÑÐµÑ ÑÑÐž Ð²ÐžÐŽÐ° ÑÐ°Ð¹Ð»ÐŸÐ² ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐž, Ñ ÐºÐŸÑÐŸÑÑÐŒÐž Ð²Ñ ÑÑÐ°Ð»ÐºÐœÐµÑÐµÑÑ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ: Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐžÐµ Ð»ÐŸÐ³Ðž, Ð»ÐŸÐ³Ðž ÐŸÑÐžÐ±ÐŸÐº Ðž ÐžÐœÐžÑÐžÐ°Ð»ÐžÐ·Ð°ÑÐžÐž. ÐÐŸÑÐ»ÐµÐŽÐœÐžÐµ ÐŽÐ²Ð° ÐœÐ°Ð²ÐµÑÐœÑÐºÐ° Ð±ÑÐŽÑÑ Ð¿ÐŸÐ»ÐµÐ·ÐœÑ ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ»Ñ Ð»ÑÐŽÐµÐ¹, Ð·Ð°ÐœÐžÐŒÐ°ÑÑÐžÑ
+ÑÑ ÑÐµÑ
+ÐœÐžÑÐµÑÐºÐžÐŒ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµÐŒ ÑÑÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ.</Text>
+<Text id="594">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone ÐŒÐŸÐ¶ÐµÑ ÑÐŸÑ
+ÑÐ°ÐœÑÑÑ Ðž Ð·Ð°Ð¿ÐžÑÑÐ²Ð°ÑÑ Ð²ÑÐµ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž, ÑÐŸÐ²ÐµÑÑÐ°ÐµÐŒÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐŒ ÐœÐ° ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÑÑÑÐ°ÐœÐžÑÐµ, ÐºÐŸÑÐŸÑÑÑ ÐŸÐœ Ð¿ÐŸÑÐµÑÐžÐ», Ð±ÐµÐ· ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÐœÐžÐºÐ°ÐºÐžÑ
+ Ð»ÐžÑÐœÑÑ
+. Ð ÐµÐ³ÐžÑÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÑÐ°Ð¹Ð»Ñ, Ð¿ÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ Ð²ÑÐºÐ»ÑÑÐµÐœÐœÑÐµ, ÐŒÐŸÐ¶ÐœÐŸ Ð°ÐºÑÐžÐ²ÐžÑÐŸÐ²Ð°ÑÑ, ÐŽÐŸÐ±Ð°Ð²ÐžÐ² ÑÐ»ÐµÐŽÑÑÑÑÑ ÑÑÑÐŸÐºÑ Ð² Ð³Ð»Ð°Ð²ÐœÐŸÐŒ ÑÐžÑÑÐµÐŒÐœÐŸÐŒ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ:</Text>
+<CodeLine>logcgiargs true</CodeLine>
+<CodeLine>usecookies true</CodeLine>
+<Text id="595">ÐÐŸ ÑÐŒÐŸÐ»ÑÐ°ÐœÐžÑ ÐŸÐœÐž Ð²ÑÐºÐ»ÑÑÐµÐœÑ Ðž Ð¿ÐŸÑÑÐŸÐŒÑ ÐœÐµ Ð¿ÑÐŸÐžÑÑ
+ÐŸÐŽÐžÑ ÐœÐžÐºÐ°ÐºÐŸÐ¹ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐž ÐŽÐŸ ÐžÑ
+ Ð²ÐºÐ»ÑÑÐµÐœÐžÑ. Ð¡ÑÑÐŸÐºÐ° logcgiargs Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ðž Ð²ÑÐºÐ»ÑÑÐ°ÐµÑ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÑ. ÐÐºÑÐžÐ²ÐžÑÐŸÐ²Ð°Ð² usecookies, ÐºÐ°Ð¶ÐŽÐŸÐŒÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð¿ÑÐžÑÐ²Ð°ÐžÐ²Ð°ÐµÑÑÑ ÐŸÑÐŸÐ±ÑÐ¹ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÐºÐŸÐŽ, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÑÐŸÑÐ»ÐµÐŽÐžÑÑ Ð·Ð° ÐŽÐµÐ¹ÑÑÐ²ÐžÑÐŒÐž ÐŸÑÐŽÐµÐ»ÑÐœÐŸÐ³ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÑÐµÑÐµÐ· ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð».</Text>
+<Text id="596">ÐÐ°Ð¶ÐŽÐ°Ñ ÑÑÑÐŸÐºÐ° Ð² Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐŸÐŒ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ Ð·Ð°Ð¿ÐžÑÑÐ²Ð°ÐµÑ Ð¿ÐŸÑÐµÑÐµÐœÐœÑÑ, ÑÑÑÐ°ÐœÐžÑÑ. ÐÐœ ÑÐŸÐŽÐµÑÐ¶ÐžÑ (a) IP Ð°ÐŽÑÐµÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ, (Ðª) Ð²ÑÐµÐŒÑ Ð¿ÑÐŸÐ²ÐµÐŽÐµÐœÐœÐŸÐµ ÑÐ°ÐŒ, (Ñ) Ð°ÑÐ³ÑÐŒÐµÐœÑÑ CGI Ð² ÑÐºÐŸÐ±ÐºÐ°Ñ
+ Ðž (d) ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ Ð±ÑÐ°ÑÐ·ÐµÑÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ (ÐœÐ°Ð¿ÑÐžÐŒÐµÑ Netscape ÐœÐ°Ð·ÑÐ²Ð°ÐµÑÑÑ "Mozilla"). ÐÐžÐ¶Ðµ Ð¿ÑÐžÐ²ÐµÐŽÐµÐœÐ° ÐŽÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐ°Ñ Ð»ÐžÐœÐžÑ, ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐ°Ñ ÐºÐ°Ð¶ÐŽÑÐ¹ ÐžÐ· ÐŸÐ¿ÐžÑÐ°ÐœÑÑ
+ Ð¿ÐŸÐŽÐ¿ÑÐœÐºÑÐŸÐ²:</Text>
+<CodeLine>/fast-cgi-bin/niupepalibrary</CodeLine>
+<CodeLine>(a) its-www1.massey.ac.nz</CodeLine>
+<CodeLine>(b) [ Thu Dec07 23:47:00 NZDT2000]</CodeLine>
+<CodeLine>(c) (a=p, b=0, bcp=, beu=, c=niupepa, cc=, ccp=0, ccs=0, cl=, cm=, cq2=, d=, e=, er=, f=0, fc=1, gc=0, gg=text, gt=0, h=, h2=, hl=1, hp=, il=l, j=, j2=, k=1, ky=, l=en, m=50, n=, n2=, o=20, p=home, pw=, q=, q2=, r=1, s=0, sp=frameset, t=1, ua=, uan=, ug=, uma=listusers, umc=, umnpw1=, umnpw2=, umpw=, umug=, umun=, umus=, un=, us=invalid, v=0, w=w, x=0, z=130.123.128.4-950647871)</CodeLine>
+<CodeLine>(d) âMozilla/4.08 [en] (Win95; I ;Nav)â</CodeLine>
+<Text id="597">ÐÐŸÑÐ»ÐµÐŽÐœÐžÐ¹ CGI Ð°ÑÐ³ÑÐŒÐµÐœÑ "z" ÑÐ²Ð»ÑÐµÑÑÑ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÐŸÐœÐœÑÐŒ ÐºÐŸÐŽÐŸÐŒ ÐžÐ»Ðž "cookie", ÐŸÐ±ÑÐ°Ð·ÐŸÐ²Ð°ÐœÐœÑÐŒ Ð±ÑÐ°ÑÐ·ÐµÑÐŸÐŒ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ: ÐŸÐœ ÑÐŸÑÑÐŸÐžÑ ÐžÐ· IP-Ð°ÐŽÑÐµÑÐ° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ, Ð¿ÐŸÑÐ»Ðµ ÑÐµÐ³ÐŸ ÐžÐŽÐµÑ ÑÐºÐ°Ð·Ð°ÐœÐžÐµ ÑÐŸÐ³ÐŸ Ð²ÑÐµÐŒÐµÐœÐž, ÐºÐŸÐ³ÐŽÐ° ÐŸÐœ Ð²Ð¿ÐµÑÐ²ÑÐµ Ð²ÐŸÑÐµÐ» Ð² Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÑ.</Text>
+<Text id="598">Ð ÐµÐ³ÐžÑÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» usage.txt Ð¿ÐŸÐŒÐµÑÐµÐœ Ð² ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ etc Ð² ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ¹ ÑÑÑÑÐºÑÑÑÐµ Greenstone (ÑÐŒ. Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð Ð°Ð·ÑÐ°Ð±ÐŸÑÑÐžÐºÐ°). ÐÐŸÐ³ÐŽÐ° Ð²ÐºÐ»ÑÑÐµÐœÐ° ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÑ, ÐºÐ°Ð¶ÐŽÐŸÐµ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ Ð²ÑÐµÑ
+ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Ð·Ð°Ð¿ÐžÑÑÐ²Ð°ÐµÑÑÑ, ÐœÐŸ Ð² ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐŒ ÑÐ°Ð¹Ð»Ðµ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÑ Ð»ÐžÑÑ Ð¿ÐŸÑÐ»ÐµÐŽÐœÐžÐµ 100 ÑÐµÐ³ÐžÑÑÑÐ°ÑÐžÐž Ð¿ÑÐž Ð¿ÐŸÐŒÐŸÑÐž ÑÐŸÐµÐŽÐžÐœÐµÐœÐžÑ usage link ÐœÐ° Ð ÐžÑÑÐœÐºÐµ 17.</Text>
+</Content>
+</Section>
+<Section id="user_management">
+<Title>
+<Text id="599">ÐÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹</Text>
+</Title>
+<Content>
+<Text id="600">Greenstone ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÑÑ
+ÐµÐŒÑ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÐž, ÐºÐŸÑÐŸÑÑÑ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŽÐ»Ñ ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÐžÑ Ðž ÐºÐŸÐœÑÑÐŸÐ»Ñ ÐŽÐŸÑÑÑÐ¿Ð°ÐŒ Ðº ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐŒ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑÐŒ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ. ÐÐ° ÐŽÐ°ÐœÐœÑÐ¹ ÐŒÐŸÐŒÐµÐœÑ ÐŸÐœ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ»Ñ ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœÐžÑ ÐŽÐŸÑÑÑÐ¿Ð° Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Ðº ÐÐŸÐ»Ð»ÐµÐºÑÐŸÑÑ Ðž ÐœÐµÐºÐŸÑÐŸÑÑÐŒ ÑÑÐœÐºÑÐžÑÐŒ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ. ÐÑÐ»Ðž ÐœÐµÐŸÐ±Ñ
+ÐŸÐŽÐžÐŒÐŸ ÐžÐŽÐµÐœÑÐžÑÐžÑÐžÑÐŸÐ²Ð°ÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð¿ÐµÑÐµÐŽ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÐµÐŒ ÐµÐŒÑ ÐŽÐŸÑÑÑÐ¿Ð° Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒ, ÑÐŸ ÑÑÐŸ ÑÐ°ÐºÐ¶Ðµ ÐŸÑÑÑÐµÑÑÐ²ÐžÐŒÐŸ. Ð Ð¿ÑÐžÐŒÐµÑÑ, ÐŽÐŸÑÑÑÐ¿ Ðº ÐœÐµÐºÐŸÑÐŸÑÑÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐŸÑÑÑÐµÑÑÐ²Ð»ÐµÐœ ÑÐŸÐ»ÑÐºÐŸ Ð·Ð°ÑÐµÐ³ÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐŒÐž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒÐž Ð¿ÑÑÐµÐŒ Ð²Ð²ÐŸÐŽÐ° ÐÐ Ðž Ð¿Ð°ÑÐŸÐ»Ñ (Ñ
+ÐŸÑÑ ÑÑÐŸ Ð¿ÐŸÐºÐ° ÐœÐµ Ð¿ÑÐ°ÐºÑÐžÐºÑÐµÑÑÑ). Ð­ÑÐŸ Ð¿ÐŸÐºÐ°Ð·Ð°ÐœÐŸ ÐœÐ° Ð ÐžÑÑÐœÐºÐµ 16Ð°.</Text>
+<Text id="601">ÐÐ° ÑÑÑÐ°ÐœÐžÑÐµ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÑÐŸÑÐŒÐŸÑÑÐµÑÑ ÑÐ¿ÐžÑÐŸÐº Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹, ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ ÐœÐŸÐ²ÑÑ
+ Ðž ÑÐŽÐ°Ð»ÐžÑÑ ÑÑÐ°ÑÑÑ
+. ÐÐŸÑÑÑÐ¿ Ðº ÑÑÐŸÐ¹ ÑÑÐœÐºÑÐžÐž ÐºÐŸÐœÐµÑÐœÐŸ Ð¶Ðµ ÐŸÐ³ÑÐ°ÐœÐžÑÐµÐœ: ÑÐŸÐ»ÑÐºÐŸ ÑÐ¿ÐŸÐ»ÐœÐŸÐŒÐŸÑÐµÐœÐœÑÐŒ Ð»ÐžÑÐ°ÐŒ ÑÐ°Ð·ÑÐµÑÐµÐœÐ° ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ ÐœÐŸÐ²ÑÑ
+ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹. ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ðž ÐŒÐŸÐ³ÑÑ Ð¿ÑÐžÐœÐ°ÐŽÐ»ÐµÐ¶Ð°ÑÑ Ðº ÐœÐµÑÐºÐŸÐ»ÑÐºÐžÐŒ Ð³ÑÑÐ¿Ð¿Ð°ÐŒ. ÐÐ° ÐŽÐ°ÐœÐœÑÐ¹ ÐŒÐŸÐŒÐµÐœÑ ÑÑÑÐµÑÑÐ²ÑÐµÑ ÑÐŸÐ»ÑÐºÐŸ ÐŽÐ²Ðµ Ð³ÑÑÐ¿Ð¿Ñ "Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐ°ÑÐŸÑÑ" Ðž "colbuilder". Ð§Ð»ÐµÐœÑ Ð¿ÐµÑÐ²ÐŸÐ¹ Ð³ÑÑÐ¿Ð¿Ñ ÐŒÐŸÐ³ÑÑ ÐŽÐŸÐ±Ð°Ð²Ð»ÑÑÑ Ðž ÑÐŽÐ°Ð»ÑÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÐµÐ¹ Ðž ÐžÐ·ÐŒÐµÐœÑÑÑ ÐžÑ
+ Ð³ÑÑÐ¿Ð¿Ñ. Ð§Ð»ÐµÐœÑ Ð²ÑÐŸÑÐŸÐ¹ Ð³ÑÑÐ¿Ð¿Ñ ÐžÐŒÐµÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº Ð²ÑÑÐµÐŸÐ¿ÐžÑÐ°ÐœÐœÑÐŒ ÑÑÐµÐŽÑÑÐ²Ð°ÐŒ ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐœÐŸÐ²ÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ðž ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ (ÑÐŽÐ°Ð»ÐµÐœÐžÑ) ÑÑÑÐµÑÑÐ²ÑÑÑÐžÑ
+.</Text>
+<Text id="602">ÐÐŸÑÐ»Ðµ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð¿ÐŸÑÐ²Ð»ÑÐµÑÑÑ ÐŸÐŽÐžÐœ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ admin, ÐºÐŸÑÐŸÑÑÐ¹ Ð¿ÑÐžÐœÐ°ÐŽÐ»ÐµÐ¶ÐžÑ ÐŸÐ±ÐµÐžÐŒ Ð³ÑÑÐ¿Ð¿Ð°ÐŒ. ÐÐ°ÑÐŸÐ»Ñ ÑÑÐŸÐ³ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Ð²Ð²ÐŸÐŽÐžÑÑÑ ÐµÑÐµ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž. Ð­ÑÐŸÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŒÐŸÐ¶ÐµÑ ÑÐŸÐ·ÐŽÐ°Ð²Ð°ÑÑ ÐžÐŒÐµÐœÐ° Ðž Ð¿Ð°ÑÐŸÐ»Ðž ÐŽÐ»Ñ Ð»ÑÐŽÐµÐ¹,Ð¿ÑÐžÐœÐ°ÐŽÐ»ÐµÐ¶Ð°ÑÐžÑ
+ Ðº Ð³ÑÑÐ¿Ð¿Ðµ colbuilder. ÐÐŒÐµÐœÐœÐŸ ÑÐ°ÐºÐŸÐ¹ ÐŒÐµÑÐŸÐŽ ÑÐµÐºÐŸÐŒÐµÐœÐŽÑÐµÑÑÑ ÐŽÐ»Ñ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÐŽÐŸÑÑÑÐ¿Ð° ÐŽÑÑÐ³ÐžÐŒ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹. ÐÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ðµ Ð·Ð°Ð¿ÐžÑÑÐ²Ð°ÐµÑÑÑ Ð² ÐŽÐ²Ðµ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+, ÐºÐŸÑÐŸÑÑÐµ ÐœÐ°Ñ
+ÐŸÐŽÑÑÑÑ Ð² ÑÐ°Ð¹Ð»ÐŸÐ²ÐŸÐ¹ ÑÑÑÑÐºÑÑÑÐµ Greenstone (ÑÐŒ. Ð ÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Ð Ð°Ð·ÑÐŸÐ±ÐŸÑÑÐžÐºÐ°).</Text>
+</Content>
+</Section>
+<Section id="technical_information">
+<Title>
+<Text id="603">Ð¢ÐµÑ
+ÐœÐžÑÐµÑÐºÐ°Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ</Text>
+</Title>
+<Content>
+<Text id="604">Ð¡ÑÑÐ»ÐºÐž Ð¿ÐŸÐŽ Ð·Ð°Ð³ÐŸÐ»ÐŸÐ²ÐºÐŸÐŒ <i>Technical information</i> Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÑÑ ÐŽÐ°Ð»ÑÐœÐµÐ¹ÑÑÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ Ð¿ÑÐŸÑÐµÑÑÐµ ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž. Ð¡ÑÑÐ»ÐºÐ° <i>general</i> ÐŽÐ°ÐµÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÑÐµÑ
+ÐœÐžÑÐµÑÐºÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž, Ð²ÐºÐ»ÑÑÐ°Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž, Ð² ÐºÐŸÑÐŸÑÑÑ
+ Ð²ÑÐµ ÑÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐŸ. ÐÐµÐœÑ <i>protocol</i>, ÐŽÐ»Ñ Ð»ÑÐ±ÐŸÐ³ÐŸ Ð²ÐžÐŽÐ° Ð¿ÑÐŸÑÐŸÐºÐŸÐ»Ð°, ÐŽÐ°ÐµÑ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ ÐŸ ÐºÐ°Ð¶ÐŽÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÐŒÐŸÐ¹ ÑÑÐžÐŒ Ð¿ÑÐŸÑÐŸÐºÐŸÐ»ÐŸÐŒ.</Text>
+<Text id="605">Ð ÐœÐ°ÐºÐŸÐœÐµÑ, Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐžÐ¹ ÐºÐŸÐŽ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ° (user interface code), ÐœÐ°Ð·ÑÐ²Ð°ÐµÐŒÑÐ¹ "receptionist", ("ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ" ) ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐŽÐµÐ¹ÑÑÐ²ÐžÑ ÐŽÐ»Ñ Ð¿ÐµÑÐµÐŽÐ°ÑÐž ÐœÐ°ÐŒÐµÑÐµÐœÐžÐ¹ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ. Ð­ÑÐž ÐŽÐµÐ¹ÑÑÐ²ÐžÑ ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑ Ð°ÑÐ³ÑÐŒÐµÐœÑÑ CGI, ÐœÐ°Ð·Ð²Ð°ÐœÐœÑÐŒ Ð°. ÐÐ°Ð¿ÑÐžÐŒÐµÑ, ÐµÑÐ»Ðž a=status, ÑÐŸ ÑÐµÐ³ÐžÑÑÑÐ°ÑÐŸÑ Ð°ÐºÑÐžÐ²ÐžÐ·ÐžÑÑÐµÑ ÐŽÐµÐ¹ÑÑÐ²ÐžÐµ status, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐŸÐºÐ°Ð·ÑÐ²Ð°ÐµÑ ÑÑÐ°ÑÑÑÐœÑÑ ÑÑÑÐ°ÐœÐžÑÑ. Ð­Ð»ÐµÐŒÐµÐœÑ ÐŒÐµÐœÑ ÐŽÐ°ÐµÑ ÐŽÐŸÑÑÑÐ¿ Ðº Ð¿ÐµÑÐµÑÐœÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐµÐ¹, Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÐŒÑÑ
+ ÑÐžÑÑÐµÐŒÐŸÐ¹, Ð° ÐŽÑÑÐ³ÐŸÐ¹ Ð²ÐµÐŽÐµÑ Ðº Ð°ÑÐ³ÑÐŒÐµÐœÑÐ°ÐŒ, Ðº ÐºÐŸÑÐŸÑÑÐŒ Ð¿ÑÐžÐ±ÐµÐ³Ð°ÑÑ ÑÑÐž ÐŽÐµÐ¹ÑÑÐ²ÐžÑ.</Text>
+</Content>
+</Section>
+</Content>
+</Chapter>
+<Chapter id="appendix_a_software_features">
+<Title>
+<Text id="606">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ Ð ÐÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ</Text>
+</Title>
+<Content>
+<Table class="hidden" id="table_appendixa">
+<Title/>
+<TableContent>
+<tr>
+<th width="132">
+<Text id="607">ÐŽÐŸÑÑÑÐ¿ÐœÑÐ¹ ÑÐµÑÐµÐ· Ð²ÐµÐ± Ð±ÑÐ°ÑÐ·ÐµÑ</Text>
+</th>
+<th width="397">
+<Text id="608">ÐÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŸÑÐºÑÑÐ²Ð°ÑÑÑÑ Ð² ÐŸÐºÐœÐµ ÑÑÐ°ÐœÐŽÐ°ÑÑÐœÐŸÐ³ÐŸ Ð²ÐµÐ±-Ð±ÑÐ°ÑÐ·ÐµÑÐ° (Netscape ÐžÐ»Ðž Internet Explorer) Ðž ÑÐŸÐ²ÐŒÐµÑÐ°ÑÑ Ð»ÐµÐ³ÐºÐŸÑÑÑ Ð² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž Ñ ÐŒÐœÐŸÐ³ÐŸÑÑÐŸÑÐŸÐœÐœÐžÐŒÐž Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÐŒÐž Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑÐŒÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="609">ÐÐŸÐ»ÐœÐŸ-ÑÐµÐºÑÑÐŸÐ²ÐŸÐ¹ Ðž ÑÐ°Ð·ÐŽÐµÐ»ÑÐœÑÐ¹ Ð¿ÐŸÐžÑÐºÐž</Text>
+</th>
+<th width="397">
+<Text id="610">ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŒÐŸÐ¶ÐµÑ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÑÑ Ð¿ÐŸÐžÑÐº Ð¿ÐŸ Ð²ÑÐµÐŒÑ ÑÐµÐºÑÑÑ ÐžÐ»Ðž Ð¿ÐŸ ÐžÐœÐŽÐµÐºÑÐ°ÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÑÐ°Ð·ÐŽÐµÐ»ÐŸÐ², ÐžÐœÐŽÐµÐºÑÐ°ÐŒ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹, Ð°Ð²ÑÐŸÑÐŸÐ², Ð² ÐºÐ°Ð¶ÐŽÐŸÐŒ ÐžÐ· ÐºÐŸÑÐŸÑÑÑ
+ ÐŒÐŸÐ¶ÐœÐŸ ÐžÑÐºÐ°ÑÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐµ ÑÐ»ÐŸÐ²Ð° ÐžÐ»Ðž ÑÑÐ°Ð·Ñ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="611">Ð³ÐžÐ±ÐºÐžÐµ ÑÑÐµÐŽÑÑÐ²Ð° Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°</Text>
+</th>
+<th width="397">
+<Text id="612">ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ ÐŒÐŸÐ¶ÐµÑ Ð¿ÑÐŸÑÐŒÐ°ÑÑÐžÐ²Ð°ÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÐŸ ÑÐ°ÐºÐžÐŒ ÐžÐœÐŽÐµÐºÑÐ°ÐŒ, ÐºÐ°Ðº Ð°Ð²ÑÐŸÑ, ÑÐºÐ°Ð·Ð°ÑÐµÐ»Ðž, ÐŽÐ°ÑÐ° Ðž Ñ.ÐŽ. ÐÐ°Ð¶ÐŽÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð¿ÑÐµÐŽÐ»Ð°Ð³Ð°ÐµÑ ÑÐ²ÐŸÐž ÑÑÑÑÐŸÐ¹ÑÑÐ²Ð° ÐŽÐ»Ñ ÐŸÑÑÑÐµÑÑÐ²Ð»ÐµÐœÐžÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ðž ÐŽÐ°Ð¶Ðµ Ð²ÐœÑÑÑÐž ÑÐ°ÐŒÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÑÑÐµÑÑÐ²ÑÐµÑ Ð±ÐŸÐ»ÑÑÐŸÐµ ÐºÐŸÐ»ÐžÑÐµÑÑÐ²ÐŸ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐŸÐ² ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°. ÐÐœÑÐµÑÑÐµÐ¹ÑÑ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ðž Ð¿ÐŸÐžÑÐºÐ° ÑÐŸÐ·ÐŽÐ°ÑÑÑÑ Ð²ÐŸ Ð²ÑÐµÐŒÑ Ð¿ÑÐŸÑÐµÑÑÐ° Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ Ð² ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÐžÐž Ñ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="613">Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÑÐµÐºÐž ÑÐŸÐ·ÐŽÐ°ÐµÑ ÑÑÑÑÐºÑÑÑÑ ÐŽÐŸÑÑÑÐ¿Ð°</Text>
+</th>
+<th width="397">
+<Text id="614">ÐÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, ÑÐŸÐ·ÐŽÐ°ÐœÐœÑÐµ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ Greenstone, Ð»ÐµÐ³ÐºÐž Ð² ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž. ÐÑÐµ Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÐµ ÑÑÑÑÐºÑÑÑÑ Ðž ÑÑÑÑÐºÑÑÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÑÐŸÐ·ÐŽÐ°ÑÑÑÑ Ð¿ÑÑÐŒÐŸ ÐžÐ· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÑÐ»Ðž Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ ÐœÐŸÐ²ÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÑ
+ÐŸÐ¶ÐµÐ³ÐŸ ÑÐŸÑÐŒÐ°ÑÐ°, ÑÐŸ ÐŸÐœÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð¿ÑÐžÑÐŸÐµÐŽÐžÐœÐµÐœÑ Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐ°Ðº Ðž ÐŽÐµÐ»Ð°ÑÑ. Ð§ÐµÑÐµÐ· ÐºÐ°ÐºÐŸÐ¹-ÑÐŸ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÐ¹ Ð¿ÑÐŸÐŒÐµÐ¶ÑÑÐŸÐº Ð²ÑÐµÐŒÐµÐœÐž ÐŸÐœÐž ÐœÐ°ÑÐžÐœÐ°ÑÑ Ð¿ÐŸÐžÑÐº ÐœÐŸÐ²ÐŸÐ³ÐŸ ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ð° Ðž Ð¿ÐµÑÐµÑÑÑÐ°ÐžÐ²Ð°ÑÑ ÐžÐœÐŽÐµÐºÑÑ â Ð²ÑÐµ Ð±ÐµÐ· ÑÑÑÐœÐŸÐ³ÐŸ Ð²ÐŒÐµÑÐ°ÑÐµÐ»ÑÑÑÐ²Ð°.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="615">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ ÐŽÐŸÑÑÑÐ¿ÐœÑÐµ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ</Text>
+</th>
+<th width="397">
+<Text id="616">ÐÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ - ÑÑÐŸ ÑÐ°ÐºÐ°Ñ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ, ÐºÐ°Ðº Ð°Ð²ÑÐŸÑ, ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÐŽÐ°ÑÐ°, ÐºÐ»ÑÑÐµÐ²ÑÐµ ÑÐ»ÐŸÐ²Ð° Ðž Ñ.ÐŽ.. ÐÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÑÐ»ÑÐ¶Ð°Ñ ÐŸÑÐœÐŸÐ²ÐŸÐ¹ ÐŽÐ»Ñ ÐžÐœÐŽÐµÐºÑÐŸÐ² Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°. ÐÐœÐž ÐŽÐŸÐ»Ð¶ÐœÑ Ð±ÑÑÑ ÑÐºÐ°Ð·Ð°ÐœÑ Ð»ÐžÐ±ÐŸ Ð¿ÐŸÐ»ÑÑÐµÐœÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐžÐ· ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². Ð¡Ñ
+ÐµÐŒÐ° Dublin Core metadata ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²Ð° ÑÐ»ÐµÐºÑÑÐŸÐœÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ñ
+ÐŸÑÑ ÐŒÐŸÐ¶ÐœÐŸ Ð¿ÑÐžÐŒÐµÐœÑÑÑ Ðž ÐŽÑÑÐ³ÐžÐµ ÑÑ
+ÐµÐŒÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="617">ÐÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ Ðº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ ÑÐ°ÑÑÐžÑÑÑÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž ÑÐžÑÑÐµÐŒÑ</Text>
+</th>
+<th width="397">
+<Text id="618">ÐÐ»Ñ ÑÐŸÐ³ÐŸ, ÑÑÐŸÐ±Ñ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÑÐŸ Ð²ÑÐµÐ²ÐŸÐ·ÐŒÐŸÐ¶ÐœÑÐŒÐž Ð²ÐžÐŽÐ°ÐŒÐž ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÑÐ°ÑÑÐžÑÐžÑÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž Ð¿ÑÑÐµÐŒ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÐ¹ ÐŽÐ»Ñ ÐœÐŸÐ²ÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ² ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐµ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ ÐœÐ° ÐŽÐ°ÐœÐœÑÐ¹ ÐŒÐŸÐŒÐµÐœÑ ÑÑÑÐµÑÑÐ²ÑÑÑ ÐŽÐ»Ñ ÑÐ»ÐµÐŽÑÑÑÐžÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ²: ÑÐµÐºÑÑÐŸÐ²ÑÑ
+, HTML, Word, PDF, PostScript, E-mail. ÐÐŸÐ»Ð»ÐµÐºÑÐžÑ ÐŒÐŸÐ¶ÐµÑ ÐžÐŒÐµÑÑ ÐžÑÑ
+ÐŸÐŽÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐ°Ð·ÐœÑÑ
+ ÑÐŸÑÐŒÐ°ÑÐŸÐ². ÐÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐžÐœÐŽÐµÐºÑÐŸÐ² Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÐžÐ· ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÑÑ
+ÐµÐŒÐ° "Ñ1Ð°Ð·Ð·Ð1ÐµÐ³8"(ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ): ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÑÐŸÐ·ÐŽÐ°ÑÑ ÐžÐœÐŽÐµÐºÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° ÑÐ°Ð·ÐœÑÑ
+ Ð²ÐžÐŽÐŸÐ², ÐŸÑÐœÐŸÐ²Ð°ÐœÐœÑÑ
+ ÐœÐ° ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="619">Ð¡Ð¿ÑÐŸÐµÐºÑÐžÑÐŸÐ²Ð°Ðœ ÐŽÐ»Ñ ÐŒÑÐ»ÑÑÐžÐ³ÐžÐ³Ð°Ð±Ð°Ð¹ÑÐœÑÑ
+ (ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹)</Text>
+</th>
+<th width="397">
+<Text id="620">ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÐŒÐžÐ»Ð»ÐžÐŸÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÐžÑÑÐµÐŒÑ Greenstone ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž ÑÐ°Ð·ÐŒÐµÑÐŸÐŒ Ð² ÐœÐµÑÐºÐŸÐ»ÑÐºÐŸ Ð³ÐžÐ³Ð°Ð±Ð°Ð¹Ñ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="621">ÐÐŸÐºÑÐŒÐµÐœÑÑ ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐœÐ° Ð»ÑÐ±ÐŸÐŒ ÑÐ·ÑÐºÐµ</Text>
+</th>
+<th width="397">
+<Text id="622">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Unicode, Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑ ÐžÑÐ¿ÑÐ°Ð²ÐœÐŸ ÑÐ°Ð±ÐŸÑÐ°ÑÑ ÐœÐ° Ð»ÑÐ±ÐŸÐŒ ÑÐ·ÑÐºÐµ. ÐÐ° ÑÑÐŸÑ ÐŒÐŸÐŒÐµÐœÑ ÑÐŸÐ·ÐŽÐ°ÐœÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐœÐ° Ð°ÑÐ°Ð±ÑÐºÐŸÐŒ, ÑÑÐ°ÐœÑÑÐ·ÐºÐŸÐŒ, ÐºÐžÑÐ°Ð¹ÑÐºÐŸÐŒ, Ð³ÐŸÐ»Ð»Ð°ÐœÐŽÑÐºÐŸÐŒ, Ð°ÐœÐ³Ð»ÐžÐ¹ÑÐºÐŸÐŒ, ÐžÑÐ¿Ð°ÐœÑÐºÐŸÐŒ, ÐŒÐ°Ð¹ÐŸÑÑÐºÐŸÐŒ ÑÐ·ÑÐºÐ°Ñ
+. ÐÐµÑÐµÐ²ÐŸÐŽ ÐœÐ° Ð»ÐµÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ ÐŽÐ»Ñ Ð¿ÐµÑÐµÐ²ÐŸÐŽÐ° Unicode Ð² Ð°Ð»ÑÐ°Ð²ÐžÑÐœÑÑ ÑÐŸÑÐŒÑ, Ð¿ÐŸÐŽÐŽÐµÑÐ¶ÐžÐ²Ð°ÐµÐŒÑÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐžÐŒ Ð±ÑÐ°ÑÐ·ÐµÑÐŸÐŒ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="623">ÐÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐžÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ ÐŽÐŸÑÑÑÐ¿ÐµÐœ ÐœÐ° ÑÐ°Ð·ÐœÑÑ
+ ÑÐ·ÑÐºÐ°Ñ
+</Text>
+</th>
+<th width="397">
+<Text id="624">ÐÐœÑÐµÑÑÐµÐ¹Ñ ÐŽÐŸÑÑÑÐ¿ÐµÐœ ÐœÐ° ÑÐ°Ð·ÐœÑÑ
+ ÑÐ·ÑÐºÐ°Ñ
+. ÐÐ° ÐŽÐ°ÐœÐœÑÐ¹ ÐŒÐŸÐŒÐµÐœÑ ÐžÐœÑÐµÑÑÐµÐ¹Ñ ÐŽÐŸÑÑÑÐ¿ÐµÐœ ÐœÐ° ÑÐ»ÐµÐŽÑÑÑÐžÑ
+ ÑÐ·ÑÐºÐ°Ñ
+: Ð°ÑÐ°Ð±ÑÐºÐŸÐŒ, ÑÑÐ°ÐœÑÑÐ·ÐºÐŸÐŒ, ÐºÐžÑÐ°Ð¹ÑÐºÐŸÐŒ, Ð³ÐŸÐ»Ð»Ð°ÐœÐŽÑÐºÐŸÐŒ, Ð°ÐœÐ³Ð»ÐžÐ¹ÑÐºÐŸÐŒ, ÐžÑÐ¿Ð°ÐœÑÐºÐŸÐŒ, ÐŒÐ°Ð¹ÐŸÑÑÐºÐŸÐŒ, Ð¿ÐŸÑÑÑÐ³Ð°Ð»ÑÑÐºÐŸÐŒ. ÐÐŸÐ²ÑÐµ ÑÐ·ÑÐºÐž ÐŒÐŸÐ¶ÐœÐŸ Ð»ÐµÐ³ÐºÐŸ ÐŽÐŸÐ±Ð°Ð²ÐžÑÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="625">ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÑÐµÐºÑÑ, ÑÐžÑÑÐœÐºÐž, Ð°ÑÐŽÐžÐŸ Ðž Ð²ÐžÐŽÐµÐŸ</Text>
+</th>
+<th width="397">
+<Text id="626">ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÑÐµÐºÑÑ, ÑÐžÑÑÐœÐºÐž, Ð°ÑÐŽÐžÐŸ Ðž Ð²ÐžÐŽÐµÐŸ ÐºÐ»ÐžÐ¿Ñ. ÐÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ ÐœÐµÑÐµÐºÑÑÐŸÐ²ÐŸÐ³ÐŸ ÐŒÐ°ÑÐµÑÐžÐ°Ð»Ð° Ð»ÐžÐ±ÐŸ ÑÐŸÐµÐŽÐžÐœÐµÐœÐŸ Ñ ÑÐµÐºÑÑÐŸÐ²ÑÐŒ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐŒ ÑÑÑÐ»ÐºÐŸÐ¹, Ð»ÐžÐ±ÐŸ ÐœÐ° ÐžÑ
+ ÐŒÐµÑÑÐµ ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ ÑÐµÐºÑÑÐŸÐ²ÐŸÐµ ÐŸÐ¿ÐžÑÐ°ÐœÐžÐµ ÐžÐ»Ðž ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ ÑÐžÑÑÐœÐºÐ° ÐŽÐ»Ñ ÐŸÐ±Ð»ÐµÐ³ÑÐµÐœÐžÑ Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÐŸÐžÑÐºÐ° Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°. ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÑÐžÐŒÐµÐœÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐµ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ Ðž ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÐŽÐ°Ð¶Ðµ ÐŽÐ»Ñ ÐœÐµÑÐµÐºÑÑÐŸÐ²ÑÑ
+ ÐŽÐ°ÐœÐœÑÑ
+.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="627">ÐÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑ Ð¿ÑÐŸÐŽÐ²ÐžÐœÑÑÑÐµ ÑÐµÑ
+ÐœÐŸÐ»ÐŸÐ³ÐžÐž ÑÐ¶Ð°ÑÐžÑ</Text>
+</th>
+<th width="397">
+<Text id="628">Ð¢ÐµÑ
+ÐœÐŸÐ»ÐŸÐ³ÐžÐž ÑÐ¶Ð°ÑÐžÑ Ð¿ÑÐžÐŒÐµÐœÑÑÑÑÑ ÐŽÐ»Ñ ÑÐŒÐµÐœÑÑÐµÐœÐžÑ ÑÐ°ÐŒÐµÑÐŸÐ² ÐžÐœÐŽÐµÐºÑÐŸÐ² Ðž ÑÐµÐºÑÑÐ°. Ð£ÐŒÐµÐœÑÑÐµÐœÐžÐµ ÑÐ°Ð·ÐŒÐµÑÐŸÐ² ÑÐµÐºÑÑÐ° Ðº ÑÐŸÐŒÑ Ð¶Ðµ ÑÐ²ÐµÐ»ÐžÑÐžÐ²Ð°ÐµÑ ÑÐºÐŸÑÐŸÑÑÑ ÐŸÐ±ÐœÐ°ÑÑÐ¶ÐµÐœÐžÑ Ðž ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÑ ÑÐµÐºÑÑÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="629">ÐÐŸÑÑÑÐ¿ÐœÐ° ÑÑÐœÐºÑÐžÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ</Text>
+</th>
+<th width="397">
+<Text id="630">Ð€ÑÐœÐºÑÐžÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐœÐ°ÐŽÐµÐ»ÑÐµÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐœÑÑ
+ Ð»ÐžÑ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑÑ ÑÐ°Ð·ÑÐµÑÐ°ÑÑ ÐœÐŸÐ²ÑÐŒ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ ÑÑÑÐŸÐžÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž, Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÑÑÑ ÐœÐµÐºÐŸÑÐŸÑÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ ÑÐŸÐ»ÑÐºÐŸ Ð·Ð°ÑÐµÐ³ÐžÑÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÐŒ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ, Ð¿ÑÐŸÐ²ÐµÑÑÑÑ ÑÐŸÑÑÐ°Ð² Ð²ÑÐµÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ðž Ñ.ÐŽ.  Ð ÐµÐ³ÐžÑÑÑÐ°ÑÐžÐŸÐœÐœÑÐµ ÑÐ°Ð¹Ð»Ñ (logs) ÐŒÐŸÐ³ÑÑ Ð·Ð°Ð¿ÐžÑÑÐ²Ð°ÑÑ Ð²ÑÐµ Ð·Ð°Ð¿ÑÐŸÑÑ, ÑÐŽÐµÐ»Ð°ÐœÐœÑÐµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="631">ÐÑÑÑÑÐŸÐµ Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÐµ ÐœÐŸÐ²ÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</th>
+<th width="397">
+<Text id="632">ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÑ Ðž ÑÐŸÐ·ÐŽÐ°ÐœÑ Ð² Ð»ÑÐ±ÐŸÐµ Ð²ÑÐµÐŒÑ Ð±ÐµÐ· Ð¿ÐµÑÐµÐ³ÑÑÐ·ÐºÐž ÑÐžÑÑÐµÐŒÑ. ÐÑÐž Ð¿ÐŸÑÐ²Ð»ÐµÐœÐžÐž ÐœÐŸÐ²ÑÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐŸÐœÐž Ð¿ÐŸÑÐ²Ð»ÑÑÑÑÑ Ð² ÐžÐœÑÐµÑÑÐµÐ¹ÑÐµ Ð³Ð»Ð°Ð²ÐœÐŸÐ³ÐŸ ÐŒÐµÐœÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="633"><i>Collections can be published on the Internet or on CD-ROM</i></Text>
+</th>
+<th width="397">
+<Text id="634">The software can be used to serve collections over the World-Wide Web. Greenstone collections can be made available, in precisely the same form, on CD-ROM. The user interface is through a standard web browser (Netscape is provided on each disk), and the interaction is identical to accessing the collection on the webâexcept that response times are more predictable. The CD-ROMs run under all versions of the Windows operating system.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="635">ÐÐŸÐ»Ð»ÐµÐºÑÐžÐž ÐŒÐŸÐ³ÑÑ Ð±ÑÑÑ ÑÐ°ÑÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÑ ÑÑÐµÐŽÐž ÑÐ°Ð·ÐœÑÑ
+ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐŸÐ²</Text>
+</th>
+<th width="397">
+<Text id="636">ÐÐžÐ±ÐºÐ°Ñ ÑÑÑÑÐºÑÑÑÐ° Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ ÑÐ°Ð·ÐœÑÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐ°ÐŒ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ ÑÐ°Ð·ÐœÑÐŒÐž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒÐž, Ð² ÑÐŸ Ð¶Ðµ ÑÐ°ÐŒÐŸÐµ Ð²ÑÐµÐŒÑ Ð²ÑÑ
+ÐŸÐŽÑ ÐœÐ° ÑÐºÑÐ°Ðœ Ð² ÐŸÐŽÐœÐŸÐŒ ÑÐžÐ¿Ðµ, ÐœÐ° ÐŸÐŽÐœÐŸÐ¹ Ð²ÑÐ±-ÑÑÑÐ°ÐœÐžÑÐµ, ÐºÐ°Ðº ÑÐ°ÑÑÑ ÐŸÐŽÐœÐŸÐ¹ Ðž ÑÐŸÐ¹ Ð¶Ðµ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="637">Ð Ð°Ð±ÐŸÑÐ°ÐµÑ ÐºÐ°Ðº Ð² Unix, ÑÐ°Ðº Ðž Ð² Windows</Text>
+</th>
+<th width="397">
+<Text id="638">Greenstone ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ðž Ð² Windows (3.1/3.11,95/98/ME,NT/2000) Ðž Unix (Linux Ðž SunOS). ÐÑÐ±Ð°Ñ ÐžÐ· ÑÑÐžÑ
+ ÑÐžÑÑÐµÐŒ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐ° Ð² ÐºÐ°ÑÐµÑÑÐ²Ðµ Ð²ÐµÐ±-ÑÐµÑÐ²ÐµÑÐ°. Ð¡ÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ ÐœÐµÐ²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ ÐœÐ° ÑÑÑÐ°ÑÐµÐ²ÑÐžÑ
+ ÑÐžÑÑÐµÐŒÐ°Ñ
+ Windows 3.1/3.11, ÐœÐŸ ÐŸÐœÐž ÐŒÐŸÐ³ÑÑ ÑÑÐžÑÑÐ²Ð°ÑÑ Ð³ÐŸÑÐŸÐ²ÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="132">
+<Text id="639">Ð§ÑÐŸ Ð²Ñ Ð¿ÐŸÐ»ÑÑÐ°ÐµÑÐµ Ñ Greenstone</Text>
+</th>
+<th width="397">
+<Text id="640">Greenstone Digital Library ÑÐ²Ð»ÑÐµÑÑÑ ÐŸÐ±ÑÐµÐŽÐŸÑÑÑÐ¿ÐœÑÐŒ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐŒ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµÐŒ, ÐŽÐŸÑÑÑÐ¿ÐœÑÐŒ ÐœÐ° Ð²ÐµÐ±-ÑÐ°Ð¹ÑÐµ New Zealand Digital Library (nzdl.org), ÑÐŸÐŸÑÐ²ÐµÑÑÑÐ²ÑÑÑÐžÐŒ GNU General Public License. ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð² ÑÐµÐ±Ñ Ð²ÑÐµ, ÑÑÐŸ Ð±ÑÐ»ÐŸ ÐŸÐ¿ÐžÑÐ°ÐœÐŸ Ð²ÑÑÐµ: Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ CD, ÑÐŸÐ·ÐŽÐ°ÐœÐžÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐŒÐœÐŸÐ³ÐŸÑÐ·ÑÐºÐŸÐ²ÑÐµ Ð²ÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸÑÑÐž, ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÑ Ðº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐµ Ðž ÐºÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑÑ ÐŽÐ»Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐžÑÑ
+ÐŸÐŽÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ². ÐÑÐž ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐºÐ°Ðº Ð² Windows, ÑÐ°Ðº Ðž Ð² Unix. Ð¢Ð°Ðº ÐºÐ°Ðº ÑÑÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÐŸÐ±ÑÐµÐŽÐŸÑÑÑÐ¿ÐœÐ°, ÐŒÑ Ð±ÑÐ»Ðž Ð±Ñ ÑÐ°ÐŽÑ Ð²Ð°ÑÐžÐŒ Ð¿ÑÐµÐŽÐ»ÐŸÐ¶ÐµÐœÐžÑÐŒ Ð¿ÐŸ ÐµÑ ÐžÐ·ÐŒÐµÐœÐµÐœÐžÑ Ðž ÑÐ»ÑÑÑÐµÐœÐžÑ.</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<Chapter id="appendix_b_glossary_of_terms">
+<Title>
+<Text id="641">ÐÑÐžÐ»ÐŸÐ¶ÐµÐœÐžÐµ Ð ÐÐ»ÐŸÑÑÐ°ÑÐžÐ¹ Ð¿ÐŸÐœÑÑÐžÐ¹</Text>
+</Title>
+<Content>
+<Table id="table_appendixa" class="hidden">
+<Title/>
+<TableContent>
+<tr>
+<th width="123">
+<Text id="642"><b>ÐÐŸÐœÑÐžÐµ</b></Text>
+</th>
+<th width="406">
+<Text id="643"><b>ÐÐœÐ°ÑÐµÐœÐžÐµ</b></Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="644"><i>autoconf</i></Text>
+</th>
+<th width="406">
+<Text id="645">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð² Unix, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ ÐŽÐ»Ñ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž ÐžÐœÑÑÐ°Ð»Ð»ÑÑÐžÐŸÐœÐœÐŸÐ³ÐŸ Ð¿Ð°ÐºÐµÑÐ° Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Greenstone ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ ÐœÐ° Ð²Ð°ÑÐµÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="646"><i>Autorun</i> ÐÐ²ÑÐŸÐ·Ð°Ð³ÑÑÐ·ÐºÐ°</Text>
+</th>
+<th width="406">
+<Text id="647">Ð­ÑÐŸ ÐŸÐŽÐœÐŸ ÐžÐ· ÑÑÐµÐŽÑÑÐ² Windows, ÐºÐŸÑÐŸÑÐŸÐµ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž Ð·Ð°Ð¿ÑÑÐºÐ°ÐµÑ Ð»ÑÐ±ÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ð¿ÐŸÑÐ»Ðµ Ð²ÑÑÐ°Ð²ÐºÐž CD-ROM Ð² ÐŽÐžÑÐºÐŸÐ²ÐŸÐŽ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="648">Boolean query ÐÑÐ»ÐµÐ² Ð·Ð°Ð¿ÑÐŸÑ</Text>
+</th>
+<th width="406">
+<Text id="649">ÐÐ°Ð¿ÑÐŸÑ Ðº ÑÐžÑÑÐµÐŒÐµ Ð¿ÐŸÐžÑÐºÐ° ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž, ÐºÐŸÑÐŸÑÑÐ¹ ÐŒÐŸÐ¶ÐµÑ ÑÐŸÑÑÐŸÑÑÑ ÐžÐ· ÑÐŸÑÐ·ÐŸÐ² Ð, ÐÐÐ Ðž ÑÐ»ÐŸÐ²Ð° ÐÐÐ¢.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="650">Browsing ÐÑÐŸÑÐŒÐŸÑÑ, ÐŸÐ±Ð·ÐŸÑ</Text>
+</th>
+<th width="406">
+<Text id="651">ÐÐŸÑÑÑÐ¿ Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÑÐµÐŒ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ð¿ÐµÑÐµÑÐœÑ ÑÐ°Ð·Ð»ÐžÑÐœÑÑ
+ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ (Ð°Ð²ÑÐŸÑ, ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÐŽÐ°ÑÐ°, ÐºÐ»ÑÑÐµÐ²ÑÐµ ÑÐ»ÐŸÐ²Ð°)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="652"><i>buildcol.pl</i></Text>
+</th>
+<th width="406">
+<Text id="653">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="654">Building ÐÐŸÑÑÑÐŸÐµÐœÐžÐµ</Text>
+</th>
+<th width="406">
+<Text id="655">ÐÑÐŸÑÐµÑÑ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐžÐœÐŽÐµÐºÑÐœÑÑ
+ ÑÑÑÑÐºÑÑÑ Ðž ÑÑÑÑÐºÑÑÑ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°, ÐºÐŸÑÐŸÑÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑÑÑ ÐŽÐ»Ñ ÐŽÐŸÑÑÑÐ¿Ð° Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑÐŒ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="656">C++</Text>
+</th>
+<th width="406">
+<Text id="657">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÑÐ¹ ÑÐ·ÑÐº, Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ ÐœÐ°Ð¿ÐžÑÐ°ÐœÐŸ Ð±ÐŸÐ»ÑÑÐžÐœÑÑÐ²ÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ Greenstone ÐÐ°Ð»ÑÐµ Ðž Ð±ÐŸÐ»ÑÑÐžÐµ ÑÐµÐ³ÐžÑÑÑÑ Ð²ÑÐ³Ð»ÑÐŽÑÑ ÐŸÐŽÐžÐœÐ°ÐºÐŸÐ²ÐŸ ÐŽÐ»Ñ ÑÐ¿ÑÐŸÑÐµÐœÐžÑ Ð¿ÐŸÐžÑÐºÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="658">Casefolding</Text>
+</th>
+<th width="406">
+<Text id="659">Making uppercase and lowercase words look the same, for searching purposes</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="660">CGI (Common Gateway Interface)</Text>
+</th>
+<th width="406">
+<Text id="661">Ð¡Ñ
+ÐµÐŒÐ°, ÐºÐŸÑÐŸÑÐ°Ñ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÐµÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ ÑÐ°Ð±ÐŸÑÐ°ÑÑ Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°ÐŒÐž ÐœÐ° Ð³Ð»Ð°Ð²ÐœÐŸÐŒ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐµ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÑÐ°Ð±ÐŸÑÑ Ñ Ð²ÐµÐ±-ÑÑÑÐ°ÐœÐžÑÐ°ÐŒÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="662">Ð¡ÐºÑÐžÐ¿Ñ CGI</Text>
+</th>
+<th width="406">
+<Text id="663">ÐÐŸÐŽ, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐ²ÑÐ·Ð°Ðœ Ñ ÐºÐœÐŸÐ¿ÐºÐŸÐ¹, ÐŒÐµÐœÑ ÐžÐ»Ðž ÑÑÑÐ»ÐºÐŸÐ¹ ÐœÐ° Ð²ÐµÐ±Â¬ÑÑÑÐ°ÐœÐžÑÐµ, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ, ÑÑÐŸ ÐŽÐŸÐ»Ð¶ÐµÐœ ÑÐŽÐµÐ»Ð°ÑÑ Ð³Ð»Ð°Ð²ÐœÑÐ¹ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑ Ð¿ÑÐž ÐœÐ°Ð¶Ð°ÑÐžÐž ÐœÐ° ÐœÐµÐµ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="664"><i>cgi-bin</i></Text>
+</th>
+<th width="406">
+<Text id="665">ÐÐžÑÐµÐºÑÐŸÑÐžÑ, Ð² ÐºÐŸÑÐŸÑÐŸÐ¹ ÑÐŸÑ
+ÑÐ°ÐœÐµÐœÑ ÑÐºÑÐžÐ¿ÑÑ CGI.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="666">Classifier ÐÐ»Ð°ÑÑÐžÑÐžÐºÐ°ÑÐŸÑ</Text>
+</th>
+<th width="406">
+<Text id="667">ÐÐŸÐŽÐŸÐ²ÑÐ¹ ÐŒÐŸÐŽÑÐ»Ñ, ÐºÐŸÑÐŸÑÑÐ¹ Ð°ÐœÐ°Ð»ÐžÐ·ÐžÑÑÐµÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ° ÐŽÐ»Ñ ÑÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÐžÐœÐŽÐµÐºÑÐŸÐ² ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="668">Collection ÐÐŸÐ»Ð»ÐµÐºÑÐžÑ</Text>
+</th>
+<th width="406">
+<Text id="669">ÐÐ°Ð±ÐŸÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ², ÐºÐŸÑÐŸÑÑÐµ ÑÐŸÐ±ÑÐ°ÐœÑ Ð²ÐŒÐµÑÑÐµ Ð¿ÐŸÐŽ ÐŸÐŽÐœÐžÐŒ Ð¿ÐŸÐžÑÐºÐŸÐ²ÑÐŒ Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑ ÐžÐœÑÐµÑÑÐµÐ¹ÑÐŸÐŒ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="670">Collection configuration file ÐÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</th>
+<th width="406">
+<Text id="671">Ð€Ð°Ð¹Ð», ÐºÐŸÑÐŸÑÑÐ¹, ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ, ÐºÐ°Ðº ÐŽÐŸÐ»Ð¶ÐœÐ° Ð±ÑÑÑ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÂ¬Ð²Ð°ÐœÐ° Ðž Ð¿ÐŸÑÑÑÐŸÐµÐœÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ, ÐºÐ°ÐºÐžÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐžÐœÐŽÐµÐºÑÑ Ðž ÑÐ·ÑÐº ÐžÐœÑÐµÑÑÐµÐ¹ÑÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="672">Collection server Ð¡ÐµÑÐ²ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</th>
+<th width="406">
+<Text id="673">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°, ÐŸÑÐ²ÐµÑÑÑÐ²ÐµÐœÐœÐ°Ñ Ð·Ð° Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÐµ ÐŽÐŸÑÑÑÐ¿Ð° Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Ð¿ÑÐž ÐµÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="674">Configuration file ÐÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð»</Text>
+</th>
+<th width="406">
+<Text id="675">Ð¡ÐŒÐŸÑÑÐžÑÐµ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐºÐŸÐ»ÐµÐºÑÐžÐž, Ð³Ð»Ð°Ð²ÐœÑÐ¹ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð», ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð» ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="676">CVS (Concurrent Versioning System)</Text>
+</th>
+<th width="406">
+<Text id="677">Ð¡Ñ
+ÐµÐŒÐ° ÐŽÐ»Ñ Ð¿ÐŸÐŽÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÐžÑÑ
+ÐŸÐŽÐœÐŸÐ³ÐŸ ÐºÐŸÐŽÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ Ð²
+Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="678"><i>db2txt</i></Text>
+</th>
+<th width="406">
+<Text id="679">Ð¡ÑÐµÐŽÑÑÐ²ÐŸ ÐŽÐ»Ñ Ð¿ÑÐŸÑÐŒÐŸÑÑÐ° Ð±Ð°Ð· ÐŽÐ°ÐœÐœÑÑ
+ GDBM Ð² ÑÐµÐºÑÑÐŸÐ²ÐŸÐŒ ÑÐµÐ¶ÐžÐŒÐµ (ÑÐŒÐŸÑÑÐžÑÐµ GDBM)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="680">Demo collection ÐÐµÐŒÐŸÐœÑÑÑÐ°ÑÐžÐŸÐœÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ</Text>
+</th>
+<th width="406">
+<Text id="681">ÐÐŸÐŽÑÐ°Ð·ÐŽÐµÐ» ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž Humanities Development Library, ÑÐ°Ð¿ÑÐŸÑÑÑÐ°ÐœÑÐµÐŒÑÐ¹ Ñ ÑÑÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐŸÐ¹ Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÐŽÐ»Ñ ÐžÐ»Ð»ÑÑÑÑÐ°ÑÐžÐž Ðž ÐŸÐ±ÑÑÐµÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="682">Digital library ÐŠÐžÑÑÐŸÐ²Ð°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° DL</Text>
+</th>
+<th width="406">
+<Text id="683">ÐÐ°Ð±ÐŸÑ ÑÐžÑÑÐŸÐ²ÑÑ
+ ÐŸÐ±ÑÐµÐºÑÐŸÐ² (ÑÐµÐºÑÑÐŸÐ²ÑÑ
+, Ð°ÑÐŽÐžÐŸ Ðž Ð²ÐžÐŽÐµÐŸ) Ð²ÐŒÐµÑÑÐµ ÑÐŸ ÑÑÐµÐŽÑÑÐ²Ð°ÐŒÐž ÐŽÐŸÑÑÑÐ¿Ð° Ðž ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÑ, Ð²ÑÐ±ÐŸÑÐ°, ÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž Ðž Ð¿ÐŸÐŽÐŽÐµÑÐ¶Ð°ÐœÐžÑ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Ð Ð°Ð·Ð²ÐžÑÐžÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ Ð³ÑÐŒÐ°ÐœÐžÑÐ°ÑÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐŽÐ»Ñ ÑÐ°Ð·Ð²ÐžÐ²Ð°ÑÑÐžÑ
+ÑÑ ÑÑÑÐ°Ðœ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="684">DL</Text>
+</th>
+<th width="406">
+<Text id="685">Development Library, A Greenstone collection of humanitarian information for developing countries</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="686">Document ÐÐŸÐºÑÐŒÐµÐœÑ</Text>
+</th>
+<th width="406">
+<Text id="687">ÐÑÐœÐŸÐ²ÐœÐŸÐ¹ ÑÐ»ÐµÐŒÐµÐœÑ, ÐžÐ· ÐºÐŸÑÐŸÑÐŸÐ³ÐŸ ÑÐŸÑÑÐŸÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÑÐœÑÐµ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž: ÐŒÐŸÐ¶ÐµÑ Ð²ÐºÐ»ÑÑÐ°ÑÑ Ð² ÑÐµÐ±Ñ ÑÐµÐºÑÑ, Ð³ÑÐ°ÑÐžÐºÑ, Ð·Ð²ÑÐº Ðž Ð²ÐžÐŽÐµÐŸ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="688">Dublin core</Text>
+</th>
+<th width="406">
+<Text id="689">Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐ¹ ÐŒÐµÑÐŸÐŽ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="690">Fast CGI</Text>
+</th>
+<th width="406">
+<Text id="691">Ð¡ÑÐµÐŽÑÑÐ²ÐŸ, Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑÐµÐµ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑ ÑÐºÑÐžÐ¿ÑÑ CGI Ð² Ð°ÐºÑÐžÐ²ÐœÐŸÑÑÐž, ÑÑÐŸÐ±Ñ Ð¿ÑÐž Ð¿ÐŸÐ²ÑÐŸÑÐœÐŸÐŒ Ð²ÐºÐ»ÑÑÐµÐœÐžÐž ÐžÑ
+ Ð·Ð°ÐœÐŸÐ²ÐŸ ÐœÐµ Ð·Ð°Ð¿ÑÑÐºÐ°ÑÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="692">Filter program ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÑÐžÐ»ÑÑÑÐ°ÑÐžÐž</Text>
+</th>
+<th width="406">
+<Text id="693">Ð¢Ð° ÑÐ°ÑÑÑ ÑÐµÑÐ²ÐµÑÐ° ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹, ÐºÐŸÑÐŸÑÐ°Ñ Ð²ÑÐ¿ÐŸÐ»ÐœÑÐµÑ ÐŸÐ¿ÐµÑÐ°ÑÐžÐž Ð·Ð°Ð¿ÑÐŸÑÐ° Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="694">Format string Ð€ÐŸÑÐŒÐ°ÑÐœÐ°Ñ ÑÑÑÐŸÐºÐ°</Text>
+</th>
+<th width="406">
+<Text id="695">Ð¡ÑÑÐŸÐºÐ°, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐºÐ°Ð·ÑÐ²Ð°ÐµÑ, ÐºÐ°Ðº Ð²ÑÐ¿ÐŸÐ»ÐœÑÑÑ Ð¿ÐŸÐºÐ°Ð· ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ð² Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="696">GB-encoding</Text>
+</th>
+<th width="406">
+<Text id="697">Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐ¹ ÐŒÐµÑÐŸÐŽ ÐºÐŸÐŽÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐºÐžÑÐ°Ð¹ÑÐºÐŸÐ³ÐŸ ÑÐ·ÑÐºÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="698">GDBM ÐÐµÐœÐµÐŽÐ¶ÐµÑ Ð±Ð°Ð· ÐŽÐ°ÐœÐœÑÑ
+ GNU</Text>
+</th>
+<th width="406">
+<Text id="699">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ Ð² Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐŒ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐž Greenstone ÐŽÐ»Ñ Ñ
+ÑÐ°ÐœÐµÐœÐžÑ ÐŒÐµÑÐ°ÐŽÐ°ÐœÐœÑÑ
+ ÐŽÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="700">GIMP</Text>
+</th>
+<th width="406">
+<Text id="701">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° (Ð² Linux), ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐžÐºÐŸÐœÐŸÐº Ð² Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="702">GML (Greenstone Markup Language)</Text>
+</th>
+<th width="406">
+<Text id="703">XML-ÑÐŸÐ²ÐŒÐµÑÑÐžÐŒÑÐ¹ ÑÐŸÑÐŒÐ°Ñ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÐŽÐ»Ñ Ð²ÐœÑÑÑÐµÐœÐœÐµÐ³ÐŸ Ñ
+ÑÐ°ÐœÐµÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ².</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="704">Gnu license (ÐÐžÑÐµÐœÐ·ÐžÑ GNU)</Text>
+</th>
+<th width="406">
+<Text id="705">ÐÐžÑÐµÐœÐ·ÐžÑ, Ð¿ÐŸÐ·Ð²ÐŸÐ»ÑÑÑÐ°Ñ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÐŒ ÑÐ²ÐŸÐ±ÐŸÐŽÐœÐŸ Ð¿ÐµÑÐµÐ¿ÐžÑÑÐ²Ð°ÑÑ Ðž ÑÐ°ÑÐ¿ÑÐŸÑÑÑÐ°ÐœÑÑÑ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ, Ð° ÑÐ°ÐºÐ¶Ðµ ÐŒÐŸÐŽÐžÑÐžÑÐžÑÐŸÐ²Ð°ÑÑ ÐµÐµ Ð¿ÑÐž ÑÑÐ»ÐŸÐ²ÐžÐž, ÑÑÐŸ ÐŒÐŸÐŽÐžÑÐžÐºÐ°ÑÐžÑ ÑÐ°ÐºÐ¶Ðµ Ð±ÑÐŽÐµÑ ÐŸÐ±ÑÐµÐŽÐŸÑÑÑÐ¿ÐœÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="706">Greenstone</Text>
+</th>
+<th width="406">
+<Text id="707">ÐÐ°Ð·Ð²Ð°ÐœÐžÐµ ÐŽÐ°ÐœÐœÐŸÐ¹ ÑÐžÑÑÐŸÐ²ÐŸÐ¹ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="708">GSDL Greenstone Digital Library</Text>
+</th>
+<th width="406">
+<Text id="709">ÐÐ±Ð±ÑÐµÐ²ÐžÐ°ÑÑÑÐ° ÐœÐ°Ð·Ð²Ð°ÐœÐžÑ ÐŠÐžÑÑÐŸÐ²Ð°Ñ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="710"><i>%GSDLHOME%</i></Text>
+</th>
+<th width="406">
+<Text id="711">ÐÐµÑÐµÐŒÐµÐœÐœÐ°Ñ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ cÐžÑÑÐµÐŒÑ, Ð¿ÑÐµÐŽÑÑÐ°Ð²Ð»ÑÑÑÐ°Ñ ÐŽÐžÑÐµÐºÑÐŸÑÐžÑ Ð²ÑÑÑÐµÐ³ÐŸ ÑÑÐŸÐ²ÐœÑ, Ð² ÐºÐŸÑÐŸÑÐŸÐ¹ ÑÐŸÐŽÐµÑÐ¶Ð°ÑÑÑ Ð²ÑÐµ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÑ Ðž ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž Greenstone (Ð² Unix ÑÑÐŸ SGSDLHOME).</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="712"><i>%GSDLOS%</i></Text>
+</th>
+<th width="406">
+<Text id="713">ÐÐµÑÐµÐŒÐµÐœÐœÐ°Ñ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐ°ÐµÑ ÑÑ ÐŸÐ¿ÐµÑÐ°ÑÐžÐŸÐœÐœÑÑ ÑÐžÑÑÐµÐŒÑ, ÐºÐŸÑÐŸÑÐ°Ñ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÑÑÑ Ð² ÐŽÐ°ÐœÐœÑÐ¹ ÐŒÐŸÐŒÐµÐœÑ.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="714"><i>hashfile</i></Text>
+</th>
+<th width="406">
+<Text id="715">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Ð² Greenstone, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ Ð¿ÑÐž ÐžÐŒÐ¿ÐŸÑÑÐµ Ðž Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÐž ÐŽÐ»Ñ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐžÑÐµÐ»Ñ ÐºÐ°Ð¶ÐŽÐŸÐ³ÐŸ ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="716">HTML</Text>
+</th>
+<th width="406">
+<Text id="717">Ð¯Ð·ÑÐº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ, Ð² ÐºÐŸÑÐŸÑÐŸÐŒ ÐœÐ°Ð¿ÐžÑÐ°ÐœÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð² Ð²ÐµÐ±-ÑÑÑÐ°ÐœÐžÑÐ°Ñ
+ </Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="718"><i>import.pl</i></Text>
+</th>
+<th width="406">
+<Text id="719">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ ÐŽÐ»Ñ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ²</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="720">Importing ÐÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ</Text>
+</th>
+<th width="406">
+<Text id="721">ÐÑÐŸÑÐµÑÑ Ð¿ÐµÑÐµÐœÐŸÑÐ° ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² ÐžÐ·Ð²ÐœÐµ Ð² ÑÐžÑÑÐµÐŒÑ Greenstone</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="722">Index ÐÐœÐŽÐµÐºÑ</Text>
+</th>
+<th width="406">
+<Text id="723">ÐÐ°ÑÐ°ÐŒÐµÑÑ, Ð¿ÐŸ ÐºÐŸÑÐŸÑÐŸÐŒÑ ÐŸÑÑÑÐµÑÑÐ²Ð»ÑÐµÑÑÑ Ð¿ÐŸÐžÑÐº Ðž Ð¿ÑÐŸÑÐŒÐŸÑÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="724">InstallShield</Text>
+</th>
+<th width="406">
+<Text id="725">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Windows, Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐºÐŸÑÐŸÑÐŸÐ¹ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° ÑÑÑÐ°ÐœÐ°Ð²Ð»ÐžÐ²Ð°ÐµÑÑÑ ÐœÐ° Ð¶ÐµÑÑÐºÐžÐ¹ ÐŽÐžÑÐº Ñ CD-ROM</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="726">Main configuration file ÐÐ»Ð°Ð²ÐœÑÐ¹ ÐºÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÑÐ°Ð¹Ð»</Text>
+</th>
+<th width="406">
+<Text id="727">Ð€Ð°Ð¹Ð», ÑÐŸÐŽÐµÑÐ¶Ð°ÑÐžÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÑ Ðž ÑÐºÐ°Ð·Ð°ÐœÐžÑ, ÑÐžÐ¿ÐžÑÐœÑÐµ ÐŽÐ»Ñ Ð²ÑÐµÑ
+ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="728">Metadata ÐÐµÑÐ°ÐŽÐ°ÐœÐœÑÐµ</Text>
+</th>
+<th width="406">
+<Text id="729">ÐÐ¿ÐžÑÐ°ÑÐµÐ»ÑÐœÑÐµ ÐŽÐ°ÐœÐœÑÐµ, ÑÐ°ÐºÐžÐµ ÐºÐ°Ðº Ð°Ð²ÑÐŸÑ, ÐœÐ°Ð·Ð²Ð°ÐœÐžÐµ, ÐŽÐ°ÑÐ°, ÐºÐ»ÑÑÐµÐ²ÑÐµ ÑÐ»ÐŸÐ²Ð° Ðž Ñ.ÐŽ., ÐºÐŸÑÐŸÑÑÐµ ÐžÐŒÐµÐµÑ ÐºÐ°Ð¶ÐŽÑÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ (ÐžÐ»Ðž ÐŽÐŸÐºÑÐŒÐµÐœÑÐ°Ð»ÑÐœÐ°Ñ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÑ)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="730">MG</Text>
+</th>
+<th width="406">
+<Text id="731">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ Greenstone ÐŽÐ»Ñ Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÐŸÐ³ÐŸ ÐžÐœÐŽÐµÐºÑÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð² ÑÐµÐ±Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÐµ ÐŒÐµÑÐŸÐŽÑ ÑÐ¶Ð°ÑÐžÑ (ÑÐŒÐŸÑÑÐžÑÐµ Witten, I.H., Morrat, A. Bell, T. Managing Gigabytesrcompressing and indexing documents and images, Morgan Kaufman, Ð²ÑÐŸÑÐŸÐµ ÐžÐ·ÐŽÐ°ÐœÐžÐµ, 1999)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="732"><i>mgbuild</i></Text>
+</th>
+<th width="406">
+<Text id="733">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° MG ÐŽÐ»Ñ Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ ÑÐ¶Ð°ÑÑÑ
+ Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÑÑ
+ ÐžÐœÐŽÐµÐºÑÐŸÐ²</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="734"><i>mgquery</i></Text>
+</th>
+<th width="406">
+<Text id="735">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° MG ÐŽÐ»Ñ Ð·Ð°Ð¿ÑÐŸÑÐ° ÑÐ¶Ð°ÑÑÑ
+ Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÑÑ
+ ÐžÐœÐŽÐµÐºÑÐŸÐ²</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="736"><i>mkcol.pl</i></Text>
+</th>
+<th width="406">
+<Text id="737">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone, ÐºÐŸÑÐŸÑÐ°Ñ ÑÐŸÐ·ÐŽÐ°ÑÑ Ðž ÐžÐœÐžÑÐžÐžÑÑÐµÑ ÑÑÑÑÐºÑÑÑÑ ÐŽÐžÑÐµÐºÑÐŸÑÐžÐž ÐŽÐ»Ñ ÐœÐŸÐ²ÐŸÐ¹ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="738">New ZealandÂ Digital Library Project ÐÑÐŸÐµÐºÑ ÐŠÐžÑÑÐŸÐ²ÐŸÐ¹ ÐÐžÐ±Ð»ÐžÐŸÑÐµÐºÐž ÐÐŸÐ²ÐŸÐ¹ ÐÐµÐ»Ð°ÐœÐŽÐžÐž</Text>
+</th>
+<th width="406">
+<Text id="739">ÐÑÑÐ»ÐµÐŽÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐžÐ¹ Ð¿ÑÐŸÐµÐºÑ ÐŽÐµÐ¿Ð°ÑÑÐ°ÐŒÐµÐœÑÐ° ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÐœÐŸÐ³ÐŸ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ ÑÐœÐžÐ²ÐµÑÑÐžÑÐµÑÐ° ÐÐ°Ð¹ÐºÐ°ÑÐŸ, ÐÐŸÐ²Ð°Ñ ÐÐµÐ»Ð°ÐœÐŽÐžÑ, ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐ·ÐŽÐ°Ð» Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÐµ Greenstone (nzdl.org)</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="740">OID (Object Identifier) ÐÐ¿ÑÐµÐŽÐµÐ»ÐžÑÐµÐ»Ñ ÐŸÐ±ÑÐµÐºÑÐ°</Text>
+</th>
+<th width="406">
+<Text id="741">Ð£ÐœÐžÐºÐ°Ð»ÑÐœÑÐ¹ ÐžÐŽÐµÐœÑÐžÑÐžÐºÐ°ÑÐžÐŸÐœÐœÑÐ¹ ÐºÐŸÐŽ, Ð¿ÑÐžÑÐ²Ð°ÐžÐ²Ð°ÐµÐŒÑÐ¹ ÐºÐ°Ð¶ÐŽÐŸÐŒÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="742">Perl</Text>
+</th>
+<th width="406">
+<Text id="743">Ð¯Ð·ÑÐº Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐžÑÐŸÐ²Ð°ÐœÐžÑ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÐŽÐ»Ñ ÐŸÐ¿ÐµÑÐ°ÑÐžÐ¹ Ð¿ÑÐŸÑÐµÑÑÐ° Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="744">Ping</Text>
+</th>
+<th width="406">
+<Text id="745">Ð¡ÐŸÐŸÐ±ÑÐµÐœÐžÐµ, Ð¿ÐŸÑÐ»Ð°ÐœÐœÐŸÐµ Ð² ÑÐžÑÑÐµÐŒÑ ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ,
+ÑÐ°Ð±ÐŸÑÐ°ÐµÑ ÐŸÐœÐ° ÐžÐ»Ðž ÐœÐµÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="746">Plugin ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐµ ÐŽÐŸÐ¿ÐŸÐ»ÐœÐµÐœÐžÐµ</Text>
+</th>
+<th width="406">
+<Text id="747">ÐÐŸÐŽÑÐ»ÑÐœÑÐ¹ ÐºÐŸÐŽ ÐŽÐ»Ñ ÑÐ°Ð±ÐŸÑÑ Ñ ÑÐ°Ð·Ð»ÐžÑÐœÑÐŒÐž ÑÐŸÑÐŒÐ°ÑÐ°ÐŒÐž, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ Ð²ÐŸ Ð²ÑÐµÐŒÑ ÐžÐŒÐ¿ÐŸÑÑÐžÑÐŸÐ²Ð°ÐœÐžÑ Ðž Ð¿ÐŸÑÑÑÐŸÐµÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="748">Protocol ÐÑÐŸÑÐŸÐºÐŸÐ»</Text>
+</th>
+<th width="406">
+<Text id="749">ÐÐ°Ð±ÐŸÑ ÑÑÐ»ÐŸÐ²ÐœÑÑ
+ ÐŸÐ±ÐŸÐ·ÐœÐ°ÑÐµÐœÐžÐ¹, Ð¿ÑÐž Ð¿ÐŸÐŒÐŸÑÐž ÐºÐŸÑÐŸÑÑÑ
+ Greenstone receptionist ÑÐ°Ð±ÐŸÑÐ°ÐµÑ Ñ ÑÐµÑÐ²ÐµÑÐŸÐŒ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="750">Ð Ð°ÐœÐ¶ÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ Ð·Ð°Ð¿ÑÐŸÑ</Text>
+</th>
+<th width="406">
+<Text id="751">ÐÐ°Ð¿ÑÐŸÑ Ðº ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐŸÐœÐœÐŸÐ¹ ÑÐžÑÑÐµÐŒÐµ ÐžÐ·Ð²Ð»ÐµÑÐµÐœÐžÑ, ÐºÐŸÑÐŸÑÐ°Ñ Ð²ÑÐŽÐ°ÐµÑ ÐŽÐŸÐºÑÐŒÐµÐœÑÑ Ð¿ÐŸ ÑÑÐµÐ¿ÐµÐœÐž Ð²Ð°Ð¶ÐœÐŸÑÑÐž.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="752">Receptionist</Text>
+</th>
+<th width="406">
+<Text id="753">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°, ÐºÐŸÑÐŸÑÐ°Ñ ÐŸÑÐ³Ð°ÐœÐžÐ·ÐŸÐ²ÑÐ²Ð°ÐµÑ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»ÑÑÐºÐžÐ¹ ÐžÐœÑÐµÑÑÐµÐ¹Ñ Greenstone.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="754">RTF</Text>
+</th>
+<th width="406">
+<Text id="755">Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐ¹ ÑÐŸÑÐŒÐ°Ñ ÐŽÐ»Ñ Ð²Ð·Ð°ÐžÐŒÐŸÐŸÐ±ÐŒÐµÐœÐ° ÑÐµÐºÑÑÐŸÐ²ÑÐŒÐž ÐÐŸÐºÑÐŒÐµÐœÑÐ°ÐŒÐž</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="756">Searching ÐÐŸÐžÑÐº</Text>
+</th>
+<th width="406">
+<Text id="757">ÐÐŸÑÑÑÐ¿ Ðº ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐž ÑÐµÑÐµÐ· Ð¿ÐŸÐ»ÐœÐŸÑÐµÐºÑÑÐŸÐ²ÐŸÐ¹ Ð¿ÐŸÐžÑÐº ÐµÐ³ÐŸ ÑÐŸÐŽÐµÑÐ¶ÐžÐŒÐŸÐ³ÐŸ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="758">Server Ð¡ÐµÑÐ²ÐµÑ</Text>
+</th>
+<th width="406">
+<Text id="759">Ð¡ÐŒÐŸÑÑÐžÑÐµ ÑÐµÑÐ²ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑÐžÐ¹ Ðž Ð²ÐµÐ±-ÑÐµÑÐ²ÐµÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="760"><i>setup.bat, setup.sh, setup.csh</i></Text>
+</th>
+<th width="406">
+<Text id="761">Ð¡ÐºÑÐžÐ¿Ñ, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÐ¹ ÐŽÐ»Ñ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž Ðž ÑÐµÐŸÑÐ³Ð°ÐœÐžÐ·Ð°ÑÐžÐž Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐœÐŸÐ³ÐŸ ÐŸÐ±ÐµÑÐ¿ÐµÑÐµÐœÐžÑ Greenstone Ð¿ÐŸ Ð²Ð°ÑÐµÐŒÑ Ð¶ÐµÐ»Ð°ÐœÐžÑ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="762">Site configuration ÐÐŸÐœÑÐžÐ³ÑÑÐ°ÑÐžÑ ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÑ</Text>
+</th>
+<th width="406">
+<Text id="763">Ð€Ð°Ð¹Ð», ÐºÐŸÑÐŸÑÑÐ¹ ÑÐŸÐŽÐµÑÐ¶ÐžÑ Ð²ÑÐµ ÑÐºÐ°Ð·Ð°ÐœÐžÑ ÐŽÐ»Ñ ÐœÐ°ÑÑÑÐŸÐ¹ÐºÐž Greenstone Ðº ÐŒÐµÑÑÐŸÐ¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÑ, ÐœÐ° ÐºÐŸÑÐŸÑÐŸÐµ ÐŸÐœ Ð±ÑÐŽÐµÑ Ð£ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="764">Stemming</Text>
+</th>
+<th width="406">
+<Text id="765">ÐÐ³ÐœÐŸÑÐžÑÐŸÐ²Ð°ÐœÐžÐµ ÐŸÐºÐŸÐœÑÐ°ÐœÐžÐ¹ ÑÐ»ÐŸÐ² ÐŽÐ»Ñ ÑÐ°ÑÑÐžÑÐµÐœÐžÑ
+ÐŸÐ±ÐŸÐ±ÑÐµÐœÐžÑ Ð·Ð°Ð¿ÑÐŸÑÐ°</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="766">STL</Text>
+</th>
+<th width="406">
+<Text id="767">Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ ÑÐ°Ð±Ð»ÐŸÐœÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ°, ÑÐžÑÐŸÐºÐŸÐŽÐŸÑÑÑÐ¿ÐœÐ°Ñ Ð±ÐžÐ±Ð»ÐžÐŸÑÐµÐºÐ° ÐºÐŸÐŽÐ° C++, ÑÐ°Ð·ÑÐ°Ð±ÐŸÑÐ°ÐœÐœÐ°Ñ Silicon Graphics</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="768">txt2db</Text>
+</th>
+<th width="406">
+<Text id="769">ÐÑÐŸÐ³ÑÐ°ÐŒÐŒÐ° Greenstone, ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÐ°Ñ Ð² Ð¿ÑÐŸÑÐµÑÑÐµ ÑÐŸÐ·ÐŽÐ°ÐœÐžÑ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
+ GDBM</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="770">Unicode Ð£ÐœÐžÐºÐŸÐŽ</Text>
+</th>
+<th width="406">
+<Text id="771">Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ ÑÑ
+ÐµÐŒÐ° ÐŽÐ»Ñ Ð¿ÐŸÐºÐ°Ð·Ð° ÑÐžÐŒÐ²ÐŸÐ»ÐŸÐ², ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÐµÐŒÑÑ
+ ÐŒÐžÑÐŸÐ²ÑÐŒÐž ÑÐ·ÑÐºÐ°ÐŒÐž </Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="772">UNU</Text>
+</th>
+<th width="406">
+<Text id="773">Ð£ÐœÐžÐ²ÐµÑÑÐžÑÐµÑ ÐÐÐ</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="774">Web server ÐÐµÐ±-ÑÐµÑÐ²ÐµÑ</Text>
+</th>
+<th width="406">
+<Text id="775">Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÐ°Ñ Ð¿ÑÐŸÐ³ÑÐ°ÐŒÐŒÐ°, ÐºÐŸÑÐŸÑÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÑÑÑ ÐºÐŸÐŒÐ¿ÑÑÑÐµÑÑ ÐŽÐ»Ñ Ð¿ÑÐµÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÐŽÐŸÑÑÑÐ¿Ð° Ðº ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÑÐµÑÐµÐ· WWW.</Text>
+</th>
+</tr>
+<tr>
+<th width="123">
+<Text id="776">XML</Text>
+</th>
+<th width="406">
+<Text id="777">Ð¡ÑÐ°ÐœÐŽÐ°ÑÑÐœÑÐ¹ ÑÐŸÑÐŒÐ°Ñ ÐŽÐ»Ñ ÑÑÑÑÐºÑÑÑÐžÑÐŸÐ²Ð°ÐœÐœÑÑ
+ ÐŽÐŸÐºÑÐŒÐµÐœÑÐŸÐ² Ðž ÐŽÐ°ÐœÐœÑÑ
+ Ð² ÐÐœÑÐµÑÐœÐµÑÐµ (Greenstone Markup Language ÐœÐ°Ñ
+ÐŸÐŽÐžÑÑÑ Ð² XML ÑÐŸÐ²ÐŒÐµÑÑÐžÐŒÐŸÐŒ ÑÐŸÑÐŒÐ°ÑÐµ)</Text>
+</th>
+</tr>
+</TableContent>
+</Table>
+</Content>
+</Chapter>
+<FootnoteList>
+<Footnote id="1">
+<Text id="778">ÑÑÐ° ÐŸÐ¿ÑÐžÑ Ð¿ÐŸÐ²ÑÐµÐ¶ÐŽÐ°ÐµÑÑÑ, ÐµÑÐ»Ðž ÑÐ»ÐµÐŒÐµÐœÑ Ñ ÑÐµÐŒ Ð¶Ðµ ÑÐ°ÐŒÑÐŒ ÐžÐŒÐµÐœÐµÐŒ ÑÐ¶Ðµ ÑÑÑÐµÑÑÐ²ÑÐµÑ</Text>
+</Footnote>
+</FootnoteList>
+</Manual>
Index: /trunk/gsdl-documentation/shared/ApplyXSLT.java
===================================================================
--- /trunk/gsdl-documentation/shared/ApplyXSLT.java	(revision 13632)
+++ /trunk/gsdl-documentation/shared/ApplyXSLT.java	(revision 13632)
@@ -0,0 +1,93 @@
+/**
+ *#########################################################################
+ *
+ * A component of the Greenstone Librarian Interface (GLI) application, 
+ * part of the Greenstone digital library software suite from the New 
+ * Zealand Digital Library Project at the University of Waikato, 
+ * New Zealand.
+ *
+ * Author: Michael Dewsnip 
+ *         Greenstone Project, New Zealand Digital Library
+ *         University of Waikato
+ *         http://www.nzdl.org
+ *
+ * Copyright (C) 2004 New Zealand Digital Library, University of Waikato
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+ *########################################################################
+ */
+
+import java.io.*;
+import javax.xml.transform.Transformer;
+import javax.xml.transform.TransformerFactory;
+import javax.xml.transform.TransformerConfigurationException;
+import javax.xml.transform.TransformerException;
+import javax.xml.transform.stream.StreamSource;
+import javax.xml.transform.stream.StreamResult;
+
+/** Any class that wants to act as the owner of an AppendLineOnlyFileDocument has to implement this.
+ * @author Michael Dewsnip, Greenstone Project, New Zealand Digital Library, University of Waikato
+ * @version 2.41 final
+ */
+public class ApplyXSLT
+{
+    static public void main(String[] args)
+    {
+	if (args.length < 2) {
+	    System.err.println("Usage: ApplyXSLT <XSLfile> <XMLfile>");
+	    System.exit(1);
+	}
+
+	System.setProperty("javax.xml.transform.TransformerFactory",
+			   "org.apache.xalan.processor.TransformerFactoryImpl");
+	TransformerFactory t_factory = null;
+	try {
+	    t_factory = org.apache.xalan.processor.TransformerFactoryImpl.newInstance();
+	}
+	catch (Exception ex) {
+	    System.err.println("XMLTransformer() exception " + ex.getMessage());
+	    System.exit(1);
+	}
+
+	String stylesheet = args[0];
+	String xml_in = args[1];
+	try {
+	    // Use the TransformerFactory to process the stylesheet Source and generate a Transformer
+	    Transformer transformer = t_factory.newTransformer(new StreamSource(stylesheet));
+
+	    // Use the Transformer to transform an XML Source and send the output to a Result object
+	    StreamSource input = (xml_in.equals("-") ? new StreamSource(System.in) : new StreamSource(xml_in));
+	    OutputStreamWriter output = new OutputStreamWriter(System.out, "UTF-8");
+	    transformer.transform(input, new StreamResult(output));
+	}
+	catch (TransformerConfigurationException ex) {
+	    //System.err.println("XMLTransformer: couldn't create transformer object: " + ex.getMessageAndLocation());
+	    //System.err.println(ex.getLocationAsString());  
+	    ex.printStackTrace();
+	    System.exit(1);
+	}
+	catch (Exception ex) {
+	    //System.err.println("XMLTransformer: couldn't transform the source: " + ex.getMessage());
+	    ex.printStackTrace();
+	    System.exit(1);
+	}
+    }
+
+
+    static public String replaceAll(String source_string, String match_regexp, String replace_string)
+    {
+	return source_string.replaceAll(match_regexp, replace_string);
+    }
+}
Index: /trunk/gsdl-documentation/shared/Dictionary.java
===================================================================
--- /trunk/gsdl-documentation/shared/Dictionary.java	(revision 13632)
+++ /trunk/gsdl-documentation/shared/Dictionary.java	(revision 13632)
@@ -0,0 +1,439 @@
+
+import java.util.ResourceBundle;
+import java.util.Locale;
+import java.util.HashMap;
+import java.net.URL;
+import java.io.File;
+import java.io.InputStream;
+import java.io.FileInputStream;
+import java.io.Reader;
+import java.io.FileReader;
+import java.io.InputStreamReader;
+import java.io.BufferedReader;
+//import org.apache.xerces.parsers.DOMParser;
+import org.xml.sax.InputSource;
+//import org.xml.sax.XMLReader;
+//import org.xml.sax.XMLReaderFactory;
+import javax.xml.parsers.DocumentBuilder;
+import javax.xml.parsers.DocumentBuilderFactory;
+import org.w3c.dom.Document;
+import org.w3c.dom.Element;
+import org.w3c.dom.Node;
+import org.w3c.dom.NodeList;
+
+public class Dictionary {
+
+    private ResourceBundle glidict = null;
+    private ResourceBundle perldict = null;
+    private MacroFile core_macros = null;
+    private MacroFile aux_macros = null;
+    private HashMap metadata = null;
+    private Locale locale = null;
+    private String lang = null;
+    static final private int GLIDICT = 0;
+    static final private int GLIHELP = 1;
+    static final private int COREDM = 2;
+    static final private int AUXDM = 3;
+    static final private int TUTORIALS = 4;
+    static final private int PERLMODULES = 5;
+    static final private int METADATA = 6;
+
+    protected String gsdl_home = null;
+    
+    private ClassLoader classloader = null;
+
+
+    public Dictionary(String lang) {
+	this.lang = lang;
+	this.locale = new Locale(lang);
+	if (this.locale==null) {
+	    this.locale = Locale.getDefault();
+	}
+	gsdl_home = System.getProperty("GSDLHOME");
+	if (gsdl_home == null) {
+	    System.err.println("Error: GSDLHOME is null!!");
+	    System.exit(1);
+	}
+
+	this.classloader = new MyClassLoader(this.getClass().getClassLoader());
+    }
+    
+    public String get(String key) {
+	return get(key, null);
+    }
+    public String get(String key, String args) {
+	int pos = key.indexOf("::");
+	if (pos==-1) {
+	    System.err.println("invalid key: "+key);
+	    return "";
+	}
+	String package_name = key.substring(0, pos);
+	String key_name = key.substring(pos+2);
+	//System.err.println("pack = "+package_name+", key="+key_name);
+
+	if (package_name.equals("glidict")) {
+	    loadDictionary(GLIDICT);
+	    return getDictionaryText(glidict, key_name, args);
+	}
+	if (package_name.equals("coredm")) {
+	    loadDictionary(COREDM);
+	    return getMacroText(core_macros, key_name);
+	}
+	if (package_name.equals("perlmodules")) {
+	    loadDictionary(PERLMODULES);
+	    return getDictionaryText(perldict, key_name, args);
+	}
+	if (package_name.equals("auxdm")) {
+	    loadDictionary(AUXDM);
+	    return getMacroText(aux_macros, key_name);
+	}
+	if (package_name.equals("glihelp")) {
+	    return "";
+	}
+	if (package_name.equals("tutorials")) {
+	    return "";
+	}
+	if (package_name.equals("metadata")) {
+	    pos = key_name.indexOf(".");
+	    String namespace = key_name.substring(0,pos);
+	    String element = key_name.substring(pos+1);
+	    if (loadMetadata(namespace)) {
+		return getMetadataName(namespace, element);
+	    }
+	    return key_name;
+	}
+	System.err.println("invalid package name "+package_name);
+	return "";
+    }
+
+    public String getDictionaryText(ResourceBundle dictionary, String key, String args) {
+
+	try {
+	    String initial_raw = dictionary.getString(key);
+	    // convert to unicode, copied from gatherer dictionary
+	    String initial = new String(initial_raw.getBytes("ISO-8859-1"), "UTF-8");
+	    if (args == null || args.equals("")) {
+		return initial;
+	    }
+	    String [] args_array = args.split(";");
+	    // If the string contains arguments we have to insert them.
+	    String complete = "";
+	    // While we still have initial string left.
+	    while(initial.length() > 0 && initial.indexOf('{') != -1 && initial.indexOf('}') != -1) {
+		// Remove preamble
+		int opening = initial.indexOf('{');
+		int closing = initial.indexOf('}');
+		complete = complete + initial.substring(0, opening);
+		// Parse arg_num
+		String arg_str = initial.substring(opening + 1, closing);
+		int arg_num = Integer.parseInt(arg_str);
+		if(closing + 1 < initial.length()) {
+		    initial = initial.substring(closing + 1);
+		}
+		else {
+		    initial = "";
+		}
+		// Insert argument
+		if(0 <= arg_num && arg_num < args_array.length) {
+		    complete = complete + args_array[arg_num];
+		}
+	    }
+	    return complete + initial;
+
+	    //this.raw = ResourceBundle.getBundle(this.resource, this.locale);
+	} catch (Exception e) {
+	    //System.err.println("Dictionary: couldn't locate a resource bundle for "+resource);
+	}
+	System.err.println("no value found for key "+key+" in dictionary "+dictionary.toString());
+	return "";
+    }
+
+    private String getMacroText(MacroFile macros, String key) {
+	return macros.get(key);
+    }
+    
+    private String getMetadataName(String namespace, String element_name) {
+	Element meta_set = (Element)metadata.get(namespace);
+	String default_value = namespace+"."+element_name;
+	if (meta_set == null) {
+	    return default_value;
+	}
+	Element this_elem = getNamedChild(meta_set, "Element", "name", element_name);
+	if (this_elem == null) {
+	    return default_value;
+	}
+	Element this_lang = getNamedChild(this_elem, "Language", "code", this.lang);
+	if (this_lang == null) {
+	    this_lang = this_elem; // sometimes have attributes as children of element
+	}
+	
+	// need to modify this if we get multiple languages at the same level
+	Element label_att = getNamedChild(this_lang, "Attribute", "name", "label");
+	if (label_att == null) {
+	    return default_value;
+	}
+	return namespace+"."+getTextValue(label_att);
+    }
+    
+    private Element getNamedChild(Element parent, String child_element, String att_name, String att_value) {
+	NodeList elements = parent.getElementsByTagName(child_element);
+	for (int i=0; i<elements.getLength(); i++) {
+	    Element e = (Element)elements.item(i);
+	    if (e.getAttribute(att_name).equals(att_value)) {
+		return e;
+	    }
+	}
+	return null;
+    }
+    
+    private String getTextValue(Element elem) {
+	elem.normalize();
+	Node n = elem.getFirstChild();
+        while (n!=null && n.getNodeType() !=Node.TEXT_NODE) {
+            n=n.getNextSibling();
+        }
+	return n.getNodeValue();
+    }
+
+		
+    
+    private boolean loadDictionary(int type) {
+	switch (type) {
+	case GLIDICT:
+	    if (this.glidict == null) {
+		glidict = ResourceBundle.getBundle("dictionary", this.locale, this.classloader);
+		
+	    }
+	    break;
+	case PERLMODULES:
+	    if (this.perldict == null) {
+		perldict = ResourceBundle.getBundle("strings", this.locale, this.classloader);
+	    }
+	    break;
+	    
+	case COREDM:
+	    if (this.core_macros == null) {
+		core_macros = new MacroFile(MacroFile.CORE);
+	    }
+	    break;
+	    
+	case AUXDM:
+	    if (this.aux_macros == null) {
+		aux_macros = new MacroFile(MacroFile.AUX);
+	    }
+	    break;
+	}
+	return true;
+    }
+    
+    private boolean loadMetadata(String namespace) {
+	if (metadata == null) {
+	    metadata = new HashMap();
+	}
+
+	if (metadata.containsKey(namespace)) {
+	    // already loaded
+	    return true;
+	}
+	// find the metadata file
+	String file_name = namespace+".mds";
+	if (namespace.equals("dc")) {
+	    // what about qualified???
+	    file_name = "dublin.mds";
+	}
+	
+	file_name = gsdl_home + File.separator + "gli" + File.separator + "metadata"+ File.separator + file_name;
+	//System.err.println("metadata filename = "+file_name);
+	File metadata_file = new File(file_name);
+	if (!metadata_file.exists()) {
+	    System.err.println("metadata file "+file_name+" does not exist!");
+	    return false;
+	}
+	// parse the file
+	Element elem = parseXMLFile(metadata_file);
+	if (elem != null) {
+	    metadata.put(namespace, elem);
+	    return true;
+	}
+	return false;
+    }
+
+    private Element parseXMLFile(File file) {
+
+	try {
+	    //DOMParser parser = new DOMParser();
+	    //XMLReader parser = XMLReaderFactory.createXMLReader();
+	    DocumentBuilder builder =  DocumentBuilderFactory.newInstance().newDocumentBuilder();
+	    Document doc = builder.parse(file);
+	    //FileReader reader = new FileReader(file);
+	    //InputSource xml_source = new InputSource(reader);
+
+            //parser.parse(xml_source);
+            return doc.getDocumentElement();
+	} catch (Exception e) {
+	    System.err.println("XML Parse Error: "+e.getMessage());
+	    return null;
+	}
+	
+    }
+    private class MyClassLoader 
+    extends ClassLoader {
+
+	private String gliclassesdir = null;
+	private String perldir = null;
+
+	public MyClassLoader(ClassLoader parent) {
+
+	    super(parent);
+	    gliclassesdir = gsdl_home+File.separator+"gli"+File.separator+"classes";
+	    perldir = gsdl_home+File.separator+"perllib";
+	    
+	}
+
+	public URL findResource(String name) {
+	    try {
+		File resource_path = new File(this.gliclassesdir, name);
+		if (resource_path.exists()) {
+		    return new URL("file://"+resource_path.getAbsolutePath());
+		}
+		resource_path = new File(this.perldir, name);
+		if (resource_path.exists()) {
+		    return new URL("file://"+resource_path.getAbsolutePath());
+		}
+	    } catch (Exception e) {};
+	    
+	    
+	    return super.findResource(name);
+	}
+
+
+    }
+
+    private class MacroFile {
+	public static final int CORE = 0;
+	public static final int AUX = 1;
+	
+	private File macro_file = null;
+	private HashMap macros = null;
+
+	public MacroFile(int type) {
+	    String filename = gsdl_home+File.separator+"macros"+File.separator;
+	    if (lang.equals("en")) {
+		filename += "english";
+	    } else if (lang.equals("fr")) {
+		filename += "french";
+	    } else if (lang.equals("es")) {
+		filename += "spanish";
+	    } else if (lang.equals("ru")) {
+		filename += "russian";
+	    } else {
+		System.err.println("Couldn't work out macro file name for lang "+lang);
+		return;
+	    }
+	    if(type == CORE) {
+		filename += ".dm";
+	    } else if (type == AUX) {
+		filename += "2.dm";
+	    } else {
+		System.err.println("Unknown Macro file type: "+type+"!");
+	    }
+
+	    macro_file = new File(filename);
+	    if (!macro_file.exists()) {
+		System.err.println("Macro file "+filename+" doesn't exist!");
+		return;
+	    }
+	    macros = new HashMap();
+	    loadMacroFile();
+	}
+
+	public String get(String key) {
+	    if (!key.startsWith("_") || !key.endsWith("_")) {
+		System.err.println("Error in macro key "+key);
+		return "";
+	    }
+	    String value = (String)macros.get(key.substring(1, key.length()-1));
+	    //System.err.println("proper_key"+key.substring(1, key.length()-1));
+	    if (value == null) {
+		System.err.println("No value found for key "+key+" in macro file "+macro_file.getName());
+		return "";
+	    } 
+	    return value;
+	}
+	private boolean loadMacroFile() {
+	    String current_package = "";
+	    try {
+		InputStream istream = new FileInputStream(macro_file);
+		Reader in_reader = new InputStreamReader(istream, "UTF-8");
+		BufferedReader in = new BufferedReader(in_reader);
+		String macro_str = null;
+		while((macro_str = in.readLine()) != null) {
+		    if (macro_str.startsWith("#")) {
+			// a comment
+			continue;
+		    }
+		    if (macro_str.startsWith("package")) {
+			macro_str = macro_str.substring(8);
+			macro_str = macro_str.trim();
+			if (macro_str.indexOf("#")!=-1) {
+			    macro_str = macro_str.substring(0, macro_str.indexOf("#"));
+			    macro_str = macro_str.trim();
+			}
+			current_package = macro_str;
+			//System.err.println("current package = "+current_package);
+			continue;
+		    }
+		    if (macro_str.startsWith("_")) {
+			if (macro_str.indexOf("#")!=-1) {
+			    //strip off any comments - hopefully there are no # in the actual text
+			    macro_str = macro_str.substring(0, macro_str.indexOf("#"));
+			}
+			macro_str = macro_str.trim();
+			String macro_name = macro_str.substring(1, macro_str.indexOf("_", 1));
+			//System.err.println("macro name = "+macro_name);
+			// find the {
+			int start_bracket = macro_str.indexOf("{");
+			int end_bracket = 0;
+			String line = null;
+			while(!macro_str.endsWith("}") && (line = in.readLine()) != null) {
+			    macro_str += line;
+			    macro_str = macro_str.trim();
+			}
+			if (!macro_str.endsWith("}")) {
+			    System.err.println("can't find the end of macro "+macro_name+", value="+macro_str);
+			    continue;
+			}
+			String macro_value = macro_str.substring(start_bracket+1, macro_str.length()-1);
+			//System.err.println("macro value = "+macro_value);
+			//System.err.println("adding key "+current_package+":"+macro_name+", value = "+macro_value);
+			macros.put(current_package+":"+macro_name, macro_value);
+			continue;
+		    }
+		} //while
+	    } catch (Exception e) {
+		System.err.println("Exception when trying to load macro file "+macro_file+":"+e.getMessage());
+		return false;
+	    }
+	    return true;
+	}
+    }
+
+    public static void main(String []args) {
+	if (args.length != 1) {
+	    System.err.println("Usage: java Dictionary <iso lang code>");
+	    return;
+	}
+	
+	Dictionary dict = new Dictionary(args[0]);
+	System.err.println("glidict::General.OK " +dict.get("glidict::General.OK"));
+	System.err.println("glidict::Autofilter.Order_Tooltip "+ dict.get("glidict::Autofilter.Order_Tooltip"));
+
+	System.err.println("macros _Global:textdefaulttitle_ "+dict.get("coredm::_Global:textdefaulttitle_"));
+	System.err.println("macros _about:textsubcols2_ "+dict.get("coredm::_about:textsubcols2_"));
+	System.err.println("macros _home:textdescrcollector_ "+dict.get("auxdm::_home:textdescrcollector_"));
+	
+	//System.err.println("", dict.get(""));
+	//System.err.println("", dict.get(""));
+
+    }
+}
Index: /trunk/gsdl-documentation/shared/ExternalRef.java
===================================================================
--- /trunk/gsdl-documentation/shared/ExternalRef.java	(revision 13632)
+++ /trunk/gsdl-documentation/shared/ExternalRef.java	(revision 13632)
@@ -0,0 +1,44 @@
+import java.io.InputStream;
+import java.io.FileInputStream;
+
+import org.w3c.dom.Document;
+import javax.xml.parsers.DocumentBuilderFactory;
+import javax.xml.parsers.DocumentBuilder;
+import org.w3c.dom.Document;
+import org.w3c.dom.Element;
+import org.w3c.dom.Node;
+import org.w3c.dom.NodeList;
+
+
+public class ExternalRef{	
+
+	public ExternalRef(){}	
+
+	public String getRef(String file, String lang, String targettype, String id){
+		
+		try{
+		String tfile = file+"_"+lang+".xml";
+		String path = tfile;
+
+		DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
+        DocumentBuilder domBuilder = factory.newDocumentBuilder();
+        InputStream is = new FileInputStream(path);
+        Document doc = domBuilder.parse(is);
+
+		NodeList list = doc.getElementsByTagName(targettype);
+		System.out.println(list.getLength());
+		int i=0;
+		for(i=0; i<list.getLength(); i++){
+			Node node = list.item(i);
+			String id_temp = node.getAttributes().getNamedItem("id").getNodeValue();			
+			if(id_temp.equals(id)) break;
+		}
+		return (++i)+"";
+        
+		}catch(Exception e){
+			System.err.println(e.getMessage());
+			//e.printStackTrace();
+			return "";
+		}
+	}	
+}
