summaryrefslogtreecommitdiffstats
path: root/scribus/doc/en/collect4output.html
diff options
context:
space:
mode:
Diffstat (limited to 'scribus/doc/en/collect4output.html')
-rw-r--r--scribus/doc/en/collect4output.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/scribus/doc/en/collect4output.html b/scribus/doc/en/collect4output.html
index f10ca6c..a7cd98a 100644
--- a/scribus/doc/en/collect4output.html
+++ b/scribus/doc/en/collect4output.html
@@ -13,7 +13,7 @@
<p>In summary, what Collect for Output entails is creating a directory for your project, selecting that directory, then Scribus takes it from there, saving the document inside, along with its images, and if you wish, font files and color profiles. Technically, you do not need to create a new directory or choose an empty one, but for many uses, having only the files for the particular project in that directory would make the most sense.</p>
<p>When the document is saved all of the links for the images are changed for the document copy in this new directory. Let's show an example.</p>
<p>&nbsp;</p>
-<table cellpadding="3" width="90%">
+<table cellpadding="3" width="100%">
<tr><td><img src="images/collect_out1.png"></td>
<td><p>Here I am about to collect a project consisting of a presentation document. After selecting <i>File > Collect for Output</i>, I am presented with this dialog, which you can see is strictly for working with directories. At this point I have created a new directory named &ldquo;conference&rdquo;. This is KDE on Linux, so your dialog may differ, but should still have the same functionality.</p>
<p>The next step is to select the <i>conference</i> directory by clicking on it. Don't click <i>OK</i> yet.</p></td></tr>