r17594 by gpittman - improved image prefs_preflight.png, print2.html

Tue Jun 19 16:27:07 UTC 2012

Author: gpittman
Date: Tue Jun 19 16:27:07 2012
New Revision: 17594

URL: http://scribus.net/websvn/listing.php?repname=Scribus&sc=1&rev=17594
Log:
improved image prefs_preflight.png, print2.html

Modified:
    trunk/Scribus/doc/en/images/prefs_preflight.png
    trunk/Scribus/doc/en/print2.html

Modified: trunk/Scribus/doc/en/images/prefs_preflight.png
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=17594&path=/trunk/Scribus/doc/en/images/prefs_preflight.png
==============================================================================
Binary files - no diff available.

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

--- trunk/Scribus/doc/en/print2.html (original)
+++ trunk/Scribus/doc/en/print2.html Tue Jun 19 16:27:07 2012
@@ -23,7 +23,9 @@
 <table width="100%"><tr><td align="center"><img src="images/prefs_preflight.png"></td></tr></table>
 <p>The options in this panel are as follows:</p>
 <ul>
-<li><b>File Type (drop-down list):</b> Here you can select which print/export filetype’s potential issues Scribus will check for by default.</li>
+<li><b>Show pages without errors:</b> When checked, lists all pages in the output, not just those with errors.</li>
+<li><b>Show errors for items on layers that will not print:</b> Self-explanatory.</li>
+<li><b>Output Profile (drop-down list):</b> Here you can select which print/export filetype’s potential issues Scribus will check for by default.</li>
 <li><b>Ignore all errors:</b> From what you have read before, you can hopefully conclude that you would be ill-advised to check this option â€“ an error discovered <i>after</i> a commercial print-run could prove to be costly. </li>
 <li><b>Automatic check before printing or exporting:</b> Having this option active means that the Preflight Verifier will not only be launched intentionally by you via the Menu Bar, but also automatically when you want to print or to export PostScript or PDF files and in case an error has been detected.</li>
 <li><b>Check for missing glyphs:</b> This option will let Scribus check for missing glyphs in a font. <i>Do not underestimate the importance of this option</i>, as a simple change of a font, e.g. via a style sheet or direct formatting, can result in text using glyphs that aren’t available in the new font.</li>
@@ -31,12 +33,13 @@
 <li><b>Check of overflow in text frames:</b> As an avid reader of this Online Help you know for sure that working with Scribus is mostly <a href="WwFrames.html">frame-based</a>, and of course you are also aware of the <a href="WwText.html">necessity</a> to either reduce the font size or to enlarge a text frame or to link to a subsequent frame if the text doesn’t fit into a particular frame. Similar to the “missing glyphs” issue, one of the likely issues that may ruin or devaluate your costly print is the change of a font, since the glyph widths change from font to font. In some cases, even using the same font on different platforms or even the same font on the same computer may result in a text overflow, as the update may have installed a new version of a font file with different font metrics.</li>
 <li><b>Check for used transparencies:</b> The PostScript file format doesn’t support transparency, and neither does the PDF 1.3 specification, which is still supported by Scribus. Since PDF/X-3 is also based on PDF 1.3, you only need this option active for the three previously mentioned export/print destinations.</li>
 <li><b>Check for missing images:</b> Scribus doesn’t store bitmap images in its own file format; it only creates links to files in one of the <a href="importhints.html">supported bitmap formats</a>. Since it can easily happen that users save an image under a different name, another file format or another location, the link to the image may become a “dead link”, i.e. the <a href="WwImages.html">image frame</a> will be empty, an issue that can be easily overlooked. This option lets Scribus detect such dead links.</li>
+<li><b>Check for part filled image frames:</b> If your image frame has a background color, or has a visible border, this may be important to check for.</li>
 <li><b>Check image resolution:</b> As an enlightened reader you already <a href="importhints.html">know</a> that the resolution of bitmap images can be critical to the success of a print run – if the resolution is too low, images will look awful when printed, and if the resolution is too high, the file size of an exported PostScript or PDF file may be too large to be handled by a commercial Raster Image Processor (RIP). This option will let Scribus check whether the resolution of an image is too high or low for a certain output destination. As you can see, you can change the limits in both directions, but keep in mind that the default values make sense in most cases.</li>
 <li><b>Check for placed PDF files:</b> Scribus can import PDF files into image frames via <a href="toolbox5.html">Ghostscript</a>. However, since Scribus lets Ghostscript “rasterize” (i.e.: create a bitmap image of) an imported PDF file, you may not like the result. Moreover, the quality of the file import depends on the Ghostscript version you have installed. Hence the option to let Scribus check for placed PDF files, which is especially useful if you exchange Scribus files between computers with different Ghostscript versions installed.</li>
 <li><b>Check for GIF images:</b> You already <a href="importhints.html">learned</a> that GIF files have no place in professional printing, but while you know this, you may still receive a ZIP-archive from others with a Scribus file and related images, some of which may very well be GIFs. So while the GIF threat need not be imminent, it doesn’t hurt to leave the check mark where it is by default.</li>
 <li><b>Check for PDF Annotations and Fields:</b> PDF files that contain Annotations and Fields will be rejected by every commercial Raster Image Processor (RIP), so if you want to create a print-ready PDF file, you are advised to have this option active.</li>
+<li><b>Check for Visible/Printable Mismatch in Layers:</b> The possibility to make a layer invisible during the process of designing is very helpful, but forgetting to switch on visibility again may result in a PostScript or PDF file with missing elements. The reverse can also happen: You may create a document with multiple layers for different languages or different color patterns. This option will let Scribus investigate whether a visible layer is also “printable”, and in this context “printable” also means that the layer or its content will be exported.</li>
 <li><b>Ignore non-printable layers:</b> This option will help you to only export the layers that are marked as “printable”, which is especially helpful if you created a file with <a href="layers.html">language-specific layers</a>. </li>
-<li><b>Check for Visible/Printable Mismatch in Layers:</b> The possibility to make a layer invisible during the process of designing is very helpful, but forgetting to switch on visibility again may result in a PostScript or PDF file with missing elements. The reverse can also happen: You may create a document with multiple layers for different languages or different color patterns. This option will let Scribus investigate whether a visible layer is also “printable”, and in this context “printable” also means that the layer or its content will be exported.</li>
 </ul>
 <h3>The Print Preview</h3>
 <p>As mentioned in the previous section, one of the challenges of using an advanced DTP application like Scribus is handling “high-level” PostScript output. If you happen to be able to use a real PostScript printer (which won’t be a device that’s as small as your photo printer), you may start to appreciate some of Scribus’s PostScript/printing features. Let’s have a closer look at the Print Preview, which can be called via <i>File > Print Preview</i>.</p>


