r15792 by christoph - added bitmap font info to importhints1.html

[scribus-commit]

Author: christoph
Date: Sun Nov  7 04:11:25 2010
New Revision: 15792

URL: http://scribus.info/websvn/listing.php?repname=Scribus&sc=1&rev=15792
Log:
added bitmap font info to importhints1.html

Modified:
    trunk/Scribus/doc/en/importhints1.html

Modified: trunk/Scribus/doc/en/importhints1.html
URL: http://scribus.info/websvn/diff.php?repname=Scribus&rev=15792&path=/trunk/Scribus/doc/en/importhints1.html
==============================================================================
--- trunk/Scribus/doc/en/importhints1.html (original)
+++ trunk/Scribus/doc/en/importhints1.html Sun Nov  7 04:11:25 2010
@@ -42,7 +42,15 @@
 <li>Importing an EPS file as a vector drawing may take <b>very</b> long, depending on the complexity of the source file. If you choose this import method, Scribus displays a progress dialog, which can give you an impression of the work that&rsquo;s going on in the background, e.g. analyzing the EPS, and generating native Scribus objects:<br>
 <table width="100%"><tr><td align="center"><img src="images/eps-imp2.png" title="EPS import progress" alt="EPS import progress" /></td></tr></table><br>
 </li>Many EPS files that contain beautiful artwork look like they consist exclusively of vector data. However, if you take a closer look, you will notice that more often than not a &ldquo;vector&rdquo; drawing actually contains bitmap files as well. There can be many reasons for the inclusion of bitmap files in EPS &ldquo;drawings&rdquo;. For example, an artist using Illustrator may have worked with bitmap design elements for performance reasons (using hundreds of vector elements requires much more computing power). Another reason may be that the program that created the EPS has some artistic features that cannot be &ldquo;translated&rdquo; into PostScript, so certain vector elements had to be converted to bitmaps. Also note that many design templates for fliers or postcards combine vector data, bitmaps and fonts into a single file, simply because EPS files can be read by many drawing and page layout programs.<br>
-If you are working with this kind of &ldquo;mixed&rdquo; EPS, you need to be very careful! First, when such a file is being imported into Scribus, Ghostscript will convert every single bitmap in the source file into a format that can be read by Scribus. This may take quite some time, but more importantly, Ghostscript will save every converted bitmap on your hard disk in your home directory, and depending on the content of the source EPS, you may run out of disk space faster than you can imagine! Since Scribus files are plain text and do not store any bitmap data, you will also have to distribute all the converted bitmap files with your SLA file if you want to edit or output the file on another computer. To find the required files, look for files with the name of the original EPS and the file extensions PNG, TIF(F), PSD and DAT (the DAT files are so-called &ldquo;raw&rdquo; bitmaps). This can be quite cumbersome, and you can make your life easier by using <i>File > Collect f!
 or Output</i>.<br>
+If you are working with this kind of &ldquo;mixed&rdquo; EPS, you need to be very careful! First, when such a file is being imported into Scribus, Ghostscript will convert every single bitmap in the source file into a format that can be read by Scribus. This may take quite some time, but more importantly, Ghostscript will save every converted bitmap on your hard disk in your home directory, and depending on the content of the source EPS, you may run out of disk space faster than you can imagine! Since Scribus files are plain text and do not store any bitmap data, you will also have to distribute all the converted bitmap files with your SLA file if you want to edit or output the file on another computer. To find the required files, look for files with the name of the original EPS and the file extensions PNG, TIF(F), PSD and DAT (the DAT files are so-called &ldquo;raw&rdquo; bitmaps). This can be quite cumbersome, and you can make your life easier by using <i>File > Collect f!
 or Output</i>.<br><br>
+<table border="1" align="center">
+  <tbody>
+    <tr>
+      <td><span style="color: red;">A special note for LaTeX users: If your LaTeX file uses bitmap fonts and you create an EPS or PostScript file from your LaTeX source, Ghostscript will create a bitmap for each glyph during import into Scribus, which may result in hundreds or even thousands of tiny bitmaps. If you really need to use a bitmap font, you should either consider using a Scribus <a href="renderframes.html">Render Frame</a> or loading the EPS/PS file into an image frame.</span></td>
+    </tr>
+  </tbody>
+</table>
+<br>
 A second potential issue is bitmap file incompatibility and is most likely to occur with recent versions of Illustrator. Illustrator is often used alongside Photoshop, and the changes made to Photoshop&rsquo;s PSD format since version 6 haven&rsquo;t been published. Thus, Ghostscript&rsquo;s attempts to read or convert those embedded PSDs may fail, which will trigger a warning in Scribus:
 <br><table width="100%"><tr><td align="center"><img src="images/eps-imp3.png" title="Bitmap conversion failure" alt="Bitmap conversion failure" /></td></tr></table><br></li>
 <li>EPS export quality from other applications can vary widely. Some applications unfortunately like to add their own ingredients to the sauce. The first step for testing a failed import is to open the file in <a href="toolbox6.html">GSview</a>, then press <b>M</b> to watch the messages from Ghostscript while it attempts to open the file. When you have a failure in GSview, the messages can be cryptic sometimes, but they may be a helpful pointer to see what is the problem.</li>