yetangitu/recoll
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

change version to future 1.21 + document new query language features

Browse source
This commit is contained in:
Jean-Francois Dockes 2015-02-07 10:29:18 +01:00
parent 13a2428710
commit 1f2776daf6
4 changed files with 34 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

2
src/VERSION
View file

@ -1 +1 @@
1.20.1
1.21.0

39
src/doc/user/usermanual.xml
View file

@ -2966,10 +2966,12 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
<para>An element is composed of an optional field specification,
and a value, separated by a colon (the field separator is the last
colon in the element). Example:
colon in the element). Examples:
<replaceable>Eugenie</replaceable>,
<replaceable>author:balzac</replaceable>,
<replaceable>dc:title:grandet</replaceable> </para>
<replaceable>dc:title:grandet</replaceable>
<replaceable>dc:title:"eugenie grandet"</replaceable>
</para>
<para>The colon, if present, means "contains". Xesam defines other
relations, which are mostly unsupported for now (except in special
@ -2994,9 +2996,13 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
<replaceable>word3</replaceable>. Explicit
parenthesis are <emphasis>not</emphasis> supported.</para>
<para>As of &RCL; 1.21, you can use parentheses to group
elements, which will sometimes make things clearer, and may
allow expressing combinations which would have been difficult
otherwise.</para>
<para>An element preceded by a <literal>-</literal> specifies a
term that should <emphasis>not</emphasis> appear. Pure negative
queries are forbidden.</para>
term that should <emphasis>not</emphasis> appear.</para>
<para>As usual, words inside quotes define a phrase
(the order of words is significant), so that
@ -3004,6 +3010,14 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
<replaceable>title:prejudice title:pride</replaceable>, and is
unlikely to find a result.</para>
<para>Words inside phrases and capitalized words are not
stem-expanded. Wildcards may be used anywhere inside a term.
Specifying a wild-card on the left of a term can produce a very
slow search (or even an incorrect one if the expansion is
truncated because of excessive size). Also see
<link linkend="RCL.SEARCH.WILDCARDS">
More about wildcards</link>.</para>
<para>To save you some typing, recent &RCL; versions (1.20 and later)
interpret a comma-separated list of terms as an AND list inside the
field. Use slash characters ('/') for an OR list. No white space
@ -3014,10 +3028,12 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
<programlisting>author:john/ringo</programlisting> would search for
<literal>john</literal> or <literal>ringo</literal>.</para>
<para>Modifiers can be set on a phrase clause, for example to specify
<para>Modifiers can be set on a double-quote value, for example to specify
a proximity search (unordered). See
<link linkend="RCL.SEARCH.LANG.MODIFIERS">the modifier
section</link>.</para>
section</link>. No space must separate the final
double-quote and the modifiers value, e.g. <replaceable>"two
one"po10</replaceable></para>
<para>&RCL; currently manages the following default fields:</para>
@ -3084,7 +3100,8 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
<listitem><para><literal>dir</literal> for filtering the
results on file location
(Ex: <literal>dir:/home/me/somedir</literal>). <literal>-dir</literal>
(Ex: <literal>dir:/home/me/somedir</literal>).
<literal>-dir</literal>
also works to find results not in the specified directory
(release >= 1.15.8). Tilde expansion will be performed as
usual (except for a bug in versions 1.19 to
@ -3205,14 +3222,6 @@ dir:recoll dir:src -dir:utils -dir:common
</itemizedlist>
<para>Words inside phrases and capitalized words are not
stem-expanded. Wildcards may be used anywhere inside a term.
Specifying a wild-card on the left of a term can produce a very
slow search (or even an incorrect one if the expansion is
truncated because of excessive size). Also see
<link linkend="RCL.SEARCH.WILDCARDS">
More about wildcards</link>.</para>
<para>The document input handlers used while indexing have the
possibility to create other fields with arbitrary names, and
aliases may be defined in the configuration, so that the exact

4
src/qtgui/ssearch_w.cpp
View file

@ -155,10 +155,10 @@ void SSearch::searchTypeChanged(int typ)
"<i>field:term1</i> : 'term1' in field 'field'.<br>\n"
" Standard field names/synonyms:<br>\n"
" title/subject/caption, author/from, recipient/to, filename, ext.<br>\n"
" Pseudo-fields: dir, mime/format, type/rclcat, date.<br>\n"
" Pseudo-fields: dir, mime/format, type/rclcat, date, size.<br>\n"
" Two date interval exemples: 2009-03-01/2009-05-20 2009-03-01/P2M.<br>\n"
"<i>term1 term2 OR term3</i> : term1 AND (term2 OR term3).<br>\n"
" No actual parentheses allowed.<br>\n"
" You can use parentheses to make things clearer.<br>\n"
"<i>\"term1 term2\"</i> : phrase (must occur exactly). Possible modifiers:<br>\n"
"<i>\"term1 term2\"p</i> : unordered proximity search with default distance.<br>\n"
"Use <b>Show Query</b> link when in doubt about result and see manual (&lt;F1>) for more detail.\n"

7
website/features.html
View file

@ -272,9 +272,10 @@ application/x-tar = execm rcltar
unrtf</a>. Please note that up to version 0.21.3,
<span class="command">unrtf</span> mostly does not work with
non western-european character sets. Many serious problems
(crashes and infinite loops) were fixed in unrtf 0.21.8, so
that's really what you want. Building Unrtf from source is
quick and easy.</li>
(crashes with serious security implications and infinite
loops) were fixed in unrtf 0.21.8, so you really want to use
this or a newer release. Building Unrtf from source is quick
and easy.</li>
<li><span class="application">TeX</span> with <span class=
"command">untex</span>. If there is no untex package for