|
a/website/BUGS.txt |
|
b/website/BUGS.txt |
|
... |
|
... |
| 3 |
Bugs that are listed in an older version section are supposedly fixed in
|
3 |
Bugs that are listed in an older version section are supposedly fixed in
|
| 4 |
later versions. Bugs listed in the topmost section may also exist in older
|
4 |
later versions. Bugs listed in the topmost section may also exist in older
|
| 5 |
versions.
|
5 |
versions.
|
| 6 |
|
6 |
|
| 7 |
Latest (1.7.5):
|
7 |
Latest (1.7.5):
|
|
|
8 |
- Debian and Ubuntu: the rclsoff Openoffice filter doesn't work,
|
|
|
9 |
because of an incorrect shell syntax (understood by bash but not sh). To
|
|
|
10 |
fix, you edit /usr[/local]/share/recoll/filters/rclsoff and can change
|
|
|
11 |
the line:
|
|
|
12 |
trap cleanup EXIT SIGHUP SIGQUIT SIGINT SIGTERM
|
|
|
13 |
into:
|
|
|
14 |
trap cleanup EXIT HUP QUIT INT TERM
|
|
|
15 |
or download the updated filter from the filters page:
|
|
|
16 |
http://www.recoll.org/filters/filters.html
|
|
|
17 |
|
| 8 |
- 1.6/1.7 NEAR crashes: 1.6 has added NEAR searches. Unlike what recoll did
|
18 |
- NEAR crashes: 1.6 has added NEAR searches. Unlike what recoll did
|
| 9 |
with PHRASES, stemming expansion is performed on terms inside NEAR
|
19 |
with PHRASES, stemming expansion is performed on terms inside NEAR
|
| 10 |
clauses (except if prevented by a capitalized entry of course). There is
|
20 |
clauses (except if prevented by a capitalized entry of course). There is
|
| 11 |
a bug in Xapian at least up to 0.9.9, where NEAR does not support
|
21 |
a bug in Xapian at least up to 0.9.9, where NEAR does not support
|
| 12 |
multiple OR subclauses, as would result from a multiple expansion. This
|
22 |
multiple OR subclauses, as would result from a multiple expansion. This
|
| 13 |
manifests itself by a 'not implemented' Xapian exception. Workarounds:
|
23 |
manifests itself by a 'not implemented' Xapian exception. Workarounds:
|
|
... |
|
... |
| 50 |
recollindex program (the recoll index thread doesn't work for creating
|
60 |
recollindex program (the recoll index thread doesn't work for creating
|
| 51 |
the database). Don't know the reason. Only idea I have is problem with
|
61 |
the database). Don't know the reason. Only idea I have is problem with
|
| 52 |
exception handling (recoll catches an exception while trying the
|
62 |
exception handling (recoll catches an exception while trying the
|
| 53 |
yest inexistant db).
|
63 |
yest inexistant db).
|
| 54 |
|
64 |
|
|
|
65 |
***************************************************************************
|
| 55 |
1.7.3
|
66 |
1.7.3
|
| 56 |
- Processing will stop on first error while indexing an mbox file. This
|
67 |
- Processing will stop on first error while indexing an mbox file. This
|
| 57 |
could happen just because an attachment could not be decoded, and can
|
68 |
could happen just because an attachment could not be decoded, and can
|
| 58 |
cause non-indexing of many messages. The most probable cause of error is
|
69 |
cause non-indexing of many messages. The most probable cause of error is
|
| 59 |
a missing filter (ie for ms-word files), so the temporary workaround
|
70 |
a missing filter (ie for ms-word files), so the temporary workaround
|
|
... |
|
... |
| 64 |
1.6.2
|
75 |
1.6.2
|
| 65 |
- Relatively unfrequent issue with message boundary detection in mbox
|
76 |
- Relatively unfrequent issue with message boundary detection in mbox
|
| 66 |
files, could cause miscellaneous problems.
|
77 |
files, could cause miscellaneous problems.
|
| 67 |
- Executing an external viewer for a file with single-quotes in the name
|
78 |
- Executing an external viewer for a file with single-quotes in the name
|
| 68 |
would not work.
|
79 |
would not work.
|
| 69 |
***************************************************************************
|
80 |
|
| 70 |
1.5.10
|
81 |
1.5.10
|
| 71 |
- If a defaultcharset was set in the configuration file for a subdirectory,
|
82 |
- If a defaultcharset was set in the configuration file for a subdirectory,
|
| 72 |
it would stay in effect for all subsequent files/directories (except if
|
83 |
it would stay in effect for all subsequent files/directories (except if
|
| 73 |
explicitely overridden), potentially causing many transcoding errors.
|
84 |
explicitely overridden), potentially causing many transcoding errors.
|
| 74 |
|
85 |
|