1.12.2 release

This commit is contained in:
dockes 2009-10-21 07:15:19 +00:00
parent 22163c49c0
commit e4da5e810c
12 changed files with 1027 additions and 797 deletions

View File

@ -21,9 +21,9 @@
<div class="rightlinks">
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="download.html">Downloads</a></li>
<li><a href="doc.html">Documentation</a></li>
<li><a href="index.html">Home</a></li>
<li><a href="download.html">Downloads</a></li>
<li><a href="doc.html">Documentation</a></li>
</ul>
</div>
@ -32,358 +32,383 @@
<h1>Known bugs in current and older versions</h1>
<p><i>Bugs that are listed in an older version section are
supposedly fixed in later versions. Bugs listed in the
topmost section may also exist in older versions.</i></p>
supposedly fixed in later versions. Bugs listed in the
topmost section may also exist in older versions.</i></p>
<h2><a name="b_latest">Latest (recoll 1.12.0 + xapian 1.0.10)</a></h2>
<h2><a name="b_latest">Latest (recoll 1.12.1 + xapian 1.0.15)</a></h2>
<ul>
<li>To compile the Python interface for recoll 1.12, you need
to edit setup.py and replace "rcldb/pathhash.cpp" with
"utils/fileudi.cpp".</li>
<li>Performing a full index with release 1.11 or later, over a
version created with a much older recoll release may
sometimes end with an error saying "backend doesn't
implement metadata". If this happens, you need to delete
the index directory (typically <em>~/.recoll/xapiandb/</em>)
and restart indexing. For big indexes, removing the
directory preventively may be preferable to avoid losing
time.</li>
<li>Performing a full index with release 1.11 or later, over a
version created with a much older recoll release may
sometimes end with an error saying "backend doesn't
implement metadata". If this happens, you need to delete
the index directory (typically <em>~/.recoll/xapiandb/</em>)
and restart indexing. For big indexes, to avoid losing
time, removing the directory preventively may be preferable .</li>
<li> When Recoll is built with qt 4.4.0, the icons in the
result list are all displayed at the top of the page and
garbled. This appears to be a qt bug, fixed in 4.4.1. Use
either qt 4.3.x or 4.4.1</li>
<li> When Recoll is built with qt 4.4.0, the icons in the
result list are all displayed at the top of the page and
garbled. This appears to be a qt bug, fixed in 4.4.1. Use
either qt 4.3.x or 4.4.1</li>
<li> If the user-chosen result list entry format results in
several paragraphs (in the qt textedit sense), right clicks
will only work inside the first one for each entry.</li>
<li> If the user-chosen result list entry format results in
several paragraphs (in the qt textedit sense), right clicks
will only work inside the first one for each entry.</li>
<li> When a mime type has an external viewer defined, but the
actual file is compressed (ie: xxx.txt.gz), recoll will try
to start the external viewer on the compressed file, which
will not work in most cases.</li>
<li> When a mime type has an external viewer defined, but the
actual file is compressed (ie: xxx.txt.gz), recoll will try
to start the external viewer on the compressed file, which
will not work in most cases.</li>
<li>NEAR expansion errors: recoll performs stemming expansion
inside NEAR clauses (except if prevented by a capitalized
entry). Because of a Xapian bug (at least up to 1.0.10),
NEAR does not support multiple OR subclauses. This manifests
itself by a 'not implemented' Xapian exception or an
explicit error message. Workarounds:
<ul>
<li>Prevent expansion of NEAR terms (possibly except one) by
<li>It seems that the recoll program sometimes segfaults when
exiting after the first execution ?</li>
<li> If you are seeing a delay of a few seconds before the
result list displays for the first query of a recoll
instance, try changing the result list font in the query
preferences. This is not a recoll problem, I don't know the
exact cause (I've seen it happen with "Sans Serif" and go
away with Helvetica or Arial).</li>
<li> Under some versions of KDE (ie: Fedora FC5 KDE
3.5.4-0.5.fc5), there is a problem with the window stacking
order. Opening the "browse" file selection dialog from the
advanced search dialog will stack the latter under the main
window, possibly making it invisible. This is quite probably
a Kwin bug, possibly related to
http://bugs.kde.org/show_bug.cgi?id=79183 or a correction
thereof.</li>
<li>Under Solaris, it is necessary to perform initial
indexing with the recollindex program (the recoll index
thread doesn't work for creating the database). Don't know
the reason. Only idea I have is problem with exception
handling (recoll catches an exception while trying the yet
inexistant db).</li>
<li>The default filter for files in microsoft word format
(application/msword, .doc), antiword, has trouble with some
relatively rare files with a very small text, resulting in the
following error message:
<blockquote>
I'm afraid the text stream of this file is too small to
handle.
</blockquote>
Only small files produced by Microsoft Word on a Mac, or by
OpenOffice will trigger this message. As a workaround, install
wvWare and modify mimeconf to use the rcldoc filter, which
will use vwWare if it is available. This will result in
slower indexing for doc files.</li>
</ul>
<h2><a name="b_1_12_1">1.12.1</a></h2>
<li>Uncatched Xapian exceptions can crash the GUI when a query
is run while the index is being updated.</li>
<li>The result list right-click pop up menu does not appear
when the cursor is inside a table.</li>
<li>Multithreaded access to Xlib can crash the real-time indexer.</li>
<li>A looping filter (ie: rclps trying to index loop.ps) can
keep on running forever and stop the indexing while eating cpu.</li>
<li>Filter subprocesses can sometimes be left around after
indexing is interrupted. Two signals are sometimes necessary
to get recollindex to exit.</li>
<li>Signals SIGUSR1 and SIGUSR2 are not blocked.</li>
<li>Sort does not work on queries started from the command line.</li>
<h2><a name="b_1_12_0">1.12.0</a></h2>
<ul>
<li>To compile the Python interface for recoll 1.12, you need
to edit setup.py and replace "rcldb/pathhash.cpp" with
"utils/fileudi.cpp".</li>
<li>rclman outputs control characters, causing problems with
preview and phrase searches in manual pages.</li>
<li>rcllyx has trouble with 8bit characters in file names.</li>
<li>"recoll -q ..." processes incorrectly second and further
command line arguments.</li>
<li><a name="XapianNearPatch">The</a>
following problem was corrected by Xapian 1.0.11 or
1.0.12, and I can see no reason to use older versions and/or the
patches below. However, they're kept around in case someone
needs them.<br>
NEAR expansion errors: recoll performs stemming expansion inside
NEAR clauses (except if prevented by a capitalized
entry). Because of a Xapian bug (up to 1.0.12 (or 11?)), NEAR
does not support multiple OR subclauses. This manifests itself
by a 'not implemented' Xapian exception or an explicit error
message. Workarounds:
<ul>
<li>Prevent expansion of NEAR terms (possibly except one) by
capitalizing them.
<li>Or apply the following patch to xapian, inside the
<li>Or apply the following patch to xapian, inside the
"api/" directory:<br>
0.x versions:
0.x versions:
<a href="xapian/xapNearDistrib-0.x.patch">
xapian/xapNearDistrib-0.x.patch</a>
<br>
1.0.[0-9]:
xapian/xapNearDistrib-0.x.patch</a>
<br>
1.0.[0-9]:
<a href="xapian/xapNearDistrib-1.0.0_9.patch">
xapian/xapNearDistrib-1.0.0_9.patch</a>
<br>
1.0.10:
xapian/xapNearDistrib-1.0.0_9.patch</a>
<br>
1.0.10:
<a href="xapian/xapNearDistrib-1.0.10.patch">
xapian/xapNearDistrib-1.0.10.patch</a>
<br>
xapian/xapNearDistrib-1.0.10.patch</a>
<br>
or fetch the already patched source from
<a href="xapian/">xapian/</a>
then recompile, and install.
</li>
</ul>
<a href="xapian/">the local xapian/ directory</a>
then recompile, and install.
</li>
</ul>
</li>
I hope that an equivalent fix will make it into xapian at
some point (the current fix is not completely correct but
still handles most useful cases).</li>
<li>It seems that the recoll program sometimes segfaults when
exiting after the first execution ?</li>
<li> If you are seeing a delay of a few seconds before the
result list displays for the first query of a recoll
instance, try changing the result list font in the query
preferences. This is not a recoll problem, I don't know the
exact cause (I've seen it happen with "Sans Serif" and go
away with Helvetica or Arial).</li>
<li> Under some versions of KDE (ie: Fedora FC5 KDE
3.5.4-0.5.fc5), there is a problem with the window stacking
order. Opening the "browse" file selection dialog from the
advanced search dialog will stack the latter under the main
window, possibly making it invisible. This is quite probably
a Kwin bug, possibly related to
http://bugs.kde.org/show_bug.cgi?id=79183 or a correction
thereof.</li>
<li> Under Solaris, it is necessary to perform initial indexing with the
recollindex program (the recoll index thread doesn't work for creating
the database). Don't know the reason. Only idea I have is problem with
exception handling (recoll catches an exception while trying the
yet inexistant db).</li>
<li>The default filter for files in microsoft word format
(application/msword, .doc), antiword, has trouble with some
relatively rare files with a very small text, resulting in the
following error message:
<blockquote>
I'm afraid the text stream of this file is too small to
handle.
</blockquote>
Only small files produced by Microsoft Word on a Mac, or by
OpenOffice will trigger this message. As a workaround, install
wvWare and modify mimeconf to use the rcldoc filter, which
will use vwWare if it is available. This will result in
slower indexing for doc files.</li>
</ul>
<h2><a name="b_1_11_4">1.11.4</a></h2>
<ul>
<li>Possibly harmful bug in strerror_r usage (GNU case).</li>
<li>Incorrect handling of "accents" inside Japanese katakana
text.</li>
<li>Using the "Erase history" command on an empty history
would cause recoll to crash.</li>
<li>Possibly harmful bug in strerror_r usage (GNU case).</li>
<li>Incorrect handling of "accents" inside Japanese katakana
text.</li>
<li>Using the "Erase history" command on an empty history
would cause recoll to crash.</li>
</ul>
<h2><a name="b_1_11_1">1.11.1</a></h2>
<ul>
<li>Unicode space characters like
<em>0x3000,&nbsp;Ideographic&nbsp;space</em>
where not detected inside user entries like the main
interface search entry. Badly parsed searches would retrieve no
results, when the same search entered with ascii space characters
would have succeeded.</li>
<li>Spaces were inserted inside CJK strings when building
abstracts for the result list.</li>
<li>Accent removal should not be performed for Japanese.</li>
<li>When using the query language, an OR part with more than
two terms will swallow preceding AND terms, one for each
additional OR. Ex: (champagne ext:odt OR ext:sxw OR ext:lyx)
will be interpreted as
"champagne OR ext:odt OR ext:sxw OR ext:lyx"
instead of the correct
"champagne AND (ext:odt OR ext:sxw OR ext:lyx)"
Workaround until the fix is issued: add non-existing terms
before the OR part and check the resulting query:
"champagne bogusxyztv ext:odt OR ext:sxw OR ext:lyx"
</li>
<li>The "Copy file name" and "Copy URL" entries of the
right-click menus only copy the data to the X11 primary
selection (use middle-button click to paste). This is
probably a mistake, the data should be copied to the
clipboard too (permitting the use of the "Paste" edit menu
entry or Ctrl+V in the target).</li>
<li>Unicode space characters like
<em>0x3000,&nbsp;Ideographic&nbsp;space</em>
where not detected inside user entries like the main
interface search entry. Badly parsed searches would retrieve no
results, when the same search entered with ascii space characters
would have succeeded.</li>
<li>Spaces were inserted inside CJK strings when building
abstracts for the result list.</li>
<li>Accent removal should not be performed for Japanese.</li>
<li>When using the query language, an OR part with more than
two terms will swallow preceding AND terms, one for each
additional OR. Ex: (champagne ext:odt OR ext:sxw OR ext:lyx)
will be interpreted as
"champagne OR ext:odt OR ext:sxw OR ext:lyx"
instead of the correct
"champagne AND (ext:odt OR ext:sxw OR ext:lyx)"
Workaround until the fix is issued: add non-existing terms
before the OR part and check the resulting query:
"champagne bogusxyztv ext:odt OR ext:sxw OR ext:lyx"
</li>
<li>The "Copy file name" and "Copy URL" entries of the
right-click menus only copy the data to the X11 primary
selection (use middle-button click to paste). This is
probably a mistake, the data should be copied to the
clipboard too (permitting the use of the "Paste" edit menu
entry or Ctrl+V in the target).</li>
<li>Possibly harmful bug in strerror_r usage (GNU case).</li>
<li>Possibly harmful bug in strerror_r usage (GNU case).</li>
</ul>
<h2>1.10.6</h2>
<ul>
<li> If the locale is not utf-8, non-ascii command line
arguments to recoll and recollq are not converted to utf-8,
which may prevent, for example, the kde applet from
working. The workaround is to apply the following one-line
fix to qtgui/main.cpp, recompile and install recoll:
<pre>
386c386
&lt; sSearch->setSearchString(QString::fromUtf8(qstring.c_str()));
---
&gt; sSearch->setSearchString(QString::fromLocal8Bit(qstring.c_str()));
</pre>
</li>
<li> If the locale is not utf-8, non-ascii command line
arguments to recoll and recollq are not converted to utf-8,
which may prevent, for example, the kde applet from
working. The workaround is to apply the following one-line
fix to qtgui/main.cpp, recompile and install recoll:
<pre>
386c386
&lt; sSearch->setSearchString(QString::fromUtf8(qstring.c_str()));
---
&gt; sSearch->setSearchString(QString::fromLocal8Bit(qstring.c_str()));
</pre>
</li>
</ul>
<h2>1.10.1</h2>
<ul>
<li> A relatively simple error case can cause the indexer to
stop processing an mbox file (forgetting all subsequent
messages). More specifically, this happens when encountering
more than than a few dozen errors while handling
attachments. This is relatively common: for exemple if an
external helper application is missing and multiple
attachments of the affected type are found (ie: multiple
images and no exiftool). Workaround: install the helper
application.
<li> The decoding of base-64 data in emails fails in a relatively uncommon
but sometimes encountered case.
<li> In a preview window, when walking the search term hits with the
Previous/Next buttons, 'Previous' actually acts as 'Next' (it does work
normally for the local search).
<li> Problems in detecting message separators inside Thunderbird mailboxes
(quite probably mainly for messages imported from outlook?). Can lead to
unindexed messages, and even apparently indexer crashes in some cases.
<li> File names indexed as terms can sometimes overflow the maximum term
size, halting the indexing.
<li> For Phrase/Near searches, only the first term group is highlighted in
preview.
<li> A relatively simple error case can cause the indexer to
stop processing an mbox file (forgetting all subsequent
messages). More specifically, this happens when encountering
more than than a few dozen errors while handling
attachments. This is relatively common: for exemple if an
external helper application is missing and multiple
attachments of the affected type are found (ie: multiple
images and no exiftool). Workaround: install the helper
application.
<li> The decoding of base-64 data in emails fails in a relatively uncommon
but sometimes encountered case.
<li> In a preview window, when walking the search term hits with the
Previous/Next buttons, 'Previous' actually acts as 'Next' (it does work
normally for the local search).
<li> Problems in detecting message separators inside Thunderbird mailboxes
(quite probably mainly for messages imported from outlook?). Can lead to
unindexed messages, and even apparently indexer crashes in some cases.
<li> File names indexed as terms can sometimes overflow the maximum term
size, halting the indexing.
<li> For Phrase/Near searches, only the first term group is highlighted in
preview.
</ul>
<h2>1.10.0</h2>
<ul>
<li> If a filter fails while trying to extract the data from a file, the file
will not be indexed at all (not even the file name). The file
name should be indexed in this case. This happens in particular in the
very common case where the helper application is not installed (ie:
missing Exiftool -> no *.jpg names in the index).
<li> If a filter fails while trying to extract the data from a file, the file
will not be indexed at all (not even the file name). The file
name should be indexed in this case. This happens in particular in the
very common case where the helper application is not installed (ie:
missing Exiftool -> no *.jpg names in the index).
<li> If several query language "ext:" qualifiers are specified, they will be
joined by an AND instead of OR, resulting in no results. Using an
explicit OR doesn't work (actually OR + field names is generally
broken). In some cases, you can use a "type:" qualifier as a workaround.
<li> If several query language "ext:" qualifiers are specified, they will be
joined by an AND instead of OR, resulting in no results. Using an
explicit OR doesn't work (actually OR + field names is generally
broken). In some cases, you can use a "type:" qualifier as a workaround.
</ul>
<h2>1.9.x</h2>
<ul>
<li> Problems have been reported indexing big mailstores (several hundreds of
thousands of messages): resulting in a very big database and even
crashes.
<li> Problems have been reported indexing big mailstores (several hundreds of
thousands of messages): resulting in a very big database and even
crashes.
</ul>
<h2>1.8.2</h2>
<ul>
<li> Under ubuntu (at least, maybe debian too), the default awk interpreter
(mawk) is ancient, and the recoll pdf input filter does not
work (removes all space characters). This can be solved by installing the
gawk package.
$ apt-get install gawk
$ update-alternatives --set awk /usr/bin/gawk
<li> Under ubuntu (at least, maybe debian too), the default awk interpreter
(mawk) is ancient, and the recoll pdf input filter does not
work (removes all space characters). This can be solved by installing the
gawk package.
$ apt-get install gawk
$ update-alternatives --set awk /usr/bin/gawk
<li> There are sometimes problems with document deletions: the index can
get in a state where deleted or moved documents are not purged from the
index (the log file says that the doc are deleted, but they aren't
actually). When this happens, the only solution currently is to reindex
from scratch (recollindex -z). This is due to a xapian bug, which is
fixed in xapian 1.0.2, or you can apply the following patch to xapian
1.0.1 to fix it:
http://www.lesbonscomptes.com/recoll/xapian/xapian-delete-document.patch
<li> There are sometimes problems with document deletions: the index can
get in a state where deleted or moved documents are not purged from the
index (the log file says that the doc are deleted, but they aren't
actually). When this happens, the only solution currently is to reindex
from scratch (recollindex -z). This is due to a xapian bug, which is
fixed in xapian 1.0.2, or you can apply the following patch to xapian
1.0.1 to fix it:
http://www.lesbonscomptes.com/recoll/xapian/xapian-delete-document.patch
<li> The dates shown for email attachments in a result list are the email
folder modification date. This should be inherited from the parent
message instead.
<li> The dates shown for email attachments in a result list are the email
folder modification date. This should be inherited from the parent
message instead.
<li> There are a few problems in the qt4 version of recoll:
<li> Some accelerators (esc-spc, ctl-arrow) do not work, neither do
copy/paste between the result list and preview windows and x11
applications.
<li> The qt4 q3textedit::find() method is extremely slow, so that
positionning to first search term in Recoll preview has been disabled,
and the application will sometimes appear to be looping when using the
find feature in the preview window (it's not looping, it's searching...)
<li> There are a few problems in the qt4 version of recoll:
<li> Some accelerators (esc-spc, ctl-arrow) do not work, neither do
copy/paste between the result list and preview windows and x11
applications.
<li> The qt4 q3textedit::find() method is extremely slow, so that
positionning to first search term in Recoll preview has been disabled,
and the application will sometimes appear to be looping when using the
find feature in the preview window (it's not looping, it's searching...)
</ul>
<h2>1.8.1</h2>
<ul>
<li> This is not really a bug but .beagle really should be included in
"skippedNames", or you end up indexing the beagle text cache, which is
not really desirable.
<li> Doc bug: the manual states that the query language supports a "mime:"
switch to filter mime types. There is currently no such thing.
<li> This is not really a bug but .beagle really should be included in
"skippedNames", or you end up indexing the beagle text cache, which is
not really desirable.
<li> Doc bug: the manual states that the query language supports a "mime:"
switch to filter mime types. There is currently no such thing.
</ul>
<h2>1.7.5</h2>
<ul>
<li> Debian and Ubuntu: the rclsoff Openoffice filter doesn't work,
because of an incorrect shell syntax (understood by bash but not sh). To
fix, you edit /usr[/local]/share/recoll/filters/rclsoff and can change
the line:
trap cleanup EXIT SIGHUP SIGQUIT SIGINT SIGTERM
into:
trap cleanup EXIT HUP QUIT INT TERM
or download the updated filter from the filters page:
http://www.recoll.org/filters/filters.html
<li> Debian and Ubuntu: the rclsoff Openoffice filter doesn't work,
because of an incorrect shell syntax (understood by bash but not sh). To
fix, you edit /usr[/local]/share/recoll/filters/rclsoff and can change
the line:
trap cleanup EXIT SIGHUP SIGQUIT SIGINT SIGTERM
into:
trap cleanup EXIT HUP QUIT INT TERM
or download the updated filter from the filters page:
http://www.recoll.org/filters/filters.html
</ul>
<h2>1.7.3</h2>
<ul>
<li> Processing will stop on first error while indexing an mbox file. This
could happen just because an attachment could not be decoded, and can
cause non-indexing of many messages. The most probable cause of error is
a missing filter (ie for ms-word files), so the temporary workaround
would be to install the missing filters. This bug is specific to 1.7 and
1.6 users need not worry. A correction will be issued very soon.
<li> Messages of type multipart/signed are not indexed.
<li> Processing will stop on first error while indexing an mbox file. This
could happen just because an attachment could not be decoded, and can
cause non-indexing of many messages. The most probable cause of error is
a missing filter (ie for ms-word files), so the temporary workaround
would be to install the missing filters. This bug is specific to 1.7 and
1.6 users need not worry. A correction will be issued very soon.
<li> Messages of type multipart/signed are not indexed.
</ul>
<h2>1.6.2</h2>
<ul>
<li> Relatively unfrequent issue with message boundary detection in mbox
files, could cause miscellaneous problems.
<li> Executing an external viewer for a file with single-quotes in the name
would not work.
<li> Relatively unfrequent issue with message boundary detection in mbox
files, could cause miscellaneous problems.
<li> Executing an external viewer for a file with single-quotes in the name
would not work.
</ul>
<h2>1.5.10</h2>
<ul>
<li> If a defaultcharset was set in the configuration file for a subdirectory,
it would stay in effect for all subsequent files/directories (except if
explicitely overridden), potentially causing many transcoding errors.
<li> If a defaultcharset was set in the configuration file for a subdirectory,
it would stay in effect for all subsequent files/directories (except if
explicitely overridden), potentially causing many transcoding errors.
</ul>
<h2>1.5.[1-7]</h2>
<ul>
<li> Dates in result list come from the file's ctimes, which may be confusing
<li> Some rare MIME messages with null boundaries can crash the indexer.
<li> Dates in result list come from the file's ctimes, which may be confusing
<li> Some rare MIME messages with null boundaries can crash the indexer.
</ul>
<h2>1.5.0</h2>
<ul>
<li> Under some conditions, recoll startup and exit could be very slow: the
simple search history list had serious problems with non-ascii strings,
whose size sometimes doubled at each program startup/stop.
<li> Under some conditions, recoll startup and exit could be very slow: the
simple search history list had serious problems with non-ascii strings,
whose size sometimes doubled at each program startup/stop.
</ul>
<h2>1.3.3</h2>
<ul>
<li> Several of the external filters did not handle path names with embedded
spaces (rcluncomp rclsoff rclps rclmedia rcldjvu). This is fixed in 1.4.
<li> Several of the external filters did not handle path names with embedded
spaces (rcluncomp rclsoff rclps rclmedia rcldjvu). This is fixed in 1.4.
<li> If your QT installation is built with the QT_NO_STL flag, Recoll will not
compile. I have a patch for this (will be fixed in the next release),
contact me if you get the problem. Typical error message:
main.cpp:160: error: no match for 'operator+=' in 'msg += reason'
<li> If your QT installation is built with the QT_NO_STL flag, Recoll will not
compile. I have a patch for this (will be fixed in the next release),
contact me if you get the problem. Typical error message:
main.cpp:160: error: no match for 'operator+=' in 'msg += reason'
<li> The 'None of these words' field in the complex search does not work if
there are no other filled fields (it transforms into an ordinary
search). Workaround: enter very common term(s) in the 'any of these
words' field.
<li> The 'None of these words' field in the complex search does not work if
there are no other filled fields (it transforms into an ordinary
search). Workaround: enter very common term(s) in the 'any of these
words' field.
<li> Indexing cannot currently be conveniently and cleanly
stopped when it's started. You can kill the process, and
keyboard interrupt might work, but this may leave the
database in a bad state. This is fixed in the upcoming
release, there is no current workaround.
<li> Indexing cannot currently be conveniently and cleanly
stopped when it's started. You can kill the process, and
keyboard interrupt might work, but this may leave the
database in a bad state. This is fixed in the upcoming
release, there is no current workaround.
</ul>
<h2>1.2.2</h2>
<ul>
<li> The preview window is supposed to scroll after loading the document so
that the first search term is visible. This does not work in many cases.
<li> The result list title is not shown for sorted lists
<li> The preview window is supposed to scroll after loading the document so
that the first search term is visible. This does not work in many cases.
<li> The result list title is not shown for sorted lists
Notes on older versions:
<li> Trouble compiling on some linux systems (Gentoo and Slackware?). There
existed a quite common issue where the Recoll link will fail trying to
use a libstdc++.la file. This was due to a problem with the xapian-config
program. A workaround has been included in the configure script for
recoll 1.2.2, and the problem should not occur any more.
Notes on older versions:
<li> Trouble compiling on some linux systems (Gentoo and Slackware?). There
existed a quite common issue where the Recoll link will fail trying to
use a libstdc++.la file. This was due to a problem with the xapian-config
program. A workaround has been included in the configure script for
recoll 1.2.2, and the problem should not occur any more.
<li> Case-insensitive search should now work in most cases
(used to not work except for accented ascii).
<li> Case-insensitive search should now work in most cases
(used to not work except for accented ascii).
<li> All directories and files with names beginning with a dot were ignored
by the skippedNames directive in the default recoll.conf file from
older versions (no indexation of mozilla or thunderbird email !). An
upgrade will not fix this (it will not modify an existing
configuration). You need to edit recoll.conf by hand and remove the .*
from skippedNames.</li>
<li> All directories and files with names beginning with a dot were ignored
by the skippedNames directive in the default recoll.conf file from
older versions (no indexation of mozilla or thunderbird email !). An
upgrade will not fix this (it will not modify an existing
configuration). You need to edit recoll.conf by hand and remove the .*
from skippedNames.</li>
</ul>

File diff suppressed because it is too large Load Diff

View File

@ -34,7 +34,7 @@
please send me an <a
href="mailto:jean-francois.dockes@wanadoo.fr">email</a>.</p>
<h1>Translation</h1>
<h1><a name="translation">Translation</a></h1>
<p>More translations is good ! If you are a non-english speaker
(and understand english, which can probably be assumed, you
@ -55,7 +55,7 @@
<li>Ukrainian: <a href="translations/recoll_uk.ts">recoll_uk.ts</a></li>
</ul>
<h1>Development</h1>
<h1><a name="development">Development</a></h1>
<p>Apart from general development for additional functionality
or bug fixes, the following tasks are waiting for you:</p>
@ -79,6 +79,100 @@
<li>Etc. :)</li>
</ul>
<h1><a name="problemreport">Problem reporting</a></h1>
<p>Once in a while it will happen that a Recoll program will
crash (either the "recoll" graphical interface or the
"recollindex" command line indexing command).</p>
<p>Reporting crashes is very useful. It can help others, and it
can get your own problem to be solved.</p>
<p>All reports are useful. But, in order to maximize usefulness,
a crash report should include a so-called stack trace, something
that indicates what the program was doing when it
crashed. Getting a useful stack trace is not very difficult,
but it may need a little work on your part (which
will then enable me do my part of the work).</p>
<p>If your distribution includes a separate package for Recoll
debugging symbols, it probably also has a page on its web site
explaining how to use them to get a stack trace. You should
follow these instructions. If there is no debugging package,
you should follow the instructions below. A little
familiarity with the command line will be necessary.</p>
<dl><dt>Compiling and installing a debugging version</dt>
<dd>
<ul>
<li>Obtain the recoll source for the version you are using
(<a
href="http://www.recoll.org/download.html">www.recoll.org</a>),
and extract the source tree.</li>
<li>Follow the instructions for
<a
href="http://www.lesbonscomptes.com/recoll/usermanual/index.html#RCL.INSTALL.BUILDING">
building Recoll from source</a> with the following
modifications:
<ul>
<li>Before running <tt>configure</tt>, edit
the <tt>mk/localdefs.in</tt> file and remove the <tt>-O2</tt>
option(s). </li>
<li>When running <tt>configure</tt>, specify the
standard installation location for your system as a prefix
(to avoid ending up with two installed versions, which
would almost certainly end in confusion). On Linux this
would typically be:
<br><tt>configure --prefix=/usr</tt>.
</li> <li>When installing, arrange for the installed
executables not to be stripped of debugging symbols by
specifying a value for the STRIP environment variable
(ie: <tt>echo</tt> or <tt>ls</tt>): <br><tt>sudo make
install STRIP=ls</tt>
</li>
</ul>
</ul></dd>
<dt>Getting a core dump</dt>
<dd>You will need to run the operation that caused the crash
inside a writable directory, and tell the system that you
accept core dumps. The commands need to be run in a shell
inside a terminal window. Ie:
<pre><tt>
cd
ulimit -c unlimited
recoll #(or recollindex or whatever you want to run).
</tt></pre>
Hopefully, you will succeed in getting the command to crash,
and you will get a core file.
</dd>
<dt>Using gdb to get a stack trace</dt>
<dd>
<ul>
<li>Install <tt>gdb</tt> if it is not already on the system.</li>
<li>Run <tt>gdb</tt> on the command that crashed and the
core file (depending on the system, the core file may be
named "core" or something else, like recollindex.core, or
core.pid), ie:
<br><tt>gdb /usr/bin/recollindex core</tt>
</li>
<li>Inside <tt>gdb</tt>, you need to use different
commands to get a stack trace for <tt>recoll</tt>
and <tt>recollindex</tt>. For <tt>recollindex</tt> you
can use the <tt>bt</tt> command. For <tt>recoll</tt>
use: <br><tt>thread&nbsp;apply&nbsp;all&nbsp;bt&nbsp;full</tt>
</li>
<li>Copy/paste the output to your report email :), and
quit <tt>gdb</tt> ("q").</li>
</ul>
</dd>
</dl>
</div>
</body>
</html>

View File

@ -117,16 +117,19 @@
<h2><a name="source">Source</a></h2>
<p><b>Current version:</b>1.12.0:
<a href="recoll-1.12.0.tar.gz">recoll-1.12.0.tar.gz</a>.
<p><b>Current version:</b> 1.12.2:
<a href="src/recoll-1.12.2.tar.gz">recoll-1.12.2.tar.gz</a>.
<a href="CHANGES.html">Changes</a>. <a href="BUGS.html">Bugs</a>.
</p>
<p>In order to build Recoll from source, you will need a
xapian-core installation. You will find source and binary
<p>In order to build Recoll from source, you will need to install
the Xapian core development libraries. You will find source and binary
packages on the <a href="http://www.xapian.org/download.php">
Xapian download page</a>.
Recoll 1.12 needs at least xapian 1.0.5, and I can see no
reason not to use the latest 1.0 Xapian (1.0.10 currently).</p>
Recoll 1.12 needs at least xapian 1.0.5, I suggest
using the latest 1.0 Xapian (1.0.16 currently). Xapian
versions after 1.0.12 don't need the
<a href="BUGS.html#XapianNearPatch">NEAR patch</a> any more.</p>
<table>
<tr><td valign="top">Qt:</td>
<td>
@ -143,101 +146,116 @@
</table>
<p>Older recoll releases:
<a href="recoll-1.11.4.tar.gz">1.11.4</a>.
<a href="recoll-1.10.6.tar.gz">1.10.6</a>.
<a href="recoll-1.9.0.tar.gz">1.9.0</a>.
<a href="older/recoll-1.8.2.tar.gz">1.8.2</a>.
<a href="older/recoll-1.7.6.tar.gz">1.7.6</a>.
<a href="older/recoll-1.6.3.tar.gz">1.6.3</a>.
<a href="older/recoll-1.5.11.tar.gz">1.5.11</a>.
<a href="older/recoll-1.4.3.tar.gz">1.4.3</a>.
<a href="older/recoll-1.3.3.tar.gz">1.3.3</a>.
<a href="older/recoll-1.2.3.tar.gz">1.2.3</a>.
<a href="older/recoll-1.1.0.tar.gz">1.1.0</a>.
<a href="older/recoll-1.0.16.tar.gz">1.0.16</a>.
<a href="src/recoll-1.12.1.tar.gz">1.12.1</a>.
<a href="src/recoll-1.11.4.tar.gz">1.11.4</a>.
<a href="src/recoll-1.10.6.tar.gz">1.10.6</a>.
<a href="src/recoll-1.9.0.tar.gz">1.9.0</a>.
<a href="src/older/recoll-1.8.2.tar.gz">1.8.2</a>.
<a href="src/older/recoll-1.7.6.tar.gz">1.7.6</a>.
<a href="src/older/recoll-1.6.3.tar.gz">1.6.3</a>.
<a href="src/older/recoll-1.5.11.tar.gz">1.5.11</a>.
<a href="src/older/recoll-1.4.3.tar.gz">1.4.3</a>.
<a href="src/older/recoll-1.3.3.tar.gz">1.3.3</a>.
<a href="src/older/recoll-1.2.3.tar.gz">1.2.3</a>.
<a href="src/older/recoll-1.1.0.tar.gz">1.1.0</a>.
<a href="src/older/recoll-1.0.16.tar.gz">1.0.16</a>.
</p>
<p>A separate source file contains a KDE kicker applet to start
a Recoll search from the KDE toolbar:
<a href="recoll_applet-1.10.0.tgz">recoll_applet-1.10.0.tgz</a>.
<a href="src/recoll_applet-1.10.0.tgz">recoll_applet-1.10.0.tgz</a>.
This is a very slightly modified version of the
<a href="http://demandiseineseite.gmxhome.de/find/">
find_applet. It will work with any recoll version after 1.10.</a></p>
find_applet</a>. It will work with any recoll version after 1.10.</p>
<h2><a name="rpms">Packages</a></h2>
<p>The executables inside the binary rpms have a static link to
xapian 1.0.10, there is no real dependency except Qt 3.3
(or Qt 4.1 when mentioned).
Some Fedora and Mandriva packages unfortunately think that they
depend on exiftool (which is needed by the little
used jpeg info filter), due to excessive rpmbuild
cleverness.
<br>
Of course you need xapian-core installed to use the source
rpms. </p>
<p>Packages or ports for Recoll are available in the standard
repositories for many distributions.</p>
<p>However they are often a bit older or built with older Xapian
releases. Here follow a number of updated packages and
instructions for a number of distributions.</p>
<p><b>Fedora Core 6-9 with Qt 3.x</b>
<a href="fc6/recoll-1.12.0-1.i386.rpm">
recoll-1.12.0-1.i386.rpm</a>.
<h3>Ubuntu</h3>
<blockquote>
<p><a href="http://www.launchpad.net/~xapian-backports/+archive/ppa">
Xapian</a> and
<a href="http://www.launchpad.net/~recoll-backports/+archive/ppa">
Recoll</a> have Personal Package Archives on
launchpad.net. These hold the latest versions, compiled for a
set of Ubuntu series.
You just need to add the PPAs to your system software sources,
and you can then install the normal package manager to install
or update Recoll and Xapian.
To avoid messages about signature errors, you will have to
import the Recoll and Xapian public keys:
<pre><tt>
gpg --keyserver keyserver.ubuntu.com --recv 9DA85604
gpg --export --armor 9DA85604 | sudo apt-key add -
gpg --keyserver keyserver.ubuntu.com --recv A0735AD0
gpg --export --armor A0735AD0 | sudo apt-key add -
</tt></pre>
</p>
</blockquote>
<h3>RPMS</h3>
<p><i>The executables inside the binary rpms which follow have a
static link to Xapian 1.0.16, there is no real dependency except Qt 3
or Qt 4.<br>
Some Fedora and Mandriva packages unfortunately think that they
depend on exiftool (which is needed by the little used jpeg
info filter), due to excessive rpmbuild cleverness.
<br>You need to install the Xapian library development
package if you want use the source rpms.</i></p>
<h3>Fedora</h3>
<blockquote>
<p><b>Fedora Core 6 with Qt 3.3.8</b>
<a href="fc6/recoll-1.12.2-1.i386.rpm">
recoll-1.12.2-1.i386.rpm</a>.
Source:
<a href="fc6/recoll-1.12.0-1.src.rpm">
recoll-1.12.0-1.src.rpm</a>
This package also installs and runs on Fedora 9.
<a href="fc6/recoll-1.12.2-1.src.rpm">
recoll-1.12.2-1.src.rpm</a>
This package usually also installs and runs on Fedora 9.
</p>
<p><b>Fedora Core 10 with Qt 4</b>
<a href="fc10/recoll-1.12.0-1.fc10.i586.rpm">
recoll-1.12.0-1.fc10.i586.rpm</a>.
<a href="fc10/recoll-1.12.2-1.fc10.i586.rpm">
recoll-1.12.2-1.fc10.i586.rpm</a>.
Source:
<a href="fc10/recoll-1.12.0-1.fc10.src.rpm">
recoll-1.12.0-1.fc10.src.rpm</a>
<a href="fc10/recoll-1.12.2-1.fc10.src.rpm">
recoll-1.12.2-1.fc10.src.rpm</a>
</p>
</blockquote>
<p><b>Mandriva 2006 with Qt 3</b> (also works on 2005 and 2007).
<a href="mandriva2006/recoll-1.12.0-0.1.20060mdk.i586.rpm">
recoll-1.12.0-0.1.20060mdk.i586.rpm</a>.
<h3>OpenSUSE</h3>
<blockquote>
<p><b>OpenSUSE 11.0 with qt3</b>:
<a href="suse11.0/recoll-1.12.2-0.i586.rpm">
recoll-1.12.2-0.i586.rpm</a>.
Source: <a href="suse11.0/recoll-1.12.2-0.src.rpm">
recoll-1.12.2-0.src.rpm</a></p>
<p><b>OpenSUSE 11.1 with qt4</b>:
<a href="suse11.1/recoll-1.12.2-0.i586.rpm">
recoll-1.12.2-0.i586.rpm</a>.
Source: <a href="suse11.1/recoll-1.12.2-0.src.rpm">
recoll-1.12.2-0.src.rpm</a></p>
<p>If you build from source on OpenSUSE 11, note that the default
qt4 version on some systems is 4.4.0 which will badly
display the the result list icons. Use qt3 or install a
newer version of qt4.</p>
</blockquote>
<h3>Mandriva</h3>
<blockquote>
<p><b>Mandriva 2008 with Qt 4</b>:
<a href="mandriva2008spring/recoll-1.12.2-1mdv2008.1.i586.rpm">
recoll-1.12.2-1mdv2008.1.i586.rpm</a>.
Source:
<a href="mandriva2006/recoll-1.12.0-0.1.20060mdk.src.rpm">
recoll-1.12.0-0.1.20060mdk.src.rpm</a>
</p>
<p><b>Mandriva 2008 with Qt 4</b>
<a href="mandriva2008spring/recoll-1.12.0-1mdv2008.1.i586.rpm">
recoll-1.12.0-1mdv2008.1.i586.rpm</a>.
Source:
<a href="mandriva2008spring/recoll-1.12.0-1mdv2008.1.src.rpm">
recoll-1.12.0-1mdv2008.1.src.rpm</a>
</p>
<p><b>Suse 11.0 with qt3</b>
<a href="suse11/recoll-1.12.0-0.i586.rpm">
recoll-1.12.0-0.i586.rpm</a>.
Source:
<a href="suse11/recoll-1.12.0-0.src.rpm">
recoll-1.12.0-0.src.rpm</a><br>
If you build from source on OpenSuse 11, note that the default
qt4 version is 4.4.0 which will badly display the result list
icons. Use qt3 or install a newer version of qt4.
</p>
<p><b>Ubuntu 6.06 dapper / edgy / gutsy / hardy</b>
<a href="debian/dapper/recoll_1.12.0-0ubuntu1_i386.deb">
recoll_1.12.0-0ubuntu1_i386.deb</a>
<a href="debian/dapper/">debian/dapper</a>. This package was
built on "dapper" and appears to work correctly on later
Ubuntu releases. This package is not configured for real-time
indexing.</p>
<p>Here is a package for Ubuntu 8.04 Hardy which supports
real-time indexing. It is also built for qt4, so this must be
installed on the target system. Avoid qt 4.4.0 (from hardy
backports). The standard 4.3.x is fine (or 4.4.1 and later)
<a href="debian/hardy/recoll_1.12.0-0ubuntu1_i386.deb">
debian/hardy/recoll_1.12.0-0ubuntu1_i386.deb</a>
</p>
<p><b>Debian unstable</b> Recoll is in the package repository,
you can install it with the usual <em>apt-get install recoll</em>.
<a href="http://packages.qa.debian.org/r/recoll.html">
Package page</a></p>
<a href="mandriva2008spring/recoll-1.12.2-1mdv2008.1.src.rpm">
recoll-1.12.2-1mdv2008.1.src.rpm</a>
</p>
</blockquote>
<h2><a name="otherbinary">Binary bundles</a></h2>
@ -245,27 +263,39 @@
The executables were built with xapian 1.0.8 (patched for the
NEAR bug) and libiconv 1.9.2 (where relevant) as static
libraries. They depend on Qt 3.3. For Solaris, you should be
able to find a Qt package
<a href="http://www.sunfreeware.com/">here</a>.</p>
able to find a Qt package on
<a href="http://www.sunfreeware.com/">sunfreeware</a>.</p>
<p>The installation instructions are <a
href="usermanual/rcl.install.html"> there</a>.</p>
<p><a href="usermanual/rcl.install.html">Installation
instructions here</a>.</p>
<p><span class="application">FreeBSD</span> 6.4 i386:
<a href="freebsd/recoll-1.12.0-FreeBSD-6.4-STABLE.tgz">
recoll-1.12.0-FreeBSD-6.4-STABLE.tgz</a>
</p>
<h3>FreeBSD</h3>
<blockquote>
<p>The FreeBSD ports track the Recoll releases quite
closely, so there is actually little point in using the
following. Only for the <i>really</i> impatient:</p>
<p><b>FreeBSD 6.4 i386 Qt 4.4.3</b>:
<a href="freebsd/recoll-1.12.2-FreeBSD-6.4-STABLE.tgz">
recoll-1.12.2-FreeBSD-6.4-STABLE.tgz</a>
</p>
<p><b>FreeBSD 7.2 i386 Qt 4.5.2</b>:
<a href="freebsd/recoll-1.12.2-FreeBSD-7.2-STABLE.tgz">
recoll-1.12.2-FreeBSD-7.2-STABLE.tgz</a>
</p>
</blockquote>
<p><span class="application">Solaris 8</span> sparc.
Note to Solaris users: you need to perform the initial
indexing pass with "recollindex", not the recoll GUI indexing
thread. See <a href="BUGS.html">errata</a>.
<a href="sunos/recoll-1.12.0-SunOS-5.8.tgz">
recoll-1.12.0-SunOS-5.8.tgz</a>.
<h3>Solaris</h3>
<blockquote>
<p>Note to Solaris users: you need to perform the initial
indexing pass with "recollindex", not the recoll GUI indexing
thread. See <a href="BUGS.html">errata</a>.
<p><b>Solaris 8 SPARC</b>:
<a href="sunos/recoll-1.12.2-SunOS-5.8.tgz">
recoll-1.12.2-SunOS-5.8.tgz</a>. </p>
<p>Recoll also builds and runs on Solaris 10, but, given the
situation of open source packages for Solaris (very old Qt on
the Companion CD, inconsistent versions of the compiler and
situation (2008) of open source packages for Solaris (very old
Qt on the Companion CD, inconsistent versions of the compiler and
non-threaded version of Qt on sunfreeware), I've come to the
temporary conclusion that you are better off building than
trying to install packages. The approach I tried in 2008 and
@ -277,9 +307,9 @@
<li>Compile xapian-core and install it (with prefix /usr/local).</li>
<li>Configure and install Qt. The following config worked for me,
with Qt 3.3.8:
<pre>
<pre><tt>
./configure -platform solaris-g++ -prefix /usr/local/Trolltech/Qt-3.3.8/ -thread
</pre>
</tt></pre>
Then make. Weirdly, I had to add the Qt build lib/
directory to LD_LIBRARY_PATH at some point during the
build).
@ -295,6 +325,7 @@
</p>
<p>Obviously, there are other ways to do it (use CC, install
some place else ... ), but I tried this one.</p>
</blockquote>
<h2><a name="ports">FreeBSD ports</a></h2>

View File

@ -38,7 +38,7 @@
<dt><a name="systems">Supported systems</a></dt>
<dd><span class="application">Recoll</span> has been compiled and
tested on FreeBSD, Linux, Darwin and Solaris (versions
FreeBSD 5/6, Redhat 7/8/9, Fedora Core 5/6/7, Suse 10/11,
FreeBSD 5-7, Redhat 7/8/9, Fedora Core 5-10, Suse 10/11,
Gentoo, Debian 3.1, Solaris 8/9/10. Other not too distant
releases should be ok too).</dd>

View File

@ -47,7 +47,7 @@
<p><span class="application">Recoll</span> is free, open source,
and licensed under the GPL. The current version is
<a class="important" href="download.html">1.12.0</a>
<a class="important" href="download.html">1.12.2</a>
(<a href="CHANGES.html">Changes</a>).</p>
<h2>Features: </h2>
@ -55,7 +55,7 @@
<ul>
<li>Easy installation, few dependancies. No database daemon,
web server, desktop environment or exotic language necessary.</li>
<li>Will run on most unix-based <a
<li>Will run on most Unix-based <a
href="features.html#systems">systems</a></li>
<li>Qt-based GUI. Can use either Qt 3 or Qt 4.</li>
@ -80,9 +80,12 @@
<h2>News: </h2>
<ul>
<li>2009-01-30 : <a href="download.html#source">1.12.0</a> is
out. Please give it a try, I'll wait a few weeks for initial
problem reports before generating the packages.</li>
<li>2009-10-22 : <a href="download.html#source">1.12.2</a> is
out. It fixes a number of
<a href="CHANGES.html">ennoying bugs</a>.</li>
<li>2009-06-23 : <a href="download.html#source">1.12.1</a> is
out. It fixes a couple of minor bugs, and build errors with the
latest gcc and gnu libc.</li>
<li>2008-09-01 : <a href="filters/filters.html">A new
filter</a> for Office Open XML formats (docx ...).</li>
<li>2008-05-22 : we now have a mailing list:

View File

@ -48,7 +48,7 @@
<p><span class="application">Recoll</span> est un logiciel libre
gratuit, dont le code source est disponible sous licence GPL.
La dernière version est
<a class="important" href="download.html">1.12.0</a></p>
<a class="important" href="download.html">1.12.2</a></p>
<p>L'interface utilisateur de
<span class="application">Recoll</span> est traduite en
@ -94,8 +94,12 @@
<h2>Nouvelles: </h2>
<ul>
<li>2009-01-30 : la version
<a href="download.html#source">1.12.0</a> vient de sortir.</li>
<li>2009-10-22 : la version
<a href="download.html#source">1.12.2</a> vient de sortir et
corrige quelques <a href="CHANGES.html">bugs</a>.</li>
<li>2009-06-23 : la version
<a href="download.html#source">1.12.1</a> vient de sortir.</li>
<li>2008-09-01 : <a href="filters/filters.html">Un nouveau
filtre</a> pour les formats Office Open XML (docx ...).</li>

View File

@ -1,19 +1,50 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Photos</title>
<title>RECOLL: screenshots</title>
<meta name="Author" content="Jean-Francois Dockes">
<meta name="Description" content=
"Screenshots for Recoll, a simple full-text unix/linux desktop search system">
<meta name="Keywords" content=
"full text search,fulltext,desktop search,unix,linux,solaris,open source,free">
<meta http-equiv="Content-language" content="en">
<meta http-equiv="content-type" content=
"text/html; charset=iso-8859-1">
<meta name="robots" content="All,Index,Follow">
<link type="text/css" rel="stylesheet" href="../styles/style.css">
</head>
<body>
<div class="rightlinks">
<ul>
<li><a href="http://www.recoll.org">Home</a></li>
<li>Screenshots</li>
<li><a href="../download.html">Downloads</a></li>
<li><a href="../doc.html">Documentation</a></li>
</ul>
</div>
<div class="content">
<table>
<tr>
<td align="center"><a href="recoll0.html"><img src="recoll0-thumb.png"></a></td>
<td align="center"><a href="recoll1.html"><img src="recoll1-thumb.png"></a></td>
<td align="center"><a href="recoll2.html"><img src="recoll2-thumb.png"></a></td>
</tr><tr>
<td align="center"><a href="recoll3.html"><img src="recoll3-thumb.png"></a></td>
</tr>
<tr>
<td align="center"><a href="recoll4.html"><img src="recoll4-thumb.png"></a></td>
<td align="center"><a href="recoll5.html"><img src="recoll5-thumb.png"></a></td>
</tr><tr>
<td align="center"><a href="recoll_chinese.html"><img src="recoll_chinese-thumb.png"></a></td>
<td align="center"><a href="recoll-HTML_search_results.html"><img src="recoll-HTML_search_results-thumb.png"></a></td>
</tr></table></body></html>
</tr>
</table>
</div>
</body>
</html>

View File

Before

Width:  |  Height:  |  Size: 1.8 KiB

After

Width:  |  Height:  |  Size: 1.8 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 40 KiB

After

Width:  |  Height:  |  Size: 52 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 232 KiB

View File

Before

Width:  |  Height:  |  Size: 1.4 KiB

After

Width:  |  Height:  |  Size: 1.4 KiB