+/**
+ * Templates
+ * You can define your own template set (skin) and put it in a new
+ * directory under SM_PATH/templates. The ID must match the name of
+ * the template directory as the example below. You can name the
+ * template whatever you want. For an example of a template, see
+ * the ones included in the SM_PATH/templates directory.
+ *
+ * To add a new template to the options that users can choose from, just
+ * add a new number to the array at the bottom, and follow the pattern.
+ *
+ * $templateset_default sets the skin that will be used by default
+ * when a user doesn't have a skin selection
+ * in their preferences. (Must be the "ID" of
+ * the desired template set)
+ *
+ * $templateset_fallback tells SquirrelMail which template set (skin)
+ * to use when looking for a file that is not
+ * contained within whatever skin is currently
+ * being used. (Must be the "ID" of the desired
+ * template set)
+ *
+ * $rpc_templateset sets the skin that will be used by default
+ * when a user is making an RPC request. This
+ * does not usually need to be changed, but
+ * can be used to change the RPC protocol that
+ * is used to respond to RPC requets. (Must be
+ * the "ID" of the desired template set and
+ * should NOT be a template set that is included
+ * in the $aTemplateSet list; PLEASE NOTE that
+ * new RPC template sets should always be named
+ * "<skin name>_rpc", as SquirrelMail will assume
+ * any template sets ending in "_rpc" are intended
+ * for its RPC interface only)
+ *
+ * @global string $templateset_default
+ * @global string $templateset_fallback
+ * @global string $rpc_templateset
+ */
+$templateset_default = 'default';
+$templateset_fallback = 'default';
+$rpc_templateset = 'default_rpc';
+
+$aTemplateSet[0]['ID'] = 'default';
+$aTemplateSet[0]['NAME'] = 'Default';
+$aTemplateSet[1]['ID'] = 'default_advanced';
+$aTemplateSet[1]['NAME'] = 'Advanced';
+
+/**
+ * Default interface font size.
+ * @global string $default_fontsize
+ * @since 1.5.1
+ */
+$default_fontsize = '';