--- a/src/doc/user/usermanual.xml
+++ b/src/doc/user/usermanual.xml
@@ -3794,6 +3794,34 @@
         <literal>OR</literal> with <literal>ext</literal> terms for
       example.</para> </note>
 
+      <sect2 id="RCL.SEARCH.LANG.RANGES">
+        <title>Range clauses</title>
+
+        <para>&RCL; 1.24 and later support range clauses on fields which
+        have been configured to support it. No default field uses them
+        currently, so this paragraph is only interesting if you modified
+        the fields configuration and possibly use a custom input
+        handler.</para>
+
+        <para>A range clause looks like one of the following:</para>
+        <programlisting><replaceable>myfield</replaceable>:<replaceable>small</replaceable>..<replaceable>big</replaceable>
+<replaceable>myfield</replaceable>:<replaceable>small</replaceable>..
+<replaceable>myfield</replaceable>:..<replaceable>big</replaceable>
+        </programlisting>
+
+        <para>The nature of the clause is indicated by the two dots
+        <literal>..</literal>, and the effect is to filter the results for
+        which the <replaceable>myfield</replaceable> value is in the
+        possibly open-ended interval.</para>
+
+        <para>See the section about the <link
+        linkend="RCL.INSTALL.CONFIG.FIELDS"> 
+        <filename>fields</filename> configuration file</link> for the
+        details of configuring a field for range searches.</para>
+
+        
+      </sect2>
+      
       <sect2 id="RCL.SEARCH.LANG.MODIFIERS">
         <title>Modifiers</title>
 
@@ -4638,6 +4666,11 @@
       other aspects of fields handling is defined inside the
       <filename>fields</filename> configuration file.</para>
 
+      <para>Some fields may also designated as supporting range queries,
+      meaning that the results may be selected for an interval of its
+      values. See the <link linkend="RCL.INSTALL.CONFIG.FIELDS">
+      configuration section</link> for more details.</para>
+      
       <para>The sequence of events for field processing is as follows:
       <itemizedlist>
         <listitem><para>During indexing, 
@@ -6212,6 +6245,16 @@
             </listitem>
           </varlistentry>
           <varlistentry>
+            <term>[calues]</term>
+            <listitem><para>Fields listed in this section will be stored as
+            &XAP; <literal>values</literal> inside the index. This makes
+            them available for range queries, allowing to filter results
+            according to the field value. This feature currently supports
+            string and integer data. See the comments in the file for more
+            detail</para> 
+            </listitem>
+          </varlistentry>
+          <varlistentry>
             <term>[stored]</term>
             <listitem><para>A field becomes stored (displayable inside
             results) by having its name listed in this section (typically