|
a/website/BUGS.html |
|
b/website/BUGS.html |
|
... |
|
... |
34 |
<p><i>Bugs that are listed in an older version section are
|
34 |
<p><i>Bugs that are listed in an older version section are
|
35 |
supposedly fixed in later versions. Bugs listed in the
|
35 |
supposedly fixed in later versions. Bugs listed in the
|
36 |
topmost section may also exist in older versions.</i></p>
|
36 |
topmost section may also exist in older versions.</i></p>
|
37 |
|
37 |
|
38 |
|
38 |
|
39 |
<h2><a name="b_latest">recoll 1.18.1</a></h2>
|
39 |
<h2><a name="b_latest">recoll 1.18.2</a></h2>
|
40 |
<ul>
|
|
|
41 |
|
|
|
42 |
<li>When using the Firefox plugin, increasing the web cache
|
|
|
43 |
size only has an effect when initially creating the
|
|
|
44 |
cache. If the cache already exists, you need to delete it
|
|
|
45 |
for the new limit to take effect.</li>
|
|
|
46 |
|
|
|
47 |
<li>Sizes for documents bigger than 2 GB were improperly
|
|
|
48 |
displayed.</li>
|
|
|
49 |
|
|
|
50 |
<li>Wildcards expressions sometimes cause false matches
|
|
|
51 |
because of issues in handling errors from fnmatch(). This
|
|
|
52 |
will only occur in an UTF-8 locale where file name
|
|
|
53 |
conversion errors are possible (for old 8bit file
|
|
|
54 |
names).</li>
|
|
|
55 |
|
|
|
56 |
<li>There are sometimes issues with CHM files character
|
|
|
57 |
encoding.</li>
|
|
|
58 |
|
|
|
59 |
<li>Sorting by field 'relevancyrating' was not equivalent to
|
|
|
60 |
natural Xapian ordering.</li>
|
|
|
61 |
|
|
|
62 |
<li>Weird data in filter output text (e.g.: produced by some
|
|
|
63 |
versions of pdftotext) can cause an error which will halt
|
|
|
64 |
the processing of the document, which becomes
|
|
|
65 |
unsearchable. This is a relatively uncommon problem which
|
|
|
66 |
signals itself by a specific error in the indexing log, so
|
|
|
67 |
you can know if you are affected. Look for:
|
|
|
68 |
<tt>xapian add_posting error Empty termnames aren't allowed</tt>
|
|
|
69 |
</li>
|
|
|
70 |
|
|
|
71 |
<li>Raw indexes (not default): diacritics and case expansion
|
|
|
72 |
is not applied to terms containing numbers so that a
|
|
|
73 |
case-insensitive search does not work for them (e.g.:
|
|
|
74 |
searching for ds1820 will not find DS1820).</li>
|
|
|
75 |
|
|
|
76 |
|
|
|
77 |
<li>When no indexing helper applications are actually missing,
|
40 |
<li>When no indexing helper applications are actually missing,
|
78 |
an ennoying popup is shown in the GUI at each end of a batch
|
41 |
an ennoying popup is shown in the GUI at each end of a batch
|
79 |
indexing run (it's supposed to be shown only once).</li>
|
42 |
indexing run (it's supposed to be shown only once).</li>
|
80 |
|
43 |
|
81 |
<li>Category (media, message, etc.) expansion does not work
|
44 |
<li>Category (media, message, etc.) expansion does not work
|
|
... |
|
... |
128 |
startup. This is fixed by removing (back it up just in case)
|
91 |
startup. This is fixed by removing (back it up just in case)
|
129 |
~/.config/Recoll.org/recoll.conf, the QSettings storage for
|
92 |
~/.config/Recoll.org/recoll.conf, the QSettings storage for
|
130 |
recoll.</li>
|
93 |
recoll.</li>
|
131 |
</ul>
|
94 |
</ul>
|
132 |
|
95 |
|
|
|
96 |
|
|
|
97 |
<h2><a name="b_1_18_1">recoll 1.18.1</a></h2>
|
|
|
98 |
<ul>
|
|
|
99 |
|
|
|
100 |
<li>When using the Firefox plugin, increasing the web cache
|
|
|
101 |
size only has an effect when initially creating the
|
|
|
102 |
cache. If the cache already exists, you need to delete it
|
|
|
103 |
for the new limit to take effect.</li>
|
|
|
104 |
|
|
|
105 |
<li>Sizes for documents bigger than 2 GB are improperly
|
|
|
106 |
displayed.</li>
|
|
|
107 |
|
|
|
108 |
<li>Wildcards expressions sometimes cause false matches
|
|
|
109 |
because of issues in handling errors from fnmatch(). This
|
|
|
110 |
will only occur in an UTF-8 locale where file name
|
|
|
111 |
conversion errors are possible (for old 8bit file
|
|
|
112 |
names).</li>
|
|
|
113 |
|
|
|
114 |
<li>CHM files character encoding is sometimes wrongly processed.</li>
|
|
|
115 |
|
|
|
116 |
<li>Sorting by field 'relevancyrating' is not equivalent to
|
|
|
117 |
natural Xapian ordering.</li>
|
|
|
118 |
|
|
|
119 |
<li>Weird data in filter output text (e.g.: produced by some
|
|
|
120 |
versions of pdftotext) can cause an error which will halt
|
|
|
121 |
the processing of the document, which becomes
|
|
|
122 |
unsearchable. This is a relatively uncommon problem which
|
|
|
123 |
signals itself by a specific error in the indexing log, so
|
|
|
124 |
you can know if you are affected. Look for:
|
|
|
125 |
<tt>xapian add_posting error Empty termnames aren't allowed</tt>
|
|
|
126 |
</li>
|
|
|
127 |
|
|
|
128 |
<li>Raw indexes (not default): diacritics and case expansion
|
|
|
129 |
is not applied to terms containing numbers so that a
|
|
|
130 |
case-insensitive search does not work for them (e.g.:
|
|
|
131 |
searching for ds1820 will not find DS1820).</li>
|
|
|
132 |
</ul>
|
133 |
|
133 |
|
134 |
<h2><a name="b_1_18_0">recoll 1.18.0</a></h2>
|
134 |
<h2><a name="b_1_18_0">recoll 1.18.0</a></h2>
|
135 |
<ul>
|
135 |
<ul>
|
136 |
<li>Thumbnails are not found on newer desktops (e.g. Ubuntu
|
136 |
<li>Thumbnails are not found on newer desktops (e.g. Ubuntu
|
137 |
Quantal) because of a change in the freedesktop.org
|
137 |
Quantal) because of a change in the freedesktop.org
|