Dev fix: Add renderer as an initialisation parameter

- The core logic was already present, it just wasn't in the defaults or
  available to be set in the init object

.datatables-commit-sync

@@ -1 +1 @@
-edb86ae044f713f531cfd4ff945034901f50f82a
+36c1b4956c69e3f29913f7a64db290f276f0d7d8

media/js/jquery.dataTables.js

@@ -5915,6 +5915,7 @@
 				"iTabIndex",
 				"fnStateLoadCallback",
 				"fnStateSaveCallback",
+				"renderer",
 				[ "iCookieDuration", "iStateDuration" ], // backwards compat
 				[ "oSearch", "oPreviousSearch" ],
 				[ "aoSearchCols", "aoPreSearchCols" ],
@@ -11070,7 +11071,25 @@
 		 *
 		 *  @deprecated 1.10. Please use `ajax` for this functionality now.
 		 */
-		"sServerMethod": "GET"
+		"sServerMethod": "GET",
+	
+	
+		/**
+		 * DataTables makes use of renderers when displaying HTML elements for
+		 * a table. These renderers can be added or modified by plug-ins to
+		 * generate suitable mark-up for a site. For example the Bootstrap
+		 * integration plug-in for DataTables uses a paging button renderer to
+		 * display pagination buttons in the mark-up required by Bootstrap.
+		 *
+		 * For further information about the renderers available see
+		 * DataTable.ext.renderer
+		 *  @type string|object
+		 *  @default null
+		 *
+		 *  @name DataTable.defaults.renderer
+		 *
+		 */
+		"renderer": null
 	};
 	
 	_fnHungarianMap( DataTable.defaults );