doc

website/download.html

@@ -293,8 +293,11 @@ packages if you want use the source rpms.</p>
 <h3>Fedora</h3>
 
 <p>Recoll is present in the standard Fedora package repositories starting from
-F-12. The new versions are tracked quite closely, so I don't build the rpms any
-more (email me if you need one).</p>
+  F-12. The new versions are usually tracked quite closely, but
+  1.19.14p2 is not there yet, so here are some packages
+  for <a href="fedora20">Fedora 20</a> and <a href="fedora21">Fedora
+  21</a>. There are only x86_64 binaries for now, use the source rpm
+  for other archs.</p>
 
 <h3>OpenSUSE</h3>
 

website/features.html

@@ -160,12 +160,14 @@
 
       <ul>
         <li><span class="application">pdf</span> with the <span class=
-        "command">pdftotext</span> command, which used to be installed
-        as part of <a href="http://www.foolabs.com/xpdf/">xpdf</a> but
-        is nowadays more often found with 
+        "command">pdftotext</span> command, which comes with 
           <a href="http://poppler.freedesktop.org/">poppler</a>,
-          depending on your distribution (the package name is quite
-          often <tt>poppler-utils</tt>).</li>
+          (the package name is quite
+          often <tt>poppler-utils</tt>). 
+          <em>Note: the older <span class="command">pdftotext</span> command
+            which comes with <span class="application">xpdf</span> is
+            not compatible with <span class="application">
+              Recoll</span></em>.</li> 
 
         <li><span class="application">msword</span> with <a href=
         "http://www.winfield.demon.nl/">antiword</a>.  It is also useful to

website/filters/filters.html

@@ -76,12 +76,26 @@
       <p>However, if you are running a Recoll version older than 1.17,
         you should really upgrade.</p>
 
+      <h2>Attachments to PDF documents (1.20 and older)</h2>
+
+      <p>A new <a href="rclmpdf">rclmpdf</a> filter for processing
+        PDF files with attachments. This replaces the old <b>rclpdf</b>
+        filter. You need to add it to ~/.recoll/mimeconf until it is
+        made standard (this is still a bit experimental, and a big
+        change from the previous filter):
+        <pre><tt>
+        [index]
+        application/pdf = execm rclmpdf
+        </tt></pre>
+        Note the <tt>execm</tt> instead of <tt>exec</tt>. </p>  
+
       <h2><a name="soff1">Open/Libre-Office documents (1.19 and older)</a></h2>
 
       <p><a href="rclsoff">rclsoff</a>: the previous version did not
         produce white space between input tab-separated words, leading
         to search failures.</p>
 
+
       <h2>Purple logs (1.20 and older)</h2>
 
       <p>New <a href="rclpurple">rclpurple</a> filter for Pidging and

website/index.html.en

@@ -52,7 +52,8 @@
           display an even quicker text preview.</li>
         <li>The software is free, open source,
 	  and licensed under the GPL.</li>
-        <li><a href="features.html">Detailed features</a>.</li>  
+        <li><a href="features.html">Detailed features</a> and
+          application requirements for supported document types.</li>  
       </ul>
 
       <p>The current <span class="application">Recoll</span> version is
@@ -94,6 +95,17 @@
       <div class="news">
       
       <dl>
+        <dt>2014-11-09</dt> <dd>If you are still running anything
+          older than 1.19.14p2, <span class="important">YOU SHOULD
+          UPGRADE</span>. In
+          particular, <a href="release-1.19.html#rodb">this index
+            corruption issue</a> leading to repeated reindexing of
+            documents, and possibly query problems too, can be pretty
+          ennoying.<br/> 
+          GOTO <a href="download.html">download</a> and
+          install 1.19.14p2 or 1.20. <em>Reset your index after
+            upgrading (rm -rf ~/.recoll/xapiandb)</em>.</dd>
+
         <dt>2014-07-28</dt> <dd>A nice new application to complement
           Recoll: <a href="https://github.com/pidlug/recollfs">recollfs</a>
           implements a Fuse filesystem where Recoll queries are

website/release-1.19.html

@@ -34,15 +34,17 @@ be turned on <em>only</em> by editing recoll.conf (<a
 href="usermanual/usermanual.html#RCL.INDEXING.CONFIG.SENS">see the manual</a>).
 If you do so, you must then reset the index.</p>
 
-<p>Always reset the index if you do not know by which version it was created
-(you're not sure it's 1.18). The simplest way to do this is to quit all Recoll
-programs and just delete the index directory (<span
-class="literal">rm -rf ~/.recoll/xapiandb</span>), then start
-<code>recoll</code> or <code>recollindex</code>. <br>
-<span class="literal">recollindex -z</span>  will do the same in most, but
-not all, cases. It's better to use the <tt>rm</tt> method, which will also
-ensure that no debris from older releases remain (e.g.: old stemming files
-which are not used any more).</p>
+<p>To be safe, always reset the index when upgrading to 1.19. There
+  was a <a href="#rodb">persistent index corruption issue</a> in 1.18
+  and earlier versions.
+  The simplest way to do this is to quit all Recoll
+  programs and just delete the index directory (
+  <span class="literal">rm -rf ~/.recoll/xapiandb</span>), then start
+  <code>recoll</code> or <code>recollindex</code>. <br>
+  <span class="literal">recollindex -z</span>  will do the same in most, but
+  not all, cases. It's better to use the <tt>rm</tt> method, which will also
+  ensure that no debris from older releases remain (e.g.: old stemming files
+  which are not used any more).</p>
 
 <p>Installing 1.19 over an 1.18 index will force a lot of reindexing anyway
 because Recoll switched to using <i>st_ctime</i> instead of <i>st_mtime</i> to
@@ -74,12 +76,15 @@ Configuration</em> menu.</p>
   <li>1.19.14 fixes relatively minor but ennoying issues in
     indexing, plus a few other glitches:
     <ul>
-      <li>The use of a separate readonly Database object for querying
-        the index while indexing would trigger Xapian errors, (bad
-        block reads), and subsequent up-to-date check failures
-        (leading to unnecessary reindexing). The jury is out as to the
-        cause, but using the same object for reading and writing seems
-        to eliminate the problem.</li>
+      <li id="rodb" class="important">The use of a separate readonly
+        Database object 
+        for querying the index while indexing would trigger Xapian
+        errors, (bad block reads), and subsequent up-to-date check
+        failures (leading to unnecessary reindexing). The jury is out
+        as to the cause, but using the same object for reading and
+        writing seems to eliminate the problem. This is linked to
+        a <a href="http://trac.xapian.org/ticket/645">Xapian
+        ticket</a>.</li>
       <li>An unnecessary log message in the child process between
         forking and executing the filter could block on a mutex, and
         lead to a 20 mn timeout for the affected father process thread