1 | #Strings for translation:
|
---|
2 | These need to be translated into French, Spanish, Russian, except where indicated.
|
---|
3 |
|
---|
4 | bibtext-e._text1_:Apart from the standard plugins, this collection uses <i>BibTexPlugin</i>,
|
---|
5 | which processes references in the BibTeX format (well known to computer
|
---|
6 | scientists). Two options have been set for BibTexPlugin:
|
---|
7 | <i>-OIDtype assigned -OIDmetadata Number</i>. This means the metadata
|
---|
8 | element \"Number\" will be used as the record identifier, instead of
|
---|
9 | Greenstone's default hash identifiers. These options are available for
|
---|
10 | all plugins.\n
|
---|
11 |
|
---|
12 | bibtext-e._text2_:This groups 200 documents together into a single archive file.
|
---|
13 | bibtext-e._text3_:The <i>buildtype</i> option shows that the default search engine <i>mgpp</i> is
|
---|
14 | 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.
|
---|
15 |
|
---|
16 | 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.
|
---|
17 | <p>
|
---|
18 | The <i>levels</i> lines specifies only document level, as bibliographic records don't have internal structure.
|
---|
19 |
|
---|
20 | #russian only
|
---|
21 | bibtex-e._text5_:Fielded searching, with a form-based interface, is selected by <i>format SearchTypes \"form,plain\"
|
---|
22 | </i> in the configuration file. In fact, a plain textual full-text search
|
---|
23 | index is included in this collection as well (since <i>form</i> comes first,
|
---|
24 | it is the default interface; you reach the <i>plain</i> search through
|
---|
25 | the <i>Preferences</i> page).\n
|
---|
26 |
|
---|
27 | bibtex-supp-e._text1_:The \"documented-examples/\" parts of the collection names are necessary
|
---|
28 | because these collections reside in the \"documented-examples\" collection
|
---|
29 | group subfolder in the collect directory.\n
|
---|
30 |
|
---|
31 | wrdpdf-e._text1_:If you encounter these problems, you
|
---|
32 | can either remove the offending documents from your collection, or try using
|
---|
33 | some of the advanced plugin options to process the documents in different ways.
|
---|
34 | For more information, see the Enhanced PDf and Word tutorials on the
|
---|
35 | <a href=\'http://wiki.greenstone.org/wiki/index.php/Tutorial_exercises\'>Greenstone wiki</a>.
|
---|
36 |
|
---|
37 | # the following string has only changed a little, so have put the original strings hee too.
|
---|
38 | 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.
|
---|
39 | 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.
|
---|
40 | 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.
|
---|
41 | isis-e._text1_ [l=ru] ÐÑО Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
|
---|
42 | ÑПÑÑПÑÑ ÐžÐ· МеÑкПлÑкОÑ
|
---|
43 | ÑайлПв, МП плагОМ ISISPlugin ОÑпПлÑзÑÐµÑ ÑПлÑкП Ўва: CDS.fdt , (гЎе CDS -- ÐžÐŒÑ Ð±Ð°Ð·Ñ ÐŽÐ°ÐœÐœÑÑ
|
---|
44 | ), ÑПЎеÑжаÑОй ОЌеМа пПлей, ОÑпПлÑзÑеЌÑÑ
|
---|
45 | в базе ЎаММÑÑ
|
---|
46 | , О CDS.mst, ÑПЎеÑжаÑОй ÑакÑОÑеÑкОе запОÑО. ÐÑÑкОй Ñаз, кПгЎа ISISPlugin ÑÑалкОваеÑÑÑ Ñ ÑайлПЌ \".mst\" ПМ ОÑÐµÑ ÐŽÐ»Ñ ÐœÐµÐ³ÐŸ ÑППÑвеÑÑÑвÑÑÑОй Ñайл \".fdt\".
|
---|
47 | isis-e._text2_:The <i>-OIDtype incremental</i> plugin option was used to give identifiers
|
---|
48 | that are consistent across different operating systems (which may not happen with HASH identifiers), so that we can link to a document in
|
---|
49 | this description.
|
---|
50 | authen-e._text1_:The <a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>collection
|
---|
51 | configuration file</a> is exactly the same as for the original demo collection apart from the authentication directives, one plugin option (and this description).
|
---|
52 | authen-e._text1_[l=fr] Ce <a href=\"_httpcollection_/etc/collect.cfg\"
|
---|
53 | target=collect.cfg>fichier de configuration de collection</a> est
|
---|
54 | exactement le même que celui de la collection de démonstration originale
|
---|
55 | sauf pour les directives d'authentification (et cette description).
|
---|
56 | 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).
|
---|
57 | authen-e._text1_[l=ru]<a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>Ѐайл кПМÑОгÑÑаÑОО кПллекÑОО</a> ÑПÑМП ÑакПй же как О в ПÑОгОМалÑМПй ЎеЌП кПллекÑОО кÑПЌе ЎОÑекÑОв аÑÑеМÑОÑОкаÑОО (О ЎаММПгП ПпОÑаМОÑ).
|
---|
58 |
|
---|
59 | authen-e._text2_:In this case, we have used the <i>-OIDtype dirname</i> option to HTMLPlugin,
|
---|
60 | which specifies that directory names should be used as identifiers. This works
|
---|
61 | for collections where each document is in a separate directory. We have used
|
---|
62 | this option to ensure that identifiers remain the same across different
|
---|
63 | platforms (which may not be the case for HASH identifiers), as we need to
|
---|
64 | specify identifiers here for the authentication directives.
|
---|
65 |
|
---|
66 | #russian only
|
---|
67 | dld-e._text1_:The DLS collection is fairly complex.
|
---|
68 |
|
---|
69 | dls-e._text2_:this text is part of it
|
---|
70 |
|
---|
71 | marc-e._text1_:The <i>dc.Title</i> classifier is an AZList, while the other two are AZCompactList, which groups items with the same metadata into a bookshelf. The <i>-removesuffix</i> argument for the <i>Title</i> and <i>Creator</i>
|
---|
72 | classifiers removes suffixes from the metadata string (<i>dc.Title</i> and
|
---|
73 | <i>dc.Creator</i> respectively).
|
---|
74 |
|
---|
75 | marc-e._text2_:The <i>VList</i> format statement controls the display of search results and all classifiers. For bookshelves, the number of leaf documents is displayed on the right-hand side. For documents, <i>dc.Title</i> is displayed, along with <i>dc.Creator</i> and <i>dc.Publisher</i>. <i>[sibling:dc.Creator]</i> is used as dc.Creator has multiple values, and specifies that all values be output, not just the first one.
|
---|
76 |
|
---|
77 | marc-e._text3_:Multiple MARC fields may map to a single Dublin Core field.
|
---|
78 | For example, fields 720 (\"Uncontrolled name\"), 100 (\"Personal name\"),
|
---|
79 | 110 (\"Corporate name\") and 111 (\"Meeting name\") all map to
|
---|
80 | <i>dc.Creator</i>. Actual MARC records normally
|
---|
81 | define only one of these fields, and anyway Greenstone allows
|
---|
82 | multi-valued metadata.\n
|
---|
83 | <p>
|
---|
84 | Some mappings are dependent on subfields. For example, MARC field 260 contains
|
---|
85 | information about publication and distribution. Subfields \"c\" (Date of Publication) and \"g\" (Date of manufacture) are mapped to <i>dc.Date</i>, using the following mapping line:
|
---|
86 | <blockquote>
|
---|
87 | 260$c$g -> dc.Date
|
---|
88 | </blockquote>
|
---|
89 |
|
---|
90 | Greenstone also provides a file for mapping MARC to <b>qualified</b> dublin core: <a href=\"_httpprefix_/etc/marc2qdc.txt\" target=marc2qdc>greenstone/etc/marc2qdc.txt</a>. This can be used by the MARC plugin by setting the <i>-metadata_mapping_file</i> option to \"marc2qdc.txt\".
|
---|
91 |
|
---|
92 |
|
---|
93 | #####################
|
---|
94 | The entire description (and collection meta) needs translating into chinese and arabic if possible for all collections.
|
---|
95 |
|
---|
96 | pagedimg-e, style-e, wiki-e have no translations yet, so entire thing needs to be done for fr, es, ru.
|
---|
97 |
|
---|
98 | pagedimg-e has strings in extra.dm that need translating.
|
---|
99 |
|
---|
100 | the two strings in the top level (group) etc/collect.cfg also need translating.
|
---|
101 |
|
---|
102 | In particular to check translations: bibtex-e in russian.
|
---|
103 |
|
---|
104 | collections I have done (I think):
|
---|
105 |
|
---|
106 | authen-e
|
---|
107 | bibtex-e & bibtex-supp-e
|
---|
108 | garish-e
|
---|
109 | image-e
|
---|
110 | isis-e
|
---|
111 | pagedimg-e
|
---|
112 | style-e
|
---|
113 | wiki-e
|
---|
114 | wrdpdf-e
|
---|
115 | marc-e
|
---|
116 |
|
---|
117 | don't send off the others yet!!
|
---|
118 |
|
---|
119 | I haven't checked all colls yet for search meta using _labeltext_.
|
---|
120 | You probably won't have time either...
|
---|
121 |
|
---|
122 |
|
---|
123 | ############################################################
|
---|
124 | Next installment:
|
---|
125 |
|
---|
126 | gsarch-e._text1_:This is a collection of email messages
|
---|
127 | from the Greenstone mailing list archives, from November/December, 2008.
|
---|
128 | gsarch-e._text2_:In this case, there is a file per month per mailing list, and each file contains many email messages.
|
---|
129 | gsarch-e._text3_:The <i>Email</i>
|
---|
130 | plugin splits these into individual documents, and produces <i>Title</i>,
|
---|
131 | <i>Subject</i>, <i>From</i>, <i>FromName</i>, <i>FromAddr</i>,
|
---|
132 | <i>Date</i>, <i>DateText</i>, <i>InReplyTo</i>, and optionally <i>Headers</i>, metadata.
|
---|
133 | gsarch-e._text3_ [l=fr]Le plugin <i>E-mail</i> les éclate en documents individuels et produit les méta-données
|
---|
134 | <i>Title</i>, <i>Subject</i>, <i>Headers</i>, <i>From</i>, <i>FromName</i>, <i>FromAddr</i>, <i>Date</i> et <i>DateText</i>.
|
---|
135 |
|
---|
136 | gsarch-e._text3_ [l=es] El plugin <i>Email</i> los divide en documentos individuales y produce metadatos de <i>TÃtulo, Asunto, Encabezados, Remitente, Nombre del Remitente, Dirección del Remitente, Fecha y Texto de la Fecha (Title, Subject, Headers, From, FromName, FromAddr, Date y DateText</i>, respectivamente).
|
---|
137 | gsarch-e._text3_ [l=ru] ÐлагОМ Ðmail ÑÐ°Ð·Ð±ÐžÐ²Ð°ÐµÑ ÐžÑ
|
---|
138 | Ма ОМЎОвОЎÑалÑÐœÑе ЎПкÑЌеМÑÑ Ðž ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐŒÐµÑаЎаММÑе: <i>ÐазваМОе (Title), ÐÑÐµÐŽÐŒÐµÑ (Subject), ÐагПлПвкО (Headers), ÐÑ (from), ÐÐŒÑ ÐŸÑпÑавОÑÐµÐ»Ñ (FromName), ÐÐŽÑÐµÑ ÐŸÑпÑавОÑÐµÐ»Ñ (FromAddr), ÐаÑа (Date)</i> О <i>DateText</i>.
|
---|
139 | gsarch-e._text4_:Otherwise the node\'s label starts with the
|
---|
140 | <i>Subject</i> which links to the document, then gives <i>FromName</i> metadata, with a link to \"Search by Sender\", followed by the <i>DateText</i>.
|
---|
141 | gsarch-e._text5_:For
|
---|
142 | document nodes the <i>FromName</i>, with a link to \"Search By Sender\", <i>Subject</i> (linked to the document), and <i>DateText</i> metadata is
|
---|
143 | shown.
|
---|
144 | gsarch-e._text6_:Finally, the document text is formatted to show the header fields (<i>FromName</i>, <i>DateText</i>, <i>Subject</i>, <i>InReplyTo</i>), followed by
|
---|
145 | the message text (written as <i>[Text]</i> in the format statement). FromName is linked to a search on that name, while InReplyTo links to the email message that it refers to.
|
---|
146 |
|
---|
147 | collections I have done:
|
---|
148 | gsarch-e
|
---|