Index: branches/unlabeled/unlabeled-1.1.4/core/module_help/languages_edit_general.txt
===================================================================
diff -u -r2326 -r2866
--- branches/unlabeled/unlabeled-1.1.4/core/module_help/languages_edit_general.txt	(.../languages_edit_general.txt)	(revision 2326)
+++ branches/unlabeled/unlabeled-1.1.4/core/module_help/languages_edit_general.txt	(.../languages_edit_general.txt)	(revision 2866)
@@ -1,14 +1,14 @@
-The general tab contains the cultural settings of the pack.
-<ul>
-    <li> Language Id - this field is a read-only, unique and internal system regional package ID. It is also displayed in the URL as a part of the query string.  </li>
-    <li> Pack Name - this field contains the English name of a regional package, or any label the administrator wants to use for the pack.  </li>
-    <li> Local Name - this field contains the name of the regional package in the native language of the pack. For example, for a German regional pack, this field would be set to 'Deutsch.'  </li>
-    <li> Icon URL - this field contains the URL of the image, which will be used to display the regional pack designator icon (usually a country flag, associated with the pack's language). This may be a remote URL, or a local URL, in which case it should be relative to the 'in-portal/themes/[current theme]' directory. The icon is necessary for the language selector in the default theme on the front end.  </li>
-    <li> Date Format - this field contains the date format of the regional pack. The information should be entered using standard programming codes for various formats of days, months and years. For more information about the date codes, please refer to PHP's web site: <a href="http://us2.php.net/manual/en/function.date.php">http://us2.php.net/manual/en/function.date.php </a>. The example to the right of the field shows the resulting format of the current date. This example will update after you save the changes.  </li>
-    <li> Time Format - this field contains the time format of the regional pack. The information should be entered using standard programming codes for various formats of seconds, minutes and hours. For more information about the time codes, please refer to PHP's web site: <a href="http://us2.php.net/manual/en/function.date.php">http://us2.php.net/manual/en/function.date.php </a>. The example to the right of the field shows the resulting format of the current time. This example will update after you save the changes.  </li>
-    <li> Decimal Point - this field contains the character that will be used for separating the decimal part from the whole number. For example, in the U.S. it is a period: '10.00' and in Europe , as well as other locals, it is a comma: '10,00'.  </li>
-    <li> Thousands Separator - this field contains the character that will be used for separating the thousands in numbers.  </li>
-    <li> Enabled - this field is the regional pack status flag.  </li>
-    <li> Primary - this flag indicates whether the pack is primary or not. If you check it while editing a non-primary pack, the pack that used to be primary will no longer be - only one primary pack can exist in a system.  </li>
-    <li> Copy Labels to this Language - this is not an actual attribute of the regional pack, like the other fields on this form. It is a function that will copy all language phrases from another pack, designated in the drop down, into the current pack. It is useful for creation of new regional packs. </li>
+The general tab contains the cultural settings of the pack.
+<ul>
+    <li> Language Id - this field is a read-only, unique and internal system regional package ID. It is also displayed in the URL as a part of the query string.  </li>
+    <li> Pack Name - this field contains the English name of a regional package, or any label the administrator wants to use for the pack.  </li>
+    <li> Local Name - this field contains the name of the regional package in the native language of the pack. For example, for a German regional pack, this field would be set to 'Deutsch.'  </li>
+    <li> Icon URL - this field contains the URL of the image, which will be used to display the regional pack designator icon (usually a country flag, associated with the pack's language). This may be a remote URL, or a local URL, in which case it should be relative to the 'in-portal/themes/[current theme]' directory. The icon is necessary for the language selector in the default theme on the front end.  </li>
+    <li> Date Format - this field contains the date format of the regional pack. The information should be entered using standard programming codes for various formats of days, months and years. For more information about the date codes, please refer to PHP's web site: <a href="http://us2.php.net/manual/en/function.date.php">http://us2.php.net/manual/en/function.date.php </a>. The example to the right of the field shows the resulting format of the current date. This example will update after you save the changes.  </li>
+    <li> Time Format - this field contains the time format of the regional pack. The information should be entered using standard programming codes for various formats of seconds, minutes and hours. For more information about the time codes, please refer to PHP's web site: <a href="http://us2.php.net/manual/en/function.date.php">http://us2.php.net/manual/en/function.date.php </a>. The example to the right of the field shows the resulting format of the current time. This example will update after you save the changes.  </li>
+    <li> Decimal Point - this field contains the character that will be used for separating the decimal part from the whole number. For example, in the U.S. it is a period: '10.00' and in Europe , as well as other locals, it is a comma: '10,00'.  </li>
+    <li> Thousands Separator - this field contains the character that will be used for separating the thousands in numbers.  </li>
+    <li> Enabled - this field is the regional pack status flag.  </li>
+    <li> Primary - this flag indicates whether the pack is primary or not. If you check it while editing a non-primary pack, the pack that used to be primary will no longer be - only one primary pack can exist in a system.  </li>
+    <li> Copy Labels to this Language - this is not an actual attribute of the regional pack, like the other fields on this form. It is a function that will copy all language phrases from another pack, designated in the drop down, into the current pack. It is useful for creation of new regional packs. </li>
 </ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.4/core/module_help/email_messages_edit.txt
===================================================================
diff -u -r2326 -r2866
--- branches/unlabeled/unlabeled-1.1.4/core/module_help/email_messages_edit.txt	(.../email_messages_edit.txt)	(revision 2326)
+++ branches/unlabeled/unlabeled-1.1.4/core/module_help/email_messages_edit.txt	(.../email_messages_edit.txt)	(revision 2866)
@@ -1,8 +1,8 @@
-An email notification has the following fields:
-<ul>
-    <li> Subject - this field contains the subject of the email notification.  </li>
-    <li> Send Email As - This flag designates the email to be either in Plain Text or in the HTML format. Some older email clients cannot display the HTML emails, although they can be formatted a lot better.  </li>
-    <li> Extra Mail Headers &#65533; this field contains additional email headers that you may want to add to the outgoing email notification. The mail headers need to be entered in exact accordance with the email regulations.  </li>
-    <li> Message -this field contains the body of the message. It is possible, and in many cases recommended, to use In-tags in side the email subject and body. The In-tags will allow you to create customized emails. For example, to create an email notification that will address the user by their first and last names, you would use the following In-tags: 'Dear &lt;inp:touser _Field=&quot;FirstName&quot; /&gt; &lt;inp:touser _Field=&quot;LastName&quot; /&gt; '. </li>
-</ul>
+An email notification has the following fields:
+<ul>
+    <li> Subject - this field contains the subject of the email notification.  </li>
+    <li> Send Email As - This flag designates the email to be either in Plain Text or in the HTML format. Some older email clients cannot display the HTML emails, although they can be formatted a lot better.  </li>
+    <li> Extra Mail Headers &#65533; this field contains additional email headers that you may want to add to the outgoing email notification. The mail headers need to be entered in exact accordance with the email regulations.  </li>
+    <li> Message -this field contains the body of the message. It is possible, and in many cases recommended, to use In-tags in side the email subject and body. The In-tags will allow you to create customized emails. For example, to create an email notification that will address the user by their first and last names, you would use the following In-tags: 'Dear &lt;inp:touser _Field=&quot;FirstName&quot; /&gt; &lt;inp:touser _Field=&quot;LastName&quot; /&gt; '. </li>
+</ul>
 The other columns in the list display the information about the event itself, which cannot be changed from the Regional settings section. To change the event properties, please go to the appropriate Events section, for example, Structure &amp; Data -&gt; Email Setting for In-portal platform category events.
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.4/core/module_help/styles_list.txt
===================================================================
diff -u -r2326 -r2866
--- branches/unlabeled/unlabeled-1.1.4/core/module_help/styles_list.txt	(.../styles_list.txt)	(revision 2326)
+++ branches/unlabeled/unlabeled-1.1.4/core/module_help/styles_list.txt	(.../styles_list.txt)	(revision 2866)
@@ -1,14 +1,14 @@
-<meta content="text/html; charset=utf-8" http-equiv="CONTENT-TYPE"/>
-<title></title>
-<meta content="OpenOffice.org 1.1.4  (Linux)" name="GENERATOR"/>
-<meta content="Pavel Kharitonov" name="AUTHOR"/>
-<meta content="20050804;18210000" name="CREATED"/>
-<meta content="20050816;12012000" name="CHANGED"/><style type="text/css"><!--
-@page { size: 8.27in 11.69in; margin: 0.79in }
-P { margin-bottom: 0.08in }
--->
-</style>
-<p style="margin-bottom: 0in;"><span style="font-weight: bold;">Stylesheets<br/>
-<br/>
-</span>The &ldquo;Stylesheets&rdquo; section of the Console lists all available style sheets.  Here you can add, modify and delete the style sheets, as well as enable, disable and clone them.  Remember, that to take effect, a style sheet must be enabled and attached to a theme.</p>
+<meta content="text/html; charset=utf-8" http-equiv="CONTENT-TYPE"/>
+<title></title>
+<meta content="OpenOffice.org 1.1.4  (Linux)" name="GENERATOR"/>
+<meta content="Pavel Kharitonov" name="AUTHOR"/>
+<meta content="20050804;18210000" name="CREATED"/>
+<meta content="20050816;12012000" name="CHANGED"/><style type="text/css"><!--
+@page { size: 8.27in 11.69in; margin: 0.79in }
+P { margin-bottom: 0.08in }
+-->
+</style>
+<p style="margin-bottom: 0in;"><span style="font-weight: bold;">Stylesheets<br/>
+<br/>
+</span>The &ldquo;Stylesheets&rdquo; section of the Console lists all available style sheets.  Here you can add, modify and delete the style sheets, as well as enable, disable and clone them.  Remember, that to take effect, a style sheet must be enabled and attached to a theme.</p>
 <p style="margin-bottom: 0in;">When editing base and block styles, please don&rsquo;t forget that the changes do not take effect until the entire style sheet is saved.</p>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.4/core/module_help/block_style_edit.txt
===================================================================
diff -u -r2326 -r2866
--- branches/unlabeled/unlabeled-1.1.4/core/module_help/block_style_edit.txt	(.../block_style_edit.txt)	(revision 2326)
+++ branches/unlabeled/unlabeled-1.1.4/core/module_help/block_style_edit.txt	(.../block_style_edit.txt)	(revision 2866)
@@ -1,10 +1,10 @@
-Each block style has the following properties:<br/>
-<ul>
-    <li>Selector ID &ndash; internal, read-only ID of the selector.</li>
-    <li>Selector Name &ndash; the CSS name of the selector.  All custom selectors usually start with a &ldquo;.&rdquo;, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc.  The selector name is used in the &ldquo;class&rdquo; attributes of the HTML elements inside theme templates.  Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.</li>
-    <li>Based On &ndash; the name of the base style, related to this block style.</li>
-    <li>Name &ndash; the name of the block style, used for internal reference by the administrator.</li>
-    <li>Description &ndash; this is a field for administrator&rsquo;s notes about the style sheet.</li>
-    <li>Advanced CSS &ndash; this field contains advanced CSS instructions, per CSS 2.1 specifications.  It is optional.</li>
-    <li>Style &ndash; this is the actual definition of the style for this selector.  Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style&rsquo;s properties, which can be modified here.  Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.</li>
+Each block style has the following properties:<br/>
+<ul>
+    <li>Selector ID &ndash; internal, read-only ID of the selector.</li>
+    <li>Selector Name &ndash; the CSS name of the selector.  All custom selectors usually start with a &ldquo;.&rdquo;, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc.  The selector name is used in the &ldquo;class&rdquo; attributes of the HTML elements inside theme templates.  Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.</li>
+    <li>Based On &ndash; the name of the base style, related to this block style.</li>
+    <li>Name &ndash; the name of the block style, used for internal reference by the administrator.</li>
+    <li>Description &ndash; this is a field for administrator&rsquo;s notes about the style sheet.</li>
+    <li>Advanced CSS &ndash; this field contains advanced CSS instructions, per CSS 2.1 specifications.  It is optional.</li>
+    <li>Style &ndash; this is the actual definition of the style for this selector.  Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style&rsquo;s properties, which can be modified here.  Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.</li>
 </ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.2.4/core/admin_templates/js/colorselector.js
===================================================================
diff -u -r2326 -r2866
--- branches/unlabeled/unlabeled-1.2.4/core/admin_templates/js/colorselector.js	(.../colorselector.js)	(revision 2326)
+++ branches/unlabeled/unlabeled-1.2.4/core/admin_templates/js/colorselector.js	(.../colorselector.js)	(revision 2866)
@@ -1,104 +1,104 @@
-	// color Selector
-
-	var aColors = '000000,993300,333300,003300,003366,000080,333399,333333,800000,FF6600,808000,808080,008080,0000FF,666699,808080,FF0000,FF9900,99CC00,339966,33CCCC,3366FF,800080,999999,FF00FF,FFCC00,FFFF00,00FF00,00FFFF,00CCFF,993366,C0C0C0,FF99CC,FFCC99,FFFF99,CCFFCC,CCFFFF,99CCFF,CC99FF,FFFFFF';
-	var $color_selector_field = '';
-	
-	function InitColorSelector()
-	{
-		var $selector = document.getElementById('colorSelector_div');
-		
-		if( !isset($selector) )
-		{
-			var $selector = document.createElement('DIV');
-			$selector.id = 'colorSelector_div';
-			$selector.className = 'table_color1';
-			$selector.style.width = '178px';
-			$selector.style.borderWidth = '1px';
-			$selector.style.borderColor = '#000000';
-			$selector.style.display = 'none';
-			$selector.style.position = 'absolute';
-			$selector.style.borderStyle = 'solid';
-			
-			var $s_table = document.createElement('TABLE');
-			$s_table.id = 'colorSelector';
-			$selector.appendChild($s_table);
-			document.body.appendChild($selector);
-
-			var oTable = document.getElementById('colorSelector');
-			var iCounter = 0;
-			aColors = aColors.split(',');
-
-			while(iCounter < aColors.length)
-			{
-				var oRow = oTable.insertRow(-1);
-				for(var i = 0; i < 8 && iCounter < aColors.length; i++, iCounter++)
-				{
-					var $cell = document.createElement('TD');
-					$cell.innerHTML = '<div class="ColorBox" style="background-color: #'+aColors[iCounter]+'"></div>';
-					$cell.onmouseover = this.colorMouseOver;
-					$cell.onmouseout = this.colorMouseOut;
-					$cell.onclick = this.colorClick;
-					$cell.setAttribute('ColorIndex', iCounter);
-					var oDiv=oRow.insertCell(-1).appendChild($cell);
-				};
-			}
-		}
-	}
-	
-	function updateColor($event,$color_id)
-	{
-		document.getElementById('color_'+$color_id).style.backgroundColor = document.getElementById($color_id).value;
-	}
-	
-	function colorMouseOver($e)
-	{
-		if(!$e) $e = window.event;
-		//print_pre(this);
-		this.parentNode.style.backgroundColor = '#C8D3E2';
-		this.parentNode.style.borderColor = '#7196CC';
-		
-	}
-	
-	function colorMouseOut($e, $element)
-	{
-		if(!$e) $e = window.event;
-		if(!$element) $element = this;
-		$element.parentNode.style.backgroundColor = '#F6F6F6';
-		$element.parentNode.style.borderColor = '#F6F6F6';
-	}
-	
-	function colorClick($e)
-	{
-		if(!$e) $e = window.event;
-		var $color = aColors[ this.getAttribute('ColorIndex') ];
-		
-		document.getElementById('color_'+$color_selector_field).style.backgroundColor = $color;
-		document.getElementById($color_selector_field).value = '#' + $color;
-		document.getElementById('colorSelector_div').style.display = 'none';
-		
-		colorMouseOut($e, this);
-	}
-	
-	function openColorSelector($e, $field)
-	{
-		$color_selector_field = $field;
-		var $div = document.getElementById('colorSelector_div');
-
-		var posx = 0;
-		var posy = 0;
-		if (!$e) var $e = window.event;
-		if ($e.pageX || $e.pageY)
-		{
-			posx = $e.pageX;
-			posy = $e.pageY;
-		}
-		else if ($e.clientX || $e.clientY)
-		{
-			posx = $e.clientX + document.body.scrollLeft;
-			posy = $e.clientY + document.body.scrollTop;
-		}
-
-		$div.style.left = posx;
-		$div.style.top = posy;
-		$div.style.display = 'block';
-	}
+	// color Selector
+
+	var aColors = '000000,993300,333300,003300,003366,000080,333399,333333,800000,FF6600,808000,808080,008080,0000FF,666699,808080,FF0000,FF9900,99CC00,339966,33CCCC,3366FF,800080,999999,FF00FF,FFCC00,FFFF00,00FF00,00FFFF,00CCFF,993366,C0C0C0,FF99CC,FFCC99,FFFF99,CCFFCC,CCFFFF,99CCFF,CC99FF,FFFFFF';
+	var $color_selector_field = '';
+	
+	function InitColorSelector()
+	{
+		var $selector = document.getElementById('colorSelector_div');
+		
+		if( !isset($selector) )
+		{
+			var $selector = document.createElement('DIV');
+			$selector.id = 'colorSelector_div';
+			$selector.className = 'table_color1';
+			$selector.style.width = '178px';
+			$selector.style.borderWidth = '1px';
+			$selector.style.borderColor = '#000000';
+			$selector.style.display = 'none';
+			$selector.style.position = 'absolute';
+			$selector.style.borderStyle = 'solid';
+			
+			var $s_table = document.createElement('TABLE');
+			$s_table.id = 'colorSelector';
+			$selector.appendChild($s_table);
+			document.body.appendChild($selector);
+
+			var oTable = document.getElementById('colorSelector');
+			var iCounter = 0;
+			aColors = aColors.split(',');
+
+			while(iCounter < aColors.length)
+			{
+				var oRow = oTable.insertRow(-1);
+				for(var i = 0; i < 8 && iCounter < aColors.length; i++, iCounter++)
+				{
+					var $cell = document.createElement('TD');
+					$cell.innerHTML = '<div class="ColorBox" style="background-color: #'+aColors[iCounter]+'"></div>';
+					$cell.onmouseover = this.colorMouseOver;
+					$cell.onmouseout = this.colorMouseOut;
+					$cell.onclick = this.colorClick;
+					$cell.setAttribute('ColorIndex', iCounter);
+					var oDiv=oRow.insertCell(-1).appendChild($cell);
+				};
+			}
+		}
+	}
+	
+	function updateColor($event,$color_id)
+	{
+		document.getElementById('color_'+$color_id).style.backgroundColor = document.getElementById($color_id).value;
+	}
+	
+	function colorMouseOver($e)
+	{
+		if(!$e) $e = window.event;
+		//print_pre(this);
+		this.parentNode.style.backgroundColor = '#C8D3E2';
+		this.parentNode.style.borderColor = '#7196CC';
+		
+	}
+	
+	function colorMouseOut($e, $element)
+	{
+		if(!$e) $e = window.event;
+		if(!$element) $element = this;
+		$element.parentNode.style.backgroundColor = '#F6F6F6';
+		$element.parentNode.style.borderColor = '#F6F6F6';
+	}
+	
+	function colorClick($e)
+	{
+		if(!$e) $e = window.event;
+		var $color = aColors[ this.getAttribute('ColorIndex') ];
+		
+		document.getElementById('color_'+$color_selector_field).style.backgroundColor = $color;
+		document.getElementById($color_selector_field).value = '#' + $color;
+		document.getElementById('colorSelector_div').style.display = 'none';
+		
+		colorMouseOut($e, this);
+	}
+	
+	function openColorSelector($e, $field)
+	{
+		$color_selector_field = $field;
+		var $div = document.getElementById('colorSelector_div');
+
+		var posx = 0;
+		var posy = 0;
+		if (!$e) var $e = window.event;
+		if ($e.pageX || $e.pageY)
+		{
+			posx = $e.pageX;
+			posy = $e.pageY;
+		}
+		else if ($e.clientX || $e.clientY)
+		{
+			posx = $e.clientX + document.body.scrollLeft;
+			posy = $e.clientY + document.body.scrollTop;
+		}
+
+		$div.style.left = posx;
+		$div.style.top = posy;
+		$div.style.display = 'block';
+	}
Index: branches/unlabeled/unlabeled-1.1.4/core/module_help/phrase_edit.txt
===================================================================
diff -u -r2326 -r2866
--- branches/unlabeled/unlabeled-1.1.4/core/module_help/phrase_edit.txt	(.../phrase_edit.txt)	(revision 2326)
+++ branches/unlabeled/unlabeled-1.1.4/core/module_help/phrase_edit.txt	(.../phrase_edit.txt)	(revision 2866)
@@ -1,7 +1,7 @@
-A label has the following fields:
-<ul>
-    <li> Phrase Id - this field is a read-only, unique and internal system language phrase ID.  </li>
-    <li> Label - this field contains the system name of the language phrase. This name is used in all templates, and in some settings. For visual convenience, all labels to be used on the front-end start with the prefix 'lu_', and all labels to be used in the administrative console start with the prefix 'la_'. The administrator may use their own conventions for naming the labels, however it is recommended to follow this naming rule to keep the regional pack compatible with the ones produced by Intechnic Corporation. </li>
-    <li> Value - this field contains the label value in the local language of the pack. That is where the translation goes.  </li>
-    <li> Phrase Type - this field designates whether the label is to be used in the front-end, or in the administrative panel, or in both. Unlike the prefix of the label, this field must be set properly, as it drives the caching mechanism.  There are two ways to edit multiple labels at once. The first way is to edit one label, and then to use the blue Previous and Next buttons to go back and forth between the labels. The same order as in the list will be used in this case. The second way is to select multiple labels at once, and click the edit button.  As with any other second-level list, it is very important to remember, that your changes are not actually saved, until the regional package is saved. If you make changes to the labels, and then move to a different section without hitting Save on the regional package level, your changes will be lost. </li>
+A label has the following fields:
+<ul>
+    <li> Phrase Id - this field is a read-only, unique and internal system language phrase ID.  </li>
+    <li> Label - this field contains the system name of the language phrase. This name is used in all templates, and in some settings. For visual convenience, all labels to be used on the front-end start with the prefix 'lu_', and all labels to be used in the administrative console start with the prefix 'la_'. The administrator may use their own conventions for naming the labels, however it is recommended to follow this naming rule to keep the regional pack compatible with the ones produced by Intechnic Corporation. </li>
+    <li> Value - this field contains the label value in the local language of the pack. That is where the translation goes.  </li>
+    <li> Phrase Type - this field designates whether the label is to be used in the front-end, or in the administrative panel, or in both. Unlike the prefix of the label, this field must be set properly, as it drives the caching mechanism.  There are two ways to edit multiple labels at once. The first way is to edit one label, and then to use the blue Previous and Next buttons to go back and forth between the labels. The same order as in the list will be used in this case. The second way is to select multiple labels at once, and click the edit button.  As with any other second-level list, it is very important to remember, that your changes are not actually saved, until the regional package is saved. If you make changes to the labels, and then move to a different section without hitting Save on the regional package level, your changes will be lost. </li>
 </ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.4/core/module_help/base_styles.txt
===================================================================
diff -u -r2326 -r2866
--- branches/unlabeled/unlabeled-1.1.4/core/module_help/base_styles.txt	(.../base_styles.txt)	(revision 2326)
+++ branches/unlabeled/unlabeled-1.1.4/core/module_help/base_styles.txt	(.../base_styles.txt)	(revision 2866)
@@ -1,9 +1,9 @@
-<meta content="text/html; charset=utf-8" http-equiv="CONTENT-TYPE"/>
-<title></title>
-<meta content="OpenOffice.org 1.1.4  (Linux)" name="GENERATOR"/>
-<meta content="Pavel Kharitonov" name="AUTHOR"/>
-<meta content="20050804;18210000" name="CREATED"/>
-<meta content="20050816;12012000" name="CHANGED"/><span style="font-weight: bold;">Base Styles</span><br/>
-<br/>
-This tab lists all base styles of the style sheet.  The base styles have exactly the same properties as the block styles (see above).  They are also managed in the same way, and with the same forms, only there is no option to reset to base style for obvious reasons.<br/>
+<meta content="text/html; charset=utf-8" http-equiv="CONTENT-TYPE"/>
+<title></title>
+<meta content="OpenOffice.org 1.1.4  (Linux)" name="GENERATOR"/>
+<meta content="Pavel Kharitonov" name="AUTHOR"/>
+<meta content="20050804;18210000" name="CREATED"/>
+<meta content="20050816;12012000" name="CHANGED"/><span style="font-weight: bold;">Base Styles</span><br/>
+<br/>
+This tab lists all base styles of the style sheet.  The base styles have exactly the same properties as the block styles (see above).  They are also managed in the same way, and with the same forms, only there is no option to reset to base style for obvious reasons.<br/>
 The base styles define how the general page elements look, as opposed to specific content block styles.
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.4/core/module_help/base_style_edit.txt
===================================================================
diff -u -r2326 -r2866
--- branches/unlabeled/unlabeled-1.1.4/core/module_help/base_style_edit.txt	(.../base_style_edit.txt)	(revision 2326)
+++ branches/unlabeled/unlabeled-1.1.4/core/module_help/base_style_edit.txt	(.../base_style_edit.txt)	(revision 2866)
@@ -1,10 +1,10 @@
-Each block style has the following properties:<br/>
-<ul>
-    <li>Selector ID &ndash; internal, read-only ID of the selector.</li>
-    <li>Selector Name &ndash; the CSS name of the selector.  All custom selectors usually start with a &ldquo;.&rdquo;, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc.  The selector name is used in the &ldquo;class&rdquo; attributes of the HTML elements inside theme templates.  Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.</li>
-    <li>Based On &ndash; the name of the base style, related to this block style.</li>
-    <li>Name &ndash; the name of the block style, used for internal reference by the administrator.</li>
-    <li>Description &ndash; this is a field for administrator&rsquo;s notes about the style sheet.</li>
-    <li>Advanced CSS &ndash; this field contains advanced CSS instructions, per CSS 2.1 specifications.  It is optional.</li>
-    <li>Style &ndash; this is the actual definition of the style for this selector.  Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style&rsquo;s properties, which can be modified here.  Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.</li>
+Each block style has the following properties:<br/>
+<ul>
+    <li>Selector ID &ndash; internal, read-only ID of the selector.</li>
+    <li>Selector Name &ndash; the CSS name of the selector.  All custom selectors usually start with a &ldquo;.&rdquo;, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc.  The selector name is used in the &ldquo;class&rdquo; attributes of the HTML elements inside theme templates.  Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.</li>
+    <li>Based On &ndash; the name of the base style, related to this block style.</li>
+    <li>Name &ndash; the name of the block style, used for internal reference by the administrator.</li>
+    <li>Description &ndash; this is a field for administrator&rsquo;s notes about the style sheet.</li>
+    <li>Advanced CSS &ndash; this field contains advanced CSS instructions, per CSS 2.1 specifications.  It is optional.</li>
+    <li>Style &ndash; this is the actual definition of the style for this selector.  Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style&rsquo;s properties, which can be modified here.  Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.</li>
 </ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.4/core/module_help/stylesheets_edit.txt
===================================================================
diff -u -r2326 -r2866
--- branches/unlabeled/unlabeled-1.1.4/core/module_help/stylesheets_edit.txt	(.../stylesheets_edit.txt)	(revision 2326)
+++ branches/unlabeled/unlabeled-1.1.4/core/module_help/stylesheets_edit.txt	(.../stylesheets_edit.txt)	(revision 2866)
@@ -1,10 +1,10 @@
-<span style="font-weight: bold;">General</span><br/>
-<br/>
-The style sheet edit form contains the following fields:<br/>
-<ul>
-    <li>Stylesheet ID &ndash; internal, read-only system ID of the style sheet.</li>
-    <li>Name &ndash; administrator-assigned friendly name of the style sheet.  It is used to attach it to a theme, and it is not displayed anywhere on the front end.</li>
-    <li>Description &ndash; this is a field for administrator&rsquo;s notes about the style sheet.</li>
-    <li>Advanced CSS &ndash; this field contains advanced CSS instructions, per CSS 2.1 specifications.  It is optional.</li>
-    <li>Enabled &ndash; this checkbox controls whether the style sheet is enabled or disabled.</li>
+<span style="font-weight: bold;">General</span><br/>
+<br/>
+The style sheet edit form contains the following fields:<br/>
+<ul>
+    <li>Stylesheet ID &ndash; internal, read-only system ID of the style sheet.</li>
+    <li>Name &ndash; administrator-assigned friendly name of the style sheet.  It is used to attach it to a theme, and it is not displayed anywhere on the front end.</li>
+    <li>Description &ndash; this is a field for administrator&rsquo;s notes about the style sheet.</li>
+    <li>Advanced CSS &ndash; this field contains advanced CSS instructions, per CSS 2.1 specifications.  It is optional.</li>
+    <li>Enabled &ndash; this checkbox controls whether the style sheet is enabled or disabled.</li>
 </ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.4/core/module_help/block_styles.txt
===================================================================
diff -u -r2326 -r2866
--- branches/unlabeled/unlabeled-1.1.4/core/module_help/block_styles.txt	(.../block_styles.txt)	(revision 2326)
+++ branches/unlabeled/unlabeled-1.1.4/core/module_help/block_styles.txt	(.../block_styles.txt)	(revision 2866)
@@ -1,3 +1,3 @@
-<span style="font-weight: bold;">Block Styles</span><br/>
-<br/>
+<span style="font-weight: bold;">Block Styles</span><br/>
+<br/>
 This tab lists all block styles of the style sheet.  Block styles describe the look &amp; feel of specific content blocks to be used in a theme.  Each block style is based on a base style (see next tab); sometimes it overrides one or more properties of the base style.  You can add, modify and delete block styles, as well as clone and reset them to the base styles they are related to.
\ No newline at end of file