Changeset 12877
- Timestamp:
- 2006-09-27T17:27:47+12:00 (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gsdl/macros/english.dm
r12789 r12877 409 409 _textstem_ {ignore word endings} 410 410 _textnostem_ {whole word must match} 411 _textaccentdiffs_ {Accent differences:} 412 _textignoreaccents_ {ignore accents} 413 _textmatchaccents_ {accents must match} 414 411 415 _textprefop_ {Return up to _maxdocoption_ hits with _hitsperpageoption_ hits per page.} 412 416 _textextlink_ {Access to external Web pages:} … … 429 433 <br>} 430 434 431 _textsearchtype_ { Search type:}432 _textformsearchtype_ {f ormwith _formnumfieldoption_ fields}433 _textplainsearchtype_ { plainwith _boxsizeoption_ query box}434 _textregularbox_ { regular}435 _textsearchtype_ {Query style:} 436 _textformsearchtype_ {fielded with _formnumfieldoption_ fields} 437 _textplainsearchtype_ {normal with _boxsizeoption_ query box} 438 _textregularbox_ {single line} 435 439 _textlargebox_ {large} 436 440 … … 552 556 _texthelpquerytermstitle_ {Search terms} 553 557 _texthelpqueryterms_ { 554 <p>Whatever you type into the query box is interpreted as a list of words 555 called "search terms." Each term contains nothing but alphabetic characters 556 and digits. Terms are separated by white space. If any other characters such 558 <p>Whatever you type into the query box is interpreted as a list of words or phrases 559 called "search terms." A term is a single word containing only letters and digits, or a phrase consisting of a sequence of words enclosed in double quotes ("..."). Terms are separated by white space. If any other characters such 557 560 as punctuation appear, they serve to separate terms just as though they were 558 561 spaces. And then they are ignored. You can't search for words that include … … 597 600 likely to appear in the documents you are looking for. Documents are 598 601 displayed in order of how closely they match the query. When determining 599 600 602 the degree of match, 601 603 602 604 <p><ul> 603 <li> the more search term s a document contains, the closer it matches;604 <li> rare termsare more important than common ones;605 <li> the more search term occurrences a document contains, the closer it matches; 606 <li> terms which are rare in the collection as a whole are more important than common ones; 605 607 <li> short documents match better than long ones. 606 608 </ul> … … 612 614 } 613 615 614 _texthelpadvancedsearchtitle_ {Advanced searching }616 _texthelpadvancedsearchtitle_ {Advanced searching using the _1_ search engine} 615 617 616 618 _texthelpadvancedsearch_ { … … 650 652 } 651 653 652 _texthelpformsearchtitle_ {F ormsearching}654 _texthelpformsearchtitle_ {Fielded searching} 653 655 654 656 _texthelpformsearch_ { 655 <p>Form searching provides the opportunity to combine searches across fields. For example, search for "Smith" in Title AND "snail farming" in Subject. Each line of the form behaves similarly to a single plain search: boolean operators are only allowed in advanced mode, phrases must be specified using double quotes. The individual lines of the form are combined using AND (for an all search) or OR (for a some search). Terms inside the field are also combined the same way. In advanced mode, you can specify different combinations of AND/OR/NOT between the fields using the drop-down lists, and inside a field you can use boolean operators. 656 } 657 <p>Fielded searching provides the opportunity to combine searches across fields. For example, one can search for "Smith" in Title AND "snail farming" in Subject. In simple query mode, each line of the form behaves like a normal single line search. The individual lines of the form are combined using AND (for an "all" search) or OR (for a "some" search). Terms inside the field are also combined the same way. In advanced mode, you can specify different combinations of AND/OR/NOT between the fields using the drop-down lists, and inside a field you can use boolean operators. 658 } 659 660 _texthelpformstemming_ {The "fold" and "stem" boxes allow you to specify whether the terms inside that field are casefolded or stemmed. These are both switched off by default for advanced form searching.} 657 661 658 662 _textdatesearch_ {Searching with Dates} … … 715 719 a different language if you like. You can also alter the encoding scheme 716 720 used by Greenstone for output to the browser -- the software chooses 717 sensible defaults, but with some browsers better visual results can be used 718 by switching to a different encoding scheme. All collections allow you to 721 sensible defaults, but with some browsers it may be necessary to switch to 722 a different encoding scheme to ensure correct character display. 723 All collections allow you to 719 724 switch from the standard graphical interface format to a textual one. This 720 725 is particularly useful for visually impaired users who use large screen … … 740 745 _texthelpsearchprefstitle_ {Search preferences} 741 746 _texthelpsearchprefs_ { 747 <p>You can switch to an "advanced" query mode which allows you to combine terms 748 using & (for "and"), | (for "or"), and ! (for "not"), using parentheses for 749 grouping if desired. This allows you to specify more precise queries. 742 750 <p>_selectsearchtypeprefs_ 743 <p>You can switch to an "advanced" query mode which allows you to combine terms 744 using & (for "and"), | (for "or"), and ! (for "not"), using parentheses for grouping if desired. This allows you to specify more precise 745 queries. 746 <p>Two pairs of buttons control the kind of text matching in the searches that 747 you make. The first set (labeled "case differences") controls whether upper and 748 lower case must match. The second ("word endings") controls whether to ignore 749 word endings or not. 750 751 <p>For example, if the buttons <i>ignore case differences</i> and 752 <i>ignore word endings</i> are selected, the query<p> 753 <ul><kbd>African building</kbd></ul> 754 <p>will be treated the same as<p> 755 <ul><kbd>africa builds</kbd></ul><p> 756 because the uppercase letter in "African" will be transformed to 757 lowercase, and the suffixes "n" and "ing" will be removed from 758 "African" and "building" respectively (also, "s" would be removed from 759 "builds"). 760 761 <p>You can turn the search history feature, which shows you your last few 751 <p>_selectwordmodificationprefs_ 752 <p>You can turn on the search history feature, which shows you your last few 762 753 queries. This makes it easy to repeat slightly modified versions of previous 763 754 queries. … … 766 757 } 767 758 759 _textcasefoldprefs_ {A pair of buttons controls whether upper and lower case must match when searching. For example, if "_preferences:textignorecase_" is selected, <i>snail farming</i> will be treated the same as <i>Snail Farming</i> and <i>SNAIL FARMING</i>.} 760 _textstemprefs_{A pair of buttons controls whether to ignore word endings or not when searching. For example, if "_preferences:textstem_" is selected, <i>snail farming</i> will be treated the same as <i>snails farm</i> and <i>snail farmer</i>. This currently only works properly for English language text. _selectstemoptionsprefs_} 761 _textaccentfoldprefs_ {A pair of buttons controls whether accented and unaccented letters must match when searching. For example, if "_preferences:textignoreaccents_" is selected, <i>fédération</i> will be treated the same as <i>fedération</i> and <i>federation</i>.} 762 763 _textstemoptionsprefs_ {It may be more convenient and precise to use the search term truncation facility described above in "_texthelpquerytermstitle_".} 764 768 765 _textsearchtypeprefsplain_ {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.} 769 766 770 _textsearchtypeprefsform_ {You can change the number of fields shown in the form.}771 772 _textsearchtypeprefsboth_ {You can switch the search type of the collection between " plain" search, and "form" search.767 _textsearchtypeprefsform_ {You can change the number of fields shown in the search form.} 768 769 _textsearchtypeprefsboth_ {You can switch the search type of the collection between "normal" search, and "fielded" search. 773 770 <ul> 774 <li> Plainsearch provides a single query box. _textsearchtypeprefsplain_</li>775 <li>F orm search provides a number of query boxes, each querying a different field of the index. This enables fielded searching. _textsearchtypeprefsform_ </li>771 <li>Normal search provides a single query box. _textsearchtypeprefsplain_</li> 772 <li>Fielded search provides a number of query boxes, each querying a different field of the index. This enables searching over different fields at once. _textsearchtypeprefsform_ </li> 776 773 </ul> 777 774 } … … 786 783 _texthelpscope_ { 787 784 <p> 788 In most collections you can choosedifferent indexes to search. For example, there might785 In most collections you are given a choice of different indexes to search. For example, there might 789 786 be author or title indexes. Or there might be chapter or paragraph indexes. Generally, 790 787 the full matching document is returned regardless of which index you search.
Note:
See TracChangeset
for help on using the changeset viewer.