Changeset 11767 for trunk/gsdl/macros/english.dm

Timestamp:

2006-05-03T16:09:01+12:00 (18 years ago)

Author:

kjdon

Message:

added extra stuff for search help, removed \n from doc buttons, changed the mgpp and lucene plain search text bits

File:

• trunk/gsdl/macros/english.dm (modified) (11 diffs)

trunk/gsdl/macros/english.dm

@@ -141 +141 @@
 _labelBrwse_ {Browse}
 _labelCollage_ {Collage}
-_labelbrows_ {Browse}
 _labelPeople_ {People A-Z}
 _labelAcronym_ {Acronyms}
@@ -270 +269 @@
 _textCONTINUE_ {CONTINUE?}
 
-_textEXPANDTEXT_ {EXPAND\nTEXT}
-
-_textCONTRACTCONTENTS_ {CONTRACT\nCONTENTS}
+_textEXPANDTEXT_ {EXPAND TEXT}
+
+_textCONTRACTCONTENTS_ {CONTRACT CONTENTS}
 
 _textDETACH_ {DETACH}
 
-_textEXPANDCONTENTS_ {EXPAND\nCONTENTS}
-
-_textCONTRACT_ {CONTRACT\nTEXT}
-
-_textHIGHLIGHT_ {HIGH-\nLIGHTING}
-
-_textNOHIGHLIGHT_ {NO HIGH-\nLIGHTING}
+_textEXPANDCONTENTS_ {EXPAND CONTENTS}
+
+_textCONTRACT_ {CONTRACT TEXT}
+
+_textHIGHLIGHT_ {HIGHLIGHTING}
+
+_textNOHIGHLIGHT_ {NO HIGHLIGHTING}
 
 
@@ -352 +351 @@
 _textadvancedsearch_ {Search _indexselection_ _If_(_jselection_,of _jselection_ )_If_(_gselection_,at _gselection_ level )_If_(_nselection_,in _nselection_ language )using _querytypeselection_ query}
 
-_textformsimplesearch_ {Search _If_(_jselection_,_jselection_ )_If_(_gformselection_,at _gformselection_ level )_If_(_nselection_,in _nselection_ language )for _formquerytypeselection_ of}
-
-_textformadvancedsearch_ {Search _If_(_jselection_,_jselection_ )_If_(_gformselection_,at _gformselection_ level )_If_(_nselection_,in _nselection_ language )and display results in _formquerytypeselection_ order}
+_textadvancedmgppsearch_ {Search _indexselection_ _If_(_jselection_,of _jselection_ )_If_(_gselection_,at _gselection_ level )_If_(_nselection_,in _nselection_ language ) and display results in _formquerytypeadvancedselection_ order}
+
+_textadvancedlucenesearch_ {Search _indexselection_ _If_(_jselection_,of _jselection_ )_If_(_gselection_,at _gselection_ level )_If_(_nselection_,in _nselection_ language ) for}
+
+_textformsimplesearch_ {Search _If_(_jselection_,_jselection_ )_If_(_gformselection_,at _gformselection_ level )_If_(_nselection_,in _nselection_ language )for _formquerytypesimpleselection_ of}
+
+_textformadvancedsearch_ {Search _If_(_jselection_,_jselection_ )_If_(_gformselection_,at _gformselection_ level )_If_(_nselection_,in _nselection_ language )and display results in _formquerytypeadvancedselection_ order}
 
 
@@ -665 +668 @@
 
 <p>Below the title or front-cover photograph are some buttons. Click on
-<i>expand text</i> to expand out the whole text of the current section, or
+<i>_document:textEXPANDTEXT_</i> to expand out the whole text of the current section, or
 book. If the document is large, this could take a long time and use a lot
-of memory! Click on <i>expand contents</i> to expand out the whole table of
+of memory! Click on <i>_document:textEXPANDCONTENTS_</i> to expand out the whole table of
 contents so that you can see the titles of all chapters and
-subsections. Click on <i>detach</i> to make a new browser window for this
+subsections. Click on <i>_document:textDETACH_</i> to make a new browser window for this
 document. (This is useful if you want to compare documents, or read two at
 once.) Finally, when you do a search the words you search for are
-highlighted. Click on <i>no highlighting</i> to remove highlighting.</p>
+highlighted. Click on <i>_document:textNOHIGHLIGHT_</i> to remove highlighting.</p>
 }
 
@@ -706 +709 @@
 <p>A maximum of 100 is imposed on the number of
   documents returned.  You can change this number by clicking the
-  <i>preferences</i> button at the top of the page.<p>
+  <i>_Global:linktextPREFERENCES_</i> button at the top of the page.<p>
 }
 
@@ -724 +727 @@
 }
 
+_texthelpmgppsearching_ {
+For collections built with MGPP a few other options are available. 
+
+<ul>
+<li>A <b>*</b> at the end of a query term  matches all words <b>starting with</b> that word, e.g. <b>comput*</b> matches all words starting with <b>comput</b>.
+<li><b>/x</b> can be used to give higher weight to one or more of the query terms, eg <b>computer/10 science</b> gives computer 10 times more weight than science when ranking documents.
+</ul>
+}
+
+_texthelplucenesearching_ {
+For collections built with Lucene a few other options are available. 
+
+<ul>
+<li><b>?</b> can be used as a wildcard in place of a single letter. For example, <b>b?t</b> will match  <b>bet</b>, <b>bit</b> and <b>bat</b> etc.
+<li><b>*</b> can be used as a wildcard in place of multiple letters. For example, <b>comput*</b> matches all words starting with <b>comput</b>.
+</ul>
+Both of these wildcards can be used in the middle of a term, or at the end. They cannot be used at the start of a search term.
+}
+
 _texthelpquerytypetitle_ {Query type}
 _texthelpquerytype_ {
@@ -731 +753 @@
   <li>Queries for <b>all</b> of 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, in alphabetical
-      order.<p>
+      Documents that satisfy the query are displayed, in build order.
+<p>
 
   <li>Queries for <b>some</b> of the words.  Just list some terms that are
@@ -752 +774 @@
 }
 
+_texthelpadvancedsearchtitle_ {Advanced searching}
+
+_texthelpadvancedsearch_ {
+<p>If you have selected advanced query type (in preferences) you have slightly different search options. _selectadvancedsearch_
+}
+
+_texthelpadvsearchmg_ {
+Advanced searching in MG collections gives you two options, ranked and boolean.
+A <b>ranked</b> search is exactly the same as the <b>some</b> search descibed in <a href="\#query-type">_texthelpquerytypetitle_</a>.
+<p>_texthelpbooleansearch_
+}
+
+_texthelpbooleansearch_ {
+A <b>boolean</b> search allows you to combine terms
+using & (for "and"), | (for "or"), and ! (for "not"), using parentheses for grouping if desired. The default operator is | (for "or").
+<p>
+For example, <b>snail & farming</b> will match documents which contain both <b>snail</b> AND <b>farming</b>, whereas <b>snail | farming</b> will match documents that contain either <b>snail</b> OR <b>farming</b>.
+<b>snail !farming</b> will match documents that contain <b>snail</b> AND DO NOT contain <b>farming</b>.
+<p>
+More precise queries can be specified using combinations of operators and parentheses. For example, <b>(sheep | cattle) & (farm | station)</b>, or <b>sheep | cattle | goat !pig</b>.
+}
+
+_texthelpadvsearchmgpp_ {
+Advanced searches in MGPP collections use boolean operators. _texthelpbooleansearch_
+<p>The results can be displayed in <b>ranked</b> order, as described for the <b>some</b> search in <a href="\#query-type">_texthelpquerytypetitle_</a>, or in "build" order. This is the order that documents were processed during the creation of the collection.
+<p>
+Further operators include <b>NEARx</b> and <b>WITHINx</b>.
+NEARx is used to specify the maximum distance apart (x words) two query
+terms must be for a document to match. 
+WITHINx specifies that the second term must occur within x words <i>after</i> the first term. This is similar to NEAR but the order is important. The default distance is 20.
+}
+
+_texthelpadvsearchlucene_ {
+Advanced searches in Lucene collections use boolean operators. _texthelpbooleansearch_
+}
 _textdatesearch_ {Searching with Dates}
 
@@ -795 +852 @@
 
 _texthelppreferences_ {
-<p>When you click the <i>preferences</i> button at the top of the page you will
+<p>When you click the <i>_Global:linktextPREFERENCES_</i> button at the top of the page you will
 be able to change some features of the interface to suit your own requirements.
 }
@@ -836 +893 @@
 _texthelpsearchprefstitle_ {Search preferences}
 _texthelpsearchprefs_ {
+<p>You can switch to an "advanced" query mode which allows you to combine terms
+using & (for "and"), | (for "or"), and ! (for "not"), using parentheses for grouping if desired. This allows you to specify more precise
+queries. 
+<p> It is possible to get a large query box, so that you can
+easily do paragraph-sized searching. It is surprisingly quick to search for
+large amounts of text.
 <p>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.  It is possible to get a large query box, so that you can
-easily do paragraph-sized searching. It is surprisingly quick to search for
-large amounts of text.
+word endings or not.  
 
 <p>For example, if the buttons <i>ignore case differences</i> and
@@ -853 +914 @@
       "builds").
 
-<p>You can switch to an "advanced" query mode which allows you to combine terms
-using AND (&), OR (|), and NOT (!). This allows you to specify more precise
-queries. You can turn the search history feature, which shows you your last few
+<p>You can turn the search history feature, which shows you your last few
 queries.  This makes it easy to repeat slightly modified versions of previous
-queries. Finally, you can control the number of hits returned, and the
+queries. 
+<p>Finally, you can control the number of hits returned, and the
 number presented on each screenful.
 }