r21610 by gpittman - fixed some problems with importing text information

Wed Dec 7 23:11:48 UTC 2016

Author: gpittman
Date: Wed Dec  7 23:11:48 2016
New Revision: 21610

URL: http://scribus.net/websvn/listing.php?repname=Scribus&sc=1&rev=21610
Log:
fixed some problems with importing text information

Modified:
    trunk/Scribus/doc/en/WwText.html
    trunk/Scribus/doc/en/menu.xml

Modified: trunk/Scribus/doc/en/WwText.html
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=21610&path=/trunk/Scribus/doc/en/WwText.html
==============================================================================

--- trunk/Scribus/doc/en/WwText.html	(original)
+++ trunk/Scribus/doc/en/WwText.html	Wed Dec  7 23:11:48 2016
@@ -31,9 +31,9 @@
 <p>Plain text into an empty frame will use the default font settings for your text frames, which you can change in <i>File > Preferences > Tools</i>.</p>
 <h3>CSV, HTML, and ODT files</h3>
 <ul>
-<li>CSV files (comma-separated values) are typically generated by spreadsheet or database programs, but they are simple enough that they could be created with a text editor. The data will be arranged so that a comma or some other character tells Scribus when the next field is coming, and a newline tells when the next row comes in the file. On importation, you have an opportunity to declare the separator, and also declare a <i>value separator</i>, typically quotation marks. The value separator is optional, and would be used to allow the inclusion of a comma inside the field. If you check that the first row is a header, those values will be made bold. When Scribus pulls in the data, it will use tabs between the fields. For the header row, these will be center-type and for the rest left-type.</li>
-<li>Considering the wide variety of HTML tags, it shouldn’t be surprising that there are limitations to what Scribus can interpret from an HTML file. It will interpret text only between the <body> and </body> tags and mainly focus on recognizing headers, paragraph and line breaks, and text styles, though the styles available may depend on the fonts on the system. You can expect at least some extraneous text in a complex HTML file. Scribus will assign styles to variously formatted text.</li>
-<li>ODT files (e.g. from LibreOffice) are the recommended format when you want to automatically assign Scribus styles to text you import into a frame. Generally a very good to excellent result can be expected for recognizing and assigning styles, provided that you use styles in Writer (or another wordprocessor that supports ODT). This can also be a workaround for DOC or other files, by importing into Writer and then saving as an ODT file. You cannot expect good results importing tables in this fashion, even in an ODT file.</li>
+<li><b>CSV files</b> (comma-separated values) are typically generated by spreadsheet or database programs, but they are simple enough that they could be created with a text editor. The data will be arranged so that a comma or some other character tells Scribus when the next field is coming, and a newline tells when the next row comes in the file. On importation, you have an opportunity to declare the separator, and also declare a <i>value separator</i>, typically quotation marks. The value separator is optional, and would be used to allow the inclusion of a comma inside the field. If you check that the first row is a header, those values will be made bold. When Scribus pulls in the data, it will use tabs between the fields. For the header row, these will be center-type and for the rest left-type.</li>
+<li>Considering the wide variety of HTML tags, it shouldn’t be surprising that there are limitations to what Scribus can interpret from an <b>HTML file</b>. It will interpret text only between the <body> and </body> tags and mainly focus on recognizing headers, paragraph and line breaks, and text styles, though the styles available may depend on the fonts on the system. You can expect at least some extraneous text in a complex HTML file. Scribus will assign styles to variously formatted text. Check <a href="importhints4.html">Importing HTML files</a> for more detail.</li>
+<li><b>ODT files</b> (for example from LibreOffice) are the recommended format when you want to automatically assign Scribus styles to text you import into a frame. Generally a very good to excellent result can be expected for recognizing and assigning styles, provided that you use styles in Writer (or another wordprocessor that supports ODT). This can also be a workaround for DOC or other files, by importing into Writer and then saving as an ODT file. You cannot expect good results importing tables in this fashion, even in an ODT file.</li>
 </ul>
 <h3>Tagged Files</h3>
 <table cellpadding=3><tr>

Modified: trunk/Scribus/doc/en/menu.xml
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=21610&path=/trunk/Scribus/doc/en/menu.xml
==============================================================================
--- trunk/Scribus/doc/en/menu.xml	(original)
+++ trunk/Scribus/doc/en/menu.xml	Wed Dec  7 23:11:48 2016
@@ -61,7 +61,6 @@
 			<submenuitem text="Importing Vector Drawings" file="importhints2.html"/>
 			<submenuitem text="Importing SVG" file="scribus-svg.html" />
 			<submenuitem text="Importing Clipart Files" file="importclipart.html" />
-			<submenuitem text="Importing Text" file="importhints4.html" />
 			<submenuitem text="Importing OpenOffice.org and ODF Files" file="importhints3.html" />
 			<submenuitem text="Importing HTML Files" file="importhints4.html" />
 		</submenuitem>


