diff --git a/website/BUGS.html b/website/BUGS.html
index 37d3a4d7..9231a6be 100644
--- a/website/BUGS.html
+++ b/website/BUGS.html
@@ -36,44 +36,7 @@
topmost section may also exist in older versions.
-
-
-
- - When using the Firefox plugin, increasing the web cache
- size only has an effect when initially creating the
- cache. If the cache already exists, you need to delete it
- for the new limit to take effect.
-
- - Sizes for documents bigger than 2 GB were improperly
- displayed.
-
- - Wildcards expressions sometimes cause false matches
- because of issues in handling errors from fnmatch(). This
- will only occur in an UTF-8 locale where file name
- conversion errors are possible (for old 8bit file
- names).
-
- - There are sometimes issues with CHM files character
- encoding.
-
- - Sorting by field 'relevancyrating' was not equivalent to
- natural Xapian ordering.
-
- - Weird data in filter output text (e.g.: produced by some
- versions of pdftotext) can cause an error which will halt
- the processing of the document, which becomes
- unsearchable. This is a relatively uncommon problem which
- signals itself by a specific error in the indexing log, so
- you can know if you are affected. Look for:
- xapian add_posting error Empty termnames aren't allowed
-
-
- - Raw indexes (not default): diacritics and case expansion
- is not applied to terms containing numbers so that a
- case-insensitive search does not work for them (e.g.:
- searching for ds1820 will not find DS1820).
-
-
+
- When no indexing helper applications are actually missing,
an ennoying popup is shown in the GUI at each end of a batch
indexing run (it's supposed to be shown only once).
@@ -131,6 +94,43 @@ video/x-msvideo = exec rclbad
+
+
+
+ - When using the Firefox plugin, increasing the web cache
+ size only has an effect when initially creating the
+ cache. If the cache already exists, you need to delete it
+ for the new limit to take effect.
+
+ - Sizes for documents bigger than 2 GB are improperly
+ displayed.
+
+ - Wildcards expressions sometimes cause false matches
+ because of issues in handling errors from fnmatch(). This
+ will only occur in an UTF-8 locale where file name
+ conversion errors are possible (for old 8bit file
+ names).
+
+ - CHM files character encoding is sometimes wrongly processed.
+
+ - Sorting by field 'relevancyrating' is not equivalent to
+ natural Xapian ordering.
+
+ - Weird data in filter output text (e.g.: produced by some
+ versions of pdftotext) can cause an error which will halt
+ the processing of the document, which becomes
+ unsearchable. This is a relatively uncommon problem which
+ signals itself by a specific error in the indexing log, so
+ you can know if you are affected. Look for:
+ xapian add_posting error Empty termnames aren't allowed
+
+
+ - Raw indexes (not default): diacritics and case expansion
+ is not applied to terms containing numbers so that a
+ case-insensitive search does not work for them (e.g.:
+ searching for ds1820 will not find DS1820).
+
+
- Thumbnails are not found on newer desktops (e.g. Ubuntu