[FIX] Improve language strings, including spelling, grammar, natural expressions, consistency, and gender neutrality.

[FIX] Improve language strings, including spelling, grammar, natural expressions, consistency, and gender neutrality.

[FIX] get headtitle in smarty plugin block title working
[ENH] Remove unnecessary tra

[FIX] User task cleaning: respect user date and time formats, use smarty icon function and famfam icons, clean up text, some indenting. 

[KIL] xajax removal: First pass of removing Xajax.
3rd party library link disconnected and support files removed.
"loadComponent" functionality removed.
Remaining dependant features' (gmap, webmail, shoutbox) ajax operation disabled and marked with AJAX_TODO comments.
[KIL] xajax removal: Part 2 - feature_wiki_save_draft
Table tiki_page_drafts not removed to preserve existing data but removed from tiki.sql for new installs.
Script in devtools started for manual removal.

[ENH] ajax: splitting feature_ajax part 1. New pref for xajax
Part 2. Low level xajax pref checks in smarty blocks, smarty and lib. Also added missing pref tests in tiki-index.php
Part 3. replacement of feature_ajax with ajax_xajax in other files using xajax directly. Other areas (such as Google maps, auto save etc untouched).

[bp/r28407][KIL] Remove redundant textareasize.* (replaced by resize toolbar buttons in Tiki 4.0, and resizable textareas in Tiki 5.0)
Backported from branches/experimental/wysiwyg_ckeditor_update - seems safe - clearing the decks.

[KIL] Remove redundant textareasize.* (replaced by resize toolbar buttons in Tiki 4.0, and resizable textareas in Tiki 5.0)

Note: Removed 'quicktags_over_textarea' pref behaviour. This was broken by the pref renaming - i'm sure this has been discussed and was agred to be an unnecessary overhead to maintain. Toolbars can now only be above the edit area as is consistant with convention.

Manual merge, so possibly a few more bits to come - such as:
TODO:
Rename quicktags to toolbars (coming very soon)
Find/make missing icons
Check no javascript behaviour
Create database upgrade script
Test test test!

[FIX] Make top-right floating help plugins-help, add plugin work with text areas, and also quicktag plugin adding work.

[MOD] Quick fix to change quicktags order to ascending by label so H1, H2, H3 (etc) list in the right order.

DB schema patch to rename "bold" to "  text, bold" etc so they list in a more usable order (and is more consistant across features).

TODO (in quicktags revamp for 3.x)
  Refactor so everything uses smarty_block_textarea()

[MOD] svn:keywords setting - adding property for keyword Id ($Id: ... $) expansion -- $Header: $ CVS keyword is obsolete, use $Id: $ instead

[MOD] SVN Migration: reorganize the directories structure of the repository after the import made by cvs2svn

(Preliminary note : This is a deep modification in tikiwiki's prefs code. Please test first and send feedback if you can)

 * Now use the $prefs array everywhere (in php files also) instead of global vars. This will :

	- allow to use prefs the same way in smarty and php ($prefs array),

	- simplify all code parts that modifiy a preference, because when a pref is modified in php's $prefs array, it is also up-to-date in smarty $prefs array (everything is passed by reference now). So, no more need to reassign values in smarty each time,

	- avoid duplication of values in memory,

	- reduce risks of errors (e.g. collision in variables names, forget to add one of the "global $prefname", ...)


 * All user prefs are now retrieved in one query at tiki-setup stage (as site prefs) and also in session vars (when sessions are used). This will :

	- reduce overhead and database queries after the first page


 * User prefs are now overriding $prefs. This will :

	- simplify the whole usage of $prefs, because only one array is used (no more need, in general, to use tikilib's functions to get user prefs),

	- set some $prefs['site_*'] (listed in the $user_overrider_prefs array of lib/setup/user_prefs.php) for some specific site prefs that needs to be accessed in php (for example when sending mails) and that could have been overrided with the corresponding user pref