Changeset 11767
- Timestamp:
- 2006-05-03T16:09:01+12:00 (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gsdl/macros/english.dm
r11402 r11767 141 141 _labelBrwse_ {Browse} 142 142 _labelCollage_ {Collage} 143 _labelbrows_ {Browse}144 143 _labelPeople_ {People A-Z} 145 144 _labelAcronym_ {Acronyms} … … 270 269 _textCONTINUE_ {CONTINUE?} 271 270 272 _textEXPANDTEXT_ {EXPAND \nTEXT}273 274 _textCONTRACTCONTENTS_ {CONTRACT \nCONTENTS}271 _textEXPANDTEXT_ {EXPAND TEXT} 272 273 _textCONTRACTCONTENTS_ {CONTRACT CONTENTS} 275 274 276 275 _textDETACH_ {DETACH} 277 276 278 _textEXPANDCONTENTS_ {EXPAND \nCONTENTS}279 280 _textCONTRACT_ {CONTRACT \nTEXT}281 282 _textHIGHLIGHT_ {HIGH -\nLIGHTING}283 284 _textNOHIGHLIGHT_ {NO HIGH -\nLIGHTING}277 _textEXPANDCONTENTS_ {EXPAND CONTENTS} 278 279 _textCONTRACT_ {CONTRACT TEXT} 280 281 _textHIGHLIGHT_ {HIGHLIGHTING} 282 283 _textNOHIGHLIGHT_ {NO HIGHLIGHTING} 285 284 286 285 … … 352 351 _textadvancedsearch_ {Search _indexselection_ _If_(_jselection_,of _jselection_ )_If_(_gselection_,at _gselection_ level )_If_(_nselection_,in _nselection_ language )using _querytypeselection_ query} 353 352 354 _textformsimplesearch_ {Search _If_(_jselection_,_jselection_ )_If_(_gformselection_,at _gformselection_ level )_If_(_nselection_,in _nselection_ language )for _formquerytypeselection_ of} 355 356 _textformadvancedsearch_ {Search _If_(_jselection_,_jselection_ )_If_(_gformselection_,at _gformselection_ level )_If_(_nselection_,in _nselection_ language )and display results in _formquerytypeselection_ order} 353 _textadvancedmgppsearch_ {Search _indexselection_ _If_(_jselection_,of _jselection_ )_If_(_gselection_,at _gselection_ level )_If_(_nselection_,in _nselection_ language ) and display results in _formquerytypeadvancedselection_ order} 354 355 _textadvancedlucenesearch_ {Search _indexselection_ _If_(_jselection_,of _jselection_ )_If_(_gselection_,at _gselection_ level )_If_(_nselection_,in _nselection_ language ) for} 356 357 _textformsimplesearch_ {Search _If_(_jselection_,_jselection_ )_If_(_gformselection_,at _gformselection_ level )_If_(_nselection_,in _nselection_ language )for _formquerytypesimpleselection_ of} 358 359 _textformadvancedsearch_ {Search _If_(_jselection_,_jselection_ )_If_(_gformselection_,at _gformselection_ level )_If_(_nselection_,in _nselection_ language )and display results in _formquerytypeadvancedselection_ order} 357 360 358 361 … … 665 668 666 669 <p>Below the title or front-cover photograph are some buttons. Click on 667 <i> expand text</i> to expand out the whole text of the current section, or670 <i>_document:textEXPANDTEXT_</i> to expand out the whole text of the current section, or 668 671 book. If the document is large, this could take a long time and use a lot 669 of memory! Click on <i> expand contents</i> to expand out the whole table of672 of memory! Click on <i>_document:textEXPANDCONTENTS_</i> to expand out the whole table of 670 673 contents so that you can see the titles of all chapters and 671 subsections. Click on <i> detach</i> to make a new browser window for this674 subsections. Click on <i>_document:textDETACH_</i> to make a new browser window for this 672 675 document. (This is useful if you want to compare documents, or read two at 673 676 once.) Finally, when you do a search the words you search for are 674 highlighted. Click on <i> no highlighting</i> to remove highlighting.</p>677 highlighted. Click on <i>_document:textNOHIGHLIGHT_</i> to remove highlighting.</p> 675 678 } 676 679 … … 706 709 <p>A maximum of 100 is imposed on the number of 707 710 documents returned. You can change this number by clicking the 708 <i> preferences</i> button at the top of the page.<p>711 <i>_Global:linktextPREFERENCES_</i> button at the top of the page.<p> 709 712 } 710 713 … … 724 727 } 725 728 729 _texthelpmgppsearching_ { 730 For collections built with MGPP a few other options are available. 731 732 <ul> 733 <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>. 734 <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. 735 </ul> 736 } 737 738 _texthelplucenesearching_ { 739 For collections built with Lucene a few other options are available. 740 741 <ul> 742 <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. 743 <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>. 744 </ul> 745 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. 746 } 747 726 748 _texthelpquerytypetitle_ {Query type} 727 749 _texthelpquerytype_ { … … 731 753 <li>Queries for <b>all</b> of the words. These look for documents (or 732 754 chapters, or titles) that contain all the words you have specified. 733 Documents that satisfy the query are displayed, in alphabetical734 order.<p>755 Documents that satisfy the query are displayed, in build order. 756 <p> 735 757 736 758 <li>Queries for <b>some</b> of the words. Just list some terms that are … … 752 774 } 753 775 776 _texthelpadvancedsearchtitle_ {Advanced searching} 777 778 _texthelpadvancedsearch_ { 779 <p>If you have selected advanced query type (in preferences) you have slightly different search options. _selectadvancedsearch_ 780 } 781 782 _texthelpadvsearchmg_ { 783 Advanced searching in MG collections gives you two options, ranked and boolean. 784 A <b>ranked</b> search is exactly the same as the <b>some</b> search descibed in <a href="\#query-type">_texthelpquerytypetitle_</a>. 785 <p>_texthelpbooleansearch_ 786 } 787 788 _texthelpbooleansearch_ { 789 A <b>boolean</b> search allows you to combine terms 790 using & (for "and"), | (for "or"), and ! (for "not"), using parentheses for grouping if desired. The default operator is | (for "or"). 791 <p> 792 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>. 793 <b>snail !farming</b> will match documents that contain <b>snail</b> AND DO NOT contain <b>farming</b>. 794 <p> 795 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>. 796 } 797 798 _texthelpadvsearchmgpp_ { 799 Advanced searches in MGPP collections use boolean operators. _texthelpbooleansearch_ 800 <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. 801 <p> 802 Further operators include <b>NEARx</b> and <b>WITHINx</b>. 803 NEARx is used to specify the maximum distance apart (x words) two query 804 terms must be for a document to match. 805 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. 806 } 807 808 _texthelpadvsearchlucene_ { 809 Advanced searches in Lucene collections use boolean operators. _texthelpbooleansearch_ 810 } 754 811 _textdatesearch_ {Searching with Dates} 755 812 … … 795 852 796 853 _texthelppreferences_ { 797 <p>When you click the <i> preferences</i> button at the top of the page you will854 <p>When you click the <i>_Global:linktextPREFERENCES_</i> button at the top of the page you will 798 855 be able to change some features of the interface to suit your own requirements. 799 856 } … … 836 893 _texthelpsearchprefstitle_ {Search preferences} 837 894 _texthelpsearchprefs_ { 895 <p>You can switch to an "advanced" query mode which allows you to combine terms 896 using & (for "and"), | (for "or"), and ! (for "not"), using parentheses for grouping if desired. This allows you to specify more precise 897 queries. 898 <p> It is possible to get a large query box, so that you can 899 easily do paragraph-sized searching. It is surprisingly quick to search for 900 large amounts of text. 838 901 <p>Two pairs of buttons control the kind of text matching in the searches that 839 902 you make. The first set (labeled "case differences") controls whether upper and 840 903 lower case must match. The second ("word endings") controls whether to ignore 841 word endings or not. It is possible to get a large query box, so that you can 842 easily do paragraph-sized searching. It is surprisingly quick to search for 843 large amounts of text. 904 word endings or not. 844 905 845 906 <p>For example, if the buttons <i>ignore case differences</i> and … … 853 914 "builds"). 854 915 855 <p>You can switch to an "advanced" query mode which allows you to combine terms 856 using AND (&), OR (|), and NOT (!). This allows you to specify more precise 857 queries. You can turn the search history feature, which shows you your last few 916 <p>You can turn the search history feature, which shows you your last few 858 917 queries. This makes it easy to repeat slightly modified versions of previous 859 queries. Finally, you can control the number of hits returned, and the 918 queries. 919 <p>Finally, you can control the number of hits returned, and the 860 920 number presented on each screenful. 861 921 }
Note:
See TracChangeset
for help on using the changeset viewer.