* Less logic in theme code.
   * Encourages use of the menu system.
   * Easier to find where a title or breadcrumb comes from in other people's code because there are less places to look. Look in menu and then grep for the appropriate set function. Looking for calls to theme_page() is hard because there are too many of them.
   * Very slightly more efficient.

    + added support for multi-site configurations.
    + tidied up some old cruft and added code comments.

- Patch #6166 by Moshe: node preview should not display links.  Push the links to the theme instead of the theme having to pull them in using node_link().

  TODO:
    1. Update theme upgrade instructions in the handbook: node_link() is gone.
    2. Remove page_link() just like we removed node_link().

- Patch #12886 by thorne: fixed XHTML problem: the bluemarine theme used a border=0 attribute on the img tag for the site logo.

1) Clean up the text analyser: make it handle UTF-8 and all sorts of characters. The word splitter now does intelligent splitting into words and supports all Unicode characters. It has smart handling of acronyms, URLs, dates, ...

2) It now indexes the filtered output, which means it can take advantage of HTML tags. Meaningful tags (headers, strong, em, ...) are analysed and used to boost certain words scores. This has the side-effect of allowing the indexing of PHP nodes.

3) Link analyser for node links. The HTML analyser also checks for links. If they point to a node on the current site (handles path aliases) then the link's words are counted as part of the target node. This helps bring out commonly linked FAQs and answers to the top of the results.

4) Index comments along with the node. This means that the search can make a difference between a single node/comment about 'X' and a whole thread about 'X'. It also makes the search results much shorter and more relevant (before this patch, comments were even shown first).

5) We now keep track of total counts as well as a per item count for a word. This allows us to divide the word score by the total before adding up the scores for different words, and automatically makes noisewords have less influence than rare words. This dramatically improves the relevancy of multiword searches. This also makes the disadvantage of now using OR searching instead of AND searching less problematic.

6) Includes support for text preprocessors through a hook. This is required to index Chinese and Japanese, because these languages do not use spaces between words. An external utility can be used to split these into words through a simple wrapper module. Other uses could be spell checking (although it would have no UI).

7) Indexing is now regulated: only a certain amount of items will be indexed per cron run. This prevents PHP from running out of memory or timing out. This also makes the reindexing required for this patch automatic. I also added an index coverage estimate to the search admin screen.

8) Code cleanup! Moved all the search stuff from common.inc into search.module, rewired some hooks and simplified the functions used. The search form and results now also use valid XHTML and form_ functions. The search admin was moved from search/configure to admin/search for consistency.

9) Improved search output: we also show much more info per item: date, author, node type, amount of comments and a cool dynamic excerpt à la Google. The search form is now much more simpler and the help is only displayed as tips when no search results are found.

10) By moving all search logic to SQL, I was able to add a pager to the search results. This improves usability and performance dramatically.

- Patch #11728 by Uwe Hermann: fixed some typos in the code comments, Doxygen documentation and screen output.

  Uwe: I dropped the 'iff' chunks as 'iff' stands for 'if and only if'.

- #9576 : A last-minute fix for pushbutton in Opera/Konqueror/Safari got lost in the move to the new template system.
http://drupal.org/node/9576#comment-11328
This still suffers from the Safari gamma bug, which we agreed not to cater to.

- Patch #9988 by MegaGrunt: visual improvements to the tabs in Pushbutton.

Replace hardcoded <html lang="en"> with a locale dependant one. This is especially important for asian sites where this has an effect on font selection.

- Patch by JonBob: for consistency and readability, add brief descriptions of each source file inside the @file comment block at the head of the file. This helps with Doxygen indexing, and also allows neophytes to see what a file does immediately on opening the source, regardless of the organization of the hooks.

- Fixing 'flash of unstyled content' in bluemarine/pushbutton, which got reintroduced after the template changes.
- Fixed separate styles: added theme_get_styles() and the xtemplate {styles} tag to make sure stylesheets get included in the right order (drupal-specific, template-specific, style-specific).
- Fixing missing class on screenshots.
- Renamed drupal_get_theme_setting() and drupal_get_theme_settings() to theme_get_setting() and theme_get_settings().

   + removes 'toggle_search' from the features array in chameleon.theme
   + merges changes to bluemarine from just a couple of hours before template patch was committed

- Theme system changes.  Please consult http://drupal.org/node/view/9576 for details.

Tiny tweak to XTemplate CSS: the vertical padding at the bottom of a sticky post should be outside the gray sticky rectangle, not inside it.

- Removing gAMA chunk from xtemplate logo.png for less to avoid more gamma issues.

- Restoring background coloring for the watchdog logs (was broken)
- Making watchdog backgrounds lighter, makes it easier on the eyes and improves readability.
- Adjusted the spacing between items on the frontpage a bit to be clearer.
- Fixed the vertical stretching of table rows with form controls in them.

- Changed the way status messages are printed as per Kristjan's suggestion:
  http://drupal.org/files/issues/error_messages_list.png (issue #9138).

  drupal_set_message() has been changed to group message by type and a
  helper function, theme_status_message(), is added to display the messages.
  Chameleon and Xtemplate have been updated to use this new function.

- Updated CHANGELOG.txt.

- Bug #8823: fixed typo: '..' -> '.'.

- Improved the error/status reporting in Chameleon: made the messages
  stand out a bit better by using green-ish and red-ish colors, resp.
  for 'success' and 'failure'.

- Small change to the way context-sensitive help texts are emitted -
  the pages wouldn't validate in the presence of help texts with
  block-level elements.

 to get of proprietary formats).