#Strings for translation:
These need to be translated into French, Spanish, Russian, except where indicated.

bibtext-e._text1_:Apart from the standard plugins, this collection uses <i>BibTexPlugin</i>, 
which processes references in the BibTeX format (well known to computer 
scientists). Two options have been set for BibTexPlugin: 
<i>-OIDtype assigned -OIDmetadata Number</i>. This means the metadata 
element \"Number\" will be used as the record identifier, instead of 
Greenstone's default hash identifiers. These options are available for 
all plugins.\n

bibtext-e._text2_:This groups 200 documents together into a single archive file. 
bibtext-e._text3_:The <i>buildtype</i> option shows that the default search engine <i>mgpp</i> is
used. The <i>indexes</i> line specifies indexes for \"text\", and \"metadata\". In this case, \"text\" will be the original BibTeX record. \"metadata\" is a special keyword signifying that an index should be built for any metadata item found in the collection. 

bibtex-3._text4_:An additional keyword, \"allfields\", could also be used in the <i>indexers</i> line, specifying that combined searching over all indexes should be available. 
<p>
The <i>levels</i> lines specifies only document level, as bibliographic records don't have internal structure.

#russian only
bibtex-e._text5_:Fielded searching, with a form-based interface, is selected by <i>format SearchTypes \"form,plain\"
</i> in the configuration file. In fact, a plain textual full-text search
index is included in this collection as well (since <i>form</i> comes first, 
it is the default interface; you reach the <i>plain</i> search through 
the <i>Preferences</i> page).\n

bibtex-supp-e._text1_:The \"documented-examples/\" parts of the collection names are necessary 
because these collections reside in the \"documented-examples\" collection 
group subfolder in the collect directory.\n

wrdpdf-e._text1_:If you encounter these problems, you
can either remove the offending documents from your collection, or try using
some of the advanced plugin options to process the documents in different ways.
For more information, see the Enhanced PDf and Word tutorials on the  
<a href=\'http://wiki.greenstone.org/wiki/index.php/Tutorial_exercises\'>Greenstone wiki</a>.

isis-e._text1_:These databases have several files, but ISISPlugin uses just three: CDS.fdt (where CDS is the name of the database), containing the field names used in the database, CDF.xrf (a cross-reference file), and CDS.mst, containing the actual records. Whenever ISISPlugin encounters an \".mst\" file, it looks for the corresponding \".fdt\" and \".xrf\" files.
isis-e._text1_ [l=fr] Ces bases de données ont plusieurs fichiers, mais ISISPlugin en utilise seulement deux: CDS.fdt (où CDS est le nom de la base de données) contenant les noms de champ utilisés dans la base de données, et CDS.mst qui contient les enregistrements. A chaque fois que ISISPlugin rencontre un fichier \".mst\", il cherche le fichier \".fdt\" correspondant. 
isis-e._text1_ [l=es] Estas bases de datos contienen varios archivos, pero ISISPlugin solo utiliza dos: CDS.fdt (donde CDS es el nombre de la base de datos), el cual contiene los nombres de los campos usados en la base de datos, y CDS.mst, el cual contiene los registros. Cada vez que ISISPlugin encuentra un archivo \".mst\", busca el archivo \".fdt\" correspondiente.
isis-e._text1_ [l=ru] Эти базы данных состоят из нескольких файлов, но плагин ISISPlugin использует только два: CDS.fdt , (где CDS -- имя базы данных ), содержащий имена полей, используемых в базе данных, и CDS.mst, содержащий фактические записи. Всякий раз, когда ISISPlugin сталкивается с файлом \".mst\" он ищет для него соответствующий файл \".fdt\".

authen-e._text1_:The <a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>collection
configuration file</a> is exactly the same as for the original demo collection apart from the authentication directives, one plugin option (and this description).
authen-e._text1_[l=fr] Ce <a href=\"_httpcollection_/etc/collect.cfg\"
target=collect.cfg>fichier de configuration de collection</a> est
exactement le même que celui de la collection de démonstration originale
sauf pour les directives d'authentification (et cette description).
authen-e._text1_[l=es] El <a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>archivo de configuración</a> es exactamente el mismo que el de la demo original salvo las directivas para la autenticación (y su descripción).
authen-e._text1_[l=ru]<a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>Файл конфигурации коллекции</a> точно такой же как и в оригинальной демо коллекции кроме директив аутентификации (и данного описания).

authen-e._text2_:In this case, we have used the <i>-OIDtype dirname</i> option to HTMLPlugin,
which specifies that directory names should be used as identifiers. This works 
for collections where each document is in a separate directory. We have used 
this option to ensure that identifiers remain the same across different 
platforms (which may not be the case for HASH identifiers), as we need to 
specify identifiers here for the authentication directives.




#####################
The entire description (and collection meta)  needs translating into chinese and arabic if possible for all collections.

pagedimg-e, style-e, wiki-e have no translations yet, so entire thing needs to be done for fr, es, ru.

the two strings in the top level (group) etc/collect.cfg also need translating.