CRM-13946: Backport PR #2185: set default database connection to UTF-8
CRM-14208 additional includes for J3.2.1+
CRM-14334 merge records: allow empty value to overwrite existing value
notice fixes
fix for CRM-14427

----------------------------------------
* CRM-14427: PCP account creation fails if contact already exists
  https://issues.civicrm.org/jira/browse/CRM-14427
notice fixes
CRM-14390 - Inherit CMS language don't work in WordPress

https://issues.civicrm.org/jira/browse/CRM-14390
Merge pull request #2854 from dlobo/CRM-14390

CRM-14390 - Inherit CMS language don't work in WordPress
CRM-14444: templates/CRM/Report/Form/Layout/Table.tpl: right-align report cells that are T_FLOAT.
Merge pull request #2855 from mlutfy/4.4-crm14444

CRM-14444: templates/CRM/Report/Form/Layout/Table.tpl: right-align report cells that are T_FLOAT.
CRM-14439 - CRM_Core_Menu - For breadcrumbs, set forceBackend=1

----------------------------------------
* CRM-14439: WP demo - Access denied when visiting breadcrumb links from field listing
  https://issues.civicrm.org/jira/browse/CRM-14439
CRM-14439 - CRM_Core_Invoke::rebuildMenuAndCaches - Change order

Currently, CRM_Core_Menu::store() truncates "civicrm_menu" and then refills
it; then, CRM_Core_Config::clearCaches (by-way-of clearDBCache) truncates
"civicrm_menu" without refilling.  This seems pointless.  (For CRM-14439,
this has the effect of producing an empty menu table after running setup.sh
-- so the table is eventually filled at some uncontrolled future point.)

The evident intent of "rebuildMenuAndCaches" is to truncate and then refill
the table, so this patch does that.

----------------------------------------
* CRM-14439: WP demo - Access denied when visiting breadcrumb links from field listing
  https://issues.civicrm.org/jira/browse/CRM-14439
Merge pull request #2835 from lcdservices/CRM-14334

CRM-14334 merge records: allow empty value to overwrite existing value
CRM-14208 move joomlaBase outside of condition clause
CRM_Utils_System_WordPress::url - Change code-branch for caes "isset($path)&&isset($query)"

In the other usages of $script and $base, there's a decision to use $script XOR $base as the effective
base-URL.  However, in this branch, the values are concatenated to form the effective base-URL -- which
shouldn't produce a valid base-URL.  (Note: In this context, we're evaluating conditons of isset($path) and
isset($query) which should have no bearing on the validity of $script or $base as a base-URL.)
CRM_Utils_System_WordPress::url - Change code-branch for case "!isset($path)&&!isset($query)"
CRM_Utils_System_WordPress::url - Simplify deep if/else/string-concatenation. Fix forceBackend.
Merge pull request #2843 from kurund/CRM-14427

CRM-14427
CRM-14446 contact.get api tests + fix on date filters

----------------------------------------
* CRM-14446: Contact.get api - birth_date & deceased_date fixes
  https://issues.civicrm.org/jira/browse/CRM-14446
CRM-14446 contact api.getfields declare birth_date & deceased_date high low filters so they will accept strtotime strings

----------------------------------------
* CRM-14446:
  https://issues.civicrm.org/jira/browse/CRM-14446