|
a/website/BUGS.html |
|
b/website/BUGS.html |
|
... |
|
... |
| 33 |
|
33 |
|
| 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 |
<h2>Latest (recoll 1.11.2 + xapian 1.0.x)</h2>
|
38 |
<h2>Latest (recoll 1.11.4 + xapian 1.0.x)</h2>
|
| 39 |
<ul>
|
39 |
<ul>
|
| 40 |
|
40 |
|
| 41 |
<li>Performing a full index with release 1.11, over a version
|
41 |
<li>Performing a full index with release 1.11, over a version
|
| 42 |
created with a much older recoll release may sometimes end
|
42 |
created with a much older recoll release may sometimes end
|
| 43 |
with an error saying "backend doesn't implement metadata".
|
43 |
with an error saying "backend doesn't implement metadata".
|
|
... |
|
... |
| 113 |
the database). Don't know the reason. Only idea I have is problem with
|
113 |
the database). Don't know the reason. Only idea I have is problem with
|
| 114 |
exception handling (recoll catches an exception while trying the
|
114 |
exception handling (recoll catches an exception while trying the
|
| 115 |
yet inexistant db).</li>
|
115 |
yet inexistant db).</li>
|
| 116 |
</ul>
|
116 |
</ul>
|
| 117 |
|
117 |
|
| 118 |
<h2>1.11.1</h2>
|
118 |
<h2><a name="b_1_11_1">1.11.1</a></h2>
|
| 119 |
<ul>
|
119 |
<ul>
|
| 120 |
<li>Unicode space characters like
|
120 |
<li>Unicode space characters like
|
| 121 |
<em>0x3000, Ideographic space</em>
|
121 |
<em>0x3000, Ideographic space</em>
|
| 122 |
where not detected inside user entries like the main
|
122 |
where not detected inside user entries like the main
|
| 123 |
interface search entry. Badly parsed searches would retrieve no
|
123 |
interface search entry. Badly parsed searches would retrieve no
|
| 124 |
results, when the same search entered with ascii space characters
|
124 |
results, when the same search entered with ascii space characters
|
| 125 |
would have succeeded.</li>
|
125 |
would have succeeded.</li>
|
| 126 |
<li>Spaces were inserted inside CJK strings when building
|
126 |
<li>Spaces were inserted inside CJK strings when building
|
| 127 |
abstracts for the result list.</li>
|
127 |
abstracts for the result list.</li>
|
|
|
128 |
<li>Accent removal should not be performed for Japanese.</li>
|
|
|
129 |
<li>When using the query language, an OR part with more than
|
|
|
130 |
two terms will swallow preceding AND terms, one for each
|
|
|
131 |
additional OR. Ex: (champagne ext:odt OR ext:sxw OR ext:lyx)
|
|
|
132 |
will be interpreted as
|
|
|
133 |
"champagne OR ext:odt OR ext:sxw OR ext:lyx"
|
|
|
134 |
instead of the correct
|
|
|
135 |
"champagne AND (ext:odt OR ext:sxw OR ext:lyx)"
|
|
|
136 |
Workaround until the fix is issued: add non-existing terms
|
|
|
137 |
before the OR part and check the resulting query:
|
|
|
138 |
"champagne bogusxyztv ext:odt OR ext:sxw OR ext:lyx"
|
|
|
139 |
</li>
|
| 128 |
</ul>
|
140 |
</ul>
|
| 129 |
|
141 |
|
| 130 |
<h2>1.10.6</h2>
|
142 |
<h2>1.10.6</h2>
|
| 131 |
<ul>
|
143 |
<ul>
|
| 132 |
<li> If the locale is not utf-8, non-ascii command line
|
144 |
<li> If the locale is not utf-8, non-ascii command line
|